bug 2101012: Release 4.8 go getter update #6380

jhixson74 · 2022-09-20T22:42:43Z

No description provided.

openshift-ci · 2022-09-20T22:42:46Z

@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.8 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 · 2022-09-21T16:49:48Z

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

expected Bugzilla bug 2101012 to depend on a bug targeting a release in 4.9.0, 4.9.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 2101012: Release 4.8 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 · 2022-09-21T22:01:52Z

/override bugzilla/valid-bug

openshift-ci · 2022-09-21T22:02:22Z

@jhixson74: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

bugzilla/valid-bug

Only the following failed contexts/checkruns were expected:

ci/prow/e2e-aws
ci/prow/e2e-aws-fips
ci/prow/e2e-aws-workers-rhel7
ci/prow/e2e-azure-resourcegroup
ci/prow/e2e-crc
ci/prow/e2e-libvirt
ci/prow/e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-metal-single-node-live-iso
ci/prow/e2e-openstack
ci/prow/e2e-openstack-kuryr
ci/prow/e2e-ovirt
ci/prow/gofmt
ci/prow/golint
ci/prow/govet
ci/prow/images
ci/prow/openstack-manifests
ci/prow/shellcheck
ci/prow/tf-fmt
ci/prow/tf-lint
ci/prow/unit
ci/prow/verify-codegen
ci/prow/verify-vendor
ci/prow/yaml-lint
pull-ci-openshift-installer-agent-installer-e2e-aws
pull-ci-openshift-installer-agent-installer-gofmt
pull-ci-openshift-installer-agent-installer-golint
pull-ci-openshift-installer-agent-installer-govet
pull-ci-openshift-installer-agent-installer-images
pull-ci-openshift-installer-agent-installer-unit
pull-ci-openshift-installer-agent-installer-verify-codegen
pull-ci-openshift-installer-agent-installer-verify-vendor
pull-ci-openshift-installer-fcos-e2e-openstack
pull-ci-openshift-installer-master-e2e-crc
pull-ci-openshift-installer-master-e2e-libvirt
pull-ci-openshift-installer-master-e2e-metal-ipi-ovn-ipv6
pull-ci-openshift-installer-master-e2e-metal-single-node-live-iso
pull-ci-openshift-installer-master-e2e-openstack-kuryr
pull-ci-openshift-installer-master-e2e-ovirt
pull-ci-openshift-installer-master-openstack-manifests
pull-ci-openshift-installer-master-shellcheck
pull-ci-openshift-installer-master-tf-fmt
pull-ci-openshift-installer-master-tf-lint
pull-ci-openshift-installer-master-yaml-lint
pull-ci-openshift-installer-release-4.10-e2e-aws-fips
pull-ci-openshift-installer-release-4.10-e2e-azure-resourcegroup
pull-ci-openshift-installer-release-4.6-e2e-aws-workers-rhel7
tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

Details

In response to this:

/override bugzilla/valid-bug

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 · 2022-09-21T22:05:13Z

/bugzilla refresh

openshift-ci · 2022-09-21T22:05:18Z

@r4f4: This pull request references Bugzilla bug 2101012, which is invalid:

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

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

jhixson74 · 2022-09-26T18:28:36Z

/retest

jstuever · 2022-10-12T16:03:50Z

/cc @patrickdillon
/uncc

openshift-ci · 2022-10-14T20:48:45Z

@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:

OCPBUGSM-45995: Release 4.8 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-robot · 2022-10-14T20:49:38Z

@jhixson74: No Jira issue with key OCPBUGS-45995 exists in the tracker at https://issues.redhat.com/.
Once a valid bug is referenced in the title of this pull request, request a bug refresh with /jira refresh.

Details

In response to this:

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-10-14T20:49:38Z

@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:

OCPBUGS-45995: Release 4.8 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 · 2022-10-14T20:49:46Z

/bugzilla refresh

openshift-ci · 2022-10-14T20:49:49Z

@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:

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

jhixson74 · 2022-10-14T20:50:17Z

/jira refresh

openshift-ci-robot · 2022-10-14T20:50:19Z

@jhixson74: No Jira issue with key OCPBUGS-45995 exists in the tracker at https://issues.redhat.com/.
Once a valid bug is referenced in the title of this pull request, request a bug refresh with /jira refresh.

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 · 2022-10-14T20:52:15Z

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

expected dependent Bugzilla bug 2101013 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 2101012: Release 4.8 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 · 2022-12-16T01:00:40Z

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

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

openshift-bot · 2022-12-17T01:00:33Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-12-17T01:00:41Z

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

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

openshift-bot · 2022-12-18T01:00:33Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-12-18T01:00:42Z

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

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

openshift-bot · 2022-12-19T01:00:37Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-12-19T01:00:47Z

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

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

openshift-bot · 2022-12-20T01:00:22Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-12-20T01:00:49Z

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

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

openshift-bot · 2022-12-21T01:00:49Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-12-21T01:01:06Z

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

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

openshift-bot · 2022-12-22T01:00:49Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-12-22T01:01:02Z

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

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

openshift-bot · 2022-12-23T01:01:11Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-12-23T01:01:29Z

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

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

openshift-bot · 2022-12-24T01:01:11Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-12-24T01:01:22Z

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

Requesting review from QA contact:
/cc @gpei

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.

patrickdillon · 2023-01-19T15:53:11Z

/bugzilla refresh

openshift-ci · 2023-01-19T15:53:18Z

@patrickdillon: This pull request references Bugzilla bug 2101012, which is valid.

6 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target release (4.8.z) matches configured target release for branch (4.8.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
dependent bug Bugzilla bug 2101013 is in the state CLOSED (ERRATA), which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
dependent Bugzilla bug 2101013 targets the "4.9.z" release, which is one of the valid target releases: 4.9.0, 4.9.z
bug has dependents

Requesting review from QA contact:
/cc @gpei

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 · 2023-01-19T15:54:05Z

/approve
/label backport-risk-assessed

openshift-ci · 2023-01-19T15:55:06Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: patrickdillon

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:

~~OWNERS~~ [patrickdillon]

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

gpei · 2023-01-20T00:30:16Z

/label cherry-pick-approved

openshift-ci · 2023-01-20T00:35:17Z

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

openshift/installer#6380

Bugzilla bug 2101012 has been moved to the MODIFIED state.

Details

In response to this:

bug 2101012: Release 4.8 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 bot requested review from jstuever and rna-afk September 20, 2022 22:44

jhixson74 changed the title ~~Release 4.8 go getter update~~ bug 2101012: Release 4.8 go getter update Sep 21, 2022

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 bot requested review from patrickdillon and removed request for jstuever October 12, 2022 16:03

jhixson74 changed the title ~~bug 2101012: Release 4.8 go getter update~~ OCPBUGSM-45995: Release 4.8 go getter update Oct 14, 2022

openshift-ci bot removed 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 Oct 14, 2022

jhixson74 changed the title ~~OCPBUGSM-45995: Release 4.8 go getter update~~ OCPBUGS-45995: Release 4.8 go getter update Oct 14, 2022

jhixson74 changed the title ~~OCPBUGS-45995: Release 4.8 go getter update~~ bug 2101012: Release 4.8 go getter update Oct 14, 2022

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 Oct 14, 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 Dec 24, 2022

openshift-ci bot requested a review from gpei December 24, 2022 01:01

openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jan 19, 2023

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 19, 2023

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 Jan 20, 2023

openshift-merge-robot merged commit 84453a1 into openshift:release-4.8 Jan 20, 2023

bug 2101012: Release 4.8 go getter update #6380

bug 2101012: Release 4.8 go getter update #6380

Uh oh!

Conversation

jhixson74 commented Sep 20, 2022

Uh oh!

openshift-ci bot commented Sep 20, 2022

Uh oh!

openshift-ci bot commented Sep 21, 2022

Uh oh!

jhixson74 commented Sep 21, 2022

Uh oh!

openshift-ci bot commented Sep 21, 2022

Uh oh!

r4f4 commented Sep 21, 2022

Uh oh!

openshift-ci bot commented Sep 21, 2022

Uh oh!

jhixson74 commented Sep 26, 2022

Uh oh!

jstuever commented Oct 12, 2022

Uh oh!

openshift-ci bot commented Oct 14, 2022

Uh oh!

openshift-ci-robot commented Oct 14, 2022

Uh oh!

openshift-ci bot commented Oct 14, 2022

Uh oh!

jhixson74 commented Oct 14, 2022

Uh oh!

openshift-ci bot commented Oct 14, 2022

Uh oh!

jhixson74 commented Oct 14, 2022

Uh oh!

openshift-ci-robot commented Oct 14, 2022

Uh oh!

openshift-ci bot commented Oct 14, 2022

Uh oh!

openshift-ci bot commented Dec 16, 2022

Uh oh!

openshift-bot commented Dec 17, 2022

Uh oh!

openshift-ci bot commented Dec 17, 2022

Uh oh!

openshift-bot commented Dec 18, 2022

Uh oh!

openshift-ci bot commented Dec 18, 2022

Uh oh!

openshift-bot commented Dec 19, 2022

Uh oh!

openshift-ci bot commented Dec 19, 2022

Uh oh!

openshift-bot commented Dec 20, 2022

Uh oh!

openshift-ci bot commented Dec 20, 2022

Uh oh!

openshift-bot commented Dec 21, 2022

Uh oh!

openshift-ci bot commented Dec 21, 2022

Uh oh!

openshift-bot commented Dec 22, 2022

Uh oh!

openshift-ci bot commented Dec 22, 2022

Uh oh!

openshift-bot commented Dec 23, 2022

Uh oh!

openshift-ci bot commented Dec 23, 2022

Uh oh!

openshift-bot commented Dec 24, 2022

Uh oh!

openshift-ci bot commented Dec 24, 2022

Uh oh!

patrickdillon commented Jan 19, 2023

Uh oh!

openshift-ci bot commented Jan 19, 2023

Uh oh!

patrickdillon commented Jan 19, 2023

Uh oh!

openshift-ci bot commented Jan 19, 2023

Uh oh!