Bug 1827271

Summary: rolling_upgrade.yaml is failing with error "fail on unregistered red hat rhcs linux"
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Guillaume Abrioux <gabrioux>
Component: Ceph-AnsibleAssignee: Guillaume Abrioux <gabrioux>
Status: CLOSED ERRATA QA Contact: Ameena Suhani S H <amsyedha>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.3CC: amsyedha, aschoen, ceph-eng-bugs, ceph-qe-bugs, dsavinea, gmeno, hmunjulu, nthomas, tchandra, tserlin, vashastr, ykaul
Target Milestone: z5   
Target Release: 3.3   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: RHEL: ceph-ansible-3.2.42-1.el7cp Ubuntu: ceph-ansible_3.2.42-2redhat1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1826884 Environment:
Last Closed: 2020-06-10 15:44:19 UTC Type: ---
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: 1826884    
Bug Blocks:    

Description Guillaume Abrioux 2020-04-23 14:05:48 UTC 
+++ This bug was initially created as a clone of Bug #1826884 +++

Description of problem: Updating ceph cluster from RHCS 4 to RHCS 4.1 on rhel 7.8 fails with "fail on unregistered red hat rhcs linux"



Actual results:rolling_upgrade.yaml is failing with "fail on unregistered red hat rhcs linux"


Expected results:rolling_upgrade.yaml should update the cluster from RHCS 4 to RHCS 4.1



Workaround suggested :  https://github.com/ceph/ceph-ansible/pull/5296/files

after making the above change the error is not seen anymore. 

attached are the logs

--- Additional comment from RHEL Program Management on 2020-04-22 17:04:28 UTC ---

Please specify the severity of this bug. Severity is defined here:
https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity.

--- Additional comment from Harish Munjulur on 2020-04-22 17:05:49 UTC ---
Comment 13 errata-xmlrpc 2020-06-10 15:44:19 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-2020:2488