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



    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 6.0.0
    •, 6.5.0, 6.0.1, 5.5.2
    • Amster, upgrade
    •  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)
    • Yes
    • 0
    • No
    • None


      Bug description

      Upgrade fails 5.5.x --> 6.x
      Upgrade fails 6.0.0 -->
      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


        1. Screen Shot 2018-06-04 at 15.27.20.png
          345 kB
          Adam Heath
        2. Screen Shot 2018-06-04 at 15.28.32.png
          386 kB
          Adam Heath
        3. upgradereport.20180413171344
          8 kB
          Andrew Vinall

        Issue Links



              pilar.gomez Pilar Gomez [X] (Inactive)
              AndrewVinall Andrew Vinall
              Filip Kubáň [X] Filip Kubáň [X] (Inactive)
              0 Vote for this issue
              9 Start watching this issue