Skip to content

[release-4.14] OCPBUGS-76930: terraform/provider/google: Fixing inconsistencies with service account creation#10324

Open
sunku5494 wants to merge 1 commit intoopenshift:release-4.14from
sunku5494:gcp-inconsistency-fix-414
Open

[release-4.14] OCPBUGS-76930: terraform/provider/google: Fixing inconsistencies with service account creation#10324
sunku5494 wants to merge 1 commit intoopenshift:release-4.14from
sunku5494:gcp-inconsistency-fix-414

Conversation

@sunku5494
Copy link
Contributor

@sunku5494 sunku5494 commented Feb 19, 2026

No description provided.

@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 19, 2026
@openshift-ci-robot
Copy link
Contributor

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

  • expected the bug to target either version "4.14." or "openshift-4.14.", 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-76930 to depend on a bug targeting a version in 4.15.0, 4.15.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:

… the service account creation

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
Copy link
Contributor

openshift-ci bot commented Feb 19, 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 rwsu 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

@sunku5494 sunku5494 force-pushed the gcp-inconsistency-fix-414 branch from d781a46 to 3ec0cc4 Compare February 24, 2026 14:38
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 24, 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/e2e-gcp-ovn-xpn 3ec0cc4 link false /test e2e-gcp-ovn-xpn
ci/prow/e2e-gcp-ovn 3ec0cc4 link true /test e2e-gcp-ovn
ci/prow/images 3ec0cc4 link true /test images
ci/prow/e2e-gcp-ovn-byo-vpc 3ec0cc4 link false /test e2e-gcp-ovn-byo-vpc
ci/prow/e2e-aws-ovn 3ec0cc4 link true /test e2e-aws-ovn
ci/prow/e2e-gcp-secureboot 3ec0cc4 link false /test e2e-gcp-secureboot

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.

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-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.

2 participants