Unable to deploy A/X/B i386 with MaaS 2.3.2 (6485) zfs module not found

Bug #1768709 reported by Po-Hsu Lin on 2018-05-03
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Undecided
Unassigned
curtin
Undecided
Unassigned

Bug Description

The attempt to deploy Bionic/Artful/Xenial i386 with MaaS 2.3.2 (6485) will fail with the zfs module issue like in bug 1739761:

curtin: Installation started. (18.1-1-g45564eef-0ubuntu1~16.04.1)
third party drivers not installed or necessary.t
modprobe: FATAL: Module zfs not found in directory /lib/modules/4.13.0-39-genericm
Unexpected error while running command.U
Command: ['modprobe', '--use-blacklist', 'zfs']C
Exit code: 1E
Reason: -R
Stdout: ''S
Stderr: ''S
curtin: Installation failed with exception: Unexpected error while running command.c
Command: ['curtin', 'block-meta', 'custom']C
Exit code: 3E
Reason: -R
Stdout: modprobe: FATAL: Module zfs not found in directory /lib/modules/4.13.0-39-genericS
        Unexpected error while running command.
        Command: ['modprobe', '--use-blacklist', 'zfs']
        Exit code: 1
        Reason: -
        Stdout: ''
        Stderr: ''

Stderr: ''S

Steps:
  1. Go to the MaaS UI, pick a node and set the arch to i386
  2. Deploy Bionic/Artful/Xenial on it (Trusty is the only working release)

Related branches

Po-Hsu Lin (cypressyew) on 2018-05-03
summary: - Unable to deploy Artful i386 with MaaS 2.3.2 (6485)
+ Unable to deploy A/X/B i386 with MaaS 2.3.2 (6485) zfs module not found
Po-Hsu Lin (cypressyew) on 2018-05-03
description: updated
Revision history for this message
Andres Rodriguez (andreserl) wrote :

Hi there,

Zfs is only available on amd64 and not on i386. It sounds like curtin needs not to blacklist this module when executing i386.

Changed in maas:
status: New → Invalid
Ryan Harper (raharper) on 2018-05-03
Changed in curtin:
status: New → Confirmed
Po-Hsu Lin (cypressyew) on 2018-05-11
Changed in curtin:
status: Confirmed → In Progress
Revision history for this message
Ryan Harper (raharper) wrote :

An upstream commit landed for this bug.

To view that commit see the following URL:
https://git.launchpad.net/curtin/commit/?id=5313b9e2

Changed in curtin:
status: In Progress → Fix Committed
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

I can confirm that the i386 deployment is now working with our MaaS 2.3.3-6498, curtin (18.1-17-gae48e86f-0ubuntu1~16.04.1)

Please feel free to close this bug.
Thank you!

Ryan Harper (raharper) on 2018-06-01
Changed in curtin:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers