yahoo-eng-team team mailing list archive

[Edward Hope-Morley <edward.hope-morley@xxxxxxxxxxxxx>]

Public bug reported:

When booting an instance using:

nova boot --flavor <some-flavor-id> \
--block-device id=<image-id>,source=image,dest=volume,size=10,bus=virtio,bootindex=0 \
--block-device source=blank,dest=volume,size=1,format=swap,bus=virtio,bootindex=1 \
--block-device source=blank,dest=volume,size=100,format=disk,bus=virtio,bootindex=2 a-test-vm

the command completes without error but both extra volumes are created
as local raw images instead of in cinder. So for non-root volumes,
dest=volume has the same effect as dest=blank but dest=volume should
really be creating the volumes using cinder.

** 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/1341684

Title:
  nova boot not creating non-root volume type properly

Status in OpenStack Compute (Nova):
  New

Bug description:
  When booting an instance using:

  nova boot --flavor <some-flavor-id> \
  --block-device id=<image-id>,source=image,dest=volume,size=10,bus=virtio,bootindex=0 \
  --block-device source=blank,dest=volume,size=1,format=swap,bus=virtio,bootindex=1 \
  --block-device source=blank,dest=volume,size=100,format=disk,bus=virtio,bootindex=2 a-test-vm

  the command completes without error but both extra volumes are created
  as local raw images instead of in cinder. So for non-root volumes,
  dest=volume has the same effect as dest=blank but dest=volume should
  really be creating the volumes using cinder.

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