Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rptest: request feature state from each node in await_feature #23579

Merged

Conversation

nvartolomei
Copy link
Contributor

@nvartolomei nvartolomei commented Oct 1, 2024

Fixes ControllerSnapshotPolicyTest.test_snapshotting_policy test.

Before the test would spuriously fail because it would try to deactivate and then reactive the feature before waiting for deactivation to finish.

The admin endpoint checks feature state without a linearizable barrier to short-circuit execution if feature is already active. This is why we need to wait for previous command to be applied first. To make sure the in-memory state is updated.


Regression likely introduced in #22533

Backports Required

  • none - not a bug fix
  • none - this is a backport
  • none - issue does not exist in previous branches
  • none - papercut/not impactful enough to backport
  • v24.2.x
  • v24.1.x
  • v23.3.x

Release Notes

  • none

@nvartolomei nvartolomei requested a review from ztlpn October 1, 2024 08:56
ztlpn
ztlpn previously approved these changes Oct 1, 2024
@vbotbuildovich
Copy link
Collaborator

vbotbuildovich commented Oct 1, 2024

new failures in https://buildkite.com/redpanda/redpanda/builds/55519#019247a1-468b-4226-b925-d8702516727d:

"rptest.tests.shard_placement_test.ShardPlacementTest.test_node_join"

new failures in https://buildkite.com/redpanda/redpanda/builds/55519#019247a5-525e-4e66-a6db-badb4cc9ba73:

"rptest.tests.shard_placement_test.ShardPlacementTest.test_node_join"

@vbotbuildovich
Copy link
Collaborator

vbotbuildovich commented Oct 1, 2024

Fixes ControllerSnapshotPolicyTest.test_snapshotting_policy test.

Before the test would spuriously fail because it would try to deactivate
and then reactive the feature before waiting for deactivation to finish.

The admin endpoint checks feature state without a linearizable barrier
to short-circuit execution if feature is already active. This is why we
need to wait for previous command to be applied first. To make sure the
in-memory state is updated.

Also, request feature state only from started nodes. We have tests (i.e.
upgrade tests) which try to enable features before all nodes are
started.
@ztlpn
Copy link
Contributor

ztlpn commented Oct 1, 2024

Thanks!

@nvartolomei nvartolomei merged commit 52b4423 into redpanda-data:dev Oct 1, 2024
16 checks passed
@vbotbuildovich
Copy link
Collaborator

/backport v24.2.x

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