Custom Storage Silently Failing

Users
1

I’ve been trying to commission a machine with a custom storage layout but, no matter what I do commisioning always fails. My bash script writes the custom storage json just fine and gets marked as “passed”, but the 50-maas-01-commissioning step fails. It doesn’t contain any error output and only shows a correct looking json in the stdout tab(with my extra storage config present). Any ideas on what could be going wrong here?

I’m using ubuntu24 with maas 3.6.0

2

Probably the storage config you provided is not valid. I’d suggest to start simple and try a simple configuration according to the docs

3

I tried copy pasting one of the suggested configs from the tutorial page but get the same error, here’s what i’m currently testing with:

cat > $MAAS_STORAGE_CONFIG_FILE <<'EOF'
{
  "layout": {
    "sda": {
      "type": "disk",
      "ptable": "gpt",
      "boot": true,
      "partitions": [
        {
          "name": "sda1",
          "fs": "vfat",
          "size": "500M",
          "bootable": true
        },
        {
          "name": "sda2",
          "size": "5G",
          "fs": "ext4"
        },
        {
          "name": "sda3",
          "size": "2G",
          "fs": "swap"
        },
        {
          "name": "sda4",
          "size": "120G",
          "fS": "ext4"
        }
      ]
    }
  },
  "mounts": {
    "/": {
      "device": "sda2",
      "options": "noatime"
    },
    "/boot/efi": {
      "device": "sda1"
    },
    "/data": {
      "device": "sda4"
    },
    "none": {
      "device": "sda3"
    }
  }
}
EOF
4

any logs in the regiond?

5

Not seeing anything useful in logs via “journalctl -t maas-rackd -r”. Is there a way to turn up logging levels?

6

check maas-regiond plz

7

journalctl -u snap.maas.pebble.service ended up providing the logs I needed.

Turns out the docs have a typo… One of the “fs” keys uses a capital S.

8

This has been fixed. Sorry for that mistake. Glad you found it.