Hi, thanks for catching this, and for testing the proposed version of ubuntu-advantage-tools (v32).
We are still a bit baffled by how this escaped our CI, and to be honest, haven't yet been able to reproduce the apparmor DENIED message. Looking at the apparmor profiles involved, we don't see a rule allowing /etc/os-release to be read, Yet it doesn't happen in a jammy test installation, and so far we can't explain why.
Hi, thanks for catching this, and for testing the proposed version of ubuntu- advantage- tools (v32).
We are still a bit baffled by how this escaped our CI, and to be honest, haven't yet been able to reproduce the apparmor DENIED message. Looking at the apparmor profiles involved, we don't see a rule allowing /etc/os-release to be read, Yet it doesn't happen in a jammy test installation, and so far we can't explain why.
Looking at https:/ /cockpit- logs.us- east-1. linodeobjects. com/image- refresh- ubuntu- 2204-6e3c7232- 20240512- 223711/ log.html, looks like you have jammy-proposed enabled at large, and grabbing everything from there, if I understood that correctly. I'll try to reproduce it that way.