Skip to content

pipeline-manager: fix starting pipeline while clearing storage#5812

Merged
snkas merged 1 commit intomainfrom
fix-clearing-transition
Mar 13, 2026
Merged

pipeline-manager: fix starting pipeline while clearing storage#5812
snkas merged 1 commit intomainfrom
fix-clearing-transition

Conversation

@snkas
Copy link
Contributor

@snkas snkas commented Mar 12, 2026

Before it was possible to (early) start a pipeline while storage was still clearing, and to clear storage while still awaiting the transition of the resources status during early start. Only once the resources status transitioned, was it no longer possible for storage status to change.

Changes:

  • No longer allow a pipeline to be (early) started when the storage is still clearing, returning an error instead.
  • No longer allow storage to be cleared during early start, returning an error instead.
  • Always allow any of the other resources statuses to transition to Stopping, even if storage status does not match expectation. The same for transitioning from Stopping to Stopped. This is a fail-safe for if storage status ends up in an expected status due to an internal error.

PR information

  • Database tests added
  • Python integration tests added
  • Documentation is not updated
  • Changelog is updated
  • No breaking changes (all are fixes of behavior that should have been in place)

@snkas snkas requested a review from mythical-fred March 12, 2026 19:31
@snkas snkas requested review from gz and mythical-fred March 12, 2026 19:55
Copy link

@mythical-fred mythical-fred left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changelog added, and I was wrong about the { .. } pattern — it compiles fine on unit variants. LGTM.

@snkas snkas force-pushed the fix-clearing-transition branch 2 times, most recently from 72975a6 to 4ea4663 Compare March 13, 2026 09:14
@snkas snkas enabled auto-merge March 13, 2026 09:19
@snkas snkas added this pull request to the merge queue Mar 13, 2026
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Mar 13, 2026
Before it was possible to (early) start a pipeline while storage was
still clearing, and to clear storage while still awaiting the transition
of the resources status during early start. Only once the resources
status transitioned, was it no longer possible for storage status to
change.

Changes:
- No longer allow a pipeline to be (early) started when the storage is
  still clearing, returning an error instead.
- No longer allow storage to be cleared during early start, returning an
  error instead.
- Always allow any of the other resources statuses to transition to
  `Stopping`, even if storage status does not match expectation.
  The same for transitioning from `Stopping` to `Stopped`. This is a
  fail-safe for if storage status ends up in an expected status due to
  an internal error.

Signed-off-by: Simon Kassing <simon.kassing@feldera.com>
@snkas snkas force-pushed the fix-clearing-transition branch from 4ea4663 to 8a60a79 Compare March 13, 2026 11:18
@snkas snkas enabled auto-merge March 13, 2026 11:19
@snkas snkas added this pull request to the merge queue Mar 13, 2026
Merged via the queue into main with commit 4b0d24b Mar 13, 2026
1 check passed
@snkas snkas deleted the fix-clearing-transition branch March 13, 2026 13:02
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