yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #14251
[Bug 1297701] Re: Create VM use another tenant's port, the VM can't communicate with other
I think in this case it should be up to the admin to ensure the appropriate security group rules are added.
Do you think it should be different?
** Changed in: neutron
Status: New => Confirmed
** Changed in: neutron
Status: Confirmed => Opinion
** Changed in: neutron
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1297701
Title:
Create VM use another tenant's port, the VM can't communicate with
other
Status in OpenStack Neutron (virtual network service):
Opinion
Status in OpenStack Compute (Nova):
New
Bug description:
An admin user create port for another project, then use this port
Create VM, the VM can't communicate with other, because the security
rule does not work. the vm in nova can not show IP.
root@ubuntu01:/var/log/neutron# neutron port-show 66c2d6bd-7d39-4948-b561-935cb9d264eb
+-----------------------+-----------------------------------------------------------------------------------+
| Field | Value |
+-----------------------+-----------------------------------------------------------------------------------+
| admin_state_up | True |
| allowed_address_pairs | {"ip_address": "169.254.16.253", "mac_address": "fa:16:3e:48:73:a7"} |
| binding:capabilities | {"port_filter": false} |
| binding:host_id | |
| binding:vif_type | unbound |
| device_id | |
| device_owner | |
| extra_dhcp_opts | |
| fixed_ips | {"subnet_id": "5519e015-fc83-44c2-99ad-d669b3c2c9d7", "ip_address": "10.10.10.4"} |
| id | 66c2d6bd-7d39-4948-b561-935cb9d264eb |
| mac_address | fa:16:3e:48:73:a7 |
| name | |
| network_id | 255f3e92-5a6e-44a5-bbf9-1a62bf5d5935 |
| security_groups | 94ad554f-392d-4dd5-8184-357f37b75111 |
| status | DOWN |
| tenant_id | 3badf700bbc749ec9d9869fddc63899f |
+-----------------------+-----------------------------------------------------------------------------------+
root@ubuntu01:/var/log/neutron# keystone tenant-list
+----------------------------------+---------+---------+
| id | name | enabled |
+----------------------------------+---------+---------+
| 34fddbc22c184214b823be267837ef81 | admin | True |
| 48eb4330b6e74a9f9e74d3e191a0fa2e | service | True |
+----------------------------------+---------+---------+
root@ubuntu01:/var/log/neutron# nova list
+--------------------------------------+-------+--------+------------+-------------+----------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+-------+--------+------------+-------------+----------+
| 5ce98599-75cb-49db-aa76-668491ee3bd0 | test3 | ACTIVE | None | Running | |
+--------------------------------------+-------+--------+------------+-------------+----------+
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1297701/+subscriptions
References