Quickstart uses incorrect addresses for Ocata and previous branches

Bug #1684288 reported by Dan Sneddon
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
Medium
Unassigned

Bug Description

When using quickstart to deploy an Ocata undercloud, the br-ctlplane gets created with the 192.168.24.x addresses instead of the former default of 192.0.2.x (the default was changed in Pike). This has the result that the default network templates in Ocata do not work for deployments, so customization of the network environment is required.

Is this intentional? If so, this should be documented. If not, the scripts should probably be modified to use the prior addresses.

Tags: quickstart
Revision history for this message
Dan Sneddon (dsneddon) wrote :

Note this only applies to network-isolation deployments. Without network isolation, there aren't any static routes and everything is learned through DHCP.

affects: tripleo-quickstart → tripleo
Changed in tripleo:
status: New → Triaged
importance: Undecided → Medium
milestone: none → pike-2
tags: added: quickstart
Changed in tripleo:
milestone: pike-2 → pike-3
Changed in tripleo:
milestone: pike-3 → pike-rc1
Changed in tripleo:
milestone: pike-rc1 → queens-1
Changed in tripleo:
milestone: queens-1 → queens-2
Changed in tripleo:
milestone: queens-2 → queens-3
Changed in tripleo:
milestone: queens-3 → queens-rc1
Changed in tripleo:
milestone: queens-rc1 → rocky-1
Changed in tripleo:
milestone: rocky-1 → rocky-2
Changed in tripleo:
milestone: rocky-2 → rocky-3
Revision history for this message
Dan Sneddon (dsneddon) wrote :

This bug is no longer relevant. All of the built-in templates have been refactored to use the 192.168.24.x network by default.

Changed in tripleo:
status: Triaged → Fix Released
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.