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

[18.0-fr1] Remove DS tigger PoC content #2713

Open
wants to merge 1 commit into
base: 18.0-fr1
Choose a base branch
from

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #2703

/assign pablintino

Copy link

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

Nodeset centos-9-multinode-rhel-9-2-crc-extracted-2-39-0-3xl-novacells does not match existing definition in branch main

The problem appears in the the "centos-9-multinode-rhel-9-2-crc-extracted-2-39-0-3xl-novacells" nodeset stanza:

nodeset:
name: centos-9-multinode-rhel-9-2-crc-extracted-2-39-0-3xl-novacells
nodes:
- name: controller
label: cloud-centos-9-stream-tripleo
- name: crc
label: coreos-crc-extracted-2-39-0-3xl
- name: undercloud
label: cloud-rhel-9-2-tripleo
...

in "openstack-k8s-operators/ci-framework/zuul.d/[email protected]", line 150

@github-actions github-actions bot marked this pull request as draft February 5, 2025 08:46
Copy link

github-actions bot commented Feb 5, 2025

Thanks for the PR! ❤️
I'm marking it as a draft, once your happy with it merging and the PR is passing CI, click the "Ready for review" button below.

@frenzyfriday frenzyfriday enabled auto-merge (rebase) February 5, 2025 08:51
Copy link
Contributor

openshift-ci bot commented Feb 5, 2025

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by:

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:

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

@pablintino pablintino force-pushed the cherry-pick-2703-to-18.0-fr1 branch from 462c255 to c4117de Compare February 20, 2025 13:56
Copy link

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

Job downstream-va-hci-trigger-job not defined

The problem appears in the the "architecture-downstream-va-hci-trigger-job" job stanza:

job:
name: architecture-downstream-va-hci-trigger-job
parent: downstream-va-hci-trigger-job
description: |
This job will trigger a VA HCI job downstream.
We can invoke this job by adding following comment
\trigger github-experimental in the github pull request comment.
These jobs runs in github-experimental-trigger pipeline.
files:
...

in "openstack-k8s-operators/architecture/zuul.d/trigger-jobs.yaml@main", line 1

@pablintino pablintino force-pushed the cherry-pick-2703-to-18.0-fr1 branch from c4117de to 2150760 Compare February 25, 2025 09:19
Copy link

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

Job downstream-va-hci-trigger-job not defined

The problem appears in the the "architecture-downstream-va-hci-trigger-job" job stanza:

job:
name: architecture-downstream-va-hci-trigger-job
parent: downstream-va-hci-trigger-job
description: |
This job will trigger a VA HCI job downstream.
We can invoke this job by adding following comment
\trigger github-experimental in the github pull request comment.
These jobs runs in github-experimental-trigger pipeline.
files:
...

in "openstack-k8s-operators/architecture/zuul.d/trigger-jobs.yaml@main", line 1

@pablintino
Copy link
Contributor

I need to cleanup the architecture repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants