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

RHEL-9.5: Kickstart installation with DVD for trying to perform bond configuration results with system having unwanted network connections.

Linking RHIVOS CVEs to...Migration: Automation ...Sync from "Extern...XMLWordPrintable

    • Yes
    • Low
    • 2
    • rhel-anaconda
    • 3
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • 25Q3 - July/28, 25Q3 - Aug/11
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • x86_64
    • None

      What were you trying to do that didn't work?

      We are seeing that trying to install RHEL 9.5 and configure bonding through kickstart is creating rogue network interface entries apart from "bond0" and its slaves.

      network --bootproto=static --device=bond0 --ip=192.168.122.100 --netmask=255.255.255.0 --gateway=192.168.122.1 --nameserver=8.8.8.8 --onboot=on --noipv6 --activate --bondslaves=enp1s0,enp7s0
      
      # nmcli c s
      NAME           UUID                                  TYPE      DEVICE 
      bond0          0bd4e74f-c026-4745-a25c-3bd88c405cb3  bond      bond0  
      bond0_slave_1  8a0ac43b-45d5-4cbf-92ce-0d2b48c1ae10  ethernet  enp1s0 
      bond0_slave_2  dc55ffba-98c7-4526-8e69-bffd9209047d  ethernet  enp2s0 
      lo             a8c0a91f-6f65-4088-8c5f-3dabb73d0145  loopback  lo     
      enp1s0         445f480b-9915-4218-b5e4-e283540060fb  ethernet  --     
      enp2s0         e7514a05-1da8-4620-8fa8-97196f2fc1ed  ethernet  --  

      Previously, a similar bug was reported for RHEL 9.4 and was fixed in RHEL 9.5, and the engineering team had verified the anaconda-34.25.5.7-1.el9 version with the fix.

      1. RHEL-38451

       

      Currently, we are seeing this behaviour with the anaconda-34.25.5.9-1.el9 version.

      Please provide the package NVR for which the bug is seen:

      Anaconda-34.25.5.9-1.el9

      How reproducible is this bug?:

      Always

      Steps to reproduce

      1. Install RHEL 9.5 with the kickstart configuration having network configuration as per below.
       network --bootproto=static --device=bond0 --ip=192.168.122.100 --netmask=255.255.255.0 --gateway=192.168.122.1 --nameserver=8.8.8.8 --onboot=on --noipv6 --activate --bondslaves=enp1s0,enp7s0

      Expected results

        
      # nmcli c s
      NAME           UUID                                  TYPE      DEVICE 
      bond0          0bd4e74f-c026-4745-a25c-3bd88c405cb3  bond      bond0  
      bond0_slave_1  8a0ac43b-45d5-4cbf-92ce-0d2b48c1ae10  ethernet  enp1s0 
      bond0_slave_2  dc55ffba-98c7-4526-8e69-bffd9209047d  ethernet  enp2s0 
      lo             a8c0a91f-6f65-4088-8c5f-3dabb73d0145  loopback  lo     

      Actual results

       # nmcli c s
      NAME           UUID                                  TYPE      DEVICE 
      bond0          0bd4e74f-c026-4745-a25c-3bd88c405cb3  bond      bond0  
      bond0_slave_1  8a0ac43b-45d5-4cbf-92ce-0d2b48c1ae10  ethernet  enp1s0 
      bond0_slave_2  dc55ffba-98c7-4526-8e69-bffd9209047d  ethernet  enp2s0 
      lo             a8c0a91f-6f65-4088-8c5f-3dabb73d0145  loopback  lo     
      enp1s0         445f480b-9915-4218-b5e4-e283540060fb  ethernet  --     
      enp2s0         e7514a05-1da8-4620-8fa8-97196f2fc1ed  ethernet  --   

              rvykydal@redhat.com Radek Vykydal
              rhn-support-swthakur Swapnil Thakur
              anaconda-maint-list anaconda-maint-list
              Release Test Team Release Test Team
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: