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

unwanted DHCP on bond port: autoconnect re-enabled by policy

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Undefined Undefined
    • None
    • rhel-9.4
    • NetworkManager
    • No
    • Critical
    • rhel-sst-network-management
    • ssg_networking
    • 0
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None

      Testing OCP deployment with OVS balance-slb bond.

      We have autoconnection disabled to prevent DHCP on the OVS bond slaves during boot.

      no-auto-default=*
      ignore-carrier=*
      

      How-ever DHCP re-enables on the secondary slave, acquires a lease which causes the system to select the wrong IP and fail the OCP deployment

      Reproducible once with no-auto-default=*, and once before without no-auto-default=*

      NetworkManager-1.46.0-21.el9_4.x86_64

      Feb 05 23:26:07 localhost coreos-copy-firstboot-network[1155]: '/mnt/boot_partition/coreos-firstboot-network/eno3.nmconnection' -> '/run/NetworkManager/system-connections/eno3.nmconnection'
      Feb 05 23:26:57 master-2 coreos-boot-edit[2000]: removed '/mnt/boot_partition/coreos-firstboot-network/eno3.nmconnection'
      Feb 05 23:27:01 master-2 coreos-teardown-initramfs[2136]: Only in /run/coreos-teardown-initramfs/connections-compare-1/: eno3.nmconnection
      Feb 05 23:27:01 master-2 coreos-teardown-initramfs[2138]: '/run/NetworkManager/system-connections/eno3.nmconnection' -> '/sysroot/etc/NetworkManager/system-connections/eno3.nmconnection'
      Feb 05 23:27:01 master-2 coreos-teardown-initramfs[2141]: Relabeled /sysroot//etc/NetworkManager/system-connections/eno3.nmconnection from <no context> to system_u:object_r:NetworkManager_etc_rw_t:s0
      Feb 05 23:27:05 master-2 coreos-teardown-initramfs[2136]: Only in /run/coreos-teardown-initramfs/connections-compare-1/: eno3.nmconnection
      Feb 05 23:27:05 master-2 coreos-teardown-initramfs[2138]: '/run/NetworkManager/system-connections/eno3.nmconnection' -> '/sysroot/etc/NetworkManager/system-connections/eno3.nmconnection'
      Feb 05 23:27:05 master-2 coreos-teardown-initramfs[2141]: Relabeled /sysroot//etc/NetworkManager/system-connections/eno3.nmconnection from <no context> to system_u:object_r:NetworkManager_etc_rw_t:s0
      Feb 05 23:27:08 master-2 NetworkManager[2742]: <trace> [1738798028.4744] settings: storage[e1118a10-5096-5835-8828-fa7b580d282a,cb1f4b4c4701435d/keyfile]: change event with connection "eno3" (file "/etc/NetworkManager/system-connections/eno3.nmconnection")
      Feb 05 23:27:08 master-2 NetworkManager[2742]: <trace> [1738798028.4761] policy: block-autoconnect: unblocking port profiles for controller ifname="eno3", uuid="e1118a10-5096-5835-8828-fa7b580d282a"
      Feb 05 23:27:08 master-2 NetworkManager[2742]: <trace> [1738798028.5000] settings: auto-default: cannot create auto-default connection for device eno3: disabled by "no-auto-default"
      Feb 05 23:27:08 master-2 NetworkManager[2742]: <debug> [1738798028.5000] manager: (eno3): assume: cannot generate connection: device has no existing configuration
      
      Feb 05 23:27:09 master-2 NetworkManager[2742]: <debug> [1738798029.0009] manager: (eno3): assume: cannot generate connection: device has no existing configuration
      Feb 05 23:27:09 master-2 NetworkManager[2742]: <debug> [1738798029.4915] manager: (eno3): assume: cannot generate connection: device has no existing configuration
      
      Feb 05 23:29:57 master-2 NetworkManager[1602]: <debug> [1738798197.8367] manager: (eno3): assume: cannot generate connection: device has no existing configuration
      
      Feb 05 23:29:57 master-2 NetworkManager[1602]: <debug> [1738798197.8381] policy: re-enabling autoconnect for all connections on eno3
      Feb 05 23:29:57 master-2 NetworkManager[1602]: <trace> [1738798197.8381] manager: block-autoconnect: device[58113fc3d4f82133,eno2]-profile[1bac443f24e05e57,Wired] Connection]: retries set 1 (is-reset)
      Feb 05 23:29:57 master-2 NetworkManager[1602]: <trace> [1738798197.8381] manager: block-autoconnect: device[d78ffb26a3a12218,eno3]-profile[1bac443f24e05e57,Wired] Connection]: entry created (not initialized)
      Feb 05 23:29:57 master-2 NetworkManager[1602]: <trace> [1738798197.8381] manager: block-autoconnect: device[d78ffb26a3a12218,eno3]-profile[536f181ac4eb9165,eno3] entry created (not initialized)
      Feb 05 23:29:57 master-2 NetworkManager[1602]: <debug> [1738798197.8381] device[d78ffb26a3a12218] (eno3): add_pending_action (3): 'autoactivate'
      
      Feb 05 23:29:57 master-2 NetworkManager[1602]: <trace> [1738798197.8385] manager: block-autoconnect: device[d78ffb26a3a12218,eno3]-profile[1bac443f24e05e57,Wired] Connection]: retries set 1 (is-reset)
      Feb 05 23:29:57 master-2 NetworkManager[1602]: <info>  [1738798197.8409] device (eno3): Activation: starting connection 'Wired Connection' (0c549a54-83e6-46b9-8d80-245bd752abfb)
      
      Feb 05 23:29:57 master-2 NetworkManager[1602]: <trace> [1738798197.8431] policy: block-autoconnect: unblocking port profiles for controller ifname="eno3", uuid="0c549a54-83e6-46b9-8d80-245bd752abfb"
      Feb 05 23:29:57 master-2 NetworkManager[1602]: <trace> [1738798197.8431] policy: block-autoconnect: unblocking child profiles for parent ifname="eno3", uuid="0c549a54-83e6-46b9-8d80-245bd752abfb"
      
      
      Feb 05 23:29:57 master-2 NetworkManager[1602]: <info>  [1738798197.8468] dhcp4 (eno3): activation: beginning transaction (timeout in 90 seconds)
      Feb 05 23:29:57 master-2 NetworkManager[1602]: <debug> [1738798197.8496] dhcp4 (eno3): event: send DISCOVER to 255.255.255.255
      
      Feb 05 23:29:57 master-2 NetworkManager[1602]: <trace> [1738798197.2943] settings: storage[e1118a10-5096-5835-8828-fa7b580d282a,3c9c69e4369d79e9/keyfile]: change event with connection "eno3" (file "/etc/NetworkManager/system-connections/eno3.nmconnection")
      
      Feb 05 23:30:00 master-2 NetworkManager[1602]: <debug> [1738798200.8531] dhcp4 (eno3): event: received OFFER of 192.168.111.47 from 192.168.111.1
      
      
      Feb 05 23:31:00 master-2 NetworkManager[1602]: <trace> [1738798260.6863] keyfile: commit: "/etc/NetworkManager/system-connections/eno3.nmconnection": profile e1118a10-5096-5835-8828-fa7b580d282a (eno3) written
      Feb 05 23:31:00 master-2 NetworkManager[1602]: <trace> [1738798260.6864] settings: storage[e1118a10-5096-5835-8828-fa7b580d282a,3c9c69e4369d79e9/keyfile]: change event with connection "eno3" (file "/etc/NetworkManager/system-connections/eno3.nmconnection")
      Feb 05 23:31:00 master-2 nm-dispatcher[2558]: req:18 'pre-up' [eno3]: environment: CONNECTION_FILENAME=/etc/NetworkManager/system-connections/eno3.nmconnection
      Feb 05 23:31:00 master-2 nm-dispatcher[2558]: req:25 'pre-down' [eno3]: environment: CONNECTION_FILENAME=/etc/NetworkManager/system-connections/eno3.nmconnection
      Feb 05 23:31:00 master-2 nm-dispatcher[2558]: req:26 'down' [eno3]: environment: CONNECTION_FILENAME=/etc/NetworkManager/system-connections/eno3.nmconnection
      Feb 05 23:31:00 master-2 nm-dispatcher[2558]: req:27 'pre-up' [eno3]: environment: CONNECTION_FILENAME=/etc/NetworkManager/system-connections/eno3.nmconnection
      Feb 05 23:31:02 master-2 nm-dispatcher[2558]: req:39 'up' [eno3]: environment: CONNECTION_FILENAME=/etc/NetworkManager/system-connections/eno3.nmconnection
      
      

      DHCP is disabled in all the NMstate

      kargs had ip=dhcp

      ovn:
        bridge-mappings:
          - localnet: localnet-network
            bridge: br-ex
            state: present
      interfaces:
        - name: br-ex
          type: ovs-bridge
          state: up
          ipv4:
            enabled: false
            dhcp: false
          ipv6:
            enabled: false
            dhcp: false
          bridge:
            allow-extra-patch-ports: true
            port:
              - name: br-ex
              - name: patch-ex-to-phy
          ovs-db:
            external_ids:
              bridge-uplink: "patch-ex-to-phy"
        - name: br-ex
          type: ovs-interface
          state: up
          copy-mac-from: eno2
          ipv4:
            enabled: true
            dhcp: true
            auto-route-metric: 48
          ipv6:
            enabled: false
            dhcp: false
        - name: br-phy
          type: ovs-bridge
          state: up
          ipv4:
            enabled: false
            dhcp: false
          ipv6:
            enabled: false
            dhcp: false
          bridge:
            allow-extra-patch-ports: true
            port:
              - name: patch-phy-to-ex
              - name: ovs-bond
                link-aggregation:
                  mode: balance-slb
                  port:
                    - name: eno2
                    - name: eno3
        - name: patch-ex-to-phy
          type: ovs-interface
          state: up
          patch:
            peer: patch-phy-to-ex
        - name: patch-phy-to-ex
          type: ovs-interface
          state: up
          patch:
            peer: patch-ex-to-phy
        - name: eno1
          type: ethernet
          state: up
          ipv4:
            enabled: false
          ipv6:
            enabled: false
        - name: eno2
          type: interface
          state: up
          ipv4:
            enabled: false
          ipv6:
            enabled: false
        - name: eno3
          type: interface
          state: up
          ipv4:
            enabled: false
          ipv6:
            enabled: false
        - name: eno4
          type: interface
          state: up
          ipv4:
            enabled: false
          ipv6:
            enabled: false
        - name: ens2f0
          type: interface
          state: down
          ipv4:
            enabled: false
          ipv6:
            enabled: false
        - name: ens2f1
          type: interface
          state: down
          ipv4:
            enabled: false
          ipv6:
            enabled: false
      
      

              rh-ee-sfaye Stanislas Faye
              rbrattai@redhat.com Ross Brattain
              Network Management Team Network Management Team
              Vladimir Benes Vladimir Benes
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: