Bug 1097247
| Summary: | New Pulp services don't output proper status | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] Pulp | Reporter: | Eric Helms <ehelms> | ||||
| Component: | API/integration | Assignee: | Randy Barlow <rbarlow> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Irina Gulina <igulina> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 2.4 Beta | CC: | igulina, ipanova, rbarlow, skarmark | ||||
| Target Milestone: | --- | Keywords: | Triaged | ||||
| Target Release: | 2.4.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-08-09 06:57:02 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: | |||||||
| Attachments: |
|
||||||
|
Description
Eric Helms
2014-05-13 12:37:21 UTC
This was fixed in pulp-2.4.0-0.19.beta. >>rpm -qa pulp* pulp-rpm-admin-extensions-2.4.0-0.20.beta.fc20.noarch pulp-rpm-handlers-2.4.0-0.20.beta.fc20.noarch pulp-selinux-2.4.0-0.20.beta.fc20.noarch pulp-admin-client-2.4.0-0.20.beta.fc20.noarch pulp-agent-2.4.0-0.20.beta.fc20.noarch pulp-rpm-yumplugins-2.4.0-0.20.beta.fc20.noarch pulp-server-2.4.0-0.20.beta.fc20.noarch pulp-consumer-client-2.4.0-0.20.beta.fc20.noarch pulp-puppet-handlers-2.4.0-0.20.beta.fc20.noarch pulp-puppet-consumer-extensions-2.4.0-0.20.beta.fc20.noarch pulp-puppet-plugins-2.4.0-0.20.beta.fc20.noarch pulp-puppet-admin-extensions-2.4.0-0.20.beta.fc20.noarch pulp-rpm-consumer-extensions-2.4.0-0.20.beta.fc20.noarch pulp-rpm-plugins-2.4.0-0.20.beta.fc20.noarch >> service pulp_celerybeat status Redirecting to /bin/systemctl status pulp_celerybeat.service pulp_celerybeat.service - Pulp's Celerybeat Loaded: loaded (/usr/lib/systemd/system/pulp_celerybeat.service; enabled) Active: active (running) since Wed 2014-06-11 16:31:46 UTC; 19h ago Main PID: 19788 (celery) CGroup: /system.slice/pulp_celerybeat.service └─19788 /usr/bin/python /usr/bin/celery beat --scheduler=pulp.server.async.scheduler.Scheduler >>service pulp_resource_manager status pulp_resource_manager.service - Pulp Resource Manager Loaded: loaded (/usr/lib/systemd/system/pulp_resource_manager.service; enabled) Active: active (running) since Thu 2014-06-12 11:44:34 UTC; 7s ago Main PID: 5702 (celery) CGroup: /system.slice/pulp_resource_manager.service ├─5702 /usr/bin/python /usr/bin/celery worker -A pulp.server.async.app -n resource_manager@%h -Q resource_manager -c 1 --events └─5711 /usr/bin/python /usr/bin/celery worker -A pulp.server.async.app -n resource_manager@%h -Q resource_manager -c 1 --events >>service pulp_workers status Redirecting to /bin/systemctl status pulp_workers.service pulp_workers.service - Pulp Celery Workers Loaded: loaded (/usr/lib/systemd/system/pulp_workers.service; enabled) Active: active (exited) since Wed 2014-06-11 16:31:46 UTC; 19h ago Main PID: 19765 (code=exited, status=0/SUCCESS) CGroup: /system.slice/pulp_workers.service Tried other commands (start, stop, restart) and it controled only a specified service. Verified. Hi Irina, This bug wasn't very clear now that I look back at it, but the original issue that was reported was about our init scripts having working status commands that set correct exit codes. I noticed that you verified our systemd units here. Can you retest on RHEL 6, which uses the init scripts instead of the systemd units? Apologies for not making that clear before you verified it! Created attachment 909150 [details]
verifiyng screenlog over RHEL6.5
status reported by services is mutually independent
This has been fixed in Pulp 2.4.0-1. |