This bug was fixed in the package apparmor - 4.1.0~beta5-0ubuntu13
---------------
apparmor (4.1.0~beta5-0ubuntu13) plucky; urgency=medium
* Rename and edit patch to fix lsblk denials on networked file systems
(LP: #2092232):
- d/p/u/lsblk_hyper_v_fixup.patch ->
d/p/u/lsblk_network_disk_fixup.patch
* Add patch to fix kernel feature search with substrings (LP: #2105986):
- d/p/u/libapparmor-feature-match-prefixes.patch
- d/p/u/libapparmor-bump-patch-version-for-features-prefix.patch
* Add patch to align aa-notify userns_special_profiles default to config
default (LP: #2106174):
- d/p/u/utils-add-unprivileged_userns-to-aa-notify-list.patch
* Add patches for aa-notify default config to avoid suggesting
capabilities addition for unprivileged_userns profile (LP: #2106177):
- d/p/u/aa-notify-dont-merge-configs-with-confdir.patch
- d/p/u/aa-notify-userns-filtering.patch
-- Ryan Lee <ryan....@canonical.com> Wed, 02 Apr 2025 11:01:53 -0700
** Changed in: apparmor (Ubuntu)
Status: New => Fix Released
--
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:
Fix Released
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
