-
Bug
-
Resolution: Done-Errata
-
Normal
-
rhel-9.4
-
nmstate-2.2.26-1.el9
-
Yes
-
None
-
Regression
-
1
-
rhel-sst-network-management
-
ssg_networking
-
6
-
1
-
False
-
-
No
-
NMT - RHEL-9.5 DTM 4
-
-
Pass
-
Automated
-
None
What were you trying to do that didn't work?
A regression of https://bugzilla.redhat.com/show_bug.cgi?id=2169982
Please provide the package NVR for which bug is seen:
nmstate-2.2.16-1.el9.x86_64
How reproducible:
100%
Steps to reproduce
echo '
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
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
' | nmstatectl apply
Expected results
Pass
Actual results
[2023-10-31T09:25:58Z INFO nmstate::query_apply::net_state] Created checkpoint /org/freedesktop/NetworkManager/Checkpoint/228
[2023-10-31T09:25:58Z INFO nmstate::nm::settings::connection] Creating veth peer profile veth0_p for veth0
[2023-10-31T09:25:58Z INFO nmstate::nm::profile] Skipping activation of veth0 as its controller bond0 will automatically activate it
[2023-10-31T09:25:58Z INFO nmstate::nm::profile] Skipping activation of veth0 as its controller bond0 will automatically activate it
[2023-10-31T09:25:58Z INFO nmstate::nm::settings::connection] Creating veth peer profile veth1_p for veth1
[2023-10-31T09:25:58Z INFO nmstate::nm::profile] Skipping activation of veth1 as its controller bond0 will automatically activate it
[2023-10-31T09:25:58Z INFO nmstate::nm::profile] Skipping activation of veth1 as its controller bond0 will automatically activate it
[2023-10-31T09:25:58Z INFO nmstate::nm::query_apply::profile] Creating connection UUID Some("a8be7d40-82fe-4524-b467-43cda1d69567"), ID Some("bond0"), type Some("bond") name Some("bond0")
[2023-10-31T09:25:58Z INFO nmstate::nm::query_apply::profile] Creating connection UUID Some("e8bf1f98-8b07-4219-8361-496c50e9f6b6"), ID Some("veth0"), type Some("veth") name Some("veth0")
[2023-10-31T09:25:58Z INFO nmstate::nm::query_apply::profile] Creating connection UUID Some("cef30de1-ca38-49d3-9993-2430d680b8af"), ID Some("veth0_p"), type Some("veth") name Some("veth0_p")
[2023-10-31T09:25:58Z INFO nmstate::nm::query_apply::profile] Creating connection UUID Some("7ef951a0-9b61-4e2f-b8f0-20a814cd567b"), ID Some("veth1"), type Some("veth") name Some("veth1")
[2023-10-31T09:25:58Z INFO nmstate::nm::query_apply::profile] Creating connection UUID Some("b31063bd-8a02-412a-8b77-cc7f8ce1aa17"), ID Some("veth1_p"), type Some("veth") name Some("veth1_p")
[2023-10-31T09:25:58Z INFO nmstate::nm::query_apply::profile] Activating connection a8be7d40-82fe-4524-b467-43cda1d69567: bond0/bond
[2023-10-31T09:25:58Z INFO nmstate::query_apply::net_state] Retrying on: VerificationError: Verification failure: bond0.interface.link-aggregation.port desire '["veth0","veth1"]', current '["veth0"]'
[2023-10-31T09:25:59Z INFO nmstate::query_apply::net_state] Retrying on: VerificationError: Desired route destination: ::/0 next-hop-interface: bond0 next-hop-address: 192:168:199::1 table-id: 200 not found after apply
[2023-10-31T09:26:00Z INFO nmstate::query_apply::net_state] Retrying on: VerificationError: Desired route destination: ::/0 next-hop-interface: bond0 next-hop-address: 192:168:199::1 table-id: 200 not found after apply
[2023-10-31T09:26:01Z INFO nmstate::query_apply::net_state] Retrying on: VerificationError: Desired route destination: ::/0 next-hop-interface: bond0 next-hop-address: 192:168:199::1 table-id: 200 not found after apply
[2023-10-31T09:26:02Z INFO nmstate::query_apply::net_state] Retrying on: VerificationError: Desired route destination: ::/0 next-hop-interface: bond0 next-hop-address: 192:168:199::1 table-id: 200 not found after apply
[2023-10-31T09:26:05Z INFO nmstate::nm::settings::connection] Creating veth peer profile veth0_p for veth0
[2023-10-31T09:26:05Z INFO nmstate::nm::settings::connection] Creating veth peer profile veth1_p for veth1
[2023-10-31T09:26:05Z INFO nmstate::nm::query_apply::profile] Modifying connection UUID Some("a8be7d40-82fe-4524-b467-43cda1d69567"), ID Some("bond0"), type Some("bond") name Some("bond0")
[2023-10-31T09:26:05Z INFO nmstate::nm::query_apply::profile] Modifying connection UUID Some("e8bf1f98-8b07-4219-8361-496c50e9f6b6"), ID Some("veth0"), type Some("veth") name Some("veth0")
[2023-10-31T09:26:05Z INFO nmstate::nm::query_apply::profile] Modifying connection UUID Some("cef30de1-ca38-49d3-9993-2430d680b8af"), ID Some("veth0_p"), type Some("veth") name Some("veth0_p")
[2023-10-31T09:26:05Z INFO nmstate::nm::query_apply::profile] Modifying connection UUID Some("7ef951a0-9b61-4e2f-b8f0-20a814cd567b"), ID Some("veth1"), type Some("veth") name Some("veth1")
[2023-10-31T09:26:05Z INFO nmstate::nm::query_apply::profile] Modifying connection UUID Some("b31063bd-8a02-412a-8b77-cc7f8ce1aa17"), ID Some("veth1_p"), type Some("veth") name Some("veth1_p")
[2023-10-31T09:26:05Z INFO nmstate::nm::query_apply::profile] Activating connection a8be7d40-82fe-4524-b467-43cda1d69567: bond0/bond
[2023-10-31T09:26:05Z INFO nmstate::nm::query_apply::profile] Reapplying connection e8bf1f98-8b07-4219-8361-496c50e9f6b6: veth0/veth
[2023-10-31T09:26:05Z INFO nmstate::nm::query_apply::profile] Activating connection cef30de1-ca38-49d3-9993-2430d680b8af: veth0_p/veth
[2023-10-31T09:26:05Z INFO nmstate::nm::query_apply::profile] Reapplying connection 7ef951a0-9b61-4e2f-b8f0-20a814cd567b: veth1/veth
[2023-10-31T09:26:05Z INFO nmstate::nm::query_apply::profile] Activating connection b31063bd-8a02-412a-8b77-cc7f8ce1aa17: veth1_p/veth
[2023-10-31T09:26: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
[2023-10-31T09:26: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
[2023-10-31T09:26: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
[2023-10-31T09:26:08Z 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
[2023-10-31T09:26:09Z INFO nmstate::query_apply::net_state] Rollbacked to checkpoint /org/freedesktop/NetworkManager/Checkpoint/228
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
- links to
-
RHEA-2024:129019 Bug fixes and enhancements of nmstate