Remove custom nodesets and use inherited one

[cescgina]

After [1] merged the parent ci-framework jobs are using 4.18 crc cloud
nodeset, this change removes the custom nodeset and uses the one from
the parent job.

[1] openstack-k8s-operators/ci-framework#2819

[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

[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/33aec48daf3e478b8e0d8dbb51740f9b

✔️ openstack-meta-content-provider-master SUCCESS in 2h 12m 38s
✔️ watcher-operator-validation-master SUCCESS in 1h 59m 14s
❌ watcher-operator-validation-ocp4-16 RETRY_LIMIT in 53m 14s
✔️ noop SUCCESS in 0s
✔️ watcher-operator-validation SUCCESS in 1h 51m 50s
✔️ watcher-operator-kuttl SUCCESS in 44m 15s

[cescgina]

Since all the jobs but the 4.16 are working with the crc-cloud change, I'm proposing in this PR making the 4.16 job non-voting until the issues are resolved.

[SeanMooney]

i would prefer to keep the 4.16 job voting but not move ti to CRC cloud and keep it with extracted until the issue is resovled

[cescgina]

i would prefer to keep the 4.16 job voting but not move ti to CRC cloud and keep it with extracted until the issue is resovled

agreed, we're looking at how to achieve that ,but we need changes in the ci-framework base jobs. Setting it non-voting is a quick way to unblock our CI temporarily, we can decide depending on the urgency and how long the ci-framework changes take

[danpawlik]

recheck

[cescgina]

i would prefer to keep the 4.16 job voting but not move ti to CRC cloud and keep it with extracted until the issue is resovled

agreed, we're looking at how to achieve that ,but we need changes in the ci-framework base jobs. Setting it non-voting is a quick way to unblock our CI temporarily, we can decide depending on the urgency and how long the ci-framework changes take

I marked the 4.16 as voting again, we fixed the base job problem and it seems to be working

[amoralej]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: amoralej

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

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

[amoralej]

FTR, this is using crc-extracted for 4.16 job:

2025-04-08 07:32:53.467040 | localhost | Distro: RedHat 4.16
2025-04-08 07:32:53.467082 | localhost | Provider: vexxhost-nodepool-tripleo
2025-04-08 07:32:53.467120 | localhost | Label: coreos-crc-extracted-2-39-0-xxl

And crc-cloud for 4.18:

2025-04-08 07:27:08.783898 | localhost | Distro: RedHat 4.18
2025-04-08 07:27:08.783917 | localhost | Provider: vexxhost-nodepool-tripleo
2025-04-08 07:27:08.783934 | localhost | Label: crc-cloud-ocp-4-18-1-xxl

[raukadah]

/lgtm