Skip to content

bug 2101013: Release 4.9 go getter update #6381

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 3 commits into from
Dec 5, 2022
Merged

bug 2101013: Release 4.9 go getter update #6381

openshift-merge-robot merged 3 commits into from
Dec 5, 2022

Conversation

@jhixson74
Copy link
Member

@jhixson74 jhixson74 commented Sep 20, 2022

No description provided.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 20, 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.9 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.

@jhixson74 jhixson74 changed the title Release 4.9 go getter update bug 2101013: Release 4.9 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 2101013, which is invalid:

  • expected Bugzilla bug 2101013 to depend on a bug targeting a release in 4.10.0, 4.10.z and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but no dependents were found

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 2101013: Release 4.9 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.

@jstuever
Copy link
Contributor

jstuever commented Oct 12, 2022

/cc @patrickdillon
/uncc

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

patrickdillon commented Nov 1, 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 Nov 1, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 1, 2022

@patrickdillon: This pull request references Bugzilla bug 2101013, which is valid. 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.9.z) matches configured target release for branch (4.9.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 2101014 is in the state RELEASE_PENDING, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
  • dependent Bugzilla bug 2101014 targets the "4.10.z" release, which is one of the valid target releases: 4.10.0, 4.10.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.

@patrickdillon
Copy link
Contributor

patrickdillon commented Nov 1, 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 Nov 1, 2022
@sadasu
Copy link
Contributor

sadasu commented Nov 1, 2022

/retest-required

@sadasu
Copy link
Contributor

sadasu commented Nov 1, 2022

/approve

@sadasu
Copy link
Contributor

sadasu commented Nov 2, 2022

/retest-required

@sadasu
Copy link
Contributor

sadasu commented Nov 2, 2022

/lgtm

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

sadasu commented Nov 3, 2022

/retest-required

@gpei
Copy link
Contributor

gpei commented Nov 11, 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 Nov 11, 2022
@r4f4 r4f4 mentioned this pull request Nov 30, 2022
Merged
@jhixson74
Copy link
Member Author

jhixson74 commented Dec 1, 2022

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 1, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jhixson74, 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 Dec 1, 2022
@jhixson74
Copy link
Member Author

jhixson74 commented Dec 1, 2022

/hold

verify-vendor is failing

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 1, 2022
@jhixson74
go.mod: update go-getter to v1.6.2
2f006e6 
Update go-getter to v1.6.2 to address several vulnerabilities.
@jhixson74
go.mod: update go-getter to v1.6.2
9e5e179 
go mod tidy
@jhixson74
go.mod: update go-getter to v1.6.2
9bf462b 
go mod vendor
@jhixson74 jhixson74 force-pushed the release-4.9-go-getter-update branch from 1c968c5 to 9bf462b Compare December 2, 2022 00:14
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Dec 2, 2022
@jhixson74
Copy link
Member Author

jhixson74 commented Dec 2, 2022

/test e2e-aws
/test e2e-libvirt
/test e2e-openstack
/test okd-e2e-aws

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 2, 2022 •
edited
Loading

@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-metal-single-node-live-iso 9bf462b link false /test e2e-metal-single-node-live-iso
ci/prow/e2e-crc 9bf462b link false /test e2e-crc

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.

@jhixson74
Copy link
Member Author

jhixson74 commented Dec 5, 2022

/test e2e-aws
/test e2e-libvirt
/test e2e-openstack
/test okd-e2e-aws

@jhixson74
Copy link
Member Author

jhixson74 commented Dec 5, 2022

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 5, 2022
@r4f4
Copy link
Contributor

r4f4 commented Dec 5, 2022

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 5, 2022
@r4f4 r4f4 removed their assignment Dec 5, 2022
@r4f4 r4f4 mentioned this pull request Dec 5, 2022
Merged
@openshift-merge-robot openshift-merge-robot merged commit f079984 into openshift:release-4.9 Dec 5, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 5, 2022

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

Bugzilla bug 2101013 has been moved to the MODIFIED state.

Details

In response to this:

bug 2101013: Release 4.9 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.

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

Reviewers

@patrickdillon patrickdillon Awaiting requested review from patrickdillon

Assignees

@sadasu sadasu

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

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

7 participants

@jhixson74 @jstuever @patrickdillon @sadasu @gpei @r4f4 @openshift-merge-robot