Wrong disk setup shown while extending
Bug #1387028 reported by
Marc Koderer
This bug affects 6 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Fix Committed
|
High
|
Aleksey Kasatkin | ||
| 6.0.x |
Won't Fix
|
Medium
|
Aleksey Kasatkin | ||
Bug Description
Problem:
-----------
After activation of additional disks in the raid controller Fuel shows a wrong disk setup and cannot be changed.
Steps:
--------
1.) Setup a compute node with storage (lvm). Only 2 disk are active (300gb)
2.) Activate additional disks (6.5TB)
3.) The shown disk layout for the node changed. It looks like that the newly added disks are used for LVM.
But this is not the case:
# lvm vgs
VG #PV #LV #SN Attr VSize VFree
cinder 1 1 0 wz--n- 112.41g 111.41g
image 1 1 0 wz--n- 112.41g 32.00m
Revision history for this message
| Marc Koderer (m-koderer) wrote | #1 |
| Changed in fuel: | |
| milestone: | none → 6.0 |
| assignee: | nobody → Fuel Python Team (fuel-python) |
Revision history for this message
| Dima Shulyak (dshulyak) wrote | #2 |
| Changed in fuel: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
Revision history for this message
| Marc Koderer (m-koderer) wrote | #3 |
| Changed in fuel: | |
| milestone: | 6.0 → 6.1 |
| tags: | added: module-volumes |
| tags: | added: customer-found |
| tags: | added: feature-hardware-change |
| Changed in fuel: | |
| assignee: | Fuel Python Team (fuel-python) → Aleksey Kasatkin (alekseyk-ru) |
Revision history for this message
| Dmitry Pyzhov (dpyzhov) wrote | #4 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to fuel-web (master) | #5 |
| Changed in fuel: | |
| status: | Confirmed → In Progress |
| Changed in fuel: | |
| importance: | Medium → High |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to fuel-web (master) | #6 |
| Changed in fuel: | |
| status: | In Progress → Fix Committed |
To post a comment you must log in.
You activated disk after node was provisioned?
I think if you will re-provision node with all disks activated before provisioning - the will be no such problem.
But i understand that this may be not an option.