yahoo-eng-team team mailing list archive

["Gary W. Smith" <gary.w.smith@xxxxxx>]

1. If you want a volume to create an image, the easiest way is to do so at volume creation type by specifying that the volume source is an image rather than empty. But, if you want to take an empty volume and place a bootable image on it, you can attach the volume to a VM, login to the VM, and download (or build up) a bootable image on that volume.
2. The bootable flag indicates that the volume likely contains a bootable image. If you create a volume from an image, the bootable flag is set automatically. If you set a volume to bootable when the volume contains no bootable image (as you appear to have done), then you will get the error if you try to boot it.
3. Uploading a volume to image (glance) is useful in a variety of circumstances, but there is no requirement that the volume being upload is bootable. 


** Changed in: horizon
       Status: New => Invalid

** Tags added: volume

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1456458

Title:
  Create volume without source (empty volume)

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  When create a new volume without source, the empty volume is not
  bootable. then going to edit volume to  change it to bootable and the
  status of bootable in this volume is "YES".

               1.  Don't we have any button to add image to this empty
  volume ?

               2. When we launch new instance from this volume. This is successful with status "active", but in the console we will see the infor : " Booting from hard Disk... Boot failed: not a bootble disk .... No bootable device"
                  ---> so what does the status "YES" of bootable in the volume mean?

              3. we can create new volume, upload to image from above
  volume. The new is unusable the same. what  purpose for this flow?

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