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

[zuul] Add telemetry-operator-multinode-autoscaling-tempest job #284

Merged
merged 16 commits into from
Feb 22, 2024

Conversation

elfiesmelfie
Copy link
Contributor

@elfiesmelfie elfiesmelfie commented Jan 22, 2024

This is a first pass, creating a tempest job based on neutron-operator. This change runs the neutron tempest tests to establish that the environment is configured correctly for tempest tests.

Depends-On: openstack-k8s-operators/ci-framework#1110
Depends-On: openstack-k8s-operators/ci-framework#1116
Depends-On: openstack-k8s-operators/tcib#132
Depends-On: #301
Depends-On: https://review.opendev.org/c/openstack/releases/+/907406
Depends-On: https://review.rdoproject.org/r/c/rdoinfo/+/51721

Copy link
Contributor

openshift-ci bot commented Jan 22, 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

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

while parsing a block mapping
in "openstack-k8s-operators/telemetry-operator/zuul.d/projects.yaml@main", line 5, column 5
did not find expected key
in "openstack-k8s-operators/telemetry-operator/zuul.d/projects.yaml@main", line 26, column 6

Copy link

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

expected a dictionary for dictionary value @ data['jobs']

The error appears in the following project stanza:

project:
name: openstack-k8s-operators/telemetry-operator
# templates:
# - podified-multinode-edpm-pipeline
# this pipeline contains: github-check:
# jobs:
# - openstack-k8s-operators-content-provider
# - podified-multinode-edpm-deployment-crc: &content_providere_edpm
# dependencies:
# - openstack-k8s-operators-content-provider
# - podified-multinode-hci-deployment-crc: *content_providere_edpm

  # Do I have the content provider available somewhere?
  # I can also temperorily inherit from one of the end-to-end deployments; which is the ci-framework tempest job.
  jobs:
    - openstack-k8s-operators-content-provider
      # The dependency on the content provider is baked into the job definition.
    - telemetry-operator-tempest-multinode

in "openstack-k8s-operators/telemetry-operator/zuul.d/projects.yaml@main", line 41, column 3

Copy link

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

extra keys not allowed @ data['jobs']['github-check']

The error appears in the following project stanza:

project:
name: openstack-k8s-operators/telemetry-operator
# templates:
# - podified-multinode-edpm-pipeline
# this pipeline contains: github-check:
# jobs:
# - openstack-k8s-operators-content-provider
# - podified-multinode-edpm-deployment-crc: &content_providere_edpm
# dependencies:
# - openstack-k8s-operators-content-provider
# - podified-multinode-hci-deployment-crc: *content_providere_edpm

  # Do I have the content provider available somewhere?
  # I can also temperorily inherit from one of the end-to-end deployments; which is the ci-framework tempest job.
  jobs:
    github-check:
      - openstack-k8s-operators-content-provider
        # The dependency on the content provider is baked into the job definition.
      - telemetry-operator-tempest-multinode

in "openstack-k8s-operators/telemetry-operator/zuul.d/projects.yaml@main", line 41, column 3

@elfiesmelfie elfiesmelfie force-pushed the efoley-zuul-tempest branch 2 times, most recently from e14421d to fcd3ccb Compare January 22, 2024 18:12
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/1d7f383411ef44b4970f9d1ecf4ac8c5

✔️ openstack-k8s-operators-content-provider SUCCESS in 44m 00s
telemetry-operator-tempest-multinode FAILURE in 21m 57s

@elfiesmelfie
Copy link
Contributor Author

recheck

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/f51a2f19db914c6088592126b8e2c8cb

✔️ openstack-k8s-operators-content-provider SUCCESS in 43m 33s
telemetry-operator-tempest-multinode FAILURE in 23m 26s

@elfiesmelfie
Copy link
Contributor Author

recheck

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/0708caf022a8452ca95273d81b70868a

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 20m 21s
telemetry-operator-tempest-multinode FAILURE in 58m 26s

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/ffd4faae0dd74bc08e03270c4d2a1509

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 18m 29s
telemetry-operator-tempest-multinode FAILURE in 58m 37s

@elfiesmelfie
Copy link
Contributor Author

elfiesmelfie commented Jan 24, 2024

recheck

