-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Highest
-
Affects Version/s: CCMA - 3.4.7, CCMA - 3.4.8, CCMA - 3.4.10, CCMA - 3.4.11, CCMA - 3.4.12, CCMA - 3.4.13, CCMA - 3.4.14, CCMA - 3.4.15, CCMA - 3.4.17, CCMA - 3.5.1, CCMA - 3.6.0, CCMA - 3.7.0, CCMA - 3.7.1, CCMA - 3.8.0, CCMA - 3.9.0, CCMA - 3.9.1, CCMA - 3.9.2, CCMA - 3.9.3, CCMA - 3.9.4, CCMA - 3.9.5, CCMA - 3.9.6, CCMA - 3.9.7, CCMA - 3.9.8, CCMA - 3.9.9, CCMA - 3.9.10, CCMA - 3.9.11, CCMA - 3.9.12, CCMA - 3.9.13, CCMA - 3.9.14, CCMA - 3.9.15, CCMA - 3.9.16, CCMA - 3.9.17, CCMA - 3.10.0, CCMA - 3.10.1, CCMA - 3.10.2, CCMA - 3.10.3, CCMA - 3.10.4, CCMA - 3.10.5, CCMA - 3.10.6, CCMA - 3.10.7, CCMA - 3.10.8, CCMA - 3.10.9, CCMA - 3.10.10, CCMA - 3.10.11, CCMA - 3.10.12, CCMA - 3.10.13, CCMA - 3.11.0
-
Component/s: Apps - Migration Assistant
-
Severity 2 - Major
Issue Summary
This is reproducible on Data Center: yes
App migration containers are getting created for attachments only and space only migrations in CCMA. In very rare circumstances this may cause the migration to get stuck in starting state.
Steps to Reproduce
- Install apps with automated app migration
- Create an attachment only migration
- Execute attachment only migration
- You will see app containers getting created in server logs
Expected Results
App containers are not created in space only and attachment only migrations
Actual Results
App migration containers are created as shown in your server logs and in very rare cases causes your migration to get stuck in starting state.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available