Hide Forgot
This bug has been copied from bug #664378 and has been proposed to be backported to 5.6 z-stream (EUS).
Created attachment 473936 [details] Patch
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: If a user specifies an incorrect RHN Satellite address in RHEV-H or a network problem prevents a connection between RHEV-H and RHN Satellite, RHEV-H would take a long time to time out. This bug will reduce the time out to 90 seconds and correctly detects if a failure occurred.
Verified in rhev-h 5.6-9.1 ovirt-config-rhn returned an error as expected within 90 seconds while port 443 (https) was DROP by iptables.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -If a user specifies an incorrect RHN Satellite address in RHEV-H or a network problem prevents a connection between RHEV-H and RHN Satellite, RHEV-H would take a long time to time out. This bug will reduce the time out to 90 seconds and correctly detects if a failure occurred.+When Red Hat Enterprise Virtualization Hypervisor failed to connect to Red Hat Network Satellite (for example, due to a network failure or when a user specified an incorrect address), it took a long time for the failed request to time out. This update changes the timeout value to 30 seconds, enables 3 retries, and ensures that the connection failure is now detected as expected.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0352.html