pf9-containerproxy.service is in Failed State on Platform9 Management Plane?

Problem

• Why systemd service pf9-containerproxy.service is in failed state on the Platform9 Management Plane Virtual Machine?

xxxxxxxxxx

[root@airctl-support-lts.pf9.localnet ~(admin)]# systemctl status pf9-containerproxy.service

● pf9-containerproxy.service - Platform9 Container Proxy Service

   Loaded: loaded (/usr/lib/systemd/system/pf9-containerproxy.service; enabled; vendor preset: disabled)

   Active: failed (Result: start-limit) since Thu 2022-07-07 20:34:25 UTC; 2 weeks 4 days ago

 Main PID: 5025 (code=exited, status=1/FAILURE)

Environment

• Platform9 Edge Cloud - All Versions

Answer

• The systemd service pf9-containerproxy.service on Platform9 Management Plane was previously used for multiple purposes but mainly as a Certificate Authority (CA) server.
• In latter versions it was replaced with another Platform9 System Service i.e. pf9-vault.service

xxxxxxxxxx

[root@airctl-support-lts.pf9.localnet ~(admin)]# systemctl list-units --all | grep -i vault

pf9-vault.service                  loaded    active   running   "Platform9 Vault - Handling PMK secrets"

• The pf9-containerproxy.service is currently not in use but because it is integrated in the qbert package, it is not yet completely removed.

[root@airctl-support-lts.pf9.localnet ~(admin)]# rpm -q --whatprovides /usr/lib/systemd/system/pf9-containerproxy.service

pf9-qbert-5.3.0-15888.x86_64

• The service failure status won't have any adverse effect on the management plane or the clusters and hence it can be safely ignored.