hypershift_framework.go:518: failed to create cluster, tearing down: failed to create infra: failed to create proxy host: failed to launch proxy host: operation error EC2: RunInstances, exceeded maximum number of attempts, 11, https response error StatusCode: 500, RequestID: 4405939b-db1e-4b0e-ba24-8bf25a6af768, api error InsufficientInstanceCapacity: We currently do not have sufficient t2.micro capacity in the Availability Zone you requested (us-east-1a). Our system will be working on provisioning additional capacity. You can currently get t2.micro capacity by not specifying an Availability Zone in your request or choosing us-east-1b, us-east-1c, us-east-1d, us-east-1e, us-east-1f.
fixture.go:417: Failed saving machine console logs; this is nonfatal: failed to get machine console logs: failed to get hostedcluster: hostedclusters.hypershift.openshift.io "proxy-492rc" not found
fixture.go:425: Failed to dump machine journals; this is nonfatal: no SSH secret specified for cluster, cannot dump journals
hypershift_framework.go:591: Destroyed cluster. Namespace: e2e-clusters-bm4qk, name: proxy-492rc
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-9q7jq/karpenter-upgrade-control-plane-7gb8f in 1m27s
hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster karpenter-upgrade-control-plane-7gb8f
upgrade_safe_check.go:87: UpgradeSafeFieldCheck: latch engaged for status.controlPlaneVersion
util.go:3158: Successfully waited for HostedCluster e2e-clusters-9q7jq/karpenter-upgrade-control-plane-7gb8f to have valid conditions in 0s
hypershift_framework.go:349: skipping postTeardown()
hypershift_framework.go:327: skipping teardown, already called
util.go:305: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-9q7jq/karpenter-upgrade-control-plane-7gb8f in 0s
util.go:322: Successfully waited for kubeconfig secret to have data in 0s
util.go:384: Successfully waited for a successful connection to the guest API server in 0s
karpenter_control_plane_upgrade_test.go:57: Starting Karpenter control plane upgrade. FromImage: registry.build01.ci.openshift.org/ci-op-tzid58pd/release@sha256:622e3aad9f1316badf4e7c2069a15bb6e480d3a5783727abee78031623fec157, toImage: registry.build01.ci.openshift.org/ci-op-tzid58pd/release@sha256:6d4783079f137cd54df67f3528c2264174af34f0ecc7ad5459eaa16c73152e98
karpenter_control_plane_upgrade_test.go:68: machine-os version(s) in latest release: [9.8.20260713-1 10.2.20260714-0]
karpenter_control_plane_upgrade_test.go:73: Created Karpenter NodePool
karpenter_control_plane_upgrade_test.go:75: Created workloads
util.go:583: Successfully waited for 1 nodes to become ready in 7m9s
karpenter_test.go:1560: Successfully waited for NodeClaims to be ready in 0s
karpenter_test.go:1516: Successfully waited for Pods to be scheduled on provisioned Karpenter nodes in 15s
karpenter_control_plane_upgrade_test.go:82: Pre-upgrade node: ip-10-0-134-179.ec2.internal, OS image: Red Hat Enterprise Linux CoreOS 9.8.20260708-0 (Plow)
karpenter_control_plane_upgrade_test.go:84: Updating cluster image. Image: registry.build01.ci.openshift.org/ci-op-tzid58pd/release@sha256:6d4783079f137cd54df67f3528c2264174af34f0ecc7ad5459eaa16c73152e98
util.go:620: Successfully waited for HostedCluster e2e-clusters-9q7jq/karpenter-upgrade-control-plane-7gb8f to rollout in 23m36s
karpenter_control_plane_upgrade_test.go:110: Control plane upgrade complete, waiting for NodeClaim drift detection
karpenter_test.go:1611: Successfully waited for NodeClaim on-demand-j4rsl to be drifted in 0s
karpenter_control_plane_upgrade_test.go:114: Karpenter Nodes drifted
eventually.go:259: Failed to get **v1.Node: context deadline exceeded
util.go:583: Failed to wait for 1 nodes to become ready in 45m0s: context deadline exceeded
eventually.go:384: observed invalid **v1.Node state after 45m0s
eventually.go:401: - observed **v1.Node /ip-10-0-134-179.ec2.internal invalid: expected node OS image "Red Hat Enterprise Linux CoreOS 9.8.20260708-0 (Plow)" to contain one of [9.8.20260713-1 10.2.20260714-0]
util.go:583: *v1.Node /ip-10-0-134-179.ec2.internal conditions:
util.go:583: MemoryPressure=False: KubeletHasSufficientMemory(kubelet has sufficient memory available)
util.go:583: DiskPressure=False: KubeletHasNoDiskPressure(kubelet has no disk pressure)
util.go:583: PIDPressure=False: KubeletHasSufficientPID(kubelet has sufficient PID available)
util.go:583: Ready=True: KubeletReady(kubelet is posting ready status)