kubernetes-sigs/cluster-api PR #7658 pull-cluster-api-e2e-informing-release-1-2 #1597514807043428352
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | sbueringer: [release-1.2] 🌱 Bump github.com/coredns/corefile-migration |
| Result | ABORTED |
| Tests | 1 failed / 1 succeeded |
| Started | |
| Elapsed | 24m51s |
| Revision | 5a9b702b20b66b20bada0fa8b04a12de009ee91d |
| Refs |
7658 |
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capi\-e2e\sWhen\supgrading\sa\sworkload\scluster\susing\sClusterClass\swith\sRuntimeSDK\s\[PR\-Informing\]\s\[ClusterClass\]\sShould\screate\,\supgrade\sand\sdelete\sa\sworkload\scluster$'
/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/cluster_upgrade_runtimesdk.go:129
Timed out after 300.010s.
Error: Unexpected non-nil/non-zero argument at index 1:
<*url.Error>: &url.Error{Op:"Get", URL:"https://127.0.0.1:44177/apis/cluster.x-k8s.io/v1beta1/namespaces/k8s-upgrade-with-runtimesdk-xspj85/machinepools/k8s-upgrade-with-runtimesdk-92naya-mp-0", Err:(*net.OpError)(0xc000b60280)}
/home/prow/go/src/sigs.k8s.io/cluster-api/test/framework/machinepool_helpers.go:267
STEP: Creating a namespace for hosting the "k8s-upgrade-with-runtimesdk" test spec
INFO: Creating namespace k8s-upgrade-with-runtimesdk-xspj85
INFO: Creating event watcher for namespace "k8s-upgrade-with-runtimesdk-xspj85"
STEP: Deploy Test Extension
serviceaccount/test-extension created
role.rbac.authorization.k8s.io/test-extension created
rolebinding.rbac.authorization.k8s.io/test-extension created
service/webhook-service created
deployment.apps/test-extension created
certificate.cert-manager.io/serving-cert created
issuer.cert-manager.io/selfsigned-issuer created
STEP: Deploy Test Extension ExtensionConfig and ConfigMap
STEP: Wait for test extension deployment to be availabel
STEP: Waiting for deployment k8s-upgrade-with-runtimesdk-xspj85/test-extension to be available
STEP: Watch Deployment logs of test extension
INFO: Creating log watcher for controller k8s-upgrade-with-runtimesdk-xspj85/test-extension, pod test-extension-5cc84bffbf-sftpb, container extension
STEP: Creating a workload cluster
INFO: Creating the workload cluster with name "k8s-upgrade-with-runtimesdk-92naya" using the "upgrades-runtimesdk" template (Kubernetes 1.24.4, 1 control-plane machines, 2 worker machines)
INFO: Getting the cluster template yaml
INFO: clusterctl config cluster k8s-upgrade-with-runtimesdk-92naya --infrastructure (default) --kubernetes-version 1.24.4 --control-plane-machine-count 1 --worker-machine-count 2 --flavor upgrades-runtimesdk
INFO: Applying the cluster template yaml to the cluster
clusterclass.cluster.x-k8s.io/quick-start-runtimesdk created
dockerclustertemplate.infrastructure.cluster.x-k8s.io/quick-start-cluster created
kubeadmcontrolplanetemplate.controlplane.cluster.x-k8s.io/quick-start-control-plane created
dockermachinetemplate.infrastructure.cluster.x-k8s.io/quick-start-control-plane created
dockermachinetemplate.infrastructure.cluster.x-k8s.io/quick-start-default-worker-machinetemplate created
kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/quick-start-default-worker-bootstraptemplate created
configmap/cni-k8s-upgrade-with-runtimesdk-92naya-crs-0 created
clusterresourceset.addons.cluster.x-k8s.io/k8s-upgrade-with-runtimesdk-92naya-crs-0 created
kubeadmconfig.bootstrap.cluster.x-k8s.io/k8s-upgrade-with-runtimesdk-92naya-mp-0-config created
cluster.cluster.x-k8s.io/k8s-upgrade-with-runtimesdk-92naya created
machinepool.cluster.x-k8s.io/k8s-upgrade-with-runtimesdk-92naya-mp-0 created
dockermachinepool.infrastructure.cluster.x-k8s.io/k8s-upgrade-with-runtimesdk-92naya-dmp-0 created
INFO: Calling PreWaitForCluster
INFO: Blocking with BeforeClusterCreate hook
STEP: Setting BeforeClusterCreate response to Status:Success to unblock the reconciliation
INFO: Waiting for the cluster infrastructure to be provisioned
STEP: Waiting for cluster to enter the provisioned phase
INFO: Waiting for control plane to be initialized
INFO: Waiting for the first control plane machine managed by k8s-upgrade-with-runtimesdk-xspj85/k8s-upgrade-with-runtimesdk-92naya-dv8ll to be provisioned
STEP: Waiting for one control plane node to exist
INFO: Waiting for control plane to be ready
INFO: Waiting for control plane k8s-upgrade-with-runtimesdk-xspj85/k8s-upgrade-with-runtimesdk-92naya-dv8ll to be ready (implies underlying nodes to be ready as well)
STEP: Waiting for the control plane to be ready
STEP: Checking all the the control plane machines are in the expected failure domains
INFO: Waiting for the machine deployments to be provisioned
STEP: Waiting for the workload nodes to exist
STEP: Checking all the machines controlled by k8s-upgrade-with-runtimesdk-92naya-md-0-8454b are in the "fd4" failure domain
INFO: Waiting for the machine pools to be provisioned
STEP: Waiting for the machine pool workload nodes
STEP: Upgrading the Cluster topology
INFO: Patching the new Kubernetes version to Cluster topology
INFO: Calling PreWaitForControlPlaneToBeUpgraded
INFO: Blocking with BeforeClusterUpgrade hook
STEP: Setting BeforeClusterUpgrade response to Status:Success to unblock the reconciliation
INFO: Waiting for control-plane machines to have the upgraded Kubernetes version
STEP: Ensuring all control-plane machines have upgraded kubernetes version v1.25.0
INFO: Waiting for kube-proxy to have the upgraded Kubernetes version
STEP: Ensuring kube-proxy has the correct image
INFO: Calling PreWaitForMachineDeploymentToBeUpgraded
INFO: Blocking with AfterControlPlaneUpgrade hook
STEP: Setting AfterControlPlaneUpgrade response to Status:Success to unblock the reconciliation
INFO: Waiting for Kubernetes versions of machines in MachineDeployment k8s-upgrade-with-runtimesdk-xspj85/k8s-upgrade-with-runtimesdk-92naya-md-0-8454b to be upgraded to v1.25.0
INFO: Ensuring all MachineDeployment Machines have upgraded kubernetes version v1.25.0
STEP: Upgrading the machinepool instances
INFO: Patching the new Kubernetes version to Machine Pool k8s-upgrade-with-runtimesdk-xspj85/k8s-upgrade-with-runtimesdk-92naya-mp-0
INFO: Waiting for Kubernetes versions of machines in MachinePool k8s-upgrade-with-runtimesdk-xspj85/k8s-upgrade-with-runtimesdk-92naya-mp-0 to be upgraded from v1.24.4 to v1.25.0
INFO: Ensuring all MachinePool Instances have upgraded kubernetes version v1.25.0
from junit.e2e_suite.2.xml
Filter through log files | View test history on testgrid
capi-e2e When following the Cluster API quick-start with ClusterClass [PR-Informing] [ClusterClass] Should create a workload cluster
capi-e2e When following the Cluster API quick-start [PR-Blocking] Should create a workload cluster
capi-e2e When following the Cluster API quick-start with IPv6 [IPv6] [PR-Informing] Should create a workload cluster
capi-e2e When following the Cluster API quick-start with Ignition Should create a workload cluster
capi-e2e When testing Cluster API working on self-hosted clusters Should pivot the bootstrap cluster to a self-hosted cluster
capi-e2e When testing Cluster API working on self-hosted clusters using ClusterClass [ClusterClass] Should pivot the bootstrap cluster to a self-hosted cluster
capi-e2e When testing ClusterClass changes [ClusterClass] Should successfully rollout the managed topology upon changes to the ClusterClass
capi-e2e When testing K8S conformance [Conformance] Should create a workload cluster and run kubetest
capi-e2e When testing KCP adoption Should adopt up-to-date control plane Machines without modification
capi-e2e When testing MachineDeployment rolling upgrades Should successfully upgrade Machines upon changes in relevant MachineDeployment fields
capi-e2e When testing MachineDeployment scale out/in Should successfully scale a MachineDeployment up and down upon changes to the MachineDeployment replica count
capi-e2e When testing MachinePools Should successfully create a cluster with machine pool machines
capi-e2e When testing clusterctl upgrades [clusterctl-Upgrade] Should create a management cluster and then upgrade all the providers
capi-e2e When testing node drain timeout A node should be forcefully removed if it cannot be drained in time
capi-e2e When testing unhealthy machines remediation Should successfully trigger KCP remediation
capi-e2e When testing unhealthy machines remediation Should successfully trigger machine deployment remediation
capi-e2e When upgrading a workload cluster using ClusterClass [ClusterClass] Should create and upgrade a workload cluster and eventually run kubetest
capi-e2e When upgrading a workload cluster using ClusterClass and testing K8S conformance [Conformance] [K8s-Upgrade] [ClusterClass] Should create and upgrade a workload cluster and eventually run kubetest
capi-e2e When upgrading a workload cluster using ClusterClass with a HA control plane [ClusterClass] Should create and upgrade a workload cluster and eventually run kubetest
capi-e2e When upgrading a workload cluster using ClusterClass with a HA control plane using scale-in rollout [ClusterClass] Should create and upgrade a workload cluster and eventually run kubetest
... skipping 1130 lines ... INFO: Waiting for the machine deployments to be provisioned STEP: Waiting for the workload nodes to exist STEP: Checking all the machines controlled by quick-start-0itu85-md-0-tzklh are in the "fd4" failure domain INFO: Waiting for the machine pools to be provisioned STEP: PASSED! STEP: Dumping logs from the "quick-start-0itu85" workload cluster Failed to get logs for machine quick-start-0itu85-md-0-tzklh-7c4d9d5fdc-6pvcc, cluster quick-start-anf8x1/quick-start-0itu85: exit status 2 Failed to get logs for machine quick-start-0itu85-qwsqh-snfm7, cluster quick-start-anf8x1/quick-start-0itu85: exit status 2 STEP: Dumping all the Cluster API resources in the "quick-start-anf8x1" namespace STEP: Deleting cluster quick-start-anf8x1/quick-start-0itu85 STEP: Deleting cluster quick-start-0itu85 INFO: Waiting for the Cluster quick-start-anf8x1/quick-start-0itu85 to be deleted STEP: Waiting for cluster quick-start-0itu85 to be deleted STEP: Deleting namespace used for hosting the "quick-start" test spec ... skipping 10 lines ...