-
Notifications
You must be signed in to change notification settings - Fork 105
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
[WIP] Install telemetry_tempest_plugin from master branch #1065
[WIP] Install telemetry_tempest_plugin from master branch #1065
Conversation
Skipping CI for Draft Pull Request. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
b7cd42d
to
6b3340f
Compare
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/f442300bbda24b2b8f3621f8f3fc089c ✔️ openstack-k8s-operators-content-provider SUCCESS in 37m 57s |
recheck The failure was in deploying openstack. |
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/95d05ed7303443f5ab607f2043a52277 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 35m 38s |
Zuul encountered a syntax error while parsing its configuration in the expected a list for dictionary value @ data['templates'] The error appears in the following project stanza: project: in "openstack-k8s-operators/ci-framework/zuul.d/projects.yaml@main", line 1, column 3 |
64a4ba7
to
e7b1574
Compare
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/620f772e2cbe4584a25d0339e0854f05 ✔️ noop SUCCESS in 0s |
fa54545
to
04f1eaa
Compare
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/60e581058b944a27b963ef97c239c5b9 ✔️ noop SUCCESS in 0s |
04f1eaa
to
292217f
Compare
65d25ac
to
e417628
Compare
Using the tempest role from ci_framework ran the tempest container via podman on the controller. test_operator uses the same image and runs tempest in a pod on the OCP cluster. Depends-On: openstack-k8s-operators/ci-framework#1065
Using the tempest role from ci_framework ran the tempest container via podman on the controller. test_operator uses the same image and runs tempest in a pod on the OCP cluster. Depends-On: openstack-k8s-operators/ci-framework#1065
The version of the telemetry-tempest-plugin in the tempest container is behind master. The test in the tempest image require gnocchi, which is not included by the telemetry operator. In order to test the telemetry-operator tempest job, the newer version of the telemetry-tempest-plugin needs to be used. In order to test this, the tempest role has been modified to update the version of telemetery-tempest-plugin to be included.
I don't want to wait for these jobs to pass while testing a PoC
…nfig This should let us use an arbitrary version of a plugin without overriding the whole cifmw_test_operator_tempest_config.
e417628
to
6088f95
Compare
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Using the tempest role from ci_framework ran the tempest container via podman on the controller. test_operator uses the same image and runs tempest in a pod on the OCP cluster. Depends-On: openstack-k8s-operators/ci-framework#1065
Closing as this was a workaround, and the issues fixes have been split into different PRs. |
The version of the telemetry-tempest-plugin in the tempest container is behind master.
The test in the tempest image require gnocchi, which is not included by the telemetry operator. In order to test the telemetry-operator tempest job, the newer version of the telemetry-tempest-plugin needs to be used.
In order to test this, the tempest role has been modified to update the version of telemetery-tempest-plugin to be included.
As a pull request owner and reviewers, I checked that: