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

DNM - Checking CI jobs with CRC 2.48 - OCP 4.18 #2780

Closed

Conversation

danpawlik
Copy link
Contributor

No description provided.

Copy link
Contributor

openshift-ci bot commented Mar 7, 2025

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 Mar 7, 2025

[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 bshewale for approval. For more information see the 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

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

Nodeset centos-9-medium-2x-centos-9-crc-extracted-2-39-0-xxl already defined

The problem appears in the the "centos-9-medium-2x-centos-9-crc-extracted-2-39-0-xxl" nodeset stanza:

nodeset:
name: centos-9-medium-2x-centos-9-crc-extracted-2-39-0-xxl
nodes:
- name: controller
label: cloud-centos-9-stream-tripleo-medium
# Note(Chandan Kumar): Switch to xxl nodeset once RHOSZUUL-1940 resolves
- name: compute-0
label: cloud-centos-9-stream-tripleo
- name: compute-1
...

in "openstack-k8s-operators/ci-framework/zuul.d/nodeset.yaml@main", line 476

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

✔️ openstack-k8s-operators-content-provider SUCCESS in 3h 34m 58s
✔️ podified-multinode-edpm-deployment-crc SUCCESS in 1h 14m 44s
cifmw-crc-podified-edpm-baremetal RETRY_LIMIT in 13m 30s
✔️ podified-multinode-hci-deployment-crc SUCCESS in 1h 35m 30s
✔️ cifmw-multinode-tempest SUCCESS in 1h 33m 22s
✔️ adoption-standalone-to-crc-ceph-provider SUCCESS in 3h 13m 18s
✔️ noop SUCCESS in 0s
✔️ cifmw-pod-ansible-test SUCCESS in 8m 09s
✔️ cifmw-pod-pre-commit SUCCESS in 8m 19s
✔️ cifmw-pod-zuul-files SUCCESS in 4m 30s
cifmw-multinode-kuttl FAILURE in 25m 08s
✔️ build-push-container-cifmw-client SUCCESS in 22m 28s

@bshewale
Copy link
Contributor

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

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 51m 34s
✔️ podified-multinode-edpm-deployment-crc SUCCESS in 1h 07m 22s
✔️ cifmw-crc-podified-edpm-baremetal SUCCESS in 1h 28m 30s
podified-multinode-hci-deployment-crc RETRY_LIMIT in 27m 58s
✔️ cifmw-multinode-tempest SUCCESS in 1h 25m 29s
adoption-standalone-to-crc-ceph-provider FAILURE in 1h 33m 43s
✔️ noop SUCCESS in 0s
✔️ cifmw-pod-ansible-test SUCCESS in 8m 25s
✔️ cifmw-pod-pre-commit SUCCESS in 7m 36s
✔️ cifmw-pod-zuul-files SUCCESS in 4m 27s
cifmw-multinode-kuttl RETRY_LIMIT in 4m 28s
✔️ build-push-container-cifmw-client SUCCESS in 27m 14s

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

@danpawlik danpawlik closed this Mar 27, 2025
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.

3 participants