Bug 1578793

Summary:	Neutron baremetal->container upgrades leave baremetal processes
Product:	Red Hat OpenStack	Reporter:	Brent Eagles <beagles>
Component:	openstack-tripleo-heat-templates	Assignee:	Brent Eagles <beagles>
Status:	CLOSED WONTFIX	QA Contact:	Gurenko Alex <agurenko>
Severity:	high	Docs Contact:
Priority:	high
Version:	13.0 (Queens)	CC:	amuller, bcafarel, bhaley, mburns
Target Milestone:	z2	Keywords:	Triaged, ZStream
Target Release:	13.0 (Queens)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-01-13 15:24:06 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:	1563443
Bug Blocks:

Description Brent Eagles 2018-05-16 11:59:32 UTC

When upgrading to OSP 13 from previous versions, supporting processes for neutron agents like dnsmasq, haproxy, keepalived, etc. created prior to upgrade continue to run on baremetal until the node is rebooted. New processes instantiated for new neutron objects (e.g. routers, networks, etc) will run in containers resulting in a mix of both. This has potential implications with respect to support and troubleshooting.

Comment 1 Nir Yechiel 2018-05-17 12:55:42 UTC

To clarify: this should not impact the upgrade itself from a user point of view. As indicated in comment #0, the real impact is on the operator only.

Comment 4 Bernard Cafarelli 2020-01-13 15:24:06 UTC

This was an initial potential issue when switching to containerized neutron, but since then all upgrades went smoothly and neutron can shut down baremetal process and then start sidecar container ones (we base process control on PID). So we can close this one now (almost 3 releases after switching to containerized Neutron)