Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-4766

Bond is not configured correctly when in active/backup and BOOTIF is present on kernel command line

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Major Major
    • rhel-9.4
    • rhel-9.1.0
    • anaconda
    • anaconda-34.25.4.2-1.el9
    • Major
    • sst_installer
    • ssg_front_door
    • 20
    • None
    • False
    • Hide

      None

      Show
      None
    • Yes
    • None
    • Bug Fix
    • Hide
      .The installer now correctly creates bond device with multiple ports and a BOOTIF option

      Previously, the installer created incorrect connection profiles when the installation was booted with a bond network device with multiple ports along with the `BOOTIF` boot option. Consequently, the device used by the BOOTIF option was not added to the bond device though it was configured as one of its ports.

      With this update, the installer now correctly creates profiles in `initramfs` when the `BOOTIF` boot option is used. As a result, all the specified ports are now added to the bond device on the installed system.
      Show
      .The installer now correctly creates bond device with multiple ports and a BOOTIF option Previously, the installer created incorrect connection profiles when the installation was booted with a bond network device with multiple ports along with the `BOOTIF` boot option. Consequently, the device used by the BOOTIF option was not added to the bond device though it was configured as one of its ports. With this update, the installer now correctly creates profiles in `initramfs` when the `BOOTIF` boot option is used. As a result, all the specified ports are now added to the bond device on the installed system.
    • Done
    • None

      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

            rvykydal@redhat.com Radek Vykydal
            rhn-support-rmetrich Renaud M├ętrich
            anaconda-maint-list anaconda-maint-list
            Release Test Team Release Test Team
            Sagar Dubewar Sagar Dubewar
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: