Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionChristophe Besson
2021-08-31 12:32:45 UTC
Description of problem:
Customer falls in the emergency shell in one of the last step of the upgrade (persistentnamingconfig). They have an ixgbe NIC with several VFs enabled on the host. Originally they enabled it with a "homemade fashion" by doing some echoes into /sys from the rc.local boot script. We suggested to change their approach by enabling it thanks to an udev rule, but they claim that leads to the same issue.
Version-Release number of selected component (if applicable):
leapp-repository-0.12.0-2.el7_9.noarch
How reproducible:
100% for the customer.
Unable to reproduce without the HW.
Actual results:
[ 282.416451] localhost upgrade[1235]: ====> * persistentnetnamesconfig
[ 282.416451] localhost upgrade[1235]: Generate udev persistent network naming configuration
[ 282.504037] localhost upgrade[1235]: Process Process-186:
[ 282.504037] localhost upgrade[1235]: Traceback (most recent call last):
[ 282.504037] localhost upgrade[1235]: File "/usr/lib64/python3.6/multiprocessing/process.py", line 258, in _bootstrap
[ 282.504037] localhost upgrade[1235]: self.run()
[ 282.504037] localhost upgrade[1235]: File "/usr/lib64/python3.6/multiprocessing/process.py", line 93, in run
[ 282.504037] localhost upgrade[1235]: self._target(*self._args, **self._kwargs)
[ 282.504037] localhost upgrade[1235]: File "/root/tmp_leapp_py3/leapp/repository/actor_definition.py", line 72, in _do_run
[ 282.504037] localhost upgrade[1235]: actor_instance.run(*args, **kwargs)
[ 282.504037] localhost upgrade[1235]: File "/root/tmp_leapp_py3/leapp/actors/__init__.py", line 335, in run
[ 282.504037] localhost upgrade[1235]: self.process(*args)
[ 282.504037] localhost upgrade[1235]: File "/etc/leapp/repos.d/system_upgrade/el7toel8/actors/persistentnetnamesconfig/actor.py", line 37, in process
[ 282.504037] localhost upgrade[1235]: rhel8_name = rhel8_ifaces_map[iface.mac].name
[ 282.504037] localhost upgrade[1235]: KeyError: 'd6:3e:e4:aa:bb:cc'
[ 282.740480] localhost upgrade[1235]: =========================================================================================================
[ 282.740480] localhost upgrade[1235]: Actor persistentnetnamesconfig unexpectedly terminated with exit code: 1 - Please check the above details
[ 282.740480] localhost upgrade[1235]: =========================================================================================================
Additional info:
Attaching privately the sosreport + rdsosreport
Comment 3Christophe Besson
2021-08-31 12:33:47 UTC
the suggested workaround for now is to disable SR-IOV on the host.