cannot open 'rpool': no such pool

Bug #1786567 reported by james beedy on 2018-08-10
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Undecided
Unassigned

Bug Description

MAAS version: 2.4.0 (6981-g011e51b-snap)

Enlisted and configured this node, deployment fails with https://paste.ubuntu.com/p/kHM2QTjj7v/

An overhead view:

Machine Summary https://imgur.com/a/uRE8SNB

Interfaces https://imgur.com/a/NwTNiGd

Storage https://imgur.com/a/Gf4Hlxg

Commissioning https://imgur.com/a/kKESVYO

Hardware Tests https://imgur.com/a/aV3PrIV

Logs https://imgur.com/a/wK8gruj

Events https://imgur.com/a/rcHuqRm

Configuration https://imgur.com/a/ZvcYYWY

regiond.log and rackd.log attached

james beedy (jamesbeedy) wrote :
Andres Rodriguez (andreserl) wrote :

Hi James,

Could you please attache the machine's curtin configuration? (maas <user> machine get-curtin-config <system-id> ?

Also, it would seem that you are using ZFS ? if so, ZFS is only supported on the root device. If you are using it in the root device, this could actually be a curtin issue but we would need the storage logs to confirm.

Changed in maas:
status: New → Incomplete
james beedy (jamesbeedy) wrote :

Andres,

Here is the curtin config http://paste.ubuntu.com/p/3GRnbn5sZV/

I had previously tried to use zfsroot on the root device, which is what initially spawned this error. I couldn't get it to go away, so I deleted the node and re-enlisted. The error remains for this node (even though I have not configured zfsroot), even after a delete and re-enlist.

Where are the storage logs?

james beedy (jamesbeedy) wrote :

duplicate of #1770280

james beedy (jamesbeedy) wrote :

After getting the node into rescue mode and using dd to zero out the boot disk, I now get the error https://paste.ubuntu.com/p/V32C9kGs7n/

james beedy (jamesbeedy) wrote :

After wiping the disks in a myriad of ways, deleting, re-enlisting, and re-configuring the node a number of times, I seem to have gotten past the issues I was experiencing here and able to get the node to deploy successfully again.

Launchpad Janitor (janitor) wrote :

[Expired for MAAS because there has been no activity for 60 days.]

Changed in maas:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments