[Bug 2125758] [NEW] autoinstall ignores storage section in the cloud-init yaml

Peter V. Saveliev 2125758 at bugs.launchpad.net
Fri Sep 26 11:59:04 UTC 2025


Public bug reported:

The image used: `ubuntu-24.04.3-live-server-amd64.iso`

It doesn't matter what I provide in the `storage` section of the
autoinstall yaml, it never gets installed on the nvme disk:


```
$ lsblk -l
NAME    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda       8:0    0   1.7T  0 disk
sdb       8:16   0   1.7T  0 disk
sdc       8:32   0  18.2T  0 disk
sdd       8:48   0  18.2T  0 disk
sdd1      8:49   0     1G  0 part /boot/efi
sdd2      8:50   0  18.2T  0 part /
sde       8:64   0  18.2T  0 disk
sdf       8:80   0  18.2T  0 disk
nvme0n1 259:1    0 447.1G  0 disk
```

user-data yaml:
```
[…]
autoinstall:
  version: 1
  […]
  storage:
    config:
    - transport: pcie
      preserve: true
      id: nvme-controller-nvme0
      type: nvme_controller
    - ptable: gpt
      nvme_controller: nvme-controller-nvme0
      match:
        path: /dev/nvme0n1
      wipe: superblock-recursive
      preserve: false
      name: ''
      grub_device: false
      id: disk-nvme0n1
      type: disk
    - device: disk-nvme0n1
      size: 1G
      wipe: superblock
      flag: boot
      number: 1
      preserve: false
      grub_device: true
      id: partition-0
      type: partition
    - fstype: fat32
      volume: partition-0
      preserve: false
      id: format-0
      type: format
    - device: disk-nvme0n1
      size: -1
      wipe: superblock
      number: 2
      preserve: false
      grub_device: false
      id: partition-1
      type: partition
    - fstype: ext4
      volume: partition-1
      preserve: false
      id: format-1
      type: format
    - path: /
      device: format-1
      id: mount-1
      type: mount
    - path: /boot/efi
      device: format-0
      id: mount-0
      type: mount
```

I have tried to match:

* exact serial
* path

When I put there:

```
  […]
  interactive-sessions:
    - storage
```

Then it works after I manually choose the nvme disk. It's ok as a short-
term workaround, but not as the solution.

** Affects: subiquity (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to subiquity in Ubuntu.
https://bugs.launchpad.net/bugs/2125758

Title:
  autoinstall ignores storage section in the cloud-init yaml

Status in subiquity package in Ubuntu:
  New

Bug description:
  The image used: `ubuntu-24.04.3-live-server-amd64.iso`

  It doesn't matter what I provide in the `storage` section of the
  autoinstall yaml, it never gets installed on the nvme disk:

  
  ```
  $ lsblk -l
  NAME    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
  sda       8:0    0   1.7T  0 disk
  sdb       8:16   0   1.7T  0 disk
  sdc       8:32   0  18.2T  0 disk
  sdd       8:48   0  18.2T  0 disk
  sdd1      8:49   0     1G  0 part /boot/efi
  sdd2      8:50   0  18.2T  0 part /
  sde       8:64   0  18.2T  0 disk
  sdf       8:80   0  18.2T  0 disk
  nvme0n1 259:1    0 447.1G  0 disk
  ```

  user-data yaml:
  ```
  […]
  autoinstall:
    version: 1
    […]
    storage:
      config:
      - transport: pcie
        preserve: true
        id: nvme-controller-nvme0
        type: nvme_controller
      - ptable: gpt
        nvme_controller: nvme-controller-nvme0
        match:
          path: /dev/nvme0n1
        wipe: superblock-recursive
        preserve: false
        name: ''
        grub_device: false
        id: disk-nvme0n1
        type: disk
      - device: disk-nvme0n1
        size: 1G
        wipe: superblock
        flag: boot
        number: 1
        preserve: false
        grub_device: true
        id: partition-0
        type: partition
      - fstype: fat32
        volume: partition-0
        preserve: false
        id: format-0
        type: format
      - device: disk-nvme0n1
        size: -1
        wipe: superblock
        number: 2
        preserve: false
        grub_device: false
        id: partition-1
        type: partition
      - fstype: ext4
        volume: partition-1
        preserve: false
        id: format-1
        type: format
      - path: /
        device: format-1
        id: mount-1
        type: mount
      - path: /boot/efi
        device: format-0
        id: mount-0
        type: mount
  ```

  I have tried to match:

  * exact serial
  * path

  When I put there:

  ```
    […]
    interactive-sessions:
      - storage
  ```

  Then it works after I manually choose the nvme disk. It's ok as a
  short-term workaround, but not as the solution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2125758/+subscriptions




More information about the foundations-bugs mailing list