Skip to content

OCPBUGS-75250: Use correct Project ID with GCP Shared VPC#10297

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
sadasu:sadasu-OCPBUGS-75250
Mar 14, 2026
Merged

OCPBUGS-75250: Use correct Project ID with GCP Shared VPC#10297
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
sadasu:sadasu-OCPBUGS-75250

Conversation

@sadasu
Copy link
Contributor

@sadasu sadasu commented Feb 11, 2026

Problem: When userProvisionedDNS is enabled on GCP, the Installer tries to get the Load balancer IP address from the correct project. This LB IP is then used to update the bootstrap ignition file. When Shared VPC (XPN) was configured, Installer was trying to get the LB IP addresses from the Network Project ID and failing to get the LB IPs.
Solution: This LB IP is a front end configuration that should be read from the service project that is available in projectID.

@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Feb 11, 2026
@openshift-ci-robot
Copy link
Contributor

@sadasu: This pull request references Jira Issue OCPBUGS-75250, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @jianli-wei

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.

}

apiIntIPAddress, err := getInternalLBAddress(ctx, in.InstallConfig.Config.GCP.ProjectID, in.InstallConfig.Config.GCP.Region, getAPIAddressName(in.InfraID), in.InstallConfig.Config.GCP.Endpoint)
apiIntIPAddress, err := getInternalLBAddress(ctx, networkProjectID, in.InstallConfig.Config.GCP.Region, getAPIAddressName(in.InfraID), in.InstallConfig.Config.GCP.Endpoint)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My bad, I told you the wrong fix. This is actually ok as the LB is in the service project. The issue is here where we are using the host project instead of the service project.

Copy link
Contributor Author

@sadasu sadasu Feb 11, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No worries. We realized we needed a different fairly quickly and thanks for helping us get to the right fix.

Switched to getting GCP Load Balancer IP addresses from the service
project "GCP.ProjectID" in all cases, even when Shared VPC (XPN) is
configured.

This fix provides the correct project to use for getting the Load
Balancer IP address when UserProvisionedDNS is enabled, and the
ignition files are updated with the Load Balancer IP.
@sadasu sadasu force-pushed the sadasu-OCPBUGS-75250 branch from 8675665 to 47e3ad9 Compare February 11, 2026 18:33
@patrickdillon
Copy link
Contributor

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 11, 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 Feb 11, 2026
@sadasu
Copy link
Contributor Author

sadasu commented Feb 11, 2026

/retest

@sadasu
Copy link
Contributor Author

sadasu commented Feb 13, 2026

/jira cc-qa

@openshift-ci-robot
Copy link
Contributor

@sadasu: This pull request references Jira Issue OCPBUGS-75250, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @jianli-wei

Details

In response to this:

/jira cc-qa

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.

@sadasu
Copy link
Contributor Author

sadasu commented Feb 17, 2026

The e2e-gcp-custom-dns job is failing due to https://issues.redhat.com/browse/OCPBUGS-75200.

@sadasu
Copy link
Contributor Author

sadasu commented Feb 18, 2026

/test e2e-gcp-xpn-custom-dns

@patrickdillon
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 23, 2026
@sadasu
Copy link
Contributor Author

sadasu commented Feb 26, 2026

@jianli-wei and @barbacbd I looked at ci/prow/e2e-gcp-custom-dns. The errors I see there are known and the associated bug is https://issues.redhat.com/browse/OCPBUGS-75200

The errors I see in ci/prow/e2e-gcp-xpn-custom-dns seem to be related to clean up of Route53 entries used for custom-dns setup?

@jianli-wei
Copy link
Contributor

@jianli-wei and @barbacbd I looked at ci/prow/e2e-gcp-custom-dns. The errors I see there are known and the associated bug is https://issues.redhat.com/browse/OCPBUGS-75200

The errors I see in ci/prow/e2e-gcp-xpn-custom-dns seem to be related to clean up of Route53 entries used for custom-dns setup?

@sadasu

