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...
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: leapp-repository
Version: 7.9
Hardware: x86_64
OS: Linux
Target Milestone: rc
: ---
Assignee: Leapp team
QA Contact: Alois Mahdal
Depends On:
TreeView+ depends on / blocked
Reported: 2020-10-20 11:11 UTC by Jaison Raju
Modified: 2020-12-03 11:40 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-11-18 20:40:18 UTC
Target Upstream Version:

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

How reproducible:

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/

Note You need to log in before you can comment on or make changes to this bug.