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 CRC Cloud with image based on OCP 4.16 rc4 #2019

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

danpawlik
Copy link
Contributor

This is early test PR that uses new way for deploying the CRC - crc-cloud [1] and image that is base on OCP 4.16 rc4 with small modifications [2]. In the future, that image would be created by the nodepool-builder, but right now it is just a PoC (Proof of concept). Also is worth to mention, that the base job includes few workarounds until the PR in the official projects are not merged [3][4][5]

[1] https://github.com/crc-org/crc-cloud
[2] https://softwarefactory-project.io/r/c/software-factory/sf-infra/+/31853
[3] crc-org/crc-cloud#188
[4] crc-org/crc-cloud#189
[5] crc-org/crc-cloud#190

@danpawlik danpawlik requested a review from bshewale July 3, 2024 11:35
@danpawlik danpawlik requested review from lewisdenny and removed request for bshewale and lewisdenny July 3, 2024 11:35
Copy link
Contributor

openshift-ci bot commented Jul 3, 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

@danpawlik danpawlik requested review from viroel and bshewale July 3, 2024 11:35
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:

found duplicate anchor; first occurrence
in "openstack-k8s-operators/ci-framework/zuul.d/base.yaml@main", line 130, column 24
second occurrence
in "openstack-k8s-operators/ci-framework/zuul.d/base.yaml@main", line 319, column 24

@danpawlik danpawlik requested a review from lewisdenny July 3, 2024 11:35
@danpawlik danpawlik force-pushed the crc-cloud branch 3 times, most recently from 473ebf5 to d1c7db4 Compare July 3, 2024 11:43
@danpawlik
Copy link
Contributor Author

recheck

@danpawlik
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/5df149fbb3624440805861c355c8f06f

✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 10m 35s
podified-multinode-edpm-deployment-crc RETRY_LIMIT Host unreachable in 42m 36s
✔️ cifmw-crc-podified-edpm-baremetal SUCCESS in 1h 14m 46s
podified-multinode-hci-deployment-crc RETRY_LIMIT in 1h 36m 01s
cifmw-multinode-tempest RETRY_LIMIT Host unreachable in 1h 29m 24s
✔️ noop SUCCESS in 0s
✔️ cifmw-pod-ansible-test SUCCESS in 8m 59s
✔️ cifmw-pod-pre-commit SUCCESS in 7m 42s
✔️ cifmw-pod-zuul-files SUCCESS in 4m 54s
cifmw-multinode-kuttl RETRY_LIMIT Host unreachable in 14m 50s

@danpawlik
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/178dd4b0c06f43379074b294026ce371

✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 37m 13s
podified-multinode-edpm-deployment-crc RETRY_LIMIT Host unreachable in 1h 28m 51s
✔️ cifmw-crc-podified-edpm-baremetal SUCCESS in 1h 19m 33s
podified-multinode-hci-deployment-crc RETRY_LIMIT in 1h 34m 41s
cifmw-multinode-tempest RETRY_LIMIT Host unreachable in 1h 28m 17s
✔️ noop SUCCESS in 0s
✔️ cifmw-pod-ansible-test SUCCESS in 9m 39s
✔️ cifmw-pod-pre-commit SUCCESS in 7m 54s
✔️ cifmw-pod-zuul-files SUCCESS in 4m 49s
cifmw-multinode-kuttl RETRY_LIMIT Host unreachable in 1h 27m 05s

@danpawlik
Copy link
Contributor Author

recheck

1 similar comment
@danpawlik
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/b5475b5f45ac4cea960f14d2261e0cab

✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 23m 39s
podified-multinode-edpm-deployment-crc FAILURE in 1h 13m 38s
✔️ cifmw-crc-podified-edpm-baremetal SUCCESS in 1h 25m 40s
podified-multinode-hci-deployment-crc FAILURE in 1h 50m 23s
cifmw-multinode-tempest FAILURE in 1h 16m 44s
✔️ noop SUCCESS in 0s
✔️ cifmw-pod-ansible-test SUCCESS in 8m 48s
✔️ cifmw-pod-pre-commit SUCCESS in 8m 19s
✔️ cifmw-pod-zuul-files SUCCESS in 5m 08s
cifmw-multinode-kuttl FAILURE in 45m 09s

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

✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 02m 17s
podified-multinode-edpm-deployment-crc FAILURE in 1h 13m 27s
✔️ cifmw-crc-podified-edpm-baremetal SUCCESS in 1h 27m 08s
podified-multinode-hci-deployment-crc FAILURE in 1h 47m 44s
cifmw-multinode-tempest FAILURE in 1h 18m 09s
✔️ noop SUCCESS in 0s
✔️ cifmw-pod-ansible-test SUCCESS in 9m 01s
✔️ cifmw-pod-pre-commit SUCCESS in 8m 02s
✔️ cifmw-pod-zuul-files SUCCESS in 5m 19s
cifmw-multinode-kuttl FAILURE in 1h 05m 08s

