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.
Description of problem:
The 85-write-ifcfg.sh pre-pivot hook seems to be able to miss writing out a bond ifcfg file into /tmp/ifcfg/ if it's combined with a vlan.
If I use kernel args like:
```
rd.break=cleanup rd.neednet=1 vlan=bond0.251:bond0 ip=192.168.122.111::192.168.122.1:255.255.255.0:myhostname:bond0.251:none:192.168.122.1 bond=bond0:ens2,ens3:mode=active-backup,miimon=100
```
I see only a single file get created in `/tmp/ifcfg/`:
```
# ls /tmp/ifcfg/
ifcfg-bond0.251
# cat /tmp/ifcfg/ifcfg-bond0.251
# Generated by dracut initrd
NAME="bond0.251"
ONBOOT=yes
NETBOOT=yes
UUID="5235ffc0-ff86-4d90-9583-b4d560e5974b"
BOOTPROTO=none
IPADDR="192.168.122.111"
NETMASK="255.255.255.0"
GATEWAY="192.168.122.1"
TYPE=Vlan
DEVICE="bond0.251"
VLAN=yes
PHYSDEV="bond0"
```
I would expect more files to get created that represent the bond and the slave devices.
If I leave the vlan out of the picture then more files do get created appropriately. With kernel arguments:
```
rd.break=cleanup rd.neednet=1 ip=192.168.122.111::192.168.122.1:255.255.255.0:myhostname:bond0:none:192.168.122.1 bond=bond0:ens2,ens3:mode=active-backup,miimon=100
```
we get:
```
cleanup:/# tail /tmp/ifcfg/*
==> /tmp/ifcfg/ifcfg-bond0 <==
ONBOOT=yes
NETBOOT=yes
UUID="42aed295-2d2a-4710-b028-e25eceaa523f"
BOOTPROTO=none
IPADDR="192.168.122.111"
NETMASK="255.255.255.0"
GATEWAY="192.168.122.1"
BONDING_OPTS="mode=active-backup miimon=100"
NAME="bond0"
TYPE=Bond
==> /tmp/ifcfg/ifcfg-ens2 <==
# Generated by dracut initrd
NAME="ens2"
TYPE=Ethernet
ONBOOT=yes
NETBOOT=yes
SLAVE=yes
MASTER="bond0"
UUID="b91f34ff-5bd9-4388-9a7a-b9cba9f575f4"
DEVICE="ens2"
==> /tmp/ifcfg/ifcfg-ens3 <==
# Generated by dracut initrd
NAME="ens3"
TYPE=Ethernet
ONBOOT=yes
NETBOOT=yes
SLAVE=yes
MASTER="bond0"
UUID="0c923765-35f4-4bef-9ebf-582d2bd1cf6e"
DEVICE="ens3"
```
Version-Release number of selected component (if applicable):
```
$ rpm -q dracut
dracut-049-70.git20200228.el8.x86_64
```
How reproducible: Always
Steps to Reproduce:
See description
Actual results:
Only ifcfg-bond0.251 in /tmp/ifcfg/
Expected results:
More files getting created that represent the bonds and subordinate devices.
Additional info:
This is on RHCOS 45.82.202007141718-0 tested on rhcos-4.5.2-x86_64-qemu.x86_64.qcow2. This bug was created out of the investigation for https://bugzilla.redhat.com/show_bug.cgi?id=1862146
Comment 3RHEL Program Management
2022-02-04 07:27:13 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.