Bug 1434619
| Summary: | systemd-vconsole-setup.service fails to start on F26 Alpha base cloud image | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mike Ruckman <mruckman> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 26 | CC: | dustymabe, gmarr, jkurik, johannbg, lnykryn, mruckman, msekleta, muadda, niko.kortstrom, robatino, ssahani, s, systemd-maint, zbyszek |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | AcceptedBlocker | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-05-25 00:53:51 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1349188 | ||
|
Description
Mike Ruckman
2017-03-21 23:56:15 UTC
With the latest RC1.2 [0], I see the same. UNIT LOAD ACTIVE SUB DESCRIPTION ------------------------------------------------------------------- ● dnf-makecache.service loaded failed failed dnf makecache ● systemd-vconsole-setup.service loaded failed failed Setup Virtual Console [0] https://kojipkgs.fedoraproject.org/compose/26/Fedora-26-20170321.1/compose/CloudImages/x86_64/images/Fedora-Cloud-Base-26_Alpha-1.2.x86_64.qcow2 Proposed as a Blocker for 26-final by Fedora user roshi using the blocker tracking app because: Final System Services 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." A few more notes: We have had this problem in the past and it didn't get much attention. https://bugzilla.redhat.com/show_bug.cgi?id=1272686 I guess the difference now is that plymouth is no longer masking the failure and we are seeing it when we run `systemctl --failed`. Here is some journal output from the service during boot: Mar 22 15:18:21 localhost systemd[1]: Starting Setup Virtual Console... Mar 22 15:18:21 localhost systemd-vconsole-setup[591]: KD_FONT_OP_GET failed while trying to get the font metadata: Invalid argument Mar 22 15:18:21 localhost systemd-vconsole-setup[591]: Fonts will not be copied to remaining consoles Mar 22 15:18:21 localhost systemd[1]: Started Setup Virtual Console. Mar 22 15:18:22 localhost.localdomain systemd-vconsole-setup[626]: /usr/bin/setfont failed with error code 1. Mar 22 15:18:22 localhost.localdomain systemd[1]: systemd-vconsole-setup.service: Main process exited, code=exited, status=1/FAILURE Mar 22 15:18:22 localhost.localdomain systemd[1]: Failed to start Setup Virtual Console. Mar 22 15:18:22 localhost.localdomain systemd[1]: systemd-vconsole-setup.service: Unit entered failed state. Mar 22 15:18:22 localhost.localdomain systemd[1]: systemd-vconsole-setup.service: Failed with result 'exit-code'. ok that journal output was from a fedora atomic host.. The journal output from a fedora cloud base image is just a little different: ``` [root@cloudhost ~]# journalctl -u systemd-vconsole-setup -- Logs begin at Wed 2017-03-22 15:33:22 UTC, end at Wed 2017-03-22 15:38:28 UTC. -- Mar 22 15:33:23 localhost systemd[1]: Starting Setup Virtual Console... Mar 22 15:33:23 localhost systemd[1]: Started Setup Virtual Console. Mar 22 15:33:24 localhost.localdomain systemd-vconsole-setup[319]: setfont: putfont: 512,8x16: failed: -1 Mar 22 15:33:24 localhost.localdomain systemd-vconsole-setup[319]: putfont: PIO_FONT: Invalid argument Mar 22 15:33:24 localhost.localdomain systemd-vconsole-setup[319]: /usr/bin/setfont failed with error code 71. Mar 22 15:33:24 localhost.localdomain systemd-vconsole-setup[319]: Setting source virtual console failed, ignoring remaining ones Mar 22 15:33:24 localhost.localdomain systemd[1]: systemd-vconsole-setup.service: Main process exited, code=exited, status=1/FAILURE Mar 22 15:33:24 localhost.localdomain systemd[1]: Failed to start Setup Virtual Console. Mar 22 15:33:24 localhost.localdomain systemd[1]: systemd-vconsole-setup.service: Unit entered failed state. Mar 22 15:33:24 localhost.localdomain systemd[1]: systemd-vconsole-setup.service: Failed with result 'exit-code'. ``` Discussed during the 2017-03-27 blocker review meeting: [1] The decision was made to classify this bug as an AcceptedBlocker was made as it violates the following Final criteria: "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." [1] https://meetbot.fedoraproject.org/fedora-blocker-review/2017-03-27/f26-blocker-review.2017-03-27-16.01.txt can we get someone from systemd to take a look at this one? *** This bug has been marked as a duplicate of bug 1272686 *** This bug has not been accepted on the Prioritized list as it is already on the list of Accepted Blockers. |