Can't deploy focal KVM hosts

Bug #1881655 reported by Jorge Niedbalski
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
MAAS
Expired
High
Unassigned

Bug Description

[Environment]

Focal 20.04

maas 2.8.0~beta4-8512-g.1897d06c8 6741 latest/edge canonical* -
maas-cli 0.6.5 13 latest/stable canonical* -

Reproducible with 2.7 as well.

[Description]

I have a all-in-one installation with only 20.04 images synchronized and settings
enforced to use 20.04 for commissioning/deploy as default.

* Isn't possible to deploy a machine with focal + selecting it as
"Register as MAAS KVM host", the error "ubuntu/bionic is not a supported operating system and release combination." is raised.

Steps to reproduce.

1) Select Deploy
2) Select 20.04 and default kernel
3) Click on "register as MAAS KVM host"
4) Click on deploy

Error "ubuntu/bionic is not a supported operating system and release combination." is raised.

Tags: seg
Felipe Reyes (freyes)
tags: added: seg
Changed in maas:
status: New → Confirmed
Revision history for this message
Victor Tapia (vtapia) wrote :

libvirt-bin is not available in Focal and the UI is filtering the deployment of Focal+KVM. I'm attaching two patches for MAAS 2.8 that enable that combination by updating the UI filter and replacing the package with ones that are available both in Bionic and Focal (libvirt-daemon, libvirt-clients..). I've been testing the change and it seems to work fine.

Revision history for this message
Victor Tapia (vtapia) wrote :
Alberto Donato (ack)
Changed in maas:
status: Confirmed → Triaged
milestone: none → 2.9.0b1
milestone: 2.9.0b1 → none
importance: Undecided → High
Revision history for this message
Adam Collard (adam-collard) wrote :

Since this bug was filed, MAAS has grown support for deploying KVM hosts on Focal and beyond - can you confirm if this works for you now in a stable MAAS release (e.g. 3.2.2)

Changed in maas:
status: Triaged → Incomplete
Alberto Donato (ack)
Changed in maas:
status: Incomplete → New
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for MAAS because there has been no activity for 60 days.]

Changed in maas:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.