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

Bug 2065736

Summary: RHOSP13-16.1 FFU - Use state file for workaround 1925078
Product: Red Hat OpenStack Reporter: Joaquín Veira <jveiraca>
Component: openstack-tripleo-heat-templatesAssignee: Lukas Bezdicka <lbezdick>
Status: CLOSED ERRATA QA Contact: Khomesh Thakre <kthakre>
Severity: medium Docs Contact:
Priority: medium    
Version: 16.1 (Train)CC: jpretori, lbezdick, mburns, omcgonag, ramishra, rrubins, sgolovat, vkoul
Target Milestone: z9Keywords: Triaged
Target Release: 16.1 (Train on RHEL 8.2)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-11.3.2-1.20220407124102.29a02c1.el8ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-12-07 20:29:31 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: 2069662    
Bug Blocks:    

Description Joaquín Veira 2022-03-18 15:30:30 UTC
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 4 Lukas Bezdicka 2022-04-13 15:39:20 UTC
*** Bug 2027942 has been marked as a duplicate of this bug. ***

Comment 16 errata-xmlrpc 2022-12-07 20:29:31 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 (Moderate: Red Hat OpenStack 16.1.9 (openstack-tripleo-heat-templates) security update), 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/RHSA-2022:8796