Bug 1591067

Summary: neutron-ovs-cleanup service is not enabled in controller and compute nodes using Director in RHOSP13beta
Product: Red Hat OpenStack Reporter: Keigo Noha <knoha>
Component: openstack-tripleo-heat-templatesAssignee: Brent Eagles <beagles>
Status: CLOSED ERRATA QA Contact: Toni Freger <tfreger>
Severity: medium Docs Contact:
Priority: urgent    
Version: 13.0 (Queens)CC: amuller, bcafarel, beagles, chrisw, dalvarez, jschluet, jthomas, majopela, mburns, mowens, mvalsecc, nalmond, nyechiel, ragiman, srevivo
Target Milestone: z3Keywords: Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-8.0.7-2.el7ost Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1874741 (view as bug list) Environment:
Last Closed: 2018-11-13 22:26:39 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:    
Bug Blocks: 1874741    
Attachments:
Description Flags
scripts, ansible playbook and service file to install cleanup service none

Description Keigo Noha 2018-06-14 01:18:01 UTC
Description of problem:
neutron-ovs-cleanup service is not enabled in comupte and controller using Director in RHOSP13beta.
Until RHOSP12, neutron-ovs-cleanup service is enabled in systemd.
But, in RHOSP13 beta, neutron-ovs-cleanup service is not enabled. 

Version-Release number of selected component (if applicable):
RHOSP13beta

How reproducible:
When overcloud is deployed with director. 

Actual results:
neutron-ovs-cleanup service is not enabled in controller and compute nodes.

Expected results:
neutron-ovs-cleanup service should be enabled.

Comment 4 Brent Eagles 2018-06-28 16:17:54 UTC
Considering https://bugzilla.redhat.com/show_bug.cgi?id=1595733 - there is a potential problem in that the OVS, L3, and DHCP agents will still likely be running if we simply reactivate the cleanup services. In short, I think we need to fix 1595733 first (and possibly roll up running the cleanups as part of that fix since the service packages will no longer be installed on the baremetal in later releases).

Comment 5 Brent Eagles 2018-07-04 12:50:09 UTC
The fix to https://bugs.launchpad.net/tripleo/+bug/1778913 will introduce graceful shutdown for services that are running in containers. For a cleanup to work well, it should be run after this service completes and not before (ports, namespaces, etc, will otherwise be deleted "out from under" the running agents). In short, the fix to https://bugs.launchpad.net/tripleo/+bug/1778913 should be merged to 13 before we add cleanup processes to shutdown.

Comment 15 Miguel Angel Ajo 2018-08-14 12:56:00 UTC
As a workaround, when shutting down or rebooting a node they should follow the next procedure:


ovs-vsctl del-br br-int
ovs-vsctl del-br br-tun
shutdown # or reboot


On OSP13z3 we will have this automated.

Comment 16 Daniel Alvarez Sanchez 2018-08-14 12:58:24 UTC
After talking about it with Brent we feel that prior to applying Miguel steps, neutron agents should be stopped first.

Comment 17 Keigo Noha 2018-08-16 05:29:43 UTC
Hello Brent,

Thank you for your work on the upstream.
Could you merge the fix into RHOSP13?
I understand that you're working on upstream's stable/queens branch.
This issue will have an impact to all RHOSP13 users.
We should fix this at RHOSP13z2.

Best Regards,
Keigo Noha

Comment 25 Brent Eagles 2018-08-28 12:20:31 UTC
Created attachment 1479233 [details]
scripts, ansible playbook and service file to install cleanup service

Comment 26 Keigo Noha 2018-10-09 01:32:12 UTC
Hello Brent,

Thank you for your work on this bugzilla.
Do we have any updates for this bugzilla? Do we ship the fix at RHOSP13z3?

Best Regards,
Keigo Noha

Comment 37 errata-xmlrpc 2018-11-13 22:26:39 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/RHBA-2018:3587