GCP-484: Write project IDs to SHARED_DIR before resource creation

[cristianoveiga]

Summary

• Write deprovision-critical values (project IDs, region, cluster name) to SHARED_DIR before creating any GCP resources
• Ensures the deprovision step can clean up orphaned projects if the provision step fails or the job is interrupted
• Deprovision already handles non-existent projects gracefully (|| true)

Problem

When the gke-provision step is aborted mid-execution (e.g., job cancelled or timed out), the deprovision step cannot clean up orphaned GCP projects because project IDs were only written to SHARED_DIR at the end of the script.

Evidence: provision build log

Test plan

• Verify deprovision step can clean up projects when provision completes normally
• Verify deprovision handles non-existent projects gracefully (no errors if projects were never created)

Jira: https://issues.redhat.com/browse/GCP-484

🤖 Generated with Claude Code

[openshift-ci-robot]

@cristianoveiga: This pull request references GCP-484 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Summary

• Write deprovision-critical values (project IDs, region, cluster name) to SHARED_DIR before creating any GCP resources
• Ensures the deprovision step can clean up orphaned projects if the provision step fails or the job is interrupted
• Deprovision already handles non-existent projects gracefully (|| true)

Problem

When the gke-provision step is aborted mid-execution (e.g., job cancelled or timed out), the deprovision step cannot clean up orphaned GCP projects because project IDs were only written to SHARED_DIR at the end of the script.

Evidence: provision build log

Test plan

• Verify deprovision step can clean up projects when provision completes normally
• Verify deprovision handles non-existent projects gracefully (no errors if projects were never created)

Jira: https://issues.redhat.com/browse/GCP-484

🤖 Generated with Claude Code

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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cristianoveiga

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:

• ci-operator/step-registry/hypershift/gcp/gke/provision/OWNERS [cristianoveiga]

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]

[REHEARSALNOTIFIER]
@cristianoveiga: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
pull-ci-openshift-hypershift-main-e2e-gke	openshift/hypershift	presubmit	Registry content changed
pull-ci-openshift-hypershift-release-5.0-e2e-gke	openshift/hypershift	presubmit	Registry content changed
pull-ci-openshift-hypershift-release-4.23-e2e-gke	openshift/hypershift	presubmit	Registry content changed
pull-ci-openshift-hypershift-release-4.22-e2e-gke	openshift/hypershift	presubmit	Registry content changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[cristianoveiga]

/pj-rehearse pull-ci-openshift-hypershift-main-e2e-gke

[openshift-ci-robot]

@cristianoveiga: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[openshift-ci]

@cristianoveiga: 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/rehearse/openshift/hypershift/main/e2e-gke	66c29a0	link	unknown	/pj-rehearse pull-ci-openshift-hypershift-main-e2e-gke

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.