Bug 1582180 - Unclear error message when creating an external network of the wrong type (like non-flat in a virt environment)
Summary: Unclear error message when creating an external network of the wrong type (li...
Keywords:
Status: CLOSED DUPLICATE of bug 1570786
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Assaf Muller
QA Contact: Toni Freger
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-24 12:46 UTC by Udi Kalifon
Modified: 2018-05-30 14:58 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-30 14:58:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.