← Back to team overview

yahoo-eng-team team mailing list archive

  1. yahoo-eng-team team
  2. Mailing list archive
  3. Message #39696

[Bug 1503346] [NEW] can not boot a VM with a custom Aggregates

  Thread Previous • Date Previous • • Thread Next 
Public bug reported:

boot a VM with a custom Aggregates will fail

1. Exact version of Nova/OpenStack you are running:
libera 

2. Reproduce steps:
step 1. in dashboard, admin -> host aggregates tap
    click "create host aggregate"
         "Host Aggregate Information" tap:
               name: "Pro"
               Availability Zone: "Pro-zone".
          "Manage Hosts within Aggregate" tap
               assign a host to this aggregate.

step 2. create an instance  with new  Availability Zone "Pro-zone".
      the instance will fail.

3. Relevant log files:
log:
383144-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d] Traceback (most recent call last):
383145-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d]   File "/opt/stack/nova/nova/compute/manager.py", line 1743, in _prep_block_device
383146-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d]     wait_func=self._await_block_device_map_created)
383147-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d]   File "/opt/stack/nova/nova/virt/block_device.py", line 476, in attach_block_devices
383148-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d]     map(_log_and_attach, block_device_mapping)
383149-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d]   File "/opt/stack/nova/nova/virt/block_device.py", line 474, in _log_and_attach
383150-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d]     bdm.attach(*attach_args, **attach_kwargs)
383151-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d]   File "/opt/stack/nova/nova/virt/block_device.py", line 383, in attach
383152-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d]     availability_zone=av_zone)
383153-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d]   File "/opt/stack/nova/nova/volume/cinder.py", line 388, in create
383154-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d]     raise exception.InvalidInput(reason=e)
383155-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d] InvalidInput: Invalid input received: Invalid input received: Availability zone 'nova-pro' is invalid. (HTTP 400) (Request-ID: req-daeac6d4-7464-4846-b71f-728e0e3069a1)

** Affects: nova
     Importance: Undecided
     Assignee: lvmxh (shaohef)
         Status: New

** Description changed:

  boot a VM with a custom Aggregates will fail
  
  1. Exact version of Nova/OpenStack you are running:
+ libera 
  
  2. Reproduce steps:
  step 1. in dashboard, admin -> host aggregates tap
-     click "create host aggregate"
-          "Host Aggregate Information" tap:
-                name: "Pro"
-                Availability Zone: "Pro-zone".
-           "Manage Hosts within Aggregate" tap
-                assign a host to this aggregate.
+     click "create host aggregate"
+          "Host Aggregate Information" tap:
+                name: "Pro"
+                Availability Zone: "Pro-zone".
+           "Manage Hosts within Aggregate" tap
+                assign a host to this aggregate.
  
  step 2. create an instance  with new  Availability Zone "Pro-zone".
-       the instance will fail.
- 
+       the instance will fail.
  
  3. Relevant log files:
- log: 
+ log:
  383144-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d] Traceback (most recent call last):
  383145-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d]   File "/opt/stack/nova/nova/compute/manager.py", line 1743, in _prep_block_device
  383146-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d]     wait_func=self._await_block_device_map_created)
  383147-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d]   File "/opt/stack/nova/nova/virt/block_device.py", line 476, in attach_block_devices
  383148-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d]     map(_log_and_attach, block_device_mapping)
  383149-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d]   File "/opt/stack/nova/nova/virt/block_device.py", line 474, in _log_and_attach
  383150-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d]     bdm.attach(*attach_args, **attach_kwargs)
  383151-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d]   File "/opt/stack/nova/nova/virt/block_device.py", line 383, in attach
  383152-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d]     availability_zone=av_zone)
  383153-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d]   File "/opt/stack/nova/nova/volume/cinder.py", line 388, in create
  383154-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d]     raise exception.InvalidInput(reason=e)
  383155-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d] InvalidInput: Invalid input received: Invalid input received: Availability zone 'nova-pro' is invalid. (HTTP 400) (Request-ID: req-daeac6d4-7464-4846-b71f-728e0e3069a1)

** Changed in: nova
     Assignee: (unassigned) => lvmxh (shaohef)

-- 
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/1503346

Title:
  can not boot a VM with a custom Aggregates

Status in OpenStack Compute (nova):
  New

Bug description:
  boot a VM with a custom Aggregates will fail

  1. Exact version of Nova/OpenStack you are running:
  libera 

  2. Reproduce steps:
  step 1. in dashboard, admin -> host aggregates tap
      click "create host aggregate"
           "Host Aggregate Information" tap:
                 name: "Pro"
                 Availability Zone: "Pro-zone".
            "Manage Hosts within Aggregate" tap
                 assign a host to this aggregate.

  step 2. create an instance  with new  Availability Zone "Pro-zone".
        the instance will fail.

  3. Relevant log files:
  log:
  383144-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d] Traceback (most recent call last):
  383145-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d]   File "/opt/stack/nova/nova/compute/manager.py", line 1743, in _prep_block_device
  383146-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d]     wait_func=self._await_block_device_map_created)
  383147-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d]   File "/opt/stack/nova/nova/virt/block_device.py", line 476, in attach_block_devices
  383148-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d]     map(_log_and_attach, block_device_mapping)
  383149-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d]   File "/opt/stack/nova/nova/virt/block_device.py", line 474, in _log_and_attach
  383150-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d]     bdm.attach(*attach_args, **attach_kwargs)
  383151-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d]   File "/opt/stack/nova/nova/virt/block_device.py", line 383, in attach
  383152-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d]     availability_zone=av_zone)
  383153-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d]   File "/opt/stack/nova/nova/volume/cinder.py", line 388, in create
  383154-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d]     raise exception.InvalidInput(reason=e)
  383155-2015-10-06 16:56:54.464 TRACE nova.compute.manager [instance: 6fea2aaa-3d9f-4d88-8987-4764084dbf4d] InvalidInput: Invalid input received: Invalid input received: Availability zone 'nova-pro' is invalid. (HTTP 400) (Request-ID: req-daeac6d4-7464-4846-b71f-728e0e3069a1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1503346/+subscriptions
  Thread Previous • Date Previous • • Thread Next