Align juno's gate-check/bootstrapping more closely to kilo/master

Bug #1480390 reported by Jesse Pretorius
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Invalid
Medium
Jesse Pretorius
Juno
Won't Fix
Medium
Jesse Pretorius
Trunk
Invalid
Medium
Jesse Pretorius

Bug Description

When testing upgrades or building juno AIO's for testing, the workflow is very different to kilo/master. This is confusing and causes much frustration. Also, upgrades fail due to the juno AIO bootstrapping setting the external_vip_address to 192.168.1.1 which causes haproxy to fail when trying to bind to that address.

Changed in openstack-ansible:
milestone: none → 10.1.12
status: New → Confirmed
Revision history for this message
Jesse Pretorius (jesse-pretorius) wrote :

Setting Juno series target to "Won't Fix" as there will be no more adjustments going into the Juno branch unless they are Critical bugs.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.