When launch an instance, selecting the source gets the volume snapshot list incorrectly

Bug #1736636 reported by Brin Zhang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
In Progress
Medium
Ahmed Zaid

Bug Description

On dashboard,steps as follows:
1.Open the OpenStack Horizon,select Project--> Compute--> instances-->Launch Instance;
2.Input instance name,next,Select Boot Source-->Volume Snapshot;
3.Get a list of available volume snapshots;
The snapshot list obtained here is incorrect.The volume on which these volume snapshots depend must be bootable,but all available snapshots of the volume are taken here, regardless of whether the volume on which the snapshot is based bootable.
4.next is ok.

Revision history for this message
Brin Zhang (zhangbailin) wrote :

The url of get volume snapshots is true,so change the project to cinder
e.g. http://10.180.207.25/volume/v2/06ceeae716e041e8b3acb53622b350bc/volumes/detail?bootable=1&status=available

affects: horizon → cinder
Brin Zhang (zhangbailin)
affects: cinder → horizon
Ying Zuo (yingzuo)
Changed in horizon:
importance: Undecided → Medium
milestone: none → next
status: New → Confirmed
Ahmed Zaid (ahmedzaid10)
Changed in horizon:
assignee: nobody → Ahmed Zaid (ahmedzaid10)
Revision history for this message
Ahmed Zaid (ahmedzaid10) wrote :

It gives error when you try to make instance with non bootable volume :
Block Device 44be9b74-eecd-4c57-af70-31079a227bf5 is not bootable. (HTTP 400) (Request-ID: req-3b408624-17ea-446d-9e8f-0112679b6136).

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to horizon (master)

Fix proposed to branch: master
Review: https://review.openstack.org/529532

Changed in horizon:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on horizon (master)

Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: master
Review: https://review.openstack.org/529532
Reason: This review is > 4 months without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.