- Previously, the "yum update --disablerepo" command removed a product certificate. As a consequence, the product was no longer installed on the client and it was impossible to retrieve the content. This bug has been fixed, certificates are no longer removed when the "--disablerepo" option is used, and repositories can now be enabled or disabled as expected.
- When the .pem certificate file failed to be located, an exit status of 1 was always returned. As a consequence, an error was indicated also in case no products were installed on the system. With this update, when no products are installed and the "--auto-attach" option is used for registering a system, the message "No products installed" is returned to inform the user that there is no need to attach any subscriptions and the system status is "Current" (green). Also, a zero return code indicates that the registration was successful.
- When configuration options in camelCase are removed from the /etc/rhsm/rhsm.conf file and then restored with the "subscription-manager config" command, they are restored in lowercase. For example, the "subscription-manager config --rhsmcertd.autoattachinterval" command fails to restore the "autoAttachInterval" option in camelCase and, as a consequence, the entry is ignored by the rhsmcertd daemon. However, an existing value can be successfully changed by using such a command. With this update, the "subscription-manager config --remove" command no longer deletes the option from the configuration file but restores its default value instead. As a result, the described problem occurs only when configuration options are manually deleted from /etc/rhsm/rhsm.conf and not reset with the "--remove" option, which is recommended.
- Subscription Manager now includes certificates and maps for Advanced Mission Critical Update Support (AUS). This enables migration from RHN Classic to RHSM for AUS subscriptions.
- The rhn-migrate-classic-to-rhsm tool now supports Activation Keys when registering to RHSM. This simplifies automated migration.
- The rhn-migrate-classic-to-rhsm tool no longer requires RHN Classic credentials if the new "--keep" option is used. This functionality can help simplify automated migration.