Sunpike Services Are Failed Due To Dependency On Pf9-vault

Problem

After rebooting DU VM all the sunpike services failed due to which the Cluster Add-ons are not getting deployed.

Post rebooting DU VM the pf9-vault service failed to start, resulting dependent sunpike services to fail and the cluster add-ons were not deployed in clusters. Later the pf9-vault service came up but sunpike service are still in failed state.

systemd: pf9-vault.service: control process exited, code=exited status=1

systemd: Failed to start "Platform9 Vault - Handling PMK secrets".

systemd: Dependency failed for Platform9 Sunpike kube-controllers Container.

systemd: Job sunpike-kube-controllers.service/start failed with result 'dependency'.

systemd: Dependency failed for Platform9 Sunpike kube-apiserver Container.

systemd: Dependency failed for Platform9 Sunpike K8s API Container.

systemd: Dependency failed for Platform9 Sunpike Conductor Container.

systemd: Job sunpike-conductor.service/start failed with result 'dependency'.

systemd: Dependency failed for Platform9 Sunpike Controller Manager Container.

systemd: Job sunpike-controller-manager.service/start failed with result 'dependency'.

systemd: Job sunpike-apiserver.service/start failed with result 'dependency'.

systemd: Job sunpike-kube-apiserver.service/start failed with result 'dependency'.

This is an known issue with sunpike system services dependencies and Platform9 Engineering is working on the fix. Contact Platform9 Support to check the status of the bug.

# systemctl start sunpike-kine sunpike-kube-apiserver sunpike-kube-controllers sunpike-apiserver sunpike-conductor sunpike-controller-manager

Last updated on

Was this page helpful?