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 (Unknown unexpected error response from ABS) in ShadowIndexingCompactedTopicTest.test_upload #15824

Closed
vbotbuildovich opened this issue Dec 21, 2023 · 4 comments
Labels
area/cloud-storage Shadow indexing subsystem auto-triaged used to know which issues have been opened from a CI job ci-failure sev/low Bugs which are non-functional paper cuts, e.g. typos, issues in log messages

Comments

@vbotbuildovich
Copy link
Collaborator

vbotbuildovich commented Dec 21, 2023

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

Module: rptest.tests.shadow_indexing_compacted_topic_test
Class: ShadowIndexingCompactedTopicTest
Method: test_upload
Arguments: {
    "cloud_storage_type": 2
}
test_id:    ShadowIndexingCompactedTopicTest.test_upload
status:     FAIL
run time:   179.919 seconds

<BadLogLines nodes=docker-rp-14(1) example="ERROR 2023-12-20 22:34:10,395 [shard 1:au  ] abs - abs_client.cc:492 - Received [Bad Request] Unknown unexpected error response from ABS:">
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 142, in wrapped
    redpanda.raise_on_bad_logs(
  File "/root/tests/rptest/services/redpanda.py", line 1321, in raise_on_bad_logs
    raise BadLogLines(bad_lines)
rptest.services.utils.BadLogLines: <BadLogLines nodes=docker-rp-14(1) example="ERROR 2023-12-20 22:34:10,395 [shard 1:au  ] abs - abs_client.cc:492 - Received [Bad Request] Unknown unexpected error response from ABS:">

JIRA Link: CORE-1685

@vbotbuildovich vbotbuildovich added auto-triaged used to know which issues have been opened from a CI job ci-failure labels Dec 21, 2023
@dotnwat dotnwat changed the title CI Failure (key symptom) in ShadowIndexingCompactedTopicTest.test_upload CI Failure (Unknown unexpected error response from ABS) in ShadowIndexingCompactedTopicTest.test_upload Dec 21, 2023
@dotnwat
Copy link
Member

dotnwat commented Dec 21, 2023

I don't see anything out of the ordinary between successful put requests and the one that failed. Further, it seems like we throw away important information in the error reporting that would be helpful in debugging.

We should log more detailed trace information to debug this when it occurs. This could be the headers for the response. Or at least log information about why we are seemingly not getting the string error code parsed out of the xml or json response.

@dotnwat dotnwat added area/cloud-storage Shadow indexing subsystem sev/low Bugs which are non-functional paper cuts, e.g. typos, issues in log messages labels Dec 21, 2023
@vbotbuildovich
Copy link
Collaborator Author

@vbotbuildovich
Copy link
Collaborator Author

@piyushredpanda
Copy link
Contributor

Not seen in at least two months, closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/cloud-storage Shadow indexing subsystem auto-triaged used to know which issues have been opened from a CI job ci-failure sev/low Bugs which are non-functional paper cuts, e.g. typos, issues in log messages
Projects
None yet
Development

No branches or pull requests

3 participants