Skip to content
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

Conversation

elfiesmelfie
Copy link
Contributor

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:

  • Appropriate testing is done and actually running
  • Appropriate documentation exists and/or is up-to-date:
    • README in the role
    • Content of the docs/source is reflecting the changes

Copy link
Contributor

openshift-ci bot commented Jan 24, 2024

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

Copy link
Contributor

openshift-ci bot commented Jan 24, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign rlandy for approval. For more information see the Kubernetes Code Review Process.

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Copy link

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://review.rdoproject.org/zuul/buildset/f442300bbda24b2b8f3621f8f3fc089c

✔️ openstack-k8s-operators-content-provider SUCCESS in 37m 57s
podified-multinode-edpm-deployment-crc FAILURE in 21m 58s
✔️ noop SUCCESS in 0s
✔️ cifmw-molecule-tempest SUCCESS in 5m 56s

@elfiesmelfie
Copy link
Contributor Author

recheck

The failure was in deploying openstack.

Copy link

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://review.rdoproject.org/zuul/buildset/95d05ed7303443f5ab607f2043a52277

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 35m 38s
podified-multinode-edpm-deployment-crc FAILURE in 1h 19m 09s
✔️ noop SUCCESS in 0s
✔️ cifmw-molecule-tempest SUCCESS in 5m 39s

Copy link

Zuul encountered a syntax error while parsing its configuration in the
repo openstack-k8s-operators/ci-framework on branch main. The error
was:

expected a list for dictionary value @ data['templates']

The error appears in the following project stanza:

project:
github-check:
jobs:
- noop
#- cifmw-baremetal-nested-crc
#- cifmw-content-provider-build-images
#- cifmw-edpm-build-images
#- cifmw-multinode-kuttl
#- cifmw-tcib
#- cifmw-molecule-artifacts
#- cifmw-molecule-build_containers
#- cifmw-molecule-build_openstack_packages
#- cifmw-molecule-cert_manager
#- cifmw-molecule-ci_gen_kustomize_values
#- cifmw-molecule-ci_local_storage
#- cifmw-molecule-ci_metallb
#- cifmw-molecule-ci_multus
#- cifmw-molecule-ci_netconfig
#- cifmw-molecule-ci_network
#- cifmw-molecule-ci_nmstate
#- cifmw-molecule-ci_setup
#- cifmw-molecule-cifmw_block_device
#- cifmw-molecule-cifmw_ceph_client
#- cifmw-molecule-cifmw_ceph_spec
#- cifmw-molecule-cifmw_cephadm
#- cifmw-molecule-cifmw_create_admin
#- cifmw-molecule-cifmw_test_role
#- cifmw-molecule-copy_container
#- cifmw-molecule-devscripts
#- cifmw-molecule-discover_latest_image
#- cifmw-molecule-dlrn_promote
#- cifmw-molecule-dlrn_report
#- cifmw-molecule-edpm_build_images
#- cifmw-molecule-edpm_deploy
#- cifmw-molecule-edpm_deploy_baremetal
#- cifmw-molecule-edpm_kustomize
#- cifmw-molecule-edpm_prepare
#- cifmw-molecule-env_op_images
#- cifmw-molecule-hci_prepare
#- cifmw-molecule-hive
#- cifmw-molecule-idrac_configuration
#- cifmw-molecule-install_ca
#- cifmw-molecule-install_yamls
#- cifmw-molecule-libvirt_manager
#- cifmw-molecule-manage_secrets
#- cifmw-molecule-networking_mapper
#- cifmw-molecule-openshift_login
#- cifmw-molecule-openshift_provisioner_node
#- cifmw-molecule-openshift_setup
#- cifmw-molecule-operator_build
#- cifmw-molecule-operator_deploy
#- cifmw-molecule-os_must_gather
#- cifmw-molecule-pkg_build
#- cifmw-molecule-registry_deploy
#- cifmw-molecule-repo_setup
#- cifmw-molecule-reproducer
#- cifmw-molecule-rhol_crc
#- cifmw-molecule-run_hook
#- cifmw-molecule-set_openstack_containers
#- cifmw-molecule-tempest
#- cifmw-molecule-test_deps
#- cifmw-molecule-tobiko
#- cifmw-molecule-tofu
name: openstack-k8s-operators/ci-framework
templates:
#- podified-multinode-edpm-pipeline
#- data-plane-adoption-pipeline

in "openstack-k8s-operators/ci-framework/zuul.d/projects.yaml@main", line 1, column 3

@elfiesmelfie elfiesmelfie force-pushed the efoley-telemetry-operator-tempest-tests branch from 64a4ba7 to e7b1574 Compare January 25, 2024 13:15
Copy link

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://review.rdoproject.org/zuul/buildset/620f772e2cbe4584a25d0339e0854f05

✔️ noop SUCCESS in 0s
cifmw-molecule-tempest FAILURE in 6m 30s

@elfiesmelfie elfiesmelfie force-pushed the efoley-telemetry-operator-tempest-tests branch from fa54545 to 04f1eaa Compare January 25, 2024 19:23
Copy link

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://review.rdoproject.org/zuul/buildset/60e581058b944a27b963ef97c239c5b9

✔️ noop SUCCESS in 0s
cifmw-molecule-tempest FAILURE in 5m 09s

@elfiesmelfie elfiesmelfie force-pushed the efoley-telemetry-operator-tempest-tests branch from 04f1eaa to 292217f Compare January 25, 2024 19:55
@elfiesmelfie elfiesmelfie force-pushed the efoley-telemetry-operator-tempest-tests branch from 65d25ac to e417628 Compare January 31, 2024 19:54
elfiesmelfie added a commit to elfiesmelfie/nova-operator that referenced this pull request Feb 2, 2024
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
SeanMooney pushed a commit to elfiesmelfie/nova-operator that referenced this pull request Feb 2, 2024
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.
@openshift-merge-robot
Copy link
Contributor

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.

openshift-merge-bot bot pushed a commit to openstack-k8s-operators/nova-operator that referenced this pull request Feb 9, 2024
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
@elfiesmelfie
Copy link
Contributor Author

Closing as this was a workaround, and the issues fixes have been split into different PRs.

@elfiesmelfie elfiesmelfie deleted the efoley-telemetry-operator-tempest-tests branch February 12, 2024 19:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants