1
45%
master: 45%

Ran 01 Jun 2026 07:21AM UTC

Files 73

Run time 2s

Badge

Embed ▾

Committed 01 Jun 2026 07:18AM UTC coverage: 43.809% (-0.09%) from 43.894%

Job # 26740842852.1

Build Type

push

github

Committed by

web-flow

Commit Message

Fix deletion timestamp handling for clusters with finalizers (#3015)

When a Postgres cluster has a finalizer, deleting it sets a DeletionTimestamp
but doesn't remove the object until the finalizer is cleared. The operator
was not properly handling these DeletionTimestamp changes:

1. postgresqlUpdate() was filtering out events where only DeletionTimestamp
   changed (it only checked Spec and Annotations), causing the delete to
   never be processed.

2. EventUpdate case in processEvent() didn't check for DeletionTimestamp,
   so even if the event reached the processor, it would run Update() instead
   of Delete().

3. removeFinalizer() used a cached object with stale resourceVersion,
   causing "object has been modified" errors.

Fixes:
- Add explicit DeletionTimestamp check in postgresqlUpdate() to queue the event
- Add DeletionTimestamp check in EventUpdate to call Delete() when set
- Fetch latest object from API before removing finalizer to avoid conflicts

Co-authored-by: Felix Kunde <felix-kunde@gmx.de>

Coverage Stats

6701 of 15296 relevant lines covered (43.81%)

17.06 hits per line

zalando / postgres-operator / 26740842852 / 1
45%
master: 45%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 26740842852.1

zalando / postgres-operator / 26740842852 / 1 45% master: 45%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 26740842852.1

zalando / postgres-operator / 26740842852 / 1
45%
master: 45%

README BADGES
x