| Summary: | qcow image: httpd 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: | low | 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:34:18 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 issue is fixed, patch send Checking with: rhscon-appliance-0.3-8 And I see that httpd 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], httpd 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 2. Login as a root and check if httpd service is running Actual results ============== ~~~ # systemctl status httpd ● httpd.service - The Apache HTTP Server Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Fri 2016-08-19 08:36:18 EDT; 45min ago Docs: man:httpd(8) man:apachectl(8) Main PID: 5671 (code=exited, status=1/FAILURE) ~~~ Looking further, I see (via journalctl) in the logs: ~~~ Aug 19 09:35:18 dhcp-127-72.lab.eng.brq.redhat.com systemd[1]: Starting The Apache HTTP Server... Aug 19 09:35:18 dhcp-127-72.lab.eng.brq.redhat.com systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE Aug 19 09:35:18 dhcp-127-72.lab.eng.brq.redhat.com systemd[1]: httpd.service: control process exited, code=exited status=1 Aug 19 09:35:18 dhcp-127-72.lab.eng.brq.redhat.com systemd[1]: Failed to start The Apache HTTP Server. Aug 19 09:35:18 dhcp-127-72.lab.eng.brq.redhat.com systemd[1]: Unit httpd.service entered failed state. Aug 19 09:35:18 dhcp-127-72.lab.eng.brq.redhat.com systemd[1]: httpd.service failed. ~~~ Expected results ================ Apache service should be up and running after the 1st boot of imported virtual machine. Additional info =============== When the apache service is restarted manually, it starts with success.