As expected I could solve the issue in a test via
flags=(attach_disconnected).

Although I had cases where the issue appeared and others where it never
showed up - didn't find the difference for that yet. Never the less the
fix will help the affected cases and should not break others.

The worst is that I found this to be hiding the actual error message.
In my case where I was seeing it ntp was "actually" complaining about bug 
1737998.
But I think atm most ntp errors might look like the apparmor deny which makes 
this a bit more severe than I thought at first.

Opened an MP for it at [1].

@Martin - do you test Debian as well and if you have apparmor enabled
there does it hit there as well? Just to know if you have a bug I could
post the fix on

@Martin - since I failed to see when it hits and when not - if you can
test from a ppa [2] (or modify the case to have the one line change) it
would be nice if you could confirm the fix. If you happen to see why it
only happens "sometimes" let me know.

[1]: 
https://code.launchpad.net/~paelzer/ubuntu/+source/ntp/+git/ntp/+merge/335147
[2]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3080

** Changed in: ntp (Ubuntu Bionic)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1727202

Title:
  [17.10 regression] AppArmor denial: Failed name lookup - disconnected
  path

Status in ntp package in Ubuntu:
  Triaged
Status in ntp source package in Artful:
  New
Status in ntp source package in Bionic:
  Triaged

Bug description:
  Merely installing and starting ntp.service in Ubuntu 17.10 now causes
  this AppArmor violation:

  audit: type=1400 audit(1508915894.215:25): apparmor="DENIED"
  operation="sendmsg" info="Failed name lookup - disconnected path"
  error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log"
  pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  
  (many times). This hasn't happened in earlier Ubuntu releases yet.

  This was spotted by Cockpit's integration tests, as our "ubuntu-
  stable" image now moved to 17.10 after its release.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ntp 1:4.2.8p10+dfsg-5ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Wed Oct 25 03:19:34 2017
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1727202/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to