Bug 2095329: [release-4.10] Bump go to v1.17 (#922) by perdasilva · Pull Request #310 · openshift/operator-framework-olm

perdasilva · 2022-05-27T15:41:04Z

This commit updates the operator-registry's go version
to v1.17.

Signed-off-by: Alexander Greene greene.al1991@gmail.com
Upstream-repository: operator-registry
Upstream-commit: c970d617ce2d77c096102e2d881a15ef680bacf9

openshift-ci · 2022-05-27T15:41:07Z

@perdasilva: 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] Bump go to v1.17 (#922)

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 · 2022-05-27T15:41:47Z

@perdasilva: This pull request references Bugzilla bug 2083919, which is invalid:

expected the bug to target the "4.10.z" release, but it targets "---" instead
expected Bugzilla bug 2083919 to depend on a bug targeting a release in 4.11.0 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 2083919: [release-4.10] Bump go to v1.17 (#922)

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.

perdasilva · 2022-05-27T15:43:02Z

/bugzilla refresh

openshift-ci · 2022-05-27T15:43:06Z

@perdasilva: This pull request references Bugzilla bug 2083919, which is invalid:

expected Bugzilla bug 2083919 to depend on a bug targeting a release in 4.11.0 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:

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

timflannagan · 2022-05-27T15:44:06Z

/lgtm

openshift-bot · 2022-05-28T01:00:31Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-05-28T01:00:34Z

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

expected the bug to target the "4.10.z" release, but it targets "---" instead
expected Bugzilla bug 2083919 to depend on a bug targeting a release in 4.11.0 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:

/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 · 2022-05-29T01:01:00Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-05-29T01:01:06Z

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

expected the bug to target the "4.10.z" release, but it targets "---" instead
expected Bugzilla bug 2083919 to depend on a bug targeting a release in 4.11.0 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:

/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 · 2022-05-30T01:01:06Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-05-30T01:01:09Z

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

expected the bug to target the "4.10.z" release, but it targets "---" instead
expected Bugzilla bug 2083919 to depend on a bug targeting a release in 4.11.0 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:

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

jianzhangbjz · 2022-06-03T08:27:40Z

/bugzilla refresh

openshift-ci · 2022-06-03T08:27:43Z

@jianzhangbjz: This pull request references Bugzilla bug 2083919, which is invalid:

expected Bugzilla bug 2083919 to depend on a bug targeting a release in 4.11.0 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:

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

bandrade · 2022-06-06T02:59:28Z

/label cherry-pick-approved

timflannagan · 2022-06-07T20:06:25Z

It looks like we don't have a 4.11 parent BZ, so we'll need to retarget the referenced BZ to 4.11 and verify that first before we can start the backport process to the release-4.10 branch.

/hold

perdasilva · 2022-06-09T11:42:59Z

It looks like we don't have a 4.11 parent BZ, so we'll need to retarget the referenced BZ to 4.11 and verify that first before we can start the backport process to the release-4.10 branch.

/hold

Does that make sense though? 4.11 is already on go1.17

timflannagan · 2022-06-09T13:31:01Z

I think the intention is to make sure the proper backport chain has been followed, and in cases like this it doesn't make much sense as 4.11 is already on Go 1.17, and so we'd need to either flip a 4.11 BZ to MODIFIED/ON_QA/VERIFIED and create a cherry-pick 4.10 BZ here in order to make the BZ bot, or we'd have someone override that valid-bug label.

perdasilva · 2022-06-09T14:00:30Z

/label backport-risk-assessed

openshift-ci · 2022-06-09T14:42:05Z

@perdasilva: This pull request references Bugzilla bug 2095329, which is invalid:

expected dependent Bugzilla bug 2083919 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:

Bug 2095329: [release-4.10] Bump go to v1.17 (#922)

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.

timflannagan · 2022-06-09T14:44:02Z

/hold cancel
/lgtm

openshift-bot · 2022-06-10T01:01:12Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-06-10T01:01:28Z

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

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

Details

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.

jianzhangbjz · 2022-06-10T01:55:40Z

/bugzilla refresh

openshift-ci · 2022-06-10T01:55:58Z

@jianzhangbjz: This pull request references Bugzilla bug 2095329, 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 release (4.10.z) matches configured target release for branch (4.10.z)
bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
dependent bug Bugzilla bug 2083919 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
dependent Bugzilla bug 2083919 targets the "4.11.0" release, which is one of the valid target releases: 4.11.0
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Bugzilla (bandrade@redhat.com), 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.

jianzhangbjz · 2022-06-10T01:56:24Z

/label cherry-pick-approved

openshift-ci · 2022-06-10T01:58:29Z

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

openshift/operator-framework-olm#310

Bugzilla bug 2095329 has been moved to the MODIFIED state.

Details

In response to this:

Bug 2095329: [release-4.10] Bump go to v1.17 (#922)

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.

perdasilva · 2022-06-10T14:00:36Z

/bugzilla refresh

openshift-ci · 2022-06-10T14:00:41Z

@perdasilva: Bugzilla bug 2095329 is in an unrecognized state (VERIFIED) and will not be moved to the MODIFIED state.

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.

Signed-off-by: Joe Lanford <joe.lanford@gmail.com> Upstream-repository: api Upstream-commit: 0d032b99c9cf9b73445ad9f5f46485d58a39a7e9

perdasilva changed the title ~~[release-4.10] Bump go to v1.17 (#922)~~ Bug 2083919: [release-4.10] Bump go to v1.17 (#922) May 27, 2022

openshift-ci Bot added bugzilla/severity-medium Referenced Bugzilla bug's severity is medium 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 May 27, 2022

openshift-ci Bot requested review from ankitathomas and njhale May 27, 2022 15:41

openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 27, 2022

openshift-ci Bot assigned timflannagan May 27, 2022

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 27, 2022

perdasilva force-pushed the operator-registry-go-bump branch from 8ecb2d1 to c88dcc6 Compare May 30, 2022 06:57

openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label May 30, 2022

perdasilva force-pushed the operator-registry-go-bump branch 3 times, most recently from cc8120c to fc86d73 Compare May 30, 2022 08:51

openshift-ci Bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 30, 2022

perdasilva force-pushed the operator-registry-go-bump branch from fc86d73 to 7f8ad59 Compare May 30, 2022 09:18

perdasilva closed this May 30, 2022

perdasilva force-pushed the operator-registry-go-bump branch from 7f8ad59 to 1a99acb Compare May 30, 2022 09:19

openshift-ci Bot removed the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 30, 2022

perdasilva reopened this May 30, 2022

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 Jun 6, 2022

openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 7, 2022

openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jun 9, 2022

perdasilva changed the title ~~Bug 2083919: [release-4.10] Bump go to v1.17 (#922)~~ Bug 2095329: [release-4.10] Bump go to v1.17 (#922) Jun 9, 2022

openshift-ci Bot added lgtm Indicates that a PR is ready to be merged. and removed do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Jun 9, 2022

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 Jun 10, 2022

openshift-merge-robot merged commit c10b001 into openshift:release-4.10 Jun 10, 2022

openshift-bot mentioned this pull request Jan 11, 2024

NO-ISSUE: Synchronize From Upstream Repositories #656

Closed

tmshort mentioned this pull request Jan 16, 2024

NO-ISSUE: Synchronize From Upstream Repositories #659

Merged

Conversation

perdasilva commented May 27, 2022

Uh oh!

openshift-ci Bot commented May 27, 2022

Uh oh!

openshift-ci Bot commented May 27, 2022

Uh oh!

perdasilva commented May 27, 2022

Uh oh!

openshift-ci Bot commented May 27, 2022

Uh oh!

timflannagan commented May 27, 2022

Uh oh!

openshift-bot commented May 28, 2022

Uh oh!

openshift-ci Bot commented May 28, 2022

Uh oh!

openshift-bot commented May 29, 2022

Uh oh!

openshift-ci Bot commented May 29, 2022

Uh oh!

openshift-bot commented May 30, 2022

Uh oh!

openshift-ci Bot commented May 30, 2022

Uh oh!

jianzhangbjz commented Jun 3, 2022

Uh oh!

openshift-ci Bot commented Jun 3, 2022

Uh oh!

bandrade commented Jun 6, 2022

Uh oh!

timflannagan commented Jun 7, 2022

Uh oh!

perdasilva commented Jun 9, 2022

Uh oh!

timflannagan commented Jun 9, 2022

Uh oh!

perdasilva commented Jun 9, 2022

Uh oh!

openshift-ci Bot commented Jun 9, 2022

Uh oh!

timflannagan commented Jun 9, 2022

Uh oh!

openshift-bot commented Jun 10, 2022

Uh oh!

openshift-ci Bot commented Jun 10, 2022

Uh oh!

jianzhangbjz commented Jun 10, 2022

Uh oh!

openshift-ci Bot commented Jun 10, 2022

Uh oh!

jianzhangbjz commented Jun 10, 2022

Uh oh!

openshift-ci Bot commented Jun 10, 2022

Uh oh!

perdasilva commented Jun 10, 2022

Uh oh!

openshift-ci Bot commented Jun 10, 2022

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants