Description of problem: When using rhel_reg_http_proxy_* parameters for RHEL subscription, TripleO will never check if the proxy is actually available. If it's not, it will fail and the poor user will never know why (it will probably timeout). Version-Release number of selected component (if applicable): 8, 9, 10, 11, 12. How reproducible: You need a RHSM proxy not available over the network (can be tested with a fake IP). Actual results: 1. Deploy Director with RHSM environment and proxy parameters, with an IP that isn't reachable. 2. Deployment will fail after a timeout when trying to subscribe nodes. Expected results: 1. Deploy Director with RHSM environment and proxy parameters, with an IP that isn't reachable. 2. Deployment should fail to subscribe nodes, since proxy isn't reachable. 3. A message should explain to the user that the proxy isn't available over the network. Additional info: The RHSM proxy feature was introduced in OSP12: https://bugzilla.redhat.com/show_bug.cgi?id=1314480
*** Bug 1505357 has been marked as a duplicate of this bug. ***
I've marked https://bugzilla.redhat.com/show_bug.cgi?id=1505357 a duplicate of this bz. Should we consider backporting your fix to pike/12?
Verified on puddle 2018-05-01.6. Deployment fails with respective message that IP is not reachable.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:2086