Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-12912

Upgrade 5.5.x --> 6.x fails if Amster has been used at some point to export/import

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 6.0.0
    • Fix Version/s: 6.0.0.2, 6.5.0, 6.0.1, 5.5.2
    • Component/s: Amster, upgrade
    • Labels:
    • Environment:
       ForgeRock Access Management 6.0.0-SNAPSHOT Build f219ef7d5b (2018-April-13 02:16)
      Amster OpenAM Shell (5.5.0 build 95de0e129b, JVM: 1.8.0_121)
    • Support Ticket IDs:
    • Verified Version/s:
    • Needs QA verification:
      Yes

      Description

      Bug description

      Upgrade fails 5.5.x --> 6.x
      Upgrade fails 6.0.0 --> 6.0.0.1
      Upgrade fails 6.0.0 --> 6.0.1

      The cause of the failure is that the property "com.iplanet.am.version" is added to the server config (it should only be part of the server defaults) when we import an amster config.
      That cause the installer to think that the server is not upgraded, even after running the upgrade process, making it impossible to upgrade unless this property is manually deleted from ldap (see screenshots)

      How to reproduce the issue

      • Install AM 5.5.x or newer. Let's use 5.5.1 for this example.
      • Export the config using Amster.
      • Install a fresh AM (same version as before, 5.5.1)
      • Import the config with amster.
      • Upgrade to a newer AM, for example AM 6.0.0.
      Expected behaviour
      • Upgrade succeeds
      Current behaviour
      • Restart of AM is required to complete the upgrade
        • The configurator returns to the upgrade screen in a loop

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                pilar.gomez Pilar Gomez [X] (Inactive)
                Reporter:
                AndrewVinall Andrew Vinall
                QA Assignee:
                Filip Kubáň [X] (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: