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

CI Failure (Wrong value on some nodes) in ClusterConfigAliasTest.test_aliasing #16143

Closed
vbotbuildovich opened this issue Jan 18, 2024 · 7 comments · Fixed by #16931
Closed
Assignees
Labels
auto-triaged used to know which issues have been opened from a CI job ci-failure

Comments

@vbotbuildovich
Copy link
Collaborator

https://buildkite.com/redpanda/redpanda/builds/43836

Module: rptest.tests.cluster_config_test
Class: ClusterConfigAliasTest
Method: test_aliasing
Arguments: {
    "prop_set": [
        "data_transforms_per_core_memory_reservation",
        "wasm_per_core_memory_reservation",
        [
            23,
            3
        ],
        [
            27000000,
            37000000,
            47000000
        ],
        true
    ]
}
test_id:    ClusterConfigAliasTest.test_aliasing
status:     FAIL
run time:   39.045 seconds

AssertionError("Wrong value on some nodes: data_transforms_per_core_memory_reservation!=47000000 in {'docker-rp-5': 47000000, 'docker-rp-8': 37000000, 'docker-rp-11': 47000000}")
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/dist-packages/ducktape/tests/runner_client.py", line 184, in _do_run
    data = self.run_test()
  File "/usr/local/lib/python3.10/dist-packages/ducktape/tests/runner_client.py", line 269, in run_test
    return self.test_context.function(self.test)
  File "/usr/local/lib/python3.10/dist-packages/ducktape/mark/_mark.py", line 481, in wrapper
    return functools.partial(f, *args, **kwargs)(*w_args, **w_kwargs)
  File "/root/tests/rptest/services/cluster.py", line 82, in wrapped
    r = f(self, *args, **kwargs)
  File "/root/tests/rptest/tests/cluster_config_test.py", line 1498, in test_aliasing
    self._check_propagated_and_persistent(prop_set.primary_name,
  File "/root/tests/rptest/tests/cluster_config_test.py", line 205, in _check_propagated_and_persistent
    self._check_value_everywhere(key, expect_value)
  File "/root/tests/rptest/tests/cluster_config_test.py", line 195, in _check_value_everywhere
    assert all(
AssertionError: Wrong value on some nodes: data_transforms_per_core_memory_reservation!=47000000 in {'docker-rp-5': 47000000, 'docker-rp-8': 37000000, 'docker-rp-11': 47000000}
@vbotbuildovich vbotbuildovich added auto-triaged used to know which issues have been opened from a CI job ci-failure labels Jan 18, 2024
@dotnwat dotnwat changed the title CI Failure (key symptom) in ClusterConfigAliasTest.test_aliasing CI Failure (Wrong value on some nodes) in ClusterConfigAliasTest.test_aliasing Jan 20, 2024
@dotnwat
Copy link
Member

dotnwat commented Jan 20, 2024

@andresaristizabal can you take a look? I think you were the last one to look at config option aliasing? If not, let me know and I'll reassign. Thanks!

@vbotbuildovich
Copy link
Collaborator Author

@vbotbuildovich
Copy link
Collaborator Author

@vbotbuildovich
Copy link
Collaborator Author

@piyushredpanda
Copy link
Contributor

I think you meant to tag @andijcr here?

@vbotbuildovich
Copy link
Collaborator Author

@vbotbuildovich
Copy link
Collaborator Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-triaged used to know which issues have been opened from a CI job ci-failure
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants