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