Description of problem: When named-chroot.service is running, named-chroot-setup.service is used to prepare runtime environment and cleanup after it stops. If bind-chroot is uninstalled when service is still running, it will produce errors from triggers. Version-Release number of selected component (if applicable): bind-9.11.3-13.fc27.x86_64 How reproducible: always Steps to Reproduce: 1. dnf install bind-chroot 2. systemctl start named-chroot 3. dnf remove bind-chroot Actual results: Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Running scriptlet: bind-chroot-32:9.11.4-1.fc29.x86_64 1/1 Erasing : bind-chroot-32:9.11.4-1.fc29.x86_64 1/1 warning: directory /var/named/chroot/var/named: remove failed: Device or resource busy warning: directory /var/named/chroot/usr/lib64/bind: remove failed: Device or resource busy warning: directory /var/named/chroot/run/named: remove failed: Device or resource busy warning: directory /var/named/chroot/etc/named: remove failed: Device or resource busy Running scriptlet: bind-chroot-32:9.11.4-1.fc29.x86_64 1/1 Verifying : bind-chroot-32:9.11.4-1.fc29.x86_64 1/1 Removed: bind-chroot-32:9.11.4-1.fc29.x86_64 Expected results: Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Running scriptlet: bind-chroot-32:9.11.4-1.fc29.x86_64 1/1 Erasing : bind-chroot-32:9.11.4-1.fc29.x86_64 1/1 Running scriptlet: bind-chroot-32:9.11.4-1.fc29.x86_64 1/1 Verifying : bind-chroot-32:9.11.4-1.fc29.x86_64 1/1 Removed: bind-chroot-32:9.11.4-1.fc29.x86_64 Additional info: named-chroot-setup.service is never mentioned in triggers. However, systemctl will wait only on explicitly mentioned services. -- Unit named-chroot.service has begun shutting down. Jul 12 16:25:36 srawhide named[3542]: received control channel command 'stop' Jul 12 16:25:36 srawhide named[3542]: shutting down: flushing changes Jul 12 16:25:36 srawhide named[3542]: stopping command channel on 127.0.0.1#953 Jul 12 16:25:36 srawhide named[3542]: stopping command channel on ::1#953 Jul 12 16:25:36 srawhide named[3542]: no longer listening on 127.0.0.1#53 Jul 12 16:25:36 srawhide named[3542]: no longer listening on ::1#53 Jul 12 16:25:36 srawhide named[3542]: exiting Jul 12 16:25:36 srawhide systemd[1]: Stopped Berkeley Internet Name Domain (DNS). -- Subject: Unit named-chroot.service has finished shutting down -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit named-chroot.service has finished shutting down. Jul 12 16:25:36 srawhide systemd[1]: Stopping Set-up/destroy chroot environment for named (DNS)... -- Subject: Unit named-chroot-setup.service has begun shutting down -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit named-chroot-setup.service has begun shutting down. Jul 12 16:25:36 srawhide systemd[1]: Reloading. Jul 12 16:25:36 srawhide systemd[1]: named-chroot-setup.service: Current command vanished from the unit file, execution of the command list won't be resumed. Jul 12 16:25:36 srawhide systemd[1]: Stopped named-chroot-setup.service. -- Subject: Unit named-chroot-setup.service has finished shutting down -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit named-chroot-setup.service has finished shutting down. Note second service was aborted without proper fininalising. I think adding named-chroot-setup.service to shutdown might fix that.
bind-dyndb-ldap-11.1-12.fc27 dnsperf-2.1.0.0-17.fc27 bind-9.11.4-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-c0f12f789e
dhcp-4.3.6-21.fc28 dnsperf-2.1.0.0-17.fc28 bind-dyndb-ldap-11.1-12.fc28 bind-9.11.4-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-be34943e96
bind-9.11.4-1.fc27, bind-dyndb-ldap-11.1-12.fc27, dnsperf-2.1.0.0-17.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-c0f12f789e
bind-9.11.4-1.fc28, bind-dyndb-ldap-11.1-12.fc28, dhcp-4.3.6-21.fc28, dnsperf-2.1.0.0-17.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-be34943e96
bind-9.11.4-1.fc28, bind-dyndb-ldap-11.1-12.fc28, dhcp-4.3.6-21.fc28, dnsperf-2.1.0.0-17.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.
bind-9.11.4-1.fc27, bind-dyndb-ldap-11.1-12.fc27, dnsperf-2.1.0.0-17.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.