yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #01885
[Bug 1064973] Re: Boot from volume causes network allocation problem
** Changed in: nova
Status: Invalid => New
--
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/1064973
Title:
Boot from volume causes network allocation problem
Status in OpenStack Compute (Nova):
New
Bug description:
Dear OpenStack developers,
The new Folsom feature "boot from volume" is really impressive and
very usefull for us, thank you very much. We found a bug during the
network allocation process when this feature is used.
In fact, when we boot an instance on a specified volume using command
line or Horizon dashboard:
For instance: nova boot --flavor 3 --image img-ID --security-groups
Proxy --nic net-id=net-ID --block-device-mapping vda=vol-ID:::0 test-
boot-volume
Nova compute automatically allocate all available networks (not only
the chosen one) to the newly created instance.
In our setup, we are using Quantum with the OpenVSwitch plugin.
Example:
root@as-001:~# quantum net-list
+--------------------------------------+--------+--------------------------------------+
| id | name | subnets |
+--------------------------------------+--------+--------------------------------------+
| 5b488575-9156-4b0a-82b9-102774194cde | lan | 7156a5de-b2d0-45ee-a08c-e4b987817a04 |
| 5ee6d216-d73a-4da6-8913-10dce3c92d8c | public | 7e101045-a1e2-4f16-bae5-7d394f5cf4d5 |
+--------------------------------------+--------+--------------------------------------+
nova boot --flavor 3 --image ae440422-f7e8-4c50-bda8-efbc9919d7c1
--security-groups Proxy --nic net-id=5b488575-9156-4b0a-
82b9-102774194cde --block-device-mapping
vda=1cf4ee59-7386-44c7-807e-647019462276:::0 test-ubuntu
But the instance "test-ubuntu" is automatically created with two NIC
(instead of one) on the networks LAN and PUBLIC (instead of only LAN
network).
root@as-001:~# nova list
+--------------------------------------+-------------+--------+--------------------------------------+
| ID | Name | Status | Networks |
+--------------------------------------+-------------+--------+--------------------------------------+
| 4137155f-e3f6-4cf6-bc8a-9282d269c6ef | test | ACTIVE | lan=172.16.0.3 |
| a0456945-d640-4567-b923-457aff4bf19e | test-ubuntu | ACTIVE | lan=172.16.0.4; public=5.135.124.198 |
+--------------------------------------+-------------+--------+--------------------------------------+
Here the log part for network allocation:
2012-10-10 13:26:12 AUDIT nova.compute.manager [req-6680c528-c1c0-4094-a137-bff037d6da02 ced093d0db3f408288acad5e7653e61e 52a5fe7334e846359dfa8cd16764eafd] [instance: a
513ba0b-51b7-4b30-bf1a-dfc8a193f054] Starting instance...
2012-10-10 13:26:12 DEBUG nova.utils [req-6680c528-c1c0-4094-a137-bff037d6da02 ced093d0db3f408288acad5e7653e61e 52a5fe7334e846359dfa8cd16764eafd] Got semaphore "compute
_resources" for method "update_usage"... from (pid=31752) inner /usr/lib/python2.7/dist-packages/nova/utils.py:713
2012-10-10 13:26:12 DEBUG nova.utils [req-6680c528-c1c0-4094-a137-bff037d6da02 ced093d0db3f408288acad5e7653e61e 52a5fe7334e846359dfa8cd16764eafd] Got semaphore "compute
_resources" for method "update_usage"... from (pid=31752) inner /usr/lib/python2.7/dist-packages/nova/utils.py:713
2012-10-10 13:26:12 DEBUG nova.network.quantumv2.api [req-6680c528-c1c0-4094-a137-bff037d6da02 ced093d0db3f408288acad5e7653e61e 52a5fe7334e846359dfa8cd16764eafd] alloca
te_for_instance() for test-ubuntu from (pid=31752) allocate_for_instance /usr/lib/python2.7/dist-packages/nova/network/quantumv2/api.py:93
2012-10-10 13:26:12 DEBUG nova.network.quantumv2.api [req-6680c528-c1c0-4094-a137-bff037d6da02 ced093d0db3f408288acad5e7653e61e 52a5fe7334e846359dfa8cd16764eafd] get_instance_nw_info() for test-ubuntu from (pid=31752) _get_instance_nw_info /usr/lib/python2.7/dist-packages/nova/network/quantumv2/api.py:178
2012-10-10 13:26:13 DEBUG nova.compute.manager [req-6680c528-c1c0-4094-a137-bff037d6da02 ced093d0db3f408288acad5e7653e61e 52a5fe7334e846359dfa8cd16764eafd] [instance: a513ba0b-51b7-4b30-bf1a-dfc8a193f054] Instance network_info: |[VIF({'network': Network({'bridge': '', 'subnets': [Subnet({'ips': [FixedIP({'meta': {}, 'version': 4, 'type': 'fixed', 'floating_ips': [], 'address': u'5.135.124.198'})], 'version': 4, 'meta': {'dhcp_server': u'5.135.124.193'}, 'dns': [IP({'meta': {}, 'version': 4, 'type': 'dns', 'address': u'8.8.4.4'}), IP({'meta': {}, 'version': 4, 'type': 'dns', 'address': u'8.8.8.8'})], 'routes': [], 'cidr': u'5.135.124.192/28', 'gateway': IP({'meta': {}, 'version': 4, 'type': 'gateway', 'address': u'5.135.124.206'})})], 'meta': {'injected': False, 'tenant_id': u'52a5fe7334e846359dfa8cd16764eafd'}, 'id': u'5ee6d216-d73a-4da6-8913-10dce3c92d8c', 'label': u'public'}), 'meta': {}, 'id': u'3710c3de-557c-47a4-b82f-03422939a1ca', 'address': u'fa:16:3e:ce:c1:b8'}), VIF({'network': Network({'bridge': '', 'subnets': [Subnet({'ips': [FixedIP({'meta': {}, 'version': 4, 'type': 'fixed', 'floating_ips': [], 'address': u'172.16.0.4'})], 'version': 4, 'meta': {'dhcp_server': u'172.16.0.2'}, 'dns': [IP({'meta': {}, 'version': 4, 'type': 'dns', 'address': u'8.8.4.4'}), IP({'meta': {}, 'version': 4, 'type': 'dns', 'address': u'8.8.8.8'})], 'routes': [], 'cidr': u'172.16.0.0/12', 'gateway': IP({'meta': {}, 'version': 4, 'type': 'gateway', 'address': u'172.16.0.1'})})], 'meta': {'injected': False, 'tenant_id': u'52a5fe7334e846359dfa8cd16764eafd'}, 'id': u'5b488575-9156-4b0a-82b9-102774194cde', 'label': u'lan'}), 'meta': {}, 'id': u'd4661f8a-6253-41b1-9921-ac72b70d372a', 'address': u'fa:16:3e:d9:c4:79'})]| from (pid=31752) _allocate_network /usr/lib/python2.7/dist-packages/nova/compute/manager.py:715
2012-10-10 13:26:13 DEBUG nova.utils [req-6680c528-c1c0-4094-a137-bff037d6da02 ced093d0db3f408288acad5e7653e61e 52a5fe7334e846359dfa8cd16764eafd] Got semaphore "compute_resources" for method "begin_resource_claim"... from (pid=31752) inner /usr/lib/python2.7/dist-packages/nova/utils.py:713
Let me know if you need further information.
Best regards.
Sam
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1064973/+subscriptions