Description of problem: When proxy is set via heat-templates and deployment started, there is no check for availability of proxy. If proxy is not available, later in a deployment a generic timeout error will be shown, that does not point to the proxy misconfiguration/unavailability Version-Release number of selected component (if applicable): RHOS 12 How reproducible: 100% Steps to Reproduce: 1. Add proxy.yaml with incorrect proxy and/or port specified 2. Start deployment with mentioned yaml used 3. Actual results: Subscription will fail with a host unreachable or timeout Expected results: Before deployment started an error message should be shown, indicating issues connecting to the proxy Additional info:
*** This bug has been marked as a duplicate of bug 1504301 ***