Skip to content

[release/v1.6.x] Recover from drifted Ready/Released status conditions - #1582

Merged
matheuscscp merged 1 commit into
release/v1.6.xfrom
backport-1580-to-release/v1.6.x
Sep 2, 2026
Merged

[release/v1.6.x] Recover from drifted Ready/Released status conditions#1582
matheuscscp merged 1 commit into
release/v1.6.xfrom
backport-1580-to-release/v1.6.x

Conversation

@fluxcdbot

Copy link
Copy Markdown
Member

Automated backport to release/v1.6.x, triggered by a label in #1580.

When a post-action status condition patch failed for a HelmRelease
that was just installed or upgraded (e.g. due to version conflicts),
but history was successfully persisted, a HelmRelease could be
stranded with `Ready=Unknown` while actually being completely
installed in the cluster.

Subsequent reconciliations of the HelmRelease would not correct
that drift as the pre-existing correction mechanism required
a `Released` status condition to exist. However, since that
would've been created in the same patch as the missing `Ready`
update, that would always fail.

This fix extends the existing correction mechanism to allow
for a missing `Released` status condition, in which case it will
resort to `status.lastAttemptedReleaseAction` or `status.history`
to determine the desired state for `Ready` and `Released`.

Signed-off-by: Peter Bücker <peter.buecker@form3.tech>
Assisted-by: cursor/grok-4.6
(cherry picked from commit 49996c7)
@matheuscscp
matheuscscp merged commit eaa97e0 into release/v1.6.x Sep 2, 2026
4 of 5 checks passed
@matheuscscp
matheuscscp deleted the backport-1580-to-release/v1.6.x branch September 2, 2026 13:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants