Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1444495

Summary:	There is no way to tell Neutron OVS cleanup to skip certain ports (e.g. Octavia health manager ports)
Product:	Red Hat OpenStack	Reporter:	Brent Eagles <beagles>
Component:	openstack-neutron	Assignee:	Nir Magnezi <nmagnezi>
Status:	CLOSED ERRATA	QA Contact:	Alexander Stafeyev <astafeye>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	11.0 (Ocata)	CC:	amuller, astafeye, beagles, chrisw, nyechiel, srevivo
Target Milestone:	async	Keywords:	Triaged, ZStream
Target Release:	11.0 (Ocata)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-neutron-10.0.1-2.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-06-15 16:56:08 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:

Description Brent Eagles 2017-04-21 12:49:34 UTC

Related issue: 
https://bugzilla.redhat.com/show_bug.cgi?id=1444143

Description of problem:

In cases like Octavia we need to create neutron ports on neutron managed bridges that can be restored on boot through node configuration without being removed by neutron-ovs-cleanup.


How reproducible:
100%

Steps to Reproduce:
1. Create an interface definition files that configures a port on the integration bridge (i.e. br-int) 
2. Reboot the host
3. Observe that the port is created when networking is started and then is very quickly removed as neutron-ovs-cleanup runs shortly thereafter.

Actual results:

Ports required for proper operation of services like Octavia are removed.

Expected results:

The ovs cleanup process considers port specific data and omits ports tagged as belonging to a set of services from cleanup.

Comment 1 Assaf Muller 2017-04-28 21:21:43 UTC

*** Bug 1443302 has been marked as a duplicate of this bug. ***

Comment 4 Nir Magnezi 2017-05-18 16:24:33 UTC

Brent,

The fix from neutron's side is done.
I posted a single comment about the TripleO Docs to make sure we leverage this fix when we create the port.

Also for QE Verification, please take this into account:

https://review.openstack.org/#/c/447496/17/doc/source/advanced_deployment/deploy_octavia.rst@221

Comment 7 Alexander Stafeyev 2017-05-28 11:27:18 UTC

(In reply to Nir Magnezi from comment #4)
> Brent,
> 
> The fix from neutron's side is done.
> I posted a single comment about the TripleO Docs to make sure we leverage
> this fix when we create the port.
> 
> Also for QE Verification, please take this into account:
> 
> https://review.openstack.org/#/c/447496/17/doc/source/advanced_deployment/
> deploy_octavia.rst@221

I can not verify this one until the post deployment patch is merged =\

Comment 9 errata-xmlrpc 2017-06-15 16:56:08 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-2017:1474