Skip to content

Instantly share code, notes, and snippets.

@richardcase

richardcase/e2e.log

Created May 1, 2026 12:48
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save richardcase/6e550972888e3c4d09ae447b2a7b2e19 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save richardcase/6e550972888e3c4d09ae447b2a7b2e19 to your computer and use it in GitHub Desktop.
Download ZIP
k3s CAPI e2e log
Raw
e2e.log
achineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 12:15:53.609662 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
STEP: Waiting for the cluster infrastructure of cluster workload-cluster-creation-8wce72/capik3s-create-g5wioo to be provisioned @ 05/01/26 12:15:53.609
STEP: Waiting for cluster to enter the provisioned phase @ 05/01/26 12:15:53.616
STEP: Waiting for control plane of cluster workload-cluster-creation-8wce72/capik3s-create-g5wioo to be initialized @ 05/01/26 12:16:03.627
STEP: Waiting for the first control plane machine managed by workload-cluster-creation-8wce72/capik3s-create-g5wioo-control-plane to be provisioned @ 05/01/26 12:16:03.647
STEP: Waiting for one control plane node to exist @ 05/01/26 12:16:03.647
STEP: Waiting for control plane of cluster workload-cluster-creation-8wce72/capik3s-create-g5wioo to be ready @ 05/01/26 12:17:03.705
STEP: Waiting for control plane workload-cluster-creation-8wce72/capik3s-create-g5wioo-control-plane to be ready (implies underlying nodes to be ready as well) @ 05/01/26 12:17:03.708
STEP: Waiting for the control plane to be ready @ 05/01/26 12:17:03.708
STEP: Checking all the control plane machines are in the expected failure domains @ 05/01/26 12:17:03.726
STEP: Waiting for the machine deployments of cluster workload-cluster-creation-8wce72/capik3s-create-g5wioo to be provisioned @ 05/01/26 12:17:03.728
STEP: Waiting for the workload nodes to exist @ 05/01/26 12:17:03.735
STEP: Checking all the machines controlled by capik3s-create-g5wioo-md-0 are in the "" failure domain @ 05/01/26 12:20:04.002
STEP: Waiting for the machine pools of cluster workload-cluster-creation-8wce72/capik3s-create-g5wioo to be provisioned @ 05/01/26 12:20:04.01
STEP: Dumping logs from the "capik3s-create-g5wioo" workload cluster @ 05/01/26 12:20:04.027
STEP: Dumping all the Cluster API resources in the "workload-cluster-creation-8wce72" namespace @ 05/01/26 12:20:04.743
INFO: clusterctl describe cluster capik3s-create-g5wioo --show-conditions=all --show-machinesets=true --grouping=false --echo=true --v1beta2
STEP: Deleting all clusters in the workload-cluster-creation-8wce72 namespace @ 05/01/26 12:20:05.023
STEP: Deleting cluster workload-cluster-creation-8wce72/capik3s-create-g5wioo @ 05/01/26 12:20:05.031
INFO: Waiting for the Cluster workload-cluster-creation-8wce72/capik3s-create-g5wioo to be deleted
STEP: Waiting for cluster workload-cluster-creation-8wce72/capik3s-create-g5wioo to be deleted @ 05/01/26 12:20:05.048
STEP: Deleting namespace used for hosting the "workload-cluster-creation" test spec @ 05/01/26 12:20:35.097
INFO: Deleting namespace workload-cluster-creation-8wce72
• [281.760 seconds]
------------------------------
Workload cluster creation Creating a cluster with clusterclass [ClusterClass] Should create a workload cluster with clusterclass
/Users/richard/code/oss/cluster-api-k3s/test/e2e/create_test.go:127
STEP: Creating a namespace for hosting the "workload-cluster-creation" test spec @ 05/01/26 12:20:35.108
INFO: Creating namespace workload-cluster-creation-q9bhbi
INFO: Creating event watcher for namespace "workload-cluster-creation-q9bhbi"
STEP: Creating a workload cluster with v1beta1 controlplane @ 05/01/26 12:20:35.121
STEP: Creating the workload cluster with name "capik3s-create-yukixr" using the "topology" template (Kubernetes v1.33.5+k3s1, 1 control-plane machines, 1 worker machines) @ 05/01/26 12:20:35.121
STEP: Getting the cluster template yaml @ 05/01/26 12:20:35.121
INFO: clusterctl config cluster capik3s-create-yukixr --infrastructure docker --kubernetes-version v1.33.5+k3s1 --control-plane-machine-count 1 --worker-machine-count 1 --flavor topology
I0501 12:20:35.197517 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 ClusterClass is deprecated; use cluster.x-k8s.io/v1beta2 ClusterClass"
I0501 12:20:35.198866 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerClusterTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerClusterTemplate"
I0501 12:20:35.201019 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 12:20:35.202909 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 12:20:35.204516 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachinePoolTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachinePoolTemplate"
STEP: Applying the cluster template yaml to the cluster @ 05/01/26 12:20:35.205
STEP: Creating the workload cluster with name "capik3s-create-yukixr" from the provided yaml @ 05/01/26 12:20:35.205
STEP: Applying the cluster template yaml of cluster workload-cluster-creation-q9bhbi/capik3s-create-yukixr @ 05/01/26 12:20:35.205
I0501 12:20:35.210058 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 ClusterClass is deprecated; use cluster.x-k8s.io/v1beta2 ClusterClass"
I0501 12:20:35.229796 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 ClusterClass is deprecated; use cluster.x-k8s.io/v1beta2 ClusterClass"
I0501 12:20:35.235629 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerClusterTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerClusterTemplate"
I0501 12:20:35.252327 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerClusterTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerClusterTemplate"
I0501 12:20:35.271006 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 12:20:35.281370 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 12:20:35.307126 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 12:20:35.316765 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 12:20:35.321011 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachinePoolTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachinePoolTemplate"
I0501 12:20:35.330774 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachinePoolTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachinePoolTemplate"
I0501 12:20:35.334889 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 Cluster is deprecated; use cluster.x-k8s.io/v1beta2 Cluster"
I0501 12:20:35.552082 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 Cluster is deprecated; use cluster.x-k8s.io/v1beta2 Cluster"
STEP: Waiting for the cluster infrastructure of cluster workload-cluster-creation-q9bhbi/capik3s-create-yukixr to be provisioned @ 05/01/26 12:20:35.552
STEP: Waiting for cluster to enter the provisioned phase @ 05/01/26 12:20:35.562
STEP: Waiting for control plane of cluster workload-cluster-creation-q9bhbi/capik3s-create-yukixr to be initialized @ 05/01/26 12:20:45.601
STEP: Waiting for the first control plane machine managed by workload-cluster-creation-q9bhbi/capik3s-create-yukixr-dvzsj to be provisioned @ 05/01/26 12:20:45.608
STEP: Waiting for one control plane node to exist @ 05/01/26 12:20:45.608
STEP: Waiting for control plane of cluster workload-cluster-creation-q9bhbi/capik3s-create-yukixr to be ready @ 05/01/26 12:21:45.789
STEP: Waiting for control plane workload-cluster-creation-q9bhbi/capik3s-create-yukixr-dvzsj to be ready (implies underlying nodes to be ready as well) @ 05/01/26 12:21:45.791
STEP: Waiting for the control plane to be ready @ 05/01/26 12:21:45.791
STEP: Checking all the control plane machines are in the expected failure domains @ 05/01/26 12:21:45.817
STEP: Waiting for the machine deployments of cluster workload-cluster-creation-q9bhbi/capik3s-create-yukixr to be provisioned @ 05/01/26 12:21:45.821
STEP: Waiting for the workload nodes to exist @ 05/01/26 12:21:45.827
STEP: Checking all the machines controlled by capik3s-create-yukixr-capik3s-create-yukixr-md-0-d22gc are in the "" failure domain @ 05/01/26 12:24:26.019
STEP: Waiting for the machine pools of cluster workload-cluster-creation-q9bhbi/capik3s-create-yukixr to be provisioned @ 05/01/26 12:24:26.029
STEP: Dumping logs from the "capik3s-create-yukixr" workload cluster @ 05/01/26 12:24:26.047
STEP: Dumping all the Cluster API resources in the "workload-cluster-creation-q9bhbi" namespace @ 05/01/26 12:24:26.586
INFO: clusterctl describe cluster capik3s-create-yukixr --show-conditions=all --show-machinesets=true --grouping=false --echo=true --v1beta2
STEP: Deleting all clusters in the workload-cluster-creation-q9bhbi namespace @ 05/01/26 12:24:26.824
STEP: Deleting cluster workload-cluster-creation-q9bhbi/capik3s-create-yukixr @ 05/01/26 12:24:26.831
INFO: Waiting for the Cluster workload-cluster-creation-q9bhbi/capik3s-create-yukixr to be deleted
STEP: Waiting for cluster workload-cluster-creation-q9bhbi/capik3s-create-yukixr to be deleted @ 05/01/26 12:24:26.846
STEP: Deleting namespace used for hosting the "workload-cluster-creation" test spec @ 05/01/26 12:24:56.904
INFO: Deleting namespace workload-cluster-creation-q9bhbi
• [261.816 seconds]
------------------------------
Workload cluster upgrade K3s-Upgrade Upgrading a cluster with 1 control plane Should create and upgrade a workload cluster
/Users/richard/code/oss/cluster-api-k3s/test/e2e/cluster_upgrade.go:141
STEP: Creating a namespace for hosting the "workload-cluster-upgrade" test spec @ 05/01/26 12:24:56.917
INFO: Creating namespace workload-cluster-upgrade-r1fjym
INFO: Creating event watcher for namespace "workload-cluster-upgrade-r1fjym"
STEP: Creating a workload cluster @ 05/01/26 12:24:56.933
STEP: Creating the workload cluster with name "capik3s-cluster-upgrade-hejz1g" using the "" template (Kubernetes v1.33.5+k3s1, 1 control-plane machines, 2 worker machines) @ 05/01/26 12:24:56.933
STEP: Getting the cluster template yaml @ 05/01/26 12:24:56.933
INFO: clusterctl config cluster capik3s-cluster-upgrade-hejz1g --infrastructure docker --kubernetes-version v1.33.5+k3s1 --control-plane-machine-count 1 --worker-machine-count 2 --flavor (default)
STEP: Applying the cluster template yaml to the cluster @ 05/01/26 12:24:56.986
STEP: Creating the workload cluster with name "capik3s-cluster-upgrade-hejz1g" from the provided yaml @ 05/01/26 12:24:56.986
STEP: Applying the cluster template yaml of cluster workload-cluster-upgrade-r1fjym/capik3s-cluster-upgrade-hejz1g @ 05/01/26 12:24:56.986
I0501 12:24:57.012324 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 Cluster is deprecated; use cluster.x-k8s.io/v1beta2 Cluster"
I0501 12:24:57.025006 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 Cluster is deprecated; use cluster.x-k8s.io/v1beta2 Cluster"
I0501 12:24:57.029588 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 MachineDeployment is deprecated; use cluster.x-k8s.io/v1beta2 MachineDeployment"
I0501 12:24:57.045916 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 MachineDeployment is deprecated; use cluster.x-k8s.io/v1beta2 MachineDeployment"
I0501 12:24:57.099085 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerCluster is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerCluster"
I0501 12:24:57.123468 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerCluster is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerCluster"
I0501 12:24:57.131216 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 12:24:57.148290 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 12:24:57.156534 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 12:24:57.170389 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
STEP: Waiting for the cluster infrastructure of cluster workload-cluster-upgrade-r1fjym/capik3s-cluster-upgrade-hejz1g to be provisioned @ 05/01/26 12:24:57.17
STEP: Waiting for cluster to enter the provisioned phase @ 05/01/26 12:24:57.178
STEP: Waiting for control plane of cluster workload-cluster-upgrade-r1fjym/capik3s-cluster-upgrade-hejz1g to be initialized @ 05/01/26 12:25:07.19
STEP: Waiting for the first control plane machine managed by workload-cluster-upgrade-r1fjym/capik3s-cluster-upgrade-hejz1g-control-plane to be provisioned @ 05/01/26 12:25:07.197
STEP: Waiting for one control plane node to exist @ 05/01/26 12:25:07.197
STEP: Waiting for control plane of cluster workload-cluster-upgrade-r1fjym/capik3s-cluster-upgrade-hejz1g to be ready @ 05/01/26 12:26:07.252
STEP: Waiting for control plane workload-cluster-upgrade-r1fjym/capik3s-cluster-upgrade-hejz1g-control-plane to be ready (implies underlying nodes to be ready as well) @ 05/01/26 12:26:07.254
STEP: Waiting for the control plane to be ready @ 05/01/26 12:26:07.254
STEP: Checking all the control plane machines are in the expected failure domains @ 05/01/26 12:26:07.764
STEP: Waiting for the machine deployments of cluster workload-cluster-upgrade-r1fjym/capik3s-cluster-upgrade-hejz1g to be provisioned @ 05/01/26 12:26:07.769
STEP: Waiting for the workload nodes to exist @ 05/01/26 12:26:07.78
STEP: Checking all the machines controlled by capik3s-cluster-upgrade-hejz1g-md-0 are in the "" failure domain @ 05/01/26 12:28:57.977
STEP: Waiting for the machine pools of cluster workload-cluster-upgrade-r1fjym/capik3s-cluster-upgrade-hejz1g to be provisioned @ 05/01/26 12:28:57.987
STEP: Upgrading the Kubernetes control-plane @ 05/01/26 12:28:58.004
STEP: Patching the new kubernetes version to KCP @ 05/01/26 12:28:58.006
STEP: Waiting for control-plane machines to have the upgraded kubernetes version @ 05/01/26 12:28:58.061
STEP: Ensuring all control-plane machines have upgraded kubernetes version v1.34.5+k3s1 @ 05/01/26 12:28:58.061
STEP: Upgrading the machine deployment @ 05/01/26 12:31:18.205
INFO: Patching the new kubernetes version to Machine Deployment workload-cluster-upgrade-r1fjym/capik3s-cluster-upgrade-hejz1g-md-0
INFO: Waiting for Kubernetes versions of machines in MachineDeployment workload-cluster-upgrade-r1fjym/capik3s-cluster-upgrade-hejz1g-md-0 to be upgraded from v1.33.5+k3s1 to v1.34.5+k3s1
INFO: Ensuring all MachineDeployment Machines have upgraded kubernetes version v1.34.5+k3s1
STEP: Waiting until nodes are ready @ 05/01/26 12:38:28.761
STEP: Dumping logs from the "capik3s-cluster-upgrade-hejz1g" workload cluster @ 05/01/26 12:38:28.864
STEP: Dumping all the Cluster API resources in the "workload-cluster-upgrade-r1fjym" namespace @ 05/01/26 12:38:29.57
INFO: clusterctl describe cluster capik3s-cluster-upgrade-hejz1g --show-conditions=all --show-machinesets=true --grouping=false --echo=true --v1beta2
STEP: Deleting all clusters in the workload-cluster-upgrade-r1fjym namespace @ 05/01/26 12:38:29.847
STEP: Deleting cluster workload-cluster-upgrade-r1fjym/capik3s-cluster-upgrade-hejz1g @ 05/01/26 12:38:29.853
INFO: Waiting for the Cluster workload-cluster-upgrade-r1fjym/capik3s-cluster-upgrade-hejz1g to be deleted
STEP: Waiting for cluster workload-cluster-upgrade-r1fjym/capik3s-cluster-upgrade-hejz1g to be deleted @ 05/01/26 12:38:29.877
STEP: Deleting namespace used for hosting the "workload-cluster-upgrade" test spec @ 05/01/26 12:38:59.925
INFO: Deleting namespace workload-cluster-upgrade-r1fjym
• [843.027 seconds]
------------------------------
Workload cluster upgrade K3s-Upgrade Upgrading a cluster with HA control plane Should create and upgrade a workload cluster
/Users/richard/code/oss/cluster-api-k3s/test/e2e/cluster_upgrade.go:141
STEP: Creating a namespace for hosting the "workload-cluster-upgrade" test spec @ 05/01/26 12:38:59.946
INFO: Creating namespace workload-cluster-upgrade-6vzndx
INFO: Creating event watcher for namespace "workload-cluster-upgrade-6vzndx"
STEP: Creating a workload cluster @ 05/01/26 12:38:59.963
STEP: Creating the workload cluster with name "capik3s-cluster-upgrade-cziuh7" using the "" template (Kubernetes v1.33.5+k3s1, 3 control-plane machines, 1 worker machines) @ 05/01/26 12:38:59.963
STEP: Getting the cluster template yaml @ 05/01/26 12:38:59.963
INFO: clusterctl config cluster capik3s-cluster-upgrade-cziuh7 --infrastructure docker --kubernetes-version v1.33.5+k3s1 --control-plane-machine-count 3 --worker-machine-count 1 --flavor (default)
STEP: Applying the cluster template yaml to the cluster @ 05/01/26 12:39:00.004
STEP: Creating the workload cluster with name "capik3s-cluster-upgrade-cziuh7" from the provided yaml @ 05/01/26 12:39:00.004
STEP: Applying the cluster template yaml of cluster workload-cluster-upgrade-6vzndx/capik3s-cluster-upgrade-cziuh7 @ 05/01/26 12:39:00.004
I0501 12:39:00.027891 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 Cluster is deprecated; use cluster.x-k8s.io/v1beta2 Cluster"
I0501 12:39:00.042732 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 Cluster is deprecated; use cluster.x-k8s.io/v1beta2 Cluster"
I0501 12:39:00.049835 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 MachineDeployment is deprecated; use cluster.x-k8s.io/v1beta2 MachineDeployment"
I0501 12:39:00.085187 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 MachineDeployment is deprecated; use cluster.x-k8s.io/v1beta2 MachineDeployment"
I0501 12:39:00.106528 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerCluster is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerCluster"
I0501 12:39:00.119247 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerCluster is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerCluster"
I0501 12:39:00.126702 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 12:39:00.142834 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 12:39:00.149557 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 12:39:00.161572 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
STEP: Waiting for the cluster infrastructure of cluster workload-cluster-upgrade-6vzndx/capik3s-cluster-upgrade-cziuh7 to be provisioned @ 05/01/26 12:39:00.161
STEP: Waiting for cluster to enter the provisioned phase @ 05/01/26 12:39:00.171
STEP: Waiting for control plane of cluster workload-cluster-upgrade-6vzndx/capik3s-cluster-upgrade-cziuh7 to be initialized @ 05/01/26 12:39:10.181
STEP: Waiting for the first control plane machine managed by workload-cluster-upgrade-6vzndx/capik3s-cluster-upgrade-cziuh7-control-plane to be provisioned @ 05/01/26 12:39:10.195
STEP: Waiting for one control plane node to exist @ 05/01/26 12:39:10.195
STEP: Waiting for control plane of cluster workload-cluster-upgrade-6vzndx/capik3s-cluster-upgrade-cziuh7 to be ready @ 05/01/26 12:40:10.231
STEP: Waiting for the remaining control plane machines managed by workload-cluster-upgrade-6vzndx/capik3s-cluster-upgrade-cziuh7-control-plane to be provisioned @ 05/01/26 12:40:10.231
STEP: Waiting for all control plane nodes to exist @ 05/01/26 12:40:10.231
STEP: Waiting for control plane workload-cluster-upgrade-6vzndx/capik3s-cluster-upgrade-cziuh7-control-plane to be ready (implies underlying nodes to be ready as well) @ 05/01/26 12:42:20.381
STEP: Waiting for the control plane to be ready @ 05/01/26 12:42:20.381
STEP: Checking all the control plane machines are in the expected failure domains @ 05/01/26 12:42:20.387
STEP: Waiting for the machine deployments of cluster workload-cluster-upgrade-6vzndx/capik3s-cluster-upgrade-cziuh7 to be provisioned @ 05/01/26 12:42:20.392
STEP: Waiting for the workload nodes to exist @ 05/01/26 12:42:20.415
STEP: Checking all the machines controlled by capik3s-cluster-upgrade-cziuh7-md-0 are in the "" failure domain @ 05/01/26 12:42:50.449
STEP: Waiting for the machine pools of cluster workload-cluster-upgrade-6vzndx/capik3s-cluster-upgrade-cziuh7 to be provisioned @ 05/01/26 12:42:50.454
STEP: Upgrading the Kubernetes control-plane @ 05/01/26 12:42:50.463
STEP: Patching the new kubernetes version to KCP @ 05/01/26 12:42:50.463
STEP: Waiting for control-plane machines to have the upgraded kubernetes version @ 05/01/26 12:42:50.53
STEP: Ensuring all control-plane machines have upgraded kubernetes version v1.34.5+k3s1 @ 05/01/26 12:42:50.53
STEP: Upgrading the machine deployment @ 05/01/26 12:50:32.006
INFO: Patching the new kubernetes version to Machine Deployment workload-cluster-upgrade-6vzndx/capik3s-cluster-upgrade-cziuh7-md-0
INFO: Waiting for Kubernetes versions of machines in MachineDeployment workload-cluster-upgrade-6vzndx/capik3s-cluster-upgrade-cziuh7-md-0 to be upgraded from v1.33.5+k3s1 to v1.34.5+k3s1
INFO: Ensuring all MachineDeployment Machines have upgraded kubernetes version v1.34.5+k3s1
STEP: Waiting until nodes are ready @ 05/01/26 12:54:22.307
STEP: Dumping logs from the "capik3s-cluster-upgrade-cziuh7" workload cluster @ 05/01/26 12:54:22.4
STEP: Dumping all the Cluster API resources in the "workload-cluster-upgrade-6vzndx" namespace @ 05/01/26 12:54:23.258
INFO: clusterctl describe cluster capik3s-cluster-upgrade-cziuh7 --show-conditions=all --show-machinesets=true --grouping=false --echo=true --v1beta2
STEP: Deleting all clusters in the workload-cluster-upgrade-6vzndx namespace @ 05/01/26 12:54:23.551
STEP: Deleting cluster workload-cluster-upgrade-6vzndx/capik3s-cluster-upgrade-cziuh7 @ 05/01/26 12:54:23.557
INFO: Waiting for the Cluster workload-cluster-upgrade-6vzndx/capik3s-cluster-upgrade-cziuh7 to be deleted
STEP: Waiting for cluster workload-cluster-upgrade-6vzndx/capik3s-cluster-upgrade-cziuh7 to be deleted @ 05/01/26 12:54:23.577
STEP: Deleting namespace used for hosting the "workload-cluster-upgrade" test spec @ 05/01/26 12:54:53.628
INFO: Deleting namespace workload-cluster-upgrade-6vzndx
• [953.696 seconds]
------------------------------
Workload cluster upgrade K3s-Upgrade Upgrading a cluster with ClusterClass [ClusterClass] Should create and upgrade a workload cluster
/Users/richard/code/oss/cluster-api-k3s/test/e2e/cluster_upgrade.go:141
STEP: Creating a namespace for hosting the "workload-cluster-upgrade" test spec @ 05/01/26 12:54:53.664
INFO: Creating namespace workload-cluster-upgrade-bb4wk4
INFO: Creating event watcher for namespace "workload-cluster-upgrade-bb4wk4"
STEP: Creating a workload cluster @ 05/01/26 12:54:53.677
STEP: Creating the workload cluster with name "capik3s-cluster-upgrade-u6ymea" using the "topology" template (Kubernetes v1.33.5+k3s1, 1 control-plane machines, 2 worker machines) @ 05/01/26 12:54:53.677
STEP: Getting the cluster template yaml @ 05/01/26 12:54:53.677
INFO: clusterctl config cluster capik3s-cluster-upgrade-u6ymea --infrastructure docker --kubernetes-version v1.33.5+k3s1 --control-plane-machine-count 1 --worker-machine-count 2 --flavor topology
I0501 12:54:53.785767 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 ClusterClass is deprecated; use cluster.x-k8s.io/v1beta2 ClusterClass"
I0501 12:54:53.787821 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerClusterTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerClusterTemplate"
I0501 12:54:53.790222 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 12:54:53.792055 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 12:54:53.793170 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachinePoolTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachinePoolTemplate"
STEP: Applying the cluster template yaml to the cluster @ 05/01/26 12:54:53.793
STEP: Creating the workload cluster with name "capik3s-cluster-upgrade-u6ymea" from the provided yaml @ 05/01/26 12:54:53.794
STEP: Applying the cluster template yaml of cluster workload-cluster-upgrade-bb4wk4/capik3s-cluster-upgrade-u6ymea @ 05/01/26 12:54:53.794
I0501 12:54:53.798378 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 ClusterClass is deprecated; use cluster.x-k8s.io/v1beta2 ClusterClass"
I0501 12:54:53.817087 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 ClusterClass is deprecated; use cluster.x-k8s.io/v1beta2 ClusterClass"
I0501 12:54:53.824330 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerClusterTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerClusterTemplate"
I0501 12:54:53.839027 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerClusterTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerClusterTemplate"
I0501 12:54:53.855410 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 12:54:53.865716 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 12:54:53.888208 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 12:54:53.896479 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 12:54:53.900565 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachinePoolTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachinePoolTemplate"
I0501 12:54:53.912892 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachinePoolTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachinePoolTemplate"
I0501 12:54:53.917205 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 Cluster is deprecated; use cluster.x-k8s.io/v1beta2 Cluster"
I0501 12:54:54.132466 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 Cluster is deprecated; use cluster.x-k8s.io/v1beta2 Cluster"
STEP: Waiting for the cluster infrastructure of cluster workload-cluster-upgrade-bb4wk4/capik3s-cluster-upgrade-u6ymea to be provisioned @ 05/01/26 12:54:54.132
STEP: Waiting for cluster to enter the provisioned phase @ 05/01/26 12:54:54.139
STEP: Waiting for control plane of cluster workload-cluster-upgrade-bb4wk4/capik3s-cluster-upgrade-u6ymea to be initialized @ 05/01/26 12:55:04.155
STEP: Waiting for the first control plane machine managed by workload-cluster-upgrade-bb4wk4/capik3s-cluster-upgrade-u6ymea-lvqdh to be provisioned @ 05/01/26 12:55:04.16
STEP: Waiting for one control plane node to exist @ 05/01/26 12:55:04.16
STEP: Waiting for control plane of cluster workload-cluster-upgrade-bb4wk4/capik3s-cluster-upgrade-u6ymea to be ready @ 05/01/26 12:55:34.179
STEP: Waiting for control plane workload-cluster-upgrade-bb4wk4/capik3s-cluster-upgrade-u6ymea-lvqdh to be ready (implies underlying nodes to be ready as well) @ 05/01/26 12:55:34.182
STEP: Waiting for the control plane to be ready @ 05/01/26 12:55:34.182
STEP: Checking all the control plane machines are in the expected failure domains @ 05/01/26 12:55:34.194
STEP: Waiting for the machine deployments of cluster workload-cluster-upgrade-bb4wk4/capik3s-cluster-upgrade-u6ymea to be provisioned @ 05/01/26 12:55:34.196
STEP: Waiting for the workload nodes to exist @ 05/01/26 12:55:34.205
STEP: Checking all the machines controlled by capik3s-cluster-upgrade-u6ymea-capik3s-cluster-upgrade-u6yspdq7 are in the "" failure domain @ 05/01/26 12:59:04.481
STEP: Waiting for the machine pools of cluster workload-cluster-upgrade-bb4wk4/capik3s-cluster-upgrade-u6ymea to be provisioned @ 05/01/26 12:59:04.497
STEP: Upgrading the Cluster topology @ 05/01/26 12:59:04.547
STEP: Patching the new Kubernetes version to Cluster topology @ 05/01/26 12:59:04.548
STEP: Waiting for control-plane machines to have the upgraded kubernetes version @ 05/01/26 12:59:04.595
STEP: Ensuring all control-plane machines have upgraded kubernetes version v1.34.5+k3s1 @ 05/01/26 12:59:04.595
STEP: Waiting for Kubernetes versions of machines in MachineDeployment workload-cluster-upgrade-bb4wk4/capik3s-cluster-upgrade-u6ymea-capik3s-cluster-upgrade-u6yspdq7 to be upgraded to v1.34.5+k3s1 @ 05/01/26 13:01:24.703
INFO: Ensuring all MachineDeployment Machines have upgraded kubernetes version v1.34.5+k3s1
STEP: Waiting until nodes are ready @ 05/01/26 13:09:05.222
STEP: Dumping logs from the "capik3s-cluster-upgrade-u6ymea" workload cluster @ 05/01/26 13:09:05.329
STEP: Dumping all the Cluster API resources in the "workload-cluster-upgrade-bb4wk4" namespace @ 05/01/26 13:09:06.016
INFO: clusterctl describe cluster capik3s-cluster-upgrade-u6ymea --show-conditions=all --show-machinesets=true --grouping=false --echo=true --v1beta2
STEP: Deleting all clusters in the workload-cluster-upgrade-bb4wk4 namespace @ 05/01/26 13:09:06.331
STEP: Deleting cluster workload-cluster-upgrade-bb4wk4/capik3s-cluster-upgrade-u6ymea @ 05/01/26 13:09:06.338
INFO: Waiting for the Cluster workload-cluster-upgrade-bb4wk4/capik3s-cluster-upgrade-u6ymea to be deleted
STEP: Waiting for cluster workload-cluster-upgrade-bb4wk4/capik3s-cluster-upgrade-u6ymea to be deleted @ 05/01/26 13:09:06.356
STEP: Deleting namespace used for hosting the "workload-cluster-upgrade" test spec @ 05/01/26 13:09:36.42
INFO: Deleting namespace workload-cluster-upgrade-bb4wk4
• [882.772 seconds]
------------------------------
When testing MachineDeployment remediation Machine deployment remediation Should replace unhealthy machines
/Users/richard/code/oss/cluster-api-k3s/test/e2e/md_remediation_test.go:81
STEP: Creating a namespace for hosting the "machine-deployment-remediation" test spec @ 05/01/26 13:09:36.443
INFO: Creating namespace machine-deployment-remediation-qa6ncw
INFO: Creating event watcher for namespace "machine-deployment-remediation-qa6ncw"
STEP: Creating a workload cluster @ 05/01/26 13:09:36.465
STEP: Creating the workload cluster with name "capik3s-md-remediation-x2h3hz" using the "md-remediation" template (Kubernetes v1.33.5+k3s1, 1 control-plane machines, 1 worker machines) @ 05/01/26 13:09:36.465
STEP: Getting the cluster template yaml @ 05/01/26 13:09:36.465
INFO: clusterctl config cluster capik3s-md-remediation-x2h3hz --infrastructure docker --kubernetes-version v1.33.5+k3s1 --control-plane-machine-count 1 --worker-machine-count 1 --flavor md-remediation
STEP: Applying the cluster template yaml to the cluster @ 05/01/26 13:09:36.51
STEP: Creating the workload cluster with name "capik3s-md-remediation-x2h3hz" from the provided yaml @ 05/01/26 13:09:36.511
STEP: Applying the cluster template yaml of cluster machine-deployment-remediation-qa6ncw/capik3s-md-remediation-x2h3hz @ 05/01/26 13:09:36.511
I0501 13:09:36.573398 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 Cluster is deprecated; use cluster.x-k8s.io/v1beta2 Cluster"
I0501 13:09:36.585291 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 Cluster is deprecated; use cluster.x-k8s.io/v1beta2 Cluster"
I0501 13:09:36.589815 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 MachineDeployment is deprecated; use cluster.x-k8s.io/v1beta2 MachineDeployment"
I0501 13:09:36.602275 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 MachineDeployment is deprecated; use cluster.x-k8s.io/v1beta2 MachineDeployment"
I0501 13:09:36.606614 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 MachineHealthCheck is deprecated; use cluster.x-k8s.io/v1beta2 MachineHealthCheck"
I0501 13:09:36.622612 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 MachineHealthCheck is deprecated; use cluster.x-k8s.io/v1beta2 MachineHealthCheck"
I0501 13:09:36.645424 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerCluster is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerCluster"
I0501 13:09:36.659302 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerCluster is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerCluster"
I0501 13:09:36.667621 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 13:09:36.684834 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 13:09:36.690186 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 13:09:36.699363 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
STEP: Waiting for the cluster infrastructure of cluster machine-deployment-remediation-qa6ncw/capik3s-md-remediation-x2h3hz to be provisioned @ 05/01/26 13:09:36.699
STEP: Waiting for cluster to enter the provisioned phase @ 05/01/26 13:09:36.706
STEP: Waiting for control plane of cluster machine-deployment-remediation-qa6ncw/capik3s-md-remediation-x2h3hz to be initialized @ 05/01/26 13:09:46.72
STEP: Waiting for the first control plane machine managed by machine-deployment-remediation-qa6ncw/capik3s-md-remediation-x2h3hz-control-plane to be provisioned @ 05/01/26 13:09:46.731
STEP: Waiting for one control plane node to exist @ 05/01/26 13:09:46.732
STEP: Waiting for control plane of cluster machine-deployment-remediation-qa6ncw/capik3s-md-remediation-x2h3hz to be ready @ 05/01/26 13:10:46.782
STEP: Waiting for control plane machine-deployment-remediation-qa6ncw/capik3s-md-remediation-x2h3hz-control-plane to be ready (implies underlying nodes to be ready as well) @ 05/01/26 13:10:46.784
STEP: Waiting for the control plane to be ready @ 05/01/26 13:10:46.784
STEP: Checking all the control plane machines are in the expected failure domains @ 05/01/26 13:10:46.794
STEP: Waiting for the machine deployments of cluster machine-deployment-remediation-qa6ncw/capik3s-md-remediation-x2h3hz to be provisioned @ 05/01/26 13:10:46.798
STEP: Waiting for the workload nodes to exist @ 05/01/26 13:10:46.816
STEP: Checking all the machines controlled by capik3s-md-remediation-x2h3hz-md-0 are in the "" failure domain @ 05/01/26 13:13:47.033
STEP: Waiting for the machine pools of cluster machine-deployment-remediation-qa6ncw/capik3s-md-remediation-x2h3hz to be provisioned @ 05/01/26 13:13:47.038
STEP: Setting a machine unhealthy and wait for MachineDeployment remediation @ 05/01/26 13:13:47.046
Discovering machine health check resources
Ensuring there is at least 1 Machine that MachineHealthCheck is matching
Patching MachineHealthCheck unhealthy condition to one of the nodes
INFO: Patching the node condition to the node
Waiting for remediation
Waiting until the node with unhealthy node condition is remediated
STEP: Waiting until nodes are ready @ 05/01/26 13:17:07.501
STEP: PASSED! @ 05/01/26 13:17:07.53
STEP: Dumping logs from the "capik3s-md-remediation-x2h3hz" workload cluster @ 05/01/26 13:17:07.531
STEP: Dumping all the Cluster API resources in the "machine-deployment-remediation-qa6ncw" namespace @ 05/01/26 13:17:08.035
INFO: clusterctl describe cluster capik3s-md-remediation-x2h3hz --show-conditions=all --show-machinesets=true --grouping=false --echo=true --v1beta2
STEP: Deleting all clusters in the machine-deployment-remediation-qa6ncw namespace @ 05/01/26 13:17:08.333
STEP: Deleting cluster machine-deployment-remediation-qa6ncw/capik3s-md-remediation-x2h3hz @ 05/01/26 13:17:08.341
INFO: Waiting for the Cluster machine-deployment-remediation-qa6ncw/capik3s-md-remediation-x2h3hz to be deleted
STEP: Waiting for cluster machine-deployment-remediation-qa6ncw/capik3s-md-remediation-x2h3hz to be deleted @ 05/01/26 13:17:08.358
STEP: Deleting namespace used for hosting the "machine-deployment-remediation" test spec @ 05/01/26 13:17:38.412
INFO: Deleting namespace machine-deployment-remediation-qa6ncw
• [481.989 seconds]
------------------------------
Workload cluster scaling Scaling a cluster Should create a workload cluster with 1 worker node and scale
/Users/richard/code/oss/cluster-api-k3s/test/e2e/node_scale_test.go:80
STEP: Creating a namespace for hosting the "workload-cluster-scaling" test spec @ 05/01/26 13:17:38.435
INFO: Creating namespace workload-cluster-scaling-lzb016
INFO: Creating event watcher for namespace "workload-cluster-scaling-lzb016"
STEP: Creating a workload cluster with 1 control plane and 1 worker node @ 05/01/26 13:17:38.473
STEP: Creating the workload cluster with name "capik3s-node-scale-xe7kee" using the "" template (Kubernetes v1.33.5+k3s1, 1 control-plane machines, 1 worker machines) @ 05/01/26 13:17:38.473
STEP: Getting the cluster template yaml @ 05/01/26 13:17:38.473
INFO: clusterctl config cluster capik3s-node-scale-xe7kee --infrastructure docker --kubernetes-version v1.33.5+k3s1 --control-plane-machine-count 1 --worker-machine-count 1 --flavor (default)
STEP: Applying the cluster template yaml to the cluster @ 05/01/26 13:17:38.537
STEP: Creating the workload cluster with name "capik3s-node-scale-xe7kee" from the provided yaml @ 05/01/26 13:17:38.537
STEP: Applying the cluster template yaml of cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee @ 05/01/26 13:17:38.537
I0501 13:17:38.566014 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 Cluster is deprecated; use cluster.x-k8s.io/v1beta2 Cluster"
I0501 13:17:38.580523 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 Cluster is deprecated; use cluster.x-k8s.io/v1beta2 Cluster"
I0501 13:17:38.586168 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 MachineDeployment is deprecated; use cluster.x-k8s.io/v1beta2 MachineDeployment"
I0501 13:17:38.604383 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 MachineDeployment is deprecated; use cluster.x-k8s.io/v1beta2 MachineDeployment"
I0501 13:17:38.629281 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerCluster is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerCluster"
I0501 13:17:38.642553 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerCluster is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerCluster"
I0501 13:17:38.649571 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 13:17:38.667551 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 13:17:38.675616 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 13:17:38.689343 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
STEP: Waiting for the cluster infrastructure of cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee to be provisioned @ 05/01/26 13:17:38.689
STEP: Waiting for cluster to enter the provisioned phase @ 05/01/26 13:17:38.699
STEP: Waiting for control plane of cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee to be initialized @ 05/01/26 13:17:48.71
STEP: Waiting for the first control plane machine managed by workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee-control-plane to be provisioned @ 05/01/26 13:17:48.721
STEP: Waiting for one control plane node to exist @ 05/01/26 13:17:48.721
STEP: Waiting for control plane of cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee to be ready @ 05/01/26 13:18:48.817
STEP: Waiting for control plane workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee-control-plane to be ready (implies underlying nodes to be ready as well) @ 05/01/26 13:18:48.99
STEP: Waiting for the control plane to be ready @ 05/01/26 13:18:48.99
STEP: Checking all the control plane machines are in the expected failure domains @ 05/01/26 13:18:49.028
STEP: Waiting for the machine deployments of cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee to be provisioned @ 05/01/26 13:18:49.031
STEP: Waiting for the workload nodes to exist @ 05/01/26 13:18:49.046
STEP: Checking all the machines controlled by capik3s-node-scale-xe7kee-md-0 are in the "" failure domain @ 05/01/26 13:21:39.299
STEP: Waiting for the machine pools of cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee to be provisioned @ 05/01/26 13:21:39.327
STEP: Scaling up worker nodes to 3 @ 05/01/26 13:21:39.35
STEP: Creating the workload cluster with name "capik3s-node-scale-xe7kee" using the "" template (Kubernetes v1.33.5+k3s1, 1 control-plane machines, 3 worker machines) @ 05/01/26 13:21:39.35
STEP: Getting the cluster template yaml @ 05/01/26 13:21:39.35
INFO: clusterctl config cluster capik3s-node-scale-xe7kee --infrastructure docker --kubernetes-version v1.33.5+k3s1 --control-plane-machine-count 1 --worker-machine-count 3 --flavor (default)
STEP: Applying the cluster template yaml to the cluster @ 05/01/26 13:21:39.413
STEP: Creating the workload cluster with name "capik3s-node-scale-xe7kee" from the provided yaml @ 05/01/26 13:21:39.413
STEP: Applying the cluster template yaml of cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee @ 05/01/26 13:21:39.413
I0501 13:21:39.477057 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 Cluster is deprecated; use cluster.x-k8s.io/v1beta2 Cluster"
I0501 13:21:39.620157 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 Cluster is deprecated; use cluster.x-k8s.io/v1beta2 Cluster"
I0501 13:21:39.629198 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 MachineDeployment is deprecated; use cluster.x-k8s.io/v1beta2 MachineDeployment"
I0501 13:21:39.678422 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 MachineDeployment is deprecated; use cluster.x-k8s.io/v1beta2 MachineDeployment"
I0501 13:21:39.734013 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerCluster is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerCluster"
I0501 13:21:39.777554 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerCluster is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerCluster"
I0501 13:21:39.793652 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 13:21:39.818637 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 13:21:39.827579 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 13:21:39.869437 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
STEP: Waiting for the cluster infrastructure of cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee to be provisioned @ 05/01/26 13:21:39.869
STEP: Waiting for cluster to enter the provisioned phase @ 05/01/26 13:21:39.897
STEP: Waiting for control plane of cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee to be initialized @ 05/01/26 13:21:39.909
STEP: Waiting for the first control plane machine managed by workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee-control-plane to be provisioned @ 05/01/26 13:21:39.922
STEP: Waiting for one control plane node to exist @ 05/01/26 13:21:39.922
STEP: Waiting for control plane of cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee to be ready @ 05/01/26 13:21:39.927
STEP: Waiting for control plane workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee-control-plane to be ready (implies underlying nodes to be ready as well) @ 05/01/26 13:21:39.928
STEP: Waiting for the control plane to be ready @ 05/01/26 13:21:39.928
STEP: Checking all the control plane machines are in the expected failure domains @ 05/01/26 13:21:39.95
STEP: Waiting for the machine deployments of cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee to be provisioned @ 05/01/26 13:21:39.971
STEP: Waiting for the workload nodes to exist @ 05/01/26 13:21:39.997
STEP: Checking all the machines controlled by capik3s-node-scale-xe7kee-md-0 are in the "" failure domain @ 05/01/26 13:24:50.283
STEP: Waiting for the machine pools of cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee to be provisioned @ 05/01/26 13:24:50.29
STEP: Scaling up control planes to 3 @ 05/01/26 13:24:50.306
STEP: Creating the workload cluster with name "capik3s-node-scale-xe7kee" using the "" template (Kubernetes v1.33.5+k3s1, 3 control-plane machines, 3 worker machines) @ 05/01/26 13:24:50.307
STEP: Getting the cluster template yaml @ 05/01/26 13:24:50.307
INFO: clusterctl config cluster capik3s-node-scale-xe7kee --infrastructure docker --kubernetes-version v1.33.5+k3s1 --control-plane-machine-count 3 --worker-machine-count 3 --flavor (default)
STEP: Applying the cluster template yaml to the cluster @ 05/01/26 13:24:50.358
STEP: Creating the workload cluster with name "capik3s-node-scale-xe7kee" from the provided yaml @ 05/01/26 13:24:50.358
STEP: Applying the cluster template yaml of cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee @ 05/01/26 13:24:50.358
I0501 13:24:50.407723 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 Cluster is deprecated; use cluster.x-k8s.io/v1beta2 Cluster"
I0501 13:24:50.438443 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 Cluster is deprecated; use cluster.x-k8s.io/v1beta2 Cluster"
I0501 13:24:50.445351 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 MachineDeployment is deprecated; use cluster.x-k8s.io/v1beta2 MachineDeployment"
I0501 13:24:50.479286 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 MachineDeployment is deprecated; use cluster.x-k8s.io/v1beta2 MachineDeployment"
I0501 13:24:50.541725 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerCluster is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerCluster"
I0501 13:24:50.571801 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerCluster is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerCluster"
I0501 13:24:50.587138 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 13:24:50.619645 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 13:24:50.626099 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 13:24:50.640205 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
STEP: Waiting for the cluster infrastructure of cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee to be provisioned @ 05/01/26 13:24:50.64
STEP: Waiting for cluster to enter the provisioned phase @ 05/01/26 13:24:50.649
STEP: Waiting for control plane of cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee to be initialized @ 05/01/26 13:24:50.652
STEP: Waiting for the first control plane machine managed by workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee-control-plane to be provisioned @ 05/01/26 13:24:50.661
STEP: Waiting for one control plane node to exist @ 05/01/26 13:24:50.661
STEP: Waiting for control plane of cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee to be ready @ 05/01/26 13:24:50.702
STEP: Waiting for the remaining control plane machines managed by workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee-control-plane to be provisioned @ 05/01/26 13:24:50.703
STEP: Waiting for all control plane nodes to exist @ 05/01/26 13:24:50.703
STEP: Waiting for control plane workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee-control-plane to be ready (implies underlying nodes to be ready as well) @ 05/01/26 13:26:50.801
STEP: Waiting for the control plane to be ready @ 05/01/26 13:26:50.801
STEP: Checking all the control plane machines are in the expected failure domains @ 05/01/26 13:26:50.812
STEP: Waiting for the machine deployments of cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee to be provisioned @ 05/01/26 13:26:50.816
STEP: Waiting for the workload nodes to exist @ 05/01/26 13:26:50.829
STEP: Checking all the machines controlled by capik3s-node-scale-xe7kee-md-0 are in the "" failure domain @ 05/01/26 13:26:50.835
STEP: Waiting for the machine pools of cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee to be provisioned @ 05/01/26 13:26:50.842
STEP: Scaling down control planes to 1 @ 05/01/26 13:26:50.851
STEP: Creating the workload cluster with name "capik3s-node-scale-xe7kee" using the "" template (Kubernetes v1.33.5+k3s1, 1 control-plane machines, 3 worker machines) @ 05/01/26 13:26:50.851
STEP: Getting the cluster template yaml @ 05/01/26 13:26:50.851
INFO: clusterctl config cluster capik3s-node-scale-xe7kee --infrastructure docker --kubernetes-version v1.33.5+k3s1 --control-plane-machine-count 1 --worker-machine-count 3 --flavor (default)
STEP: Applying the cluster template yaml to the cluster @ 05/01/26 13:26:50.915
STEP: Creating the workload cluster with name "capik3s-node-scale-xe7kee" from the provided yaml @ 05/01/26 13:26:50.915
STEP: Applying the cluster template yaml of cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee @ 05/01/26 13:26:50.915
I0501 13:26:50.975881 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 Cluster is deprecated; use cluster.x-k8s.io/v1beta2 Cluster"
I0501 13:26:51.006788 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 Cluster is deprecated; use cluster.x-k8s.io/v1beta2 Cluster"
I0501 13:26:51.015435 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 MachineDeployment is deprecated; use cluster.x-k8s.io/v1beta2 MachineDeployment"
I0501 13:26:51.051029 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 MachineDeployment is deprecated; use cluster.x-k8s.io/v1beta2 MachineDeployment"
I0501 13:26:51.106654 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerCluster is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerCluster"
I0501 13:26:51.145631 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerCluster is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerCluster"
I0501 13:26:51.154722 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 13:26:51.188234 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 13:26:51.200018 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 13:26:51.222410 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
STEP: Waiting for the cluster infrastructure of cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee to be provisioned @ 05/01/26 13:26:51.222
STEP: Waiting for cluster to enter the provisioned phase @ 05/01/26 13:26:51.235
STEP: Waiting for control plane of cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee to be initialized @ 05/01/26 13:26:51.238
STEP: Waiting for the first control plane machine managed by workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee-control-plane to be provisioned @ 05/01/26 13:26:51.244
STEP: Waiting for one control plane node to exist @ 05/01/26 13:26:51.244
STEP: Waiting for control plane of cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee to be ready @ 05/01/26 13:26:51.247
STEP: Waiting for control plane workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee-control-plane to be ready (implies underlying nodes to be ready as well) @ 05/01/26 13:26:51.247
STEP: Waiting for the control plane to be ready @ 05/01/26 13:26:51.247
STEP: Checking all the control plane machines are in the expected failure domains @ 05/01/26 13:29:31.361
STEP: Waiting for the machine deployments of cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee to be provisioned @ 05/01/26 13:29:31.363
STEP: Waiting for the workload nodes to exist @ 05/01/26 13:29:31.372
STEP: Checking all the machines controlled by capik3s-node-scale-xe7kee-md-0 are in the "" failure domain @ 05/01/26 13:29:31.378
STEP: Waiting for the machine pools of cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee to be provisioned @ 05/01/26 13:29:31.383
STEP: Scaling down worker nodes to 1 @ 05/01/26 13:29:31.391
STEP: Creating the workload cluster with name "capik3s-node-scale-xe7kee" using the "" template (Kubernetes v1.33.5+k3s1, 1 control-plane machines, 1 worker machines) @ 05/01/26 13:29:31.391
STEP: Getting the cluster template yaml @ 05/01/26 13:29:31.391
INFO: clusterctl config cluster capik3s-node-scale-xe7kee --infrastructure docker --kubernetes-version v1.33.5+k3s1 --control-plane-machine-count 1 --worker-machine-count 1 --flavor (default)
STEP: Applying the cluster template yaml to the cluster @ 05/01/26 13:29:31.443
STEP: Creating the workload cluster with name "capik3s-node-scale-xe7kee" from the provided yaml @ 05/01/26 13:29:31.443
STEP: Applying the cluster template yaml of cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee @ 05/01/26 13:29:31.443
I0501 13:29:31.512433 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 Cluster is deprecated; use cluster.x-k8s.io/v1beta2 Cluster"
I0501 13:29:31.545020 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 Cluster is deprecated; use cluster.x-k8s.io/v1beta2 Cluster"
I0501 13:29:31.554065 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 MachineDeployment is deprecated; use cluster.x-k8s.io/v1beta2 MachineDeployment"
I0501 13:29:31.582191 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 MachineDeployment is deprecated; use cluster.x-k8s.io/v1beta2 MachineDeployment"
I0501 13:29:31.623468 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerCluster is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerCluster"
I0501 13:29:31.655008 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerCluster is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerCluster"
I0501 13:29:31.673840 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 13:29:31.700849 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 13:29:31.712187 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 13:29:31.744010 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
STEP: Waiting for the cluster infrastructure of cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee to be provisioned @ 05/01/26 13:29:31.744
STEP: Waiting for cluster to enter the provisioned phase @ 05/01/26 13:29:31.761
STEP: Waiting for control plane of cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee to be initialized @ 05/01/26 13:29:31.77
STEP: Waiting for the first control plane machine managed by workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee-control-plane to be provisioned @ 05/01/26 13:29:31.802
STEP: Waiting for one control plane node to exist @ 05/01/26 13:29:31.802
STEP: Waiting for control plane of cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee to be ready @ 05/01/26 13:29:31.838
STEP: Waiting for control plane workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee-control-plane to be ready (implies underlying nodes to be ready as well) @ 05/01/26 13:29:31.838
STEP: Waiting for the control plane to be ready @ 05/01/26 13:29:31.838
STEP: Checking all the control plane machines are in the expected failure domains @ 05/01/26 13:29:31.863
STEP: Waiting for the machine deployments of cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee to be provisioned @ 05/01/26 13:29:31.871
STEP: Waiting for the workload nodes to exist @ 05/01/26 13:29:31.893
STEP: Checking all the machines controlled by capik3s-node-scale-xe7kee-md-0 are in the "" failure domain @ 05/01/26 13:30:01.996
STEP: Waiting for the machine pools of cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee to be provisioned @ 05/01/26 13:30:02.003
STEP: Dumping logs from the "capik3s-node-scale-xe7kee" workload cluster @ 05/01/26 13:30:02.015
STEP: Dumping all the Cluster API resources in the "workload-cluster-scaling-lzb016" namespace @ 05/01/26 13:30:02.658
INFO: clusterctl describe cluster capik3s-node-scale-xe7kee --show-conditions=all --show-machinesets=true --grouping=false --echo=true --v1beta2
STEP: Deleting all clusters in the workload-cluster-scaling-lzb016 namespace @ 05/01/26 13:30:02.894
STEP: Deleting cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee @ 05/01/26 13:30:02.902
INFO: Waiting for the Cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee to be deleted
STEP: Waiting for cluster workload-cluster-scaling-lzb016/capik3s-node-scale-xe7kee to be deleted @ 05/01/26 13:30:02.917
STEP: Deleting namespace used for hosting the "workload-cluster-scaling" test spec @ 05/01/26 13:30:32.968
INFO: Deleting namespace workload-cluster-scaling-lzb016
• [774.536 seconds]
------------------------------
When testing KCP remediation Should replace unhealthy machines
/Users/richard/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.11.5/e2e/kcp_remediations.go:113
STEP: Creating a namespace for hosting the "kcp-remediation" test spec @ 05/01/26 13:30:32.977
INFO: Creating namespace kcp-remediation-gyf02k
INFO: Creating event watcher for namespace "kcp-remediation-gyf02k"
STEP: Creating a workload cluster @ 05/01/26 13:30:32.999
INFO: Getting the cluster template yaml
INFO: clusterctl config cluster kcp-remediation-jv5gvz --infrastructure docker --kubernetes-version v1.33.5+k3s1 --control-plane-machine-count 3 --worker-machine-count 0 --flavor kcp-remediation
I0501 13:30:33.106557 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 Cluster is deprecated; use cluster.x-k8s.io/v1beta2 Cluster"
I0501 13:30:33.117466 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 Cluster is deprecated; use cluster.x-k8s.io/v1beta2 Cluster"
I0501 13:30:33.122357 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 MachineDeployment is deprecated; use cluster.x-k8s.io/v1beta2 MachineDeployment"
I0501 13:30:33.134458 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 MachineDeployment is deprecated; use cluster.x-k8s.io/v1beta2 MachineDeployment"
I0501 13:30:33.143065 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 MachineHealthCheck is deprecated; use cluster.x-k8s.io/v1beta2 MachineHealthCheck"
I0501 13:30:33.163727 63855 warning_handler.go:64] "cluster.x-k8s.io/v1beta1 MachineHealthCheck is deprecated; use cluster.x-k8s.io/v1beta2 MachineHealthCheck"
I0501 13:30:33.187314 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerCluster is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerCluster"
I0501 13:30:33.199060 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerCluster is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerCluster"
I0501 13:30:33.208615 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 13:30:33.226617 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 13:30:33.233605 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
I0501 13:30:33.243646 63855 warning_handler.go:64] "infrastructure.cluster.x-k8s.io/v1beta1 DockerMachineTemplate is deprecated; use infrastructure.cluster.x-k8s.io/v1beta2 DockerMachineTemplate"
INFO: Waiting for the cluster infrastructure to be provisioned
STEP: Waiting for cluster to enter the provisioned phase @ 05/01/26 13:30:33.249
STEP: FIRST CONTROL PLANE MACHINE @ 05/01/26 13:30:43.262
STEP: Wait for the cluster to get stuck with the first CP machine not completing the bootstrap @ 05/01/26 13:30:43.263
INFO: Waiting for 1 machines, must have [], must not have []
INFO: - expected 1, got 1: [kcp-remediation-jv5gvz-control-plane-lsczp], of which new [kcp-remediation-jv5gvz-control-plane-lsczp], must have check: true, must not have check: true
INFO: Got 1 machines: [kcp-remediation-jv5gvz-control-plane-lsczp]
INFO: Checking the list of machines is stable
INFO: Machine kcp-remediation-jv5gvz-control-plane-lsczp is up but still bootstrapping
STEP: REMEDIATING FIRST CONTROL PLANE MACHINE @ 05/01/26 13:31:13.311
STEP: Add mhc-test:fail label to machine kcp-remediation-jv5gvz-control-plane-lsczp so it will be immediately remediated @ 05/01/26 13:31:13.311
INFO: Wait for the first CP machine to be remediated, and the replacement machine to come up, but again get stuck with the Machine not completing the bootstrap
INFO: Waiting for 1 machines, must have [], must not have [kcp-remediation-jv5gvz-control-plane-lsczp]
INFO: - expected 1, got 1: [kcp-remediation-jv5gvz-control-plane-lsczp], of which new [], must have check: true, must not have check: false
INFO: - expected 1, got 1: [kcp-remediation-jv5gvz-control-plane-lsczp], of which new [], must have check: true, must not have check: false
INFO: - expected 1, got 1: [kcp-remediation-jv5gvz-control-plane-bd4s6], of which new [kcp-remediation-jv5gvz-control-plane-bd4s6], must have check: true, must not have check: true
INFO: Got 1 machines: [kcp-remediation-jv5gvz-control-plane-bd4s6]
INFO: Checking the list of machines is stable
INFO: Machine kcp-remediation-jv5gvz-control-plane-bd4s6 is up but still bootstrapping
STEP: FIRST CONTROL PLANE MACHINE SUCCESSFULLY REMEDIATED! @ 05/01/26 13:32:03.382
STEP: Unblock bootstrap for Machine kcp-remediation-jv5gvz-control-plane-bd4s6 and wait for it to be provisioned @ 05/01/26 13:32:03.382
INFO: Sending bootstrap signal pass to Machine kcp-remediation-jv5gvz-control-plane-bd4s6
INFO: Waiting for Machine kcp-remediation-jv5gvz-control-plane-bd4s6 to acknowledge signal pass has been received
INFO: Waiting for Machine kcp-remediation-jv5gvz-control-plane-bd4s6 to be provisioned
STEP: FIRST CONTROL PLANE MACHINE UP AND RUNNING! @ 05/01/26 13:32:53.482
STEP: START PROVISIONING OF SECOND CONTROL PLANE MACHINE! @ 05/01/26 13:32:53.482
STEP: Wait for the cluster to get stuck with the second CP machine not completing the bootstrap @ 05/01/26 13:32:53.482
INFO: Waiting for 2 machines, must have [kcp-remediation-jv5gvz-control-plane-bd4s6], must not have []
INFO: - expected 2, got 1: [kcp-remediation-jv5gvz-control-plane-bd4s6], of which new [], must have check: true, must not have check: true
INFO: - expected 2, got 1: [kcp-remediation-jv5gvz-control-plane-bd4s6], of which new [], must have check: true, must not have check: true
INFO: - expected 2, got 1: [kcp-remediation-jv5gvz-control-plane-bd4s6], of which new [], must have check: true, must not have check: true
INFO: - expected 2, got 2: [kcp-remediation-jv5gvz-control-plane-kz7cv kcp-remediation-jv5gvz-control-plane-bd4s6], of which new [kcp-remediation-jv5gvz-control-plane-kz7cv], must have check: true, must not have check: true
INFO: Got 2 machines: [kcp-remediation-jv5gvz-control-plane-bd4s6 kcp-remediation-jv5gvz-control-plane-kz7cv]
INFO: Checking the list of machines is stable
INFO: Machine kcp-remediation-jv5gvz-control-plane-kz7cv is up but still bootstrapping
STEP: REMEDIATING SECOND CONTROL PLANE MACHINE @ 05/01/26 13:33:53.529
STEP: Add mhc-test:fail label to machine kcp-remediation-jv5gvz-control-plane-lsczp so it will be immediately remediated @ 05/01/26 13:33:53.529
INFO: Wait for the second CP machine to be remediated, and the replacement machine to come up, but again get stuck with the Machine not completing the bootstrap
INFO: Waiting for 2 machines, must have [kcp-remediation-jv5gvz-control-plane-bd4s6], must not have [kcp-remediation-jv5gvz-control-plane-kz7cv]
INFO: - expected 2, got 2: [kcp-remediation-jv5gvz-control-plane-bd4s6 kcp-remediation-jv5gvz-control-plane-kz7cv], of which new [], must have check: true, must not have check: false
INFO: - expected 2, got 2: [kcp-remediation-jv5gvz-control-plane-bd4s6 kcp-remediation-jv5gvz-control-plane-c2s5j], of which new [kcp-remediation-jv5gvz-control-plane-c2s5j], must have check: true, must not have check: true
INFO: Got 2 machines: [kcp-remediation-jv5gvz-control-plane-bd4s6 kcp-remediation-jv5gvz-control-plane-c2s5j]
INFO: Checking the list of machines is stable
INFO: Machine kcp-remediation-jv5gvz-control-plane-c2s5j is up but still bootstrapping
STEP: SECOND CONTROL PLANE MACHINE SUCCESSFULLY REMEDIATED! @ 05/01/26 13:34:33.605
STEP: Unblock bootstrap for Machine kcp-remediation-jv5gvz-control-plane-c2s5j and wait for it to be provisioned @ 05/01/26 13:34:33.606
INFO: Sending bootstrap signal pass to Machine kcp-remediation-jv5gvz-control-plane-c2s5j
INFO: Waiting for Machine kcp-remediation-jv5gvz-control-plane-c2s5j to acknowledge signal pass has been received
INFO: Waiting for Machine kcp-remediation-jv5gvz-control-plane-c2s5j to be provisioned
STEP: SECOND CONTROL PLANE MACHINE UP AND RUNNING! @ 05/01/26 13:35:03.703
STEP: START PROVISIONING OF THIRD CONTROL PLANE MACHINE! @ 05/01/26 13:35:03.704
STEP: Wait for the cluster to get stuck with the third CP machine not completing the bootstrap @ 05/01/26 13:35:03.704
INFO: Waiting for 3 machines, must have [kcp-remediation-jv5gvz-control-plane-c2s5j kcp-remediation-jv5gvz-control-plane-bd4s6], must not have []
INFO: - expected 3, got 2: [kcp-remediation-jv5gvz-control-plane-c2s5j kcp-remediation-jv5gvz-control-plane-bd4s6], of which new [], must have check: true, must not have check: true
INFO: - expected 3, got 3: [kcp-remediation-jv5gvz-control-plane-bd4s6 kcp-remediation-jv5gvz-control-plane-c2s5j kcp-remediation-jv5gvz-control-plane-t22sd], of which new [kcp-remediation-jv5gvz-control-plane-t22sd], must have check: true, must not have check: true
INFO: Got 3 machines: [kcp-remediation-jv5gvz-control-plane-bd4s6 kcp-remediation-jv5gvz-control-plane-c2s5j kcp-remediation-jv5gvz-control-plane-t22sd]
INFO: Checking the list of machines is stable
INFO: Machine kcp-remediation-jv5gvz-control-plane-t22sd is up but still bootstrapping
STEP: Unblock bootstrap for Machine kcp-remediation-jv5gvz-control-plane-t22sd and wait for it to be provisioned @ 05/01/26 13:35:43.748
INFO: Sending bootstrap signal pass to Machine kcp-remediation-jv5gvz-control-plane-t22sd
INFO: Waiting for Machine kcp-remediation-jv5gvz-control-plane-t22sd to acknowledge signal pass has been received
INFO: Waiting for Machine kcp-remediation-jv5gvz-control-plane-t22sd to be provisioned
STEP: ALL THE CONTROL PLANE MACHINES SUCCESSFULLY PROVISIONED! @ 05/01/26 13:36:23.841
STEP: REMEDIATING THIRD CP @ 05/01/26 13:36:23.842
STEP: Add mhc-test:fail label to machine kcp-remediation-jv5gvz-control-plane-t22sd and set an unhealthy condition on the node so it will be immediately remediated @ 05/01/26 13:36:23.842
INFO: Patching the node condition to the node
INFO: Wait for the third CP machine to be remediated, and the replacement machine to come up, but again get stuck with the Machine not completing the bootstrap
INFO: Waiting for 3 machines, must have [kcp-remediation-jv5gvz-control-plane-c2s5j kcp-remediation-jv5gvz-control-plane-bd4s6], must not have [kcp-remediation-jv5gvz-control-plane-t22sd]
INFO: - expected 3, got 3: [kcp-remediation-jv5gvz-control-plane-bd4s6 kcp-remediation-jv5gvz-control-plane-c2s5j kcp-remediation-jv5gvz-control-plane-t22sd], of which new [], must have check: true, must not have check: false
INFO: - expected 3, got 3: [kcp-remediation-jv5gvz-control-plane-c2s5j kcp-remediation-jv5gvz-control-plane-t22sd kcp-remediation-jv5gvz-control-plane-bd4s6], of which new [], must have check: true, must not have check: false
INFO: - expected 3, got 3: [kcp-remediation-jv5gvz-control-plane-bd4s6 kcp-remediation-jv5gvz-control-plane-c2s5j kcp-remediation-jv5gvz-control-plane-t22sd], of which new [], must have check: true, must not have check: false
INFO: - expected 3, got 3: [kcp-remediation-jv5gvz-control-plane-bd4s6 kcp-remediation-jv5gvz-control-plane-c2s5j kcp-remediation-jv5gvz-control-plane-t22sd], of which new [], must have check: true, must not have check: false
INFO: - expected 3, got 2: [kcp-remediation-jv5gvz-control-plane-bd4s6 kcp-remediation-jv5gvz-control-plane-c2s5j], of which new [], must have check: true, must not have check: true
INFO: - expected 3, got 3: [kcp-remediation-jv5gvz-control-plane-4frqx kcp-remediation-jv5gvz-control-plane-bd4s6 kcp-remediation-jv5gvz-control-plane-c2s5j], of which new [kcp-remediation-jv5gvz-control-plane-4frqx], must have check: true, must not have check: true
INFO: Got 3 machines: [kcp-remediation-jv5gvz-control-plane-4frqx kcp-remediation-jv5gvz-control-plane-bd4s6 kcp-remediation-jv5gvz-control-plane-c2s5j]
INFO: Checking the list of machines is stable
INFO: Machine kcp-remediation-jv5gvz-control-plane-4frqx is up but still bootstrapping
STEP: THIRD CP SUCCESSFULLY REMEDIATED! @ 05/01/26 13:37:44.074
STEP: Unblock bootstrap for Machine kcp-remediation-jv5gvz-control-plane-4frqx and wait for it to be provisioned @ 05/01/26 13:37:44.074
INFO: Sending bootstrap signal pass to Machine kcp-remediation-jv5gvz-control-plane-4frqx
INFO: Waiting for Machine kcp-remediation-jv5gvz-control-plane-4frqx to acknowledge signal pass has been received
INFO: Waiting for Machine kcp-remediation-jv5gvz-control-plane-4frqx to be provisioned
STEP: CP BACK TO FULL OPERATIONAL STATE! @ 05/01/26 13:38:24.192
STEP: Verify Cluster Available condition is true @ 05/01/26 13:38:24.192
STEP: Verify Machines Ready condition is true @ 05/01/26 13:38:24.201
STEP: PASSED! @ 05/01/26 13:38:24.207
STEP: Dumping logs from the "kcp-remediation-jv5gvz" workload cluster @ 05/01/26 13:38:24.208
STEP: Dumping all the Cluster API resources in the "kcp-remediation-gyf02k" namespace @ 05/01/26 13:38:24.922
INFO: clusterctl describe cluster kcp-remediation-jv5gvz --show-conditions=all --show-machinesets=true --grouping=false --echo=true --v1beta2
STEP: Dumping Pods and Nodes of Cluster kcp-remediation-gyf02k/kcp-remediation-jv5gvz @ 05/01/26 13:38:25.185
STEP: Deleting cluster kcp-remediation-gyf02k/kcp-remediation-jv5gvz @ 05/01/26 13:38:25.245
STEP: Deleting cluster kcp-remediation-gyf02k/kcp-remediation-jv5gvz @ 05/01/26 13:38:25.251
INFO: Waiting for the Cluster kcp-remediation-gyf02k/kcp-remediation-jv5gvz to be deleted
STEP: Waiting for cluster kcp-remediation-gyf02k/kcp-remediation-jv5gvz to be deleted @ 05/01/26 13:38:25.269
STEP: Deleting namespace used for hosting the "kcp-remediation" test spec @ 05/01/26 13:39:05.347
INFO: Deleting namespace kcp-remediation-gyf02k
• [512.380 seconds]
------------------------------
[SynchronizedAfterSuite]
/Users/richard/code/oss/cluster-api-k3s/test/e2e/e2e_suite_test.go:180
STEP: Dumping logs from the bootstrap cluster @ 05/01/26 13:39:05.361
STEP: Tearing down the management cluster @ 05/01/26 13:39:05.637
INFO: Got error while streaming logs for pod capi-k3s-control-plane-system/capi-k3s-control-plane-controller-manager-6f8c7c66b9-xlvn2, container manager: context canceled
INFO: Stopped streaming logs for pod capi-k3s-control-plane-system/capi-k3s-control-plane-controller-manager-6f8c7c66b9-xlvn2, container manager: context canceled
INFO: Got error while streaming logs for pod capi-system/capi-controller-manager-5c7d4d7fd-r6vcl, container manager: context canceled
INFO: Stopped streaming logs for pod capi-system/capi-controller-manager-5c7d4d7fd-r6vcl, container manager: context canceled
INFO: Got error while streaming logs for pod capd-system/capd-controller-manager-794b95c4b4-4bhhm, container manager: context canceled
INFO: Stopped streaming logs for pod capd-system/capd-controller-manager-794b95c4b4-4bhhm, container manager: context canceled
INFO: Got error while streaming logs for pod capi-k3s-bootstrap-system/capi-k3s-bootstrap-controller-manager-67dd45f846-qfggs, container manager: context canceled
INFO: Stopped streaming logs for pod capi-k3s-bootstrap-system/capi-k3s-bootstrap-controller-manager-67dd45f846-qfggs, container manager: context canceled
[SynchronizedAfterSuite] PASSED [1.448 seconds]
------------------------------
[ReportAfterSuite] Autogenerated ReportAfterSuite for --junit-report
autogenerated by Ginkgo
[ReportAfterSuite] PASSED [0.010 seconds]
------------------------------
Ran 11 of 11 Specs in 6665.059 seconds
SUCCESS! -- 11 Passed | 0 Failed | 0 Pending | 0 Skipped
PASS
Ginkgo ran 1 suite in 1h51m16.758652292s
Test Suite Passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment