Many thanks for checking it Jacopo. The issue mentioned on comment #9, is only happening with virtualized nodes, qemu/kvm and PowerVM LPARs. We're able to get the proper lsblk output when running from a Power9 bare metal with Plucky (upgraded from Oracular -> Plucky)**.
But regarding the original bug description - Plucky still fails to deploy via MAAS on arm64 and amd64, same as mentioned on comment #3 - I was rechecking it, able to deploy 4 nodes with Oracular and they all fail when trying to deploy Plucky with: Thu, 03 Apr. 2025 18:57:21 Marking node failed - Node operation 'Deploying' timed out after 30 minutes. ... Thu, 03 Apr. 2025 18:24:48 Node installation - 'cloudinit' running config-ssh_authkey_fingerprints with frequency once-per-instance Thu, 03 Apr. 2025 18:24:48 Rebooting ** `lsblk` output from P9 bare metal: patricia@p9bm-b:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 1.8T 0 disk ├─sda1 8:1 0 8M 0 part ├─sda2 8:2 0 2G 0 part /boot └─sda3 8:3 0 1.8T 0 part └─ubuntu--vg-ubuntu--lv 252:0 0 100G 0 lvm / sr0 11:0 1 1.5G 0 rom (There's also an issue installing Plucky (.ISO) on Power9 bare metal: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2104297 , but this is a separate issue). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2092232 Title: unable to deploy Plucky Puffin due to AppArmor lsblk denials To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/2092232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
