Bug 1807994
| Summary: | Fedora IoT 31: Unit fwupd-refresh.service has a bad unit file setting | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | nicolasoliver03 |
| Component: | fwupdate | Assignee: | Orphan Owner <extras-orphan> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 31 | CC: | dennis.schridde, pjones |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | --- | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-11-24 16:10:30 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
This package has changed maintainer in the Fedora. Reassigning to the new maintainer of this component. This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Description of problem: [root@fedora-iot-2 ~]# systemctl status fwupd-refresh.service ● fwupd-refresh.service - Refresh fwupd metadata and update motd Loaded: bad-setting (Reason: Unit fwupd-refresh.service has a bad unit file setting.) Active: inactive (dead) Docs: man:fwupdmgr(1) Feb 27 07:49:32 fedora-iot-2 systemd[1]: /usr/lib/systemd/system/fwupd-refresh.service:17: Neither a valid executable name nor an absolute path: bindir@/fwupdmgr Feb 27 07:49:32 fedora-iot-2 systemd[1]: fwupd-refresh.service: Unit configuration has fatal error, unit will not be started. [root@fedora-iot-2 ~]# systemd-analyze verify fwupd-refresh.service /usr/lib/systemd/system/iscsiuio.service:13: PIDFile= references a path below legacy directory /var/run/, updating /var/run/iscsiuio.pid → /run/iscsiuio.pid; please update the unit file accordingly. /usr/lib/systemd/system/iscsid.service:11: PIDFile= references a path below legacy directory /var/run/, updating /var/run/iscsid.pid → /run/iscsid.pid; please update the unit file accordingly. /usr/lib/systemd/system/fwupd-refresh.service:17: Neither a valid executable name nor an absolute path: bindir@/fwupdmgr fwupd-refresh.service: Unit configuration has fatal error, unit will not be started. Unit fwupd-refresh.service has a bad unit file setting. Version-Release number of selected component (if applicable): [root@fedora-iot-2 ~]# rpm -qa fwupd* fwupd-1.3.7-2.fc31.x86_64 [root@fedora-iot-2 ~]# rpm-ostree status State: idle AutomaticUpdates: disabled Deployments: ● ostree://fedora-iot:fedora/stable/x86_64/iot Version: 31.20200209.0 (2020-02-09T09:57:02Z) BaseCommit: 4beac0ca768cf3d1d0eb90963ed0ac3a0c88af2f2bff958fa84935ec3ff01ec4 GPGSignature: Valid signature by 7D22D5867F2A4236474BF7B850CB390B3C3359C4 LayeredPackages: bzip2 cockpit cockpit-ostree containerd.io docker-ce docker-ce-cli docker-compose expect git nano openvpn udisks2 How reproducible: Boot into the given Fedora IoT compose, the service will fail to start Steps to Reproduce: 1. Boot 2. systemctl status fwupd-refresh.service 3. systemd-analyze verify fwupd-refresh.service Actual results: Unit fwupd-refresh.service has a bad unit file setting. Expected results: Unit fwupd-refresh.service loads and works Additional info: