- BZ#595837, BZ#751760
Prior to this update, the libraries provided by the rhn-client-tools packages may have occasionally failed with a traceback when the network connection was reset by peer. With this update, the underlying source code has been modified to display an appropriate error message in this situation.
When more then one server was enabled in the /etc/sysconfig/rhn/up2date configuration file and the first server was not available, a yum command such as "yum update" did not attempt to connect to the second server and kept connecting to the first one. This update applies a patch that corrects this error, and when the first server is unavailable, yum now attempts to connect to the second server as expected.
The rhn-channel utility allows users to subscribe or unsubscribe from a channel on the command line. Previously, an attempt to provide both username and password interactively caused the authentication to fail with the "Invalid username/password combination" error message. This happened, because rhn-channel did not remove the newline character from the username. With this update, this error has been corrected, and the rhn-channel utility no longer fails to authenticate the user when correct credentials are entered interactively.
When a user runs the rhn_register utility on a system that is already registered, the utility displays a warning message that the system is already set up for software updates. This update rephrases this warning message for clarity.
When a user registered a system with RHN Classic immediately after its provisioning, the Subscription Manager incorrectly reported that the system is non-compliant. Consequent to this, the user had to log out and then log in to the system to work around this problem. With this update, when a user registers a system with RHN Classic, the Red Hat Network Client Tools now send a message to the Subscription Manager over D-Bus, resolving this issue.
When using the firstboot application to register a system, "RHN Classic Mode" is now selected by default on the "Choose Server" screen.
The underlying implementation of exception handling has been corrected.