INFO[2026-02-12T00:50:00Z] Running multi-stage phase pre                
INFO[2026-02-12T00:50:00Z] Running step e2e-gcp-custom-dns-gcp-provision-minimal-permission. 
INFO[2026-02-12T00:50:08Z] Step e2e-gcp-custom-dns-gcp-provision-minimal-permission succeeded after 7s. 
INFO[2026-02-12T00:50:08Z] Running step e2e-gcp-custom-dns-ipi-conf.    
INFO[2026-02-12T00:50:15Z] Step e2e-gcp-custom-dns-ipi-conf succeeded after 7s. 
INFO[2026-02-12T00:50:15Z] Running step e2e-gcp-custom-dns-ipi-conf-telemetry. 
INFO[2026-02-12T00:50:23Z] Step e2e-gcp-custom-dns-ipi-conf-telemetry succeeded after 7s. 
INFO[2026-02-12T00:50:23Z] Running step e2e-gcp-custom-dns-ipi-conf-gcp. 
INFO[2026-02-12T00:50:43Z] Step e2e-gcp-custom-dns-ipi-conf-gcp succeeded after 19s. 
INFO[2026-02-12T00:50:43Z] Running step e2e-gcp-custom-dns-ipi-install-monitoringpvc. 
INFO[2026-02-12T00:50:50Z] Step e2e-gcp-custom-dns-ipi-install-monitoringpvc succeeded after 7s. 
INFO[2026-02-12T00:50:50Z] Running step e2e-gcp-custom-dns-ipi-conf-gcp-control-plane-node-type. 
INFO[2026-02-12T00:50:57Z] Step e2e-gcp-custom-dns-ipi-conf-gcp-control-plane-node-type succeeded after 7s. 
INFO[2026-02-12T00:50:57Z] Running step e2e-gcp-custom-dns-ipi-install-rbac. 
INFO[2026-02-12T00:51:05Z] Step e2e-gcp-custom-dns-ipi-install-rbac succeeded after 7s. 
INFO[2026-02-12T00:51:05Z] Running step e2e-gcp-custom-dns-openshift-cluster-bot-rbac. 
INFO[2026-02-12T00:51:12Z] Step e2e-gcp-custom-dns-openshift-cluster-bot-rbac succeeded after 7s. 
INFO[2026-02-12T00:51:12Z] Running step e2e-gcp-custom-dns-ipi-install-hosted-loki. 
INFO[2026-02-12T00:51:19Z] Step e2e-gcp-custom-dns-ipi-install-hosted-loki succeeded after 7s. 
INFO[2026-02-12T00:51:19Z] Running step e2e-gcp-custom-dns-ipi-install-install. 
INFO[2026-02-12T02:01:10Z] Step e2e-gcp-custom-dns-ipi-install-install succeeded after 1h9m51s. 
INFO[2026-02-12T02:01:10Z] Running step e2e-gcp-custom-dns-gcp-provision-public-custom-dns. 
INFO[2026-02-12T02:03:43Z] Step e2e-gcp-custom-dns-gcp-provision-public-custom-dns succeeded after 2m32s. 
INFO[2026-02-12T02:03:43Z] Running step e2e-gcp-custom-dns-aws-provision-route53-public-record-sets. 
INFO[2026-02-12T02:06:28Z] Step e2e-gcp-custom-dns-aws-provision-route53-public-record-sets succeeded after 2m45s. 
INFO[2026-02-12T02:06:28Z] Running step e2e-gcp-custom-dns-ipi-install-times-collection. 
INFO[2026-02-12T02:06:40Z] Step e2e-gcp-custom-dns-ipi-install-times-collection succeeded after 11s. 
INFO[2026-02-12T02:06:40Z] Running step e2e-gcp-custom-dns-nodes-readiness. 
INFO[2026-02-12T02:08:01Z] Step e2e-gcp-custom-dns-nodes-readiness succeeded after 1m20s. 
INFO[2026-02-12T02:08:01Z] Running step e2e-gcp-custom-dns-multiarch-validate-nodes. 
INFO[2026-02-12T02:08:09Z] Step e2e-gcp-custom-dns-multiarch-validate-nodes succeeded after 7s. 
INFO[2026-02-12T02:08:09Z] Running step e2e-gcp-custom-dns-cucushift-installer-check-control-plane-machinesets. 
INFO[2026-02-12T02:09:12Z] Step e2e-gcp-custom-dns-cucushift-installer-check-control-plane-machinesets succeeded after 1m3s. 
INFO[2026-02-12T02:09:12Z] Running step e2e-gcp-custom-dns-cucushift-installer-check-operators. 
INFO[2026-02-12T02:12:42Z] Step e2e-gcp-custom-dns-cucushift-installer-check-operators succeeded after 3m30s. 
INFO[2026-02-12T02:12:42Z] Running step e2e-gcp-custom-dns-cucushift-installer-check-info. 
INFO[2026-02-12T02:12:53Z] Step e2e-gcp-custom-dns-cucushift-installer-check-info succeeded after 10s. 
INFO[2026-02-12T02:12:53Z] Running step e2e-gcp-custom-dns-cucushift-installer-check-capability. 
INFO[2026-02-12T02:13:01Z] Step e2e-gcp-custom-dns-cucushift-installer-check-capability succeeded after 7s. 
INFO[2026-02-12T02:13:01Z] Running step e2e-gcp-custom-dns-cucushift-installer-check-realtime. 
INFO[2026-02-12T02:13:09Z] Step e2e-gcp-custom-dns-cucushift-installer-check-realtime succeeded after 7s. 
INFO[2026-02-12T02:13:09Z] Running step e2e-gcp-custom-dns-cucushift-installer-check-compact. 
INFO[2026-02-12T02:13:16Z] Step e2e-gcp-custom-dns-cucushift-installer-check-compact succeeded after 7s. 
INFO[2026-02-12T02:13:16Z] Running step e2e-gcp-custom-dns-cucushift-installer-check-fips. 
INFO[2026-02-12T02:13:25Z] Step e2e-gcp-custom-dns-cucushift-installer-check-fips succeeded after 8s. 
INFO[2026-02-12T02:13:25Z] Running step e2e-gcp-custom-dns-cucushift-installer-check-user-provisioned-dns. 
INFO[2026-02-12T02:15:05Z] Step e2e-gcp-custom-dns-cucushift-installer-check-user-provisioned-dns succeeded after 1m40s. 
INFO[2026-02-12T02:15:05Z] Step phase pre succeeded after 1h25m5s.      
...output omitted...
INFO[2026-02-12T04:16:38Z] Step e2e-gcp-custom-dns-openshift-e2e-test failed after 2h1m33s. 
INFO[2026-02-12T04:16:38Z] Step phase test failed after 2h1m33s.        
INFO[2026-02-12T04:16:38Z] Running multi-stage phase post               
INFO[2026-02-12T04:16:38Z] Running step e2e-gcp-custom-dns-gather-network. 
INFO[2026-02-12T04:20:25Z] Step e2e-gcp-custom-dns-gather-network succeeded after 3m46s. 
INFO[2026-02-12T04:20:25Z] Running step e2e-gcp-custom-dns-gather-core-dump. 
INFO[2026-02-12T04:20:44Z] Step e2e-gcp-custom-dns-gather-core-dump succeeded after 18s. 
INFO[2026-02-12T04:20:44Z] Running step e2e-gcp-custom-dns-gather-gcp-console. 
INFO[2026-02-12T04:21:22Z] Step e2e-gcp-custom-dns-gather-gcp-console succeeded after 38s. 
INFO[2026-02-12T04:21:22Z] Running step e2e-gcp-custom-dns-gather-must-gather. 
INFO[2026-02-12T04:25:11Z] Step e2e-gcp-custom-dns-gather-must-gather succeeded after 3m48s. 
INFO[2026-02-12T04:25:11Z] Running step e2e-gcp-custom-dns-gather-extra. 
INFO[2026-02-12T04:33:55Z] Step e2e-gcp-custom-dns-gather-extra succeeded after 8m44s. 
INFO[2026-02-12T04:33:55Z] Running step e2e-gcp-custom-dns-gather-audit-logs. 
INFO[2026-02-12T04:35:08Z] Step e2e-gcp-custom-dns-gather-audit-logs succeeded after 1m12s. 
INFO[2026-02-12T04:35:08Z] Running step e2e-gcp-custom-dns-ipi-deprovision-deprovision. 
INFO[2026-02-12T04:43:54Z] Step e2e-gcp-custom-dns-ipi-deprovision-deprovision succeeded after 8m46s. 
INFO[2026-02-12T04:43:54Z] Running step e2e-gcp-custom-dns-aws-deprovision-route53-public-record-sets. 
INFO[2026-02-12T04:44:36Z] Step e2e-gcp-custom-dns-aws-deprovision-route53-public-record-sets succeeded after 41s. 
INFO[2026-02-12T04:44:36Z] Step phase post succeeded after 27m57s.      
INFO[2026-02-18T15:30:42Z] Running multi-stage phase pre                
INFO[2026-02-18T15:30:42Z] Running step e2e-gcp-xpn-custom-dns-ipi-conf. 
INFO[2026-02-18T15:31:22Z] Logs for container test in pod e2e-gcp-xpn-custom-dns-ipi-conf: 
INFO[2026-02-18T15:31:22Z] RELEASE_IMAGE_LATEST is an empty string, exiting
{"component":"entrypoint","error":"wrapped process failed: exit status 1","file":"sigs.k8s.io/prow/pkg/entrypoint/run.go:84","func":"sigs.k8s.io/prow/pkg/entrypoint.Options.internalRun","level":"error","msg":"Error executing test process","severity":"error","time":"2026-02-18T15:31:22Z"}
error: failed to execute wrapped command: exit status 1 
INFO[2026-02-18T15:31:22Z] Step e2e-gcp-xpn-custom-dns-ipi-conf failed after 40s. 
INFO[2026-02-18T15:31:22Z] Step phase pre failed after 40s.             