I updated the PR description to add a dependency

Copy link

This change depends on a change that failed to merge.

Change openstack-k8s-operators/ci-framework#1065 is needed.

@elfiesmelfie
Copy link
Contributor Author

recheck

Copy link

This change depends on a change that failed to merge.

Change openstack-k8s-operators/ci-framework#1065 is needed.

@elfiesmelfie
Copy link
Contributor Author

recheck

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/d14a83bc586b4e0faa4b9db2445a04be

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 40m 54s
telemetry-operator-tempest-multinode FAILURE in 1h 19m 36s

@elfiesmelfie
Copy link
Contributor Author

recheck

Failure was in deploying dataplane nodes

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/58a0632ac50e4b8c861cab31df245063

✔️ openstack-k8s-operators-content-provider SUCCESS in 39m 41s
telemetry-operator-tempest-multinode MERGE_CONFLICT in 2s

Copy link

This change depends on a change with an invalid configuration.

@elfiesmelfie
Copy link
Contributor Author

recheck

The dependant change has been fixed

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/a20500abda7e45a88d48ea0101529e78

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 31m 23s
telemetry-operator-tempest-multinode RETRY_LIMIT in 1h 08m 12s

@elfiesmelfie
Copy link
Contributor Author

recheck
The job failed because of an undefined var; I typoed the name of the var in the dependant patch.
The tempest molecule job has been re-enabled in ci_framework pr1065.

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/6c9bd8ab28c84c92a9ebd63199f8a2f3

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 31m 20s
telemetry-operator-tempest-multinode FAILURE in 59m 38s

@elfiesmelfie
Copy link
Contributor Author

recheck

ci-framework change is passing molecule, meaning the image gets successfully built

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/a350ee5ac58142b69a8b8f42cad7afa3

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 29m 45s
telemetry-operator-tempest-multinode FAILURE in 1h 02m 36s

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/863c8357b0134a3899df82f8f03fce9f

openstack-k8s-operators-content-provider RETRY_LIMIT in 8s
⚠️ podified-multinode-edpm-deployment-crc SKIPPED Skipped due to failed job openstack-k8s-operators-content-provider
⚠️ telemetry-operator-multinode-autoscaling-tempest SKIPPED Skipped due to failed job openstack-k8s-operators-content-provider

@elfiesmelfie
Copy link
Contributor Author

check-rdo

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/04e9853d8d644e04b4bd4f8f0df83904

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 54m 56s
podified-multinode-edpm-deployment-crc FAILURE in 1h 00m 58s
telemetry-operator-multinode-autoscaling-tempest FAILURE in 1h 32m 07s

@elfiesmelfie
Copy link
Contributor Author

check-rdo

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/ffbcdf929d87417087ed513f4d266ea0

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 53m 27s
podified-multinode-edpm-deployment-crc FAILURE in 1h 00m 02s
telemetry-operator-multinode-autoscaling-tempest FAILURE in 1h 32m 28s

@elfiesmelfie
Copy link
Contributor Author

check-rdo

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/aee4da6f457e4c83930e2c563005fcc1

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 52m 17s
podified-multinode-edpm-deployment-crc FAILURE in 1h 00m 07s
telemetry-operator-multinode-autoscaling-tempest FAILURE in 1h 30m 47s

@elfiesmelfie
Copy link
Contributor Author

check-rdo

telemetry_tempest_plugin.scenario
telemetry_tempest_plugin.aodh
cifmw_test_operator_tempest_exclude_list: |
telemetry_tempest_plugin.scenario.test_telemetry_integration_prometheus.PrometheusGabbiTest.test_ceilometer_sg_core_integration
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm skipping this test until https://review.opendev.org/c/openstack/telemetry-tempest-plugin/+/909459 is merged.
There's a patch in progress to re-enable this test: #313

Copy link
Contributor

openshift-ci bot commented Feb 22, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: elfiesmelfie, jlarriba

The full list of commands accepted by this bot can be found here.

The pull request process is described 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

@openshift-merge-bot openshift-merge-bot bot merged commit 92f3e28 into main Feb 22, 2024
9 checks passed
@elfiesmelfie elfiesmelfie deleted the efoley-zuul-tempest branch March 6, 2024 20:23
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.

4 participants