yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #09012
[Bug 1272896] Re: interface-attach without net-id fails even though ports are created
** Attachment added: "Topology print-screen"
https://bugs.launchpad.net/nova/+bug/1272896/+attachment/3957537/+files/Screenshot%20from%202014-01-26%2014%3A45%3A07.png
** Description changed:
command 'nova interface-attach <sever>' return error message, but ports
are being created and the VM is attached to all networks in tenant,
including a new port on the network it was already attached to.
How to reproduce:
1. create a VM
2. create at least one more network in tenant
3. $ nova interface-attach <serv>
Expected results
ERROR: Failed to attach interface (HTTP 500)
+
No new ports should be created.
or
attach VM to all networks THAT AREN'T ALREADY ATTACHED TO IT
-
-
Actual results
ERROR: Failed to attach interface (HTTP 500)
and, VM is attached to all tenant network, including new interfaces on the networks ALREADY ATTACHED TO IT (suitable ports are created)
-
$ neutron port-list --device_id ced4fa60-4727-4330-80cb-85e08d93ebb1 -c network_id -c device_id -c fixed_ips
+--------------------------------------+---------------------------------------------------------------------------------+--------------------------------------+
| network_id | fixed_ips | device_id |
+--------------------------------------+---------------------------------------------------------------------------------+--------------------------------------+
| 63e1fe60-d3df-4fdf-8b3c-652186da9ef4 | {...: "10.0.0.2"} | ced4fa60-4727-4330-80cb-85e08d93ebb1 |
| de940b25-daf5-455b-b8b6-5d190cefb425 | {..."10.0.0.2"} | ced4fa60-4727-4330-80cb-85e08d93ebb1 |
| 63e1fe60-d3df-4fdf-8b3c-652186da9ef4 | {"..: "10.0.0.4"} | ced4fa60-4727-4330-80cb-85e08d93ebb1 |
| d5dcef55-594f-4670-963d-9e56a1eedb7b | {..: "10.0.0.3"} | ced4fa60-4727-4330-80cb-85e08d93ebb1 |
+--------------------------------------+---------------------------------------------------------------------------------+--------------------------------------+
+
+
+ $ nova list
+ +--------------------------------------+------+--------+------------+-------------+----------------------------------------------------------+
+ | ID | Name | Status | Task State | Power State | Networks |
+ +--------------------------------------+------+--------+------------+-------------+----------------------------------------------------------+
+ | ced4fa60-4727-4330-80cb-85e08d93ebb1 | serv | ACTIVE | None | Running | net1=10.0.0.2, 10.0.0.4; private=10.0.0.3; net2=10.0.0.2 |
+ +--------------------------------------+------+--------+------------+-------------+----------------------------------------------------------+
** Also affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1272896
Title:
interface-attach without net-id fails even though ports are created
Status in OpenStack Neutron (virtual network service):
New
Status in OpenStack Compute (Nova):
New
Bug description:
command 'nova interface-attach <sever>' return error message, but
ports are being created and the VM is attached to all networks in
tenant, including a new port on the network it was already attached
to.
How to reproduce:
1. create a VM
2. create at least one more network in tenant
3. $ nova interface-attach <serv>
Expected results
ERROR: Failed to attach interface (HTTP 500)
+
No new ports should be created.
or
attach VM to all networks THAT AREN'T ALREADY ATTACHED TO IT
Actual results
ERROR: Failed to attach interface (HTTP 500)
and, VM is attached to all tenant network, including new interfaces on the networks ALREADY ATTACHED TO IT (suitable ports are created)
$ neutron port-list --device_id ced4fa60-4727-4330-80cb-85e08d93ebb1 -c network_id -c device_id -c fixed_ips
+--------------------------------------+---------------------------------------------------------------------------------+--------------------------------------+
| network_id | fixed_ips | device_id |
+--------------------------------------+---------------------------------------------------------------------------------+--------------------------------------+
| 63e1fe60-d3df-4fdf-8b3c-652186da9ef4 | {...: "10.0.0.2"} | ced4fa60-4727-4330-80cb-85e08d93ebb1 |
| de940b25-daf5-455b-b8b6-5d190cefb425 | {..."10.0.0.2"} | ced4fa60-4727-4330-80cb-85e08d93ebb1 |
| 63e1fe60-d3df-4fdf-8b3c-652186da9ef4 | {"..: "10.0.0.4"} | ced4fa60-4727-4330-80cb-85e08d93ebb1 |
| d5dcef55-594f-4670-963d-9e56a1eedb7b | {..: "10.0.0.3"} | ced4fa60-4727-4330-80cb-85e08d93ebb1 |
+--------------------------------------+---------------------------------------------------------------------------------+--------------------------------------+
$ nova list
+--------------------------------------+------+--------+------------+-------------+----------------------------------------------------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+------+--------+------------+-------------+----------------------------------------------------------+
| ced4fa60-4727-4330-80cb-85e08d93ebb1 | serv | ACTIVE | None | Running | net1=10.0.0.2, 10.0.0.4; private=10.0.0.3; net2=10.0.0.2 |
+--------------------------------------+------+--------+------------+-------------+----------------------------------------------------------+
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1272896/+subscriptions
References