Skip to content

feat: update capa with nutanix fork #4784

feat: update capa with nutanix fork

feat: update capa with nutanix fork #4784

GitHub Actions / e2e test report failed Oct 1, 2025 in 0s

42 tests run, 33 passed, 8 skipped, 1 failed.

Annotations

Check failure on line 1 in caren-e2e

See this annotation in the file changed.

@github-actions github-actions / e2e test report

caren-e2e.[It] Quick start Nutanix Cilium ClusterResourceSet topology-cilium-crs Should create a workload cluster [provider:Nutanix, cni:Cilium, addonStrategy:ClusterResourceSet]

Timed out after 600.000s.
Timed out waiting for 1 nodes to be created for MachineDeployment quick-start-vtpvp8/quick-start-q3mlrnket2j7douiurf0lx40tzdoql7b30elpr4wmiyurw2nmzm
The function passed to Eventually failed at /home/runner/go/pkg/mod/sigs.k8s.io/cluster-api/[email protected]/framework/machinedeployment_helpers.go:127 with:
Expected
    <int>: 0
to equal
    <int>: 1
Raw output
[FAILED] Timed out after 600.000s.
Timed out waiting for 1 nodes to be created for MachineDeployment quick-start-vtpvp8/quick-start-q3mlrnket2j7douiurf0lx40tzdoql7b30elpr4wmiyurw2nmzm
The function passed to Eventually failed at /home/runner/go/pkg/mod/sigs.k8s.io/cluster-api/[email protected]/framework/machinedeployment_helpers.go:127 with:
Expected
    <int>: 0
to equal
    <int>: 1
In [It] at: /home/runner/go/pkg/mod/sigs.k8s.io/cluster-api/[email protected]/framework/machinedeployment_helpers.go:128 @ 10/01/25 21:56:09.893

There were additional failures detected after the initial failure. These are visible in the timeline