PR #5792 - 04-18 08:35

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

55
Total Tests
20
Passed
20
Failed
15
Skipped

Failed Tests

TestAzureScheduler
1h3m9.57s
hypershift_framework.go:316: Successfully created hostedcluster e2e-clusters-9545h/azure-scheduler-txzrs in 1m59s hypershift_framework.go:115: Summarizing unexpected conditions for HostedCluster azure-scheduler-txzrs util.go:2123: Successfully waited for HostedCluster e2e-clusters-9545h/azure-scheduler-txzrs to have valid conditions in 25ms hypershift_framework.go:194: skipping postTeardown() hypershift_framework.go:175: skipping teardown, already called
TestAzureScheduler/Main
30m0.2s
util.go:218: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-9545h/azure-scheduler-txzrs in 25ms util.go:235: Successfully waited for kubeconfig secret to have data in 0s util.go:281: Successfully waited for a successful connection to the guest API server in 0s util.go:462: Successfully waited for 2 nodes to become ready in 25ms azure_scheduler_test.go:111: Updated clusterSizingConfig. azure_scheduler_test.go:158: Successfully waited for HostedCluster size label and annotations updated in 25ms azure_scheduler_test.go:150: Scaled Nodepool. Namespace: e2e-clusters-9545h, name: azure-scheduler-txzrs, replicas: 0xc00273f47c eventually.go:258: Failed to get **v1.Node: context deadline exceeded util.go:462: Failed to wait for 3 nodes to become ready in 30m0s: context deadline exceeded eventually.go:383: observed invalid **v1.Node state after 30m0s eventually.go:400: - observed **v1.Node collection invalid: expected 3 nodes, got 2
TestCreateCluster
45m25.57s
hypershift_framework.go:316: Successfully created hostedcluster e2e-clusters-pppfd/create-cluster-r6zfc in 2m37s hypershift_framework.go:115: Summarizing unexpected conditions for HostedCluster create-cluster-r6zfc util.go:2123: Successfully waited for HostedCluster e2e-clusters-pppfd/create-cluster-r6zfc to have valid conditions in 25ms hypershift_framework.go:194: skipping postTeardown() hypershift_framework.go:175: skipping teardown, already called
TestCreateCluster/ValidateHostedCluster
32m5.44s
util.go:218: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-pppfd/create-cluster-r6zfc in 1m18.025s util.go:235: Successfully waited for kubeconfig secret to have data in 25ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-r6zfc.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": EOF eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-r6zfc.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-r6zfc.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": EOF eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-r6zfc.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-r6zfc.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": EOF util.go:281: Successfully waited for a successful connection to the guest API server in 47.4s util.go:462: Failed to wait for 2 nodes to become ready in 30m0s: context deadline exceeded eventually.go:383: observed invalid **v1.Node state after 30m0s eventually.go:400: - observed **v1.Node collection invalid: expected 2 nodes, got 1
TestNodePool
0s
TestNodePool/HostedCluster0
49m6.67s
hypershift_framework.go:316: Successfully created hostedcluster e2e-clusters-x8w5s/node-pool-5jfjb in 2m28s hypershift_framework.go:115: Summarizing unexpected conditions for HostedCluster node-pool-5jfjb util.go:2123: Successfully waited for HostedCluster e2e-clusters-x8w5s/node-pool-5jfjb to have valid conditions in 25ms hypershift_framework.go:194: skipping postTeardown() hypershift_framework.go:175: skipping teardown, already called
TestNodePool/HostedCluster0/Main
70ms
util.go:218: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-x8w5s/node-pool-5jfjb in 25ms util.go:235: Successfully waited for kubeconfig secret to have data in 0s util.go:281: Successfully waited for a successful connection to the guest API server in 0s
TestNodePool/HostedCluster0/Main/TestMirrorConfigs
30m0.03s
nodepool_mirrorconfigs_test.go:61: Starting test MirrorConfigsTest util.go:462: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-x8w5s/node-pool-5jfjb-test-mirrorconfigs in 30m0s: context deadline exceeded eventually.go:383: observed invalid **v1.Node state after 30m0s eventually.go:400: - observed **v1.Node collection invalid: expected 1 nodes, got 0
TestNodePool/HostedCluster0/Main/TestNTOMachineConfigAppliedInPlace
30m0.02s
nodepool_nto_machineconfig_test.go:68: Starting test NTOMachineConfigRolloutTest eventually.go:258: Failed to get **v1.Node: context deadline exceeded util.go:462: Failed to wait for 2 nodes to become ready for NodePool e2e-clusters-x8w5s/node-pool-5jfjb-test-ntomachineconfig-inplace in 30m0s: context deadline exceeded eventually.go:383: observed invalid **v1.Node state after 30m0s eventually.go:400: - observed **v1.Node collection invalid: expected 2 nodes, got 0
TestNodePool/HostedCluster0/Main/TestNTOMachineConfigGetsRolledOut
30m0.04s
nodepool_nto_machineconfig_test.go:68: Starting test NTOMachineConfigRolloutTest eventually.go:258: Failed to get **v1.Node: Get "https://api-node-pool-5jfjb.aks-e2e.hypershift.azure.devcluster.openshift.com:443/api/v1/nodes?labelSelector=hypershift.openshift.io%2FnodePool%3Dnode-pool-5jfjb-test-ntomachineconfig-replace": context deadline exceeded util.go:462: Failed to wait for 2 nodes to become ready for NodePool e2e-clusters-x8w5s/node-pool-5jfjb-test-ntomachineconfig-replace in 30m0s: context deadline exceeded eventually.go:383: observed invalid **v1.Node state after 30m0s eventually.go:400: - observed **v1.Node collection invalid: expected 2 nodes, got 0
TestNodePool/HostedCluster0/Main/TestNTOPerformanceProfile
30m0.04s
nodepool_nto_performanceprofile_test.go:60: Starting test NTOPerformanceProfileTest eventually.go:258: Failed to get **v1.Node: context deadline exceeded util.go:462: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-x8w5s/node-pool-5jfjb-test-ntoperformanceprofile in 30m0s: context deadline exceeded eventually.go:383: observed invalid **v1.Node state after 30m0s eventually.go:400: - observed **v1.Node collection invalid: expected 1 nodes, got 0
TestNodePool/HostedCluster0/Main/TestNodePoolInPlaceUpgrade
30m0.02s
nodepool_upgrade_test.go:100: starting test NodePoolUpgradeTest util.go:462: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-x8w5s/node-pool-5jfjb-test-inplaceupgrade in 30m0s: context deadline exceeded eventually.go:383: observed invalid **v1.Node state after 30m0s eventually.go:400: - observed **v1.Node collection invalid: expected 1 nodes, got 0
TestNodePool/HostedCluster0/Main/TestNodePoolPrevReleaseN1
30m0.03s
nodepool_prev_release_test.go:31: Starting NodePoolPrevReleaseCreateTest. util.go:462: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-x8w5s/node-pool-5jfjb-qkjwm in 30m0s: context deadline exceeded eventually.go:383: observed invalid **v1.Node state after 30m0s eventually.go:400: - observed **v1.Node collection invalid: expected 1 nodes, got 0
TestNodePool/HostedCluster0/Main/TestNodePoolPrevReleaseN2
30m0.04s
nodepool_prev_release_test.go:31: Starting NodePoolPrevReleaseCreateTest. util.go:462: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-x8w5s/node-pool-5jfjb-w8bzz in 30m0s: context deadline exceeded eventually.go:383: observed invalid **v1.Node state after 30m0s eventually.go:400: - observed **v1.Node collection invalid: expected 1 nodes, got 0
TestNodePool/HostedCluster0/Main/TestNodePoolReplaceUpgrade
30m0.02s
nodepool_upgrade_test.go:100: starting test NodePoolUpgradeTest eventually.go:258: Failed to get **v1.Node: context deadline exceeded util.go:462: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-x8w5s/node-pool-5jfjb-test-replaceupgrade in 30m0s: context deadline exceeded eventually.go:383: observed invalid **v1.Node state after 30m0s eventually.go:400: - observed **v1.Node collection invalid: expected 1 nodes, got 0
TestNodePool/HostedCluster0/Main/TestNodepoolMachineconfigGetsRolledout
30m0.04s
nodepool_machineconfig_test.go:55: Starting test NodePoolMachineconfigRolloutTest eventually.go:258: Failed to get **v1.Node: context deadline exceeded util.go:462: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-x8w5s/node-pool-5jfjb-test-machineconfig in 30m0s: context deadline exceeded eventually.go:383: observed invalid **v1.Node state after 30m0s eventually.go:400: - observed **v1.Node collection invalid: expected 1 nodes, got 0
TestNodePool/HostedCluster2
54m2.1s
hypershift_framework.go:316: Successfully created hostedcluster e2e-clusters-z99kw/node-pool-tx9f7 in 2m0s hypershift_framework.go:115: Summarizing unexpected conditions for HostedCluster node-pool-tx9f7 eventually.go:104: Failed to get *v1beta1.HostedCluster: client rate limiter Wait returned an error: context deadline exceeded util.go:2123: Failed to wait for HostedCluster e2e-clusters-z99kw/node-pool-tx9f7 to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-z99kw/node-pool-tx9f7 invalid at RV 36435 after 2s: eventually.go:227: - incorrect condition: wanted ClusterVersionSucceeding=False, got ClusterVersionSucceeding=True: FromClusterVersion eventually.go:227: - incorrect condition: wanted ClusterVersionAvailable=False, got ClusterVersionAvailable=True: FromClusterVersion(Done applying 4.19.0-0.ci-2025-04-18-090537-test-ci-op-f5gz5rzr-latest) eventually.go:227: - incorrect condition: wanted ClusterVersionProgressing=True, got ClusterVersionProgressing=False: FromClusterVersion(Cluster version is 4.19.0-0.ci-2025-04-18-090537-test-ci-op-f5gz5rzr-latest) hypershift_framework.go:194: skipping postTeardown() hypershift_framework.go:175: skipping teardown, already called
TestNodePool/HostedCluster2/Main
60ms
util.go:218: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-z99kw/node-pool-tx9f7 in 25ms util.go:235: Successfully waited for kubeconfig secret to have data in 0s util.go:281: Successfully waited for a successful connection to the guest API server in 0s
TestNodePool/HostedCluster2/Main/TestAdditionalTrustBundlePropagation
36m8.16s
nodepool_additionalTrustBundlePropagation_test.go:36: Starting AdditionalTrustBundlePropagationTest. util.go:462: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-z99kw/node-pool-tx9f7-test-additional-trust-bundle-propagation in 5m49.025s nodepool_test.go:350: Successfully waited for NodePool e2e-clusters-z99kw/node-pool-tx9f7-test-additional-trust-bundle-propagation to have correct status in 9.025s eventually.go:104: Failed to get *v1beta1.NodePool: client rate limiter Wait returned an error: context deadline exceeded nodepool_test.go:350: Failed to wait for NodePool e2e-clusters-z99kw/node-pool-tx9f7-test-additional-trust-bundle-propagation to have correct status in 10m0s: context deadline exceeded eventually.go:224: observed *v1beta1.NodePool e2e-clusters-z99kw/node-pool-tx9f7-test-additional-trust-bundle-propagation invalid at RV 46253 after 10m0s: eventually.go:227: - incorrect condition: wanted AllNodesHealthy=True, got AllNodesHealthy=False: NodeProvisioning(Machine node-pool-tx9f7-test-additional-trust-bundle-propagation-24vqjv: NodeProvisioning ) eventually.go:227: - incorrect condition: wanted UpdatingConfig=False, got UpdatingConfig=True: AsExpected(Updating config in progress. Target config: f51d6e71) eventually.go:227: - incorrect condition: wanted ReachedIgnitionEndpoint=True, got ReachedIgnitionEndpoint=False: ignitionNotReached
TestNodePool/HostedCluster2/Main/TestAdditionalTrustBundlePropagation/AdditionalTrustBundlePropagationTest
20m10.1s
nodepool_additionalTrustBundlePropagation_test.go:70: Updating hosted cluster with additional trust bundle. Bundle: additional-trust-bundle nodepool_additionalTrustBundlePropagation_test.go:78: Successfully waited for Waiting for NodePool e2e-clusters-z99kw/node-pool-tx9f7-test-additional-trust-bundle-propagation to begin updating in 10.025s nodepool_additionalTrustBundlePropagation_test.go:92: Failed to wait for Waiting for NodePool e2e-clusters-z99kw/node-pool-tx9f7-test-additional-trust-bundle-propagation to stop updating in 20m0s: context deadline exceeded eventually.go:224: observed *v1beta1.NodePool e2e-clusters-z99kw/node-pool-tx9f7-test-additional-trust-bundle-propagation invalid at RV 30487 after 20m0s: eventually.go:227: - incorrect condition: wanted UpdatingConfig=False, got UpdatingConfig=True: AsExpected(Updating config in progress. Target config: f51d6e71) eventually.go:227: - incorrect condition: wanted AllNodesHealthy=True, got AllNodesHealthy=False: WaitingForNodeRef(Machine node-pool-tx9f7-test-additional-trust-bundle-propagation-24vqjv: WaitingForNodeRef ) nodepool_additionalTrustBundlePropagation_test.go:92: *v1beta1.NodePool e2e-clusters-z99kw/node-pool-tx9f7-test-additional-trust-bundle-propagation conditions: nodepool_additionalTrustBundlePropagation_test.go:92: UpdatingConfig=True: AsExpected(Updating config in progress. Target config: f51d6e71) nodepool_additionalTrustBundlePropagation_test.go:92: ValidGeneratedPayload=True: AsExpected(Payload generated successfully) nodepool_additionalTrustBundlePropagation_test.go:92: AllMachinesReady=False: Creating(1 of 2 machines are not ready Machine node-pool-tx9f7-test-additional-trust-bundle-propagation-24vqjv: Creating: virtualmachine creating or updating ) nodepool_additionalTrustBundlePropagation_test.go:92: AllNodesHealthy=False: WaitingForNodeRef(Machine node-pool-tx9f7-test-additional-trust-bundle-propagation-24vqjv: WaitingForNodeRef ) nodepool_additionalTrustBundlePropagation_test.go:92: UpdateManagementEnabled=True: AsExpected nodepool_additionalTrustBundlePropagation_test.go:92: ReconciliationActive=True: ReconciliationActive(Reconciliation active on resource) nodepool_additionalTrustBundlePropagation_test.go:92: ValidArchPlatform=True: AsExpected nodepool_additionalTrustBundlePropagation_test.go:92: ValidMachineConfig=True: AsExpected nodepool_additionalTrustBundlePropagation_test.go:92: UpdatingVersion=False: AsExpected nodepool_additionalTrustBundlePropagation_test.go:92: ReachedIgnitionEndpoint=False: ignitionNotReached nodepool_additionalTrustBundlePropagation_test.go:92: AutoscalingEnabled=False: AsExpected nodepool_additionalTrustBundlePropagation_test.go:92: ValidReleaseImage=True: AsExpected(Using release image: registry.build01.ci.openshift.org/ci-op-f5gz5rzr/release@sha256:cc275fe5f0244377a96fc1f3a53a3b806b9db8faf9c5ed1260afefe56c9ae0dd) nodepool_additionalTrustBundlePropagation_test.go:92: ValidTuningConfig=True: AsExpected nodepool_additionalTrustBundlePropagation_test.go:92: UpdatingPlatformMachineTemplate=False: AsExpected nodepool_additionalTrustBundlePropagation_test.go:92: Ready=True: AsExpected nodepool_additionalTrustBundlePropagation_test.go:92: AutorepairEnabled=False: AsExpected