openshift / ocp-release-operator-sdk

Apache License 2.0
16 stars 38 forks source link

[release-4.12] OCPBUGS-27618,OCPBUGS-27638,OCPBUGS-27643,OCPBUGS-27533,OCPBUGS-27553,OCPBUGS-27558: bump github.com/go-git/go-git/v5 to v5.11.0 #368

Closed oceanc80 closed 8 months ago

oceanc80 commented 8 months ago

Description of the change: This is a cherry-pick of https://github.com/openshift/ocp-release-operator-sdk/pull/364

Motivation for the change: Addresses the following CVEs:

https://github.com/advisories/GHSA-mw99-9chc-xw7r https://github.com/advisories/GHSA-449p-3h89-pw88

Checklist

If the pull request includes user-facing changes, extra documentation is required:

oceanc80 commented 8 months ago

/label backport-risk-assessed

openshift-ci-robot commented 8 months ago

@oceanc80: This pull request references Jira Issue OCPBUGS-27618, which is invalid:

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.

This pull request references Jira Issue OCPBUGS-27638, which is invalid:

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.

This pull request references Jira Issue OCPBUGS-27643, which is invalid:

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.

This pull request references Jira Issue OCPBUGS-27533, which is invalid:

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.

This pull request references Jira Issue OCPBUGS-27553, which is invalid:

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.

This pull request references Jira Issue OCPBUGS-27558, which is invalid:

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/ocp-release-operator-sdk/pull/368): > > >**Description of the change:** >This is a cherry-pick of https://github.com/openshift/ocp-release-operator-sdk/pull/364 > >**Motivation for the change:** >Addresses the following CVEs: > >https://github.com/advisories/GHSA-mw99-9chc-xw7r >https://github.com/advisories/GHSA-449p-3h89-pw88 > >**Checklist** > >If the pull request includes user-facing changes, extra documentation is required: >- [ ] Add a new changelog fragment in `changelog/fragments` (see [`changelog/fragments/00-template.yaml`](https://github.com/operator-framework/operator-sdk/tree/master/changelog/fragments/00-template.yaml)) >- [ ] Add or update relevant sections of the docs website in [`website/content/en/docs`](https://github.com/operator-framework/operator-sdk/tree/master/website/content/en/docs) > Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Focp-release-operator-sdk). 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[bot] commented 8 months ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: oceanc80, theishshah

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/ocp-release-operator-sdk/blob/release-4.12/OWNERS)~~ [oceanc80,theishshah] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
oceanc80 commented 8 months ago

/retest-required

KeenonLee commented 8 months ago

make build failed make[1]: [build/operator-sdk] Error 1 make: [build] Error

KeenonLee commented 8 months ago

https://mastern-jenkins-csb-openshift-qe.apps.ocp-c1.prod.psi.redhat.com/job/ocp-common/job/ginkgo-test-vm/52850/console 02-02 16:13:24.338 Feb 2 16:13:22.076: FAIL: unable to execute "operator-sdk": exec: "operator-sdk": executable file not found in $PATH

KeenonLee commented 8 months ago

/hold

openshift-ci[bot] commented 8 months ago

New changes are detected. LGTM label has been removed.

oceanc80 commented 8 months ago

/jira-refresh

openshift-ci[bot] commented 8 months ago

@oceanc80: 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/images 9a3a9f1929408661837a32260478fec02344dd22 link true /test images
ci/prow/sanity 9a3a9f1929408661837a32260478fec02344dd22 link true /test sanity
ci/prow/unit 9a3a9f1929408661837a32260478fec02344dd22 link true /test unit
ci/prow/e2e-ansible 9a3a9f1929408661837a32260478fec02344dd22 link true /test e2e-ansible
ci/prow/e2e-helm 9a3a9f1929408661837a32260478fec02344dd22 link true /test e2e-helm

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/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
openshift-ci-robot commented 8 months ago

@oceanc80: This pull request references Jira Issue OCPBUGS-27618. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state.

This pull request references Jira Issue OCPBUGS-27638. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state.

This pull request references Jira Issue OCPBUGS-27643. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state.

This pull request references Jira Issue OCPBUGS-27533. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state.

This pull request references Jira Issue OCPBUGS-27553. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state.

This pull request references Jira Issue OCPBUGS-27558. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state.

In response to [this](https://github.com/openshift/ocp-release-operator-sdk/pull/368): > > >**Description of the change:** >This is a cherry-pick of https://github.com/openshift/ocp-release-operator-sdk/pull/364 > >**Motivation for the change:** >Addresses the following CVEs: > >https://github.com/advisories/GHSA-mw99-9chc-xw7r >https://github.com/advisories/GHSA-449p-3h89-pw88 > >**Checklist** > >If the pull request includes user-facing changes, extra documentation is required: >- [ ] Add a new changelog fragment in `changelog/fragments` (see [`changelog/fragments/00-template.yaml`](https://github.com/operator-framework/operator-sdk/tree/master/changelog/fragments/00-template.yaml)) >- [ ] Add or update relevant sections of the docs website in [`website/content/en/docs`](https://github.com/operator-framework/operator-sdk/tree/master/website/content/en/docs) > Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Focp-release-operator-sdk). 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.