Sunpike Services Are Failed Due To Dependency On Pf9-vault
Problem
Environment
Cause
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'.
systemd: Unit pf9-vault.service entered failed state.
systemd: pf9-vault.service failed.
dracut: *** Resolving executable dependencies ***
systemd: pf9-vault.service holdoff time over, scheduling restart.
systemd: Stopped "Platform9 Vault - Handling PMK secrets".
systemd: Starting "Platform9 Vault - Handling PMK secrets"...Resolution
Workaround
PreviousMetrics-server Pods Are Continuously Restarting With Probe FailuresNextAddOn Operator Pod Restarting due to Error "Use SANs or Temporarily Enable Common Name Matching with
Last updated
