Bug 1572238
| Summary: | When restart openvswitch, ovn-controller is not reprogramming the flows. | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Daniel Alvarez Sanchez <dalvarez> |
| Component: | openstack-tripleo-heat-templates | Assignee: | Daniel Alvarez Sanchez <dalvarez> |
| Status: | CLOSED ERRATA | QA Contact: | Eran Kuris <ekuris> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 13.0 (Queens) | CC: | aconole, amuller, apevec, chrisw, dalvarez, ekuris, knylande, lhh, majopela, mburns, nusiddiq, nyechiel, oblaut, rhos-maint, samccann, srevivo |
| Target Milestone: | beta | Keywords: | Triaged |
| Target Release: | 13.0 (Queens) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-tripleo-heat-templates-8.0.3-0.20180424184718.2bc778b.el7.centos | Doc Type: | Bug Fix |
| Doc Text: |
The openvswitch systemd script deletes the /run/openvswitch folder when stopping it in the host.
The /run/openvswitch path inside the ovn-controller container becomes a stale directory. When the service is started again, it recreates the folder. In order for ovn-controller to access this folder again, the folder has to be remounted or the ovn-controller container restarted.
|
Story Points: | --- |
| Clone Of: | 1566412 | Environment: | |
| Last Closed: | 2018-06-27 13:53: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: | |||
|
Comment 5
Daniel Alvarez Sanchez
2018-04-26 14:07:16 UTC
fix verified on rpm -qa| grep openstack-tripleo-heat-templates-8 openstack-tripleo-heat-templates-8.0.2-4.el7ost.noarch cat /etc/yum.repos.d/latest-installed 13 -p 2018-04-26.3 verified on controller & compute nodes 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/RHEA-2018:2086 |