Bug 2069662

Summary: RHOSP13-16.2 FFU - Use state file for workaround 1925078
Product: Red Hat OpenStack Reporter: Jesse Pretorius <jpretori>
Component: openstack-tripleo-heat-templatesAssignee: Lukas Bezdicka <lbezdick>
Status: CLOSED ERRATA QA Contact: Archana Singh <arcsingh>
Severity: medium Docs Contact:
Priority: medium    
Version: 16.2 (Train)CC: arcsingh, mburns
Target Milestone: z3Keywords: Triaged
Target Release: 16.2 (Train on RHEL 8.4)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-11.6.1-2.20220405015036.0d9c70c.el8ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-22 16:06:16 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:    
Bug Blocks: 2065736    

Description Jesse Pretorius 2022-03-29 12:14:13 UTC
This bug was initially created as a copy of Bug #2065736

I am copying this bug because: 

The same bug & fix is true for 16.2

Description of problem:
Due to possibility of crashes during run and issues with either leapp or simple ansible execution changes we need to preserve state of WA for rhbz#1925078. Best
solution for this is to create state file and remove it after the upgrade passed.

Version-Release number of selected component (if applicable):
FFU RHOSP13 - RHOSP16.1

How reproducible:
FFU 13 - 16.1

Steps to Reproduce:
1. system_upgrade_prepare: succeeds.

2. system_upgrade: fails, no leapp kernel entry is seen in the grub menu upon reboot. Server boots into rhel 7.

3. system_upgrade: succeeds. 
The current thinking is that this is due to the previous step executing the workaround to mount the correct boot partition. At that point the grub entry for the leapp kernel is made persistent.

4. upgrade_run: failed with selinux context issue on /dev/log:
fatal: [xxxxx]: FAILED! => {"ansible_job_id": "655327715116.74431", "attempts": 3, "changed": true, "cmd": "set -o pipefail; puppet apply  --modulepath=/etc/puppet/modules:/opt/stack/puppet-modules:/usr/share/openstack-puppet/modules --detailed-exitcodes --summarize --color=false   /var/lib/tripleo-config/puppet_step_config.pp 2>&1 | logger -s -t puppet-user", "delta": "0:00:04.185379", "end": "2022-03-17 12:58:10.550703", "failed_when_result": true, "finished": 1, "msg": "non-zero return code", "rc": 1, "start": "2022-03-17 12:58:06.365324", "stderr": "logger: socket /dev/log: Connection refused", "stderr_lines": ["logger: socket /dev/log: Connection refused"], "stdout": "", "stdout_lines": []}

5. upgrade_run: succeeds.

Actual results:


Expected results:


Additional info:

Comment 16 errata-xmlrpc 2022-06-22 16:06:16 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 (Release of components for Red Hat OpenStack Platform 16.2.3 (Train)), 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-2022:4793