`bridge_name` is still present in templates during and post FFU causing further updates failure

Solution Verified - Updated -

Issue

  • bridge_name is no longer a valid variable
  • Presence of bridge_name leads to further updates failure
  • If stack update is ran post FFU with NetworkDeploymentActions it will cause an outage leading to creation of new ovs-bridge named bridge_name and disrupting the VM FIP connectivity

Environment

  • Red Hat OpenStack 17.1 [post FFU]

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content