[release-4.15] OCPBUGS-50994: Bump terraform-provider-google version to v5.37.0 to fix consistent issues during cluster creation

[sunku5494]

Updated terraform-provider-google version with
go get github.com/hashicorp/terraform-provider-google@9d7e7459a11c7063d30130d2a5cec83c5b6ce7e8

[openshift-ci-robot]

@sunku5494: This pull request references Jira Issue OCPBUGS-50994, which is invalid:

• expected Jira Issue OCPBUGS-50994 to depend on a bug targeting a version in 4.16.0, 4.16.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), 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:

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 openshift-eng/jira-lifecycle-plugin repository.

[sunku5494]

/jira refresh

[openshift-ci-robot]

@sunku5494: This pull request references Jira Issue OCPBUGS-50994, 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 text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-42014 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-42014 targets the "4.16.z" version, which is one of the valid target versions: 4.16.0, 4.16.z
• bug has dependents

Requesting review from QA contact:
/cc @mhanss

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 openshift-eng/jira-lifecycle-plugin repository.

[sunku5494]

/retest

[patrickdillon]

/approve
/lgtm

[openshift-ci]

[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

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

[openshift-ci-robot]

@sunku5494: This pull request references Jira Issue OCPBUGS-50994, which is valid.

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 POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-42014 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-42014 targets the "4.16.z" version, which is one of the valid target versions: 4.16.0, 4.16.z
• bug has dependents

Requesting review from QA contact:
/cc @mhanss

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

In response to this:

Updated terraform-provider-google version with
go get github.com/hashicorp/terraform-provider-google@9d7e7459a11c7063d30130d2a5cec83c5b6ce7e8

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 openshift-eng/jira-lifecycle-plugin repository.

[mhanss]

/label cherry-pick-approved

[sadasu]

/label backport-risk-assessed

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 64866ce and 2 for PR HEAD d8a37ca in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 64866ce and 2 for PR HEAD d8a37ca in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 64866ce and 2 for PR HEAD d8a37ca in total

[prabhapa]

/test terraform-verify-vendor
/test verify-vendor

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 64866ce and 2 for PR HEAD d8a37ca in total

[openshift-ci]

New changes are detected. LGTM label has been removed.

[sunku5494]

/retest

[openshift-ci]

@sunku5494: 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/okd-scos-e2e-aws-upgrade	5b62574	link	false	/test okd-scos-e2e-aws-upgrade
ci/prow/okd-scos-e2e-aws-ovn	5b62574	link	false	/test okd-scos-e2e-aws-ovn
ci/prow/e2e-azurestack	5b62574	link	false	/test e2e-azurestack

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.

[sunku5494]

@patrickdillon Due to a prow task involving a failing Terraform vendor, this PR was stopped from merging. I used the proper golang version (i.e. go1.20) to fix it. So, kindly add the lgtm label again.