** No longer affects: linux (Ubuntu)
** Changed in: ubuntu-power-systems
Status: Confirmed => Fix Released
--
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 Pluck
** Changed in: linux (Ubuntu)
Milestone: ubuntu-25.04 => None
--
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
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_networ
@patricia that one should be fixed by
https://bugs.launchpad.net/maas/+bug/2104530 . The hotfix will be rolled
out to TOR3 tomorrow.
--
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:
unab
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
** Summary changed:
- not able to deploy Plucky Puffin
+ unable to deploy Plucky Puffin due to AppArmor lsblk denials
--
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 P
