yahoo-eng-team team mailing list archive

[Oleksii Aleksieiev <alexzzman@xxxxxxxxx>]

Public bug reported:

Boot from image and creation of a new volume does not pass instance
availability zone to cinder when creating volume.

Here is a fail scenario.

Configure cinder to run volume service in different availability zones.

[root@node-7 ~]# cinder service-list
+------------------+--------------------+----------+---------+-------+----------------------------+
|      Binary      |        Host        |   Zone   |  Status | State |         Updated_at         |
+------------------+--------------------+----------+---------+-------+----------------------------+
| cinder-scheduler | node-10.domain.tld | internal | enabled |   up  | 2014-10-13T20:12:18.000000 |
| cinder-scheduler | node-7.domain.tld  | internal | enabled |   up  | 2014-10-13T20:12:15.000000 |
| cinder-scheduler | node-8.domain.tld  | internal | enabled |   up  | 2014-10-13T20:12:18.000000 |
|  cinder-volume   |   node-10.reg1a    |  reg1a   | enabled |   up  | 2014-10-13T20:12:14.000000 |
|  cinder-volume   |   node-10.reg1b    |  reg1b   | enabled |   up  | 2014-10-13T20:12:14.000000 |
|  cinder-volume   |    node-7.reg1a    |  reg1a   | enabled |   up  | 2014-10-13T20:12:18.000000 |
|  cinder-volume   |    node-7.reg1b    |  reg1b   | enabled |   up  | 2014-10-13T20:12:14.000000 |
|  cinder-volume   |    node-8.reg1a    |  reg1a   | enabled |   up  | 2014-10-13T20:12:21.000000 |
|  cinder-volume   |    node-8.reg1b    |  reg1b   | enabled |   up  | 2014-10-13T20:12:21.000000 |
+------------------+--------------------+----------+---------+-------+----------------------------+

 
Run CLI as below to create a volume from an existing image and using it to boot an instance.

nova boot test --flavor 1 --image 32705323-4bfb-4cd7-9711-f5459fd236d8
--nic net-id=ca3b4232-405c-4225-9724-0f0dde69c1d5  --availability-
zone=reg1a  --block-device "source=image,id=32705323-4bfb-
4cd7-9711-f5459fd236d8,dest=volume,size=10,bootindex=1"

This will attempt to create volume in internal (default) availability
zone. But creation will fail because there are no volume service in
internal  availability zone.

+--------------------------------+--------------------------------------+
|            Property            |                Value                 |
+--------------------------------+--------------------------------------+
|          attachments           |                  []                  |
|       availability_zone        |               internal               |
|            bootable            |                false                 |
|           created_at           |      2014-10-13T19:45:24.000000      |
|      display_description       |                                      |
|          display_name          |                                      |
|           encrypted            |                False                 |
|               id               | e358b519-4287-45a5-85cc-1e6a0d371fb1 |
|            metadata            |                  {}                  |
|     os-vol-host-attr:host      |                 None                 |
| os-vol-mig-status-attr:migstat |                 None                 |
| os-vol-mig-status-attr:name_id |                 None                 |
|  os-vol-tenant-attr:tenant_id  |   1cd2c85585ed42dcaf266b57c22c86ef   |
|              size              |                  10                  |
|          snapshot_id           |                 None                 |
|          source_volid          |                 None                 |
|             status             |                error                 |
|          volume_type           |                 None                 |
+--------------------------------+--------------------------------------+

The instance boot fail with error: "InvalidVolume: Invalid volume:
status must be 'available'".

** Affects: nova
     Importance: Undecided
         Status: 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/1380780

Title:
  Boot from image and create a new volume ignores availability zone

Status in OpenStack Compute (Nova):
  New

Bug description:
  Boot from image and creation of a new volume does not pass instance
  availability zone to cinder when creating volume.

  Here is a fail scenario.

  Configure cinder to run volume service in different availability
  zones.

  [root@node-7 ~]# cinder service-list
  +------------------+--------------------+----------+---------+-------+----------------------------+
  |      Binary      |        Host        |   Zone   |  Status | State |         Updated_at         |
  +------------------+--------------------+----------+---------+-------+----------------------------+
  | cinder-scheduler | node-10.domain.tld | internal | enabled |   up  | 2014-10-13T20:12:18.000000 |
  | cinder-scheduler | node-7.domain.tld  | internal | enabled |   up  | 2014-10-13T20:12:15.000000 |
  | cinder-scheduler | node-8.domain.tld  | internal | enabled |   up  | 2014-10-13T20:12:18.000000 |
  |  cinder-volume   |   node-10.reg1a    |  reg1a   | enabled |   up  | 2014-10-13T20:12:14.000000 |
  |  cinder-volume   |   node-10.reg1b    |  reg1b   | enabled |   up  | 2014-10-13T20:12:14.000000 |
  |  cinder-volume   |    node-7.reg1a    |  reg1a   | enabled |   up  | 2014-10-13T20:12:18.000000 |
  |  cinder-volume   |    node-7.reg1b    |  reg1b   | enabled |   up  | 2014-10-13T20:12:14.000000 |
  |  cinder-volume   |    node-8.reg1a    |  reg1a   | enabled |   up  | 2014-10-13T20:12:21.000000 |
  |  cinder-volume   |    node-8.reg1b    |  reg1b   | enabled |   up  | 2014-10-13T20:12:21.000000 |
  +------------------+--------------------+----------+---------+-------+----------------------------+

   
  Run CLI as below to create a volume from an existing image and using it to boot an instance.

  nova boot test --flavor 1 --image 32705323-4bfb-4cd7-9711-f5459fd236d8
  --nic net-id=ca3b4232-405c-4225-9724-0f0dde69c1d5  --availability-
  zone=reg1a  --block-device "source=image,id=32705323-4bfb-
  4cd7-9711-f5459fd236d8,dest=volume,size=10,bootindex=1"

  This will attempt to create volume in internal (default) availability
  zone. But creation will fail because there are no volume service in
  internal  availability zone.

  +--------------------------------+--------------------------------------+
  |            Property            |                Value                 |
  +--------------------------------+--------------------------------------+
  |          attachments           |                  []                  |
  |       availability_zone        |               internal               |
  |            bootable            |                false                 |
  |           created_at           |      2014-10-13T19:45:24.000000      |
  |      display_description       |                                      |
  |          display_name          |                                      |
  |           encrypted            |                False                 |
  |               id               | e358b519-4287-45a5-85cc-1e6a0d371fb1 |
  |            metadata            |                  {}                  |
  |     os-vol-host-attr:host      |                 None                 |
  | os-vol-mig-status-attr:migstat |                 None                 |
  | os-vol-mig-status-attr:name_id |                 None                 |
  |  os-vol-tenant-attr:tenant_id  |   1cd2c85585ed42dcaf266b57c22c86ef   |
  |              size              |                  10                  |
  |          snapshot_id           |                 None                 |
  |          source_volid          |                 None                 |
  |             status             |                error                 |
  |          volume_type           |                 None                 |
  +--------------------------------+--------------------------------------+

  The instance boot fail with error: "InvalidVolume: Invalid volume:
  status must be 'available'".

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1380780/+subscriptions