Skip to content

[release-4.10] OCPBUGS-377: UPI image download govc rate limit failure #6245

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.

Sign up for GitHub

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

Jump to bottom
Merged
openshift-merge-robot merged 1 commit into from
Dec 2, 2022
Merged

[release-4.10] OCPBUGS-377: UPI image download govc rate limit failure #6245

openshift-merge-robot merged 1 commit into from
Dec 2, 2022

Conversation

@openshift-cherrypick-robot
Copy link

@openshift-cherrypick-robot openshift-cherrypick-robot commented Aug 20, 2022

This is an automated cherry-pick of #6047

/assign jcpowermac

@jcpowermac
UPI image download govc rate limit failure
cf194e1 
Removing the downloading of `govc` to
workaround rate limit errors
and replacing with govc docker image
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Aug 20, 2022
Merged
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Aug 20, 2022 •
edited by openshift-ci bot
Loading

@openshift-cherrypick-robot: [Jira Issue OCPBUGS-262](https://issues.redhat.com//browse/OCPBUGS-262) has been cloned as [Jira Issue OCPBUGS-377](https://issues.redhat.com//browse/OCPBUGS-377). Retitling PR to link against new bug.
/retitle [release-4.10] OCPBUGS-377: UPI image download govc rate limit failure

Details

In response to this:

This is an automated cherry-pick of #6047

/assign jcpowermac

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/test-infra repository.

@openshift-ci openshift-ci bot changed the title [release-4.10] OCPBUGS-262: UPI image download govc rate limit failure [release-4.10] OCPBUGS-377: UPI image download govc rate limit failure Aug 20, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 20, 2022 •
edited
Loading

@openshift-cherrypick-robot: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

[release-4.10] OCPBUGS-377: UPI image download govc rate limit failure

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/test-infra repository.

@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Aug 20, 2022
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Aug 20, 2022 •
edited by openshift-ci bot
Loading

@openshift-cherrypick-robot: This pull request references [Jira Issue OCPBUGS-377](https://issues.redhat.com//browse/OCPBUGS-377), which is invalid:

  • expected dependent Jira Issue OCPBUGS-262 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is MODIFIED instead
  • expected dependent Jira Issue OCPBUGS-262 to target a version in 4.11.0, 4.11.z, but it targets "4.12.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

This is an automated cherry-pick of #6047

/assign jcpowermac

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/test-infra repository.

@openshift-ci openshift-ci bot requested review from jhixson74 and jstuever August 20, 2022 04:20
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 20, 2022

@openshift-cherrypick-robot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-ibmcloud cf194e1 link false /test e2e-ibmcloud
ci/prow/e2e-crc cf194e1 link false /test e2e-crc
ci/prow/e2e-azurestack-upi cf194e1 link false /test e2e-azurestack-upi
ci/prow/e2e-libvirt cf194e1 link false /test e2e-libvirt
ci/prow/e2e-azurestack cf194e1 link false /test e2e-azurestack
ci/prow/e2e-alibaba cf194e1 link false /test e2e-alibaba
ci/prow/okd-e2e-aws cf194e1 link false /test okd-e2e-aws
ci/prow/e2e-azure-upi cf194e1 link false /test e2e-azure-upi
ci/prow/e2e-aws-single-node cf194e1 link false /test e2e-aws-single-node
ci/prow/okd-e2e-vsphere cf194e1 link false /test okd-e2e-vsphere
ci/prow/e2e-openstack cf194e1 link false /test e2e-openstack

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

@jstuever
Copy link
Contributor

jstuever commented Oct 12, 2022

/cc @patrickdillon
/uncc

@openshift-ci openshift-ci bot requested review from patrickdillon and removed request for jstuever October 12, 2022 16:05
@patrickdillon
Copy link
Contributor

patrickdillon commented Oct 27, 2022

/jira refresh

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Oct 27, 2022

@patrickdillon: This pull request references Jira Issue OCPBUGS-377, which is invalid:

  • expected Jira Issue OCPBUGS-377 to depend on a bug targeting a version in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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 kubernetes/test-infra repository.

@r4f4
Copy link
Contributor

r4f4 commented Nov 15, 2022

/jira refresh

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Nov 15, 2022

@r4f4: This pull request references Jira Issue OCPBUGS-377, which is invalid:

  • expected dependent Jira Issue OCPBUGS-262 to target a version in 4.11.0, 4.11.z, but it targets "4.12.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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 kubernetes/test-infra repository.

@r4f4
Copy link
Contributor

r4f4 commented Nov 15, 2022

/jira refresh

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Nov 15, 2022

@r4f4: This pull request references Jira Issue OCPBUGS-377, which is invalid:

  • expected dependent Jira Issue OCPBUGS-378 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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 kubernetes/test-infra repository.

@r4f4
Copy link
Contributor

r4f4 commented Nov 18, 2022

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Nov 18, 2022
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Nov 18, 2022

@r4f4: This pull request references Jira Issue OCPBUGS-377, which is valid. The bug has been moved to the POST state.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.10.z) matches configured target version for branch (4.10.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-378 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
  • dependent Jira Issue OCPBUGS-378 targets the "4.11.z" version, which is one of the valid target versions: 4.11.0, 4.11.z
  • bug has dependents

Requesting review from QA contact:
/cc @jinyunma

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 kubernetes/test-infra repository.

@openshift-ci openshift-ci bot requested a review from jinyunma November 18, 2022 08:15
@sdodson sdodson added cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. labels Dec 2, 2022
@sdodson
Copy link
Member

sdodson commented Dec 2, 2022

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 2, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 2, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sdodson

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 Dec 2, 2022
@openshift-merge-robot openshift-merge-robot merged commit 91f9648 into openshift:release-4.10 Dec 2, 2022
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Dec 2, 2022

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-377 has been moved to the MODIFIED state.

Details

In response to this:

This is an automated cherry-pick of #6047

/assign jcpowermac

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/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jhixson74 jhixson74 Awaiting requested review from jhixson74

@patrickdillon patrickdillon Awaiting requested review from patrickdillon

@jinyunma jinyunma Awaiting requested review from jinyunma

Assignees

@sdodson sdodson

@jcpowermac jcpowermac

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. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. 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. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

8 participants

@openshift-cherrypick-robot @openshift-ci-robot @jstuever @patrickdillon @r4f4 @sdodson @jcpowermac @openshift-merge-robot