Bug 1397050

Summary: [fdProd] OvS rtnetlink race condition
Product: Red Hat Enterprise Linux 7 Reporter: Flavio Leitner <fleitner>
Component: openvswitchAssignee: Flavio Leitner <fleitner>
Status: CLOSED ERRATA QA Contact: qding
Severity: urgent Docs Contact:
Priority: urgent    
Version: 7.2CC: aconole, aloughla, atragler, cascardo, danken, edwardh, fleitner, kzhang, network-qe, phoracek, qding, wchadwic, ylavi
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openvswitch-2.5.0-19.git20160727.el7fdp Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1346232 Environment:
Last Closed: 2017-01-05 20:48:40 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:
Bug Depends On: 1346232    
Bug Blocks: 1353185, 1362393, 1377912    

Comment 4 qding 2016-11-30 01:53:17 UTC
Verified with kernel-3.10.0-514.el7.x86_64 and openvswitch-2.5.0-22.git20160727.el7fdp.x86_64 and steps in https://bugzilla.redhat.com/show_bug.cgi?id=1346232#c27
And beaker jobs:
https://beaker.engineering.redhat.com/jobs/1611867
https://beaker.engineering.redhat.com/jobs/1611575
https://beaker.engineering.redhat.com/jobs/1611574
https://beaker.engineering.redhat.com/jobs/1611573
https://beaker.engineering.redhat.com/jobs/1611572

[root@dell-per730-04 ~]# vdsm-tool configure --force

Checking configuration status...

multipath requires configuration
libvirt is not configured for vdsm yet
FAILED: conflicting vdsm and libvirt-qemu tls configuration.
vdsm.conf with ssl=True requires the following changes:
libvirtd.conf: listen_tcp=0, auth_tcp="sasl", listen_tls=1
qemu.conf: spice_tls=1.

Running configure...
Reconfiguration of certificates is done.
Reconfiguration of sebool is done.
Reconfiguration of multipath is done.
Reconfiguration of passwd is done.
Reconfiguration of sanlock is done.
Reconfiguration of libvirt is done.

Done configuring modules to VDSM.
[root@dell-per730-04 ~]# systemctl start vdsmd
[root@dell-per730-04 ~]# python
Python 2.7.5 (default, Aug  2 2016, 04:20:16) 
[GCC 4.8.5 20150623 (Red Hat 4.8.5-4)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from vdsm import vdscli
>>> c = vdscli.connect()
>>> c.setupNetworks({'test-network': {}}, {}, {'connectivityCheck': False})
{'status': {'message': 'Done', 'code': 0}}
>>> c.setupNetworks({'test-network': {'remove': True}}, {}, {'connectivityCheck': False})
{'status': {'message': 'Done', 'code': 0}}
>>> 
[root@dell-per730-04 ~]# ovs-vsctl add-br br1 -- add-port br1 test-network -- set Interface test-network type=internal
[root@dell-per730-04 ~]# dmesg | tail
[  810.286467] SELinux:  8 users, 14 roles, 4992 types, 301 bools, 1 sens, 1024 cats
[  810.286469] SELinux:  91 classes, 105180 rules
[  817.134661] device-mapper: multipath: version 1.11.0 loaded
[  817.191318] Loading iSCSI transport class v2.0-870.
[  817.206688] device-mapper: multipath service-time: version 0.3.0 loaded
[  817.214377] device-mapper: table: 253:3: multipath: error getting device
[  817.221863] device-mapper: ioctl: error adding target to table
[  861.750054] IPv6: ADDRCONF(NETDEV_CHANGE): test-network: link becomes ready
[  874.433995] device test-network entered promiscuous mode
[  874.443052] device br1 entered promiscuous mode
[root@dell-per730-04 ~]# ovs-vsctl show
a84051fd-82ad-4196-ad98-99c35fe7201f
    Bridge "ovsbr0"
        Port "ovsbr0"
            Interface "ovsbr0"
                type: internal
    Bridge "br1"
        Port test-network
            Interface test-network
                type: internal
        Port "br1"
            Interface "br1"
                type: internal
    ovs_version: "2.5.0"
[root@dell-per730-04 ~]# uname -r
3.10.0-514.el7.x86_64
[root@dell-per730-04 ~]# 
[root@dell-per730-04 ~]# rpm -q openvswitch
openvswitch-2.5.0-22.git20160727.el7fdp.x86_64

Comment 6 errata-xmlrpc 2017-01-05 20:48:40 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2017-0027.html