-
Notifications
You must be signed in to change notification settings - Fork 75
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
qa: refactor health-ok.sh, drop health-{mds,rgw}.sh #1233
Conversation
Hm, currently the scripts don't know how to deploy mds without a client (non-storage) node present. Fixing. |
@jschmid1 Is the lint failure expected? |
NOTE: setting DNM because this PR will break the teuthology I'll prepare a downstream Ceph PR to update |
Testing update. On a single-node Salt cluster with 4 external disks, I ran:
All green. UPDATE: Oops, wrong orchestration. Should be "ceph.smoketests". |
@jschmid1 As you can see, I'm removing the I have a Ceph branch: https://github.com/SUSE/ceph/tree/wip-qa-deepsea-func I haven't opened a Ceph PR yet because that branch is WIP. But when it's ready it will have tests that reproduce the ceph-restart functional testing that is being removed from the health-ok, etc. scripts by this PR. |
I saw it failing initially for exactly what you are getting:
those disappear on the next iteration .. |
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.
lgtm
I get a 404 on that one |
Let me know when to hit the merge button |
@jschmid1 Sorry, fixed that comment so it reads correctly: I have a Ceph branch: https://github.com/SUSE/ceph/tree/wip-qa-deepsea-func |
osd_restarted "0" | ||
# make sure still in HEALTH_OK | ||
ceph_cluster_status | ||
ceph_health_test |
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.
@jschmid1 Are you OK to drop this test of the restart functionality? Maybe the test should be re-implemented under ceph.smoketests
before we really drop it?
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.
Getting rid of it now means that we have at least for a short period of time no restart tests, right?
In that case I'd keep them in for now and remove them after we implemented the restart.functests
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.
Agreed to drop because the tests really are re-implemented in ceph.smoketests
and the CI will run that orchestration.
b8dd142
to
df590ea
Compare
@smithfarm looks green to me :) |
@jschmid1 Yeah, sorry, I was originally under the impression that I will reinstate the restart tests (and "--mini") into health-ok.sh. |
For master, we do. But do we already run those? |
5ef54ec
to
4422808
Compare
@jschmid1 So, to recapitulate, this PR:
In parallel, there will be a SUSE/ceph PR that will
Sound right to you? |
Now that we have the ceph.restart orchestration for testing the restart functionality, we can simplify the integration testing scripts. The actual triggering of the ceph.restart orchestration will be done in the teuthology test yaml, which lives in the Ceph repo. Signed-off-by: Nathan Cutler <[email protected]>
Signed-off-by: Nathan Cutler <[email protected]>
Signed-off-by: Nathan Cutler <[email protected]>
This function could have produced a false positive if both the RPM and Ceph version strings failed the regex match. (In that case, both the variables would have been empty and the equality test might have passed.) With this commit, the test explicity checks that the regex match actually produced a string that can be usefully compared. Signed-off-by: Nathan Cutler <[email protected]>
4422808
to
4fc7e85
Compare
This commit: * adds suse/smoke/functional test case that triggers ceph.smoketests orchestration * refactors the other test cases for compatibility with SUSE/DeepSea#1233 Signed-off-by: Nathan Cutler <[email protected]>
@jschmid1 Would it be OK to rename |
This secret code will make it easier to navigate teuthology logs, for tests that use health-ok.sh to deploy the cluster. Just search for YYYY to get to the end of the deployment phase. Signed-off-by: Nathan Cutler <[email protected]>
Signed-off-by: Nathan Cutler <[email protected]>
Yes, that'd be fine with me. Currently everything is only required to have at least one node. |
Signed-off-by: Nathan Cutler <[email protected]>
Signed-off-by: Nathan Cutler <[email protected]>
@jschmid1 OK, added smoketests rename commit - as a result, this PR now conflicts with #1216 so adding @swiftgist as reviewer. |
Signed-off-by: Nathan Cutler <[email protected]>
@jschmid1 Latest test run http://137.74.25.20:8081/ubuntu-2018-07-26_22:31:13-suse:smoke-ses6---basic-openstack/ and especially the test that runs The only failures are in the tests that run The related test yaml changes in the SUSE/ceph.git are already in the So 👍 to merge from my side. |
Now that we have the ceph.restart orchestration for testing the restart
functionality, we can simplify the integration testing scripts.
The actual triggering of the ceph.restart orchestration will be done
in the teuthology test yaml, which lives in the Ceph repo.
We retain
health-nfs-ganesha.sh
as a separate script for now, tokeep
health-ok.sh
as simple as possible for as long as possible.