Bug 1806251

Summary: Error when trying to disable ipv4 and ipv6
Product: Red Hat Enterprise Linux 8 Reporter: Ram Lavi <ralavi>
Component: nmstateAssignee: Gris Ge <fge>
Status: CLOSED DUPLICATE QA Contact: Mingyu Shi <mshi>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 8.4CC: ferferna, jiji, jishi, network-qe, till
Target Milestone: rc   
Target Release: 8.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-02-24 21:41:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
edit-error-tar none

Description Ram Lavi 2020-02-23 09:57:18 UTC
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:

Comment 1 Ram Lavi 2020-02-24 08:05:28 UTC
Found the issue: ovs-ctl was not started. 
this fixed the issue: sudo /usr/share/openvswitch/scripts/ovs-ctl start

Comment 2 Ram Lavi 2020-02-24 09:14:39 UTC
(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

Comment 3 Ram Lavi 2020-02-24 09:19:35 UTC
issue was: openvswitch service was: inactive

Comment 4 Till Maas 2020-02-24 21:41:50 UTC

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