[MGNLWORKFLOW-210] Migration failed when the customer is using LDAP Created: 13/Feb/14 Updated: 19/May/22 Resolved: 19/May/22 |
|
| Status: | Closed |
| Project: | Magnolia Workflow Module |
| Component/s: | None |
| Affects Version/s: | 5.2.2 |
| Fix Version/s: | 5.3.x |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Magnolia International | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | maintenance, quickwin | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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: |
| Description |
|
The customer is using LDAP, its LDAP usermanager is located before the admin usermanager. Thus a call to UserManager.getUser('eric') will fetch the user eric from LDAP... Changing the order of the usermanager solves the issue, but this workaround cannot be used by the customer. Here is the stacktrace thrown during the migration : 2014-02-12 15:40:05,282 ERROR info.magnolia.module.InstallContextImpl : > Error while installing or updating workflow module. Task 'Update group for user eric' failed. (ProvisionException: Guice provision errors: 1) Module instance for module [ldap] not available, most likely because the module has not yet been started. Inject a Provider<> instead to get access to the module instance when it's available. 1 error) 1) Module instance for module [ldap] not available, most likely because the module has not yet been started. Inject a Provider<> instead to get access to the module instance when it's available. 1 error |
| Comments |
| Comment by Jan Haderka [ 13/Feb/14 ] |
|
Eric and Peter are demo users, the update task to update this user should run only and only when samples are installed, otherwise it should not. |
| Comment by Magnolia International [ 26/May/14 ] |
|
Right, according to the code, user eric is installed only if demo-project is installed. Removing this dependency (with maven exclude) should fix the issue. |
| Comment by Roman Kovařík [ 19/May/22 ] |
|
Hello, This ticket is now marked as closed due to one of the following reasons:
If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you. Thank you, |