[release-4.14] OCPBUGS-27620,OCPBUGS-27640,OCPBUGS-27645,OCPBUGS-27535,OCPBUGS-27555,OCPBUGS-27560: bump github.com/go-git/go-git/v5 to v5.11.0 #366

[openshift-cherrypick-robot]

This is an automated cherry-pick of #364

/assign oceanc80

[oceanc80]

/label backport-risk-assessed

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-27807 has been cloned as Jira Issue OCPBUGS-28218. Will retitle bug to link to clone.

Jira Issue OCPBUGS-27806 has been cloned as Jira Issue OCPBUGS-28219. Will retitle bug to link to clone.

Jira Issue OCPBUGS-27805 has been cloned as Jira Issue OCPBUGS-28220. Will retitle bug to link to clone.

Jira Issue OCPBUGS-27810 has been cloned as Jira Issue OCPBUGS-28221. Will retitle bug to link to clone.

Jira Issue OCPBUGS-27811 has been cloned as Jira Issue OCPBUGS-28222. Will retitle bug to link to clone.

Jira Issue OCPBUGS-27812 has been cloned as Jira Issue OCPBUGS-28223. Will retitle bug to link to clone. /retitle [release-4.14] OCPBUGS-28218,OCPBUGS-28219,OCPBUGS-28220,OCPBUGS-28221,OCPBUGS-28222,OCPBUGS-28223: bump github.com/go-git/go-git/v5 to v5.11.0

In response to [this](https://github.com/openshift/ocp-release-operator-sdk/pull/366): >This is an automated cherry-pick of #364 > >/assign oceanc80 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-robot]

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-28218, which is invalid:

• expected dependent Jira Issue OCPBUGS-27807 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead
• expected dependent Jira Issue OCPBUGS-27807 to target a version in 4.15.0, but it targets "4.16.0" instead

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-28219, which is invalid:

• expected dependent Jira Issue OCPBUGS-27806 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead
• expected dependent Jira Issue OCPBUGS-27806 to target a version in 4.15.0, but it targets "4.16.0" instead

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-28220, which is invalid:

• expected dependent Jira Issue OCPBUGS-27805 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead
• expected dependent Jira Issue OCPBUGS-27805 to target a version in 4.15.0, but it targets "4.16.0" instead

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-28221, which is invalid:

• expected dependent Jira Issue OCPBUGS-27810 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead
• expected dependent Jira Issue OCPBUGS-27810 to target a version in 4.15.0, but it targets "4.16.0" instead

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-28222, which is invalid:

• expected dependent Jira Issue OCPBUGS-27811 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead
• expected dependent Jira Issue OCPBUGS-27811 to target a version in 4.15.0, but it targets "4.16.0" instead

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-28223, which is invalid:

• expected dependent Jira Issue OCPBUGS-27812 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead
• expected dependent Jira Issue OCPBUGS-27812 to target a version in 4.15.0, but it targets "4.16.0" instead

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/366): >This is an automated cherry-pick of #364 > >/assign oceanc80 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.

[oceanc80]

/approve

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: oceanc80, openshift-cherrypick-robot

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.14/OWNERS)~~ [oceanc80] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[grokspawn]

/lgtm

[grokspawn]

/retest

Prow is experiencing some issues. Kicking.

[KeenonLee]

/retest

[ankitathomas]

/retest

[openshift-ci[bot]]

@openshift-cherrypick-robot: all tests passed!

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

[oceanc80]

/retitle [release-4.14] OCPBUGS-27620,OCPBUGS-27640,OCPBUGS-27645,OCPBUGS-27535,OCPBUGS-27555,OCPBUGS-27560: bump github.com/go-git/go-git/v5 to v5.11.0 #366

[openshift-ci-robot]

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-27620, which is invalid:

• expected dependent Jira Issue OCPBUGS-27621 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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-27640, which is invalid:

• expected dependent Jira Issue OCPBUGS-27641 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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-27645, which is invalid:

• expected dependent Jira Issue OCPBUGS-27646 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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-27535, which is invalid:

• expected dependent Jira Issue OCPBUGS-27536 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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-27555, which is invalid:

• expected dependent Jira Issue OCPBUGS-27556 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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-27560, which is invalid:

• expected dependent Jira Issue OCPBUGS-27561 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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/366): >This is an automated cherry-pick of #364 > >/assign oceanc80 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.

