OCPBUGS-5613: Bump goutils dependency from v1.1.0 to v1.1.1 for CVE-2021-4238

[rashmigottipati]

Description of the change: Bump goutils dependency from v1.1.0 to v1.1.1

Motivation for the change: https://nvd.nist.gov/vuln/detail/CVE-2021-4238

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)
• [ ] Add or update relevant sections of the docs website in website/content/en/docs

[openshift-ci-robot]

@rashmigottipati: This pull request references Jira Issue OCPBUGS-5613, which is invalid:

• expected Jira Issue OCPBUGS-5613 to depend on a bug targeting a version in 4.9.0, 4.9.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

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/298): >**Description of the change:** >Bump goutils dependency from v1.1.0 to v1.1.1 > >**Motivation for the change:** >https://nvd.nist.gov/vuln/detail/CVE-2021-4238 > >**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://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.

[openshift-ci[bot]]

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

In response to [this](https://github.com/openshift/ocp-release-operator-sdk/pull/298): >OCPBUGS-5613: Bump goutils dependency from v1.1.0 to v1.1.1 for CVE-2021-4238 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.

[openshift-ci-robot]

@rashmigottipati: No Jira bug is referenced in the title of this pull request. To reference a bug, add 'OCPBUGS-XXX:' to the title of this pull request and request another bug refresh with /jira refresh.

In response to [this](https://github.com/openshift/ocp-release-operator-sdk/pull/298): >**Description of the change:** >Bump goutils dependency from v1.1.0 to v1.1.1 > >**Motivation for the change:** >https://nvd.nist.gov/vuln/detail/CVE-2021-4238 > >**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://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.

[openshift-ci[bot]]

@rashmigottipati: This pull request references Bugzilla bug 2156729, which is invalid:

• expected the bug to target the "4.8.z" release, but it targets "---" instead
• expected dependent Bugzilla bug 2159520 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
• expected dependent Bugzilla bug 2159843 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
• expected dependent Bugzilla bug 2159853 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
• expected dependent Bugzilla bug 2159854 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
• expected dependent Bugzilla bug 2159855 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
• expected dependent Bugzilla bug 2159856 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
• expected dependent Bugzilla bug 2159857 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
• expected dependent Bugzilla bug 2159858 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
• expected dependent Bugzilla bug 2159859 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
• expected dependent Bugzilla bug 2159860 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
• expected dependent Bugzilla bug 2159864 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
• expected dependent Bugzilla bug 2159865 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
• expected dependent Bugzilla bug 2159866 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
• expected dependent Bugzilla bug 2159867 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
• expected dependent Bugzilla bug 2159868 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
• expected dependent Bugzilla bug 2159869 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
• expected dependent Bugzilla bug 2159870 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
• expected dependent Bugzilla bug 2159871 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
• expected dependent Bugzilla bug 2159872 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
• expected dependent Bugzilla bug 2159873 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
• expected dependent Bugzilla bug 2159874 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
• expected dependent Bugzilla bug 2159876 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
• expected dependent Bugzilla bug 2159877 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
• expected dependent Bugzilla bug 2159878 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
• expected dependent Bugzilla bug 2159879 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
• expected dependent Bugzilla bug 2160086 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
• expected dependent Bugzilla bug 2160088 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
• expected dependent Bugzilla bug 2160089 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
• expected dependent Bugzilla bug 2160620 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
• expected dependent Bugzilla bug 2160621 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
• expected dependent Bugzilla bug 2161305 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
• expected dependent Bugzilla bug 2159861 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is CLOSED (NOTABUG) instead
• expected dependent Bugzilla bug 2159862 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is CLOSED (NOTABUG) instead
• expected dependent Bugzilla bug 2159863 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is CLOSED (NOTABUG) instead
• expected dependent Bugzilla bug 2159875 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is CLOSED (WONTFIX) instead
• expected dependent Bugzilla bug 2159880 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is CLOSED (NOTABUG) instead
• expected dependent Bugzilla bug 2159881 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is CLOSED (NOTABUG) instead
• expected dependent Bugzilla bug 2159882 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is CLOSED (NOTABUG) instead
• expected dependent Bugzilla bug 2159883 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is CLOSED (NOTABUG) instead
• expected dependent Bugzilla bug 2160087 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is CLOSED (WONTFIX) instead
• expected dependent Bugzilla bug 2160090 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is CLOSED (NOTABUG) instead
• expected dependent Bugzilla bug 2159520 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2159843 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2159853 to target a release in 4.9.0, 4.9.z, but it targets "4.10.8" instead
• expected dependent Bugzilla bug 2159854 to target a release in 4.9.0, 4.9.z, but it targets "4.10.8" instead
• expected dependent Bugzilla bug 2159855 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2159856 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2159857 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2159858 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2159859 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2159860 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2159864 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2159865 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2159866 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2159867 to target a release in 4.9.0, 4.9.z, but it targets "ODF 4.13.0" instead
• expected dependent Bugzilla bug 2159868 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2159869 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2159870 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2159871 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2159872 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2159873 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2159874 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2159876 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2159877 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2159878 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2159879 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2160086 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2160088 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2160089 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2160620 to target a release in 4.9.0, 4.9.z, but it targets "4.11" instead
• expected dependent Bugzilla bug 2160621 to target a release in 4.9.0, 4.9.z, but it targets "4.11" instead
• expected dependent Bugzilla bug 2161305 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2159861 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2159862 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2159863 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2159875 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2159880 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2159881 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2159882 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2159883 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2160087 to target a release in 4.9.0, 4.9.z, but it targets "---" instead
• expected dependent Bugzilla bug 2160090 to target a release in 4.9.0, 4.9.z, but it targets "---" 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.

In response to [this](https://github.com/openshift/ocp-release-operator-sdk/pull/298): >Bug 2156729: Bump goutils dependency from v1.1.0 to v1.1.1 for CVE-2021-4238 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.

[jmrodri]

@rashmigottipati the change in the PR looks correct. Nicely done.

[openshift-ci-robot]

@rashmigottipati: This pull request references Jira Issue OCPBUGS-5613, which is invalid:

• expected Jira Issue OCPBUGS-5613 to depend on a bug targeting a version in 4.9.0, 4.9.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

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/ocp-release-operator-sdk/pull/298): >**Description of the change:** >Bump goutils dependency from v1.1.0 to v1.1.1 > >**Motivation for the change:** >https://nvd.nist.gov/vuln/detail/CVE-2021-4238 > >**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://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.

[openshift-ci[bot]]

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

In response to [this](https://github.com/openshift/ocp-release-operator-sdk/pull/298): >OCPBUGS-5613: Bump goutils dependency from v1.1.0 to v1.1.1 for CVE-2021-4238 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.

[oceanc80]

/jira refresh

[openshift-ci-robot]

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

• expected dependent Jira Issue OCPBUGS-5614 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is Closed (Not a Bug) 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.

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

[oceanc80]

/jira refresh

[openshift-ci-robot]

@oceanc80: This pull request references Jira Issue OCPBUGS-5613, which is valid.

6 validation(s) were run on this bug

* bug is open, matching expected state (open) * bug target version (4.8.z) matches configured target version for branch (4.8.z) * bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST) * dependent bug [Jira Issue OCPBUGS-5614](https://issues.redhat.com//browse/OCPBUGS-5614) is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE)) * dependent [Jira Issue OCPBUGS-5614](https://issues.redhat.com//browse/OCPBUGS-5614) targets the "4.9.z" version, which is one of the valid target versions: 4.9.0, 4.9.z * 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/298#issuecomment-1387366335): >/jira refresh 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.

[openshift-ci[bot]]

@rashmigottipati: 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).

[rashmigottipati]

@emmajiafan could you please review this PR and add the qe-approved label? Thanks!

[oceanc80]

/label backport-risk-assessed

[emmajiafan]

/label qe-approved

[oceanc80]

/label cherry-pick-approved

[openshift-ci[bot]]

@oceanc80: Can not set label cherry-pick-approved: Must be member in one of these teams: []

In response to [this](https://github.com/openshift/ocp-release-operator-sdk/pull/298#issuecomment-1396984310): >/label cherry-pick-approved 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.

[openshift-ci[bot]]

@bandrade: Can not set label cherry-pick-approved: Must be member in one of these teams: []

In response to [this](https://github.com/openshift/ocp-release-operator-sdk/pull/298#pullrequestreview-1261836615): >/label cherry-pick-approved 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.

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bandrade, everettraven, rashmigottipati, varshaprasad96

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

[everettraven]

/label cherry-pick-approved

[openshift-ci[bot]]

@everettraven: Can not set label cherry-pick-approved: Must be member in one of these teams: []

In response to [this](https://github.com/openshift/ocp-release-operator-sdk/pull/298#issuecomment-1397037836): >/label cherry-pick-approved 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.

[joelanford]

I added it manually. Thanks folks!

[openshift-ci-robot]

@rashmigottipati: Jira Issue OCPBUGS-5613 is in an unrecognized state (ON_QA) and will not be moved to the MODIFIED state.

In response to [this](https://github.com/openshift/ocp-release-operator-sdk/pull/298): >**Description of the change:** >Bump goutils dependency from v1.1.0 to v1.1.1 > >**Motivation for the change:** >https://nvd.nist.gov/vuln/detail/CVE-2021-4238 > >**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://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.