-
Ticket
-
Resolution: Done
-
Critical
-
None
-
None
-
None
-
False
-
-
False
-
None
-
None
-
None
-
None
As of 4.22.0-0.ci-2026-01-23-080424 hypershift-e2e-aws is broken.
It doesn't seem like conformance tests are failing but at teardown, at least, we are getting:
TestCreateCluster/Teardown
{Failed === RUN TestCreateCluster/Teardown
journals.go:245: Successfully copied machine journals to /logs/artifacts/TestCreateCluster/machine-journals
fixture.go:341: SUCCESS: found no remaining guest resources
hypershift_framework.go:491: Destroyed cluster. Namespace: e2e-clusters-chct7, name: create-cluster-pjk75
hypershift_framework.go:513: Failed to dump cluster: failed to dump hosted cluster: found WARNING: Object got updated more than one time without a no-op update, this indicates hypershift incorrectly reverting defaulted values messages in file /logs/artifacts/TestCreateCluster/namespaces/e2e-clusters-chct7-create-cluster-pjk75/core/pods/logs/hosted-cluster-config-operator-6b9d59599c-md88p-hosted-cluster-config-operator.log
hypershift_framework.go:446: archiving /logs/artifacts/TestCreateCluster/hostedcluster-create-cluster-pjk75 to /logs/artifacts/TestCreateCluster/hostedcluster.tar.gz
--- FAIL: TestCreateCluster/Teardown (412.74s)
}
TestCreateCluster
{Failed === RUN TestCreateCluster
=== PAUSE TestCreateCluster
=== CONT TestCreateCluster
create_cluster_test.go:2492: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-chct7/create-cluster-pjk75 in 1m17s
hypershift_framework.go:249: skipping postTeardown()
hypershift_framework.go:230: skipping teardown, already called
--- FAIL: TestCreateCluster (2513.67s)
}
This causes the job and thus the payload to fail.
Started a thread.