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 }}
Repository navigation
Commit 881706a
Browse filesBrowse the repository at this point in the historyBrowse files
committed
fix(pvc-resize): avoid deadlock on simultaneous storage and resource change (#10427)
When both storage.size and resources are changed in a single patch, the
operator resizes PVCs and then immediately starts a rolling update that
deletes a pod. The orphaned PVC was classified as "resizing" instead of
"dangling", preventing the pod from being recreated and leaving the
cluster stuck.
Fix by always classifying podless resizing PVCs as "dangling" so a
replacement pod is created. This is safe because volumes are usable
during expansion and filesystem resize requires a mounted pod anyway.
Also remove the now-unused isFileSystemResizePending helper, which was
only called from the removed conditional branch in classifyPVC.
Closes#9786
Signed-off-by: Marco Nenciarini <[email protected]>
Signed-off-by: Armando Ruocco <[email protected]>
Signed-off-by: Leonardo Cecchi <[email protected]>
Co-authored-by: Armando Ruocco <[email protected]>
Co-authored-by: Leonardo Cecchi <[email protected]>
(cherry picked from commit 9147871)
0 commit comments