This job view page is being replaced by Spyglass soon. Check out the new job view.
PRedreed: feat: Azure Disk CSI Driver V2 (a.k.a. Project Mandalay) initial implementation
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-06-07 22:50
Elapsed7m11s
Revision8d550830896b22d87296d7a47bb5c8e27c2c414b
Refs 864

No Test Failures!


Error lines from build-log.txt

... skipping 272 lines ...
* minikube v1.20.0 on Debian 10.9 (amd64)
* Using the none driver based on user configuration
* Starting control plane node minikube in cluster minikube
* Running on localhost (CPUs=8, Memory=64324MB, Disk=247932MB) ...
* OS release is Debian GNU/Linux 10 (buster)
* Preparing Kubernetes v1.20.2 on Docker 20.10.5 ...
    > kubectl.sha256: 64 B / 64 B [--------------------------] 100.00% ? p/s 0s    > kubelet.sha256: 64 B / 64 B [--------------------------] 100.00% ? p/s 0s    > kubeadm.sha256: 64 B / 64 B [--------------------------] 100.00% ? p/s 0s    > kubectl: 31.47 MiB / 38.37 MiB [-------------------->____] 82.02% ? p/s ?    > kubelet: 4.71 MiB / 108.73 MiB [->________________________] 4.33% ? p/s ?    > kubectl: 38.37 MiB / 38.37 MiB [-------------] 100.00% 1.71 GiB p/s 200ms    > kubeadm: 6.12 MiB / 37.40 MiB [---->_____________________] 16.38% ? p/s ?    > kubelet: 26.21 MiB / 108.73 MiB [----->__________________] 24.11% ? p/s ?    > kubeadm: 10.54 MiB / 37.40 MiB [------->_________________] 28.18% ? p/s ?    > kubelet: 72.00 MiB / 108.73 MiB [--------------->________] 66.22% ? p/s ?    > kubeadm: 37.40 MiB / 37.40 MiB [------------] 100.00% 93.75 MiB p/s 600ms    > kubelet: 108.73 MiB / 108.73 MiB [---------] 100.00% 184.99 MiB p/s 800ms! initialization failed, will try again: wait: /bin/bash -c "sudo env PATH=/var/lib/minikube/binaries/v1.20.2:$PATH kubeadm init --config /var/tmp/minikube/kubeadm.yaml  --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--var-lib-minikube,DirAvailable--var-lib-minikube-etcd,FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml,FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml,FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml,FileAvailable--etc-kubernetes-manifests-etcd.yaml,Port-10250,Swap,Mem": exit status 1
