Bug 1584242

Summary: Upgrading DVR compute nodes to containers may end up missing parameters
Product: Red Hat OpenStack Reporter: Brent Eagles <beagles>
Component: openstack-tripleo-heat-templatesAssignee: Brent Eagles <beagles>
Status: CLOSED CURRENTRELEASE QA Contact: Federico Ressi <fressi>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 13.0 (Queens)CC: amuller, beagles, jschluet, lmarsh, mburns, sclewis
Target Milestone: z3Keywords: TestOnly, Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-8.0.2-39.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-16 10:36:23 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 2018-05-30 14:29:48 UTC 
The default environment files for OSP 13 currently expect the ComputeDVR role to be used for configuring DVR. This will cause issues when upgrading existing DVR deployments that will be using the Compute role instead. When using the default templates and provided environment files, the following occurs:

- the L3 agent mode is not set to DVR on the compute node's L3 agent
- a physical interface is not added to the bridge being used for floating IP traffic*

* Most deployments will likely be using custom networking templates.
Comment 1 Jon Schlueter 2018-06-28 19:35:51 UTC 
According to our records, this should be resolved by openstack-tripleo-heat-templates-8.0.2-38.el7ost.  This build is available now.
Comment 14 Federico Ressi 2018-10-15 14:49:48 UTC 
After upgrading from version 12 to version 13 the l3 agent container looked healthy while I never saw VM stopping replying to my pings via the floating IP I set up before starting upgrade operation. Therefore this bug has been fixed and verified.