MAAS used wrong commissioning series

Bug #2045792 reported by Marian Gasparovic
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Triaged
High
Unassigned

Bug Description

While testing MAAS 3.4 we encountered an issue when machines were commissioned using bionic instead of jammy.
We download bionic, focal and jammy images and we don't specify default commissioning series. Machines are commissioned with jammy. But in this run all machines failed commissioning and in rsyslog we can see it used bionic. Then it failed later because commissioning script uses Python3.

Logs - https://oil-jenkins.canonical.com/artifacts/0ab95743-3cad-4cde-be19-d6d4be8c1cc9/index.html

We have two occurrences of this issue.

Revision history for this message
Christian Grabowski (cgrabowski) wrote :

Hi there, looking at the hardware info in the artifacts, to confirm, these are all amd64 machines? And are the machines being commissioned bare metal or VMs?

Changed in maas:
status: New → Incomplete
Revision history for this message
Marian Gasparovic (marosg) wrote :

Yes, all amd64 and all commissioning machines are baremetal

Changed in maas:
status: Incomplete → New
Revision history for this message
Christian Grabowski (cgrabowski) wrote :

able to reproduce when commissioning a new bare metal machine specifically on 3.4 latest. Does not seem to be the case upon recommission, nor the commissioning that occurs when composing VMs.

Changed in maas:
status: New → Triaged
importance: Undecided → High
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.