[release-4.9] Bug 2026379: update go.mod for go1.16

[joelddiaz]

No description provided.

[openshift-ci]

@joelddiaz: This pull request references Bugzilla bug 2026379, which is invalid:

• expected dependent Bugzilla bug 2026374 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.

In response to this:

[release-4.9] Bug 2026379: update go.mod for go1.16

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.

[joelddiaz]

/assign @akhil-rane
these will be all manual backports ¯_(ツ)_/¯

[akhil-rane]

/lgtm

[openshift-bot]

/retest-required

Please review the full test history for this PR and help us cut down flakes.

[joelddiaz]

/cherry-pick release-4.8

[openshift-cherrypick-robot]

@joelddiaz: once the present PR merges, I will cherry-pick it on top of release-4.8 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.8

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-bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

[openshift-ci]

@openshift-bot: This pull request references Bugzilla bug 2026379, which is invalid:

• expected dependent Bugzilla bug 2026374 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA 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.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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-bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

[openshift-ci]

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

Requesting review from QA contact:
/cc @lwan-wanglin

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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.

[joelddiaz]

@lwan-wanglin is this backport on your BZs-to-verify list?

[lwan-wanglin]

Tested today, sorry for missing this one.
Verified steps are in Bug 2026379#c1

/label qe-approved
/label backport-risk-assessed
/approve

[openshift-ci]

@lwan-wanglin: Can not set label backport-risk-assessed: Must be member in one of these teams: [openshift-patch-managers]

In response to this:

Tested today, sorry for missing this one.
Verified steps are in Bug 2026379#c1

/label qe-approved
/label backport-risk-assessed
/approve

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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: joelddiaz, lwan-wanglin

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [joelddiaz]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[lwan-wanglin]

/label cherry-pick-approved

[openshift-ci]

@lwan-wanglin: Can not set label cherry-pick-approved: Must be member in one of these teams: [openshift-patch-managers]

In response to this:

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

[lwan-wanglin]

@joelddiaz need label backport-risk-assessed

[joelddiaz]

/label backport-risk-assessed

[openshift-ci]

@joelddiaz: Can not set label backport-risk-assessed: Must be member in one of these teams: [openshift-patch-managers]

In response to this:

/label backport-risk-assessed

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.

[joelddiaz]

@lwan-wanglin with openshift/release#24245 merged, you should be able to do the ckerry-pick-approved now (and I should be able to backport-risk-assessed)

[joelddiaz]

/label backport-risk-assessesd

[openshift-ci]

@joelddiaz: The label(s) /label backport-risk-assessesd cannot be applied. These labels are supported: platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, downstream-change-needed, backport-risk-assessed, cherry-pick-approved

In response to this:

/label backport-risk-assessesd

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.

[joelddiaz]

/label backport-risk-assessed

[lwan-wanglin]

Thanks joel.
/label cherry-pick-approved

[openshift-ci]

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

• openshift/aws-pod-identity-webhook#147

Bugzilla bug 2026379 has been moved to the MODIFIED state.

In response to this:

[release-4.9] Bug 2026379: update go.mod for go1.16

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-cherrypick-robot]

@joelddiaz: new pull request created: #148

In response to this:

/cherry-pick release-4.8

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-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-aws-pod-identity-webhook-container-v4.9.0-202311250023.p0.g37a1328.assembly.stream for distgit ose-aws-pod-identity-webhook.
All builds following this will include this PR.