Boot instance from volume snapshot fails
Bug #1499418 reported by
Patrick Smith
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Group Based Policy UI |
Fix Released
|
Critical
|
ank |
Bug Description
There was a bug in the create instance workflow in horizon that caused booting an instance from a volume snapshot to fail: https:/
The fix to that bug needs to be applied to the launch member workflow in GBP-UI.
Changed in group-based-policy: | |
milestone: | none → next |
affects: | group-based-policy → group-based-policy-ui |
Changed in group-based-policy-ui: | |
milestone: | next → none |
assignee: | nobody → ank (ank.b) |
importance: | Undecided → Critical |
status: | New → Confirmed |
Changed in group-based-policy-ui: | |
milestone: | none → liberty-1 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/227364 /git.openstack. org/cgit/ stackforge/ group-based- policy- ui/commit/ ?id=aafbb7e536e 99255c4667341a9 8425d2c3052836
Committed: https:/
Submitter: Jenkins
Branch: stable/kilo
commit aafbb7e536e9925 5c4667341a98425 d2c3052836
Author: Patrick Smith <email address hidden>
Date: Thu Sep 24 11:09:35 2015 -0400
Fix booting from volume snapshot
When passing the source type of the block device mapping when booting
from a volume snapshot, we need to specify "snapshot" instead of
"volume".
This fix is the same as the one applied in horizon: /github. com/openstack/ horizon/ commit/ a1db17aeff84256 6e6ac429889ca9a 3dad9a6daa
https:/
Change-Id: I4b110af9956773 e1ce53dbce91557 ac26f171c1a
Closes-Bug: #1499418