OCPBUGS-50919: Fixes panic during GCP tags fetch due to unstable network

[bharath-b-rh]

PR fixes the panic observed when fetching the GCP tags during create stage of installation. The issue was happening because of referencing the empty google API error, which could be because of the unstable network and since the call was not reaching the server.

/cc @jianli-wei @barbacbd

[openshift-ci-robot]

@bharath-b-rh: This pull request references Jira Issue OCPBUGS-50919, which is invalid:

• expected the bug to target either version "4.19." or "openshift-4.19.", but it targets "4.18.0" 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.

In response to this:

PR fixes the panic observed when fetching the GCP tags during create stage of installation. The issue was happening because of referencing the empty google API error, which could be because of the unstable network and since the call was not reaching the server.

/cc @jianli-wei @barbacbd

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.

[jianli-wei]

/label qe-approved

[openshift-ci-robot]

@bharath-b-rh: This pull request references Jira Issue OCPBUGS-50919, 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.19.0) matches configured target version for branch (4.19.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

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

In response to this:

PR fixes the panic observed when fetching the GCP tags during create stage of installation. The issue was happening because of referencing the empty google API error, which could be because of the unstable network and since the call was not reaching the server.

/cc @jianli-wei @barbacbd

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.

[bharath-b-rh]

/test altinfra-images

[openshift-ci]

@bharath-b-rh: 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-aws-ovn	830a048	link	false	/test okd-scos-e2e-aws-ovn

Full PR test history. Your PR dashboard.

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.

[patrickdillon]

/approve

[openshift-ci]

[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

Needs approval from an approver in each of these files:

• pkg/asset/installconfig/gcp/OWNERS [patrickdillon]

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