kubernetes-sigs/cluster-api PR #8336 pull-cluster-api-e2e-informing-release-1-2 #1638559574120206336
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | k8s-infra-cherrypick-robot: [release-1.2] 🐛 Drop uid from error messages |
| Result | ABORTED |
| Tests | 1 failed / 1 succeeded |
| Started | |
| Elapsed | 17m12s |
| Revision | ee50118b37ad5d945b52c175f65d06588a59b848 |
| Refs |
8336 |
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.001s.
Error: Unexpected non-nil/non-zero argument at index 1:
<*url.Error>: &url.Error{Op:"Get", URL:"https://127.0.0.1:39187/apis/cluster.x-k8s.io/v1beta1/namespaces/k8s-upgrade-with-runtimesdk-b8daq3/machinepools/k8s-upgrade-with-runtimesdk-wkks34-mp-0", Err:(*net.OpError)(0xc001c00be0)}
/home/prow/go/src/sigs.k8s.io/cluster-api/test/framework/machinepool_helpers.go:90
STEP: Creating a namespace for hosting the "k8s-upgrade-with-runtimesdk" test spec
INFO: Creating namespace k8s-upgrade-with-runtimesdk-b8daq3
INFO: Creating event watcher for namespace "k8s-upgrade-with-runtimesdk-b8daq3"
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-b8daq3/test-extension to be available
STEP: Watch Deployment logs of test extension
INFO: Creating log watcher for controller k8s-upgrade-with-runtimesdk-b8daq3/test-extension, pod test-extension-ff8f49699-5rxrb, container extension
STEP: Creating a workload cluster
INFO: Creating the workload cluster with name "k8s-upgrade-with-runtimesdk-wkks34" using the "upgrades-runtimesdk" template (Kubernetes v1.25.3, 1 control-plane machines, 2 worker machines)
INFO: Getting the cluster template yaml
INFO: clusterctl config cluster k8s-upgrade-with-runtimesdk-wkks34 --infrastructure (default) --kubernetes-version v1.25.3 --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-wkks34-crs-0 created
clusterresourceset.addons.cluster.x-k8s.io/k8s-upgrade-with-runtimesdk-wkks34-crs-0 created
kubeadmconfig.bootstrap.cluster.x-k8s.io/k8s-upgrade-with-runtimesdk-wkks34-mp-0-config created
cluster.cluster.x-k8s.io/k8s-upgrade-with-runtimesdk-wkks34 created
machinepool.cluster.x-k8s.io/k8s-upgrade-with-runtimesdk-wkks34-mp-0 created
dockermachinepool.infrastructure.cluster.x-k8s.io/k8s-upgrade-with-runtimesdk-wkks34-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-b8daq3/k8s-upgrade-with-runtimesdk-wkks34-9vtbx 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-b8daq3/k8s-upgrade-with-runtimesdk-wkks34-9vtbx 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-wkks34-md-0-kbnnj are in the "fd4" failure domain
INFO: Waiting for the machine pools to be provisioned
STEP: Waiting for the machine pool workload nodes
from junit.e2e_suite.1.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 982 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-fwiqbz-md-0-bkskz are in the "fd4" failure domain INFO: Waiting for the machine pools to be provisioned STEP: PASSED! STEP: Dumping logs from the "quick-start-fwiqbz" workload cluster Failed to get logs for machine quick-start-fwiqbz-md-0-bkskz-9fbf9f5b7-mln5v, cluster quick-start-wnf5nl/quick-start-fwiqbz: exit status 2 Failed to get logs for machine quick-start-fwiqbz-wvn7n-kjm2s, cluster quick-start-wnf5nl/quick-start-fwiqbz: exit status 2 STEP: Dumping all the Cluster API resources in the "quick-start-wnf5nl" namespace STEP: Deleting cluster quick-start-wnf5nl/quick-start-fwiqbz STEP: Deleting cluster quick-start-fwiqbz INFO: Waiting for the Cluster quick-start-wnf5nl/quick-start-fwiqbz to be deleted STEP: Waiting for cluster quick-start-fwiqbz to be deleted STEP: Deleting namespace used for hosting the "quick-start" test spec ... skipping 10 lines ...