Bug 1984873

Summary: [OSP13->16.1] the leapp persistentnetnamesdisable actor should be removed so that a reboot can be avoided
Product: Red Hat OpenStack Reporter: Jesse Pretorius <jpretori>
Component: openstack-tripleo-heat-templatesAssignee: Jesse Pretorius <jpretori>
Status: CLOSED ERRATA QA Contact: Jason Grosso <jgrosso>
Severity: medium Docs Contact:
Priority: medium    
Version: 16.1 (Train)CC: mburns, rheslop
Target Milestone: z8Keywords: 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.20210728183311.29a02c1.el8ost Doc Type: Enhancement
Doc Text:
With this update, the `LeapActorsToRemove` heat parameter is introduced so that you can remove specific actors from the leapp process if those actors inhibit the upgrade. The `LeapActorsToRemove` heat parameter is role-specific for flexibility.
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-24 11:00:12 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: 1984875    
Bug Blocks:    

Description Jesse Pretorius 2021-07-22 11:33:50 UTC
As mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1983033 after the NIC rename there is a reboot required to activate that rename. This reboot is only actually required to prevent leapp from hard-stopping the upgrade process.

The reboots, however, add a significant amount of time and operational effort to the upgrade process and it is actually completely unnecessary. We can rather just remove the actor so that leapp does not block the upgrade. Once leapp is done, there is a reboot and the new names will take effect then.

Comment 9 errata-xmlrpc 2022-03-24 11:00:12 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 (Red Hat OpenStack Platform 16.1.8 bug fix and enhancement 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-2022:0986