Bug 1373592 - IPv6 Not Implemented for Management Network in OSP 9 GA
Summary: IPv6 Not Implemented for Management Network in OSP 9 GA
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 9.0 (Mitaka)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 10.0 (Newton)
Assignee: Angus Thomas
QA Contact: Omri Hochman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-06 16:37 UTC by Dan Sneddon
Modified: 2016-10-14 17:05 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-14 17:05:47 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Dan Sneddon 2016-09-06 16:37:29 UTC 
Description of problem:
The Management network in OSP 9 does not include an IPv6-capable version of the management.yaml template in openstack-tripleo-heat-templates/network

Version-Release number of selected component (if applicable):
OSP 9 GA

How reproducible:
100%

Steps to Reproduce:
1. Configure Overcloud networking prior to deployment


Actual results:
There is no management_v6.yaml in the network/ directory inside the TripleO Heat Templates.

Expected results:
The management network should be able to be configured as IPv6 just like the other non-provisioning networks.

Additional info:
The IPv6 version of the Management network was included in this upstream patch, but the upstream patch wasn't merged to downstream in time for OSP 9 GA. We may wish to release these changes as a bugfix at some point.

https://review.openstack.org/#/c/318389/
Comment 2 Dan Sneddon 2016-10-14 17:05:47 UTC 
This was an oversight in OSP 9, but it is a very easy customization to copy either the OSP-Director 10 version of management_v6.yaml, or to create one based on the management.yaml and the other *_v6.yaml templates. This is fixed in OSP-Director 10.
Note You need to log in before you can comment on or make changes to this bug.