[zuul] Add a CloudKitty CI job #720

elfiesmelfie · 2025-07-09T17:12:17Z

Add in a job that deploys CloudKitty and runs tempest tests.

Depends-On: openstack-k8s-operators/install_yamls#1120
Depends-On: #796

openshift-ci · 2025-07-09T17:12:22Z

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

openshift-ci · 2025-07-09T17:12:24Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: elfiesmelfie

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:

~~OWNERS~~ [elfiesmelfie]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

softwarefactory-project-zuul · 2025-07-09T17:12:24Z

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

found duplicate anchor; first occurrence
in "openstack-k8s-operators/telemetry-operator/zuul.d/projects.yaml@main", line 29, column 23
second occurrence
in "openstack-k8s-operators/telemetry-operator/zuul.d/projects.yaml@main", line 141, column 23

softwarefactory-project-zuul · 2025-07-09T20:00:46Z

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

found undefined alias
in "openstack-k8s-operators/telemetry-operator/zuul.d/projects.yaml@main", line 108, column 17

softwarefactory-project-zuul · 2025-07-10T12:49:30Z

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

found undefined alias
in "openstack-k8s-operators/telemetry-operator/zuul.d/projects.yaml@main", line 108, column 17

softwarefactory-project-zuul · 2025-07-10T22:45:27Z

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

found undefined alias
in "openstack-k8s-operators/telemetry-operator/zuul.d/projects.yaml@main", line 108, column 17

softwarefactory-project-zuul · 2025-07-11T00:23:22Z

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://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/a04ae0818bb6479dbc9f067e9c96ee05

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 32m 43s
✔️ podified-multinode-edpm-deployment-crc SUCCESS in 1h 09m 10s
✔️ telemetry-openstack-meta-content-provider-master SUCCESS in 1h 29m 40s
✔️ telemetry-operator-multinode-default-telemetry SUCCESS in 1h 14m 04s
❌ functional-graphing-tests-osp18 FAILURE in 1h 04m 41s (non-voting)
❌ functional-autoscaling-tests-osp18 RETRY_LIMIT in 8m 48s
✔️ functional-logging-tests-osp18 SUCCESS in 1h 08m 11s

mgirgisf · 2025-07-14T09:30:11Z

recheck

softwarefactory-project-zuul · 2025-07-16T15:14:48Z

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

while scanning a simple key
in "openstack-k8s-operators/telemetry-operator/zuul.d/projects.yaml@main", line 161, column 1
could not find expected ':'
in "openstack-k8s-operators/telemetry-operator/zuul.d/projects.yaml@main", line 164, column 9

softwarefactory-project-zuul · 2025-07-16T16:49:17Z

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://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/1b4fbfe0345c4bd9b1baf25bce920b50

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 31m 37s
✔️ podified-multinode-edpm-deployment-crc SUCCESS in 1h 12m 53s
❌ telemetry-operator-multinode-cloudkitty FAILURE in 16m 17s
✔️ telemetry-openstack-meta-content-provider-master SUCCESS in 36m 57s

softwarefactory-project-zuul · 2025-07-16T19:22:55Z

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://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/d480b4fa1b29468d857750e3e995f034

❌ telemetry-operator-multinode-cloudkitty FAILURE in 1h 07m 15s
✔️ telemetry-openstack-meta-content-provider-master SUCCESS in 1h 31m 22s

softwarefactory-project-zuul · 2025-07-17T14:40:54Z

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://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/6f02549e96de45a0897ab3f328aa2f46

❌ telemetry-operator-multinode-cloudkitty FAILURE in 17m 08s
✔️ telemetry-openstack-meta-content-provider-master SUCCESS in 38m 01s

softwarefactory-project-zuul · 2025-07-17T16:45:19Z

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://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/0181658ddc5342bbbcd3835f9876b740

❌ telemetry-operator-multinode-cloudkitty FAILURE in 1h 10m 01s
✔️ telemetry-openstack-meta-content-provider-master SUCCESS in 1h 33m 31s

softwarefactory-project-zuul · 2025-07-17T19:04:21Z

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://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/ba2c7f058c5a41228c7dc67d04cd1e2c

❌ telemetry-operator-multinode-cloudkitty FAILURE in 1h 10m 12s
✔️ telemetry-openstack-meta-content-provider-master SUCCESS in 1h 30m 32s

softwarefactory-project-zuul · 2025-07-18T16:04:51Z

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://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/db0d2ed7e31140aa90f720c45e50adbd

❌ telemetry-operator-multinode-cloudkitty FAILURE in 1h 14m 00s
✔️ telemetry-openstack-meta-content-provider-master SUCCESS in 1h 35m 58s

ci/vars-cloudkitty-tempest.yml

elfiesmelfie · 2025-11-24T17:31:31Z

ci/vars-cloudkitty-tempest.yml

+      service_available.sg_core false
+      service_available.aodh false
+      service_available.cinder false
+      telemetry.prometheus_service_url "https://metric-storage-prometheus.openstack.svc.cluster.local:9090"
+      telemetry.ceilometer_polling_interval 120
+      telemetry.prometheus_scrape_interval 30
+      telemetry.alarm_threshold 50000000000


Suggested change

service_available.sg_core false

service_available.aodh false

service_available.cinder false

telemetry.prometheus_service_url "https://metric-storage-prometheus.openstack.svc.cluster.local:9090"

telemetry.ceilometer_polling_interval 120

telemetry.prometheus_scrape_interval 30

telemetry.alarm_threshold 50000000000

elfiesmelfie · 2025-11-24T17:31:48Z

ci/vars-cloudkitty-tempest.yml

+cifmw_test_operator_tempest_include_list: |
+  ^tempest.*\[.*\bsmoke\b.*\]
+  cloudkitty_tempest_plugin.*
+  telemetry_tempest_plugin.*


Suggested change

telemetry_tempest_plugin.*

Do we want the telemetry tests here or not? I'm OK with either, but I'm confused by the suggestion still being here.

zuul.d/projects.yaml

ci/vars-cloudkitty-tempest.yml

ci/deploy-loki-for-ck.yaml

softwarefactory-project-zuul · 2025-11-24T20:34:01Z

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

mapping values are not allowed in this context
in "openstack-k8s-operators/telemetry-operator/zuul.d/projects.yaml@main", line 168, column 17

elfiesmelfie · 2025-11-25T01:14:16Z

/retest telemetry-operator-build-deploy-kuttl

openshift-ci · 2025-11-25T01:14:20Z

@elfiesmelfie: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

/test images

/test precommit-check

/test telemetry-operator-build-deploy-kuttl

The following commands are available to trigger optional jobs:

/test telemetry-operator-build-deploy

Use /test all to run all jobs.

In response to this:

/retest telemetry-operator-build-deploy-kuttl

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-sigs/prow repository.

elfiesmelfie · 2025-11-25T01:23:38Z

/test telemetry-operator-build-deploy-kuttl

elfiesmelfie · 2025-11-25T12:50:49Z

ci/cloudkitty-pre_deploy-install_loki.yml

+        zuul:
+          projects:
+            github.com/openstack-k8s-operators/telemetry-operator:
+              src_dir: "{{ telemetry_operator_dir | default('telemetry-operator/') }}"


This is so that the playbook can be run locally.

Add a pre_deploy hook to install loki-operator for CloudKitty deployment Add a pre_deploy hook to create the oscp kustomization to enable cloudkitty * add s3storageConfig secret * Enable metricsStorage in telemetry to provide prometheus for storage * Configure storageClass for CloudKitty in configure-cloudkitty hook Set the storageClass to crc-csi-hostpath-provisioner for CloudKitty deployment in CRC-based CI jobs. This prevents the need to increase PVC allocations in install_yamls by using the default storage class available in CRC, which allocates storage as required.

elfiesmelfie · 2025-11-25T18:17:30Z

/test telemetry-operator-build-deploy-kuttl

elfiesmelfie · 2025-11-26T19:12:22Z

/test telemetry-operator-build-deploy-kuttl

elfiesmelfie · 2025-11-27T19:59:51Z

recheck

elfiesmelfie · 2025-11-27T20:00:16Z

/test telemetry-operator-build-deploy-kuttl

elfiesmelfie · 2025-12-01T12:32:33Z

/test telemetry-operator-build-deploy-kuttl

vyzigold · 2025-12-02T09:24:23Z

ci/cloudkitty-pre_deploy-install_loki.yml

+
+    - name: Set the loki-operator version to pin the version
+      ansible.builtin.set_fact:
+        loki_operator_version: "v6.3.0"


Small thing. I see this variable actually doesn't influence what version will get installed and deploy-loki-for-ck.yaml has the 6.3.0 hardcoded. Can you add a comment somewhere here noting that? I don't want to get into a situation in the future, where we'll want to use a different version of the operator and we'll be surprised that just changing the version here doesn't achieve the goal.

This is true. There should be some template rendered with the vars in it, if we're to use this.

I can address this in a follow-up so that we can merge this and get the test coverage.
I'll add a comment for now, and push a follow-up MR later today.

Sounds good.

Loki-operator needs to be pinned to 6.3.0, because 6.3.1 has this issue: https://issues.redhat.com/browse/LOG-7752

vyzigold · 2025-12-02T17:15:51Z

/lgtm

openshift-ci bot added the do-not-merge/work-in-progress label Jul 9, 2025

openshift-ci bot added the approved label Jul 9, 2025

elfiesmelfie force-pushed the efoley/cloud-kitty-job branch from 0f6903d to 2734457 Compare July 9, 2025 20:00

elfiesmelfie force-pushed the efoley/cloud-kitty-job branch from 2734457 to 594af57 Compare July 10, 2025 12:49

elfiesmelfie force-pushed the efoley/cloud-kitty-job branch from 594af57 to 4609689 Compare July 10, 2025 22:45

elfiesmelfie force-pushed the efoley/cloud-kitty-job branch from 4609689 to a7ad3f4 Compare July 10, 2025 22:49

elfiesmelfie force-pushed the efoley/cloud-kitty-job branch from a7ad3f4 to b083962 Compare July 16, 2025 15:14

elfiesmelfie force-pushed the efoley/cloud-kitty-job branch from b083962 to 522ead5 Compare July 16, 2025 15:16

elfiesmelfie force-pushed the efoley/cloud-kitty-job branch from 1cc7fcf to 2c52232 Compare July 17, 2025 14:02

elfiesmelfie force-pushed the efoley/cloud-kitty-job branch from 2c52232 to f0582c3 Compare July 17, 2025 15:09

elfiesmelfie removed the approved label Jul 17, 2025

elfiesmelfie force-pushed the efoley/cloud-kitty-job branch from f0582c3 to 15750b1 Compare July 17, 2025 17:08

openshift-ci bot added the approved label Jul 17, 2025

elfiesmelfie force-pushed the efoley/cloud-kitty-job branch from a2cf2ee to 2e117cc Compare July 18, 2025 14:27

jlarriba reviewed Jul 21, 2025

View reviewed changes

ci/vars-cloudkitty-tempest.yml Show resolved Hide resolved

elfiesmelfie commented Nov 24, 2025

View reviewed changes

vyzigold reviewed Nov 24, 2025

View reviewed changes

zuul.d/projects.yaml Outdated Show resolved Hide resolved

vyzigold reviewed Nov 24, 2025

View reviewed changes

ci/vars-cloudkitty-tempest.yml Show resolved Hide resolved

vyzigold reviewed Nov 24, 2025

View reviewed changes

ci/deploy-loki-for-ck.yaml Outdated Show resolved Hide resolved

elfiesmelfie mentioned this pull request Nov 24, 2025

Add Cloudkitty CI Job #777

Closed

elfiesmelfie force-pushed the efoley/cloud-kitty-job branch from 57284e3 to 898f69d Compare November 24, 2025 20:33

elfiesmelfie force-pushed the efoley/cloud-kitty-job branch from 898f69d to 56ac70d Compare November 24, 2025 20:43

elfiesmelfie commented Nov 25, 2025

View reviewed changes

elfiesmelfie force-pushed the efoley/cloud-kitty-job branch 2 times, most recently from 529af33 to 9e56d12 Compare November 25, 2025 14:16

elfiesmelfie force-pushed the efoley/cloud-kitty-job branch from 9e56d12 to dbb3429 Compare November 25, 2025 14:22

vyzigold reviewed Dec 2, 2025

View reviewed changes

[ci] Pin loki-operator version to 6.3.0

54fb11e

Loki-operator needs to be pinned to 6.3.0, because 6.3.1 has this issue: https://issues.redhat.com/browse/LOG-7752

elfiesmelfie force-pushed the efoley/cloud-kitty-job branch from dbb3429 to 54fb11e Compare December 2, 2025 13:04

openshift-ci bot assigned vyzigold Dec 2, 2025

openshift-ci bot added the lgtm label Dec 2, 2025

openshift-merge-bot bot merged commit 873139a into openstack-k8s-operators:main Dec 2, 2025
6 checks passed

elfiesmelfie deleted the efoley/cloud-kitty-job branch December 2, 2025 18:13

ayefimov-1 mentioned this pull request Dec 5, 2025

Add synthetic data generation files and changes infrawatch/feature-verification-tests#331

Open

[zuul] Add a CloudKitty CI job #720

[zuul] Add a CloudKitty CI job #720

Conversation

elfiesmelfie commented Jul 9, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci bot commented Jul 9, 2025

Uh oh!

openshift-ci bot commented Jul 9, 2025

Uh oh!

softwarefactory-project-zuul bot commented Jul 9, 2025

Uh oh!

softwarefactory-project-zuul bot commented Jul 9, 2025

Uh oh!

softwarefactory-project-zuul bot commented Jul 10, 2025

Uh oh!

softwarefactory-project-zuul bot commented Jul 10, 2025

Uh oh!

softwarefactory-project-zuul bot commented Jul 11, 2025 • edited by elfiesmelfie Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

mgirgisf commented Jul 14, 2025

Uh oh!

softwarefactory-project-zuul bot commented Jul 16, 2025

Uh oh!

softwarefactory-project-zuul bot commented Jul 16, 2025 • edited by elfiesmelfie Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

softwarefactory-project-zuul bot commented Jul 16, 2025

Uh oh!

softwarefactory-project-zuul bot commented Jul 17, 2025

Uh oh!

softwarefactory-project-zuul bot commented Jul 17, 2025

Uh oh!

softwarefactory-project-zuul bot commented Jul 17, 2025

Uh oh!

softwarefactory-project-zuul bot commented Jul 18, 2025

Uh oh!

Uh oh!

elfiesmelfie Nov 24, 2025

Choose a reason for hiding this comment

Uh oh!

elfiesmelfie Nov 24, 2025

Choose a reason for hiding this comment

Uh oh!

vyzigold Dec 2, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

softwarefactory-project-zuul bot commented Nov 24, 2025

Uh oh!

elfiesmelfie commented Nov 25, 2025

Uh oh!

openshift-ci bot commented Nov 25, 2025

Uh oh!

elfiesmelfie commented Nov 25, 2025

Uh oh!

elfiesmelfie Nov 25, 2025

Choose a reason for hiding this comment

Uh oh!

elfiesmelfie commented Nov 25, 2025

Uh oh!

elfiesmelfie commented Nov 26, 2025

Uh oh!

elfiesmelfie commented Nov 27, 2025

Uh oh!

elfiesmelfie commented Nov 27, 2025

Uh oh!

elfiesmelfie commented Dec 1, 2025

Uh oh!

vyzigold Dec 2, 2025

Choose a reason for hiding this comment

Uh oh!

elfiesmelfie Dec 2, 2025

Choose a reason for hiding this comment

Uh oh!

vyzigold Dec 2, 2025

Choose a reason for hiding this comment

elfiesmelfie commented Jul 9, 2025 •

edited

Loading

softwarefactory-project-zuul bot commented Jul 11, 2025 •

edited by elfiesmelfie

Loading

softwarefactory-project-zuul bot commented Jul 16, 2025 •

edited by elfiesmelfie

Loading