With kvm virtualization choosen - fuel does not check if CN supports kvm hypervisor.
Bug #1413301 reported by
Piotr Skamruk
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Triaged
|
Low
|
Fuel Sustaining | ||
| 6.0.x |
Won't Fix
|
Low
|
Fuel Python (Deprecated) | ||
| 7.0.x |
Won't Fix
|
Low
|
Fuel Python (Deprecated) | ||
| 8.0.x |
Won't Fix
|
Low
|
Fuel Python (Deprecated) | ||
| Mitaka |
Won't Fix
|
Low
|
Fuel Python (Deprecated) | ||
| Newton |
Triaged
|
Low
|
Fuel Sustaining | ||
Bug Description
In time of environment creation there is possibility to choose KVM as hypervisor, but later, in time of adding nodes in "compute" role - there is no check if particular added nodes have hardware (i.e. enabled bios settings) support to choosen hypervisor.
IMO this should be verified (by modprobe kvm_intel || modprobe kvm_amd) in time of adding nodes to "compute" role.
| Changed in fuel: | |
| assignee: | nobody → Fuel Library Team (fuel-library) |
| importance: | Undecided → Medium |
| importance: | Medium → Wishlist |
| milestone: | none → 6.1 |
| Changed in fuel: | |
| status: | New → Confirmed |
| Changed in fuel: | |
| importance: | Wishlist → Low |
| status: | Confirmed → Won't Fix |
Revision history for this message
| Bartłomiej Piotrowski (bpiotrowski) wrote | #1 |
Revision history for this message
| Matthew Mosesohn (raytrac3r) wrote | #2 |
| tags: | added: feature |
| Changed in fuel: | |
| milestone: | 6.1 → 8.0 |
| no longer affects: | fuel/8.0.x |
| tags: | added: area-python |
Revision history for this message
| Alexander Kislitsky (akislitsky) wrote | #3 |
| Changed in fuel: | |
| milestone: | 8.0 → 9.0 |
| tags: | added: wontfix-low |
To post a comment you must log in.
Moving to 8.0 as it's a low priority bug and we have SCF incoming.