Bug 2110858 - Moving unbound-anchor to a separate package left stale systemd units
Summary: Moving unbound-anchor to a separate package left stale systemd units
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: unbound
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Menšík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-26 04:24 UTC by Rob Foehl
Modified: 2022-11-10 22:14 UTC (History)
5 users (show)

Fixed In Version: unbound-1.16.3-2.fc36 unbound-1.16.3-3.fc37
Clone Of:
Environment:
Last Closed: 2022-10-26 17:27:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Rob Foehl 2022-07-26 04:24:17 UTC
Moving unbound-anchor to a separate package resulted in this after an unbound-libs upgrade:

Jul 26 00:00:00 systemd[1]: Starting unbound-anchor.service - update of the root trust anchor for DNSSEC validation in unbound...
Jul 26 00:00:00 systemd[146323]: unbound-anchor.service: Failed to locate executable /usr/sbin/unbound-anchor: No such file or directory
Jul 26 00:00:00 systemd[146323]: unbound-anchor.service: Failed at step EXEC spawning /usr/sbin/unbound-anchor: No such file or directory
Jul 26 00:00:00 systemd[1]: unbound-anchor.service: Main process exited, code=exited, status=203/EXEC
Jul 26 00:00:00 systemd[1]: unbound-anchor.service: Failed with result 'exit-code'.
Jul 26 00:00:00 systemd[1]: Failed to start unbound-anchor.service - update of the root trust anchor for DNSSEC validation in unbound.


The move itself is fine: unbound-libs is only installed here by way of a dependency, isn't actually used, and thus updating the trust anchor was a complete waste of time.  However, the repackaging didn't account for unbound-libs upgrades, leaving at least /etc/systemd/system/timers.target.wants/unbound-anchor.timer behind, and systemd awfully confused.

Comment 1 Petr Menšík 2022-08-19 10:00:22 UTC
Oh. Okay, I think unbound-anchor.timer should be included in %post scriptlet. And also new package unbound-anchor should be installed on upgrade unless supressed by ignoring recommended packages.

Comment 2 Fedora Update System 2022-10-11 12:14:49 UTC
FEDORA-2022-0f353c3ceb has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-0f353c3ceb

Comment 3 Fedora Update System 2022-10-11 12:15:24 UTC
FEDORA-2022-4eafb962d6 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-4eafb962d6

Comment 4 Petr Menšík 2022-10-11 15:00:11 UTC
I am not sure it fixed all combinations, but it should have improved upgrade from version without separate unbound-anchor. There were forgotten trigger in unbound-libs, which should not have been there. That was moved to unbound-anchor, where it belongs.

When I tested it, it reported one line error on upgrading to the new unbound-libs. I am not sure there is a good %systemd_* macro for such condition. It leaves units in deactivated, dead state. Visible by:

$ systemctl list-units unbound-anchor.{service,timer}

It seems enabled link is now properly deactivated on upgrade without the anchor.

Comment 5 Fedora Update System 2022-10-11 15:52:30 UTC
FEDORA-2022-0f353c3ceb has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-0f353c3ceb`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-0f353c3ceb

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2022-10-12 13:01:45 UTC
FEDORA-2022-4eafb962d6 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-4eafb962d6`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-4eafb962d6

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2022-10-26 17:27:41 UTC
FEDORA-2022-4eafb962d6 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2022-11-10 22:14:33 UTC
FEDORA-2022-0f353c3ceb has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.