MAAS

Commissioning fails to run on NVME multipath devices

Bug #1877220 reported by Lee Trager
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Lee Trager
MAAS 2.8.0rc1
2.7
Fix Released
High
Lee Trager
MAAS 2.7.2rc1

Bug Description

Reported on Discourse[1] and fixed in LXD[2]. MAAS needs to pull the latest version of the LXD sources to fix this.

[1] https://discourse.maas.io/t/commissioning-failure-because-sys-class-block-nvme0c0n1-dev-no-such-file-or-directory/1522
[2] https://github.com/lxc/lxd/issues/7313

Related branches

~ltrager/maas:lp1877220_2.7
Alberto Donato: Approve
MAAS Lander: Needs Fixing
Diff: 51 lines (+21/-3)
1 file modified
src/machine-resources/src/machine-resources/Gopkg.lock (+21/-3)
Revision history for this message
Lee Trager (ltrager) wrote :

This just needed an update to the LXD sources which was done on master as part of LP:1878685.

Changed in maas:
milestone: none → 2.8.0rc1
status: In Progress → Fix Committed
Alberto Donato (ack)
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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