[release-4.16] OCPBUGS-76586: terraform/provider/google: Fixing GCP inconsistencies present with the service account creation#10298
Conversation
…6.10.0 using openshift fork
Fixing the google provider inconsistencies present
with the service account creation
|
@sunku5494: This pull request references Jira Issue OCPBUGS-76586, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn 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. |
|
/retest |
Terraform Google provider v6 changed the default balancing_mode from unset (API-decided) to explicitly UTILIZATION. GCP rejects UTILIZATION for INTERNAL backend services, requiring CONNECTION. Set balancing_mode=CONNECTION explicitly on the api_internal backend service to fix GCP IPI cluster installation failures.
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/retest |
1 similar comment
|
/retest |
|
@sunku5494: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
/override jira/valid-bug |
|
@germanparente: /override requires failed status contexts, check run or a prowjob name to operate on.
Only the following failed contexts/checkruns were expected:
If you are trying to override a checkrun that has a space in it, you must put a double quote on the context. DetailsIn 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 kubernetes-sigs/prow repository. |
|
/label jira/valid-bug Adding manually since there's no need to do this fix in 4.17 |
No description provided.