This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2175664 - Bond is not configured correctly when in active/backup and BOOTIF is present on kernel command line
Summary: Bond is not configured correctly when in active/backup and BOOTIF is present ...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: anaconda
Version: 9.1
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-06 09:29 UTC by Renaud Métrich
Modified: 2024-01-17 04:25 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-18 16:06:05 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-4766 0 None Migrated None 2023-09-18 16:06:02 UTC
Red Hat Issue Tracker RHELPLAN-150713 0 None None None 2023-03-06 09:30:40 UTC

Description Renaud Métrich 2023-03-06 09:29:28 UTC 
Description of problem:

When installing a system through the network with the network interfaces configured as a bond in active/backup mode, the final network configuration generated by nm-initrd-generator is not correct, leading to the bond to only enslave a single interface when finishing the installation.

The root cause for this seems to have BOOTIF keyword cause additional network interfaces to be created.

Example below.

PXE snippet (booting on enp1s0):
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
IPAPPEND 2
DEFAULT network

label network
    kernel rhel91/vmlinuz
    append initrd=rhel91/initrd.img vconsole.keymap=fr console=tty0 console=ttyS0,115200n8 inst.ks=http://192.168.122.1/bond91.ks ip=bond0:dhcp bond=bond0:enp1s0,enp2s0:mode=active-backup inst.sshd
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

KS snippet:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
network  --bootproto=dhcp --device=bond0 --bondslaves=enp1s0,enp2s0 --bondopts=mode=active-backup --noipv6 --activate --hostname=vm-bond91
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

What shows once in installer:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
[anaconda root@vm-bond91 ~]# ls -l /etc/NetworkManager/system-connections/
total 12
-rw-------. 1 root root 392 Mar  6 09:09 bond0.nmconnection
-rw-------. 1 root root 182 Mar  6 09:09 enp1s0.nmconnection
-rw-------. 1 root root 282 Mar  6 09:09 enp2s0.nmconnection
[anaconda root@vm-bond91 ~]# grep slave /etc/NetworkManager/system-connections/*
/etc/NetworkManager/system-connections/enp2s0.nmconnection:slave-type=bond
[anaconda root@vm-bond91 ~]# nmcli con show
NAME               UUID                                  TYPE      DEVICE 
bond0              137aa253-3c03-40e4-b800-58d26188beb7  bond      bond0  
enp1s0             848a2f9b-93d5-4f8c-84ae-dd9dd0426964  ethernet  enp1s0 
enp2s0             166e056c-5dd4-4095-9c38-32991580b6d3  ethernet  enp2s0 
BOOTIF Connection  a5258cb0-6748-4eeb-b8dc-ce428ccea9b0  ethernet  --     
enp1s0             add3732a-aa2c-436e-9883-c9b89ff05bed  ethernet  --     
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

Here above 3 first connections are green (active), but configuration files for bond are not correct, only "enp2s0" is part of the bond.

When removing BOOTIF, the bond is correctly configured.

Version-Release number of selected component (if applicable):

anaconda-34.25.1.14-1.el9 (RHEL9.1 DVD)

How reproducible:

Always

Steps to Reproduce:
1. Create a VM with 2 network interfaces on same physical network (NAT in my case)
2. Boot with the snippets above

Actual results:

bond0 on installed system is not correct

Expected results:

bond0 configured correctly
Comment 1 RHEL Program Management 2023-09-18 16:04:13 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 2 RHEL Program Management 2023-09-18 16:06:05 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Comment 3 Red Hat Bugzilla 2024-01-17 04:25:28 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.