Skip to content

Fix invalid postRenderers change causing release to report Ready - #1609

Merged
stefanprodan merged 2 commits into
mainfrom
fix-post-render
Oct 25, 2026
Merged

stefanprodan merged 2 commits into
mainfrom
fix-post-render

Conversation

@matheuscscp

Copy link
Copy Markdown
Member

Fixes: #1607

@matheuscscp matheuscscp added the bug Something isn't working label Oct 12, 2026
matheuscscp and others added 2 commits October 25, 2026 15:58
Signed-off-by: Matheus Pimenta <matheuscscp@gmail.com>
Drop the observed generation guard from the post-renderers and common
metadata digest checks. A terminal error after exhausted upgrade
retries advances status.observedGeneration, so the next reconcile
skipped the check and reported the rolled-back release as Ready
while it still ran the previous post-renderers.

The guard only prevented an upgrade loop when the digests were
recorded at the end of the atomic release. They are now recorded
right after a successful install or upgrade.

Compare using the algorithm of the observed digest, so changing
--snapshot-digest-algo does not trigger upgrades.

Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
Assisted-by: claude-code/claude-opus-5-5
@matheuscscp matheuscscp added the backport:release/v1.7.x To be backported to release/v1.7.x label Oct 25, 2026
@stefanprodan
stefanprodan merged commit 6771115 into main Oct 25, 2026
8 checks passed
@stefanprodan
stefanprodan deleted the fix-post-render branch October 25, 2026 14:45
@fluxcdbot

Copy link
Copy Markdown
Member

Successfully created backport PR for release/v1.7.x:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:release/v1.7.x To be backported to release/v1.7.x bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

A failed upgrade that stores no release is reported Ready after a change of postRenderers alone

3 participants