Despite this supposedly having been fixed, I still run into this on Ubuntu 16.04.1 LTS (xenial).
This is caused by the ntp package (which comes installed by default) placing an apparmor profile in `/etc/apparmor.d/usr.sbin.ntpd`. When removing ntp and installing openntpd instead, the apparmor profile is not removed so apparmor enforces restrictions meant for ntp onto openntpd.
The solution is to (1) remove /etc/apparmor.d/usr.sbin.ntpd and (2) reload apparmor (`systemctl reload apparmor.service`). At this point openntpd will install and run without issue.
Despite this supposedly having been fixed, I still run into this on Ubuntu 16.04.1 LTS (xenial).
This is caused by the ntp package (which comes installed by default) placing an apparmor profile in `/etc/apparmor. d/usr.sbin. ntpd`. When removing ntp and installing openntpd instead, the apparmor profile is not removed so apparmor enforces restrictions meant for ntp onto openntpd.
The solution is to (1) remove /etc/apparmor. d/usr.sbin. ntpd and (2) reload apparmor (`systemctl reload apparmor.service`). At this point openntpd will install and run without issue.