[Bug 2068526] Re: apparmor blocks using more than one timemaster clock with chrony
This bug was fixed in the package chrony - 4.5-1ubuntu4.1 --- chrony (4.5-1ubuntu4.1) noble; urgency=medium * d/usr.sbin.chronyd: fix the apparmor profile to allow multiple PTP clocks/interfaces (LP: #2068526) -- Andreas Hasenack Tue, 02 Jul 2024 17:22:37 -0300 ** Changed in: chrony (Ubuntu Noble) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068526 Title: apparmor blocks using more than one timemaster clock with chrony To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2068526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068526] Re: apparmor blocks using more than one timemaster clock with chrony
Noble verification # Reproducing the bug ubuntu@n-ptp:~$ apt-cache policy chrony chrony: Installed: 4.5-1ubuntu4 Candidate: 4.5-1ubuntu4 Version table: *** 4.5-1ubuntu4 500 500 http://br.archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status $ sudo timemaster -m -q -f /etc/linuxptp/minimal.conf timemaster[153.210]: process 3251 started: chronyd -n -f /var/run/timemaster/chrony.conf timemaster[153.211]: process 3252 started: ptp4l -l 5 -f /var/run/timemaster/ptp4l.0.conf -S -i enp5s0 timemaster[153.211]: process 3253 started: ptp4l -l 5 -f /var/run/timemaster/ptp4l.1.conf -S -i enp5s0 Fatal error : Could not open socket /var/run/timemaster/chrony.SOCK1 (...) apparmor logs: [Mon Jul 22 19:18:32 2024] audit: type=1400 audit(1721675912.240:148): apparmor="DENIED" operation="mknod" class="file" profile="/usr/sbin/chronyd" name="/run/timemaster/chrony.SOCK1" pid=3251 comm="chronyd" requested_mask="c" denied_mask="c" fsuid=0 ouid=0 # Checking the fix Package from noble-proposed: ubuntu@n-ptp:~$ apt-cache policy chrony chrony: Installed: 4.5-1ubuntu4.1 Candidate: 4.5-1ubuntu4.1 Version table: *** 4.5-1ubuntu4.1 100 100 http://br.archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages 100 /var/lib/dpkg/status 4.5-1ubuntu4 500 500 http://br.archive.ubuntu.com/ubuntu noble/main amd64 Packages This time the timemaster command runs without exiting, and there are no apparmor logs: $ sudo timemaster -m -q -f /etc/linuxptp/minimal.conf timemaster[262.589]: process 4265 started: chronyd -n -f /var/run/timemaster/chrony.conf timemaster[262.589]: process 4266 started: ptp4l -l 5 -f /var/run/timemaster/ptp4l.0.conf -S -i enp5s0 timemaster[262.593]: process 4267 started: ptp4l -l 5 -f /var/run/timemaster/ptp4l.1.conf -S -i enp5s0 As a further check, lsof shows that both socket files are opened by the chronyd process: root@n-ptp:~# lsof -n | grep /run/timemaster/chrony.SOCK chronyd 4265_chrony4u unix 0xa0ebc541f000 0t0 23035 /var/run/timemaster/chrony.SOCK0 type=DGRAM (CONNECTED) chronyd 4265_chrony5u unix 0xa0ebc541f800 0t0 23036 /var/run/timemaster/chrony.SOCK1 type=DGRAM (CONNECTED) Noble verification succeeded. ** Tags removed: verification-needed-noble ** Tags added: verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068526 Title: apparmor blocks using more than one timemaster clock with chrony To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2068526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068526] Re: apparmor blocks using more than one timemaster clock with chrony
autopkgtests are green now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068526 Title: apparmor blocks using more than one timemaster clock with chrony To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2068526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068526] Re: apparmor blocks using more than one timemaster clock with chrony
Hello Kenneth, or anyone else affected, Accepted chrony into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/chrony/4.5-1ubuntu4.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: chrony (Ubuntu Noble) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068526 Title: apparmor blocks using more than one timemaster clock with chrony To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2068526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068526] Re: apparmor blocks using more than one timemaster clock with chrony
This bug was fixed in the package chrony - 4.5-3ubuntu1 --- chrony (4.5-3ubuntu1) oracular; urgency=medium * Merge with Debian unstable (LP: #2064393, LP: #2068526). Remaining changes: - d/chrony.conf: Use ubuntu ntp pool and server. (LP #1744664, #1754358) - Set -x as default if unable to set time (e.g. in containers) (LP #1589780) Chrony is a single service which acts as both NTP client (i.e. syncing the local clock) and NTP server (i.e. providing NTP services to the network), and that is both desired and expected in the vast majority of cases. But in containers syncing the local clock is usually impossible, but this shall not break the providing of NTP services to the network. To some extent this makes chrony's default config more similar to 'ntpd', which complained in syslog but still provided NTP server service in those cases. + debian/chrony.service: allow the service to run without CAP_SYS_TIME + d/control: add new dependency libcap2-bin for capsh (usually installed anyway, but make them explicit to be sure). + d/chrony.default: new option SYNC_IN_CONTAINER to not fall back (Default off) + d/chronyd-starter.sh: wrapper to handle special cases in containers and if CAP_SYS_TIME is missing. Effectively allows running the NTP server in containers on a default installation and avoid failing to sync time (or if allowed to sync, avoid multiple containers fighting over it by accident). + d/install: Make chrony-starter.sh available on install. + d/docs, d/README.container: Provide documentation about the handling of this case. - d/rules, d/chrony.examples: Ship restricted service as an example not installed to the system for use. (See LP #2051028) * Dropped: - d/usr.sbin.chronyd: apparmor fixes (LP: #2032805): + Allow the default UNIX domain socket address to be used by the reflock_sock service in the Apport configuration. + Fix failure to start timemaster due to lack of rw permissions on chrony socket. [In 4.5-2 and 4.5-3] -- Andreas Hasenack Tue, 02 Jul 2024 15:57:20 -0300 ** Changed in: chrony (Ubuntu Oracular) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068526 Title: apparmor blocks using more than one timemaster clock with chrony To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2068526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068526] Re: apparmor blocks using more than one timemaster clock with chrony
** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu/+source/chrony/+git/chrony/+merge/468629 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068526 Title: apparmor blocks using more than one timemaster clock with chrony To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2068526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068526] Re: apparmor blocks using more than one timemaster clock with chrony
** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu/+source/chrony/+git/chrony/+merge/468626 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068526 Title: apparmor blocks using more than one timemaster clock with chrony To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2068526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068526] Re: apparmor blocks using more than one timemaster clock with chrony
** Description changed:
[ Impact ]
- * An explanation of the effects of the bug on users and
+ The chronyd apparmor profile was changed as a fix for bug #2032805 to
+ allow chronyd to read/write a linuxptp timemaster socket:
- * justification for backporting the fix to the stable release.
+ @{run}/timemaster/chrony.SOCK0 rw,
- * In addition, it is helpful, but not required, to include an
-explanation of how the upload fixes this bug.
+ That works, but is limiting, as it allows only one PTP clock/interface
+ to be used. If another one is setup, the other socket will be blocked by
+ apparmor, because its name will be "chrony.SOCK1", and so on.
+
+ The fix is to simply expand the apparmor rule to allow for more socket
+ files:
+
+ @{run}/timemaster/chrony.SOCK[0-9]* rw,
[ Test Plan ]
- * detailed instructions how to reproduce the bug
+ * Launch a VM. For example:
- * these should allow someone who is not familiar with the affected
-package to reproduce the bug and verify that the updated package fixes
-the problem.
+ lxc launch ubuntu-daily:oracular o-ptp --vm
- * if other testing is appropriate to perform before landing this update,
-this should also be described here.
+ * Install chrony and linuxptp in the VM:
+
+ sudo apt update && sudo apt install chrony linuxptp -y
+
+ * stop chrony:
+
+ sudo systemctl stop chrony.service
+
+ * Create a config file for timemaster, replacing the interface name with
+ the one that exists in the VM:
+
+ /etc/linuxptp/minimal.conf:
+ [ptp_domain 0]
+ interfaces enp5s0
+
+ [ptp_domain 127]
+ interfaces enp5s0
+
+ * in one terminal, observe the output of "dmesg -wT | grep timemaster"
+
+ * in another terminal, run this command:
+
+ sudo timemaster -m -q -f /etc/linuxptp/minimal.conf
+
+
+ * In a system with the bug, the command will issue a "Fatal error" like this:
+
+ Fatal error : Could not open socket /var/run/timemaster/chrony.SOCK1
+
+ * At the same time, the system with the bug will also log this line in
+ the "dmesg -wT" terminal:
+
+ [Tue Jul 2 20:08:12 2024] audit: type=1400 audit(1719950892.125:129):
+ apparmor="DENIED" operation="mknod" class="file"
+ profile="/usr/sbin/chronyd" name="/run/timemaster/chrony.SOCK1" pid=1942
+ comm="chronyd" requested_mask="c" denied_mask="c" fsuid=0 ouid=0
+
+ * In a fixed system, there will be no apparmor log in the "dmesg -wT"
+ terminal, and the "timemaster" command will run without errors, and
+ won't exit.
+
[ Where problems could occur ]
- * Think about what the upload changes in the software. Imagine the change is
-wrong or breaks something else: how would this show up?
+ * Think about what the upload changes in the software. Imagine the change is
+ wrong or breaks something else: how would this show up?
- * It is assumed that any SRU candidate patch is well-tested before
-upload and has a low overall risk of regression, but it's important
-to make the effort to think about what ''could'' happen in the
-event of a regression.
+ * It is assumed that any SRU candidate patch is well-tested before
+ upload and has a low overall risk of regression, but it's important
+ to make the effort to think about what ''could'' happen in the
+ event of a regression.
- * This must '''never''' be "None" or "Low", or entirely an argument as to why
-your upload is low risk.
+ * This must '''never''' be "None" or "Low", or entirely an argument as to why
+ your upload is low risk.
- * This both shows the SRU team that the risks have been considered,
-and provides guidance to testers in regression-testing the SRU.
+ * This both shows the SRU team that the risks have been considered,
+ and provides guidance to testers in regression-testing the SRU.
[ Other Info ]
-
- * Anything else you think is useful to include
- * Anticipate questions from users, SRU, +1 maintenance, security teams and
the Technical Board
- * and address these questions in advance
+
+ * Anything else you think is useful to include
+ * Anticipate questions from users, SRU, +1 maintenance, security teams and
the Technical Board
+ * and address these questions in advance
[ Original Description ]
-
- The fix for bug #2032805 allows chronyd to use one PTP clock/interface with
timemaster, but not more than one.
+ The fix for bug #2032805 allows chronyd to use one PTP clock/interface
+ with timemaster, but not more than one.
Steps to reproduce (config must contain valid network interface names):
$ cat > minimal_timemaster.conf
# List two separate interfaces, or two separate domains with the same
interface:
# [ptp_domain 0]
# interfaces ens1f0np0
[ptp_domain 127]
interfaces ens1f0np0 ens1f1np1
$ sudo timemaster -m -q -f minimal_timemaster.conf
timemaster[533042.285]: process 2755518 started: chronyd -n -f
/var/run/timemaster/chrony.conf
timemaster[533042.285]: process 2755520 st
[Bug 2068526] Re: apparmor blocks using more than one timemaster clock with chrony
** Description changed:
- The fix for bug #2032805 allows chronyd to use one PTP clock/interface
- with timemaster, but not more than one.
+ [ Impact ]
+
+ * An explanation of the effects of the bug on users and
+
+ * justification for backporting the fix to the stable release.
+
+ * In addition, it is helpful, but not required, to include an
+explanation of how the upload fixes this bug.
+
+ [ Test Plan ]
+
+ * detailed instructions how to reproduce the bug
+
+ * these should allow someone who is not familiar with the affected
+package to reproduce the bug and verify that the updated package fixes
+the problem.
+
+ * if other testing is appropriate to perform before landing this update,
+this should also be described here.
+
+ [ Where problems could occur ]
+
+ * Think about what the upload changes in the software. Imagine the change is
+wrong or breaks something else: how would this show up?
+
+ * It is assumed that any SRU candidate patch is well-tested before
+upload and has a low overall risk of regression, but it's important
+to make the effort to think about what ''could'' happen in the
+event of a regression.
+
+ * This must '''never''' be "None" or "Low", or entirely an argument as to why
+your upload is low risk.
+
+ * This both shows the SRU team that the risks have been considered,
+and provides guidance to testers in regression-testing the SRU.
+
+ [ Other Info ]
+
+ * Anything else you think is useful to include
+ * Anticipate questions from users, SRU, +1 maintenance, security teams and
the Technical Board
+ * and address these questions in advance
+
+ [ Original Description ]
+
+
+ The fix for bug #2032805 allows chronyd to use one PTP clock/interface with
timemaster, but not more than one.
Steps to reproduce (config must contain valid network interface names):
$ cat > minimal_timemaster.conf
# List two separate interfaces, or two separate domains with the same
interface:
# [ptp_domain 0]
# interfaces ens1f0np0
[ptp_domain 127]
interfaces ens1f0np0 ens1f1np1
-
- $ sudo timemaster -m -q -f minimal_timemaster.conf
- timemaster[533042.285]: process 2755518 started: chronyd -n -f
/var/run/timemaster/chrony.conf
- timemaster[533042.285]: process 2755520 started: phc2sys -l 5 -a -r -R 1.00
-z /var/run/timemaster/ptp4l.0.socket -t [127:ens1f0np0] -n 127 -E
refclock_sock --refclock_sock_address /var/run/timemaster/chrony.SOCK0
- timemaster[533042.286]: process 2755522 started: phc2sys -l 5 -a -r -R 1.00
-z /var/run/timemaster/ptp4l.1.socket -t [127:ens1f1np1] -n 127 -E
refclock_sock --refclock_sock_address /var/run/timemaster/chrony.SOCK1
+ $ sudo timemaster -m -q -f minimal_timemaster.conf
+ timemaster[533042.285]: process 2755518 started: chronyd -n -f
/var/run/timemaster/chrony.conf
+ timemaster[533042.285]: process 2755520 started: phc2sys -l 5 -a -r -R 1.00
-z /var/run/timemaster/ptp4l.0.socket -t [127:ens1f0np0] -n 127 -E
refclock_sock --refclock_sock_address /var/run/timemaster/chrony.SOCK0
+ timemaster[533042.286]: process 2755522 started: phc2sys -l 5 -a -r -R 1.00
-z /var/run/timemaster/ptp4l.1.socket -t [127:ens1f1np1] -n 127 -E
refclock_sock --refclock_sock_address /var/run/timemaster/chrony.SOCK1
Fatal error : Could not open socket /var/run/timemaster/chrony.SOCK1
...
-
Quickfix:
sudo sed -i 's|@{run}/timemaster/chrony.SOCK0
rw,|@{run}/timemaster/chrony.SOCK[0-9]* rw,|' /etc/apparmor.d/usr.sbin.chronyd
sudo systemctl reload apparmor
Expected output:
The timemaster command continues to run until pressing CTRL+C
-
$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu 24.04 LTS
Release: 24.04
chrony:
- Installed: 4.5-1ubuntu4
- Candidate: 4.5-1ubuntu4
+ Installed: 4.5-1ubuntu4
+ Candidate: 4.5-1ubuntu4
linuxptp:
- Installed: 4.0-1ubuntu1
- Candidate: 4.0-1ubuntu1
+ Installed: 4.0-1ubuntu1
+ Candidate: 4.0-1ubuntu1
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linuxptp 4.0-1ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: tsoffload linkout
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Jun 5 21:53:26 2024
Dependencies:
- gcc-14-base 14-20240412-0ubuntu1
- libc6 2.39-0ubuntu8.2
- libgcc-s1 14-20240412-0ubuntu1
- libidn2-0 2.3.7-2build1
- libunistring5 1.1-2build1
+ gcc-14-base 14-20240412-0ubuntu1
+ libc6 2.39-0ubuntu8.2
+ libgcc-s1 14-20240412-0ubuntu1
+ libidn2-0 2.3.7-2build1
+ libunistring5 1.1-2build1
InstallationDate: Installed on 2024-05-14 (22 days ago)
InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Release amd64
(20240423)
ProcEnviron:
- LANG=en_US.UTF-8
- PATH=(custom, no user)
- SHELL=/bin/bash
- TERM=xterm-256color
- XDG_RUNTIME_DIR=
+ LANG=en_US.UTF-8
+ PATH=(custom, no user)
+ SHELL=/bin/bash
+ TERM=xterm-2
[Bug 2068526] Re: apparmor blocks using more than one timemaster clock with chrony
I don't think linuxptp is at fault here, so marking its task as invalid. ** Also affects: chrony (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linuxptp (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: chrony (Ubuntu Oracular) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Also affects: linuxptp (Ubuntu Oracular) Importance: Undecided Status: New ** Changed in: linuxptp (Ubuntu Noble) Status: New => Invalid ** Changed in: linuxptp (Ubuntu Oracular) 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/2068526 Title: apparmor blocks using more than one timemaster clock with chrony To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2068526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068526] Re: apparmor blocks using more than one timemaster clock with chrony
** Changed in: chrony (Ubuntu) Status: Triaged => In Progress ** Changed in: chrony (Ubuntu) Assignee: (unassigned) => Andreas Hasenack (ahasenack) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068526 Title: apparmor blocks using more than one timemaster clock with chrony To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2068526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068526] Re: apparmor blocks using more than one timemaster clock with chrony
That is awesome, thanks Vincent. We will pick it up in the subsequent merge of chrony then. ** Tags removed: server-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068526 Title: apparmor blocks using more than one timemaster clock with chrony To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2068526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068526] Re: apparmor blocks using more than one timemaster clock with chrony
Hi there, This seems like an appropriate change to me. If nobody object, I'm going to apply this on the Debian side in the next few days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068526 Title: apparmor blocks using more than one timemaster clock with chrony To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2068526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068526] Re: apparmor blocks using more than one timemaster clock with chrony
Thanks! I added this to the server team work queues. ** Changed in: chrony (Ubuntu) Status: New => Triaged ** Tags added: server-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068526 Title: apparmor blocks using more than one timemaster clock with chrony To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2068526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
