Skip to content

[release-4.15] OCPBUGS-76929: terraform/provider/google: Fixing GCP inconsistencies present with the service account creation#10316

Open
sunku5494 wants to merge 1 commit intoopenshift:release-4.15from
sunku5494:gcp-inconsistency-fix-415
Open

[release-4.15] OCPBUGS-76929: terraform/provider/google: Fixing GCP inconsistencies present with the service account creation#10316
sunku5494 wants to merge 1 commit intoopenshift:release-4.15from
sunku5494:gcp-inconsistency-fix-415

Conversation

@sunku5494
Copy link
Contributor

No description provided.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 16, 2026
@openshift-ci-robot
Copy link
Contributor

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

  • expected the bug to target either version "4.15." or "openshift-4.15.", but it targets "4.16.z" instead
  • 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-76929 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.

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-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Feb 16, 2026
@openshift-ci openshift-ci bot requested review from jhixson74 and r4f4 February 16, 2026 05:42
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 16, 2026

@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 cba15e8 link false /test okd-scos-e2e-aws-upgrade
ci/prow/okd-scos-e2e-aws-ovn cba15e8 link false /test okd-scos-e2e-aws-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.

@sunku5494 sunku5494 force-pushed the gcp-inconsistency-fix-415 branch from cba15e8 to c734d42 Compare February 19, 2026 06:44
@sunku5494 sunku5494 changed the title [release-4.15] OCPBUGS-76929: terraform/provider/google: updated google provider to 5.21.0 using openshift fork [release-4.15] OCPBUGS-76929: terraform/provider/google: Fixing GCP inconsistencies present with the service account creation Feb 19, 2026
@sunku5494 sunku5494 force-pushed the gcp-inconsistency-fix-415 branch from c734d42 to 87baeaf Compare February 24, 2026 13:52
@patrickdillon
Copy link
Contributor

/lgtm
/approve
/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Mar 2, 2026
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 2, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 2, 2026

[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

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 2, 2026
@sunku5494
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link
Contributor

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

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

Details

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants