-
Notifications
You must be signed in to change notification settings - Fork 14
[WIP] Use test operator to run some of the ansible tests #309
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
base: master
Are you sure you want to change the base?
[WIP] Use test operator to run some of the ansible tests #309
Conversation
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/1d821e5ed8184d40b67f1b2cf694cf0c ✔️ telemetry-openstack-meta-content-provider-master SUCCESS in 2h 31m 07s |
|
This change depends on a change that failed to merge. Change #308 is needed. |
165b9d5 to
866ef29
Compare
|
Merge Failed. This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset. |
35899e5 to
e36a448
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/4342e82743ce48ea90fa1382a2d4d187 ✔️ telemetry-openstack-meta-content-provider-master SUCCESS in 1h 59m 14s |
This reverts commit 5c68939.
This is needed until we have all the vars passed into the pod
The permissions are incorrect for accessing it in this way. TODO: make this task options, or guarded by a check that the dir exists, or even remove the task completely.
The cr tests should specify a namespace, since CRs are created in a particular namespace, the same as other resources like pods. The solution is currently a partial implementation, and needs to be refined so that the namespace is optional for backwards compatibility, but also so that it can actually be set
Add '-n <namespace>' to the oc commands, so that the resources are found
It is only applicable when using gnocchi/tripleo
The scale-up and scale downs tests should not run unless the cpu_high or cpu_low alarm is triggered. If the alarm is not triggered, then the scale up/down test is always going to fail, so we don't need to waste 500s waiting for it to fail. The test will be marked as skipped, but could also be marked as failed instead.
to turn off the StrictHostKeyChecking, the bool value should be "no" rather than false
pre-testing for detecting whether the feature is enabled or not
The command was updated for consistency with the task that creates the busy process, and disables strict host key checking.
0105797 to
e36a448
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/31a90b5920c043e593ed5a9832c85fb4 ✔️ telemetry-openstack-meta-content-provider-master SUCCESS in 2h 01m 12s |
e36a448 to
775762f
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/94eb1290df6743e288a81fc07ecf9b95 ✔️ telemetry-openstack-meta-content-provider-master SUCCESS in 1h 50m 09s |
| @@ -1,9 +1,12 @@ | |||
| --- | |||
| - set_fact: | |||
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.
TODO: Update the var name to be cr_namespace.
No description provided.