Comment 16 for bug 1739761

Revision history for this message
Ryan Harper (raharper) wrote : Re: [Bug 1739761] Re: Unable to deploy Precise on MaaS 2.3.0 (6434)

On Thu, Apr 26, 2018 at 9:25 PM, Scott Moser <email address hidden> wrote:
> We really probably should make it so that the modprobe is not fatal.
> Obviously if you're trying to install zfs it would be fatal, but otherwise
> we should go on.

When curtin starts, it wants to find existing filesystems and devices, and then
be able to wipe them so as to not interfere later.

If we don't have zfs module, we won't be able to clear it; That may
be OK but could impact data not meant to be wiped.

Further, if after rebooting into the target OS, if zfs module loads there
it could impact the storage configuration.

Replace bcache or md with zfs and you know we've seen situations where
these devices take over due to hidden metadata found later.

> The summary is all current initramfs for v3 images have zfs except
> precise and trusty.
>
> modprobe could fail for another reason. but it looks like at least
> 'zfs.ko' is present.

I suspect there's no bug here in curtin or maas images; possibly
out-of-date images
on the maas node?