yahoo-eng-team team mailing list archive

[lyanchih <lyan.h@xxxxxxxxxxxxxx>]

Public bug reported:

How to reproduce:
1.  create new volume and volume source is image
2.  Snapshot volume which was created at step1
3.  Launch as instance from snapshot volume which was created at step2
Then horizon will display "Block Device Mapping is Invalid: failed to get volume"

Because horizon will send volume source type instead of snapshot source type to nova. 
Therefore nova api will try to fetch volume tough volume id instead of snapshot. 
Nova create server request's data was incorrect at following link and line.
https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/instances/workflows/create_instance.py#L874

** Affects: horizon
     Importance: Undecided
     Assignee: lyanchih (lyanchih)
         Status: New

** Changed in: horizon
     Assignee: (unassigned) => lyanchih (lyanchih)

-- 
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/1474283

Title:
  Boot instance from volume snapshot fail

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  How to reproduce:
  1.  create new volume and volume source is image
  2.  Snapshot volume which was created at step1
  3.  Launch as instance from snapshot volume which was created at step2
  Then horizon will display "Block Device Mapping is Invalid: failed to get volume"

  Because horizon will send volume source type instead of snapshot source type to nova. 
  Therefore nova api will try to fetch volume tough volume id instead of snapshot. 
  Nova create server request's data was incorrect at following link and line.
  https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/instances/workflows/create_instance.py#L874

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