[oceanc80]

/jira refresh

[openshift-ci-robot]

@oceanc80: This pull request references Jira Issue OCPBUGS-27620, 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 version (4.14.z) matches configured target version for branch (4.14.z) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST) * dependent bug [Jira Issue OCPBUGS-27621](https://issues.redhat.com//browse/OCPBUGS-27621) is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA)) * dependent [Jira Issue OCPBUGS-27621](https://issues.redhat.com//browse/OCPBUGS-27621) targets the "4.15.0" version, which is one of the valid target versions: 4.15.0 * bug has dependents

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

This pull request references Jira Issue OCPBUGS-27640, 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 version (4.14.z) matches configured target version for branch (4.14.z) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST) * dependent bug [Jira Issue OCPBUGS-27641](https://issues.redhat.com//browse/OCPBUGS-27641) is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA)) * dependent [Jira Issue OCPBUGS-27641](https://issues.redhat.com//browse/OCPBUGS-27641) targets the "4.15.0" version, which is one of the valid target versions: 4.15.0 * bug has dependents

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

This pull request references Jira Issue OCPBUGS-27645, 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 version (4.14.z) matches configured target version for branch (4.14.z) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST) * dependent bug [Jira Issue OCPBUGS-27646](https://issues.redhat.com//browse/OCPBUGS-27646) is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA)) * dependent [Jira Issue OCPBUGS-27646](https://issues.redhat.com//browse/OCPBUGS-27646) targets the "4.15.0" version, which is one of the valid target versions: 4.15.0 * bug has dependents

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

This pull request references Jira Issue OCPBUGS-27535, 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 version (4.14.z) matches configured target version for branch (4.14.z) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST) * dependent bug [Jira Issue OCPBUGS-27536](https://issues.redhat.com//browse/OCPBUGS-27536) is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA)) * dependent [Jira Issue OCPBUGS-27536](https://issues.redhat.com//browse/OCPBUGS-27536) targets the "4.15.0" version, which is one of the valid target versions: 4.15.0 * bug has dependents

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

This pull request references Jira Issue OCPBUGS-27555, 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 version (4.14.z) matches configured target version for branch (4.14.z) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST) * dependent bug [Jira Issue OCPBUGS-27556](https://issues.redhat.com//browse/OCPBUGS-27556) is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA)) * dependent [Jira Issue OCPBUGS-27556](https://issues.redhat.com//browse/OCPBUGS-27556) targets the "4.15.0" version, which is one of the valid target versions: 4.15.0 * bug has dependents

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

This pull request references Jira Issue OCPBUGS-27560, 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 version (4.14.z) matches configured target version for branch (4.14.z) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST) * dependent bug [Jira Issue OCPBUGS-27561](https://issues.redhat.com//browse/OCPBUGS-27561) is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA)) * dependent [Jira Issue OCPBUGS-27561](https://issues.redhat.com//browse/OCPBUGS-27561) targets the "4.15.0" version, which is one of the valid target versions: 4.15.0 * bug has dependents

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

In response to [this](https://github.com/openshift/ocp-release-operator-sdk/pull/366#issuecomment-1917054269): >/jira refresh 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-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-27620: All pull requests linked via external trackers have merged:

• openshift/ocp-release-operator-sdk#366

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

Jira Issue OCPBUGS-27640: All pull requests linked via external trackers have merged:

• openshift/ocp-release-operator-sdk#366

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

Jira Issue OCPBUGS-27645: All pull requests linked via external trackers have merged:

• openshift/ocp-release-operator-sdk#366

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

Jira Issue OCPBUGS-27535: All pull requests linked via external trackers have merged:

• openshift/ocp-release-operator-sdk#366

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

Jira Issue OCPBUGS-27555: All pull requests linked via external trackers have merged:

• openshift/ocp-release-operator-sdk#366

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

Jira Issue OCPBUGS-27560: All pull requests linked via external trackers have merged:

• openshift/ocp-release-operator-sdk#366

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

In response to [this](https://github.com/openshift/ocp-release-operator-sdk/pull/366): >This is an automated cherry-pick of #364 > >/assign oceanc80 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-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build openshift-enterprise-helm-operator-container-v4.14.0-202401301709.p0.g0f0d1b2.assembly.stream for distgit openshift-enterprise-helm-operator. All builds following this will include this PR.