Bug 1417697
| Summary: | Unable start gnocchi-api service via systemd as a stand-alone service | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Attila Fazekas <afazekas> |
| Component: | openstack-gnocchi | Assignee: | Pradeep Kilambi <pkilambi> |
| Status: | CLOSED ERRATA | QA Contact: | Sasha Smolyak <ssmolyak> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 10.0 (Newton) | CC: | apevec, jschluet, lhh, mlopes, nlevinki, pkilambi |
| Target Milestone: | z2 | Keywords: | Triaged, ZStream |
| Target Release: | 10.0 (Newton) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-gnocchi-3.0.4-2.el7ost | Doc Type: | Bug Fix |
| Doc Text: |
Cause: gnocchi-api standalone script does not start correctly
Consequence: Due to a bug in systemd service script, gnocchi api stand alone script fails to start. Though note that its recommended that gnocchi api is used under apache wsgi anyway.
Fix: The service script has been fixed to ensure gnocchi api starts correctly at package install time.
Result: service script for gnocchi api starts as expected without any errors.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-03-01 13:38:46 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: | |||
|
Description
Attila Fazekas
2017-01-30 16:57:08 UTC
https://rhos-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/RHOS/view/RHOS10/job/qe-10_director-rhel-7.3-virthost-3cont_1comp_1ceph-ipv4-vxlan-ceph-ssl-yes-telemetry-gabbi/40/ All tests have passed Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2017-0355.html |