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.
Bug 1966478 - cannot apply current state when interfaces are attached to ovs
Summary: cannot apply current state when interfaces are attached to ovs
Keywords:
Status: CLOSED DUPLICATE of bug 2005240
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: nmstate
Version: 8.5
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: beta
: ---
Assignee: Gris Ge
QA Contact: Mingyu Shi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-01 09:06 UTC by Mingyu Shi
Modified: 2023-03-30 08:07 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-20 09:15:00 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
reproducer.sh (2.67 KB, text/plain)
2021-06-01 09:06 UTC, Mingyu Shi 		no flags Details
error in nmstate.log (168.27 KB, text/plain)
2021-06-01 09:07 UTC, Mingyu Shi 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker NMT-449 0 None None None 2023-03-30 08:07:51 UTC

Description Mingyu Shi 2021-06-01 09:06:16 UTC 
Created attachment 1788443 [details]
reproducer.sh

Description of problem:
Cannot apply current state when interfaces are attached to ovs

Version-Release number of selected component (if applicable):
nmstate-1.1.0-0.1.el8.noarch
nispor-1.1.0-1.el8.x86_64
NetworkManager-1.32.0-0.4.el8.x86_64
Linux dell-per740-79.rhts.eng.pek2.redhat.com 4.18.0-305.7.el8.kpq1.x86_64 #1 SMP Mon May 17 13:36:02 EDT 2021 x86_64 x86_64 x86_64 GNU/Linux
openvswitch2.13-2.13.0-105.el8fdp.x86_64
nmstate-plugin-ovsdb-1.1.0-0.1.el8.noarch

How reproducible:
Nearly 100%, only 1 success during my test

Steps to Reproduce:
Run the reproducer in the attachment

Actual results:
Failed

Expected results:
No failure

Additional info:
According to my test so far, to reproduce we need:
1. Many interfaces
2. Some interfaces are attached to ovs
Comment 1 Mingyu Shi 2021-06-01 09:07:46 UTC 
Created attachment 1788444 [details]
error in nmstate.log
Comment 2 Fernando F. Mancera 2021-06-08 23:16:29 UTC 
Hi Mingyu, I am using all the components that you described and I am not able to reproduce this.

These were my steps:

1. Apply the state that you attached (nmstatectl apply ovs+dummy.yaml)
2. Run the following command: nmstatectl show | nmstatectl apply
3. Run this in a loop.

Am I missing any step? Thank you!
Comment 4 Mingyu Shi 2021-06-22 12:41:22 UTC 
Hi Fernando

I reproduced it for about 6 of 10 times, with nmstate-1.1.0-0.3.alpha3.el8.noarch, please check the NM_trace.log
The timeline:
20:28:45 nmstatectl set ovs+dummy.yaml
20:32:22 nmstatectl show g0dum* > current.yaml
20:32:28 nmstatectl set current.yaml
2021-06-22 20:32:29,495 root         ERROR    Rollback failed with error Activate profile uuid:ff3f9871-b12e-42c3-97ea-1b1d86dea3cd iface:g0dummy31 type: dummy failed: reason=<enum NM_ACTIVE_CONNECTION_STATE_REASON_UNKNOWN of type NM.ActiveConnectionStateReason><enum NM_DEVICE_STATE_REASON_REMOVED of type NM.DeviceStateReason>
Traceback (most recent call last):
  File "/usr/bin/nmstatectl", line 11, in <module>
    load_entry_point('nmstate==1.1.0', '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 343, 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 114, in _apply_ifaces_state
    plugin.apply_changes(net_state, save_to_disk)
  File "/usr/lib/python3.6/site-packages/libnmstate/nm/plugin.py", line 201, in apply_changes
    NmProfiles(self.context).apply_config(net_state, save_to_disk)
  File "/usr/lib/python3.6/site-packages/libnmstate/nm/profiles.py", line 95, in apply_config
    self._ctx.wait_all_finish()
  File "/usr/lib/python3.6/site-packages/libnmstate/nm/context.py", line 213, in wait_all_finish
    raise tmp_error
libnmstate.error.NmstateLibnmError: Activate profile uuid:d7339e0f-5359-4159-8b3e-e79f82237004 iface:g0dummy30 type: dummy failed: reason=<enum NM_ACTIVE_CONNECTION_STATE_REASON_UNKNOWN of type NM.ActiveConnectionStateReason><enum NM_DEVICE_STATE_REASON_REMOVED of type NM.DeviceStateReason>
Comment 5 Gris Ge 2022-07-20 09:15:00 UTC 
This is fixed by bug 2005240

*** This bug has been marked as a duplicate of bug 2005240 ***
Note You need to log in before you can comment on or make changes to this bug.