Skip to content

qa: Restrict rados api tests to large clusters and increase timeout#58635

Merged
yuriw merged 1 commit intoceph:mainfrom
badone:wip-tracker-50371-rados_api_test-timeout-failures
Aug 1, 2024
Merged

qa: Restrict rados api tests to large clusters and increase timeout#58635
yuriw merged 1 commit intoceph:mainfrom
badone:wip-tracker-50371-rados_api_test-timeout-failures

Conversation

@badone
Copy link
Contributor

@badone badone commented Jul 17, 2024

Running these tests with thrashers on small clusters leads to many very slow ops due to the cluster being overloaded. That has a tendency to make some of the API tests timeout and fail.

Fixes: https://tracker.ceph.com/issues/50371

Contribution Guidelines

  • To sign and title your commits, please refer to Submitting Patches to Ceph.

  • If you are submitting a fix for a stable branch (e.g. "quincy"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.

  • When filling out the below checklist, you may click boxes directly in the GitHub web UI. When entering or editing the entire PR message in the GitHub web UI editor, you may also select a checklist item by adding an x between the brackets: [x]. Spaces and capitalization matter when checking off items this way.

Checklist

  • Tracker (select at least one)
    • References tracker ticket
    • Very recent bug; references commit where it was introduced
    • New feature (ticket optional)
    • Doc update (no ticket needed)
    • Code cleanup (no ticket needed)
  • Component impact
    • Affects Dashboard, opened tracker ticket
    • Affects Orchestrator, opened tracker ticket
    • No impact that needs to be tracked
  • Documentation (select at least one)
    • Updates relevant documentation
    • No doc update is appropriate
  • Tests (select at least one)
Show available Jenkins commands
  • jenkins retest this please
  • jenkins test classic perf
  • jenkins test crimson perf
  • jenkins test signed
  • jenkins test make check
  • jenkins test make check arm64
  • jenkins test submodules
  • jenkins test dashboard
  • jenkins test dashboard cephadm
  • jenkins test api
  • jenkins test docs
  • jenkins render docs
  • jenkins test ceph-volume all
  • jenkins test ceph-volume tox
  • jenkins test windows
  • jenkins test rook e2e

@badone badone requested a review from a team as a code owner July 17, 2024 03:05
@badone badone added the DNM label Jul 17, 2024
@ljflores
Copy link
Member

jenkins test api

Running these tests with thrashers on small clusters leads to many very
slow ops due to the cluster being overloaded. That has a tendency to
make some of the API tests timeout and fail.

Fixes: https://tracker.ceph.com/issues/50371

Signed-off-by: Brad Hubbard <bhubbard@redhat.com>
@badone badone force-pushed the wip-tracker-50371-rados_api_test-timeout-failures branch from 4fafe1f to d034fec Compare July 17, 2024 23:09
@badone badone removed the DNM label Jul 18, 2024
@badone
Copy link
Contributor Author

badone commented Jul 18, 2024

https://pulpito.ceph.com/bhubbard-2024-07-17_05:49:47-rados-wip-badone-testing-distro-default-smithi/

One failure is https://tracker.ceph.com/issues/65449 currently investigating the others which are in cache tiering tests which can probably be ignored or even disabled.

@badone
Copy link
Contributor Author

badone commented Jul 19, 2024

The other issue during my tests was this one which seems like some sort of networking issue, but it's not clear exactly what.

https://tracker.ceph.com/issues/67029

@ljflores
Copy link
Member

@badone as this is just a qa change, feel free to merge if you are satisfied with the tests you scheduled above.

@NitzanMordhai
Copy link
Contributor

@yuriw yuriw merged commit dd87d57 into ceph:main Aug 1, 2024
@badone badone deleted the wip-tracker-50371-rados_api_test-timeout-failures branch August 5, 2024 01:48
@batrick
Copy link
Member

batrick commented Aug 5, 2024

Unfortunately this breaks scheduling the orch suite: https://tracker.ceph.com/issues/67352

I'll post a fix in a minute.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants