Release test-operator-lock on CR deletion#466
Conversation
|
Skipping CI for Draft Pull Request. |
2361ec9 to
2c0052f
Compare
|
Build failed (check pipeline). Post ❌ openstack-k8s-operators-content-provider FAILURE in 13m 05s |
2c0052f to
1db8754
Compare
|
Build failed (check pipeline). Post ❌ openstack-k8s-operators-content-provider FAILURE in 12m 36s |
Previously, deleting a CR while its pod held the test-operator-lock could leave the lock stuck, blocking other CR instances indefinitely. Although, GC usually cleans it up in time, it is for the best to support explicit cleanup. Therefore, finalizers are now added unconditionally so the lock is always released during deletion.
1db8754 to
3b699f8
Compare
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 02m 19s |
|
recheck |
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 59m 49s |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: imatza-rh, kstrenkova The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
recheck |
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 3h 04m 01s |
2 participants
Previously, deleting a CR while its pod held the test-operator-lock left the lock stuck, blocking all other CR instances indefinitely. Finalizers are now added unconditionally so the lock is always released during deletion.