← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1456458] [NEW] Create volume without source (empty volume)

 

Public bug reported:

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?

** Affects: horizon
     Importance: Undecided
         Status: New

-- 
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):
  New

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


Follow ups

References