Unable to deploy LXD VM host on S390X

Bug #1923685 reported by Lee Trager
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Incomplete
Medium
Unassigned
Ubuntu on IBM z Systems
Triaged
Medium
Unassigned
lxd (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I just tried to deploy an LXD VM host on S390X. This is failing due to a bug in LXD which has been fixed[1]. It appears that this bug has not been backported to LXD 4.0.5 or earlier.

[1] https://github.com/lxc/lxd/issues/8477

Tags: s390x maas
Frank Heimes (fheimes)
tags: added: maas s390x
Revision history for this message
Frank Heimes (fheimes) wrote :

According to MM version 4.0/edge incl. a backported fix.
https://github.com/lxc/lxd/issues/8477
https://github.com/lxc/lxd/pull/8478

Changed in maas:
milestone: 3.0.0-beta3 → 3.0.0-beta4
Changed in maas:
milestone: 3.0.0-beta4 → 3.0.0-beta5
Changed in maas:
milestone: 3.0.0-beta5 → 3.0.0-rc1
Changed in maas:
milestone: 3.0.0-rc1 → 3.0.1
Revision history for this message
Frank Heimes (fheimes) wrote :

looks like the above mentioned fix is merged to master

Alberto Donato (ack)
Changed in maas:
status: New → Triaged
importance: Undecided → Medium
Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
status: New → Triaged
importance: Undecided → Medium
Changed in lxd (Ubuntu):
status: New → Fix Released
Revision history for this message
Jerzy Husakowski (jhusakowski) wrote :

Is this issue still reproducible on a recent MAAS (3.2+)?

Changed in maas:
milestone: 3.0.1 → none
status: Triaged → Incomplete
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.