Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1831117[details]
logs
Description of problem:
We are hitting a random issue in kubernetes-nmstate CI in a scenario with ovs-bridge and default eth0 interface connected to the ovs-bridge. The ovs-bridge is successfully created and the dynamic IP address is succesfully moved to a internal port of the ovs-bridge, but when we try to remove the ovs bridge and re-set the eth0 interface, we get the following nmstateVerification error:
Version-Release number of selected component (if applicable):
nmstate noarch 1.0.4-0.20211004.1367gitffee942.el8
NetworkManager x86_64 1:1.34.0-0.1.el8
NetworkManager-libnm x86_64 1:1.34.0-0.1.el8
NetworkManager-ovs x86_64 1:1.34.0-0.1.el8
rdo-openvswitch noarch 1:2.15-2.el8
How reproducible:
Randomly in CI but repeatingly. I didn't manage to reproduce manually.
Steps to Reproduce:
1. Apply desired state creating ovs-bridge with ovs-interface having same MAC address as eth0, to move dynamic IP from eth0 to ovs0:
interfaces:
- name: eth0
type: ethernet
state: up
ipv4:
enabled: false
- name: ovs0
type: ovs-interface
state: up
ipv4:
enabled: true
dhcp: true
mac-address: 52:55:00:D1:55:02 # mac address of eth0
- name: br114
type: ovs-bridge
state: up
bridge:
options:
stp: true
port:
- name: eth0
- name: ovs0
2. Remove the previously configured bridge after verifying that ovs0 has the dynamic IP address from eth0:
interfaces:
- name: eth0
type: ethernet
state: up
ipv4:
enabled: true
dhcp: true
- name: ovs0
type: ovs-interface
state: absent
- name: br114
type: ovs-bridge
state: absent
Actual results:
NM_DEVICE_STATE_REASON_DEPENDENCY_FAILED of type NM.DeviceStateReason>
Traceback (most recent call last):
File \"/usr/bin/nmstatectl\", line 11, in <module>
load_entry_point('nmstate==1.0.4', 'console_scripts', 'nmstatectl')()
File \"/usr/lib/python3.6/site-packages/nmstatectl/nmstatectl.py\", line 73, in main
return args.func(args)
File \"/usr/lib/python3.6/site-packages/nmstatectl/nmstatectl.py\", line 326, in set
return apply(args)
File \"/usr/lib/python3.6/site-packages/nmstatectl/nmstatectl.py\", line 354, in apply
args.save_to_disk,
File \"/usr/lib/python3.6/site-packages/nmstatectl/nmstatectl.py\", line 407, in apply_state
save_to_disk=save_to_disk,
File \"/usr/lib/python3.6/site-packages/libnmstate/netapplier.py\", line 81, in apply
_apply_ifaces_state(plugins, net_state, verify_change, save_to_disk)
File \"/usr/lib/python3.6/site-packages/libnmstate/netapplier.py\", line 132, in _apply_ifaces_state
_verify_change(plugins, net_state)
File \"/usr/lib/python3.6/site-packages/libnmstate/netapplier.py\", line 145, in _verify_change
net_state.verify(current_state)
File \"/usr/lib/python3.6/site-packages/libnmstate/net_state.py\", line 86, in verify
self._ifaces.verify(current_state.get(Interface.KEY))
File \"/usr/lib/python3.6/site-packages/libnmstate/ifaces/ifaces.py\", line 658, in verify
cur_iface.state_for_verify(),
libnmstate.error.NmstateVerificationError:
desired
=======
---
name: eth0
type: ethernet
state: up
ipv4:
enabled: true
address: []
auto-dns: true
auto-gateway: true
auto-routes: true
dhcp: true
current
=======
---
name: eth0
type: ethernet
state: up
ipv4:
enabled: true
address:
- ip: 192.168.66.102
prefix-length: 24
ipv6:
enabled: false
lldp:
enabled: false
mac-address: 52:55:00:D1:55:02
mtu: 1500
difference
==========
--- desired
+++ current
@@ -4,8 +4,12 @@
state: up
ipv4:
enabled: true
- address: []
- auto-dns: true
- auto-gateway: true
- auto-routes: true
- dhcp: true
+ address:
+ - ip: 192.168.66.102
+ prefix-length: 24
+ipv6:
+ enabled: false
+lldp:
+ enabled: false
+mac-address: 52:55:00:D1:55:02
+mtu: 1500
Expected results:
Additional info:
A similar bug was file with this same scenario: https://bugzilla.redhat.com/show_bug.cgi?id=2011879
which is about the failing rollback.
Comment 3Fernando F. Mancera
2022-06-25 12:26:47 UTC
Hello Radim, sorry for the late reply. This was reported sometime ago.. I would like to know if this is still happening and if it is happening with the rust implementation. I couldn't reproduce it manually.
In case it is still happening, could you please provide the logs of the failure?
Thank you very much!
Hello Federico,
I don't remember seeing the issue in the ci lately.
I think we can close this for now. I'll reopen the issue with new logs if it happens again.
Thanks!