Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1643254

Summary: [OSP13 Backport] Scaling out an overcloud with nodes registered to a Satellite 6 server fails with "msg": "Unable to reach the server at $sat_url:443/subscription", "rc": 69
Product: Red Hat OpenStack Reporter: Sam Doran <sdoran>
Component: ansible-role-redhat-subscriptionAssignee: Sam Doran <sdoran>
Status: CLOSED ERRATA QA Contact: Gurenko Alex <agurenko>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 13.0 (Queens)CC: agurenko, dbecker, dcadzow, emacchi, jcoufal, jjoyce, jschluet, lmarsh, mburns, mcornea, morazi, sdoran
Target Milestone: z3Keywords: FeatureBackport, Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ansible-role-redhat-subscription-1.0.1-4.el7ost Doc Type: Bug Fix
Doc Text:
In prior releases, the Satellite URL was not properly set within role. This caused the system to fail to register with Satellite because it was unable to probe the Satellite server to determine the version. This release derives the rhsm_satellite_url from rhsm_baseurl by default, but allows it to be overridden. It also passes rhsm_baseurl to the registration task to allow force registration and adds an option to ignore certificate errors. This release also adds block and rescue tasks to automatically run recovery tasks in the event of registration failure. This fix enables successful Satellite registration.
 Story Points: ---
Clone Of: 1641180 Environment:
Last Closed: 2018-11-14 01:15:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1641180    
Bug Blocks:    

Comment 9 Gurenko Alex 2018-11-01 12:57:53 UTC 
Verified on puddle 2018-10-30.1

rpm -q ansible-role-redhat-subscription
ansible-role-redhat-subscription-1.0.1-4.el7ost.noarch
Comment 13 errata-xmlrpc 2018-11-14 01:15:50 UTC 
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/RHBA-2018:3611