Skip to content

[release-4.20] USHIFT-6348: Retry brew access verification#5809

Merged
openshift-merge-bot[bot] merged 2 commits intoopenshift:release-4.20from
agullon:patch-33
Nov 27, 2025
Merged

[release-4.20] USHIFT-6348: Retry brew access verification#5809
openshift-merge-bot[bot] merged 2 commits intoopenshift:release-4.20from
agullon:patch-33

Conversation

@agullon
Copy link
Contributor

@agullon agullon commented Nov 26, 2025

No description provided.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 26, 2025

@agullon: This pull request explicitly references no jira issue.

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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Nov 26, 2025
@openshift-ci openshift-ci bot requested review from ggiguash and jogeo November 26, 2025 10:38
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 26, 2025
@agullon
Copy link
Contributor Author

agullon commented Nov 26, 2025

/test e2e-aws-tests-cache e2e-aws-tests-cache-arm

@agullon
Copy link
Contributor Author

agullon commented Nov 26, 2025

/retest

@agullon agullon changed the title [release-4.20] NO-ISSUE: Add retry logic for curl command to check brew access [release-4.20] USHIFT-6348: Cache job must fail when RPM packages are NOT downloaded from brew Nov 26, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 26, 2025 •
edited by openshift-ci bot
Loading

@agullon: This pull request references USHIFT-6348 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 bug to target the "4.20.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.

@agullon
Copy link
Contributor Author

agullon commented Nov 26, 2025

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 26, 2025

@agullon: 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

ggiguash commented Nov 27, 2025 •
edited by openshift-ci bot
Loading

/retitle [release-4.20] USHIFT-6348: Retry brew access verification
/lgtm
/label backport-risk-assessed
/label jira/valid-bug
/verified by ci

@openshift-ci openshift-ci bot changed the title [release-4.20] USHIFT-6348: Cache job must fail when RPM packages are NOT downloaded from brew [release-4.20] USHIFT-6348: Retry brew access verification Nov 27, 2025
@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 Nov 27, 2025
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Nov 27, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 27, 2025 •
edited by openshift-ci bot
Loading

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

Details

In response to this:

/retitle [release-4.20] USHIFT-6348: Retry brew access verification
/lgtm
/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.

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

openshift-ci bot commented Nov 27, 2025

[APPROVALNOTIFIER] This PR is APPROVED

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

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 69ba10b into openshift:release-4.20 Nov 27, 2025
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@ggiguash ggiguash Awaiting requested review from ggiguash

@jogeo jogeo Awaiting requested review from jogeo

Assignees

@ggiguash ggiguash

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

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@agullon @openshift-ci-robot @ggiguash