OCPBUGS-37805: Revert go version to equal ocp 4.15 go version

SchSeba commented 3 months ago

/jira cherrypick OCPBUGS-37804

openshift-ci-robot commented 3 months ago

@SchSeba: Jira Issue OCPBUGS-37804 has been cloned as Jira Issue OCPBUGS-37805. Will retitle bug to link to clone. /retitle OCPBUGS-37805: Revert go version to equal ocp 4.15 go version

In response to [this](https://github.com/openshift/sriov-network-operator/pull/978#issuecomment-2262979161): >/jira cherrypick OCPBUGS-37804 Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fsriov-network-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

openshift-ci-robot commented 3 months ago

@SchSeba: This pull request references Jira Issue OCPBUGS-37805, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"
expected dependent Jira Issue OCPBUGS-37804 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is Closed (Not a Bug) instead
expected dependent Jira Issue OCPBUGS-37804 to target a version in 4.16.0, 4.16.z, but no target version was set

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

The bug has been updated to refer to the pull request using the external bug tracker.

In response to [this](https://github.com/openshift/sriov-network-operator/pull/978): > Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fsriov-network-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

SchSeba commented 3 months ago

/jira refresh

openshift-ci-robot commented 3 months ago

@SchSeba: This pull request references Jira Issue OCPBUGS-37805, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"

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

In response to [this](https://github.com/openshift/sriov-network-operator/pull/978#issuecomment-2262998350): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fsriov-network-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

SchSeba commented 3 months ago

/jira refresh

openshift-ci-robot commented 3 months ago

@SchSeba: This pull request references Jira Issue OCPBUGS-37805, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

* bug is open, matching expected state (open) * bug target version (4.15.z) matches configured target version for branch (4.15.z) * bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST) * release note type set to "Release Note Not Required" * dependent bug [Jira Issue OCPBUGS-37804](https://issues.redhat.com//browse/OCPBUGS-37804) is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA)) * dependent [Jira Issue OCPBUGS-37804](https://issues.redhat.com//browse/OCPBUGS-37804) targets the "4.16.z" version, which is one of the valid target versions: 4.16.0, 4.16.z * bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (elevin@redhat.com), skipping review request.

In response to [this](https://github.com/openshift/sriov-network-operator/pull/978#issuecomment-2263000965): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fsriov-network-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

zeeke commented 3 months ago

/lgtm

zeeke commented 3 months ago

/label backport-risk-assessed

openshift-ci[bot] commented 3 months ago

@SchSeba: 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-openstack-nfv	3f0a06146d304e7901c2f8c700500d7d21b1e24f	link	false	`/test e2e-openstack-nfv`
ci/prow/e2e-openstack-nfv-hwoffload	3f0a06146d304e7901c2f8c700500d7d21b1e24f	link	false	`/test e2e-openstack-nfv-hwoffload`

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).

wizhaoredhat commented 3 months ago

/lgtm

openshift-ci[bot] commented 3 months ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: SchSeba, wizhaoredhat, zeeke

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](https://github.com/openshift/sriov-network-operator/blob/release-4.15/OWNERS)~~ [SchSeba,wizhaoredhat] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

evgenLevin commented 3 months ago

/label cherry-pick-approved

openshift-ci-robot commented 3 months ago

@SchSeba: Jira Issue OCPBUGS-37805: All pull requests linked via external trackers have merged:

openshift/sriov-network-operator#978

Jira Issue OCPBUGS-37805 has been moved to the MODIFIED state.

In response to [this](https://github.com/openshift/sriov-network-operator/pull/978): > Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fsriov-network-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

openshift-bot commented 3 months ago

[ART PR BUILD NOTIFIER]

Distgit: sriov-network-webhook This PR has been included in build sriov-network-webhook-container-v4.15.0-202408050308.p0.g36ef98e.assembly.stream.el9. All builds following this will include this PR.

openshift-bot commented 3 months ago

[ART PR BUILD NOTIFIER]

Distgit: sriov-network-config-daemon This PR has been included in build sriov-network-config-daemon-container-v4.15.0-202408050308.p0.g36ef98e.assembly.stream.el9. All builds following this will include this PR.

openshift-bot commented 3 months ago

[ART PR BUILD NOTIFIER]

Distgit: sriov-network-operator This PR has been included in build sriov-network-operator-container-v4.15.0-202408050308.p0.g36ef98e.assembly.stream.el9. All builds following this will include this PR.

openshift / sriov-network-operator

OCPBUGS-37805: Revert go version to equal ocp 4.15 go version #978