Issue

What were you trying to do that didn't work? https://issues.redhat.com/browse/RHEL-15086 was reproduced when DHCP server is not running. Currently, even a DHCP server is running, nmstate still warns DHCP timeout and causes failure. Please provide the package NVR for which bug is seen: nmstate-2.2.30-1.el9.x86_64 nispor-1.2.14-1.el9.x86_64 NetworkManager-1.47.91-1.el9.x86_64 How reproducible: 100% currently, random in some earlier version Steps to reproduce echo 'interfaces: - name: BR-DHCP state: up description: dhcp server type: linux-bridge bridge: options: stp: enabled: false ipv4: enabled: true address: - ip: 192.168.199.1 prefix-length: 24 ipv6: enabled: true address: - ip: aa:bb:cc::1 prefix-length: 64' | nmstatectl apply cat << EOF > /etc/dnsmasq.d/BR-DHCP.conf interface=BR-DHCP dhcp-range=192.168.199.100,192.168.199.250,255.255.255.0,48h enable-ra dhcp-range=aa:bb:cc::100,aa:bb:cc::ffff,ra-names,slaac,64,480h dhcp-option=option:classless-static-route,192.168.200.0/24,192.168.199.1 dhcp-option=option:dns-server,192.168.199.254 dhcp-option=option:domain-search,ipv4test.dns dhcp-option=option6:24,aa:bb:ccd::/64,aa:bb:cc::1 dhcp-option=option6:dns-server,aa:bb:cc::254 dhcp-option=option6:domain-search,ipv6test.dns EOF systemctl stop firewalld # might be blocking the DHCP responses from dnsmasq systemctl stop systemd-resolved # conflicts with dnsmasq systemctl restart dnsmasq sleep 30 cat << EOF > dhcp_with_static_route.yaml interfaces: - name: bond0 type: bond state: up mtu: 9000 mac-address: d4:ee:07:25:42:5a ipv4: enabled: true dhcp: true ipv6: enabled: true dhcp: true autoconf: true link-aggregation: mode: 802.3ad options: miimon: "150" port: - veth0 - veth1 - name: veth0 type: veth state: up veth: peer: veth0_p - name: veth1 type: veth state: up veth: peer: veth1_p - name: BR-DHCP type: linux-bridge description: TBD can be deleted on RHEL-31981 Failed to specify controller for bond when this bond contains port in desired state state: up bridge: port: - name: bond0_p - name: bond0_p type: bond controller: BR-DHCP state: up mtu: 9000 link-aggregation: mode: 802.3ad port: - veth0_p - veth1_p - name: veth0_p type: veth state: up veth: peer: veth0 - name: veth1_p type: veth state: up veth: peer: veth1 dns-resolver: config: server: - 8.8.8.8 - 2400:3200:baba::1 routes: config: - destination: 0.0.0.0/0 next-hop-address: 192.168.199.1 next-hop-interface: bond0 table-id: 200 - destination: ::/0 next-hop-address: 192:168:199::1 next-hop-interface: bond0 table-id: 200 EOF nmstatectl apply dhcp_with_static_route.yaml Expected results pass Actual results [2024-05-26T14:19:58Z INFO  nmstate::query_apply::net_state] Created checkpoint /org/freedesktop/NetworkManager/Checkpoint/8 [2024-05-26T14:19:58Z INFO  nmstate::nm::profile] Skipping activation of veth0 as its controller bond0 will automatically activate it [2024-05-26T14:19:58Z INFO  nmstate::nm::profile] Skipping activation of veth1 as its controller bond0 will automatically activate it [2024-05-26T14:19:58Z INFO  nmstate::nm::profile] Skipping activation of veth0_p as its controller bond0_p will automatically activate it [2024-05-26T14:19:58Z INFO  nmstate::nm::profile] Skipping activation of veth1_p as its controller bond0_p will automatically activate it [2024-05-26T14:19:58Z INFO  nmstate::nm::query_apply::profile] Modifying connection UUID Some("4ffd512c-db95-4176-807a-bf8d2c80f3cc"), ID Some("BR-DHCP"), type Some("bridge") name Some("BR-DHCP") [2024-05-26T14:19:58Z INFO  nmstate::nm::query_apply::profile] Creating connection UUID Some("939d4771-c974-4e76-8e09-7d7d3cec0e69"), ID Some("bond0"), type Some("bond") name Some("bond0") [2024-05-26T14:19:58Z INFO  nmstate::nm::query_apply::profile] Creating connection UUID Some("5985cfa7-5c0b-4a33-8793-33e7f9011505"), ID Some("bond0_p"), type Some("bond") name Some("bond0_p") [2024-05-26T14:19:58Z INFO  nmstate::nm::query_apply::profile] Creating connection UUID Some("36f89c4e-d4e1-47b3-bed3-5daa600c9031"), ID Some("veth0"), type Some("veth") name Some("veth0") [2024-05-26T14:19:58Z INFO  nmstate::nm::query_apply::profile] Creating connection UUID Some("e9c83eed-982d-456b-b668-75724b4ae2bd"), ID Some("veth1"), type Some("veth") name Some("veth1") [2024-05-26T14:19:58Z INFO  nmstate::nm::query_apply::profile] Creating connection UUID Some("a5121138-5fd4-40ec-a9c3-02c7989b5524"), ID Some("veth0_p"), type Some("veth") name Some("veth0_p") [2024-05-26T14:19:58Z INFO  nmstate::nm::query_apply::profile] Creating connection UUID Some("c04ff667-db6a-44d0-933c-df2c34b6e1a6"), ID Some("veth1_p"), type Some("veth") name Some("veth1_p") [2024-05-26T14:19:58Z INFO  nmstate::nm::query_apply::profile] Activating connection 4ffd512c-db95-4176-807a-bf8d2c80f3cc: BR-DHCP/bridge [2024-05-26T14:19:58Z INFO  nmstate::nm::query_apply::profile] Activating connection 939d4771-c974-4e76-8e09-7d7d3cec0e69: bond0/bond [2024-05-26T14:19:59Z INFO  nmstate::nm::query_apply::profile] Activating connection 5985cfa7-5c0b-4a33-8793-33e7f9011505: bond0_p/bond [2024-05-26T14:19:59Z WARN  nmstate::nm::nm_dbus::device] Unknown Device state reason 77 [2024-05-26T14:19:59Z INFO  nmstate::query_apply::net_state] Retrying on: VerificationError: Verification failure: veth1_p.interface.state desire '"up"', current '"ignore"' [2024-05-26T14:20:00Z WARN  nmstate::nm::nm_dbus::device] Unknown Device state reason 77 [2024-05-26T14:20:00Z INFO  nmstate::query_apply::net_state] Retrying on: VerificationError: Verification failure: veth1_p.interface.state desire '"up"', current '"ignore"' [2024-05-26T14:20:01Z WARN  nmstate::nm::nm_dbus::device] Unknown Device state reason 77 [2024-05-26T14:20:01Z INFO  nmstate::query_apply::net_state] Retrying on: VerificationError: Verification failure: veth1_p.interface.state desire '"up"', current '"ignore"' [2024-05-26T14:20:02Z WARN  nmstate::nm::nm_dbus::device] Unknown Device state reason 77 [2024-05-26T14:20:02Z INFO  nmstate::query_apply::net_state] Retrying on: VerificationError: Verification failure: veth1_p.interface.state desire '"up"', current '"ignore"' [2024-05-26T14:20:03Z WARN  nmstate::nm::nm_dbus::device] Unknown Device state reason 77 [2024-05-26T14:20:03Z INFO  nmstate::query_apply::net_state] Retrying on: VerificationError: Verification failure: veth1_p.interface.state desire '"up"', current '"ignore"' [2024-05-26T14:20:05Z WARN  nmstate::nm::nm_dbus::device] Unknown Device state reason 77 [2024-05-26T14:20:05Z WARN  nmstate::nm::nm_dbus::device] Unknown Device state reason 77 [2024-05-26T14:20:05Z INFO  nmstate::nm::query_apply::apply] Reactivating linux bridge port as its controller has `vlan-default-pvid` changes [2024-05-26T14:20:05Z INFO  nmstate::nm::query_apply::profile] Deactivating connection 5985cfa7-5c0b-4a33-8793-33e7f9011505: bond0_p/bond [2024-05-26T14:20:05Z INFO  nmstate::nm::query_apply::profile] Modifying connection UUID Some("4ffd512c-db95-4176-807a-bf8d2c80f3cc"), ID Some("BR-DHCP"), type Some("bridge") name Some("BR-DHCP") [2024-05-26T14:20:05Z INFO  nmstate::nm::query_apply::profile] Modifying connection UUID Some("939d4771-c974-4e76-8e09-7d7d3cec0e69"), ID Some("bond0"), type Some("bond") name Some("bond0") [2024-05-26T14:20:05Z INFO  nmstate::nm::query_apply::profile] Modifying connection UUID Some("5985cfa7-5c0b-4a33-8793-33e7f9011505"), ID Some("bond0_p"), type Some("bond") name Some("bond0_p") [2024-05-26T14:20:05Z INFO  nmstate::nm::query_apply::profile] Modifying connection UUID Some("36f89c4e-d4e1-47b3-bed3-5daa600c9031"), ID Some("veth0"), type Some("veth") name Some("veth0") [2024-05-26T14:20:05Z INFO  nmstate::nm::query_apply::profile] Modifying connection UUID Some("e9c83eed-982d-456b-b668-75724b4ae2bd"), ID Some("veth1"), type Some("veth") name Some("veth1") [2024-05-26T14:20:05Z INFO  nmstate::nm::query_apply::profile] Modifying connection UUID Some("a5121138-5fd4-40ec-a9c3-02c7989b5524"), ID Some("veth0_p"), type Some("veth") name Some("veth0_p") [2024-05-26T14:20:05Z INFO  nmstate::nm::query_apply::profile] Modifying connection UUID Some("c04ff667-db6a-44d0-933c-df2c34b6e1a6"), ID Some("veth1_p"), type Some("veth") name Some("veth1_p") [2024-05-26T14:20:05Z INFO  nmstate::nm::query_apply::profile] Activating connection 4ffd512c-db95-4176-807a-bf8d2c80f3cc: BR-DHCP/bridge [2024-05-26T14:20:05Z INFO  nmstate::nm::query_apply::profile] Activating connection 939d4771-c974-4e76-8e09-7d7d3cec0e69: bond0/bond [2024-05-26T14:20:05Z INFO  nmstate::nm::query_apply::profile] Activating connection 5985cfa7-5c0b-4a33-8793-33e7f9011505: bond0_p/bond [2024-05-26T14:20:05Z INFO  nmstate::nm::query_apply::profile] Reapplying connection 36f89c4e-d4e1-47b3-bed3-5daa600c9031: veth0/veth [2024-05-26T14:20:05Z INFO  nmstate::nm::query_apply::profile] Reapplying connection e9c83eed-982d-456b-b668-75724b4ae2bd: veth1/veth [2024-05-26T14:20:05Z INFO  nmstate::nm::query_apply::profile] Skip connection activation as its controller already activated its ports: a5121138-5fd4-40ec-a9c3-02c7989b5524: veth0_p/veth [2024-05-26T14:20:05Z INFO  nmstate::nm::query_apply::profile] Skip connection activation as its controller already activated its ports: c04ff667-db6a-44d0-933c-df2c34b6e1a6: veth1_p/veth [2024-05-26T14:20:05Z WARN  nmstate::query_apply::route] Route destination: 0.0.0.0/0 next-hop-interface: bond0 next-hop-address: 192.168.199.1 table-id: 200 still missing due to NetworkManager waiting to receive an IP address [2024-05-26T14:20:05Z INFO  nmstate::query_apply::net_state] Retrying on: VerificationError: Desired route destination: 0.0.0.0/0 next-hop-interface: bond0 next-hop-address: 192.168.199.1 table-id: 200 not found after apply [2024-05-26T14:20:06Z WARN  nmstate::query_apply::route] Route destination: 0.0.0.0/0 next-hop-interface: bond0 next-hop-address: 192.168.199.1 table-id: 200 still missing due to NetworkManager waiting to receive an IP address [2024-05-26T14:20:06Z INFO  nmstate::query_apply::net_state] Retrying on: VerificationError: Desired route destination: 0.0.0.0/0 next-hop-interface: bond0 next-hop-address: 192.168.199.1 table-id: 200 not found after apply [2024-05-26T14:20:07Z WARN  nmstate::query_apply::route] Route destination: 0.0.0.0/0 next-hop-interface: bond0 next-hop-address: 192.168.199.1 table-id: 200 still missing due to NetworkManager waiting to receive an IP address [2024-05-26T14:20:07Z INFO  nmstate::query_apply::net_state] Retrying on: VerificationError: Desired route destination: 0.0.0.0/0 next-hop-interface: bond0 next-hop-address: 192.168.199.1 table-id: 200 not found after apply [2024-05-26T14:20:09Z WARN  nmstate::query_apply::route] Route destination: 0.0.0.0/0 next-hop-interface: bond0 next-hop-address: 192.168.199.1 table-id: 200 still missing due to NetworkManager waiting to receive an IP address [2024-05-26T14:20:09Z INFO  nmstate::query_apply::net_state] Retrying on: VerificationError: Desired route destination: 0.0.0.0/0 next-hop-interface: bond0 next-hop-address: 192.168.199.1 table-id: 200 not found after apply [2024-05-26T14:20:10Z WARN  nmstate::query_apply::route] Route destination: 0.0.0.0/0 next-hop-interface: bond0 next-hop-address: 192.168.199.1 table-id: 200 still missing due to NetworkManager waiting to receive an IP address [2024-05-26T14:20:10Z INFO  nmstate::query_apply::net_state] Rollbacked to checkpoint /org/freedesktop/NetworkManager/Checkpoint/8 NmstateError: VerificationError: Desired route destination: 0.0.0.0/0 next-hop-interface: bond0 next-hop-address: 192.168.199.1 table-id: 200 not found after apply

Release Notes

No. of Comments

Resolution

Not a Bug