Skip to content

USHIFT-4082: [release-4.16] Increase dnf low-bitrate timeout#3817

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.16from
openshift-cherrypick-robot:cherry-pick-3500-to-release-4.16
Aug 27, 2024
Merged

USHIFT-4082: [release-4.16] Increase dnf low-bitrate timeout#3817
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.16from
openshift-cherrypick-robot:cherry-pick-3500-to-release-4.16

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #3500

/assign copejon

…rates, which triggers an error message but is not fatal. since it's desirable to sometimes fail due to an error (just not this one), the best option is to give the transfer some extra time to recover

Signed-off-by: Jon Cope <jcope@redhat.com>
@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 26, 2024

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: USHIFT-3270

Details

In response to this:

This is an automated cherry-pick of #3500

/assign copejon

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.

@copejon
Copy link
Contributor

copejon commented Aug 26, 2024

/cc copejon

@openshift-ci openshift-ci bot requested a review from copejon August 26, 2024 21:45
@copejon
Copy link
Contributor

copejon commented Aug 26, 2024

USHIFT-4082

/jira refresh

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

openshift-ci-robot commented Aug 26, 2024

@copejon: This pull request references USHIFT-3270 which is a valid jira issue.

Details

In response to this:

USHIFT-4082

/jira refresh

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.

@copejon copejon changed the title [release-4.16] USHIFT-3270: Increase dnf low-bitrate timeout [release-4.16] Increase dnf low-bitrate timeout Aug 26, 2024
@openshift-ci-robot openshift-ci-robot removed the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 26, 2024
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

Details

In response to this:

This is an automated cherry-pick of #3500

/assign copejon

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.

@copejon
Copy link
Contributor

copejon commented Aug 26, 2024

/jira refresh

@openshift-ci-robot
Copy link

@copejon: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

Details

In response to this:

/jira refresh

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.

@copejon copejon changed the title [release-4.16] Increase dnf low-bitrate timeout [USHIFT-4082] [release-4.16] Increase dnf low-bitrate timeout Aug 26, 2024
@copejon
Copy link
Contributor

copejon commented Aug 26, 2024

/jira refresh

@openshift-ci-robot
Copy link

@copejon: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

Details

In response to this:

/jira refresh

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.

@copejon copejon changed the title [USHIFT-4082] [release-4.16] Increase dnf low-bitrate timeout USHIFT-4082: [release-4.16] Increase dnf low-bitrate timeout Aug 26, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 26, 2024

@openshift-cherrypick-robot: This pull request references USHIFT-4082 which is a valid jira issue.

Details

In response to this:

This is an automated cherry-pick of #3500

/assign copejon

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 Aug 26, 2024
@copejon
Copy link
Contributor

copejon commented Aug 26, 2024

/backport-risk-assessed
/cherry-pick-approved
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 26, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 26, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: copejon, openshift-cherrypick-robot

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-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 26, 2024
@copejon
Copy link
Contributor

copejon commented Aug 26, 2024

/label backport-risk-assessed
/label cherry-pick-approved

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Aug 26, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 26, 2024

@copejon: Can not set label cherry-pick-approved: Must be member in one of these teams: []

Details

In response to this:

/label backport-risk-assessed
/label cherry-pick-approved

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.

@copejon
Copy link
Contributor

copejon commented Aug 26, 2024

It failed during the build phase because it could not contact any RHSM repos.

/retest

@copejon
Copy link
Contributor

copejon commented Aug 26, 2024

The CDN issues appear to be wide spread. Holding on retesting until it's fixed.

@copejon
Copy link
Contributor

copejon commented Aug 27, 2024

/retest

@ggiguash
Copy link
Contributor

/label cherry-pick-approved
/label jira/valid-bug

@openshift-ci openshift-ci bot added cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Aug 27, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 27, 2024

@openshift-cherrypick-robot: 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.

@openshift-merge-bot openshift-merge-bot bot merged commit 71a1aa8 into openshift:release-4.16 Aug 27, 2024
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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants