yahoo-eng-team team mailing list archive

[Amit Uniyal <2009448@xxxxxxxxxxxxxxxxxx>]

Public bug reported:


Description
===========
VM creation from a volume with no image data should not be allowed.
Right now, we can create a bootable volume with no image, and then we can create a VM from the volume. The VM will get created, but it won't boot as there is no image to boot from.

Nova should verify this request and send an error message with the
appropriate message.

Steps to reproduce
==================

$ openstack volume create --bootable --size 1 vol3     
$ openstack server create --network public --flavor 1  vm_3 --volume vol3  --wait                

$ openstack console log show vm_3           # it won't return any log
$ openstack console url show vm_3           # check via vnc


Expected result
===============
Nova should tell user, it's not correct.

Actual result
=============
VM gets created with without any issue, but user can't use it.

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

Title:
  Create VM from volume having no "volume_image_metadata" should not be
  allowed

Status in OpenStack Compute (nova):
  New

Bug description:

  Description
  ===========
  VM creation from a volume with no image data should not be allowed.
  Right now, we can create a bootable volume with no image, and then we can create a VM from the volume. The VM will get created, but it won't boot as there is no image to boot from.

  Nova should verify this request and send an error message with the
  appropriate message.

  Steps to reproduce
  ==================

  $ openstack volume create --bootable --size 1 vol3     
  $ openstack server create --network public --flavor 1  vm_3 --volume vol3  --wait                

  $ openstack console log show vm_3           # it won't return any log
  $ openstack console url show vm_3           # check via vnc

  
  Expected result
  ===============
  Nova should tell user, it's not correct.

  Actual result
  =============
  VM gets created with without any issue, but user can't use it.

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