Bug 1572667

Summary: don't restart openvswitch if --no-activate is specified (OSP-12)
Product: Red Hat OpenStack Reporter: Bob Fournier <bfournie>
Component: os-net-configAssignee: zenghui.shi <zshi>
Status: CLOSED ERRATA QA Contact: Shai Revivo <srevivo>
Severity: high Docs Contact:
Priority: urgent    
Version: 12.0 (Pike)CC: bfournie, hbrock, jamsmith, jslagle, mburns, mlammon, rhel-osp-director-maint, skramaja, srevivo, yroblamo, zshi
Target Milestone: z3Keywords: Regression, Triaged, ZStream
Target Release: 12.0 (Pike)Flags: jamsmith: needinfo? (zshi)
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: os-net-config-7.3.6-1.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1549107 Environment:
Last Closed: 2018-08-20 12:59:48 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:

Comment 5 mlammon 2018-07-18 17:26:03 UTC
Installed latest osp12 puddle: 2018-07-13.1 which will be rhos-osp12z3
Environment:

os-net-config-7.3.6-1.el7ost.noarch

Verified new code is in place. This is about all we can do for the bz.

sed -n '1007,1015p' /usr/lib/python2.7/site-packages/os_net_config/impl_ifcfg.py
            # DPDK initialization is done before running os-net-config, to make
            # the DPDK ports available when enabled. DPDK Hotplug support is
            # supported only in OvS 2.7 version. Until then, OvS needs to be
            # restarted after adding a DPDK port. This change will be removed
            # on migration to OvS 2.7 where DPDK Hotplug support is available.
            if ovs_needs_restart:
                msg = "Restart openvswitch"
                self.execute(msg, '/usr/bin/systemctl',
                             'restart', 'openvswitch')

Comment 7 errata-xmlrpc 2018-08-20 12:59:48 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://access.redhat.com/errata/RHSA-2018:2331