Skip to content

Conversation

@jhixson74
Copy link
Member

This should be able to cherry-pick into 4.9 and 4.8 with few hassles

Update go-getter to v1.6.2 to address several vulnerabilities.
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 15, 2022

@jhixson74: 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 go getter update

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 jstuever and rna-afk September 15, 2022 16:59
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 15, 2022

@jhixson74: 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-azurestack-upi 8a1cffe link false /test e2e-azurestack-upi
ci/prow/e2e-aws-single-node 8a1cffe link false /test e2e-aws-single-node
ci/prow/e2e-openstack-kuryr 8a1cffe link false /test e2e-openstack-kuryr
ci/prow/e2e-azurestack 8a1cffe link false /test e2e-azurestack
ci/prow/e2e-libvirt 8a1cffe link false /test e2e-libvirt
ci/prow/okd-e2e-vsphere 8a1cffe link false /test okd-e2e-vsphere
ci/prow/e2e-openstack 8a1cffe link false /test e2e-openstack
ci/prow/e2e-crc 8a1cffe link false /test e2e-crc
ci/prow/e2e-azure-upi 8a1cffe link false /test e2e-azure-upi
ci/prow/e2e-alibaba 8a1cffe link false /test e2e-alibaba
ci/prow/e2e-ibmcloud 8a1cffe link false /test e2e-ibmcloud

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.

@r4f4
Copy link
Contributor

r4f4 commented Sep 21, 2022

/retitle Bug 2101014: Release 4.10 go getter update

@openshift-ci openshift-ci bot changed the title Release 4.10 go getter update Bug 2101014: Release 4.10 go getter update Sep 21, 2022
@openshift-ci openshift-ci bot added bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Sep 21, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 21, 2022

@jhixson74: This pull request references Bugzilla bug 2101014, which is invalid:

  • expected dependent Bugzilla bug 2101015 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead

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

Details

In response to this:

Bug 2101014: Release 4.10 go getter update

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.

@sadasu
Copy link
Contributor

sadasu commented Oct 12, 2022

/bugzilla refresh

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 12, 2022

@sadasu: This pull request references Bugzilla bug 2101014, which is invalid:

  • expected dependent Bugzilla bug 2101015 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is MODIFIED instead

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

Details

In response to this:

/bugzilla 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.

@sadasu
Copy link
Contributor

sadasu commented Oct 12, 2022

/retest-required

@jstuever
Copy link
Contributor

/cc @patrickdillon
/uncc

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

sadasu commented Oct 14, 2022

/bugzilla refresh

@openshift-ci openshift-ci bot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Oct 14, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 14, 2022

@sadasu: This pull request references Bugzilla bug 2101014, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.10.z) matches configured target release for branch (4.10.z)
  • bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 2101015 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
  • dependent Bugzilla bug 2101015 targets the "4.11.z" release, which is one of the valid target releases: 4.11.0, 4.11.z
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Bugzilla ([email protected]), skipping review request.

Details

In response to this:

/bugzilla 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.

@sadasu
Copy link
Contributor

sadasu commented Oct 14, 2022

/retest-required

@sadasu
Copy link
Contributor

sadasu commented Oct 14, 2022

/approve

@sadasu
Copy link
Contributor

sadasu commented Oct 18, 2022

/retest-required

@sadasu
Copy link
Contributor

sadasu commented Oct 18, 2022

/lgtm

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

sadasu commented Oct 18, 2022

/retest-required

@sadasu
Copy link
Contributor

sadasu commented Oct 19, 2022

/label backport-risk-assessed

@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 Oct 19, 2022
@sadasu
Copy link
Contributor

sadasu commented Oct 21, 2022

/retest-required

@patrickdillon
Copy link
Contributor

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 24, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: patrickdillon, sadasu

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 Oct 24, 2022
@gpei
Copy link
Contributor

gpei commented Oct 25, 2022

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Oct 25, 2022
@openshift-merge-robot openshift-merge-robot merged commit 1ffe666 into openshift:release-4.10 Oct 25, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 25, 2022

@jhixson74: All pull requests linked via external trackers have merged:

Bugzilla bug 2101014 has been moved to the MODIFIED state.

Details

In response to this:

Bug 2101014: Release 4.10 go getter update

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.

@elfosardo
Copy link
Contributor

/cherry-pick release-4.9

@openshift-cherrypick-robot

@elfosardo: #6361 failed to apply on top of branch "release-4.9":

Applying: go.mod: update go-getter to v1.6.2
Using index info to reconstruct a base tree...
M	go.mod
Falling back to patching base and 3-way merge...
Auto-merging go.mod
CONFLICT (content): Merge conflict in go.mod
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 go.mod: update go-getter to v1.6.2
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

Details

In response to this:

/cherry-pick release-4.9

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 30, 2022

/cherry-pick release-4.9

@elfosardo 4.9 cherry-pick is at #6381

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. bugzilla/severity-high Referenced Bugzilla bug's severity is high 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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants