Plugins » Katello

There are ways to get into the situation, where Pulp3 API is available, but the content app is down (see https://pulp.plan.io/issues/9515 for an example).

I think in this case, the Pulp3 feature in Katello should not be declared as "up and running", but it is right now:

# hammer ping
…
pulp3:            
    Status:          ok
    Server Response: Duration: 32ms

# curl -k https://localhost/pulp/api/v3/status/ | python -m json.tool
{
    "database_connection": {
        "connected": true
    },
    "online_content_apps": [],
    "online_workers": [
        {
            "last_heartbeat": "2021-10-18T10:26:34.737838Z",
            "name": "2264@pipe-katello-server-nightly-centos7.tanso.example.com",
            "pulp_created": "2021-10-18T10:18:14.101891Z",
            "pulp_href": "/pulp/api/v3/workers/3fbb3a7f-27dc-4ba9-af04-dacec5e0ef39/" 
        },
        {
            "last_heartbeat": "2021-10-18T10:26:34.762561Z",
            "name": "2265@pipe-katello-server-nightly-centos7.tanso.example.com",
            "pulp_created": "2021-10-18T10:18:14.118910Z",
            "pulp_href": "/pulp/api/v3/workers/da429001-837e-4d79-a1f6-d958aaabf6ed/" 
        }
    ],
    "redis_connection": null,
…

I think we should watch for `online_content_apps` and raise a warning to the user, if that is empty.

The user visible part is that the content is not available:

# curl -k https://localhost/pulp/content/
500 Internal Server Error