PR #8991 - 07-16 18:14

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

623
Total Tests
588
Passed
5
Failed
30
Skipped

Failed Tests

TestCreateCluster
1h13m1.71s
create_cluster_test.go:47: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-n5crf/create-cluster-f5z9h in 1m5s hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster create-cluster-f5z9h util.go:3178: Successfully waited for HostedCluster e2e-clusters-n5crf/create-cluster-f5z9h to have valid conditions in 0s hypershift_framework.go:349: skipping postTeardown() hypershift_framework.go:327: skipping teardown, already called
TestCreateCluster/Main
44m41.49s
util.go:305: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-n5crf/create-cluster-f5z9h 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 create_cluster_test.go:87: fetching mgmt kubeconfig util.go:305: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-n5crf/create-cluster-f5z9h in 0s util.go:322: Successfully waited for kubeconfig secret to have data in 0s
TestCreateCluster/Main/EnsureGlobalPullSecret
28m5.34s
util.go:305: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-n5crf/create-cluster-f5z9h 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 util.go:2004: NodePool replicas: 1 util.go:2195: Waiting for nodes to stabilize after pull secret update util.go:583: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-n5crf/create-cluster-f5z9h-us-east-1a in 0s util.go:2227: Deleting the additional-pull-secret secret in the DataPlane util.go:2246: Waiting for nodes to stabilize after pull secret deletion util.go:583: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-n5crf/create-cluster-f5z9h-us-east-1a in 0s util.go:2252: Expected success, but got an error: <*fmt.wrapError | 0xc0053a0d80>: failed to wait for DaemonSet global-pull-secret-syncer to be ready: context deadline exceeded { msg: "failed to wait for DaemonSet global-pull-secret-syncer to be ready: context deadline exceeded", err: <context.deadlineExceededError>{}, } util.go:2031: Restoring original management-cluster pull secret data
TestCreateCluster/Main/EnsureGlobalPullSecret/Create_a_pod_which_uses_the_restricted_image,_should_succeed
7m0.01s
util.go:4091: Creating a pod which uses the restricted image util.go:4116: Attempt 1/3: Creating pod util.go:4121: Successfully created pod global-pull-secret-success-pod in namespace kube-system on attempt 1 util.go:4142: Created pod global-pull-secret-success-pod in namespace kube-system util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4159: Pod phase: Pending, shouldFail: false util.go:4166: Timed out after 420.001s. pod is not running Expected success, but got an error: <*errors.errorString | 0xc0030375c0>: pod is not running yet, current phase: Pending { s: "pod is not running yet, current phase: Pending", }
TestCreateCluster/Main/EnsureGlobalPullSecret/Wait_for_pull_secret_synchronization_to_stabilize_across_all_nodes
20m0s
util.go:2251: Waiting for GlobalPullSecretDaemonSet to process the deletion and stabilize all nodes util.go:2284: Waiting for global-pull-secret-syncer DaemonSet to be ready (min expected: 1) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) testing.go:1811: test executed panic(nil) or runtime.Goexit: subtest may have called FailNow on a parent test