yahoo-eng-team team mailing list archive

[James Lewis <1317880@xxxxxxxxxxxxxxxxxx>]

There seems to be a disconnect between Nova and Horizon here, because
what Nikola Đipanov observed to be "by design" in Nova below in comment
#6 appears to break functionality in Horizon.

** Also 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 Compute (nova).
https://bugs.launchpad.net/bugs/1317880

Title:
  Boot from image (creates a new volume) starts an instance with no
  image

Status in OpenStack Dashboard (Horizon):
  New
Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  1. Fire up a DevStack instance from the stable/havana, stable/icehouse, or master branches.
  2. Go into Horizon
  3. Launch an instance
  3.1 Instance Boot Source: Boot from image (creates a new volume)
  3.2 Image Name: cirros
  3.3 Device size (GB): 1

  When the instance finishes booting you’ll see that the instance only
  has a ‘-‘ in the Image Name column. If you click on the instance
  you’ll see in the Overview Meta section “Image Name (not found)”.

  My understanding of Boot from image (creates a new volume) is that it
  simply creates a instance and attaches a volume automatically. It’s
  basically a convenience for the user. Is that right?

  Seems the bug is in Nova as the instance was created with the cirros
  image and Nova isn’t reporting that fact back. The different responses
  from various clients.

  API
      curl .../v2/tenant_id/servers/server_id
      "image": “”
  python-novaclient
      nova show server_id
      "Attempt to boot from volume - no image supplied”
  Horizon
      "Image Name (not found)"

  I suspect Horizon is making some bad calls but Nova shouldn’t be
  allowing an instance to get into this state.

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