No, no I didn't. Corrected that now. On 31/12/15 01:49, Pat Riehecky wrote: > Hi Steven, > > Thanks for getting this filed upstream! > > Did you mean to set the EL Version with the bug to 7.4 rather than 7.2? > > Pat > > On 12/29/2015 09:42 PM, Steven Haigh wrote: >> Just to follow up on this, it seems that CentOS has the same problem. >> >> The change commit that broke this is: >> https://git.centos.org/blobdiff/!rpms!bind.git/d56ed2d3a2736a07a09c268f3b2607cca8f1b6ca/SOURCES!named-chroot.service >> >> >> Have lodged this in RH bugzilla: >> https://bugzilla.redhat.com/show_bug.cgi?id=1294731 >> >> -- >> Steven Haigh >> >> Email: [log in to unmask] >> Web: https://www.crc.id.au >> Phone: (03) 9001 6090 - 0412 935 897 >> >> On 23/12/2015 1:27 PM, Steven Haigh wrote: >>> Hi all, >>> >>> Just updated to the latest sl-security-rolling and noticed that the >>> named systemd stuff failed on the chroot setup. >>> >>> The faulty systemd unit seems to be: >>> /usr/lib/systemd/system/named-chroot.service >>> >>> It does a sanity check - but doesn't make it relative to the chroot: >>> ExecStartPre=/bin/bash -c 'if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; >>> then /usr/sbin/named-checkconf -z /etc/named.conf; else echo "Checking >>> of zone files is disabled"; fi' >>> >>> If you add the chroot directive in there (which it probably should have >>> anyway), then all works: >>> ExecStartPre=/bin/bash -c 'if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; >>> then /usr/sbin/named-checkconf -z -t /var/named/chroot /etc/named.conf; >>> else echo "Checking of zone files is disabled"; fi' >>> >>> Can anyone verify this - and if needed upstream this bug? >>> -- Steven Haigh Email: [log in to unmask] Web: https://www.crc.id.au Phone: (03) 9001 6090 - 0412 935 897