virtualization icon indicating copy to clipboard operation
virtualization copied to clipboard

chore(module): dvcr gc provisioners waiting timeout

Open diafour opened this issue 1 month ago • 0 comments

Description

  • Cancel garbage collection if wait for provisioners for more than 2 hours.

Why do we need it, and what problem does it solve?

Provisioners may work at the beginning of garbage collection and controller waits until all provisioners are finished. This wait process should have timeout.

What is the expected result?

GC cancels if provisioners are not finished, condition is set.

Checked with 2m timeout:

{
  "lastTransitionTime": "2025-11-24T17:42:52Z",
  "lastUpdateTime": "2025-11-24T17:42:52Z",
  "message": "Wait for resources provisioners more than 2m0s timeout: 2m1.022922825s elapsed, garbage collection canceled",
  "reason": "Error",
  "status": "False",
  "type": "GarbageCollection"
}

Checklist

  • [ ] The code is covered by unit tests.
  • [ ] e2e tests passed.
  • [ ] Documentation updated according to the changes.
  • [ ] Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: module
type: chore
summary: Cancel dvcr garbage collection if wait for provisioners for more than 2 hours.

diafour avatar Nov 24 '25 14:11 diafour