You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 22, 2024. It is now read-only.
When deleting a pod that contains PMEM-CSI and external-provisioner and PMEM-CSI shuts down first, external-provisioner logs a "connection lost" error before shutting down itself
Slightly delay the shutdown in PMEM-CSI. Assuming that all containers get killed roughly at the same time (to be checked!), external-provisioner then should shut down first.
If shutdown order is container-by-container, then we can re-order containers to so that external-provisioner comes first. It wasn't done that way because during startup, PMEM-CSI must be up first before external-provisioner can work. But it will retry to connect without verbose output, so this may be better.
Silence the error message in external-provisioner (upstream solution).
When deleting a pod that contains PMEM-CSI and external-provisioner and PMEM-CSI shuts down first, external-provisioner logs a "connection lost" error before shutting down itself
This is from https://cloudnative-k8sci.southcentralus.cloudapp.azure.com/blue/rest/organizations/jenkins/pipelines/pmem-csi/branches/PR-838/runs/14/nodes/88/steps/105/log/?start=0, i.e. testing of PR #838 , but should also occur on current devel.
That output is very verbose. It would be nice to avoid it.
The text was updated successfully, but these errors were encountered: