Remove kubetest dependencies for kind job

[aojea]

kind testing no longer depends on kubetest since

kubernetes-sigs/kind@cae88ef#diff-d9fa0450190d60ba133fb92282a94725

It also stops copying the logs manually and leverage the ARTIFACTS variable in the e2e.sh scripts

[aojea]

@ZhengZhenyu don't know if this will fix the problems but at least will be more aligned to the e2e.sh scripts to avoid that future changes on it breaks this CI

[theopenlab-ci]

Build succeeded.

• openlab-zuul-jobs-check : SUCCESS in 4m 57s

[ZhengZhenyu]

@aojea let me apply this on my test env to see if it works

[aojea]

@ZhengZhenyu please feel free to take it and redo it, I've just created it because it was easier to explain this way the change :)

[ZhengZhenyu]

| ✓ Creating kubeadm config 📜
2019-08-26 12:39:16.602573 | ubuntu-xenial-arm64 | • Starting control-plane 🕹️ ...
2019-08-26 12:39:16.603746 | ubuntu-xenial-arm64 | time="12:39:16" level=debug msg="Running: /usr/bin/docker [docker exec --privileged kind-control-plane kubeadm init --ignore-preflight-errors=all --config=/kind/kubeadm.conf --skip-token-print --v=6]"
2019-08-26 12:43:42.877367 | ubuntu-xenial-arm64 | time="12:43:42" level=debug msg="I0826 12:39:17.496707 95 initconfiguration.go:186] loading configuration from "/kind/kubeadm.conf"\n[config] WARNING: Ignored YAML document with GroupVersionKind kubeadm.k8s.io/v1beta1, Kind=JoinConfiguration\nI0826 12:39:17.519734 95 feature_gate.go:226] feature gates: &{map[]}\n[init] Using Kubernetes version: v1.14.3\n[preflight] Running pre-flight checks\nI0826 12:39:17.522464 95 checks.go:581] validating Kubernetes and kubeadm version\nI0826 12:39:17.522576 95 checks.go:172] validating if the firewall is enabled and active\nI0826 12:39:17.563957 95 checks.go:209] validating availability of port 6443\nI0826 12:39:17.564684 95 checks.go:209] validating availability of port 10251\nI0826 12:39:17.564870 95 checks.go:209] validating availability of port 10252\nI0826 12:39:17.565068 95 checks.go:292] validating the existence of file /etc/kubernetes/manifests/kube-apiserver.yaml\nI0826 12:39:17.565213 95 checks.go:292] validating the existence of file /etc/kubernetes/manifests/kube-controller-manager.yaml\nI0826 12:39:17.565275 95 checks.go:292] validating the existence of file /etc/kubernetes/manifests/kube-scheduler.yaml\nI0826 12:39:17.565338 95 checks.go:292] validating the existence of file /etc/kubernetes/manifests/etcd.yaml\nI0826 12:39:17.565428 95 checks.go:439] validating if the connectivity type is via proxy or direct\nI0826 12:39:17.567600 95 checks.go:475] validating http connectivity to first IP address in the CIDR\nI0826 12:39:17.567701 95 checks.go:475] validating http connectivity to first IP address in the CIDR\nI0826 12:39:17.567769 95 checks.go:105] validating the container runtime\nI0826 12:39:17.888261 95 checks.go:382] validating the presence of executable crictl\nI0826 12:39:17.888459 95 checks.go:341] validating the contents of file /proc/sys/net/bridge/bridge-nf-call-iptables\n\t[WARNING FileContent--proc-sys-net-bridge-bridge-nf-call-iptables]: /proc/sys/net/bridge/bridge-nf-call-iptables does not exist\nI0826 12:39:17.888714 95 checks.go:341] validating the contents of file /proc/sys/net/ipv4/ip_forward\nI0826 12:39:17.888924 95 checks.go:653] validating whether swap is enabled or not\nI0826 12:39:17.889134 95 checks.go:382] validating the presence of executable ip\nI0826 12:39:17.889490 95 checks.go:382] validating the presence of executable iptables\nI0826 12:39:17.889724 95 checks.go:382] validating the presence of executable mount\nI0826 12:39:17.889840 95 checks.go:382] validating the presence of executable nsenter\nI0826 12:39:17.890149 95 checks.go:382] validating the presence of executable ebtables\nI0826 12:39:17.891899 95 checks.go:382] validating the presence of executable ethtool\nI0826 12:39:17.892121 95 checks.go:382] validating the presence of executable socat\nI0826 12:39:17.892408 95 checks.go:382] validating the presence of executable tc\nI0826 12:39:17.892639 95 checks.go:382] validating the presence of executable touch\nI0826 12:39:17.892890 95 checks.go:524] running all checks\n[preflight] The system verification failed. Printing the output from the verification:\n\x1b[0;37mKERNEL_VERSION\x1b[0m: \x1b[0;32m4.15.0-58-generic\x1b[0m\n\x1b[0;37mOS\x1b[0m: \x1b[0;32mLinux\x1b[0m\n\x1b[0;37mCGROUPS_CPU\x1b[0m: \x1b[0;32menabled\x1b[0m\n\x1b[0;37mCGROUPS_CPUACCT\x1b[0m: \x1b[0;32menabled\x1b[0m\n\x1b[0;37mCGROUPS_CPUSET\x1b[0m: \x1b[0;32menabled\x1b[0m\n\x1b[0;37mCGROUPS_DEVICES\x1b[0m: \x1b[0;32menabled\x1b[0m\n\x1b[0;37mCGROUPS_FREEZER\x1b[0m: \x1b[0;32menabled\x1b[0m\n\x1b[0;37mCGROUPS_MEMORY\x1b[0m: \x1b[0;32menabled\x1b[0m\n\t[WARNING SystemVerification]: failed to parse kernel config: unable to load kernel module: "configs", output: "modprobe: FATAL: Module configs not found in directory /lib/modules/4.15.0-58-generic\n", err: exit status 1\nI0826 12:39:17.933466 95 checks.go:412] checking whether the given node name is reachable using net.LookupHost\nI0826 12:39:17.934374 95 checks.go:622] validating kubelet version\nI0826 12:39:18.174089 95 checks.go:131] validating if the service is enabled and active\nI0826 12:39:18.225522 95 checks.go:209] validating availability of port 10250\nI0826 12:39:18.225850 95 checks.go:209] validating availability of port 2379\nI0826 12:39:18.226023 95 checks.go:209] validating availability of port 2380\nI0826 12:39:18.226233 95 checks.go:254] validating the existence and emptiness of directory /var/lib/etcd\n[preflight] Pulling images required for setting up a Kubernetes cluster\n[preflight] This might take a minute or two, depending on the speed of your internet connection\n[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'\nI0826 12:39:18.291528 95 checks.go:842] image exists: k8s.gcr.io/kube-apiserver:v1.14.3\nI0826 12:39:18.317487 95 checks.go:842] image exists: k8s.gcr.io/kube-controller-manager:v1.14.3\nI0826 12:39:18.344577 95 checks.go:842] image exists: k8s.gcr.io/kube-scheduler:v1.14.3\nI0826 12:39:18.377941 95 checks.go:842] image exists: k8s.gcr.io/kube-proxy:v1.14.3\nI0826 12:39:18.407759 95 checks.go:842] image exists: k8s.gcr.io/pause:3.1\nI0826 12:39:18.435654 95 checks.go:842] image exists: k8s.gcr.io/etcd:3.3.10\nI0826 12:39:18.468272 95 checks.go:842] image exists: k8s.gcr.io/coredns:1.3.1\nI0826 12:39:18.468406 95 kubelet.go:61] Stopping the kubelet\n[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"\n[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"\nI0826 12:39:18.524284 95 kubelet.go:79] Starting the kubelet\n[kubelet-start] Activating the kubelet service\n[certs] Using certificateDir folder "/etc/kubernetes/pki"\nI0826 12:39:18.789369 95 certs.go:110] creating a new certificate authority for ca\n[certs] Generating "ca" certificate and key\n[certs] Generating "apiserver" certificate and key\n[certs] apiserver serving cert is signed for DNS names [kind-control-plane kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local localhost] and IPs [10.96.0.1 172.17.0.3 172.17.0.3 127.0.0.1]\n[certs] Generating "apiserver-kubelet-client" certificate and key\nI0826 12:39:24.100186 95 certs.go:110] creating a new certificate authority for etcd-ca\n[certs] Generating "etcd/ca" certificate and key\n[certs] Generating "etcd/server" certificate and key\n[certs] etcd/server serving cert is signed for DNS names [kind-control-plane localhost] and IPs [172.17.0.3 127.0.0.1 ::1]\n[certs] Generating "etcd/peer" certificate and key\n[certs] etcd/peer serving cert is signed for DNS names [kind-control-plane localhost] and IPs [172.17.0.3 127.0.0.1 ::1]\n[certs] Generating "apiserver-etcd-client" certificate and key\n[certs] Generating "etcd/healthcheck-client" certificate and key\nI0826 12:39:30.852951 95 certs.go:110] creating a new certificate authority for front-proxy-ca\n[certs] Generating "front-proxy-ca" certificate and key\n[certs] Generating "front-proxy-client" certificate and key\nI0826 12:39:33.224071 95 certs.go:69] creating a new public/private key files for signing service account users\n[certs] Generating "sa" key and public key\n[kubeconfig] Using kubeconfig folder "/etc/kubernetes"\nI0826 12:39:33.892195 95 kubeconfig.go:94] creating kubeconfig file for admin.conf\n[kubeconfig] Writing "admin.conf" kubeconfig file\nI0826 12:39:37.105275 95 kubeconfig.go:94] creating kubeconfig file for kubelet.conf\n[kubeconfig] Writing "kubelet.conf" kubeconfig file\nI0826 12:39:40.083152 95 kubeconfig.go:94] creating kubeconfig file for controller-manager.conf\n[kubeconfig] Writing "controller-manager.conf" kubeconfig file\nI0826 12:39:42.032735 95 kubeconfig.go:94] creating kubeconfig file for scheduler.conf\n[kubeconfig] Writing "scheduler.conf" kubeconfig file\n[control-plane] Using manifest folder "/etc/kubernetes/manifests"\n[control-plane] Creating sError: failed to create cluster: failed to init node with kubeadm: exit status 1

[ZhengZhenyu]

got the above log in my test run

[ZhengZhenyu]

I guess this is the key

The system verification failed. Printing the output from the verification:\n\x1b[0;37mKERNEL_VERSION\x1b[0m: \x1b[0;32m4.15.0-58-generic\x1b[0m\n\x1b[0;37mOS\x1b[0m: \x1b[0;32mLinux\x1b[0m\n\x1b[0;37mCGROUPS_CPU\x1b[0m: \x1b[0;32menabled\x1b[0m\n\x1b[0;37mCGROUPS_CPUACCT\x1b[0m: \x1b[0;32menabled\x1b[0m\n\x1b[0;37mCGROUPS_CPUSET\x1b[0m: \x1b[0;32menabled\x1b[0m\n\x1b[0;37mCGROUPS_DEVICES\x1b[0m: \x1b[0;32menabled\x1b[0m\n\x1b[0;37mCGROUPS_FREEZER\x1b[0m: \x1b[0;32menabled\x1b[0m\n\x1b[0;37mCGROUPS_MEMORY\x1b[0m: \x1b[0;32menabled\x1b[0m\n\t[WARNING SystemVerification]: failed to parse kernel config: unable to load kernel module: "configs", output: "modprobe: FATAL: Module configs not found in directory /lib/modules/4.15.0-58-generic\n", err: exit status 1\nI0827 02:26:25.839540

[aojea]

🤔 it has

--ignore-preflight-errors=all

@ZhengZhenyu can you export the logs and share them with kind export logs?

[ZhengZhenyu]

🤔 it has

--ignore-preflight-errors=all

@ZhengZhenyu can you export the logs and share them with kind export logs?

How? just kind export logs and put it in our log dir?

[aojea]

@ZhengZhenyu sorry, I meant if you can export the logs of your test and create a tarball and link them to the issue or share by another method