Actions
Issue #2340
closed`pulp-admin status` tells the health of the wrong AMQP message bus
Status:
CLOSED - WONTFIX
Priority:
High
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Master
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:
Description
Currently, pulp-admin status
prints a message like this:
[root@localhost ~]# pulp-admin status
+----------------------------------------------------------------------+
Status of the server
+----------------------------------------------------------------------+
Api Version: 2
Database Connection:
Connected: True
Known Workers:
_id: scheduler@localhost.localdomain
_ns: workers
Last Heartbeat: 2016-10-14T20:10:22Z
_id: resource_manager@localhost.localdomain
_ns: workers
Last Heartbeat: 2016-10-14T20:10:23Z
_id: reserved_resource_worker-1@localhost.localdomain
_ns: workers
Last Heartbeat: 2016-10-14T20:10:23Z
_id: reserved_resource_worker-0@localhost.localdomain
_ns: workers
Last Heartbeat: 2016-10-14T20:10:24Z
Messaging Connection:
Connected: True
Versions:
Platform Version: 2.10.1a1
The "Messaging Connection" section tells whether the consumer message bus is connected, and it corresponds to the [messaging]
section in /etc/pulp/server.conf
. However, Pulp doesn't have just one AMQP message bus. It has two: one for consumers, and one for Pulp's own task system. It seems strange that pulp-admin status
tells the health of the optional consumer messaging bus and not the mandatory task message bus.
As a user, I expect pulp-admin status
to tell me the status of Pulp's most critical components. It doesn't do so. I would suggest that:
-
pulp-admin status
tell whether or not the tasking message bus is connected. (This corresponds to the[tasks]
section in/etc/pulp/server.conf
.) - The docs should clearly explain the semantics of the "Messaging Connection" field.
Currently:
-
pulp-admin status
tells whether or not the consumer message bus is connected. (This corresponds to the[messaging]
section in/etc/pulp/server.conf
.) - The docs don't explain the semantics of the "Messaging Connection" field.
Note that much consumer-related functionality is being dropped in Pulp 3, anyway.
Actions