8.180. rhn-client-tools

Bug Fixes

BZ#891746

Previously, the rhn-channel manual page incorrectly referred to the "--username" option instead of "--user". This mistake has been corrected and the rhn-channel manual page now correctly refers to the "--user" option.

BZ#912984

Prior to this update, some messages written in English occurred in the Japanese installation of Red Hat Enterprise Linux 6.4. The untranslated strings have been translated, and the messages are now shown in the correct language.

BZ#983999

Previously, the rhn-client-tools code called by the sosreport utility on Red Hat Enterprise Linux 6 terminated unexpectedly with a traceback. The bug has been fixed and and the information about hardware is now correctly gathered by sosreport.

BZ#994531

Previously, a machine with many CPUs could report large value for idle time for all its processors. Consequently, the idle time value did not fit into XML-RPC's integer limits and running the rhn_check command on a problematic machine resulted in a traceback error. The bug has been fixed and rhn_check in the problematic scenarios works now correctly.

BZ#997637

Previously, the rhn-profile-sync utility terminated unexpectedly with a traceback when an older version of the rhn-virtualization-host package was installed on the machine. The bug has been fixed by requiring a newer version of rhn-virtualization-host.

Bug Fix

BZ#949648

The RHN Proxy did not work properly if separated from a parent by a slow enough network. Consequently, users who attempted to download larger repodata files and RPMs experienced timeouts. This update changes both RHN Proxy and Red Hat Enterprise Linux RHN Client to allow all communications to obey a configured timeout value for connections.

Enhancement

BZ#949640

While Satellite 5.3.0 now has the ability to get the number of CPUs via an API call, there was no function to obtain the number of sockets from the registered systems. This update adds a function to get the number of physical CPU sockets in a managed system from Satellite via an API call.