Bug 1823847

We should add a follow up bz that will enforce repositories as well, as the patches here just enforce the rhel release.

For downstream it need a specific patch equivalent to:


sudo sed -i -e 's/tripleo_redhat_enforce_osp.*/tripleo_redhat_enforce_osp: "16.1"/' /usr/share/ansible/roles/tripleo-redhat-enforce/vars/redhat.yml
sudo sed -i -e 's/tripleo_redhat_enforce_os:.*/tripleo_redhat_enforce_os: "8.2"/' /usr/share/ansible/roles/tripleo-redhat-enforce/vars/redhat.yml

as there is no way to make the distinction upstream between 16.0 and 16.1.

If this bug requires doc text for errata release, please set the 'Doc Type' and provide draft text according to the template in the 'Doc Text' field. The documentation team will review, edit, and approve the text.

If this bug does not require doc text, please set the 'requires_doc_text' flag to '-'.

Hi,

Verified.

Tested on undercloud and overcloud with consistent results:
 - not subscribed:

TASK [tripleo-redhat-enforce : fails if not registered] ************************
Tuesday 16 June 2020  19:09:23 +0000 (0:00:01.521)       0:00:21.522 **********
fatal: [compute-0]: FAILED! => {"changed": false, "msg": "Your environment is not subscribed! If it is expected, please set SkipRhelEnforcement to true. For Director the documentation is there https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.0/html-single/ director_installation_and_usage/i
ndex#configuring-the-undercloud-with-environment-files, for the Overcloud you need to add a new parameter file to your deploy command with that parameter set. If this is unexpected, you have to subscribe this node and ensure that RHEL is pinned to 8.2 as this is the only version supported for 16.1."}

 - subscribed but not the right rhel version:


TASK [tripleo-redhat-enforce : fails if the release is not correct] ************
Tuesday 16 June 2020  19:18:26 +0000 (0:00:00.105)       0:00:21.571 **********
fatal: [compute-0]: FAILED! => {"changed": false, "msg": "OSP16.1 is only supported with Red Hat 8.2. Please make sure to pin rhel to 8.2 using: subscription-manager release --set=8.2. You can then proceed with the update."}

  - subscribed to the right rhel version and the update goes on.

No need for a specific doc message.

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:3148