Discussed with Frank, while it is not great, CSS >0 are rare. They are more likely
Decision was to add a release note entry as known issue, and drive the fix as SRU. The remaining gap is its usage on the install path, but mainframe users are even more LTS centric. Noble is unaffected, upgrades to it will be fine once SRU fixed and towards the next LTS it will be fine too. If we respin anyway we'd like to have it for sure. But this alone isn't a reason to do so. If nothing happens that makes this a asap-respin-images case I'd ask the security folks doing the original changes to follow up on driving the SRU aspect of this. But while I wsa trying to prep a fix I found that the discussion above was a red herring. This was not "CSS0 vs CSS>0 and the latter fails". This is blocking CSS0 ! See the denial: name="/sys/devices/css0/0.0.0000/0.0.0101/block/dasda/hidden" With that I'm going back to critical until I understand more ** Changed in: apparmor (Ubuntu) Importance: Medium => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2107402 Title: lsblk on IBM z Systems blocked by apparmor in 25.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2107402/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