- name: compute-0
label: cloud-centos-9-stream-tripleo
- name: crc
label: crc-cloud-ocp-4-16-0-rc4-3xl
Copy link
Contributor

Choose a reason for hiding this comment

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

Usually, all I need is the nodeset. I'll upload a PR for STF with just that change.

In the meantime, I will need to check what the base-crc-cloud job does and how it differs from base extracted crc.

@danpawlik
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/a0054c0507f04b25979eae7feb64bb7c

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 30m 11s
podified-multinode-edpm-deployment-crc RETRY_LIMIT in 9m 12s
✔️ cifmw-crc-podified-edpm-baremetal SUCCESS in 1h 14m 42s
podified-multinode-hci-deployment-crc RETRY_LIMIT in 14m 43s
cifmw-multinode-tempest RETRY_LIMIT in 8m 57s
✔️ noop SUCCESS in 0s
✔️ cifmw-pod-ansible-test SUCCESS in 8m 49s
✔️ cifmw-pod-pre-commit SUCCESS in 8m 03s
✔️ cifmw-pod-zuul-files SUCCESS in 5m 04s
cifmw-multinode-kuttl RETRY_LIMIT in 7m 31s

@danpawlik danpawlik force-pushed the crc-cloud branch 2 times, most recently from e16e6ed to c044186 Compare August 14, 2024 08:09
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:

found duplicate anchor; first occurrence
in "openstack-k8s-operators/ci-framework/zuul.d/base.yaml@main", line 130, column 24
second occurrence
in "openstack-k8s-operators/ci-framework/zuul.d/base.yaml@main", line 215, column 24

@danpawlik danpawlik force-pushed the crc-cloud branch 3 times, most recently from 93b198a to 58643fd Compare August 14, 2024 09:31
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:

The nodeset "centos-9-medium-3x-centos-9-crc-cloud-ocp-4-16-xxl" was
not found.

The problem appears in the the "podified-multinode-hci-deployment-crc" job stanza:

job:
name: podified-multinode-hci-deployment-crc
parent: podified-multinode-hci-deployment-crc-3comp
nodeset: centos-9-medium-3x-centos-9-crc-cloud-ocp-4-16-xxl
vars:
cifmw_extras:
- '@scenarios/centos-9/multinode-ci.yml'
- '@scenarios/centos-9/hci_ceph_backends.yml'
cifmw_ceph_daemons_layout:
...

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

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-centos-9-crc-cloud-ocp-4-16-3xl already defined

The problem appears in the the "centos-9-medium-centos-9-crc-cloud-ocp-4-16-3xl" nodeset stanza:

nodeset:
name: centos-9-medium-centos-9-crc-cloud-ocp-4-16-3xl
nodes:
- name: controller
label: cloud-centos-9-stream-tripleo-medium
- name: compute-0
label: cloud-centos-9-stream-tripleo
- name: compute-1
label: cloud-centos-9-stream-tripleo
...

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

@pablintino
Copy link
Collaborator

@danpawlik Hi, I guess this one is obsolete?

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/5bdc55fc16ce471dae7c115ff2f29f54

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 55m 46s
podified-multinode-edpm-deployment-crc RETRY_LIMIT in 1m 15s
✔️ cifmw-crc-podified-edpm-baremetal SUCCESS in 1h 22m 19s
podified-multinode-hci-deployment-crc NODE_FAILURE Node request 099-0007590886 failed in 0s
cifmw-multinode-tempest RETRY_LIMIT in 1m 16s
✔️ noop SUCCESS in 0s
✔️ cifmw-pod-ansible-test SUCCESS in 7m 39s
✔️ cifmw-pod-pre-commit SUCCESS in 7m 36s
✔️ cifmw-pod-zuul-files SUCCESS in 4m 03s
cifmw-multinode-kuttl RETRY_LIMIT in 19m 27s
✔️ build-push-container-cifmw-client SUCCESS in 31m 10s

@danpawlik
Copy link
Contributor Author

recheck

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

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 38m 42s
podified-multinode-edpm-deployment-crc RETRY_LIMIT in 1m 15s
✔️ cifmw-crc-podified-edpm-baremetal SUCCESS in 1h 21m 38s
podified-multinode-hci-deployment-crc NODE_FAILURE Node request 099-0007592253 failed in 0s
cifmw-multinode-tempest RETRY_LIMIT in 1m 14s
✔️ noop SUCCESS in 0s
✔️ cifmw-pod-ansible-test SUCCESS in 8m 26s
✔️ cifmw-pod-pre-commit SUCCESS in 7m 07s
✔️ cifmw-pod-zuul-files SUCCESS in 4m 26s
cifmw-multinode-kuttl TIMED_OUT in 2h 10m 08s
✔️ build-push-container-cifmw-client SUCCESS in 31m 47s

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/90dd4d4c8db54951b5127778821f0606

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 42m 35s
podified-multinode-edpm-deployment-crc RETRY_LIMIT in 1m 14s
✔️ cifmw-crc-podified-edpm-baremetal SUCCESS in 1h 22m 41s
podified-multinode-hci-deployment-crc NODE_FAILURE Node request 099-0007593292 failed in 0s
cifmw-multinode-tempest RETRY_LIMIT in 1m 15s
✔️ noop SUCCESS in 0s
✔️ cifmw-pod-ansible-test SUCCESS in 8m 57s
✔️ cifmw-pod-pre-commit SUCCESS in 9m 03s
✔️ cifmw-pod-zuul-files SUCCESS in 4m 40s
cifmw-multinode-kuttl TIMED_OUT in 2h 10m 11s
✔️ build-push-container-cifmw-client SUCCESS in 30m 46s

