Skip to content

[release-4.16] OCPBUGS-76586: terraform/provider/google: Fixing GCP inconsistencies present with the service account creation#10298

Open
sunku5494 wants to merge 2 commits intoopenshift:release-4.16from
sunku5494:gcp-inconsistency-fix
Open

[release-4.16] OCPBUGS-76586: terraform/provider/google: Fixing GCP inconsistencies present with the service account creation#10298
sunku5494 wants to merge 2 commits intoopenshift:release-4.16from
sunku5494:gcp-inconsistency-fix

Conversation

@sunku5494
Copy link
Contributor

No description provided.

…6.10.0 using openshift fork

    Fixing the google provider inconsistencies present
    with the service account creation
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 11, 2026
@openshift-ci-robot
Copy link
Contributor

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

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-76586 to depend on a bug targeting a version in 4.17.0, 4.17.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.

Details

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.

@openshift-ci openshift-ci bot requested review from barbacbd and sadasu February 11, 2026 19:27
@sunku5494
Copy link
Contributor Author

/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.
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 18, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign bfournie for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@sunku5494
Copy link
Contributor Author

/retest

1 similar comment
@sunku5494
Copy link
Contributor Author

/retest

@sunku5494 sunku5494 changed the title [release-4.16] OCPBUGS-76586: terraform/provider/google: updated google provider to 6.10.0 using openshift fork [release-4.16] OCPBUGS-76586: terraform/provider/google: Fixing GCP inconsistencies present with the service account creation Feb 19, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 19, 2026

@sunku5494: The following test 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-vsphere-ovn fe6f9e5 link false /test okd-scos-e2e-vsphere-ovn

Full PR test history. Your PR dashboard.

Details

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.

@germanparente
Copy link

/override jira/valid-bug

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 19, 2026

@germanparente: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • jira/valid-bug

Only the following failed contexts/checkruns were expected:

  • ci/prow/altinfra-e2e-aws-ovn
  • ci/prow/altinfra-images
  • ci/prow/aro-unit
  • ci/prow/e2e-aws-ovn
  • ci/prow/e2e-aws-ovn-edge-zones
  • ci/prow/e2e-aws-ovn-edge-zones-manifest-validation
  • ci/prow/e2e-aws-ovn-fips
  • ci/prow/e2e-aws-ovn-imdsv2
  • ci/prow/e2e-aws-ovn-shared-vpc-custom-security-groups
  • ci/prow/e2e-aws-ovn-shared-vpc-edge-zones
  • ci/prow/e2e-aws-ovn-single-node
  • ci/prow/e2e-gcp-ovn
  • ci/prow/e2e-gcp-ovn-byo-vpc
  • ci/prow/e2e-gcp-ovn-xpn
  • ci/prow/e2e-gcp-secureboot
  • ci/prow/gofmt
  • ci/prow/golint
  • ci/prow/govet
  • ci/prow/images
  • ci/prow/okd-scos-e2e-vsphere-ovn
  • ci/prow/okd-scos-images
  • ci/prow/shellcheck
  • ci/prow/terraform-images
  • ci/prow/terraform-verify-vendor
  • ci/prow/tf-fmt
  • ci/prow/tf-lint
  • ci/prow/unit
  • ci/prow/verify-codegen
  • ci/prow/verify-vendor
  • ci/prow/yaml-lint
  • pull-ci-openshift-installer-fcos-gofmt
  • pull-ci-openshift-installer-fcos-golint
  • pull-ci-openshift-installer-fcos-govet
  • pull-ci-openshift-installer-fcos-images
  • pull-ci-openshift-installer-fcos-unit
  • pull-ci-openshift-installer-fcos-verify-codegen
  • pull-ci-openshift-installer-fcos-verify-vendor
  • pull-ci-openshift-installer-main-e2e-aws-ovn
  • pull-ci-openshift-installer-main-e2e-aws-ovn-edge-zones
  • pull-ci-openshift-installer-main-e2e-aws-ovn-edge-zones-manifest-validation
  • pull-ci-openshift-installer-main-e2e-aws-ovn-fips
  • pull-ci-openshift-installer-main-e2e-aws-ovn-imdsv2
  • pull-ci-openshift-installer-main-e2e-aws-ovn-shared-vpc-custom-security-groups
  • pull-ci-openshift-installer-main-e2e-aws-ovn-shared-vpc-edge-zones
  • pull-ci-openshift-installer-main-e2e-aws-ovn-single-node
  • pull-ci-openshift-installer-main-e2e-gcp-ovn
  • pull-ci-openshift-installer-main-e2e-gcp-ovn-byo-vpc
  • pull-ci-openshift-installer-main-e2e-gcp-ovn-xpn
  • pull-ci-openshift-installer-main-e2e-gcp-secureboot
  • pull-ci-openshift-installer-main-okd-scos-images
  • pull-ci-openshift-installer-main-shellcheck
  • pull-ci-openshift-installer-main-yaml-lint
  • pull-ci-openshift-installer-master-tf-fmt
  • pull-ci-openshift-installer-master-tf-lint
  • pull-ci-openshift-installer-release-4.11-aro-unit
  • pull-ci-openshift-installer-release-4.15-altinfra-e2e-aws-ovn
  • pull-ci-openshift-installer-release-4.15-altinfra-images
  • pull-ci-openshift-installer-release-4.15-terraform-images
  • pull-ci-openshift-installer-release-4.15-terraform-verify-vendor
  • tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

Details

In response to this:

/override jira/valid-bug

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.

@germanparente
Copy link

/label jira/valid-bug

Adding manually since there's no need to do this fix in 4.17

@openshift-ci openshift-ci bot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Feb 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Comments