Reviewed: https://review.openstack.org/339253
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=4caabaf864f9bec62c4a78c7e9c4dc31ea5ef063
Submitter: Jenkins
Branch: master
commit 4caabaf864f9bec62c4a78c7e9c4dc31ea5ef063
Author: Sivasathurappan Radhakrishnan <siva.radhakrish...@intel.com>
Date: Thu Jul 7 21:58:32 2016 +0000
Provide more duplicate VLAN network error info
When user tries to create a network which VLAN ID is already
used by another network, Network object will throw a DuplicateVlan
exception. However, when the exception get propagate to the API level,
it is only treated as a regular exception. This fix is to treat Duplicate
Vlan exception as a special exception (similar to DuplicateCidr) so that
users know more about what kind of duplicated setting they configured.
Change-Id: Ib2f7bc90957d4ae5647adbbda05a87195549374d
Closes-Bug: #1420112
Co-Authored-By: kahou Lei<kaho...@gmail.com>
** Changed in: nova
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1420112
Title:
Nova doesn't show enough error message when creating a new network
with a duplicate vlan ID.
Status in OpenStack Compute (nova):
Fix Released
Bug description:
This happens when user tries to create a new network with a duplicate
vlan ID:
vagrant@ubuntu:~/devstack$ nova network-list
+--------------------------------------+---------+-------------+
| ID | Label | Cidr |
+--------------------------------------+---------+-------------+
| a16f1896-da4c-4978-9776-0b6368129b07 | private | 10.0.0.0/24 |
+--------------------------------------+---------+-------------+
vagrant@ubuntu:~/devstack$ nova network-show
a16f1896-da4c-4978-9776-0b6368129b07
+---------------------+--------------------------------------+
| Property | Value
+---------------------+--------------------------------------+
| bridge | br100
| bridge_interface | eth1
| broadcast | 10.0.0.255
| cidr | 10.0.0.0/24
| cidr_v6 | -
| created_at | 2015-02-10T05:52:41.000000
| deleted | False
| deleted_at | -
| dhcp_server | 10.0.0.1
| dhcp_start | 10.0.0.3
| dns1 | 8.8.4.4
| dns2 | -
| enable_dhcp | True
| gateway | 10.0.0.1
| gateway_v6 | -
| host | -
| id | a16f1896-da4c-4978-9776-0b6368129b07
| injected | False
| label | private
| mtu | -
| multi_host | False
| netmask | 255.255.255.0
| netmask_v6 | -
| priority | -
| project_id | -
| rxtx_base | -
| share_address | False
| updated_at | -
| vlan | 100
| vpn_private_address | 10.0.0.2
| vpn_public_address | -
| vpn_public_port | 1000
+---------------------+--------------------------------------+
vagrant@ubuntu:~/devstack$ nova network-create --fixed-range-v4 20.0.0.0/24
--vlan 100 vlan100
ERROR (Conflict): There was a conflict when trying to complete your request.
(HTTP 409) (Request-ID: req-634ac773-3fc7-4013-a319-69fbd4f1cca3)
Contrary to other conflict such as subnet conflict, nova returns a
clearer error message.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1420112/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
