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 1665172 [details]
edit-error-tar

Description of problem:
Error when trying to disable ipv4 and ipv6:ERROR    NM main-loop aborted: Connection activation failed on device eth1: error=nm-manager-error-quark: Can not find a master for eth1: Master connection not found or invalid (3)


Version-Release number of selected component (if applicable):
[root@localhost ~]# rpm -q NetworkManager
NetworkManager-1.22.8-1.el8.x86_64
[root@localhost ~]# rpm -q nmstate
nmstate-0.2.5-1.el8.noarch


How reproducible:


Steps to Reproduce:
1. create a vm with centos8. add 2 nic eth1 & eth2. make sure they are managed by nmstate via nmcli con like so:
[root@localhost ~]# nmcli con
NAME         UUID                                  TYPE      DEVICE 
System eth0  5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03  ethernet  eth0   
eth1         a2405c78-faa0-4bb7-ab04-f919aea48503  ethernet  eth1   
eth2         9e88e037-343f-4e7a-90ce-4177fa08508d  ethernet  eth2  

2. perform nmstatectl edit and change the ipv4 & ipv6 to false.
3. 

Actual results:
getting an Error (attached)

Expected results:
action successful

Additional info:

Found the issue: ovs-ctl was not started. 
this fixed the issue: sudo /usr/share/openvswitch/scripts/ovs-ctl start

(In reply to Ram Lavi from comment #1)
> Found the issue: ovs-ctl was not started. 
> this fixed the issue: sudo /usr/share/openvswitch/scripts/ovs-ctl start

To be more accurate the cmd that fixed the issue is: systemctl start openvswitch

issue was: openvswitch service was: inactive

*** This bug has been marked as a duplicate of bug 1806249 ***