Hello, ~dmitrya, thanks for reporting this bug!
AFAICS libvirt's `libvirtd` profile has no rule to send SIGTERM to
`passt`, and passt's own profile has no rule to receive it from
`libvirtd` - I'd say both need an update?
i.e. passt apparmor profile should contain
signal (receive) set=("term") peer=libvirtd
or something similar.
As both libvirt and passt ship their own apparmor profiles, I don't
think apparmor itself is buggy, so I am marking the tasks as invalid.
For the same reason, this may be worth forwarding to (both?) upstreams.
A workaround, you can try killing the leftover passt process after
stopping the VM (for example with `pkill -u $USER -x passt`, or by
killing the specific PID). That should free the forwarded port so the VM
can start again.
** Tags added: server-todo
** Changed in: apparmor
Status: New => Invalid
** Changed in: apparmor (Ubuntu)
Status: New => Invalid
** Changed in: libvirt (Ubuntu)
Status: New => Triaged
** Changed in: passt (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2172904
Title:
pasta is not allowed to receive signals from libvirt due to apparmor
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2172904/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
