qa/suites/rados: remove rook coverage from the rados suite#51927
qa/suites/rados: remove rook coverage from the rados suite#51927
Conversation
The rook team relies on a daily CI system to validate rook changes. It doesn't seem that the teuthology tests are maintained, so it makes sense to remove them from the rados suite. By removing this symlink, rook test coverage will remain in the orch suite, and coverage will only be removed from the rados suite. Workaround for: https://tracker.ceph.com/issues/58585 Signed-off-by: Laura Flores <lflores@redhat.com>
|
Hey @travisn, see what you think of this PR. We've had rook tests failing for quite awhile in the rados suite, but I think your team relies on a different set of tests for rook validation. Are these tests maintained? If not, we should consider removing them. |
Correct, Rook relies on github actions in its own repo, such as the daily actions that can be seen here. I don't even recall who created the rook tests for teuthology, but if they are not being maintained, sounds good to remove them. |
|
The only way to test this is to schedule a teuthology suite and check that any rook jobs have been added. I did this with rados and orch dry runs. In rados, no more rook tests appear: https://paste.centos.org/view/5fb90a24 In orch, the rook tests are still there: https://paste.centos.org/view/8269c4c6 These can be removed from the orch suite as well, but I will leave it to cephadm folks to decide on that. |
The rook team relies on a daily CI system to validate rook changes. It doesn't seem that the teuthology tests are maintained, so it makes sense to remove them from the rados suite.
By removing this symlink, rook test coverage will remain in the orch suite, and coverage will only be removed from the rados suite.
Workaround for: https://tracker.ceph.com/issues/58585
Signed-off-by: Laura Flores lflores@redhat.com
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. "pacific"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.
Checklist
Show available Jenkins commands
jenkins retest this pleasejenkins test classic perfjenkins test crimson perfjenkins test signedjenkins test make checkjenkins test make check arm64jenkins test submodulesjenkins test dashboardjenkins test dashboard cephadmjenkins test apijenkins test docsjenkins render docsjenkins test ceph-volume alljenkins test ceph-volume toxjenkins test windows