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 Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2092232 Title: unable to deploy Plucky Puffin due to AppArmor lsblk denials Status in MAAS: Invalid Status in The Ubuntu-power-systems project: Confirmed Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Describe the bug: Deployment fails on Power9 and Power10 nodes when trying with Ubuntu 25.04/Plucky Puffin Actual behavior (what actually happened?): ``` Thu, 19 Dec. 2024 17:38:22 Marking node failed - Node operation 'Deploying' timed out after 30 minutes. Thu, 19 Dec. 2024 17:38:22 Node changed status - From 'Deploying' to 'Failed deployment' Thu, 19 Dec. 2024 17:08:06 Node installation - 'cloudinit' running config-keys_to_console with frequency once-per-instance Thu, 19 Dec. 2024 17:08:06 Node installation - 'cloudinit' running config-power_state_change with frequency once-per-instance Thu, 19 Dec. 2024 17:08:06 Node installation - 'cloudinit' running config-install_hotplug with frequency once-per-instance Thu, 19 Dec. 2024 17:08:06 Node installation - 'cloudinit' running config-ssh_authkey_fingerprints with frequency once-per-instance Thu, 19 Dec. 2024 17:08:06 Node installation - 'cloudinit' running config-final_message with frequency always Thu, 19 Dec. 2024 17:08:06 Rebooting ``` Looking its console, it seems deployment has finished quickly: ``` -----END SSH HOST KEY KEYS----- [ 29.557514] cloud-init[755]: Cloud-init v. 24.4-0ubuntu1 finished at Thu, 19 Dec 2024 17:10:00 +0000. Datasource DataSourceNone. Up 29.55 seconds [ 29.557942] cloud-init[755]: 2024-12-19 17:10:00,978 - cc_final_message.py[WARNING]: Used fallback datasource ... [ 29.563198] cloud-init[755]: +----[SHA256]-----+ Ubuntu Plucky Puffin (development branch) ubuntu hvc0 ubuntu login: ubuntu login: ``` but either way MAAS deployment fails. MAAS version: 3.5.2 Additional context: a) I'm able to deploy the same system, via MAAS, when trying with Jammy/Noble/Oracular b) Also able to deploy with Plucky Puffin .ISO image (also on the same system - P10rain-LPAR09). To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/2092232/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
