yahoo-eng-team team mailing list archive

[Feodor Tersin <ftersin@xxxxxxxxxxx>]

Public bug reported:

Since that https://review.openstack.org/#/c/182994/ is merged, Cinder
doesn't allow an empty volume name. But Nova specifies it for a new
volume when the volume is created from a snapshot or a volume. Thus boot
operation fails on compute node.

Steps to reproduce:
1 Boot an instance from a volume which should be autocreated from an image
nova boot inst --block-device source=image,dest=volume,bootindex=0,size=1,id=<cirros_id> --flavor m1.nano

2 Wait a bit and look at the instance state
nova show inst

Expected result: the instance state is active.
Actual result: the instance state is error, current stage is block device mapping.

** Affects: nova
     Importance: Undecided
         Status: New

** Description changed:

  Since that https://review.openstack.org/#/c/182994/ is merged, Cinder
  doesn't allow an empty volume name. But Nova specifies it for a new
  volume when the volume is created from a snapshot or a volume. Thus boot
  operation fails on compute node.
  
  Steps to reproduce:
  1 Boot an instance from a volume which should be autocreated from an image
  nova boot inst --block-device source=image,dest=volume,bootindex=0,size=1,id=<cirros_id> --flavor m1.nano
  
- 2 Wait a few time and look at the instance state
+ 2 Wait a bit and look at the instance state
  nova show inst
  
  Expected result: the instance state is active.
  Actual result: the instance state is error, current stage is block device mapping.

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

Title:
  Cannot boot if bdm specifies to create a new volume from an image or a
  snapshot

Status in OpenStack Compute (nova):
  New

Bug description:
  Since that https://review.openstack.org/#/c/182994/ is merged, Cinder
  doesn't allow an empty volume name. But Nova specifies it for a new
  volume when the volume is created from a snapshot or a volume. Thus
  boot operation fails on compute node.

  Steps to reproduce:
  1 Boot an instance from a volume which should be autocreated from an image
  nova boot inst --block-device source=image,dest=volume,bootindex=0,size=1,id=<cirros_id> --flavor m1.nano

  2 Wait a bit and look at the instance state
  nova show inst

  Expected result: the instance state is active.
  Actual result: the instance state is error, current stage is block device mapping.

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