While I see the non-crit "other" issue with opening its own binary I can
not confirm the disconnected path issue in a current xenial guest.
Since we knew this appears when trigging the running service to emit an error
message I tried to force such an error message. I knew on later releases I
could do so by e.g. spawning another virtual interface to bind on by starting a
KVM guest (ntp would try to bind on that but fails).
On Xenial I see the error messages without any apparmor related issue.
While I don't know what is different on bug 1475019 (maybe ntp was
manually namespaced on that setup) this bug here "as reported" is a
regression in 17.10.
** Changed in: ntp (Ubuntu Xenial)
Status: New => Invalid
** Changed in: ntp (Ubuntu Zesty)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727202
Title:
[17.10 regression] AppArmor ntp denial: Failed name lookup -
disconnected path
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1727202/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
