Considerations for upgrading from version 8.0
This topic describes considerations if you are upgrading from version 8.0 to version 8.2.
Component templates migrated from previous versions can encounter object name conflicts (QM001624875)
Component templates migrated from a previous version of BMC Server Automation can contain a local configuration object that conflicts with a global configuration object defined in the Configuration Object Dictionary. In this situation, when a user opens the template, the user cannot save the template.
If you encounter this issue, open the configuration dictionary and find the object with the same name. Within the component template, create a duplicate of the conflicting configuration object under a different name and delete the original conflicting configuration object.
Snapshots may need to be retaken after upgrade from version 8.0 to version 8.2
Because the snapshot template version may be increased during an upgrade of the Application Server from version 8.0 to version 8.2, you may need to retake snapshots after the upgrade.
Role-Based Access Control (RBAC) User Definitions
When you define a user, you have the option to configure a setting called "User must change password at next logon". When you upgrade to version 8.2, this setting is cleared for all users, including users for whom it was enabled. You must manually reset this option for your users if you want to require them to change passwords at the next logon.
Cleanup process now deletes bnp files following snapshot and audit jobs (QM001668565)
Beginning with version 8.1, BMC Server Automation removes bnp files following snapshot job and audit job execution. It does not create file location entries. The migration from version 8.0 to version 8.2 manages file_location entries marked for deletion. The cleanup process removes these files physically. The migration does not delete bnp files if you have deleted snapshot jobs from a pre-8.0 version without executing a system cleanup. Subsequent cleanups in the updated environment also skip these files.
Upgrade Model Object jobs fail (QM001687395)
In an environment that was migrated from version 8.0 to version 8.2, if a migrated Snapshot or Audit Job or a Component template refers to the FCoEInterface node, Upgrade Model Object Jobs fail with the following error: Snapshot/Audit Option -Attribute "vnicFc_identPoolName" referenced in template part "/" does not exist in the latest version of configuration object "FCoEInterface".
Workaround: Set the model object manually by opening the job or template in editor mode. Browse the server to select the expected object, save it, and rerun the job.
If a Snapshot or Audit Job or a component template does not contain a reference to FCoEInterface, the Upgrade Model Object Job works normally in a migrated environment.