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.
Bug 1889675 - leapp upgrade via director on ceph nodes do not persist network names are expected from persistentnetnamesconfig
Summary: leapp upgrade via director on ceph nodes do not persist network names are exp...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: leapp-repository
Version: 7.9
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Leapp team
QA Contact: Alois Mahdal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-20 11:11 UTC by Jaison Raju
Modified: 2021-09-01 13:14 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-19 07:30:25 UTC
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)

Description Jaison Raju 2020-10-20 11:11:07 UTC 
Description of problem:
I could test this in 2 environments.
In my latest reproducer, controller and ceph role nodes have the same hardware "Supermicro 1029u".
Although, leapp upgrade logs indicate that only controller node's initramfs was built with network link file as expected by persistentnetnamesconfig:

Oct 20 10:02:12 localhost dracut[32160]: Executing: /usr/bin/dracut --install ""/etc/systemd/network/10-leapp-enp175s0f0.link /etc/systemd/network/10-leapp-enp175s0f1.link /etc/systemd/network/10-leapp-enp216s0f0.link /etc/systemd/network/10-leapp-enp216s0f1.link"" -f --kver 4.18.0-193.28.1.el8_2.x86_64


Version-Release number of selected component (if applicable):
tripleo-ansible-0.5.1-1.20200914163925.el8ost.noarch
openstack-tripleo-heat-templates-11.3.2-1.20200914170156.el8ost.noarch
RHOS-16.1-RHEL-8-20201007.n.0

How reproducible:
Always

Steps to Reproduce:
1. Select a hardware that has different nic names in RHEL7 and RHEL8. 
2. Deploy this hardware with ceph via director on osp13.
3. Perform FFU/Upgrades.

Actual results:
persistentnetnamesconfig does not create /etc/systemd/network/10-leapp-* files.
The following command fails at the following task:
openstack overcloud upgrade run --stack overcloud --limit ceph-0
..
TASK [tripleo-network-config : Ensure network service is enabled] **************
Tuesday 20 October 2020  09:47:17 +0000 (0:00:00.102)       0:00:54.564 *******
fatal: [ceph-0]: FAILED! => {"changed": false, "msg": "Unable to start service network: Job for network.service failed because the control process exited with error code.\nSee \"systemctl status network.service\" and \"journalctl -xe\" for details.\n"}         

Expected results:
/etc/systemd/network/10-leapp-* files are created and after leapp reboot, the nic names retain.

Additional info:
If I manually create /etc/systemd/network/ directory and create corresponding files before leapp upgrade, then these files are included in the initramfs and the issue is not seen.

Sosreports: http://perf1.perf.lab.eng.bos.redhat.com/pub/jaison/upgrades-osp13-16.1.1/issues/leapp-persistentnetnamesconfig/
Comment 9 RHEL Program Management 2021-05-19 07:30:25 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Note You need to log in before you can comment on or make changes to this bug.