stdout:
[init] Using Kubernetes version: v1.20.2
[preflight] Running pre-flight checks
[preflight] The system verification failed. Printing the output from the verification:
KERNEL_VERSION: 5.4.0-1036-gke
DOCKER_VERSION: 20.10.5
OS: Linux
CGROUPS_CPU: enabled
CGROUPS_CPUACCT: enabled
CGROUPS_CPUSET: enabled
... skipping 9 lines ...
	[WARNING Service-Docker]: no supported init system detected, skipping checking for services
	[WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/
	[WARNING FileExisting-ethtool]: ethtool not found in system path
	[WARNING FileExisting-socat]: socat not found in system path
	[WARNING SystemVerification]: this Docker version is not on the list of validated versions: 20.10.5. Latest validated version: 19.03
	[WARNING Service-Kubelet]: no supported init system detected, skipping checking for services
error execution phase preflight: [preflight] Some fatal errors occurred:
	[ERROR SystemVerification]: failed to parse kernel config: unable to load kernel module: "configs", output: "modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/5.4.0-1036-gke/modules.dep.bin'\nmodprobe: FATAL: Module configs not found in directory /lib/modules/5.4.0-1036-gke\n", err: exit status 1
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
To see the stack trace of this error execute with --v=5 or higher

* 
X Error starting cluster: wait: /bin/bash -c "sudo env PATH=/var/lib/minikube/binaries/v1.20.2:$PATH kubeadm init --config /var/tmp/minikube/kubeadm.yaml  --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--var-lib-minikube,DirAvailable--var-lib-minikube-etcd,FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml,FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml,FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml,FileAvailable--etc-kubernetes-manifests-etcd.yaml,Port-10250,Swap,Mem": exit status 1
stdout:
[init] Using Kubernetes version: v1.20.2
[preflight] Running pre-flight checks
[preflight] The system verification failed. Printing the output from the verification:
KERNEL_VERSION: 5.4.0-1036-gke
DOCKER_VERSION: 20.10.5
OS: Linux
CGROUPS_CPU: enabled
CGROUPS_CPUACCT: enabled
CGROUPS_CPUSET: enabled
... skipping 9 lines ...
	[WARNING Service-Docker]: no supported init system detected, skipping checking for services
	[WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/
	[WARNING FileExisting-ethtool]: ethtool not found in system path
	[WARNING FileExisting-socat]: socat not found in system path
	[WARNING SystemVerification]: this Docker version is not on the list of validated versions: 20.10.5. Latest validated version: 19.03
	[WARNING Service-Kubelet]: no supported init system detected, skipping checking for services
error execution phase preflight: [preflight] Some fatal errors occurred:
	[ERROR SystemVerification]: failed to parse kernel config: unable to load kernel module: "configs", output: "modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/5.4.0-1036-gke/modules.dep.bin'\nmodprobe: FATAL: Module configs not found in directory /lib/modules/5.4.0-1036-gke\n", err: exit status 1
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
To see the stack trace of this error execute with --v=5 or higher

* 
╭──────────────────────────────────────────────────────────────────╮
│                                                                  │
│    * If the above advice does not help, please let us know:      │
│      https://github.com/kubernetes/minikube/issues/new/choose    │
... skipping 5 lines ...


X Exiting due to GUEST_START: wait: /bin/bash -c "sudo env PATH=/var/lib/minikube/binaries/v1.20.2:$PATH kubeadm init --config /var/tmp/minikube/kubeadm.yaml  --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--var-lib-minikube,DirAvailable--var-lib-minikube-etcd,FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml,FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml,FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml,FileAvailable--etc-kubernetes-manifests-etcd.yaml,Port-10250,Swap,Mem": exit status 1
stdout:
[init] Using Kubernetes version: v1.20.2
[preflight] Running pre-flight checks
[preflight] The system verification failed. Printing the output from the verification:
KERNEL_VERSION: 5.4.0-1036-gke
DOCKER_VERSION: 20.10.5
OS: Linux
CGROUPS_CPU: enabled
CGROUPS_CPUACCT: enabled
CGROUPS_CPUSET: enabled
... skipping 9 lines ...
	[WARNING Service-Docker]: no supported init system detected, skipping checking for services
	[WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/
	[WARNING FileExisting-ethtool]: ethtool not found in system path
	[WARNING FileExisting-socat]: socat not found in system path
	[WARNING SystemVerification]: this Docker version is not on the list of validated versions: 20.10.5. Latest validated version: 19.03
	[WARNING Service-Kubelet]: no supported init system detected, skipping checking for services
error execution phase preflight: [preflight] Some fatal errors occurred:
	[ERROR SystemVerification]: failed to parse kernel config: unable to load kernel module: "configs", output: "modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/5.4.0-1036-gke/modules.dep.bin'\nmodprobe: FATAL: Module configs not found in directory /lib/modules/5.4.0-1036-gke\n", err: exit status 1
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
To see the stack trace of this error execute with --v=5 or higher

* 
╭──────────────────────────────────────────────────────────────────╮
│                                                                  │
│    * If the above advice does not help, please let us know:      │
│      https://github.com/kubernetes/minikube/issues/new/choose    │
... skipping 2 lines ...
│    * - /root/.minikube/logs/lastStart.txt                        │
│                                                                  │
╰──────────────────────────────────────────────────────────────────╯


Unistalling helm chart
Error: Kubernetes cluster unreachable: Get "http://localhost:8080/version?timeout=32s": dial tcp [::1]:8080: connect: connection refused
Cleaning up the minikube cache

X Exiting due to HOST_DEL_CACHE: remove /root/.minikube/cache/images/k8sprow.azurecr.io/azuredisk-csi_v2.0.0-alpha.1-9dd0a8c7cc4354ada96c5fb6534e5828bf96a79a: no such file or directory
* 
╭──────────────────────────────────────────────────────────────────────────────╮
│                                                                              │
... skipping 7 lines ...


Stopping minikube
* Stopping node "minikube"  ...
* 1 nodes stopped.
Deleting CSI sanity test binary
    sanity_test.go:104: Sanity test failed exit status 80
2021/06/07 22:52:24 Deleting resource group azuredisk-csi-driver-test-ec05d200-c7e2-11eb-9967-263c55ff9fc1
--- FAIL: TestSanity (316.77s)
FAIL
FAIL	sigs.k8s.io/azuredisk-csi-driver/test/sanity	316.778s
FAIL
make: *** [Makefile:105: sanity-test-v2] Error 1
+ EXIT_VALUE=2
+ set +o xtrace
Cleaning up after docker in docker.
================================================================================
Cleaning up after docker
Stopping Docker: dockerProgram process in pidfile '/var/run/docker-ssd.pid', 1 process(es), refused to die.
... skipping 3 lines ...