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 (k8s time format does not match format) in RollingRestartTest.test_restart_pod #18614

Closed
vbotbuildovich opened this issue May 21, 2024 · 2 comments
Labels
area/htt auto-triaged used to know which issues have been opened from a CI job ci-failure ci-rca/infra CI Root Cause Analysis - Infrastructure Issue

Comments

@vbotbuildovich
Copy link
Collaborator

vbotbuildovich commented May 21, 2024

https://buildkite.com/redpanda/vtools/builds/13767

Module: rptest.redpanda_cloud_tests.rolling_restart_test
Class: RollingRestartTest
Method: test_restart_pod
test_id:    RollingRestartTest.test_restart_pod
status:     FAIL
run time:   178.920 seconds

ValueError("time data '2024-05-16T06:39:06.24361Z +00:00' does not match format '%Y-%m-%dT%H:%M:%S.%f %z'")
Traceback (most recent call last):
  File "/opt/.ducktape-venv/lib/python3.10/site-packages/ducktape/tests/runner_client.py", line 184, in _do_run
    data = self.run_test()
  File "/opt/.ducktape-venv/lib/python3.10/site-packages/ducktape/tests/runner_client.py", line 276, in run_test
    return self.test_context.function(self.test)
  File "/home/ubuntu/redpanda/tests/rptest/services/cluster.py", line 184, in wrapped
    redpanda.raise_on_bad_logs(
  File "/home/ubuntu/redpanda/tests/rptest/services/redpanda.py", line 2165, in raise_on_bad_logs
    lsearcher.search_logs(self.pods)
  File "/home/ubuntu/redpanda/tests/rptest/services/utils.py", line 193, in search_logs
    bad_loglines = self._search(nodes)
  File "/home/ubuntu/redpanda/tests/rptest/services/utils.py", line 171, in _search
    for line in self._capture_log(node, self.match_expr):
  File "/home/ubuntu/redpanda/tests/rptest/services/utils.py", line 273, in _capture_log
    logline_time = parse_k8s_time(line, tz)
  File "/home/ubuntu/redpanda/tests/rptest/services/utils.py", line 234, in parse_k8s_time
    return time.strptime(logline_time, k8s_time_format)
  File "/usr/lib/python3.10/_strptime.py", line 562, in _strptime_time
    tt = _strptime(data_string, format)[0]
  File "/usr/lib/python3.10/_strptime.py", line 349, in _strptime
    raise ValueError("time data %r does not match format %r" %
ValueError: time data '2024-05-16T06:39:06.24361Z +00:00' does not match format '%Y-%m-%dT%H:%M:%S.%f %z'

JIRA Link: CORE-3057

@vbotbuildovich vbotbuildovich added auto-triaged used to know which issues have been opened from a CI job ci-failure labels May 21, 2024
@travisdowns
Copy link
Member

@savex any idea? Seems like a one-off which is weird b/c if this parsing wasn't you think that would be a constant thing. Maybe this was fixed along the way?

@travisdowns travisdowns changed the title CI Failure (key symptom) in RollingRestartTest.test_restart_pod CI Failure (k8s time format does not match format) in RollingRestartTest.test_restart_pod Jun 23, 2024
@twmb twmb added the ci-rca/infra CI Root Cause Analysis - Infrastructure Issue label Jul 1, 2024
@rpdevmp
Copy link
Contributor

rpdevmp commented Aug 13, 2024

Closing as old issue. We now have new PandaTriage with a different logic for grouping issues by failures.

@rpdevmp rpdevmp closed this as completed Aug 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/htt auto-triaged used to know which issues have been opened from a CI job ci-failure ci-rca/infra CI Root Cause Analysis - Infrastructure Issue
Projects
None yet
Development

No branches or pull requests

4 participants