When multiple Network interface is attached to GCP machine is stuck in provisioned phase

    4.18.0-0.nightly-2024-10-16-094159

Always    

    Update machineset spec like below and scale replicas, before that set up another VPC network using gcp console or cli,make sure that it is created successfully ( refer to the existing VPC network present in machineset yaml and modify values accordingly )

    spec:
      lifecycleHooks: {}
      providerSpec:
        value:
          apiVersion: machine.openshift.io/v1beta1
          canIPForward: false
          credentialsSecret:
            name: gcp-cloud-credentials
          deletionProtection: false
          disks:
          - autoDelete: true
            boot: true
            image: projects/rhcos-cloud/global/images/rhcos-418-94-202410090804-0-gcp-x86-64
            labels: {}
            sizeGb: 128
            type: pd-ssd
          kind: GCPMachineProviderSpec
          machineType: n2-standard-4
          metadata:
            creationTimestamp: null
          networkInterfaces:
          - network: miyadav-1809g-7bdh4-network
            subnetwork: miyadav-1809g-7bdh4-worker-subnet
          - network: miyadav-1809g-7bdh4-network2
            subnetwork: miyadav-1809g-7bdh4-worker-subnet2
          projectID: openshift-qe
          region: us-central1
          serviceAccounts:
          - email: miyadav-1809g-7bdh4-w@openshift-qe.iam.gserviceaccount.com
            scopes:
            - https://www.googleapis.com/auth/cloud-platform
          shieldedInstanceConfig: {}
          tags:
          - miyadav-1809g-7bdh4-worker
          - inv
          userDataSecret:
            name: worker-user-data
          zone: us-central1-f
     

    Machines stuck in provisioned phase whereas it is successfully showing as running in gcp console with multiple NICs

Machines are running in GCP , should report back proper status .    

    serial logs url - https://console.cloud.google.com/compute/instancesDetail/zones/us-central1-f/instances/miyadav-1809g-7bdh4-worker-f-q52lv/console?port=1&project=openshift-qe
.
.
.

[   65.553572] ignition[820]: GET error: Get "https://api-int.miyadav-1809g.qe.gcp.devcluster.openshift.com:22623/config/worker": dial tcp 10.0.0.2:22623: i/o timeout
[   65.954095] ignition[820]: GET https://api-int.miyadav-1809g.qe.gcp.devcluster.openshift.com:22623/config/worker: attempt #3
.
.
.