ducktape: Respect rpk timeout in rpk #24642
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pass the timeout value for rpk that is passed to subprocess also to rpk
itself via
request_timeout_overhead
.Otherwise the specified timeout will not really be respected if the
default timeout in rpk for a certain command is shorter.
Because
request_timeout_overhead
is on top of other possible timeoutsthe total timeout might be larger than the subprocess one but that
should be fine.
Backports Required
Release Notes