[MGNLCT-190] adding new CT does NOT create workspace Created: 18/May/22  Updated: 27/Dec/23

Status: Accepted
Project: Content Types
Component/s: None
Affects Version/s: 1.3.0
Fix Version/s: 2.0.0

Type: Bug Priority: Critical
Reporter: Christoph Meier Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: VN-Maintenance
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: 4d 1.5h Time Spent: 1d 6.5h
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLREST-434 Change rest endpoint in Resource app ... Selected
dependency
depends upon MAGNOLIA-8481 Review ConfigurationSource / Registry... Selected
supersession
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLCT-221 Implement Sub-task Completed Oanh Thai Hoang  
MGNLCT-222 Review Sub-task Completed Dai Ha  
MGNLCT-223 piQA Sub-task Completed Dai Ha  
MGNLCT-224 Final QA Sub-task Completed Milan Divilek  
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: 6.3 Consolidation
Story Points: 5
Team: DeveloperX

 Description   

The creation of JCR workspace - which should be done when adding ad CT definition with
autoCreate: true
fails.

This has been observed on master after 6.3-hackathon in the context of failing functional tests ContentTypeFunctionalTests (see DEV-1975, DEV-1974) .

Now failing ContentTypeFunctionalTests are also reported for the 6.2-branch (e.g. see https://jenkins.magnolia-cms.com/job/platform/job/ce/job/release%252F6.2/29/#showFailuresLink)

 


You can use the BookShelf app  - used in for ContentTypeFunctionalTests - to reproduce.
=> https://git.magnolia-cms.com/projects/PLATFORM/repos/ce/browse/magnolia-integration-tests/tests/src/test/resources/bookshelf 

Add 1st CT then app as file-based resources - or see what happens in ContentTypeFunctionalTests - but that's maybe harder to debug
-----------------
Result after discovery :
Waiting for the "restore the file-system/resource-origin observation" in DX Core 6.3



 Comments   
Comment by Chuong Doan Huy [ 24/May/22 ]

Adding new content-types and rest-endpoints to the light modules folder is not working. But after restart server, they are registered/work.

Comment by Christoph Meier [ 25/May/22 ]

For the root-cause - why this ticket was created - it also would be interesting whether adding resurces with JCR-origin is expected to work or not - on the new master-branch.

In test-fwk we have the Junit5-extension LightModulesSupport which allows to bootstrap complete light-modules with @LightModule - and this is done by adding resources to resources JCR workspaces via REST.

@LightModule in used in some tests - and we need to know whether we can still use it in the future - or whether we need a replacement/fix for that functionality.

Comment by Oanh Thai Hoang [ 19/Jul/22 ]

Due to revert commit from https://git.magnolia-cms.com/projects/MODULES/repos/content-types/pull-requests/64/overview, this ticket need to reopen

Comment by Jaroslav Simak [ 03/Aug/22 ]

This also happens for Norsu instances that are running locally.

Generated at Mon Feb 12 00:38:01 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.