[volume allocation] Default disk partitioning logic is not optimal: we have unallocated disk space
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Confirmed
|
High
|
Fuel Sustaining | ||
| 7.0.x |
Won't Fix
|
High
|
Alexander Gordeev | ||
| Mitaka |
Won't Fix
|
High
|
Fuel Python (Deprecated) | ||
Bug Description
Note: probably we can write the error message on WebUI if we have unallocated disk space - and we need to do it before user will deploy the cloud.
Steps To Reproduce:
1. Create OpenStack environment with 3 controllers, which have 2 disks with 80Gb and 1000Gb.
2. Use default disk allocation logic (do not change partitioning for these disks)
3. Deploy OpenStack cloud on these servers
4. Wait 4 days.
Expected Result:
All available disks will be fully used for cloud needs. We shouldn't have unallocated disk space.
Observed Result:
cloud will die because of full disk space, we can see that logs and MySQL disks partitions are full. In the same time we can see that we allocated only part of the first disk and we have not allocated disk space on BOTH disks! (please see attached screenshot for more detailed information)
| Timur Nurlygayanov (tnurlygayanov) wrote | #1 |
| Changed in fuel: | |
| importance: | Undecided → High |
| status: | New → Confirmed |
| milestone: | none → 7.0 |
| description: | updated |
| Timur Nurlygayanov (tnurlygayanov) wrote | #2 |
| Changed in fuel: | |
| assignee: | Fuel UI Team (fuel-ui) → Aleksandr Gordeev (a-gordeev) |
| Changed in fuel: | |
| status: | Confirmed → Won't Fix |
| tags: | added: release-notes |
| OpenStack Infra (hudson-openstack) wrote Related fix proposed to fuel-docs (master) | #3 |
| OpenStack Infra (hudson-openstack) wrote Related fix merged to fuel-docs (master) | #4 |
| tags: | added: feature |
| tags: | added: tricky |
| tags: |
added: covered-by-bp removed: feature |
| tags: | added: long-haul-testing |
| tags: | removed: long-haul-testing |
| tags: | added: long-haul-testing |
| Changed in fuel: | |
| milestone: | 7.0 → 8.0 |
| status: | Won't Fix → Confirmed |
| no longer affects: | fuel/8.0.x |
| tags: | added: area-python |
| Changed in fuel: | |
| milestone: | 8.0 → 9.0 |
| tags: | added: need-info |
| tags: | removed: need-info |
| OpenStack Infra (hudson-openstack) wrote Related fix proposed to fuel-docs (master) | #5 |
| OpenStack Infra (hudson-openstack) wrote Related fix merged to fuel-docs (master) | #6 |
| Changed in fuel: | |
| milestone: | 9.0 → 10.0 |
| Timur Nurlygayanov (tnurlygayanov) wrote | #8 |
| Fuel Devops McRobotson (fuel-devops-robot) wrote Related fix proposed to mos/mos-docs (master) | #9 |
| Fuel Devops McRobotson (fuel-devops-robot) wrote Related fix merged to mos/mos-docs (master) | #10 |
| Changed in fuel: | |
| assignee: | Fuel Python (Deprecated) (fuel-python) → Fuel Sustaining (fuel-sustaining-team) |
| tags: |
added: release-notes-done removed: release-notes |
Looks like for MOS 7.0 we can't fix the main logic of the disk partitioning, but we can try to prepare the workaround for the issue and show some warning message to user if we have some unallocated disk space.