Skip to content

Fix crutest replace workload to use new regions - #2078

Open
leftwo wants to merge 1 commit into
alan/crutest-fresh-sparefrom
alan/crutest-live-replace-fresh
Open

leftwo wants to merge 1 commit into
alan/crutest-fresh-sparefrom
alan/crutest-live-replace-fresh

Conversation

@leftwo

@leftwo leftwo commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

In the crutest replace workload after each live repair, give the
downstairs that was replaced a new empty region before it is used as
the next replacement. This matches what the control plane does
and avoids re-use of an existing region which comes with been_active
set (which we don't want)

This uses the dsc recreate from #2073 and the crutest recreate_downstairs
from #2074.

The replace workload now requires --dsc, so update the buildomat job
to switch to that instead of providing targets.

If the replace task ends, the IO task now stops instead of running IO
until the count is reached, so a replace failure is reported right away.

@leftwo
leftwo added this pull request to stack #2077 November 6, 2026 21:06
@leftwo
leftwo force-pushed the alan/crutest-live-replace-fresh branch from c4208a9 to 67e9722 Compare November 6, 2026 21:08
After each live repair in the replace workload, give the downstairs that
was replaced a new, empty region before it is used as the next
replacement.  This makes it look like the new region the control-plane
would provide, instead of reusing a region that was already part of the
volume and would come with been_active status we don't want.

Add a dsc endpoint instead of targets to the replace workload in the live
repair buildomat job..

If the replace task ends, stop the IO task instead of running IO until
the count is reached.
@leftwo
leftwo force-pushed the alan/crutest-live-replace-fresh branch from 67e9722 to 918d2d3 Compare November 6, 2026 21:19
@leftwo leftwo changed the title Alan/crutest live replace fresh Fix crutest replace workload to use new regions Nov 6, 2026
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.

1 participant