Skip to content

Update master CLO CI to use Vector v0.54.0#76305

Open
vparfonov wants to merge 1 commit intoopenshift:mainfrom
vparfonov:clo-vector-0.54.0
Open

Update master CLO CI to use Vector v0.54.0#76305
vparfonov wants to merge 1 commit intoopenshift:mainfrom
vparfonov:clo-vector-0.54.0

Conversation

@vparfonov
Copy link
Contributor

This PR modifies CI config for building master branch of CLO to use Vector v0.54.0

@vparfonov
Copy link
Contributor Author

/assign @jcantrill

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 16, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: vparfonov
Once this PR has been reviewed and has the lgtm label, please assign cahartma for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details 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

@openshift-ci openshift-ci bot requested review from alanconway and cahartma March 16, 2026 10:23
@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@vparfonov: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-openshift-cluster-logging-operator-master-ci-index-cluster-logging-operator-bundle openshift/cluster-logging-operator presubmit Ci-operator config changed
pull-ci-openshift-cluster-logging-operator-master-e2e-target openshift/cluster-logging-operator presubmit Ci-operator config changed
pull-ci-openshift-cluster-logging-operator-master-functional-target openshift/cluster-logging-operator presubmit Ci-operator config changed
pull-ci-openshift-cluster-logging-operator-master-images openshift/cluster-logging-operator presubmit Ci-operator config changed
pull-ci-openshift-cluster-logging-operator-master-lint openshift/cluster-logging-operator presubmit Ci-operator config changed
pull-ci-openshift-cluster-logging-operator-master-unit openshift/cluster-logging-operator presubmit Ci-operator config changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 16, 2026

@vparfonov: all tests passed!

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

@vparfonov
Copy link
Contributor Author

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants