Description of problem: Parsec fails to start on boot in Rawhide: systemctl status parsec ● parsec.service - Parsec Service Loaded: loaded (/usr/lib/systemd/system/parsec.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2020-09-29 20:00:36 EDT; 1 months 17 days ago Docs: https://parallaxsecond.github.io/parsec-book/parsec_service/install_parsec_linux.html Process: 786 ExecStart=/usr/libexec/parsec -c /etc/parsec/config.toml (code=exited, status=1/FAILURE) Main PID: 786 (code=exited, status=1/FAILURE) CPU: 60ms Sep 29 20:00:36 localhost.localdomain systemd[1]: parsec.service: Scheduled restart job, restart counter is at 5. Sep 29 20:00:36 localhost.localdomain systemd[1]: Stopped Parsec Service. Sep 29 20:00:36 localhost.localdomain systemd[1]: parsec.service: Start request repeated too quickly. Sep 29 20:00:36 localhost.localdomain systemd[1]: parsec.service: Failed with result 'exit-code'. Sep 29 20:00:36 localhost.localdomain systemd[1]: Failed to start Parsec Service. journalctl: Nov 16 11:41:25 rpi4-4 systemd[1]: parsec.service: Main process exited, code=exited, status=1/FAILURE Nov 16 11:41:25 rpi4-4 systemd[1]: parsec.service: Failed with result 'exit-code'. Nov 16 11:41:25 rpi4-4 systemd[1]: Failed to start Parsec Service. Nov 16 11:41:25 rpi4-4 systemd[1]: parsec.service: Scheduled restart job, restart counter is at 5. Nov 16 11:41:25 rpi4-4 systemd[1]: Stopped Parsec Service. Nov 16 11:41:25 rpi4-4 systemd[1]: parsec.service: Start request repeated too quickly. Nov 16 11:41:25 rpi4-4 systemd[1]: parsec.service: Failed with result 'exit-code'. Nov 16 11:41:25 rpi4-4 systemd[1]: Failed to start Parsec Service. Version-Release number of selected component (if applicable): parsec-0.6.0-1.fc34 OpenQA: https://openqa.fedoraproject.org/tests/722872#
FEDORA-2020-51d32fefde has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-51d32fefde
FEDORA-2020-51d32fefde has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-51d32fefde` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-51d32fefde See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-51d32fefde has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle. Changing version to 34.
FEDORA-2021-1dc9636f7a has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-1dc9636f7a
FEDORA-2021-1dc9636f7a has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-1dc9636f7a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-1dc9636f7a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Proposing as a Final blocker, per criterion "All system services present after installation with one of the release-blocking package sets must start properly, unless they require hardware which is not present." - https://fedoraproject.org/wiki/Fedora_34_Final_Release_Criteria#System_services . IoT is a release blocking image, and the service always fails on IoT boot.
+3 in https://pagure.io/fedora-qa/blocker-review/issue/348 , marking accepted.
FEDORA-2021-1dc9636f7a has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
Confirmed fixed in current IoT tests. Closing.