Plugins » Katello

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1683081

Description of problem:
When candlepin is in "SUSPEND" mode, `hammer ping` still reports "ok" on candlepin

Version-Release number of selected component (if applicable):
master

How reproducible:
always

Steps to Reproduce:
1. # curl -k https://$HOSTNAME:8443/candlepin/status {"mode":"SUSPEND","modeReason":"QPID_DOWN","modeChangeTime":"2019-02-23T21:33:14+0000","result":false,"version":"2.5.8","rulesVersion":"5.30.1","release":"1","standalone":true,"timeUTC":"2019-02-26T08:25:05+0000","rulesSource":"database","managerCapabilities":["instance_multiplier","derived_product","vcpu","cert_v3","remove_by_pool_id","syspurpose","storage_band","cores","hypervisors_async","org_level_content_access","guest_limit","ram","batch_bind"]}
I assume it is possible to get into this state by stopping qpidd or
qdrouterd or both
2. # hammer ping
candlepin:
Status: ok
Server Response: Duration: 21ms
candlepin_auth:
Status: ok
Server Response: Duration: 16ms
pulp:
Status: ok
Server Response: Duration: 64ms
pulp_auth:
Status: ok
Server Response: Duration: 38ms
foreman_tasks:
Status: ok
Server Response: Duration: 6ms

Actual results:
`hammer ping` is still happy although Candlepin is not operating:

[root@some_client ~]# subscription-manager unregister
Unregistering from: caps1.satperf.local:8443/rhsm
HTTP error code 503: Candlepin is in Suspend mode, please check /status resource to get more details

Expected results:
`hammer ping` (or `foreman-maintain health check` should fail on this)