Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1448464

Summary:	Overcloud deployment doesn't respect the CIDR provided on InternalApiNetCidr and others
Product:	Red Hat OpenStack	Reporter:	Eduard Barrera <ebarrera>
Component:	openstack-tripleo-common	Assignee:	Toure Dunnon <tdunnon>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Udi Kalifon <ukalifon>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	10.0 (Newton)	CC:	beth.white, ebarrera, jjoyce, jrist, jschluet, jslagle, jtomasek, mburns, slinaber, tvignaud
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-07-10 15:00:40 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 Eduard Barrera 2017-05-05 13:14:02 UTC

Description of problem:

Overcloud deployed through Tripleo UI is not configuring correctly the netmask provided on InternalApiNetCidr and the other CIDR, if we provide a cidr 26 it will configure cidr 24

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

How reproducible:
always

Steps to Reproduce:
1. Use the UI for a deployment
2. provide a cidr 26 on all the apis
3.

Actual results:
Interface configured with a cidr 24, make the deployment fail on some circumstances

Expected results:
cidr configured properly

Comment 4 Jiri Tomasek 2017-05-05 15:59:23 UTC

Thanks for broader info. I think it clears the problem a lot. In OSP10 (newton) UI does not provide entire list of all the parameters. The workaround for this is setting the parameters by modifying environment files directly and then updating deployment plan with those files. (Just like using CLI) This is especially relevant to network configuration.

In newton release we introduced a feature which allows to configure environment parameters directly via UI. e.g. user enables network-isolation and then he is able to see a list of all parameters related to network isolation environment file.

This is IMHO different problem than https://bugs.launchpad.net/tripleo/+bug/1688053 reports

Comment 5 Jiri Tomasek 2017-05-05 16:17:44 UTC

(In reply to Jiri Tomasek from comment #4)
> Thanks for broader info. I think it clears the problem a lot. In OSP10
> (newton) UI does not provide entire list of all the parameters. The
> workaround for this is setting the parameters by modifying environment files
> directly and then updating deployment plan with those files. (Just like
> using CLI) This is especially relevant to network configuration.
> 
> In newton release we introduced a feature which allows to configure

In _Ocata_ ... (sorry for confusion)

> environment parameters directly via UI. e.g. user enables network-isolation
> and then he is able to see a list of all parameters related to network
> isolation environment file.
> 
> This is IMHO different problem than
> https://bugs.launchpad.net/tripleo/+bug/1688053 reports

Comment 6 Udi Kalifon 2017-07-06 08:22:29 UTC

I deployed using OSP11 with network isolation. I omitted some of the CIDRs from the templates and provided them via the GUI and they were configured properly. This was not possible in OSP10 but we now have a new feature that exposes additional parameters in the plan configuration dialog, when the user adds in an environmental file like "network isolation" for example.

Would you be OK with closing this bug?

Comment 7 Eduard Barrera 2017-07-10 13:02:09 UTC

Thanks Udi, it should be fine!

Thank you very much!