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
DPU object is in ERROR phase when there is "pre bfb-install" failure, no auto re-provisioning is attempted on timeout
Provisioning is stuck on ERROR phase when there is "pre bfb-install" failure, no auto re-provisioning is attempted on timeout. only way to trigger re-provision is to delete the DPU object.
DMS timeout only take effect on "active" API (bfb-install).
In our case the failures happened on inactive API (pre bfb-install) due to:
old "dpf-operator-system-client-secret" secret is not removed when new DPU object come up
NFS was not available to the DMS pod when it came up
Mitigating the Issue:
Deleting the DPU object will triger re-provisioning.
The text was updated successfully, but these errors were encountered:
DPU object is in ERROR phase when there is "pre bfb-install" failure, no auto re-provisioning is attempted on timeout
Provisioning is stuck on ERROR phase when there is "pre bfb-install" failure, no auto re-provisioning is attempted on timeout. only way to trigger re-provision is to delete the DPU object.
DMS timeout only take effect on "active" API (bfb-install).
In our case the failures happened on inactive API (pre bfb-install) due to:
old "dpf-operator-system-client-secret" secret is not removed when new DPU object come up
NFS was not available to the DMS pod when it came up
Mitigating the Issue:
Deleting the DPU object will triger re-provisioning.
The text was updated successfully, but these errors were encountered: