[zuul] Add update job

[elfiesmelfie]

No description provided.

[openshift-ci]

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]

[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]

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/4e708411f31e4951b8485af2c1c9a647

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 30m 30s
✔️ podified-multinode-edpm-deployment-crc SUCCESS in 1h 09m 37s
❌ telemetry-operator-multinode-autoscaling-tempest-update FAILURE in 1h 55m 47s

[elfiesmelfie]

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/4e708411f31e4951b8485af2c1c9a647

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 30m 30s ✔️ podified-multinode-edpm-deployment-crc SUCCESS in 1h 09m 37s ❌ telemetry-operator-multinode-autoscaling-tempest-update FAILURE in 1h 55m 47s

The job failed on deploy_edpm, with some timeout.
However, the jobs and content provider started at the same time, so there might be a missing dependency on the content provider

[softwarefactory-project-zuul]

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/2acf024b76814067a5d7e5122ce938ca

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 43m 45s
✔️ podified-multinode-edpm-deployment-crc SUCCESS in 1h 11m 22s
❌ telemetry-operator-multinode-autoscaling-tempest-update FAILURE in 1h 20m 11s

[softwarefactory-project-zuul]

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/05fc6a3afbbb484686f33b4af166fc4a

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 43m 10s
✔️ podified-multinode-edpm-deployment-crc SUCCESS in 1h 09m 23s
❌ telemetry-operator-multinode-autoscaling-tempest-update FAILURE in 1h 21m 51s

[elfiesmelfie]

What I should do here is run the basic update job and the non-update autoscaling-tempest job to help identify whether the issues in this new job are caused by the base job, or other settings

[softwarefactory-project-zuul]

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

expected str @ data['github-check']['jobs'][3]

The problem appears in the the "openstack-k8s-operators/telemetry-operator" project stanza:

project:
name: openstack-k8s-operators/telemetry-operator
templates:
- podified-multinode-edpm-pipeline
github-check:
jobs:
- telemetry-operator-multinode-autoscaling-tempest:
dependencies: ["openstack-k8s-operators-content-provider"]
- telemetry-operator-multinode-autoscaling-tempest-update:
...

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

[softwarefactory-project-zuul]

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/0da0ad1bc013409f90c84099a25e2c6e

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 48m 04s
✔️ podified-multinode-edpm-deployment-crc SUCCESS in 1h 15m 16s
✔️ telemetry-operator-multinode-autoscaling-tempest SUCCESS in 1h 05m 33s
❌ telemetry-operator-multinode-autoscaling-tempest-update FAILURE in 1h 20m 50s
❌ podified-multinode-edpm-update-crc FAILURE in 1h 25m 44s