With kvm virtualization choosen - fuel does not check if CN supports kvm hypervisor.

Bug #1413301 reported by Piotr Skamruk on 2015-01-21
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Low
Fuel Sustaining
6.0.x
Low
Fuel Python (Deprecated)
7.0.x
Low
Fuel Python (Deprecated)
8.0.x
Low
Fuel Python (Deprecated)
Mitaka
Low
Fuel Python (Deprecated)
Newton
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

Moving to 8.0 as it's a low priority bug and we have SCF incoming.

Matthew Mosesohn (raytrac3r) wrote :

The only way we can give feedback for the user is if nailgun agent reported KVM capability of the host in bootstrap mode. This should go over to fuel-python and be considered as a wishlist and feature.

Dmitry Pyzhov (dpyzhov) on 2015-09-28
tags: added: feature
Dmitry Pyzhov (dpyzhov) on 2015-10-12
Changed in fuel:
milestone: 6.1 → 8.0
no longer affects: fuel/8.0.x
Dmitry Pyzhov (dpyzhov) on 2015-10-22
tags: added: area-python

We passed SCF in 8.0. Moving the bug to 9.0.

Changed in fuel:
milestone: 8.0 → 9.0
tags: added: wontfix-low
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers