Performing verification for jammy. I started a fresh jammy VM, that had an attached 50gb NVMe device:
$ lsblk nvme0n1 259:0 0 46.6G 0 disk nvme1n1 259:1 0 8G 0 disk ├─nvme1n1p1 259:2 0 7.9G 0 part / ├─nvme1n1p14 259:3 0 4M 0 part └─nvme1n1p15 259:4 0 106M 0 part /boot/efi I installed nvme-cli 1.16-3ubuntu0.1 from -updates, and ran: $ sudo nvme id-ctrl /dev/nvme0n1 | grep fguid fguid : $ sudo nvme id-ctrl -o json /dev/nvme0n1 | grep fguid $ The fguid on this VM is set to all zeros, so they are being interpreted as a null byte and we get no output for this field. I then enabled -proposed and installed nvme-cli 1.16-3ubuntu0.2, and re- ran the following: $ sudo nvme id-ctrl /dev/nvme0n1 | grep fguid fguid : 00000000-0000-0000-0000-000000000000 $ sudo nvme id-ctrl -o json /dev/nvme0n1 | grep fguid "fguid" : "00000000-0000-0000-0000-000000000000", Now we are actually getting correct output, and see the actual UUID value being printed. I also ran the following python script that more or less does what maas_wipe.py does: import subprocess output = subprocess.check_output(["nvme", "id-ctrl", "/dev/nvme0n1"]) output = output.decode() It completes successfully under 1.16-3ubuntu0.2, so I think MAAS is good to go now. The package in -proposed fixes the problem. Happy to mark verified for jammy. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051299 Title: nvme-cli: fguid is printed as binary data and causes MAAS to fail erasing NVME disks To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/2051299/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
