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

Bug 1244894

Summary:	CLI does not validate if --neutron-tunnel-types matches --neutron-network-type
Product:	Red Hat OpenStack	Reporter:	Dan Sneddon <dsneddon>
Component:	rhosp-director	Assignee:	chris alfonso <calfonso>
Status:	CLOSED DUPLICATE	QA Contact:	yeylon <yeylon>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0 (Kilo)	CC:	hbrock, mburns, rhel-osp-director-maint, srevivo
Target Milestone:	---
Target Release:	Director
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-07-20 17:40:22 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 Dan Sneddon 2015-07-20 17:32:10 UTC

Description of problem:
If you deploy the overcloud with --neutron-tunnel-types vxlan, but you don't specify the --neutron-network-type, then you end up with an unusable network configuration on the overcloud. All of the OVS agents are configured for VXLAN, but the Neutron networks are GRE, so nothing can communicate.

Version-Release number of selected component (if applicable):
puddle-2015-07-17.2

How reproducible:
100%

Steps to Reproduce:
1. Deploy with --neutron-tunnel-types vxlan but do not specify the --neutron-network-type
2.
3.

Actual results:
Neutron networks are configured as GRE, but the OVS agents are configured for VXLAN tunneling.

Expected results:
The CLI should throw an error if the --neutron-network-type does not match at least one of the --neutron-tunnel-types.

Additional info:

Comment 3 Mike Burns 2015-07-20 17:40:22 UTC


*** This bug has been marked as a duplicate of bug 1244893 ***