@jianli-wei
Copy link
Contributor

/test e2e-gcp-xpn-custom-dns

@jianli-wei
Copy link
Contributor

/verified by jiwei

@openshift-ci-robot
Copy link
Contributor

@jianli-wei: This PR has been marked as verified by jiwei.

Details

In response to this:

/verified by jiwei

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 verified Signifies that the PR passed pre-merge verification criteria label Mar 12, 2026
@tthvo
Copy link
Member

tthvo commented Mar 12, 2026

/retest-required
/tide refresh

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD fe4720d and 2 for PR HEAD 47e3ad9 in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 13, 2026

@sadasu: 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-custom-dns 47e3ad9 link false /test e2e-gcp-custom-dns
ci/prow/e2e-gcp-xpn-custom-dns 47e3ad9 link false /test e2e-gcp-xpn-custom-dns

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.

@tthvo
Copy link
Member

tthvo commented Mar 13, 2026

/test okd-scos-images

@openshift-merge-bot openshift-merge-bot bot merged commit 9cade28 into openshift:main Mar 14, 2026
24 of 26 checks passed
@openshift-ci-robot
Copy link
Contributor

@sadasu: An error was encountered searching for bug OCPBUGS-75250 on the Jira server at https://issues.redhat.com. No known errors were detected, please see the full error message for details.

Full error message. No response returned: Get "https://issues.redhat.com/rest/api/2/issue/OCPBUGS-75250": GET https://issues.redhat.com/rest/api/2/issue/OCPBUGS-75250 giving up after 5 attempt(s)

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.

Details

In response to this:

Problem: When userProvisionedDNS is enabled on GCP, the Installer tries to get the Load balancer IP address from the correct project. This LB IP is then used to update the bootstrap ignition file. When Shared VPC (XPN) was configured, Installer was trying to get the LB IP addresses from the Network Project ID and failing to get the LB IPs.
Solution: This LB IP is a front end configuration that should be read from the service project that is available in projectID.

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.

@sadasu
Copy link
Contributor Author

sadasu commented Mar 23, 2026

/cherry-pick release-4.21

@openshift-cherrypick-robot

@sadasu: new pull request created: #10423

Details

In response to this:

/cherry-pick release-4.21

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.

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. jira/severity-moderate Referenced Jira bug's severity is moderate 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. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants