| Summary: | qcow image: journald service is not running when virtual machine runs in libvirt (KVM) | ||
|---|---|---|---|
| Product: | Red Hat Storage Console | Reporter: | Martin Bukatovic <mbukatov> |
| Component: | distribution | Assignee: | Timothy Asir <tjeyasin> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | sds-qe-bugs |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2 | CC: | nthomas, sankarshan |
| Target Milestone: | --- | ||
| Target Release: | 2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=510204 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-11-19 05:33:21 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: | |
This is fixed, patch pushed Checking with: rhscon-appliance-0.3-8 And I see that systemd-journald service is up and running after initial boot of virtual machine in both libvirt and openstack based environment. |
Description of problem ====================== When I import rhscon 2.0 qcow2 image into libvirt on rhel 7 host machine as described in our documentation[1], systemd-journald service is not running. [1] section "3.2. Red Hat Storage Console Qcow Installation" of "Red Hat Storage Console 2.0 Quick Start Guide" Version-Release =============== rhscon-appliance-0.3-7.x86_64.qcow2 How reproducible ================ 100 % Steps to Reproduce ================== 1. Download the rhscon 2.0 qcow image into /var/lib/libvirt/images on rhel 7 libvirt host machine. 2. Following rhscon quick start guide[1], do: 2.1 Set password for root via virt-customize 2.2 Disable cloud-init service via guestfish 2.3 Import the image into libvirt 3. Login as a root and check if httpd service is running Actual results ============== ~~~ # systemctl status systemd-journald ● systemd-journald.service - Journal Service Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static; vendor preset: disabled) Active: failed (Result: start-limit) since Fri 2016-08-19 08:35:20 EDT; 46min ago Docs: man:systemd-journald.service(8) man:journald.conf(5) Main PID: 381 (code=exited, status=1/FAILURE) Status: "Shutting down..." ~~~ Expected results ================ Journald service should be up and running after the 1st boot of imported virtual machine. Additional info =============== When the journald service is restarted manually, it starts with success. Related section from dmesg log: ~~~ # dmesg | grep -i journal [ 1.217047] systemd[1]: Listening on Journal Socket. [ 1.217059] systemd[1]: Starting Journal Socket. [ 1.218729] systemd[1]: Starting Journal Service... [ 1.257530] systemd[1]: Started Journal Service. [ 2.119263] systemd-journald[96]: Received SIGTERM from PID 1 (systemd). [ 3.102066] systemd[1]: systemd-journald.service has no holdoff time, scheduling restart. [ 3.124746] systemd[1]: Starting Journal Service... [ 3.181713] systemd-journald[344]: Failed to get machine id: No such file or directory [ 3.192091] systemd[1]: systemd-journald.service: main process exited, code=exited, status=1/FAILURE [ 3.192844] systemd[1]: Failed to start Journal Service. [ 3.194850] systemd[1]: Dependency failed for Flush Journal to Persistent Storage. [ 3.198883] systemd[1]: Job systemd-journal-flush.service/start failed with result 'dependency'. [ 3.198917] systemd[1]: Unit systemd-journald.service entered failed state. [ 3.198965] systemd[1]: systemd-journald.service failed. [ 3.199102] systemd[1]: systemd-journald.service has no holdoff time, scheduling restart. [ 3.204269] systemd[1]: Starting Journal Service... [ 3.218918] systemd-journald[365]: Failed to get machine id: No such file or directory [ 3.222585] systemd[1]: systemd-journald.service: main process exited, code=exited, status=1/FAILURE [ 3.225569] systemd[1]: Failed to start Journal Service. [ 3.228489] systemd[1]: Dependency failed for Flush Journal to Persistent Storage. [ 3.228802] systemd[1]: Job systemd-journal-flush.service/start failed with result 'dependency'. [ 3.228827] systemd[1]: Unit systemd-journald.service entered failed state. [ 3.228856] systemd[1]: systemd-journald.service failed. [ 3.228967] systemd[1]: systemd-journald.service has no holdoff time, scheduling restart. [ 3.230084] systemd[1]: Starting Journal Service... [ 3.249493] systemd-journald[371]: Failed to get machine id: No such file or directory [ 3.252814] systemd[1]: systemd-journald.service: main process exited, code=exited, status=1/FAILURE [ 3.253525] systemd[1]: Failed to start Journal Service. [ 3.256373] systemd[1]: Dependency failed for Flush Journal to Persistent Storage. [ 3.265281] systemd[1]: Job systemd-journal-flush.service/start failed with result 'dependency'. [ 3.265316] systemd[1]: Unit systemd-journald.service entered failed state. [ 3.265359] systemd[1]: systemd-journald.service failed. [ 3.267086] systemd[1]: systemd-journald.service has no holdoff time, scheduling restart. [ 3.274044] systemd[1]: Starting Journal Service... [ 3.282275] systemd-journald[379]: Failed to get machine id: No such file or directory [ 3.283082] systemd[1]: systemd-journald.service: main process exited, code=exited, status=1/FAILURE [ 3.283755] systemd[1]: Failed to start Journal Service. [ 3.284110] systemd[1]: Dependency failed for Flush Journal to Persistent Storage. [ 3.284469] systemd[1]: Job systemd-journal-flush.service/start failed with result 'dependency'. [ 3.284493] systemd[1]: Unit systemd-journald.service entered failed state. [ 3.284528] systemd[1]: systemd-journald.service failed. [ 3.284650] systemd[1]: systemd-journald.service has no holdoff time, scheduling restart. [ 3.285678] systemd[1]: Starting Journal Service... [ 3.288798] systemd-journald[381]: Failed to get machine id: No such file or directory [ 3.289543] systemd[1]: systemd-journald.service: main process exited, code=exited, status=1/FAILURE [ 3.290090] systemd[1]: Failed to start Journal Service. [ 3.290373] systemd[1]: Dependency failed for Flush Journal to Persistent Storage. [ 3.291316] systemd[1]: Job systemd-journal-flush.service/start failed with result 'dependency'. [ 3.291339] systemd[1]: Unit systemd-journald.service entered failed state. [ 3.291375] systemd[1]: systemd-journald.service failed. [ 3.291490] systemd[1]: systemd-journald.service has no holdoff time, scheduling restart. [ 3.291702] systemd[1]: start request repeated too quickly for systemd-journald.service [ 3.291754] systemd[1]: Failed to start Journal Service. [ 3.292680] systemd[1]: Dependency failed for Flush Journal to Persistent Storage. [ 3.294800] systemd[1]: Job systemd-journal-flush.service/start failed with result 'dependency'. [ 3.294810] systemd[1]: Unit systemd-journald.service entered failed state. [ 3.294815] systemd[1]: systemd-journald.service failed. [ 3.296063] systemd[1]: start request repeated too quickly for systemd-journald.service [ 3.296202] systemd[1]: Failed to start Journal Service. [ 3.297295] systemd-tmpfiles[362]: [/usr/lib/tmpfiles.d/systemd.conf:26] Failed to replace specifiers: /run/log/journal/%m [ 3.298906] systemd-tmpfiles[362]: [/usr/lib/tmpfiles.d/systemd.conf:28] Failed to replace specifiers: /run/log/journal/%m [ 3.301300] systemd-tmpfiles[362]: [/usr/lib/tmpfiles.d/systemd.conf:29] Failed to replace specifiers: /run/log/journal/%m [ 3.302876] systemd-tmpfiles[362]: [/usr/lib/tmpfiles.d/systemd.conf:32] Failed to replace specifiers: /var/log/journal/%m [ 3.304399] systemd-tmpfiles[362]: [/usr/lib/tmpfiles.d/systemd.conf:34] Failed to replace specifiers: /var/log/journal/%m [ 3.307705] systemd[1]: Unit systemd-journald.socket entered failed state. [ 3.307717] systemd[1]: systemd-journald.service failed. [ 3.308307] systemd-tmpfiles[362]: [/usr/lib/tmpfiles.d/systemd.conf:35] Failed to replace specifiers: /var/log/journal/%m [ 4.198475] systemd[1]: Starting Rebuild Journal Catalog... [ 4.235014] systemd[1]: Started Rebuild Journal Catalog. [ 4.322413] systemd-tmpfiles[482]: [/usr/lib/tmpfiles.d/systemd.conf:26] Failed to replace specifiers: /run/log/journal/%m [ 4.322794] systemd-tmpfiles[482]: [/usr/lib/tmpfiles.d/systemd.conf:28] Failed to replace specifiers: /run/log/journal/%m [ 4.323133] systemd-tmpfiles[482]: [/usr/lib/tmpfiles.d/systemd.conf:29] Failed to replace specifiers: /run/log/journal/%m [ 4.323549] systemd-tmpfiles[482]: [/usr/lib/tmpfiles.d/systemd.conf:32] Failed to replace specifiers: /var/log/journal/%m [ 4.323832] systemd-tmpfiles[482]: [/usr/lib/tmpfiles.d/systemd.conf:34] Failed to replace specifiers: /var/log/journal/%m [ 4.324144] systemd-tmpfiles[482]: [/usr/lib/tmpfiles.d/systemd.conf:35] Failed to replace specifiers: /var/log/journal/%m ~~~