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

Bug 1582180

Summary:	Unclear error message when creating an external network of the wrong type (like non-flat in a virt environment)
Product:	Red Hat OpenStack	Reporter:	Udi Kalifon <ukalifon>
Component:	openstack-neutron	Assignee:	Assaf Muller <amuller>
Status:	CLOSED DUPLICATE	QA Contact:	Toni Freger <tfreger>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	13.0 (Queens)	CC:	amuller, bhaley, chrisw, nyechiel, srevivo, ukalifon
Target Milestone:	---
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:	2018-05-30 14:58:46 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 Udi Kalifon 2018-05-24 12:46:26 UTC

Description of problem:
I tried to run this command:
openstack network create --provider-network-type vlan  --provider-segment 10 --external --provider-physical-network datacentre nova

The error only says "Bad Request":
Error while executing command: Bad Request (HTTP 400) (Request-ID: req-3dcad903-149e-4252-b8db-f85c1ec77369)

In the neutron logs the error is: "The server could not comply with the request since it is either malformed or otherwise incorrect"


Version-Release number of selected component (if applicable):
openstack-neutron-11.0.2-1.el7ost.noarch


How reproducible:
100%


Steps to Reproduce:
1. Try to create a "vlan" network in a virutal environment, where the external network should be flat...


Actual results:
Unclear error message.


Expected results:
A more specific message, about what exactly failed so we can guess that the vlan doesn't exist...

Comment 1 Assaf Muller 2018-05-24 13:02:51 UTC

Can you please attach an sosreport? Or minimally neutron-server log.

Comment 5 Brian Haley 2018-05-30 14:57:56 UTC

This is a duplicate of 1570786 even though it is a different command.  There are now three separate issues being tracked upstream and I'm working with someone more familiar with OSC to help track them down since they are all related.

Comment 6 Brian Haley 2018-05-30 14:58:46 UTC


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