Bug 1340717
Summary: | Backport to liberty: set of no-downtime patches for ovs neutron agent | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Hynek Mlnarik <hmlnarik> |
Component: | openstack-neutron | Assignee: | Hynek Mlnarik <hmlnarik> |
Status: | CLOSED ERRATA | QA Contact: | Toni Freger <tfreger> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 8.0 (Liberty) | CC: | adahms, amuller, chrisw, dcadzow, ealcaniz, jmelvin, nyechiel, ragiman, srevivo |
Target Milestone: | async | Keywords: | FeatureBackport, ZStream |
Target Release: | 8.0 (Liberty) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-neutron-7.0.4-7.el7ost | Doc Type: | Enhancement |
Doc Text: |
This update removes unnecessary downtime caused by updating OvS switch reconfiguration when restarting the OvS agent. Previously, dropping flows on physical bridges caused networking to drop. The same issue was experienced when the patch port between br-int and br-tun was deleted and rebuilt during startup. This enhancement resolves these issues, making it possible to restart the OvS agent without unnecessarily disrupting network traffic. This results in no downtime when restarting the OvS neutron agent if the bridge is already set up and reconfiguration was not requested.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-06-29 13:59:46 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: | 1341958 | ||
Bug Blocks: |
Description
Hynek Mlnarik
2016-05-30 07:20:59 UTC
*** Bug 1343106 has been marked as a duplicate of this bug. *** The code tested in latest OSP8 - openstack-neutron-7.0.4-7.el7ost.noarch 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/RHBA-2016:1353 |