NodePool creation fails when creating a cluster with KubeVirt virtual machines as nodes on a bare metal cluster using Hosted Control Plane

Procedures implemented by the customer

1) Create an OCP4.16.11 cluster (master 3node, worker 3node) in bare metal configuration as a management cluster.
It is configured in an online environment (with proxies).
2) Install Multicluster Engine Operator from the cluster console according to document [1].
3) Create host inventory
4) Install LVM Operator, MetalLB Operaotor[3] and OpenShift Virtualization[4], which are required as prerequisites for creating an HCP cluster[2], and create an instance.
5) Follow the documentation [5] and create a HostedCluster from the console of the managed cluster.
6) In the Condition state of the NodePool resource, for type: ValidGeneratedPayload, check the error message that it fails to get the ignition payload.
```` Last Transition Time: 2024-10-10
Last Transition Time: 2024-10-22T08:00:52Z
Message: Failed to generate payload: error getting ignition payload: failed to get component images: failed to look up release image metadata: failed to extract release metadata: failed to get repo setup: failed to create repository client for https://quay.io: Get “https://quay.io/v2/”: context Deadline exceeded (Client.Timeout exceeded while awaiting headers)
Observed Generation: 1
Reason: InvalidConfig
Status: 1
Type: ValidGeneratedPayload
````
7) Set proxy certificate in .spec.additionalTrustBundle of HostedCluster resource (name: example)
8) After about 10 hours (about 12 hours after cluster creation), confirm that the error message about failure to obtain the “ignition payload” has been resolved.
9) Confirmed that the status of HostedCluster and NodePool did not become the status that cluster creation was completed.
Node is not added as CURRENT NODES in NodePool resource.
```
[kni@installer-4-16-alpha fail_to_create_nodepool]$ oc get nodepool -ANAMESPACE NAME CLUSTER DESIRED NODES CURRENT NODES AUTOSCALING AUTOREPAIR VERSION UPDATINGVERSION UPDATINGCONFIG MESSAGE
clusters example-nodepool example 2 False False True True Minimum availability requires 2 replicas, current 0 available
```Current Status
I have followed the documented procedure to create a HostedCluster using KubeVirt, but the cluster creation process has not completed successfully.
The status of the cluster must-gather is attached.must-gather
must-gather.local.6209288778331882834.tgzmust-gather specifying the image
MulticlusterEngine
mce.must-gather.20241023.tgz
Virtualization
virtualization.must-gather.20241023.tgznamespace: clusters, clusters-example, hcp-host-inventory
Inspect information obtained by specifying
inspect.local.1274741544520679680.tgzRequested items
I would like to know about the procedure that needs to be taken to resolve the situation where the cluster creation using HCP described above is still in the process of creation and does not proceed.Version information
OCP: 4.16.11
MCE Operator: 2.6.3
OpenShift Virtualization: 4.16.3
LVM Operator: 4.16.2
MetalLB Operator: 4.16.0-202409032335

    4.16.11

    100%