@danpawlik
Copy link
Contributor Author

recheck

@danpawlik
Copy link
Contributor Author

So currently jobs are failing...because jobs are spawned on IBM, where most of the playbooks were done for other cloud provider.

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/9b0a261403f245f3bb61078c39c013cb

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 38m 55s
podified-multinode-edpm-deployment-crc RETRY_LIMIT in 1m 14s
✔️ cifmw-crc-podified-edpm-baremetal SUCCESS in 1h 26m 50s
podified-multinode-hci-deployment-crc NODE_FAILURE Node request 099-0007594380 failed in 0s
cifmw-multinode-tempest RETRY_LIMIT in 1m 13s
✔️ noop SUCCESS in 0s
✔️ cifmw-pod-ansible-test SUCCESS in 6m 46s
✔️ cifmw-pod-pre-commit SUCCESS in 6m 45s
✔️ cifmw-pod-zuul-files SUCCESS in 4m 06s
✔️ cifmw-multinode-kuttl SUCCESS in 2h 00m 52s
✔️ build-push-container-cifmw-client SUCCESS in 32m 02s

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

✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 11m 47s
podified-multinode-edpm-deployment-crc RETRY_LIMIT in 1m 21s
✔️ cifmw-crc-podified-edpm-baremetal SUCCESS in 1h 26m 54s
podified-multinode-hci-deployment-crc NODE_FAILURE Node request 099-0007595253 failed in 0s
cifmw-multinode-tempest RETRY_LIMIT in 1m 19s
✔️ noop SUCCESS in 0s
✔️ cifmw-pod-ansible-test SUCCESS in 7m 05s
✔️ cifmw-pod-pre-commit SUCCESS in 6m 58s
✔️ cifmw-pod-zuul-files SUCCESS in 4m 13s
cifmw-multinode-kuttl FAILURE in 34m 01s
✔️ build-push-container-cifmw-client SUCCESS in 30m 16s

@danpawlik
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://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/87f4fbe52b28499381422ca68fdd15f0

✔️ openstack-k8s-operators-content-provider SUCCESS in 36m 18s
podified-multinode-edpm-deployment-crc RETRY_LIMIT in 1m 12s
cifmw-crc-podified-edpm-baremetal RETRY_LIMIT in 13m 36s
podified-multinode-hci-deployment-crc NODE_FAILURE Node request 099-0007596226 failed in 0s
cifmw-multinode-tempest RETRY_LIMIT in 1m 14s
✔️ noop SUCCESS in 0s
✔️ cifmw-pod-ansible-test SUCCESS in 8m 01s
✔️ cifmw-pod-pre-commit SUCCESS in 8m 07s
✔️ cifmw-pod-zuul-files SUCCESS in 4m 24s
cifmw-multinode-kuttl FAILURE in 35m 32s
✔️ build-push-container-cifmw-client SUCCESS in 32m 00s

This is early test PR that uses new way for deploying the CRC -
crc-cloud [1] and image that is base on OCP 4.16.
with small modifications [2]. In the future, that image would be created
by the nodepool-builder, but right now it is just a PoC (Proof of concept).
Also is worth to mention, that the base job includes few workarounds
until the PR in the official projects are not merged [3][4][5]

[1] https://github.com/crc-org/crc-cloud
[2] https://softwarefactory-project.io/r/c/software-factory/sf-infra/+/31853
[3] crc-org/crc-cloud#188
[4] crc-org/crc-cloud#189
[5] crc-org/crc-cloud#190
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/86fa1d0f3467435bbf5a2b9d696748a7

✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 30m 55s
✔️ podified-multinode-edpm-deployment-crc SUCCESS in 1h 25m 10s
✔️ cifmw-crc-podified-edpm-baremetal SUCCESS in 1h 26m 59s
podified-multinode-hci-deployment-crc NODE_FAILURE Node request 099-0007596369 failed in 0s
✔️ cifmw-multinode-tempest SUCCESS in 1h 45m 10s
✔️ noop SUCCESS in 0s
✔️ cifmw-pod-ansible-test SUCCESS in 7m 48s
✔️ cifmw-pod-pre-commit SUCCESS in 6m 47s
✔️ cifmw-pod-zuul-files SUCCESS in 4m 32s
cifmw-multinode-kuttl TIMED_OUT in 2h 09m 28s
✔️ build-push-container-cifmw-client SUCCESS in 31m 15s

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.

5 participants