For vCenter: need to lock "CinderLVM" and check by default "VMware vCenter"
Bug #1352401 reported by
Anastasia Palkina
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Fuel UI Team |
Bug Description
"build_id": "2014-08-
"ostf_sha": "a3fa823ea0e4e0
"build_number": "390",
"auth_required": true,
"api": "1.0",
"nailgun_sha": "bd0127be006102
"production": "docker",
"fuelmain_sha": "e99879292cf6e9
"astute_sha": "ce86172e776610
"feature_groups": ["mirantis", "experimental"],
"release": "5.1",
"fuellib_sha": "4e3fdd75f8dabd
1. Create new environment (CentOS, simple mode)
2. Choose vCenter
3. Move to tab "Settings"
4. Need to lock "CinderLVM" and check by default "VMware vCenter for volumes (Cinder)"
Changed in fuel: | |
assignee: | Fuel UI Team (fuel-ui) → Vitaly Kramskikh (vkramskikh) |
Changed in fuel: | |
assignee: | Vitaly Kramskikh (vkramskikh) → Fuel UI Team (fuel-ui) |
milestone: | 5.1 → 6.0 |
Changed in fuel: | |
status: | New → Confirmed |
To post a comment you must log in.
Related bug #1352885 marked as duplicate: "Storage - Cinder LVM" nodes should not be allowed when vCenter vmdk backend is used for Cinder.