Volume dropdown is empty if only Cinder v2 is running
Bug #1477783 reported by
Yash Bathia
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Fix Released
|
Low
|
Yash Bathia |
Bug Description
Currently create_instance workflow only checks if Cinder v1 is enabled before populating volume id choices and volume snapshot id choices in the Launch Instance form. There should be checks to ensure if either Cinder v1 or v2 is enabled before populating the drop-down menu in Launch Instance.
Changed in horizon: | |
assignee: | nobody → Yash Bathia (ybathia) |
summary: |
- Handle Launch Instance errors when Cinder is disabled + Allow Cinder v1 or v2 to populate drop-down menu in Launch Instance |
description: | updated |
Changed in horizon: | |
assignee: | Yash Bathia (ybathia) → Lin Hua Cheng (lin-hua-cheng) |
Changed in horizon: | |
assignee: | Lin Hua Cheng (lin-hua-cheng) → Yash Bathia (ybathia) |
importance: | Undecided → Low |
summary: |
- Allow Cinder v1 or v2 to populate drop-down menu in Launch Instance + Volume dropdown is empty if only Cinder v2 is running |
Changed in horizon: | |
milestone: | none → liberty-3 |
Changed in horizon: | |
status: | Fix Committed → Fix Released |
Changed in horizon: | |
milestone: | liberty-3 → 8.0.0 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/205339
Review: https:/