Skip to content

[release-4.19] USHIFT-6086: Disable CentOS images and scenarios in 4.19 branch#5406

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.19from
ggiguash:no-centos-images-scenarios-419
Sep 5, 2025
Merged

[release-4.19] USHIFT-6086: Disable CentOS images and scenarios in 4.19 branch#5406
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.19from
ggiguash:no-centos-images-scenarios-419

Conversation

@ggiguash
Copy link
Contributor

@ggiguash ggiguash commented Sep 5, 2025

No description provided.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 5, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 5, 2025

@ggiguash: This pull request references USHIFT-6086 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.z" version, but no target version was set.

Details

In response to this:

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from agullon and jerpeter1 September 5, 2025 06:25
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 5, 2025
@ggiguash ggiguash force-pushed the no-centos-images-scenarios-419 branch from 9b44328 to 7eea145 Compare September 5, 2025 06:52
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 5, 2025

@ggiguash: 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.

@ggiguash
Copy link
Contributor Author

ggiguash commented Sep 5, 2025

/label backport-risk-assessed
/label jira/valid-bug
/verified by CI

@openshift-ci openshift-ci bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Sep 5, 2025
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Sep 5, 2025
@openshift-ci-robot
Copy link

@ggiguash: This PR has been marked as verified by CI.

Details

In response to this:

/label backport-risk-assessed
/label jira/valid-bug
/verified by CI

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 openshift-eng/jira-lifecycle-plugin repository.

Copy link
Contributor

@pacevedom pacevedom left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 5, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 5, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, pacevedom

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

The pull request process is described 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-merge-bot openshift-merge-bot bot merged commit 17a43d3 into openshift:release-4.19 Sep 5, 2025
11 checks passed
@ggiguash ggiguash deleted the no-centos-images-scenarios-419 branch September 9, 2025 12:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants