-
Type:
Service Pack Request
-
Status: Open
-
Resolution: Unresolved
-
Affects Version/s: AGS 3.1, 6.2.2, 6.1.0.9
-
Fix Version/s: AGS 3.4.1
-
Component/s: Records Management, Upgrades
-
Labels:None
-
Bug Priority:
-
ACT Numbers:
01013118, 01017581
Description
- Upgrade will fail when going from 6.1.0 to 6.2.2 with the following stack:
- Before upgrade stack:
- ACS 6.1.0
AGS 3.1.0
Search Services 1.3.0.1
S3 2.3
SAML 1.1.1 (identity provider is OneID)
LibreOffice 5.4.6.1
ImageMagick 7.0.8
OpenJDK 11.0.4
MySQL 5.7.21 (an RDS instance)
LDAP sync from AD
Zip distribution
- ACS 6.1.0
- After upgrade stack:
- ACS 6.2.2
AGS 3.3.1
Search Services 1.4.2
S3 3.0.0
SAML 1.2.1 (identity provider is OneID)
LibreOffice 6.4.5.2
ImageMagick 7.0.10
OpenJDK 11.0.7
MySQL 5.7.28
LDAP sync from AD
Zip distribution
- ACS 6.2.2
Supporting evidence
Steps to reproduce
- Try and upgrade from the above before stack to the after stack
- Try to start up Alfresco after the fact and you will get:
-
- 2020-08-11 01:08:19,403 ERROR [web.context.ContextLoader] [localhost-startStop-1] Context initialization failed
org.alfresco.service.cmr.security.NoSuchPersonException: 07110025 User does not exist and could not be created: System
- 2020-08-11 01:08:19,403 ERROR [web.context.ContextLoader] [localhost-startStop-1] Context initialization failed
Expected Behaviour
- Upgrade should go smoothly and not cause any errors upon startup
Observed Behaviour
- After upgrading and the initial startup is failing with logging such as:
-
- NoSuchPersonException: 07020024 User does not exist and could not be created: System
Additional notes:
- It appears the RM version could be the cause of the issue as there is a similar RM Jira in the past that does not have much attention that I will attach to this JIRA.
- Customer at this time - has been told to upgrade to the latest service pack of 6.1 (6.1.1) before ultimately heading towards 6.2.2 to see if that will remedy the issue.