Upgrade issues with Enterprise-AR and Cloud-AR

This topic describes issues you may encounter during the Enterprise-AR and Cloud-AR upgrade.

• Cloud-AR/ Enterprise-AR node identification issue
• Portmapper issues
• Related topic

Cloud-AR/ Enterprise-AR node identification issue

Old instances of Cloud-AR are referenced instead of Enterprise-AR even after merging Cloud-AR with Enterprise AR.

To fix the issue

Update the product registry (ProductRegistry.xml) on the Enterprise-AR server before you start the BMC Cloud Lifecycle Management upgrade, as follows:

1. Go to the Enterprise-AR host.

2. Back up and update ProductRegistry.xml (C:\Windows\ProductRegistry.xml on Windows and /opt/bmc/ProductRegistry.xml on Linux) with the changes indicated with the bold font:

   <registeredProduct id="G4sn283wZ6m8uDgEy6rl0h1yv9t4h001">
      <productKey>productBMCCloudLifeCycleManagement</productKey>
      <productHome>C:\Program Files\BMC Software\BMCCloudLifeCycleManagement3</productHome>
      <productHomeVariableName>BMC_CLOUD_LIFE_CYCLE_MANGEMENT_HOME</productHomeVariableName>
      <installedConfigurationFileName>BMCCloudLifeCycleManagementInstalledConfiguration.xml</installedConfigurationFileName>
      <installingConfigurationFileName>BMCCloudLifeCycleManagementInstallingConfiguration.xml</installingConfigurationFileName>
      <installHistory>
        <installEntry>
          <timestamp>1336475947694</timestamp>
          <date>May 8, 2012</date>
          <time>4:19:07 AM PDT</time>
          <version majorVersion="1" minorVersion="00" releaseVersion="2"/>
          <installedFeatures>
             <feature>featurePublicExtension</feature>
             <feature>featurePortal</feature>
        </installedFeatures>
       </installEntry>
       <upgradeEntry>
         <timestamp>1404225946815</timestamp>
         <date>July 1, 2014</date>
         <time>7:45:46 AM PDT</time>
         <version majorVersion="1" minorVersion="00" releaseVersion="4"/>
         <addedFeatures/>
       </upgradeEntry>
       <upgradeEntry>
          <timestamp>1404225946815</timestamp>
          <date>July 1, 2014</date>
          <time>7:45:46 AM PDT</time>
          <version majorVersion="1" minorVersion="00" releaseVersion="4"/>
             <addedFeatures>
          <feature>featurePrivateExtension</feature>
             </addedFeatures>
        </upgradeEntry>
      </installHistory>
   </registeredProduct>

3. Back up and update BMCCloudLifeCycleManagementInstalledConfiguration.xml (C:\<install_directory>\BMCCloudLifeCycleManagementInstalledConfiguration.xml on Windows and /<install_directory>/BMCCloudLifeCycleManagementInstalledConfiguration.xml on Linux) with the changes indicated with the bold font:
   <productFeatureMap>
     <productFeature backupOnUpgrade="false" id="featurePublicExtension" independentOfChildren="false" parent="featureCloudDbExtensions" rebootRequiredOnInstall="false" rebootRequiredOnUninstall="false" rebootRequiredOnUpgrade="false" requiredDiskSpaceMode="default" state="INSTALLED" visible="true">
     <version majorVersion="1" minorVersion="00" releaseVersion="4"/>
     <requiredDiskSpaceMap>
      <requiredDiskSpace id="default" size="200 MB"/>
      <requiredDiskSpace id="backup" size="5 MB"/>
      <requiredDiskSpace id="temporary" size="400 MB"/>
      </requiredDiskSpaceMap>
     </productFeature>
   <productFeature backupOnUpgrade="false" id="featurePrivateExtension" independentOfChildren="false" parent="featureCloudDbExtensions" rebootRequiredOnInstall="false" rebootRequiredOnUninstall="false" rebootRequiredOnUpgrade="false" requiredDiskSpaceMode="default" state="INSTALLED" visible="true">
     <version majorVersion="1" minorVersion="00" releaseVersion="4"/>
     <requiredDiskSpaceMap>
      <requiredDiskSpace id="default" size="1 MB"/>
      <requiredDiskSpace id="backup" size="0 bytes"/>
      <requiredDiskSpace id="temporary" size="0 bytes"/>
     </requiredDiskSpaceMap>
     <productFeatureReferenceMap>
      <productFeatureReference id="featurePublicExtension" type="LOCAL"/>
      </productFeatureReferenceMap>
     </productFeature>
     <productFeature backupOnUpgrade="false" id="featurePortal" independentOfChildren="false" rebootRequiredOnInstall="false" rebootRequiredOnUninstall="false" rebootRequiredOnUpgrade="false" requiredDiskSpaceMode="default" state="INSTALLED" visible="true">
     <version majorVersion="1" minorVersion="00" releaseVersion="4"/>
     <requiredDiskSpaceMap>
      <requiredDiskSpace id="default" size="150 MB"/>
      <requiredDiskSpace id="backup" size="5 MB"/>
      <requiredDiskSpace id="temporary" size="1 MB"/>
     </requiredDiskSpaceMap>
   </productFeature>
4. On the Platform Manager host:
   1. Open the <Platform_Manager_Install_dir>\BMCCloudLifeCycleManagement.xml file. 
   2. Update all the instances of Cloud-AR to the Enterprise AR host.
5. Start the install planner to upgrade to 4.6.00 and continue with product integration. 

Portmapper issues

Internal and external customers have sometimes encountered portmapper issues with the AR System server that caused the upgrade to fail. The install planner has an AR dependency that fails to stop the AR services.

To work around this issue

1. Gracefully exit the install planner.
2. Revert the Enterprise-AR or Cloud-AR VM to the last saved snapshot.
3. Re-launch the install planner.
4. Run through the upgrade prompts. 
5. When you reach the Installation Preview panel for the Enterprise-AR or Cloud-AR:
   1. Go to the Enterprise-AR or Cloud-AR VM.
   2. Stop the AR System Portmapper and the BMC Remedy Action Request System Server services.
       
   3. Return to the Installation Preview panel, review the Enterprise-AR Server information, and then click Install.
      The upgrade should be successful. 
6. Continue with the Enterprise-AR or Cloud-AR upgrade, for example, upgrading Atrium Core. 

Related topic

To review other issues that possibly affect upgrades, see Known-and-corrected-issues.