-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
Not defined
Context:
We recently saw that when the 3.4->3.5 upgrade is run on an instance which has already been upgraded to 3.5, the incomplete userTask check causes an NPE, most likely because the instance index mapping has already changed so the required field does not exist.
The issue itself will be fixed with OPT-5419 for future releases. For 35 his should be documented as a known issue.
AT:
- The potential NPE when running the upgrade on a schema that's already upgraded is documented as a known issue
This is the controller panel for Smart Panels app
- is related to
-
OPT-5419 Creation of UpgradePlan should be skipped if targetVersion same as existing schemaVersion
- Open
- links to