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.
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 Platform 16.2 (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:0995