It's possible to assign role(s) to a node that can't meet default disk allocation minimums
Bug #1453885 reported by
Andrew Woodward
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Confirmed
|
Medium
|
Fuel Sustaining | ||
6.0.x |
Won't Fix
|
Medium
|
Unassigned | ||
6.1.x |
Won't Fix
|
Medium
|
Unassigned | ||
7.0.x |
Won't Fix
|
Medium
|
Fuel Python (Deprecated) | ||
8.0.x |
Won't Fix
|
Medium
|
Fuel Python (Deprecated) | ||
Mitaka |
Won't Fix
|
Medium
|
Fuel Python (Deprecated) | ||
Newton |
Confirmed
|
Medium
|
Fuel Sustaining |
Bug Description
When assigning roles, its possible to assign one or more roles that cant satisfy the default disk allocations.
steps to reproduce
1. create a 20gb disk VM
2. discover the vm
3. allocate the VM to controller and cinder iscsi roles
expected result
node role combo should raise an exception that is given to the user and added role should not be saved.
actual result.
Node is successfully assigned role(s) in the cluster
Node can be deployed with the bad disk space
Changed in fuel: | |
milestone: | none → 6.1 |
summary: |
- its possible to assign a node to role(s) that cant meet default disk - allocation + It's possible to assign role(s) to a node that can't meet default disk + allocation minimums |
Changed in fuel: | |
importance: | Undecided → Medium |
milestone: | 6.1 → 7.0 |
tags: | added: module-astute ui |
tags: |
added: module-nailgun removed: module-astute |
tags: | added: customer-found |
description: | updated |
no longer affects: | fuel/8.0.x |
Changed in fuel: | |
milestone: | 7.0 → 8.0 |
tags: | added: area-python |
tags: | added: wontfix-low |
To post a comment you must log in.
Looks like this bug covered by blueprint: https:/ /blueprints. launchpad. net/fuel/ +spec/volume- manager- refactoring. Move it to 8.0 after discuss with Alexander Gordeev.
Feel free to return and up priority if do not agree.