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
suites: qa tasks with crush rules #53308
suites: qa tasks with crush rules #53308
Conversation
'set_choose_tries 100', | ||
'take default class hdd', | ||
'choose indep 4 type host', | ||
'chooseleaf indep 8 type osd', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use choose rather than chooseleaf here due to https://tracker.ceph.com/issues/62213
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure why this one needs 4 hosts, 8 osds per host. 2+2 should probably be a normal host chooseleaf rule, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
isn't it supposed to be 4 host 1 osd? so it will simulate full host shutdown?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right, so step chooseleaf indep 4 type host
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah,
'choose indep 4 type host',
'choose indep 1 type osd',
is almost correct, but you should use step chooseleaf indep 4 type host
instead. Using two choose steps instead of a single chooseleaf step actually has different behavior once OSDs get marked out.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
c90f6e5
to
f78ba83
Compare
364859e
to
31ba9f3
Compare
@athanatos @neha-ojha I added some code to thrash hosts, so the thrasher will be able to thrash the entire osds under one host |
62ac56d
to
65c864f
Compare
Hey @NitzanMordhai, QA caught this failure:
You can see more examples on this link: You can re-add the "needs-qa" label when it's ready for a retest! |
65c864f
to
1b10309
Compare
jenkins test make check |
@NitzanMordhai there are a few suspect jobs in the latest teuthology run as analyzed by @ronen-fr :
And two more with slightly different Tracebacks but similar problems:
These failures don't happen deterministically, so it might be worth running several of these "workloads/ec-rados-plugin=xxx} " tests multiple times to ensure they're passing. |
4f274e1
to
d536f03
Compare
646c2cd
to
2262a0e
Compare
I made some more changes to the thrasher, we had some issues with 4 hosts thrashing. |
This pull request can no longer be automatically merged: a rebase is needed and changes have to be manually resolved |
Adding new yaml entry to handle create of crush profile before creating new pool, will be skipped if no crush profile name was set. Signed-off-by: Nitzan Mordechai <nmordech@redhat.com>
Signed-off-by: Nitzan Mordechai <nmordech@redhat.com>
Extra un needed checks and sets for filestore in suites setup need to be removed. Signed-off-by: Nitzan Mordechai <nmordech@redhat.com>
To simulate real world maintanace, we will usualy shut down hosts and not just osd the following commit will add host thrasher option to Thraser, when thrash_hosts is True we won't thrash osds one by one, we will choose entire host and thrash all the osds under that host. Signed-off-by: Nitzan Mordechai <nmordech@redhat.com>
2262a0e
to
190a761
Compare
Looks like this one was merged a little early before a second round of QA could be reviewed. @NitzanMordhai can you take a look at https://tracker.ceph.com/issues/65517? |
To handle EC profiles with crush rules of 2+2 and 8+6 on few hosts:
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 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