=== RUN TestStartStop/group/old-k8s-version/serial/FirstStart
start_stop_delete_test.go:184: (dbg) Run: out/minikube-linux-amd64 start -p old-k8s-version-201745 --memory=2200 --alsologtostderr --wait=true --kvm-network=default --kvm-qemu-uri=qemu:///system --disable-driver-mounts --keep-context=false --driver=kvm2 --container-runtime=crio --kubernetes-version=v1.20.0
E0214 21:49:56.451200 250783 cert_rotation.go:171] "Unhandled Error" err="key failed with : open /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/functional-471578/client.crt: no such file or directory" logger="UnhandledError"
E0214 21:50:13.381571 250783 cert_rotation.go:171] "Unhandled Error" err="key failed with : open /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/functional-471578/client.crt: no such file or directory" logger="UnhandledError"
start_stop_delete_test.go:184: (dbg) Non-zero exit: out/minikube-linux-amd64 start -p old-k8s-version-201745 --memory=2200 --alsologtostderr --wait=true --kvm-network=default --kvm-qemu-uri=qemu:///system --disable-driver-mounts --keep-context=false --driver=kvm2 --container-runtime=crio --kubernetes-version=v1.20.0: exit status 109 (5m33.622912923s)
-- stdout --
* [old-k8s-version-201745] minikube v1.35.0 on Ubuntu 20.04 (kvm/amd64)
- MINIKUBE_LOCATION=20315
- MINIKUBE_SUPPRESS_DOCKER_PERFORMANCE=true
- KUBECONFIG=/home/jenkins/minikube-integration/20315-243456/kubeconfig
- MINIKUBE_HOME=/home/jenkins/minikube-integration/20315-243456/.minikube
- MINIKUBE_BIN=out/minikube-linux-amd64
- MINIKUBE_FORCE_SYSTEMD=
* Using the kvm2 driver based on user configuration
* Starting "old-k8s-version-201745" primary control-plane node in "old-k8s-version-201745" cluster
* Creating kvm2 VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
* Preparing Kubernetes v1.20.0 on CRI-O 1.29.1 ...
- Generating certificates and keys ...
- Booting up control plane ...
- Generating certificates and keys ...
- Booting up control plane ...
-- /stdout --
** stderr **
I0214 21:49:50.556636 290030 out.go:345] Setting OutFile to fd 1 ...
I0214 21:49:50.556721 290030 out.go:392] TERM=,COLORTERM=, which probably does not support color
I0214 21:49:50.556729 290030 out.go:358] Setting ErrFile to fd 2...
I0214 21:49:50.556733 290030 out.go:392] TERM=,COLORTERM=, which probably does not support color
I0214 21:49:50.557374 290030 root.go:338] Updating PATH: /home/jenkins/minikube-integration/20315-243456/.minikube/bin
I0214 21:49:50.558297 290030 out.go:352] Setting JSON to false
I0214 21:49:50.559474 290030 start.go:130] hostinfo: {"hostname":"ubuntu-20-agent-4","uptime":9135,"bootTime":1739560656,"procs":207,"os":"linux","platform":"ubuntu","platformFamily":"debian","platformVersion":"20.04","kernelVersion":"5.15.0-1075-gcp","kernelArch":"x86_64","virtualizationSystem":"kvm","virtualizationRole":"guest","hostId":"591c9f12-2938-3743-e2bf-c56a050d43d1"}
I0214 21:49:50.559576 290030 start.go:140] virtualization: kvm guest
I0214 21:49:50.561220 290030 out.go:177] * [old-k8s-version-201745] minikube v1.35.0 on Ubuntu 20.04 (kvm/amd64)
I0214 21:49:50.562817 290030 notify.go:220] Checking for updates...
I0214 21:49:50.562832 290030 out.go:177] - MINIKUBE_LOCATION=20315
I0214 21:49:50.563953 290030 out.go:177] - MINIKUBE_SUPPRESS_DOCKER_PERFORMANCE=true
I0214 21:49:50.565053 290030 out.go:177] - KUBECONFIG=/home/jenkins/minikube-integration/20315-243456/kubeconfig
I0214 21:49:50.566082 290030 out.go:177] - MINIKUBE_HOME=/home/jenkins/minikube-integration/20315-243456/.minikube
I0214 21:49:50.567119 290030 out.go:177] - MINIKUBE_BIN=out/minikube-linux-amd64
I0214 21:49:50.568227 290030 out.go:177] - MINIKUBE_FORCE_SYSTEMD=
I0214 21:49:50.569590 290030 config.go:182] Loaded profile config "cert-expiration-191481": Driver=kvm2, ContainerRuntime=crio, KubernetesVersion=v1.32.1
I0214 21:49:50.569702 290030 config.go:182] Loaded profile config "cert-options-733237": Driver=kvm2, ContainerRuntime=crio, KubernetesVersion=v1.32.1
I0214 21:49:50.569776 290030 config.go:182] Loaded profile config "kubernetes-upgrade-041692": Driver=kvm2, ContainerRuntime=crio, KubernetesVersion=v1.32.1
I0214 21:49:50.569863 290030 driver.go:394] Setting default libvirt URI to qemu:///system
I0214 21:49:50.604287 290030 out.go:177] * Using the kvm2 driver based on user configuration
I0214 21:49:50.605312 290030 start.go:304] selected driver: kvm2
I0214 21:49:50.605329 290030 start.go:908] validating driver "kvm2" against <nil>
I0214 21:49:50.605350 290030 start.go:919] status for kvm2: {Installed:true Healthy:true Running:true NeedsImprovement:false Error:<nil> Reason: Fix: Doc: Version:}
I0214 21:49:50.606325 290030 install.go:52] acquiring lock: {Name:mk900956b073697a4aa6c80a27c6bb0742a99a53 Clock:{} Delay:500ms Timeout:10m0s Cancel:<nil>}
I0214 21:49:50.606431 290030 install.go:117] Validating docker-machine-driver-kvm2, PATH=/home/jenkins/minikube-integration/20315-243456/.minikube/bin:/home/jenkins/workspace/KVM_Linux_crio_integration/out/:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/usr/local/go/bin:/home/jenkins/go/bin:/usr/local/bin/:/usr/local/go/bin/:/home/jenkins/go/bin
I0214 21:49:50.621235 290030 install.go:137] /home/jenkins/workspace/KVM_Linux_crio_integration/out/docker-machine-driver-kvm2 version is 1.35.0
I0214 21:49:50.621284 290030 start_flags.go:310] no existing cluster config was found, will generate one from the flags
I0214 21:49:50.621529 290030 start_flags.go:947] Waiting for all components: map[apiserver:true apps_running:true default_sa:true extra:true kubelet:true node_ready:true system_pods:true]
I0214 21:49:50.621561 290030 cni.go:84] Creating CNI manager for ""
I0214 21:49:50.621617 290030 cni.go:146] "kvm2" driver + "crio" runtime found, recommending bridge
I0214 21:49:50.621636 290030 start_flags.go:319] Found "bridge CNI" CNI - setting NetworkPlugin=cni
I0214 21:49:50.621701 290030 start.go:347] cluster config:
{Name:old-k8s-version-201745 KeepContext:false EmbedCerts:false MinikubeISO: KicBaseImage:gcr.io/k8s-minikube/kicbase-builds:v0.0.46-1739182054-20387@sha256:3788b0691001f3da958b3956b3e6c1d1db8535d5286bd2e096e6e75dc609dbad Memory:2200 CPUs:2 DiskSize:20000 Driver:kvm2 HyperkitVpnKitSock: HyperkitVSockPorts:[] DockerEnv:[] ContainerVolumeMounts:[] InsecureRegistry:[] RegistryMirror:[] HostOnlyCIDR:192.168.59.1/24 HypervVirtualSwitch: HypervUseExternalSwitch:false HypervExternalAdapter: KVMNetwork:default KVMQemuURI:qemu:///system KVMGPU:false KVMHidden:false KVMNUMACount:1 APIServerPort:8443 DockerOpt:[] DisableDriverMounts:true NFSShare:[] NFSSharesRoot:/nfsshares UUID: NoVTXCheck:false DNSProxy:false HostDNSResolver:true HostOnlyNicType:virtio NatNicType:virtio SSHIPAddress: SSHUser:root SSHKey: SSHPort:22 KubernetesConfig:{KubernetesVersion:v1.20.0 ClusterName:old-k8s-version-201745 Namespace:default APIServerHAVIP: APIServerName:minikubeCA APIServerNames:[] APIServerIPs:[] DNSDomain:cluster.local C
ontainerRuntime:crio CRISocket: NetworkPlugin:cni FeatureGates: ServiceCIDR:10.96.0.0/12 ImageRepository: LoadBalancerStartIP: LoadBalancerEndIP: CustomIngressCert: RegistryAliases: ExtraOptions:[] ShouldLoadCachedImages:true EnableDefaultCNI:false CNI:} Nodes:[{Name: IP: Port:8443 KubernetesVersion:v1.20.0 ContainerRuntime:crio ControlPlane:true Worker:true}] Addons:map[] CustomAddonImages:map[] CustomAddonRegistries:map[] VerifyComponents:map[apiserver:true apps_running:true default_sa:true extra:true kubelet:true node_ready:true system_pods:true] StartHostTimeout:6m0s ScheduledStop:<nil> ExposedPorts:[] ListenAddress: Network: Subnet: MultiNodeRequested:false ExtraDisks:0 CertExpiration:26280h0m0s Mount:false MountString:/home/jenkins:/minikube-host Mount9PVersion:9p2000.L MountGID:docker MountIP: MountMSize:262144 MountOptions:[] MountPort:0 MountType:9p MountUID:docker BinaryMirror: DisableOptimizations:false DisableMetrics:false CustomQemuFirmwarePath: SocketVMnetClientPath: SocketVMnetPath: StaticIP: S
SHAuthSock: SSHAgentPID:0 GPUs: AutoPauseInterval:1m0s}
I0214 21:49:50.621798 290030 iso.go:125] acquiring lock: {Name:mka34a06110b1b0e5d10d07fdcf0f95d49c057e1 Clock:{} Delay:500ms Timeout:10m0s Cancel:<nil>}
I0214 21:49:50.623212 290030 out.go:177] * Starting "old-k8s-version-201745" primary control-plane node in "old-k8s-version-201745" cluster
I0214 21:49:50.624373 290030 preload.go:131] Checking if preload exists for k8s version v1.20.0 and runtime crio
I0214 21:49:50.624409 290030 preload.go:146] Found local preload: /home/jenkins/minikube-integration/20315-243456/.minikube/cache/preloaded-tarball/preloaded-images-k8s-v18-v1.20.0-cri-o-overlay-amd64.tar.lz4
I0214 21:49:50.624419 290030 cache.go:56] Caching tarball of preloaded images
I0214 21:49:50.624493 290030 preload.go:172] Found /home/jenkins/minikube-integration/20315-243456/.minikube/cache/preloaded-tarball/preloaded-images-k8s-v18-v1.20.0-cri-o-overlay-amd64.tar.lz4 in cache, skipping download
I0214 21:49:50.624505 290030 cache.go:59] Finished verifying existence of preloaded tar for v1.20.0 on crio
I0214 21:49:50.624590 290030 profile.go:143] Saving config to /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/old-k8s-version-201745/config.json ...
I0214 21:49:50.624611 290030 lock.go:35] WriteFile acquiring /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/old-k8s-version-201745/config.json: {Name:mkb20fb7bf156a2ba7e1b89585c0fa08f6be2c13 Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0214 21:49:50.624747 290030 start.go:360] acquireMachinesLock for old-k8s-version-201745: {Name:mke9cb761c0a90adc4921ae56b4c4d949b22fb16 Clock:{} Delay:500ms Timeout:13m0s Cancel:<nil>}
I0214 21:50:55.363261 290030 start.go:364] duration metric: took 1m4.73848551s to acquireMachinesLock for "old-k8s-version-201745"
I0214 21:50:55.363378 290030 start.go:93] Provisioning new machine with config: &{Name:old-k8s-version-201745 KeepContext:false EmbedCerts:false MinikubeISO:https://storage.googleapis.com/minikube/iso/minikube-v1.35.0-amd64.iso KicBaseImage:gcr.io/k8s-minikube/kicbase-builds:v0.0.46-1739182054-20387@sha256:3788b0691001f3da958b3956b3e6c1d1db8535d5286bd2e096e6e75dc609dbad Memory:2200 CPUs:2 DiskSize:20000 Driver:kvm2 HyperkitVpnKitSock: HyperkitVSockPorts:[] DockerEnv:[] ContainerVolumeMounts:[] InsecureRegistry:[] RegistryMirror:[] HostOnlyCIDR:192.168.59.1/24 HypervVirtualSwitch: HypervUseExternalSwitch:false HypervExternalAdapter: KVMNetwork:default KVMQemuURI:qemu:///system KVMGPU:false KVMHidden:false KVMNUMACount:1 APIServerPort:8443 DockerOpt:[] DisableDriverMounts:true NFSShare:[] NFSSharesRoot:/nfsshares UUID: NoVTXCheck:false DNSProxy:false HostDNSResolver:true HostOnlyNicType:virtio NatNicType:virtio SSHIPAddress: SSHUser:root SSHKey: SSHPort:22 KubernetesConfig:{KubernetesVersion:v1.20.0 C
lusterName:old-k8s-version-201745 Namespace:default APIServerHAVIP: APIServerName:minikubeCA APIServerNames:[] APIServerIPs:[] DNSDomain:cluster.local ContainerRuntime:crio CRISocket: NetworkPlugin:cni FeatureGates: ServiceCIDR:10.96.0.0/12 ImageRepository: LoadBalancerStartIP: LoadBalancerEndIP: CustomIngressCert: RegistryAliases: ExtraOptions:[] ShouldLoadCachedImages:true EnableDefaultCNI:false CNI:} Nodes:[{Name: IP: Port:8443 KubernetesVersion:v1.20.0 ContainerRuntime:crio ControlPlane:true Worker:true}] Addons:map[] CustomAddonImages:map[] CustomAddonRegistries:map[] VerifyComponents:map[apiserver:true apps_running:true default_sa:true extra:true kubelet:true node_ready:true system_pods:true] StartHostTimeout:6m0s ScheduledStop:<nil> ExposedPorts:[] ListenAddress: Network: Subnet: MultiNodeRequested:false ExtraDisks:0 CertExpiration:26280h0m0s Mount:false MountString:/home/jenkins:/minikube-host Mount9PVersion:9p2000.L MountGID:docker MountIP: MountMSize:262144 MountOptions:[] MountPort:0 MountType:9p M
ountUID:docker BinaryMirror: DisableOptimizations:false DisableMetrics:false CustomQemuFirmwarePath: SocketVMnetClientPath: SocketVMnetPath: StaticIP: SSHAuthSock: SSHAgentPID:0 GPUs: AutoPauseInterval:1m0s} &{Name: IP: Port:8443 KubernetesVersion:v1.20.0 ContainerRuntime:crio ControlPlane:true Worker:true}
I0214 21:50:55.363470 290030 start.go:125] createHost starting for "" (driver="kvm2")
I0214 21:50:55.365187 290030 out.go:235] * Creating kvm2 VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
I0214 21:50:55.365395 290030 main.go:141] libmachine: Found binary path at /home/jenkins/workspace/KVM_Linux_crio_integration/out/docker-machine-driver-kvm2
I0214 21:50:55.365456 290030 main.go:141] libmachine: Launching plugin server for driver kvm2
I0214 21:50:55.381554 290030 main.go:141] libmachine: Plugin server listening at address 127.0.0.1:43029
I0214 21:50:55.381962 290030 main.go:141] libmachine: () Calling .GetVersion
I0214 21:50:55.382562 290030 main.go:141] libmachine: Using API Version 1
I0214 21:50:55.382592 290030 main.go:141] libmachine: () Calling .SetConfigRaw
I0214 21:50:55.382964 290030 main.go:141] libmachine: () Calling .GetMachineName
I0214 21:50:55.383187 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetMachineName
I0214 21:50:55.383362 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .DriverName
I0214 21:50:55.383507 290030 start.go:159] libmachine.API.Create for "old-k8s-version-201745" (driver="kvm2")
I0214 21:50:55.383547 290030 client.go:168] LocalClient.Create starting
I0214 21:50:55.383582 290030 main.go:141] libmachine: Reading certificate data from /home/jenkins/minikube-integration/20315-243456/.minikube/certs/ca.pem
I0214 21:50:55.383632 290030 main.go:141] libmachine: Decoding PEM data...
I0214 21:50:55.383663 290030 main.go:141] libmachine: Parsing certificate...
I0214 21:50:55.383754 290030 main.go:141] libmachine: Reading certificate data from /home/jenkins/minikube-integration/20315-243456/.minikube/certs/cert.pem
I0214 21:50:55.383787 290030 main.go:141] libmachine: Decoding PEM data...
I0214 21:50:55.383805 290030 main.go:141] libmachine: Parsing certificate...
I0214 21:50:55.383832 290030 main.go:141] libmachine: Running pre-create checks...
I0214 21:50:55.383846 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .PreCreateCheck
I0214 21:50:55.384196 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetConfigRaw
I0214 21:50:55.384611 290030 main.go:141] libmachine: Creating machine...
I0214 21:50:55.384627 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .Create
I0214 21:50:55.384759 290030 main.go:141] libmachine: (old-k8s-version-201745) creating KVM machine...
I0214 21:50:55.384788 290030 main.go:141] libmachine: (old-k8s-version-201745) creating network...
I0214 21:50:55.385923 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | found existing default KVM network
I0214 21:50:55.387518 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | I0214 21:50:55.387312 290690 network.go:211] skipping subnet 192.168.39.0/24 that is taken: &{IP:192.168.39.0 Netmask:255.255.255.0 Prefix:24 CIDR:192.168.39.0/24 Gateway:192.168.39.1 ClientMin:192.168.39.2 ClientMax:192.168.39.254 Broadcast:192.168.39.255 IsPrivate:true Interface:{IfaceName:virbr1 IfaceIPv4:192.168.39.1 IfaceMTU:1500 IfaceMAC:52:54:00:23:36:5f} reservation:<nil>}
I0214 21:50:55.388468 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | I0214 21:50:55.388381 290690 network.go:211] skipping subnet 192.168.50.0/24 that is taken: &{IP:192.168.50.0 Netmask:255.255.255.0 Prefix:24 CIDR:192.168.50.0/24 Gateway:192.168.50.1 ClientMin:192.168.50.2 ClientMax:192.168.50.254 Broadcast:192.168.50.255 IsPrivate:true Interface:{IfaceName:virbr2 IfaceIPv4:192.168.50.1 IfaceMTU:1500 IfaceMAC:52:54:00:b6:ad:f4} reservation:<nil>}
I0214 21:50:55.389476 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | I0214 21:50:55.389401 290690 network.go:211] skipping subnet 192.168.61.0/24 that is taken: &{IP:192.168.61.0 Netmask:255.255.255.0 Prefix:24 CIDR:192.168.61.0/24 Gateway:192.168.61.1 ClientMin:192.168.61.2 ClientMax:192.168.61.254 Broadcast:192.168.61.255 IsPrivate:true Interface:{IfaceName:virbr3 IfaceIPv4:192.168.61.1 IfaceMTU:1500 IfaceMAC:52:54:00:c8:c5:57} reservation:<nil>}
I0214 21:50:55.390645 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | I0214 21:50:55.390547 290690 network.go:206] using free private subnet 192.168.72.0/24: &{IP:192.168.72.0 Netmask:255.255.255.0 Prefix:24 CIDR:192.168.72.0/24 Gateway:192.168.72.1 ClientMin:192.168.72.2 ClientMax:192.168.72.254 Broadcast:192.168.72.255 IsPrivate:true Interface:{IfaceName: IfaceIPv4: IfaceMTU:0 IfaceMAC:} reservation:0xc0002a1920}
I0214 21:50:55.390676 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | created network xml:
I0214 21:50:55.390694 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | <network>
I0214 21:50:55.390703 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | <name>mk-old-k8s-version-201745</name>
I0214 21:50:55.390715 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | <dns enable='no'/>
I0214 21:50:55.390722 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG |
I0214 21:50:55.390733 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | <ip address='192.168.72.1' netmask='255.255.255.0'>
I0214 21:50:55.390747 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | <dhcp>
I0214 21:50:55.390757 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | <range start='192.168.72.2' end='192.168.72.253'/>
I0214 21:50:55.390768 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | </dhcp>
I0214 21:50:55.390776 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | </ip>
I0214 21:50:55.390782 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG |
I0214 21:50:55.390790 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | </network>
I0214 21:50:55.390797 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG |
I0214 21:50:55.395491 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | trying to create private KVM network mk-old-k8s-version-201745 192.168.72.0/24...
I0214 21:50:55.462132 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | private KVM network mk-old-k8s-version-201745 192.168.72.0/24 created
I0214 21:50:55.462163 290030 main.go:141] libmachine: (old-k8s-version-201745) setting up store path in /home/jenkins/minikube-integration/20315-243456/.minikube/machines/old-k8s-version-201745 ...
I0214 21:50:55.462180 290030 main.go:141] libmachine: (old-k8s-version-201745) building disk image from file:///home/jenkins/minikube-integration/20315-243456/.minikube/cache/iso/amd64/minikube-v1.35.0-amd64.iso
I0214 21:50:55.462199 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | I0214 21:50:55.462108 290690 common.go:144] Making disk image using store path: /home/jenkins/minikube-integration/20315-243456/.minikube
I0214 21:50:55.462276 290030 main.go:141] libmachine: (old-k8s-version-201745) Downloading /home/jenkins/minikube-integration/20315-243456/.minikube/cache/boot2docker.iso from file:///home/jenkins/minikube-integration/20315-243456/.minikube/cache/iso/amd64/minikube-v1.35.0-amd64.iso...
I0214 21:50:55.744579 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | I0214 21:50:55.744460 290690 common.go:151] Creating ssh key: /home/jenkins/minikube-integration/20315-243456/.minikube/machines/old-k8s-version-201745/id_rsa...
I0214 21:50:55.791378 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | I0214 21:50:55.791288 290690 common.go:157] Creating raw disk image: /home/jenkins/minikube-integration/20315-243456/.minikube/machines/old-k8s-version-201745/old-k8s-version-201745.rawdisk...
I0214 21:50:55.791407 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | Writing magic tar header
I0214 21:50:55.791424 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | Writing SSH key tar header
I0214 21:50:55.791446 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | I0214 21:50:55.791384 290690 common.go:171] Fixing permissions on /home/jenkins/minikube-integration/20315-243456/.minikube/machines/old-k8s-version-201745 ...
I0214 21:50:55.791567 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | checking permissions on dir: /home/jenkins/minikube-integration/20315-243456/.minikube/machines/old-k8s-version-201745
I0214 21:50:55.791609 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | checking permissions on dir: /home/jenkins/minikube-integration/20315-243456/.minikube/machines
I0214 21:50:55.791631 290030 main.go:141] libmachine: (old-k8s-version-201745) setting executable bit set on /home/jenkins/minikube-integration/20315-243456/.minikube/machines/old-k8s-version-201745 (perms=drwx------)
I0214 21:50:55.791651 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | checking permissions on dir: /home/jenkins/minikube-integration/20315-243456/.minikube
I0214 21:50:55.791666 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | checking permissions on dir: /home/jenkins/minikube-integration/20315-243456
I0214 21:50:55.791677 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | checking permissions on dir: /home/jenkins/minikube-integration
I0214 21:50:55.791685 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | checking permissions on dir: /home/jenkins
I0214 21:50:55.791698 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | checking permissions on dir: /home
I0214 21:50:55.791712 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | skipping /home - not owner
I0214 21:50:55.791733 290030 main.go:141] libmachine: (old-k8s-version-201745) setting executable bit set on /home/jenkins/minikube-integration/20315-243456/.minikube/machines (perms=drwxr-xr-x)
I0214 21:50:55.791752 290030 main.go:141] libmachine: (old-k8s-version-201745) setting executable bit set on /home/jenkins/minikube-integration/20315-243456/.minikube (perms=drwxr-xr-x)
I0214 21:50:55.791767 290030 main.go:141] libmachine: (old-k8s-version-201745) setting executable bit set on /home/jenkins/minikube-integration/20315-243456 (perms=drwxrwxr-x)
I0214 21:50:55.791786 290030 main.go:141] libmachine: (old-k8s-version-201745) setting executable bit set on /home/jenkins/minikube-integration (perms=drwxrwxr-x)
I0214 21:50:55.791801 290030 main.go:141] libmachine: (old-k8s-version-201745) setting executable bit set on /home/jenkins (perms=drwxr-xr-x)
I0214 21:50:55.791811 290030 main.go:141] libmachine: (old-k8s-version-201745) creating domain...
I0214 21:50:55.792676 290030 main.go:141] libmachine: (old-k8s-version-201745) define libvirt domain using xml:
I0214 21:50:55.792698 290030 main.go:141] libmachine: (old-k8s-version-201745) <domain type='kvm'>
I0214 21:50:55.792709 290030 main.go:141] libmachine: (old-k8s-version-201745) <name>old-k8s-version-201745</name>
I0214 21:50:55.792727 290030 main.go:141] libmachine: (old-k8s-version-201745) <memory unit='MiB'>2200</memory>
I0214 21:50:55.792738 290030 main.go:141] libmachine: (old-k8s-version-201745) <vcpu>2</vcpu>
I0214 21:50:55.792767 290030 main.go:141] libmachine: (old-k8s-version-201745) <features>
I0214 21:50:55.792778 290030 main.go:141] libmachine: (old-k8s-version-201745) <acpi/>
I0214 21:50:55.792784 290030 main.go:141] libmachine: (old-k8s-version-201745) <apic/>
I0214 21:50:55.792794 290030 main.go:141] libmachine: (old-k8s-version-201745) <pae/>
I0214 21:50:55.792811 290030 main.go:141] libmachine: (old-k8s-version-201745)
I0214 21:50:55.792825 290030 main.go:141] libmachine: (old-k8s-version-201745) </features>
I0214 21:50:55.792838 290030 main.go:141] libmachine: (old-k8s-version-201745) <cpu mode='host-passthrough'>
I0214 21:50:55.792851 290030 main.go:141] libmachine: (old-k8s-version-201745)
I0214 21:50:55.792863 290030 main.go:141] libmachine: (old-k8s-version-201745) </cpu>
I0214 21:50:55.792876 290030 main.go:141] libmachine: (old-k8s-version-201745) <os>
I0214 21:50:55.792893 290030 main.go:141] libmachine: (old-k8s-version-201745) <type>hvm</type>
I0214 21:50:55.792907 290030 main.go:141] libmachine: (old-k8s-version-201745) <boot dev='cdrom'/>
I0214 21:50:55.792920 290030 main.go:141] libmachine: (old-k8s-version-201745) <boot dev='hd'/>
I0214 21:50:55.792934 290030 main.go:141] libmachine: (old-k8s-version-201745) <bootmenu enable='no'/>
I0214 21:50:55.792954 290030 main.go:141] libmachine: (old-k8s-version-201745) </os>
I0214 21:50:55.792985 290030 main.go:141] libmachine: (old-k8s-version-201745) <devices>
I0214 21:50:55.793016 290030 main.go:141] libmachine: (old-k8s-version-201745) <disk type='file' device='cdrom'>
I0214 21:50:55.793038 290030 main.go:141] libmachine: (old-k8s-version-201745) <source file='/home/jenkins/minikube-integration/20315-243456/.minikube/machines/old-k8s-version-201745/boot2docker.iso'/>
I0214 21:50:55.793046 290030 main.go:141] libmachine: (old-k8s-version-201745) <target dev='hdc' bus='scsi'/>
I0214 21:50:55.793079 290030 main.go:141] libmachine: (old-k8s-version-201745) <readonly/>
I0214 21:50:55.793099 290030 main.go:141] libmachine: (old-k8s-version-201745) </disk>
I0214 21:50:55.793122 290030 main.go:141] libmachine: (old-k8s-version-201745) <disk type='file' device='disk'>
I0214 21:50:55.793140 290030 main.go:141] libmachine: (old-k8s-version-201745) <driver name='qemu' type='raw' cache='default' io='threads' />
I0214 21:50:55.793158 290030 main.go:141] libmachine: (old-k8s-version-201745) <source file='/home/jenkins/minikube-integration/20315-243456/.minikube/machines/old-k8s-version-201745/old-k8s-version-201745.rawdisk'/>
I0214 21:50:55.793169 290030 main.go:141] libmachine: (old-k8s-version-201745) <target dev='hda' bus='virtio'/>
I0214 21:50:55.793178 290030 main.go:141] libmachine: (old-k8s-version-201745) </disk>
I0214 21:50:55.793189 290030 main.go:141] libmachine: (old-k8s-version-201745) <interface type='network'>
I0214 21:50:55.793201 290030 main.go:141] libmachine: (old-k8s-version-201745) <source network='mk-old-k8s-version-201745'/>
I0214 21:50:55.793209 290030 main.go:141] libmachine: (old-k8s-version-201745) <model type='virtio'/>
I0214 21:50:55.793223 290030 main.go:141] libmachine: (old-k8s-version-201745) </interface>
I0214 21:50:55.793241 290030 main.go:141] libmachine: (old-k8s-version-201745) <interface type='network'>
I0214 21:50:55.793255 290030 main.go:141] libmachine: (old-k8s-version-201745) <source network='default'/>
I0214 21:50:55.793263 290030 main.go:141] libmachine: (old-k8s-version-201745) <model type='virtio'/>
I0214 21:50:55.793275 290030 main.go:141] libmachine: (old-k8s-version-201745) </interface>
I0214 21:50:55.793283 290030 main.go:141] libmachine: (old-k8s-version-201745) <serial type='pty'>
I0214 21:50:55.793295 290030 main.go:141] libmachine: (old-k8s-version-201745) <target port='0'/>
I0214 21:50:55.793302 290030 main.go:141] libmachine: (old-k8s-version-201745) </serial>
I0214 21:50:55.793318 290030 main.go:141] libmachine: (old-k8s-version-201745) <console type='pty'>
I0214 21:50:55.793332 290030 main.go:141] libmachine: (old-k8s-version-201745) <target type='serial' port='0'/>
I0214 21:50:55.793345 290030 main.go:141] libmachine: (old-k8s-version-201745) </console>
I0214 21:50:55.793355 290030 main.go:141] libmachine: (old-k8s-version-201745) <rng model='virtio'>
I0214 21:50:55.793370 290030 main.go:141] libmachine: (old-k8s-version-201745) <backend model='random'>/dev/random</backend>
I0214 21:50:55.793385 290030 main.go:141] libmachine: (old-k8s-version-201745) </rng>
I0214 21:50:55.793394 290030 main.go:141] libmachine: (old-k8s-version-201745)
I0214 21:50:55.793402 290030 main.go:141] libmachine: (old-k8s-version-201745)
I0214 21:50:55.793419 290030 main.go:141] libmachine: (old-k8s-version-201745) </devices>
I0214 21:50:55.793428 290030 main.go:141] libmachine: (old-k8s-version-201745) </domain>
I0214 21:50:55.793438 290030 main.go:141] libmachine: (old-k8s-version-201745)
I0214 21:50:55.797313 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:cc:46:24 in network default
I0214 21:50:55.797892 290030 main.go:141] libmachine: (old-k8s-version-201745) starting domain...
I0214 21:50:55.797914 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:50:55.797922 290030 main.go:141] libmachine: (old-k8s-version-201745) ensuring networks are active...
I0214 21:50:55.798541 290030 main.go:141] libmachine: (old-k8s-version-201745) Ensuring network default is active
I0214 21:50:55.798875 290030 main.go:141] libmachine: (old-k8s-version-201745) Ensuring network mk-old-k8s-version-201745 is active
I0214 21:50:55.799462 290030 main.go:141] libmachine: (old-k8s-version-201745) getting domain XML...
I0214 21:50:55.800146 290030 main.go:141] libmachine: (old-k8s-version-201745) creating domain...
I0214 21:50:56.148493 290030 main.go:141] libmachine: (old-k8s-version-201745) waiting for IP...
I0214 21:50:56.149380 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:50:56.149909 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | unable to find current IP address of domain old-k8s-version-201745 in network mk-old-k8s-version-201745
I0214 21:50:56.150019 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | I0214 21:50:56.149906 290690 retry.go:31] will retry after 261.837264ms: waiting for domain to come up
I0214 21:50:56.413460 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:50:56.414105 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | unable to find current IP address of domain old-k8s-version-201745 in network mk-old-k8s-version-201745
I0214 21:50:56.414163 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | I0214 21:50:56.414075 290690 retry.go:31] will retry after 330.242166ms: waiting for domain to come up
I0214 21:50:56.746462 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:50:56.747030 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | unable to find current IP address of domain old-k8s-version-201745 in network mk-old-k8s-version-201745
I0214 21:50:56.747061 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | I0214 21:50:56.746989 290690 retry.go:31] will retry after 416.03943ms: waiting for domain to come up
I0214 21:50:57.164718 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:50:57.165222 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | unable to find current IP address of domain old-k8s-version-201745 in network mk-old-k8s-version-201745
I0214 21:50:57.165261 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | I0214 21:50:57.165204 290690 retry.go:31] will retry after 578.08552ms: waiting for domain to come up
I0214 21:50:57.746263 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:50:57.747028 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | unable to find current IP address of domain old-k8s-version-201745 in network mk-old-k8s-version-201745
I0214 21:50:57.747059 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | I0214 21:50:57.746994 290690 retry.go:31] will retry after 651.818557ms: waiting for domain to come up
I0214 21:50:58.400987 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:50:58.401535 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | unable to find current IP address of domain old-k8s-version-201745 in network mk-old-k8s-version-201745
I0214 21:50:58.401566 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | I0214 21:50:58.401487 290690 retry.go:31] will retry after 588.56538ms: waiting for domain to come up
I0214 21:50:58.991361 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:50:58.991875 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | unable to find current IP address of domain old-k8s-version-201745 in network mk-old-k8s-version-201745
I0214 21:50:58.991907 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | I0214 21:50:58.991851 290690 retry.go:31] will retry after 932.433175ms: waiting for domain to come up
I0214 21:50:59.925797 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:50:59.926454 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | unable to find current IP address of domain old-k8s-version-201745 in network mk-old-k8s-version-201745
I0214 21:50:59.926486 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | I0214 21:50:59.926398 290690 retry.go:31] will retry after 1.189025506s: waiting for domain to come up
I0214 21:51:01.116921 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:01.117469 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | unable to find current IP address of domain old-k8s-version-201745 in network mk-old-k8s-version-201745
I0214 21:51:01.117495 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | I0214 21:51:01.117446 290690 retry.go:31] will retry after 1.257559774s: waiting for domain to come up
I0214 21:51:02.376775 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:02.377116 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | unable to find current IP address of domain old-k8s-version-201745 in network mk-old-k8s-version-201745
I0214 21:51:02.377144 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | I0214 21:51:02.377098 290690 retry.go:31] will retry after 1.619179944s: waiting for domain to come up
I0214 21:51:03.998332 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:03.998979 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | unable to find current IP address of domain old-k8s-version-201745 in network mk-old-k8s-version-201745
I0214 21:51:03.999012 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | I0214 21:51:03.998926 290690 retry.go:31] will retry after 2.080022335s: waiting for domain to come up
I0214 21:51:06.080451 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:06.080994 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | unable to find current IP address of domain old-k8s-version-201745 in network mk-old-k8s-version-201745
I0214 21:51:06.081026 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | I0214 21:51:06.080958 290690 retry.go:31] will retry after 2.295955346s: waiting for domain to come up
I0214 21:51:08.378010 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:08.378472 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | unable to find current IP address of domain old-k8s-version-201745 in network mk-old-k8s-version-201745
I0214 21:51:08.378508 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | I0214 21:51:08.378432 290690 retry.go:31] will retry after 3.539619619s: waiting for domain to come up
I0214 21:51:11.920280 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:11.920742 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | unable to find current IP address of domain old-k8s-version-201745 in network mk-old-k8s-version-201745
I0214 21:51:11.920773 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | I0214 21:51:11.920699 290690 retry.go:31] will retry after 3.678466874s: waiting for domain to come up
I0214 21:51:15.640099 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:15.640675 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has current primary IP address 192.168.72.19 and MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:15.640700 290030 main.go:141] libmachine: (old-k8s-version-201745) found domain IP: 192.168.72.19
I0214 21:51:15.640713 290030 main.go:141] libmachine: (old-k8s-version-201745) reserving static IP address...
I0214 21:51:15.640986 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | unable to find host DHCP lease matching {name: "old-k8s-version-201745", mac: "52:54:00:6d:30:ba", ip: "192.168.72.19"} in network mk-old-k8s-version-201745
I0214 21:51:15.715520 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | Getting to WaitForSSH function...
I0214 21:51:15.715550 290030 main.go:141] libmachine: (old-k8s-version-201745) reserved static IP address 192.168.72.19 for domain old-k8s-version-201745
I0214 21:51:15.715563 290030 main.go:141] libmachine: (old-k8s-version-201745) waiting for SSH...
I0214 21:51:15.718541 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:15.719032 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | unable to find host DHCP lease matching {name: "", mac: "52:54:00:6d:30:ba", ip: ""} in network mk-old-k8s-version-201745
I0214 21:51:15.719060 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | unable to find defined IP address of network mk-old-k8s-version-201745 interface with MAC address 52:54:00:6d:30:ba
I0214 21:51:15.719260 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | Using SSH client type: external
I0214 21:51:15.719310 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | Using SSH private key: /home/jenkins/minikube-integration/20315-243456/.minikube/machines/old-k8s-version-201745/id_rsa (-rw-------)
I0214 21:51:15.719384 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | &{[-F /dev/null -o ConnectionAttempts=3 -o ConnectTimeout=10 -o ControlMaster=no -o ControlPath=none -o LogLevel=quiet -o PasswordAuthentication=no -o ServerAliveInterval=60 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null docker@ -o IdentitiesOnly=yes -i /home/jenkins/minikube-integration/20315-243456/.minikube/machines/old-k8s-version-201745/id_rsa -p 22] /usr/bin/ssh <nil>}
I0214 21:51:15.719407 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | About to run SSH command:
I0214 21:51:15.719421 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | exit 0
I0214 21:51:15.723259 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | SSH cmd err, output: exit status 255:
I0214 21:51:15.723284 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | Error getting ssh command 'exit 0' : ssh command error:
I0214 21:51:15.723294 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | command : exit 0
I0214 21:51:15.723305 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | err : exit status 255
I0214 21:51:15.723318 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | output :
I0214 21:51:18.723432 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | Getting to WaitForSSH function...
I0214 21:51:18.725873 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:18.726290 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:6d:30:ba", ip: ""} in network mk-old-k8s-version-201745: {Iface:virbr4 ExpiryTime:2025-02-14 22:51:10 +0000 UTC Type:0 Mac:52:54:00:6d:30:ba Iaid: IPaddr:192.168.72.19 Prefix:24 Hostname:old-k8s-version-201745 Clientid:01:52:54:00:6d:30:ba}
I0214 21:51:18.726324 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined IP address 192.168.72.19 and MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:18.726416 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | Using SSH client type: external
I0214 21:51:18.726440 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | Using SSH private key: /home/jenkins/minikube-integration/20315-243456/.minikube/machines/old-k8s-version-201745/id_rsa (-rw-------)
I0214 21:51:18.726492 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | &{[-F /dev/null -o ConnectionAttempts=3 -o ConnectTimeout=10 -o ControlMaster=no -o ControlPath=none -o LogLevel=quiet -o PasswordAuthentication=no -o ServerAliveInterval=60 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null docker@192.168.72.19 -o IdentitiesOnly=yes -i /home/jenkins/minikube-integration/20315-243456/.minikube/machines/old-k8s-version-201745/id_rsa -p 22] /usr/bin/ssh <nil>}
I0214 21:51:18.726516 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | About to run SSH command:
I0214 21:51:18.726559 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | exit 0
I0214 21:51:18.854734 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | SSH cmd err, output: <nil>:
I0214 21:51:18.854978 290030 main.go:141] libmachine: (old-k8s-version-201745) KVM machine creation complete
I0214 21:51:18.855264 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetConfigRaw
I0214 21:51:18.855878 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .DriverName
I0214 21:51:18.856070 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .DriverName
I0214 21:51:18.856221 290030 main.go:141] libmachine: Waiting for machine to be running, this may take a few minutes...
I0214 21:51:18.856246 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetState
I0214 21:51:18.857655 290030 main.go:141] libmachine: Detecting operating system of created instance...
I0214 21:51:18.857667 290030 main.go:141] libmachine: Waiting for SSH to be available...
I0214 21:51:18.857672 290030 main.go:141] libmachine: Getting to WaitForSSH function...
I0214 21:51:18.857678 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHHostname
I0214 21:51:18.860018 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:18.860340 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:6d:30:ba", ip: ""} in network mk-old-k8s-version-201745: {Iface:virbr4 ExpiryTime:2025-02-14 22:51:10 +0000 UTC Type:0 Mac:52:54:00:6d:30:ba Iaid: IPaddr:192.168.72.19 Prefix:24 Hostname:old-k8s-version-201745 Clientid:01:52:54:00:6d:30:ba}
I0214 21:51:18.860362 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined IP address 192.168.72.19 and MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:18.860546 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHPort
I0214 21:51:18.860711 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHKeyPath
I0214 21:51:18.860828 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHKeyPath
I0214 21:51:18.860966 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHUsername
I0214 21:51:18.861120 290030 main.go:141] libmachine: Using SSH client type: native
I0214 21:51:18.861388 290030 main.go:141] libmachine: &{{{<nil> 0 [] [] []} docker [0x865ca0] 0x868980 <nil> [] 0s} 192.168.72.19 22 <nil> <nil>}
I0214 21:51:18.861403 290030 main.go:141] libmachine: About to run SSH command:
exit 0
I0214 21:51:18.973467 290030 main.go:141] libmachine: SSH cmd err, output: <nil>:
I0214 21:51:18.973488 290030 main.go:141] libmachine: Detecting the provisioner...
I0214 21:51:18.973498 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHHostname
I0214 21:51:18.975816 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:18.976116 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:6d:30:ba", ip: ""} in network mk-old-k8s-version-201745: {Iface:virbr4 ExpiryTime:2025-02-14 22:51:10 +0000 UTC Type:0 Mac:52:54:00:6d:30:ba Iaid: IPaddr:192.168.72.19 Prefix:24 Hostname:old-k8s-version-201745 Clientid:01:52:54:00:6d:30:ba}
I0214 21:51:18.976159 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined IP address 192.168.72.19 and MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:18.976279 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHPort
I0214 21:51:18.976456 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHKeyPath
I0214 21:51:18.976572 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHKeyPath
I0214 21:51:18.976662 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHUsername
I0214 21:51:18.976784 290030 main.go:141] libmachine: Using SSH client type: native
I0214 21:51:18.976987 290030 main.go:141] libmachine: &{{{<nil> 0 [] [] []} docker [0x865ca0] 0x868980 <nil> [] 0s} 192.168.72.19 22 <nil> <nil>}
I0214 21:51:18.977004 290030 main.go:141] libmachine: About to run SSH command:
cat /etc/os-release
I0214 21:51:19.090945 290030 main.go:141] libmachine: SSH cmd err, output: <nil>: NAME=Buildroot
VERSION=2023.02.9-dirty
ID=buildroot
VERSION_ID=2023.02.9
PRETTY_NAME="Buildroot 2023.02.9"
I0214 21:51:19.091009 290030 main.go:141] libmachine: found compatible host: buildroot
I0214 21:51:19.091023 290030 main.go:141] libmachine: Provisioning with buildroot...
I0214 21:51:19.091033 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetMachineName
I0214 21:51:19.091241 290030 buildroot.go:166] provisioning hostname "old-k8s-version-201745"
I0214 21:51:19.091270 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetMachineName
I0214 21:51:19.091452 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHHostname
I0214 21:51:19.094065 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:19.094414 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:6d:30:ba", ip: ""} in network mk-old-k8s-version-201745: {Iface:virbr4 ExpiryTime:2025-02-14 22:51:10 +0000 UTC Type:0 Mac:52:54:00:6d:30:ba Iaid: IPaddr:192.168.72.19 Prefix:24 Hostname:old-k8s-version-201745 Clientid:01:52:54:00:6d:30:ba}
I0214 21:51:19.094440 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined IP address 192.168.72.19 and MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:19.094593 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHPort
I0214 21:51:19.094795 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHKeyPath
I0214 21:51:19.094958 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHKeyPath
I0214 21:51:19.095110 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHUsername
I0214 21:51:19.095272 290030 main.go:141] libmachine: Using SSH client type: native
I0214 21:51:19.095437 290030 main.go:141] libmachine: &{{{<nil> 0 [] [] []} docker [0x865ca0] 0x868980 <nil> [] 0s} 192.168.72.19 22 <nil> <nil>}
I0214 21:51:19.095454 290030 main.go:141] libmachine: About to run SSH command:
sudo hostname old-k8s-version-201745 && echo "old-k8s-version-201745" | sudo tee /etc/hostname
I0214 21:51:19.220062 290030 main.go:141] libmachine: SSH cmd err, output: <nil>: old-k8s-version-201745
I0214 21:51:19.220089 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHHostname
I0214 21:51:19.223057 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:19.223416 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:6d:30:ba", ip: ""} in network mk-old-k8s-version-201745: {Iface:virbr4 ExpiryTime:2025-02-14 22:51:10 +0000 UTC Type:0 Mac:52:54:00:6d:30:ba Iaid: IPaddr:192.168.72.19 Prefix:24 Hostname:old-k8s-version-201745 Clientid:01:52:54:00:6d:30:ba}
I0214 21:51:19.223447 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined IP address 192.168.72.19 and MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:19.223621 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHPort
I0214 21:51:19.223801 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHKeyPath
I0214 21:51:19.223975 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHKeyPath
I0214 21:51:19.224107 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHUsername
I0214 21:51:19.224265 290030 main.go:141] libmachine: Using SSH client type: native
I0214 21:51:19.224482 290030 main.go:141] libmachine: &{{{<nil> 0 [] [] []} docker [0x865ca0] 0x868980 <nil> [] 0s} 192.168.72.19 22 <nil> <nil>}
I0214 21:51:19.224505 290030 main.go:141] libmachine: About to run SSH command:
if ! grep -xq '.*\sold-k8s-version-201745' /etc/hosts; then
if grep -xq '127.0.1.1\s.*' /etc/hosts; then
sudo sed -i 's/^127.0.1.1\s.*/127.0.1.1 old-k8s-version-201745/g' /etc/hosts;
else
echo '127.0.1.1 old-k8s-version-201745' | sudo tee -a /etc/hosts;
fi
fi
I0214 21:51:19.343025 290030 main.go:141] libmachine: SSH cmd err, output: <nil>:
I0214 21:51:19.343046 290030 buildroot.go:172] set auth options {CertDir:/home/jenkins/minikube-integration/20315-243456/.minikube CaCertPath:/home/jenkins/minikube-integration/20315-243456/.minikube/certs/ca.pem CaPrivateKeyPath:/home/jenkins/minikube-integration/20315-243456/.minikube/certs/ca-key.pem CaCertRemotePath:/etc/docker/ca.pem ServerCertPath:/home/jenkins/minikube-integration/20315-243456/.minikube/machines/server.pem ServerKeyPath:/home/jenkins/minikube-integration/20315-243456/.minikube/machines/server-key.pem ClientKeyPath:/home/jenkins/minikube-integration/20315-243456/.minikube/certs/key.pem ServerCertRemotePath:/etc/docker/server.pem ServerKeyRemotePath:/etc/docker/server-key.pem ClientCertPath:/home/jenkins/minikube-integration/20315-243456/.minikube/certs/cert.pem ServerCertSANs:[] StorePath:/home/jenkins/minikube-integration/20315-243456/.minikube}
I0214 21:51:19.343072 290030 buildroot.go:174] setting up certificates
I0214 21:51:19.343085 290030 provision.go:84] configureAuth start
I0214 21:51:19.343094 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetMachineName
I0214 21:51:19.343305 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetIP
I0214 21:51:19.345461 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:19.345781 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:6d:30:ba", ip: ""} in network mk-old-k8s-version-201745: {Iface:virbr4 ExpiryTime:2025-02-14 22:51:10 +0000 UTC Type:0 Mac:52:54:00:6d:30:ba Iaid: IPaddr:192.168.72.19 Prefix:24 Hostname:old-k8s-version-201745 Clientid:01:52:54:00:6d:30:ba}
I0214 21:51:19.345802 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined IP address 192.168.72.19 and MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:19.346004 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHHostname
I0214 21:51:19.348488 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:19.348896 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:6d:30:ba", ip: ""} in network mk-old-k8s-version-201745: {Iface:virbr4 ExpiryTime:2025-02-14 22:51:10 +0000 UTC Type:0 Mac:52:54:00:6d:30:ba Iaid: IPaddr:192.168.72.19 Prefix:24 Hostname:old-k8s-version-201745 Clientid:01:52:54:00:6d:30:ba}
I0214 21:51:19.348924 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined IP address 192.168.72.19 and MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:19.349075 290030 provision.go:143] copyHostCerts
I0214 21:51:19.349175 290030 exec_runner.go:144] found /home/jenkins/minikube-integration/20315-243456/.minikube/cert.pem, removing ...
I0214 21:51:19.349195 290030 exec_runner.go:203] rm: /home/jenkins/minikube-integration/20315-243456/.minikube/cert.pem
I0214 21:51:19.349262 290030 exec_runner.go:151] cp: /home/jenkins/minikube-integration/20315-243456/.minikube/certs/cert.pem --> /home/jenkins/minikube-integration/20315-243456/.minikube/cert.pem (1123 bytes)
I0214 21:51:19.349347 290030 exec_runner.go:144] found /home/jenkins/minikube-integration/20315-243456/.minikube/key.pem, removing ...
I0214 21:51:19.349355 290030 exec_runner.go:203] rm: /home/jenkins/minikube-integration/20315-243456/.minikube/key.pem
I0214 21:51:19.349376 290030 exec_runner.go:151] cp: /home/jenkins/minikube-integration/20315-243456/.minikube/certs/key.pem --> /home/jenkins/minikube-integration/20315-243456/.minikube/key.pem (1675 bytes)
I0214 21:51:19.349425 290030 exec_runner.go:144] found /home/jenkins/minikube-integration/20315-243456/.minikube/ca.pem, removing ...
I0214 21:51:19.349431 290030 exec_runner.go:203] rm: /home/jenkins/minikube-integration/20315-243456/.minikube/ca.pem
I0214 21:51:19.349447 290030 exec_runner.go:151] cp: /home/jenkins/minikube-integration/20315-243456/.minikube/certs/ca.pem --> /home/jenkins/minikube-integration/20315-243456/.minikube/ca.pem (1082 bytes)
I0214 21:51:19.349490 290030 provision.go:117] generating server cert: /home/jenkins/minikube-integration/20315-243456/.minikube/machines/server.pem ca-key=/home/jenkins/minikube-integration/20315-243456/.minikube/certs/ca.pem private-key=/home/jenkins/minikube-integration/20315-243456/.minikube/certs/ca-key.pem org=jenkins.old-k8s-version-201745 san=[127.0.0.1 192.168.72.19 localhost minikube old-k8s-version-201745]
I0214 21:51:19.490071 290030 provision.go:177] copyRemoteCerts
I0214 21:51:19.490142 290030 ssh_runner.go:195] Run: sudo mkdir -p /etc/docker /etc/docker /etc/docker
I0214 21:51:19.490171 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHHostname
I0214 21:51:19.492319 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:19.492662 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:6d:30:ba", ip: ""} in network mk-old-k8s-version-201745: {Iface:virbr4 ExpiryTime:2025-02-14 22:51:10 +0000 UTC Type:0 Mac:52:54:00:6d:30:ba Iaid: IPaddr:192.168.72.19 Prefix:24 Hostname:old-k8s-version-201745 Clientid:01:52:54:00:6d:30:ba}
I0214 21:51:19.492693 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined IP address 192.168.72.19 and MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:19.492871 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHPort
I0214 21:51:19.493054 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHKeyPath
I0214 21:51:19.493217 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHUsername
I0214 21:51:19.493348 290030 sshutil.go:53] new ssh client: &{IP:192.168.72.19 Port:22 SSHKeyPath:/home/jenkins/minikube-integration/20315-243456/.minikube/machines/old-k8s-version-201745/id_rsa Username:docker}
I0214 21:51:19.580628 290030 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20315-243456/.minikube/machines/server.pem --> /etc/docker/server.pem (1233 bytes)
I0214 21:51:19.606167 290030 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20315-243456/.minikube/machines/server-key.pem --> /etc/docker/server-key.pem (1679 bytes)
I0214 21:51:19.630070 290030 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20315-243456/.minikube/certs/ca.pem --> /etc/docker/ca.pem (1082 bytes)
I0214 21:51:19.654540 290030 provision.go:87] duration metric: took 311.444497ms to configureAuth
I0214 21:51:19.654561 290030 buildroot.go:189] setting minikube options for container-runtime
I0214 21:51:19.654747 290030 config.go:182] Loaded profile config "old-k8s-version-201745": Driver=kvm2, ContainerRuntime=crio, KubernetesVersion=v1.20.0
I0214 21:51:19.654829 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHHostname
I0214 21:51:19.657192 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:19.657555 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:6d:30:ba", ip: ""} in network mk-old-k8s-version-201745: {Iface:virbr4 ExpiryTime:2025-02-14 22:51:10 +0000 UTC Type:0 Mac:52:54:00:6d:30:ba Iaid: IPaddr:192.168.72.19 Prefix:24 Hostname:old-k8s-version-201745 Clientid:01:52:54:00:6d:30:ba}
I0214 21:51:19.657605 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined IP address 192.168.72.19 and MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:19.657786 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHPort
I0214 21:51:19.657983 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHKeyPath
I0214 21:51:19.658158 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHKeyPath
I0214 21:51:19.658304 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHUsername
I0214 21:51:19.658512 290030 main.go:141] libmachine: Using SSH client type: native
I0214 21:51:19.658770 290030 main.go:141] libmachine: &{{{<nil> 0 [] [] []} docker [0x865ca0] 0x868980 <nil> [] 0s} 192.168.72.19 22 <nil> <nil>}
I0214 21:51:19.658789 290030 main.go:141] libmachine: About to run SSH command:
sudo mkdir -p /etc/sysconfig && printf %s "
CRIO_MINIKUBE_OPTIONS='--insecure-registry 10.96.0.0/12 '
" | sudo tee /etc/sysconfig/crio.minikube && sudo systemctl restart crio
I0214 21:51:19.895793 290030 main.go:141] libmachine: SSH cmd err, output: <nil>:
CRIO_MINIKUBE_OPTIONS='--insecure-registry 10.96.0.0/12 '
I0214 21:51:19.895830 290030 main.go:141] libmachine: Checking connection to Docker...
I0214 21:51:19.895843 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetURL
I0214 21:51:19.897101 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | using libvirt version 6000000
I0214 21:51:19.899085 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:19.899443 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:6d:30:ba", ip: ""} in network mk-old-k8s-version-201745: {Iface:virbr4 ExpiryTime:2025-02-14 22:51:10 +0000 UTC Type:0 Mac:52:54:00:6d:30:ba Iaid: IPaddr:192.168.72.19 Prefix:24 Hostname:old-k8s-version-201745 Clientid:01:52:54:00:6d:30:ba}
I0214 21:51:19.899474 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined IP address 192.168.72.19 and MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:19.899641 290030 main.go:141] libmachine: Docker is up and running!
I0214 21:51:19.899659 290030 main.go:141] libmachine: Reticulating splines...
I0214 21:51:19.899668 290030 client.go:171] duration metric: took 24.516107336s to LocalClient.Create
I0214 21:51:19.899696 290030 start.go:167] duration metric: took 24.516190058s to libmachine.API.Create "old-k8s-version-201745"
I0214 21:51:19.899707 290030 start.go:293] postStartSetup for "old-k8s-version-201745" (driver="kvm2")
I0214 21:51:19.899716 290030 start.go:322] creating required directories: [/etc/kubernetes/addons /etc/kubernetes/manifests /var/tmp/minikube /var/lib/minikube /var/lib/minikube/certs /var/lib/minikube/images /var/lib/minikube/binaries /tmp/gvisor /usr/share/ca-certificates /etc/ssl/certs]
I0214 21:51:19.899733 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .DriverName
I0214 21:51:19.899970 290030 ssh_runner.go:195] Run: sudo mkdir -p /etc/kubernetes/addons /etc/kubernetes/manifests /var/tmp/minikube /var/lib/minikube /var/lib/minikube/certs /var/lib/minikube/images /var/lib/minikube/binaries /tmp/gvisor /usr/share/ca-certificates /etc/ssl/certs
I0214 21:51:19.899997 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHHostname
I0214 21:51:19.901854 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:19.902204 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:6d:30:ba", ip: ""} in network mk-old-k8s-version-201745: {Iface:virbr4 ExpiryTime:2025-02-14 22:51:10 +0000 UTC Type:0 Mac:52:54:00:6d:30:ba Iaid: IPaddr:192.168.72.19 Prefix:24 Hostname:old-k8s-version-201745 Clientid:01:52:54:00:6d:30:ba}
I0214 21:51:19.902252 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined IP address 192.168.72.19 and MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:19.902409 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHPort
I0214 21:51:19.902568 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHKeyPath
I0214 21:51:19.902752 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHUsername
I0214 21:51:19.902925 290030 sshutil.go:53] new ssh client: &{IP:192.168.72.19 Port:22 SSHKeyPath:/home/jenkins/minikube-integration/20315-243456/.minikube/machines/old-k8s-version-201745/id_rsa Username:docker}
I0214 21:51:19.988715 290030 ssh_runner.go:195] Run: cat /etc/os-release
I0214 21:51:19.992916 290030 info.go:137] Remote host: Buildroot 2023.02.9
I0214 21:51:19.992942 290030 filesync.go:126] Scanning /home/jenkins/minikube-integration/20315-243456/.minikube/addons for local assets ...
I0214 21:51:19.992999 290030 filesync.go:126] Scanning /home/jenkins/minikube-integration/20315-243456/.minikube/files for local assets ...
I0214 21:51:19.993102 290030 filesync.go:149] local asset: /home/jenkins/minikube-integration/20315-243456/.minikube/files/etc/ssl/certs/2507832.pem -> 2507832.pem in /etc/ssl/certs
I0214 21:51:19.993218 290030 ssh_runner.go:195] Run: sudo mkdir -p /etc/ssl/certs
I0214 21:51:20.002821 290030 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20315-243456/.minikube/files/etc/ssl/certs/2507832.pem --> /etc/ssl/certs/2507832.pem (1708 bytes)
I0214 21:51:20.027189 290030 start.go:296] duration metric: took 127.471428ms for postStartSetup
I0214 21:51:20.027234 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetConfigRaw
I0214 21:51:20.027754 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetIP
I0214 21:51:20.030174 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:20.030496 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:6d:30:ba", ip: ""} in network mk-old-k8s-version-201745: {Iface:virbr4 ExpiryTime:2025-02-14 22:51:10 +0000 UTC Type:0 Mac:52:54:00:6d:30:ba Iaid: IPaddr:192.168.72.19 Prefix:24 Hostname:old-k8s-version-201745 Clientid:01:52:54:00:6d:30:ba}
I0214 21:51:20.030541 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined IP address 192.168.72.19 and MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:20.030800 290030 profile.go:143] Saving config to /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/old-k8s-version-201745/config.json ...
I0214 21:51:20.031021 290030 start.go:128] duration metric: took 24.667536425s to createHost
I0214 21:51:20.031048 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHHostname
I0214 21:51:20.033286 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:20.033584 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:6d:30:ba", ip: ""} in network mk-old-k8s-version-201745: {Iface:virbr4 ExpiryTime:2025-02-14 22:51:10 +0000 UTC Type:0 Mac:52:54:00:6d:30:ba Iaid: IPaddr:192.168.72.19 Prefix:24 Hostname:old-k8s-version-201745 Clientid:01:52:54:00:6d:30:ba}
I0214 21:51:20.033612 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined IP address 192.168.72.19 and MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:20.033720 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHPort
I0214 21:51:20.033920 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHKeyPath
I0214 21:51:20.034081 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHKeyPath
I0214 21:51:20.034221 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHUsername
I0214 21:51:20.034383 290030 main.go:141] libmachine: Using SSH client type: native
I0214 21:51:20.034560 290030 main.go:141] libmachine: &{{{<nil> 0 [] [] []} docker [0x865ca0] 0x868980 <nil> [] 0s} 192.168.72.19 22 <nil> <nil>}
I0214 21:51:20.034571 290030 main.go:141] libmachine: About to run SSH command:
date +%s.%N
I0214 21:51:20.146699 290030 main.go:141] libmachine: SSH cmd err, output: <nil>: 1739569880.118420137
I0214 21:51:20.146719 290030 fix.go:216] guest clock: 1739569880.118420137
I0214 21:51:20.146726 290030 fix.go:229] Guest: 2025-02-14 21:51:20.118420137 +0000 UTC Remote: 2025-02-14 21:51:20.031034691 +0000 UTC m=+89.511546951 (delta=87.385446ms)
I0214 21:51:20.146742 290030 fix.go:200] guest clock delta is within tolerance: 87.385446ms
I0214 21:51:20.146747 290030 start.go:83] releasing machines lock for "old-k8s-version-201745", held for 24.783455513s
I0214 21:51:20.146767 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .DriverName
I0214 21:51:20.146964 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetIP
I0214 21:51:20.149585 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:20.149939 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:6d:30:ba", ip: ""} in network mk-old-k8s-version-201745: {Iface:virbr4 ExpiryTime:2025-02-14 22:51:10 +0000 UTC Type:0 Mac:52:54:00:6d:30:ba Iaid: IPaddr:192.168.72.19 Prefix:24 Hostname:old-k8s-version-201745 Clientid:01:52:54:00:6d:30:ba}
I0214 21:51:20.149964 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined IP address 192.168.72.19 and MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:20.150137 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .DriverName
I0214 21:51:20.150597 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .DriverName
I0214 21:51:20.150786 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .DriverName
I0214 21:51:20.150893 290030 ssh_runner.go:195] Run: curl -sS -m 2 https://registry.k8s.io/
I0214 21:51:20.150936 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHHostname
I0214 21:51:20.151011 290030 ssh_runner.go:195] Run: cat /version.json
I0214 21:51:20.151035 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHHostname
I0214 21:51:20.153637 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:20.153678 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:20.153993 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:6d:30:ba", ip: ""} in network mk-old-k8s-version-201745: {Iface:virbr4 ExpiryTime:2025-02-14 22:51:10 +0000 UTC Type:0 Mac:52:54:00:6d:30:ba Iaid: IPaddr:192.168.72.19 Prefix:24 Hostname:old-k8s-version-201745 Clientid:01:52:54:00:6d:30:ba}
I0214 21:51:20.154014 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined IP address 192.168.72.19 and MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:20.154038 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:6d:30:ba", ip: ""} in network mk-old-k8s-version-201745: {Iface:virbr4 ExpiryTime:2025-02-14 22:51:10 +0000 UTC Type:0 Mac:52:54:00:6d:30:ba Iaid: IPaddr:192.168.72.19 Prefix:24 Hostname:old-k8s-version-201745 Clientid:01:52:54:00:6d:30:ba}
I0214 21:51:20.154055 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined IP address 192.168.72.19 and MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:20.154276 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHPort
I0214 21:51:20.154357 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHPort
I0214 21:51:20.154439 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHKeyPath
I0214 21:51:20.154495 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHKeyPath
I0214 21:51:20.154585 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHUsername
I0214 21:51:20.154643 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetSSHUsername
I0214 21:51:20.154683 290030 sshutil.go:53] new ssh client: &{IP:192.168.72.19 Port:22 SSHKeyPath:/home/jenkins/minikube-integration/20315-243456/.minikube/machines/old-k8s-version-201745/id_rsa Username:docker}
I0214 21:51:20.154998 290030 sshutil.go:53] new ssh client: &{IP:192.168.72.19 Port:22 SSHKeyPath:/home/jenkins/minikube-integration/20315-243456/.minikube/machines/old-k8s-version-201745/id_rsa Username:docker}
I0214 21:51:20.259516 290030 ssh_runner.go:195] Run: systemctl --version
I0214 21:51:20.265435 290030 ssh_runner.go:195] Run: sudo sh -c "podman version >/dev/null"
I0214 21:51:20.423713 290030 ssh_runner.go:195] Run: sh -c "stat /etc/cni/net.d/*loopback.conf*"
W0214 21:51:20.430194 290030 cni.go:209] loopback cni configuration skipped: "/etc/cni/net.d/*loopback.conf*" not found
I0214 21:51:20.430249 290030 ssh_runner.go:195] Run: sudo find /etc/cni/net.d -maxdepth 1 -type f ( ( -name *bridge* -or -name *podman* ) -and -not -name *.mk_disabled ) -printf "%p, " -exec sh -c "sudo mv {} {}.mk_disabled" ;
I0214 21:51:20.447320 290030 cni.go:262] disabled [/etc/cni/net.d/87-podman-bridge.conflist] bridge cni config(s)
I0214 21:51:20.447350 290030 start.go:495] detecting cgroup driver to use...
I0214 21:51:20.447403 290030 ssh_runner.go:195] Run: sudo systemctl stop -f containerd
I0214 21:51:20.463539 290030 ssh_runner.go:195] Run: sudo systemctl is-active --quiet service containerd
I0214 21:51:20.477217 290030 docker.go:217] disabling cri-docker service (if available) ...
I0214 21:51:20.477295 290030 ssh_runner.go:195] Run: sudo systemctl stop -f cri-docker.socket
I0214 21:51:20.490458 290030 ssh_runner.go:195] Run: sudo systemctl stop -f cri-docker.service
I0214 21:51:20.506265 290030 ssh_runner.go:195] Run: sudo systemctl disable cri-docker.socket
I0214 21:51:20.635362 290030 ssh_runner.go:195] Run: sudo systemctl mask cri-docker.service
I0214 21:51:20.791913 290030 docker.go:233] disabling docker service ...
I0214 21:51:20.791970 290030 ssh_runner.go:195] Run: sudo systemctl stop -f docker.socket
I0214 21:51:20.808889 290030 ssh_runner.go:195] Run: sudo systemctl stop -f docker.service
I0214 21:51:20.822017 290030 ssh_runner.go:195] Run: sudo systemctl disable docker.socket
I0214 21:51:20.944211 290030 ssh_runner.go:195] Run: sudo systemctl mask docker.service
I0214 21:51:21.080254 290030 ssh_runner.go:195] Run: sudo systemctl is-active --quiet service docker
I0214 21:51:21.095875 290030 ssh_runner.go:195] Run: /bin/bash -c "sudo mkdir -p /etc && printf %s "runtime-endpoint: unix:///var/run/crio/crio.sock
" | sudo tee /etc/crictl.yaml"
I0214 21:51:21.114491 290030 crio.go:59] configure cri-o to use "registry.k8s.io/pause:3.2" pause image...
I0214 21:51:21.114553 290030 ssh_runner.go:195] Run: sh -c "sudo sed -i 's|^.*pause_image = .*$|pause_image = "registry.k8s.io/pause:3.2"|' /etc/crio/crio.conf.d/02-crio.conf"
I0214 21:51:21.125025 290030 crio.go:70] configuring cri-o to use "cgroupfs" as cgroup driver...
I0214 21:51:21.125074 290030 ssh_runner.go:195] Run: sh -c "sudo sed -i 's|^.*cgroup_manager = .*$|cgroup_manager = "cgroupfs"|' /etc/crio/crio.conf.d/02-crio.conf"
I0214 21:51:21.135881 290030 ssh_runner.go:195] Run: sh -c "sudo sed -i '/conmon_cgroup = .*/d' /etc/crio/crio.conf.d/02-crio.conf"
I0214 21:51:21.146571 290030 ssh_runner.go:195] Run: sh -c "sudo sed -i '/cgroup_manager = .*/a conmon_cgroup = "pod"' /etc/crio/crio.conf.d/02-crio.conf"
I0214 21:51:21.156909 290030 ssh_runner.go:195] Run: sh -c "sudo rm -rf /etc/cni/net.mk"
I0214 21:51:21.167466 290030 ssh_runner.go:195] Run: sudo sysctl net.bridge.bridge-nf-call-iptables
I0214 21:51:21.176847 290030 crio.go:166] couldn't verify netfilter by "sudo sysctl net.bridge.bridge-nf-call-iptables" which might be okay. error: sudo sysctl net.bridge.bridge-nf-call-iptables: Process exited with status 255
stdout:
stderr:
sysctl: cannot stat /proc/sys/net/bridge/bridge-nf-call-iptables: No such file or directory
I0214 21:51:21.176902 290030 ssh_runner.go:195] Run: sudo modprobe br_netfilter
I0214 21:51:21.189597 290030 ssh_runner.go:195] Run: sudo sh -c "echo 1 > /proc/sys/net/ipv4/ip_forward"
I0214 21:51:21.198779 290030 ssh_runner.go:195] Run: sudo systemctl daemon-reload
I0214 21:51:21.311520 290030 ssh_runner.go:195] Run: sudo systemctl restart crio
I0214 21:51:21.406134 290030 start.go:542] Will wait 60s for socket path /var/run/crio/crio.sock
I0214 21:51:21.406221 290030 ssh_runner.go:195] Run: stat /var/run/crio/crio.sock
I0214 21:51:21.410963 290030 start.go:563] Will wait 60s for crictl version
I0214 21:51:21.411013 290030 ssh_runner.go:195] Run: which crictl
I0214 21:51:21.414903 290030 ssh_runner.go:195] Run: sudo /usr/bin/crictl version
I0214 21:51:21.454276 290030 start.go:579] Version: 0.1.0
RuntimeName: cri-o
RuntimeVersion: 1.29.1
RuntimeApiVersion: v1
I0214 21:51:21.454366 290030 ssh_runner.go:195] Run: crio --version
I0214 21:51:21.481275 290030 ssh_runner.go:195] Run: crio --version
I0214 21:51:21.509347 290030 out.go:177] * Preparing Kubernetes v1.20.0 on CRI-O 1.29.1 ...
I0214 21:51:21.510550 290030 main.go:141] libmachine: (old-k8s-version-201745) Calling .GetIP
I0214 21:51:21.512928 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:21.513300 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:6d:30:ba", ip: ""} in network mk-old-k8s-version-201745: {Iface:virbr4 ExpiryTime:2025-02-14 22:51:10 +0000 UTC Type:0 Mac:52:54:00:6d:30:ba Iaid: IPaddr:192.168.72.19 Prefix:24 Hostname:old-k8s-version-201745 Clientid:01:52:54:00:6d:30:ba}
I0214 21:51:21.513329 290030 main.go:141] libmachine: (old-k8s-version-201745) DBG | domain old-k8s-version-201745 has defined IP address 192.168.72.19 and MAC address 52:54:00:6d:30:ba in network mk-old-k8s-version-201745
I0214 21:51:21.513550 290030 ssh_runner.go:195] Run: grep 192.168.72.1 host.minikube.internal$ /etc/hosts
I0214 21:51:21.517441 290030 ssh_runner.go:195] Run: /bin/bash -c "{ grep -v $'\thost.minikube.internal$' "/etc/hosts"; echo "192.168.72.1 host.minikube.internal"; } > /tmp/h.$$; sudo cp /tmp/h.$$ "/etc/hosts""
I0214 21:51:21.529465 290030 kubeadm.go:875] updating cluster {Name:old-k8s-version-201745 KeepContext:false EmbedCerts:false MinikubeISO:https://storage.googleapis.com/minikube/iso/minikube-v1.35.0-amd64.iso KicBaseImage:gcr.io/k8s-minikube/kicbase-builds:v0.0.46-1739182054-20387@sha256:3788b0691001f3da958b3956b3e6c1d1db8535d5286bd2e096e6e75dc609dbad Memory:2200 CPUs:2 DiskSize:20000 Driver:kvm2 HyperkitVpnKitSock: HyperkitVSockPorts:[] DockerEnv:[] ContainerVolumeMounts:[] InsecureRegistry:[] RegistryMirror:[] HostOnlyCIDR:192.168.59.1/24 HypervVirtualSwitch: HypervUseExternalSwitch:false HypervExternalAdapter: KVMNetwork:default KVMQemuURI:qemu:///system KVMGPU:false KVMHidden:false KVMNUMACount:1 APIServerPort:8443 DockerOpt:[] DisableDriverMounts:true NFSShare:[] NFSSharesRoot:/nfsshares UUID: NoVTXCheck:false DNSProxy:false HostDNSResolver:true HostOnlyNicType:virtio NatNicType:virtio SSHIPAddress: SSHUser:root SSHKey: SSHPort:22 KubernetesConfig:{KubernetesVersion:v1.20.0 ClusterName:old-k8s-
version-201745 Namespace:default APIServerHAVIP: APIServerName:minikubeCA APIServerNames:[] APIServerIPs:[] DNSDomain:cluster.local ContainerRuntime:crio CRISocket: NetworkPlugin:cni FeatureGates: ServiceCIDR:10.96.0.0/12 ImageRepository: LoadBalancerStartIP: LoadBalancerEndIP: CustomIngressCert: RegistryAliases: ExtraOptions:[] ShouldLoadCachedImages:true EnableDefaultCNI:false CNI:} Nodes:[{Name: IP:192.168.72.19 Port:8443 KubernetesVersion:v1.20.0 ContainerRuntime:crio ControlPlane:true Worker:true}] Addons:map[] CustomAddonImages:map[] CustomAddonRegistries:map[] VerifyComponents:map[apiserver:true apps_running:true default_sa:true extra:true kubelet:true node_ready:true system_pods:true] StartHostTimeout:6m0s ScheduledStop:<nil> ExposedPorts:[] ListenAddress: Network: Subnet: MultiNodeRequested:false ExtraDisks:0 CertExpiration:26280h0m0s Mount:false MountString:/home/jenkins:/minikube-host Mount9PVersion:9p2000.L MountGID:docker MountIP: MountMSize:262144 MountOptions:[] MountPort:0 MountType:9p MountUI
D:docker BinaryMirror: DisableOptimizations:false DisableMetrics:false CustomQemuFirmwarePath: SocketVMnetClientPath: SocketVMnetPath: StaticIP: SSHAuthSock: SSHAgentPID:0 GPUs: AutoPauseInterval:1m0s} ...
I0214 21:51:21.529594 290030 preload.go:131] Checking if preload exists for k8s version v1.20.0 and runtime crio
I0214 21:51:21.529640 290030 ssh_runner.go:195] Run: sudo crictl images --output json
I0214 21:51:21.560058 290030 crio.go:510] couldn't find preloaded image for "registry.k8s.io/kube-apiserver:v1.20.0". assuming images are not preloaded.
I0214 21:51:21.560112 290030 ssh_runner.go:195] Run: which lz4
I0214 21:51:21.563873 290030 ssh_runner.go:195] Run: stat -c "%s %y" /preloaded.tar.lz4
I0214 21:51:21.567845 290030 ssh_runner.go:352] existence check for /preloaded.tar.lz4: stat -c "%s %y" /preloaded.tar.lz4: Process exited with status 1
stdout:
stderr:
stat: cannot statx '/preloaded.tar.lz4': No such file or directory
I0214 21:51:21.567874 290030 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20315-243456/.minikube/cache/preloaded-tarball/preloaded-images-k8s-v18-v1.20.0-cri-o-overlay-amd64.tar.lz4 --> /preloaded.tar.lz4 (473237281 bytes)
I0214 21:51:23.150723 290030 crio.go:462] duration metric: took 1.586877998s to copy over tarball
I0214 21:51:23.150796 290030 ssh_runner.go:195] Run: sudo tar --xattrs --xattrs-include security.capability -I lz4 -C /var -xf /preloaded.tar.lz4
I0214 21:51:25.603024 290030 ssh_runner.go:235] Completed: sudo tar --xattrs --xattrs-include security.capability -I lz4 -C /var -xf /preloaded.tar.lz4: (2.452191708s)
I0214 21:51:25.603059 290030 crio.go:469] duration metric: took 2.452307853s to extract the tarball
I0214 21:51:25.603069 290030 ssh_runner.go:146] rm: /preloaded.tar.lz4
I0214 21:51:25.647042 290030 ssh_runner.go:195] Run: sudo crictl images --output json
I0214 21:51:25.691327 290030 crio.go:510] couldn't find preloaded image for "registry.k8s.io/kube-apiserver:v1.20.0". assuming images are not preloaded.
I0214 21:51:25.691354 290030 cache_images.go:88] LoadCachedImages start: [registry.k8s.io/kube-apiserver:v1.20.0 registry.k8s.io/kube-controller-manager:v1.20.0 registry.k8s.io/kube-scheduler:v1.20.0 registry.k8s.io/kube-proxy:v1.20.0 registry.k8s.io/pause:3.2 registry.k8s.io/etcd:3.4.13-0 registry.k8s.io/coredns:1.7.0 gcr.io/k8s-minikube/storage-provisioner:v5]
I0214 21:51:25.691442 290030 image.go:135] retrieving image: gcr.io/k8s-minikube/storage-provisioner:v5
I0214 21:51:25.691458 290030 image.go:135] retrieving image: registry.k8s.io/kube-proxy:v1.20.0
I0214 21:51:25.691475 290030 image.go:135] retrieving image: registry.k8s.io/pause:3.2
I0214 21:51:25.691483 290030 image.go:135] retrieving image: registry.k8s.io/kube-apiserver:v1.20.0
I0214 21:51:25.691465 290030 image.go:135] retrieving image: registry.k8s.io/kube-controller-manager:v1.20.0
I0214 21:51:25.691449 290030 image.go:135] retrieving image: registry.k8s.io/etcd:3.4.13-0
I0214 21:51:25.691546 290030 image.go:135] retrieving image: registry.k8s.io/coredns:1.7.0
I0214 21:51:25.691570 290030 image.go:135] retrieving image: registry.k8s.io/kube-scheduler:v1.20.0
I0214 21:51:25.693361 290030 image.go:178] daemon lookup for registry.k8s.io/kube-proxy:v1.20.0: Error response from daemon: No such image: registry.k8s.io/kube-proxy:v1.20.0
I0214 21:51:25.693464 290030 image.go:178] daemon lookup for registry.k8s.io/kube-scheduler:v1.20.0: Error response from daemon: No such image: registry.k8s.io/kube-scheduler:v1.20.0
I0214 21:51:25.693499 290030 image.go:178] daemon lookup for gcr.io/k8s-minikube/storage-provisioner:v5: Error response from daemon: No such image: gcr.io/k8s-minikube/storage-provisioner:v5
I0214 21:51:25.693511 290030 image.go:178] daemon lookup for registry.k8s.io/kube-apiserver:v1.20.0: Error response from daemon: No such image: registry.k8s.io/kube-apiserver:v1.20.0
I0214 21:51:25.693366 290030 image.go:178] daemon lookup for registry.k8s.io/etcd:3.4.13-0: Error response from daemon: No such image: registry.k8s.io/etcd:3.4.13-0
I0214 21:51:25.693788 290030 image.go:178] daemon lookup for registry.k8s.io/kube-controller-manager:v1.20.0: Error response from daemon: No such image: registry.k8s.io/kube-controller-manager:v1.20.0
I0214 21:51:25.694029 290030 image.go:178] daemon lookup for registry.k8s.io/coredns:1.7.0: Error response from daemon: No such image: registry.k8s.io/coredns:1.7.0
I0214 21:51:25.694062 290030 image.go:178] daemon lookup for registry.k8s.io/pause:3.2: Error response from daemon: No such image: registry.k8s.io/pause:3.2
I0214 21:51:25.846856 290030 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} registry.k8s.io/etcd:3.4.13-0
I0214 21:51:25.857207 290030 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} registry.k8s.io/kube-scheduler:v1.20.0
I0214 21:51:25.858123 290030 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} registry.k8s.io/kube-proxy:v1.20.0
I0214 21:51:25.868799 290030 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} registry.k8s.io/kube-apiserver:v1.20.0
I0214 21:51:25.871190 290030 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} registry.k8s.io/coredns:1.7.0
I0214 21:51:25.883774 290030 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} registry.k8s.io/pause:3.2
I0214 21:51:25.890757 290030 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} registry.k8s.io/kube-controller-manager:v1.20.0
I0214 21:51:25.937841 290030 cache_images.go:116] "registry.k8s.io/etcd:3.4.13-0" needs transfer: "registry.k8s.io/etcd:3.4.13-0" does not exist at hash "0369cf4303ffdb467dc219990960a9baa8512a54b0ad9283eaf55bd6c0adb934" in container runtime
I0214 21:51:25.937904 290030 cri.go:218] Removing image: registry.k8s.io/etcd:3.4.13-0
I0214 21:51:25.937955 290030 ssh_runner.go:195] Run: which crictl
I0214 21:51:25.974145 290030 cache_images.go:116] "registry.k8s.io/kube-proxy:v1.20.0" needs transfer: "registry.k8s.io/kube-proxy:v1.20.0" does not exist at hash "10cc881966cfd9287656c2fce1f144625602653d1e8b011487a7a71feb100bdc" in container runtime
I0214 21:51:25.974181 290030 cri.go:218] Removing image: registry.k8s.io/kube-proxy:v1.20.0
I0214 21:51:25.974191 290030 cache_images.go:116] "registry.k8s.io/kube-scheduler:v1.20.0" needs transfer: "registry.k8s.io/kube-scheduler:v1.20.0" does not exist at hash "3138b6e3d471224fd516f758f3b53309219bcb6824e07686b3cd60d78012c899" in container runtime
I0214 21:51:25.974225 290030 ssh_runner.go:195] Run: which crictl
I0214 21:51:25.974229 290030 cri.go:218] Removing image: registry.k8s.io/kube-scheduler:v1.20.0
I0214 21:51:25.974271 290030 ssh_runner.go:195] Run: which crictl
I0214 21:51:26.019744 290030 cache_images.go:116] "registry.k8s.io/kube-apiserver:v1.20.0" needs transfer: "registry.k8s.io/kube-apiserver:v1.20.0" does not exist at hash "ca9843d3b545457f24b012d6d579ba85f132f2406aa171ad84d53caa55e5de99" in container runtime
I0214 21:51:26.019798 290030 cri.go:218] Removing image: registry.k8s.io/kube-apiserver:v1.20.0
I0214 21:51:26.019862 290030 ssh_runner.go:195] Run: which crictl
I0214 21:51:26.025283 290030 cache_images.go:116] "registry.k8s.io/coredns:1.7.0" needs transfer: "registry.k8s.io/coredns:1.7.0" does not exist at hash "bfe3a36ebd2528b454be6aebece806db5b40407b833e2af9617bf39afaff8c16" in container runtime
I0214 21:51:26.025329 290030 cri.go:218] Removing image: registry.k8s.io/coredns:1.7.0
I0214 21:51:26.025381 290030 ssh_runner.go:195] Run: which crictl
I0214 21:51:26.033932 290030 cache_images.go:116] "registry.k8s.io/kube-controller-manager:v1.20.0" needs transfer: "registry.k8s.io/kube-controller-manager:v1.20.0" does not exist at hash "b9fa1895dcaa6d3dd241d6d9340e939ca30fc0946464ec9f205a8cbe738a8080" in container runtime
I0214 21:51:26.033957 290030 cache_images.go:116] "registry.k8s.io/pause:3.2" needs transfer: "registry.k8s.io/pause:3.2" does not exist at hash "80d28bedfe5dec59da9ebf8e6260224ac9008ab5c11dbbe16ee3ba3e4439ac2c" in container runtime
I0214 21:51:26.033973 290030 cri.go:218] Removing image: registry.k8s.io/kube-controller-manager:v1.20.0
I0214 21:51:26.033978 290030 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/etcd:3.4.13-0
I0214 21:51:26.033989 290030 cri.go:218] Removing image: registry.k8s.io/pause:3.2
I0214 21:51:26.034010 290030 ssh_runner.go:195] Run: which crictl
I0214 21:51:26.034028 290030 ssh_runner.go:195] Run: which crictl
I0214 21:51:26.034066 290030 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-scheduler:v1.20.0
I0214 21:51:26.034102 290030 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-apiserver:v1.20.0
I0214 21:51:26.034116 290030 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/coredns:1.7.0
I0214 21:51:26.034080 290030 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-proxy:v1.20.0
I0214 21:51:26.112992 290030 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/etcd:3.4.13-0
I0214 21:51:26.160461 290030 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-proxy:v1.20.0
I0214 21:51:26.160467 290030 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-controller-manager:v1.20.0
I0214 21:51:26.163253 290030 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/coredns:1.7.0
I0214 21:51:26.163321 290030 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-apiserver:v1.20.0
I0214 21:51:26.163352 290030 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/pause:3.2
I0214 21:51:26.163369 290030 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-scheduler:v1.20.0
I0214 21:51:26.215854 290030 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/etcd:3.4.13-0
I0214 21:51:26.305663 290030 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-controller-manager:v1.20.0
I0214 21:51:26.325715 290030 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-apiserver:v1.20.0
I0214 21:51:26.325765 290030 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/pause:3.2
I0214 21:51:26.325778 290030 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-proxy:v1.20.0
I0214 21:51:26.325715 290030 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/coredns:1.7.0
I0214 21:51:26.325778 290030 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-scheduler:v1.20.0
I0214 21:51:26.350427 290030 cache_images.go:289] Loading image from: /home/jenkins/minikube-integration/20315-243456/.minikube/cache/images/amd64/registry.k8s.io/etcd_3.4.13-0
I0214 21:51:26.489615 290030 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-controller-manager:v1.20.0
I0214 21:51:26.515867 290030 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/pause:3.2
I0214 21:51:26.515959 290030 cache_images.go:289] Loading image from: /home/jenkins/minikube-integration/20315-243456/.minikube/cache/images/amd64/registry.k8s.io/kube-apiserver_v1.20.0
I0214 21:51:26.515998 290030 cache_images.go:289] Loading image from: /home/jenkins/minikube-integration/20315-243456/.minikube/cache/images/amd64/registry.k8s.io/kube-scheduler_v1.20.0
I0214 21:51:26.516063 290030 cache_images.go:289] Loading image from: /home/jenkins/minikube-integration/20315-243456/.minikube/cache/images/amd64/registry.k8s.io/coredns_1.7.0
I0214 21:51:26.516087 290030 cache_images.go:289] Loading image from: /home/jenkins/minikube-integration/20315-243456/.minikube/cache/images/amd64/registry.k8s.io/kube-proxy_v1.20.0
I0214 21:51:26.536809 290030 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} gcr.io/k8s-minikube/storage-provisioner:v5
I0214 21:51:26.539975 290030 cache_images.go:289] Loading image from: /home/jenkins/minikube-integration/20315-243456/.minikube/cache/images/amd64/registry.k8s.io/kube-controller-manager_v1.20.0
I0214 21:51:26.574869 290030 cache_images.go:289] Loading image from: /home/jenkins/minikube-integration/20315-243456/.minikube/cache/images/amd64/registry.k8s.io/pause_3.2
I0214 21:51:26.696128 290030 cache_images.go:92] duration metric: took 1.004755714s to LoadCachedImages
W0214 21:51:26.696227 290030 out.go:270] X Unable to load cached images: LoadCachedImages: stat /home/jenkins/minikube-integration/20315-243456/.minikube/cache/images/amd64/registry.k8s.io/etcd_3.4.13-0: no such file or directory
X Unable to load cached images: LoadCachedImages: stat /home/jenkins/minikube-integration/20315-243456/.minikube/cache/images/amd64/registry.k8s.io/etcd_3.4.13-0: no such file or directory
I0214 21:51:26.696245 290030 kubeadm.go:926] updating node { 192.168.72.19 8443 v1.20.0 crio true true} ...
I0214 21:51:26.696373 290030 kubeadm.go:938] kubelet [Unit]
Wants=crio.service
[Service]
ExecStart=
ExecStart=/var/lib/minikube/binaries/v1.20.0/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --config=/var/lib/kubelet/config.yaml --container-runtime=remote --container-runtime-endpoint=unix:///var/run/crio/crio.sock --hostname-override=old-k8s-version-201745 --kubeconfig=/etc/kubernetes/kubelet.conf --network-plugin=cni --node-ip=192.168.72.19
[Install]
config:
{KubernetesVersion:v1.20.0 ClusterName:old-k8s-version-201745 Namespace:default APIServerHAVIP: APIServerName:minikubeCA APIServerNames:[] APIServerIPs:[] DNSDomain:cluster.local ContainerRuntime:crio CRISocket: NetworkPlugin:cni FeatureGates: ServiceCIDR:10.96.0.0/12 ImageRepository: LoadBalancerStartIP: LoadBalancerEndIP: CustomIngressCert: RegistryAliases: ExtraOptions:[] ShouldLoadCachedImages:true EnableDefaultCNI:false CNI:}
I0214 21:51:26.696466 290030 ssh_runner.go:195] Run: crio config
I0214 21:51:26.746613 290030 cni.go:84] Creating CNI manager for ""
I0214 21:51:26.746658 290030 cni.go:146] "kvm2" driver + "crio" runtime found, recommending bridge
I0214 21:51:26.746670 290030 kubeadm.go:84] Using pod CIDR: 10.244.0.0/16
I0214 21:51:26.746697 290030 kubeadm.go:189] kubeadm options: {CertDir:/var/lib/minikube/certs ServiceCIDR:10.96.0.0/12 PodSubnet:10.244.0.0/16 AdvertiseAddress:192.168.72.19 APIServerPort:8443 KubernetesVersion:v1.20.0 EtcdDataDir:/var/lib/minikube/etcd EtcdExtraArgs:map[] ClusterName:old-k8s-version-201745 NodeName:old-k8s-version-201745 DNSDomain:cluster.local CRISocket:/var/run/crio/crio.sock ImageRepository: ComponentOptions:[{Component:apiServer ExtraArgs:map[enable-admission-plugins:NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,NodeRestriction,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota] Pairs:map[certSANs:["127.0.0.1", "localhost", "192.168.72.19"]]} {Component:controllerManager ExtraArgs:map[allocate-node-cidrs:true leader-elect:false] Pairs:map[]} {Component:scheduler ExtraArgs:map[leader-elect:false] Pairs:map[]}] FeatureArgs:map[] NodeIP:192.168.72.19 CgroupDriver:cgroupfs ClientCAFile:/var/lib/minikube/certs/ca.crt Stati
cPodPath:/etc/kubernetes/manifests ControlPlaneAddress:control-plane.minikube.internal KubeProxyOptions:map[] ResolvConfSearchRegression:false KubeletConfigOpts:map[hairpinMode:hairpin-veth runtimeRequestTimeout:15m] PrependCriSocketUnix:false}
I0214 21:51:26.746885 290030 kubeadm.go:195] kubeadm config:
apiVersion: kubeadm.k8s.io/v1beta2
kind: InitConfiguration
localAPIEndpoint:
advertiseAddress: 192.168.72.19
bindPort: 8443
bootstrapTokens:
- groups:
- system:bootstrappers:kubeadm:default-node-token
ttl: 24h0m0s
usages:
- signing
- authentication
nodeRegistration:
criSocket: /var/run/crio/crio.sock
name: "old-k8s-version-201745"
kubeletExtraArgs:
node-ip: 192.168.72.19
taints: []
---
apiVersion: kubeadm.k8s.io/v1beta2
kind: ClusterConfiguration
apiServer:
certSANs: ["127.0.0.1", "localhost", "192.168.72.19"]
extraArgs:
enable-admission-plugins: "NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,NodeRestriction,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota"
controllerManager:
extraArgs:
allocate-node-cidrs: "true"
leader-elect: "false"
scheduler:
extraArgs:
leader-elect: "false"
certificatesDir: /var/lib/minikube/certs
clusterName: mk
controlPlaneEndpoint: control-plane.minikube.internal:8443
dns:
type: CoreDNS
etcd:
local:
dataDir: /var/lib/minikube/etcd
extraArgs:
proxy-refresh-interval: "70000"
kubernetesVersion: v1.20.0
networking:
dnsDomain: cluster.local
podSubnet: "10.244.0.0/16"
serviceSubnet: 10.96.0.0/12
---
apiVersion: kubelet.config.k8s.io/v1beta1
kind: KubeletConfiguration
authentication:
x509:
clientCAFile: /var/lib/minikube/certs/ca.crt
cgroupDriver: cgroupfs
hairpinMode: hairpin-veth
runtimeRequestTimeout: 15m
clusterDomain: "cluster.local"
# disable disk resource management by default
imageGCHighThresholdPercent: 100
evictionHard:
nodefs.available: "0%"
nodefs.inodesFree: "0%"
imagefs.available: "0%"
failSwapOn: false
staticPodPath: /etc/kubernetes/manifests
---
apiVersion: kubeproxy.config.k8s.io/v1alpha1
kind: KubeProxyConfiguration
clusterCIDR: "10.244.0.0/16"
metricsBindAddress: 0.0.0.0:10249
conntrack:
maxPerCore: 0
# Skip setting "net.netfilter.nf_conntrack_tcp_timeout_established"
tcpEstablishedTimeout: 0s
# Skip setting "net.netfilter.nf_conntrack_tcp_timeout_close"
tcpCloseWaitTimeout: 0s
I0214 21:51:26.746970 290030 ssh_runner.go:195] Run: sudo ls /var/lib/minikube/binaries/v1.20.0
I0214 21:51:26.757127 290030 binaries.go:44] Found k8s binaries, skipping transfer
I0214 21:51:26.757199 290030 ssh_runner.go:195] Run: sudo mkdir -p /etc/systemd/system/kubelet.service.d /lib/systemd/system /var/tmp/minikube
I0214 21:51:26.766779 290030 ssh_runner.go:362] scp memory --> /etc/systemd/system/kubelet.service.d/10-kubeadm.conf (429 bytes)
I0214 21:51:26.787809 290030 ssh_runner.go:362] scp memory --> /lib/systemd/system/kubelet.service (352 bytes)
I0214 21:51:26.805088 290030 ssh_runner.go:362] scp memory --> /var/tmp/minikube/kubeadm.yaml.new (2120 bytes)
I0214 21:51:26.824439 290030 ssh_runner.go:195] Run: grep 192.168.72.19 control-plane.minikube.internal$ /etc/hosts
I0214 21:51:26.828275 290030 ssh_runner.go:195] Run: /bin/bash -c "{ grep -v $'\tcontrol-plane.minikube.internal$' "/etc/hosts"; echo "192.168.72.19 control-plane.minikube.internal"; } > /tmp/h.$$; sudo cp /tmp/h.$$ "/etc/hosts""
I0214 21:51:26.840675 290030 ssh_runner.go:195] Run: sudo systemctl daemon-reload
I0214 21:51:26.964411 290030 ssh_runner.go:195] Run: sudo systemctl start kubelet
I0214 21:51:26.982471 290030 certs.go:68] Setting up /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/old-k8s-version-201745 for IP: 192.168.72.19
I0214 21:51:26.982493 290030 certs.go:194] generating shared ca certs ...
I0214 21:51:26.982513 290030 certs.go:226] acquiring lock for ca certs: {Name:mk43b22b1c0ea62ac748492a836a372fe73583cd Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0214 21:51:26.982702 290030 certs.go:235] skipping valid "minikubeCA" ca cert: /home/jenkins/minikube-integration/20315-243456/.minikube/ca.key
I0214 21:51:26.982762 290030 certs.go:235] skipping valid "proxyClientCA" ca cert: /home/jenkins/minikube-integration/20315-243456/.minikube/proxy-client-ca.key
I0214 21:51:26.982776 290030 certs.go:256] generating profile certs ...
I0214 21:51:26.982866 290030 certs.go:363] generating signed profile cert for "minikube-user": /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/old-k8s-version-201745/client.key
I0214 21:51:26.982883 290030 crypto.go:68] Generating cert /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/old-k8s-version-201745/client.crt with IP's: []
I0214 21:51:27.086210 290030 crypto.go:156] Writing cert to /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/old-k8s-version-201745/client.crt ...
I0214 21:51:27.086243 290030 lock.go:35] WriteFile acquiring /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/old-k8s-version-201745/client.crt: {Name:mk78690042ad4da1a6a4edca3f1fc615ab233f5a Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0214 21:51:27.086454 290030 crypto.go:164] Writing key to /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/old-k8s-version-201745/client.key ...
I0214 21:51:27.086476 290030 lock.go:35] WriteFile acquiring /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/old-k8s-version-201745/client.key: {Name:mk9dcc9f8bf351125336639900feaa5a54463656 Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0214 21:51:27.086614 290030 certs.go:363] generating signed profile cert for "minikube": /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/old-k8s-version-201745/apiserver.key.0d7fe282
I0214 21:51:27.086666 290030 crypto.go:68] Generating cert /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/old-k8s-version-201745/apiserver.crt.0d7fe282 with IP's: [10.96.0.1 127.0.0.1 10.0.0.1 192.168.72.19]
I0214 21:51:27.176437 290030 crypto.go:156] Writing cert to /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/old-k8s-version-201745/apiserver.crt.0d7fe282 ...
I0214 21:51:27.176465 290030 lock.go:35] WriteFile acquiring /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/old-k8s-version-201745/apiserver.crt.0d7fe282: {Name:mkbedbb12462578a35a6cf17b6a8d3bfc9a61c7a Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0214 21:51:27.183135 290030 crypto.go:164] Writing key to /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/old-k8s-version-201745/apiserver.key.0d7fe282 ...
I0214 21:51:27.183163 290030 lock.go:35] WriteFile acquiring /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/old-k8s-version-201745/apiserver.key.0d7fe282: {Name:mk8e3fd4279cbf58b4cf8bc88b52058b57b99cc0 Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0214 21:51:27.183287 290030 certs.go:381] copying /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/old-k8s-version-201745/apiserver.crt.0d7fe282 -> /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/old-k8s-version-201745/apiserver.crt
I0214 21:51:27.183414 290030 certs.go:385] copying /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/old-k8s-version-201745/apiserver.key.0d7fe282 -> /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/old-k8s-version-201745/apiserver.key
I0214 21:51:27.183509 290030 certs.go:363] generating signed profile cert for "aggregator": /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/old-k8s-version-201745/proxy-client.key
I0214 21:51:27.183532 290030 crypto.go:68] Generating cert /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/old-k8s-version-201745/proxy-client.crt with IP's: []
I0214 21:51:27.332957 290030 crypto.go:156] Writing cert to /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/old-k8s-version-201745/proxy-client.crt ...
I0214 21:51:27.332985 290030 lock.go:35] WriteFile acquiring /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/old-k8s-version-201745/proxy-client.crt: {Name:mk0521fddd5fd5b15f245469d92dd539e5ce995e Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0214 21:51:27.333186 290030 crypto.go:164] Writing key to /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/old-k8s-version-201745/proxy-client.key ...
I0214 21:51:27.333205 290030 lock.go:35] WriteFile acquiring /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/old-k8s-version-201745/proxy-client.key: {Name:mkb179c5d1b5603349d7002e5cbe42b54cae6bf8 Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0214 21:51:27.333437 290030 certs.go:484] found cert: /home/jenkins/minikube-integration/20315-243456/.minikube/certs/250783.pem (1338 bytes)
W0214 21:51:27.333494 290030 certs.go:480] ignoring /home/jenkins/minikube-integration/20315-243456/.minikube/certs/250783_empty.pem, impossibly tiny 0 bytes
I0214 21:51:27.333511 290030 certs.go:484] found cert: /home/jenkins/minikube-integration/20315-243456/.minikube/certs/ca-key.pem (1675 bytes)
I0214 21:51:27.333540 290030 certs.go:484] found cert: /home/jenkins/minikube-integration/20315-243456/.minikube/certs/ca.pem (1082 bytes)
I0214 21:51:27.333574 290030 certs.go:484] found cert: /home/jenkins/minikube-integration/20315-243456/.minikube/certs/cert.pem (1123 bytes)
I0214 21:51:27.333607 290030 certs.go:484] found cert: /home/jenkins/minikube-integration/20315-243456/.minikube/certs/key.pem (1675 bytes)
I0214 21:51:27.333661 290030 certs.go:484] found cert: /home/jenkins/minikube-integration/20315-243456/.minikube/files/etc/ssl/certs/2507832.pem (1708 bytes)
I0214 21:51:27.334378 290030 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20315-243456/.minikube/ca.crt --> /var/lib/minikube/certs/ca.crt (1111 bytes)
I0214 21:51:27.365750 290030 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20315-243456/.minikube/ca.key --> /var/lib/minikube/certs/ca.key (1675 bytes)
I0214 21:51:27.391666 290030 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20315-243456/.minikube/proxy-client-ca.crt --> /var/lib/minikube/certs/proxy-client-ca.crt (1119 bytes)
I0214 21:51:27.427686 290030 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20315-243456/.minikube/proxy-client-ca.key --> /var/lib/minikube/certs/proxy-client-ca.key (1675 bytes)
I0214 21:51:27.456842 290030 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/old-k8s-version-201745/apiserver.crt --> /var/lib/minikube/certs/apiserver.crt (1432 bytes)
I0214 21:51:27.488943 290030 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/old-k8s-version-201745/apiserver.key --> /var/lib/minikube/certs/apiserver.key (1675 bytes)
I0214 21:51:27.516957 290030 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/old-k8s-version-201745/proxy-client.crt --> /var/lib/minikube/certs/proxy-client.crt (1147 bytes)
I0214 21:51:27.542594 290030 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20315-243456/.minikube/profiles/old-k8s-version-201745/proxy-client.key --> /var/lib/minikube/certs/proxy-client.key (1675 bytes)
I0214 21:51:27.573435 290030 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20315-243456/.minikube/ca.crt --> /usr/share/ca-certificates/minikubeCA.pem (1111 bytes)
I0214 21:51:27.601362 290030 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20315-243456/.minikube/certs/250783.pem --> /usr/share/ca-certificates/250783.pem (1338 bytes)
I0214 21:51:27.626583 290030 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20315-243456/.minikube/files/etc/ssl/certs/2507832.pem --> /usr/share/ca-certificates/2507832.pem (1708 bytes)
I0214 21:51:27.653893 290030 ssh_runner.go:362] scp memory --> /var/lib/minikube/kubeconfig (738 bytes)
I0214 21:51:27.670757 290030 ssh_runner.go:195] Run: openssl version
I0214 21:51:27.676763 290030 ssh_runner.go:195] Run: sudo /bin/bash -c "test -s /usr/share/ca-certificates/250783.pem && ln -fs /usr/share/ca-certificates/250783.pem /etc/ssl/certs/250783.pem"
I0214 21:51:27.688401 290030 ssh_runner.go:195] Run: ls -la /usr/share/ca-certificates/250783.pem
I0214 21:51:27.692797 290030 certs.go:528] hashing: -rw-r--r-- 1 root root 1338 Feb 14 20:52 /usr/share/ca-certificates/250783.pem
I0214 21:51:27.692854 290030 ssh_runner.go:195] Run: openssl x509 -hash -noout -in /usr/share/ca-certificates/250783.pem
I0214 21:51:27.698895 290030 ssh_runner.go:195] Run: sudo /bin/bash -c "test -L /etc/ssl/certs/51391683.0 || ln -fs /etc/ssl/certs/250783.pem /etc/ssl/certs/51391683.0"
I0214 21:51:27.709384 290030 ssh_runner.go:195] Run: sudo /bin/bash -c "test -s /usr/share/ca-certificates/2507832.pem && ln -fs /usr/share/ca-certificates/2507832.pem /etc/ssl/certs/2507832.pem"
I0214 21:51:27.719630 290030 ssh_runner.go:195] Run: ls -la /usr/share/ca-certificates/2507832.pem
I0214 21:51:27.724214 290030 certs.go:528] hashing: -rw-r--r-- 1 root root 1708 Feb 14 20:52 /usr/share/ca-certificates/2507832.pem
I0214 21:51:27.724271 290030 ssh_runner.go:195] Run: openssl x509 -hash -noout -in /usr/share/ca-certificates/2507832.pem
I0214 21:51:27.729857 290030 ssh_runner.go:195] Run: sudo /bin/bash -c "test -L /etc/ssl/certs/3ec20f2e.0 || ln -fs /etc/ssl/certs/2507832.pem /etc/ssl/certs/3ec20f2e.0"
I0214 21:51:27.741344 290030 ssh_runner.go:195] Run: sudo /bin/bash -c "test -s /usr/share/ca-certificates/minikubeCA.pem && ln -fs /usr/share/ca-certificates/minikubeCA.pem /etc/ssl/certs/minikubeCA.pem"
I0214 21:51:27.752386 290030 ssh_runner.go:195] Run: ls -la /usr/share/ca-certificates/minikubeCA.pem
I0214 21:51:27.757249 290030 certs.go:528] hashing: -rw-r--r-- 1 root root 1111 Feb 14 20:45 /usr/share/ca-certificates/minikubeCA.pem
I0214 21:51:27.757294 290030 ssh_runner.go:195] Run: openssl x509 -hash -noout -in /usr/share/ca-certificates/minikubeCA.pem
I0214 21:51:27.763492 290030 ssh_runner.go:195] Run: sudo /bin/bash -c "test -L /etc/ssl/certs/b5213941.0 || ln -fs /etc/ssl/certs/minikubeCA.pem /etc/ssl/certs/b5213941.0"
I0214 21:51:27.774762 290030 ssh_runner.go:195] Run: stat /var/lib/minikube/certs/apiserver-kubelet-client.crt
I0214 21:51:27.779055 290030 certs.go:399] 'apiserver-kubelet-client' cert doesn't exist, likely first start: stat /var/lib/minikube/certs/apiserver-kubelet-client.crt: Process exited with status 1
stdout:
stderr:
stat: cannot statx '/var/lib/minikube/certs/apiserver-kubelet-client.crt': No such file or directory
I0214 21:51:27.779111 290030 kubeadm.go:392] StartCluster: {Name:old-k8s-version-201745 KeepContext:false EmbedCerts:false MinikubeISO:https://storage.googleapis.com/minikube/iso/minikube-v1.35.0-amd64.iso KicBaseImage:gcr.io/k8s-minikube/kicbase-builds:v0.0.46-1739182054-20387@sha256:3788b0691001f3da958b3956b3e6c1d1db8535d5286bd2e096e6e75dc609dbad Memory:2200 CPUs:2 DiskSize:20000 Driver:kvm2 HyperkitVpnKitSock: HyperkitVSockPorts:[] DockerEnv:[] ContainerVolumeMounts:[] InsecureRegistry:[] RegistryMirror:[] HostOnlyCIDR:192.168.59.1/24 HypervVirtualSwitch: HypervUseExternalSwitch:false HypervExternalAdapter: KVMNetwork:default KVMQemuURI:qemu:///system KVMGPU:false KVMHidden:false KVMNUMACount:1 APIServerPort:8443 DockerOpt:[] DisableDriverMounts:true NFSShare:[] NFSSharesRoot:/nfsshares UUID: NoVTXCheck:false DNSProxy:false HostDNSResolver:true HostOnlyNicType:virtio NatNicType:virtio SSHIPAddress: SSHUser:root SSHKey: SSHPort:22 KubernetesConfig:{KubernetesVersion:v1.20.0 ClusterName:old-k8s-ver
sion-201745 Namespace:default APIServerHAVIP: APIServerName:minikubeCA APIServerNames:[] APIServerIPs:[] DNSDomain:cluster.local ContainerRuntime:crio CRISocket: NetworkPlugin:cni FeatureGates: ServiceCIDR:10.96.0.0/12 ImageRepository: LoadBalancerStartIP: LoadBalancerEndIP: CustomIngressCert: RegistryAliases: ExtraOptions:[] ShouldLoadCachedImages:true EnableDefaultCNI:false CNI:} Nodes:[{Name: IP:192.168.72.19 Port:8443 KubernetesVersion:v1.20.0 ContainerRuntime:crio ControlPlane:true Worker:true}] Addons:map[] CustomAddonImages:map[] CustomAddonRegistries:map[] VerifyComponents:map[apiserver:true apps_running:true default_sa:true extra:true kubelet:true node_ready:true system_pods:true] StartHostTimeout:6m0s ScheduledStop:<nil> ExposedPorts:[] ListenAddress: Network: Subnet: MultiNodeRequested:false ExtraDisks:0 CertExpiration:26280h0m0s Mount:false MountString:/home/jenkins:/minikube-host Mount9PVersion:9p2000.L MountGID:docker MountIP: MountMSize:262144 MountOptions:[] MountPort:0 MountType:9p MountUID:d
ocker BinaryMirror: DisableOptimizations:false DisableMetrics:false CustomQemuFirmwarePath: SocketVMnetClientPath: SocketVMnetPath: StaticIP: SSHAuthSock: SSHAgentPID:0 GPUs: AutoPauseInterval:1m0s}
I0214 21:51:27.779208 290030 cri.go:54] listing CRI containers in root : {State:paused Name: Namespaces:[kube-system]}
I0214 21:51:27.779257 290030 ssh_runner.go:195] Run: sudo -s eval "crictl ps -a --quiet --label io.kubernetes.pod.namespace=kube-system"
I0214 21:51:27.837079 290030 cri.go:89] found id: ""
I0214 21:51:27.837150 290030 ssh_runner.go:195] Run: sudo ls /var/lib/kubelet/kubeadm-flags.env /var/lib/kubelet/config.yaml /var/lib/minikube/etcd
I0214 21:51:27.853732 290030 ssh_runner.go:195] Run: sudo cp /var/tmp/minikube/kubeadm.yaml.new /var/tmp/minikube/kubeadm.yaml
I0214 21:51:27.868300 290030 ssh_runner.go:195] Run: sudo ls -la /etc/kubernetes/admin.conf /etc/kubernetes/kubelet.conf /etc/kubernetes/controller-manager.conf /etc/kubernetes/scheduler.conf
I0214 21:51:27.879448 290030 kubeadm.go:155] config check failed, skipping stale config cleanup: sudo ls -la /etc/kubernetes/admin.conf /etc/kubernetes/kubelet.conf /etc/kubernetes/controller-manager.conf /etc/kubernetes/scheduler.conf: Process exited with status 2
stdout:
stderr:
ls: cannot access '/etc/kubernetes/admin.conf': No such file or directory
ls: cannot access '/etc/kubernetes/kubelet.conf': No such file or directory
ls: cannot access '/etc/kubernetes/controller-manager.conf': No such file or directory
ls: cannot access '/etc/kubernetes/scheduler.conf': No such file or directory
I0214 21:51:27.879473 290030 kubeadm.go:157] found existing configuration files:
I0214 21:51:27.879526 290030 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/admin.conf
I0214 21:51:27.889031 290030 kubeadm.go:163] "https://control-plane.minikube.internal:8443" may not be in /etc/kubernetes/admin.conf - will remove: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/admin.conf: Process exited with status 2
stdout:
stderr:
grep: /etc/kubernetes/admin.conf: No such file or directory
I0214 21:51:27.889088 290030 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/admin.conf
I0214 21:51:27.901374 290030 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/kubelet.conf
I0214 21:51:27.912717 290030 kubeadm.go:163] "https://control-plane.minikube.internal:8443" may not be in /etc/kubernetes/kubelet.conf - will remove: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/kubelet.conf: Process exited with status 2
stdout:
stderr:
grep: /etc/kubernetes/kubelet.conf: No such file or directory
I0214 21:51:27.912778 290030 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/kubelet.conf
I0214 21:51:27.924914 290030 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/controller-manager.conf
I0214 21:51:27.942213 290030 kubeadm.go:163] "https://control-plane.minikube.internal:8443" may not be in /etc/kubernetes/controller-manager.conf - will remove: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/controller-manager.conf: Process exited with status 2
stdout:
stderr:
grep: /etc/kubernetes/controller-manager.conf: No such file or directory
I0214 21:51:27.942284 290030 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/controller-manager.conf
I0214 21:51:27.959684 290030 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/scheduler.conf
I0214 21:51:27.969409 290030 kubeadm.go:163] "https://control-plane.minikube.internal:8443" may not be in /etc/kubernetes/scheduler.conf - will remove: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/scheduler.conf: Process exited with status 2
stdout:
stderr:
grep: /etc/kubernetes/scheduler.conf: No such file or directory
I0214 21:51:27.969462 290030 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/scheduler.conf
I0214 21:51:27.979150 290030 ssh_runner.go:286] Start: /bin/bash -c "sudo env PATH="/var/lib/minikube/binaries/v1.20.0:$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,NumCPU,Mem"
I0214 21:51:28.113879 290030 kubeadm.go:310] [init] Using Kubernetes version: v1.20.0
I0214 21:51:28.114157 290030 kubeadm.go:310] [preflight] Running pre-flight checks
I0214 21:51:28.275275 290030 kubeadm.go:310] [preflight] Pulling images required for setting up a Kubernetes cluster
I0214 21:51:28.275415 290030 kubeadm.go:310] [preflight] This might take a minute or two, depending on the speed of your internet connection
I0214 21:51:28.275590 290030 kubeadm.go:310] [preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
I0214 21:51:28.459073 290030 kubeadm.go:310] [certs] Using certificateDir folder "/var/lib/minikube/certs"
I0214 21:51:28.571529 290030 out.go:235] - Generating certificates and keys ...
I0214 21:51:28.571668 290030 kubeadm.go:310] [certs] Using existing ca certificate authority
I0214 21:51:28.571801 290030 kubeadm.go:310] [certs] Using existing apiserver certificate and key on disk
I0214 21:51:28.571917 290030 kubeadm.go:310] [certs] Generating "apiserver-kubelet-client" certificate and key
I0214 21:51:28.781276 290030 kubeadm.go:310] [certs] Generating "front-proxy-ca" certificate and key
I0214 21:51:28.889122 290030 kubeadm.go:310] [certs] Generating "front-proxy-client" certificate and key
I0214 21:51:29.037057 290030 kubeadm.go:310] [certs] Generating "etcd/ca" certificate and key
I0214 21:51:29.163037 290030 kubeadm.go:310] [certs] Generating "etcd/server" certificate and key
I0214 21:51:29.163491 290030 kubeadm.go:310] [certs] etcd/server serving cert is signed for DNS names [localhost old-k8s-version-201745] and IPs [192.168.72.19 127.0.0.1 ::1]
I0214 21:51:29.328250 290030 kubeadm.go:310] [certs] Generating "etcd/peer" certificate and key
I0214 21:51:29.328454 290030 kubeadm.go:310] [certs] etcd/peer serving cert is signed for DNS names [localhost old-k8s-version-201745] and IPs [192.168.72.19 127.0.0.1 ::1]
I0214 21:51:29.525978 290030 kubeadm.go:310] [certs] Generating "etcd/healthcheck-client" certificate and key
I0214 21:51:29.691207 290030 kubeadm.go:310] [certs] Generating "apiserver-etcd-client" certificate and key
I0214 21:51:29.820111 290030 kubeadm.go:310] [certs] Generating "sa" key and public key
I0214 21:51:29.820488 290030 kubeadm.go:310] [kubeconfig] Using kubeconfig folder "/etc/kubernetes"
I0214 21:51:29.977726 290030 kubeadm.go:310] [kubeconfig] Writing "admin.conf" kubeconfig file
I0214 21:51:30.129358 290030 kubeadm.go:310] [kubeconfig] Writing "kubelet.conf" kubeconfig file
I0214 21:51:30.278856 290030 kubeadm.go:310] [kubeconfig] Writing "controller-manager.conf" kubeconfig file
I0214 21:51:30.408865 290030 kubeadm.go:310] [kubeconfig] Writing "scheduler.conf" kubeconfig file
I0214 21:51:30.435199 290030 kubeadm.go:310] [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
I0214 21:51:30.436112 290030 kubeadm.go:310] [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
I0214 21:51:30.436182 290030 kubeadm.go:310] [kubelet-start] Starting the kubelet
I0214 21:51:30.584138 290030 kubeadm.go:310] [control-plane] Using manifest folder "/etc/kubernetes/manifests"
I0214 21:51:30.672210 290030 out.go:235] - Booting up control plane ...
I0214 21:51:30.672342 290030 kubeadm.go:310] [control-plane] Creating static Pod manifest for "kube-apiserver"
I0214 21:51:30.672469 290030 kubeadm.go:310] [control-plane] Creating static Pod manifest for "kube-controller-manager"
I0214 21:51:30.672596 290030 kubeadm.go:310] [control-plane] Creating static Pod manifest for "kube-scheduler"
I0214 21:51:30.672708 290030 kubeadm.go:310] [etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
I0214 21:51:30.672865 290030 kubeadm.go:310] [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
I0214 21:52:10.609271 290030 kubeadm.go:310] [kubelet-check] Initial timeout of 40s passed.
I0214 21:52:10.610103 290030 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0214 21:52:10.610376 290030 kubeadm.go:310] [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
I0214 21:52:15.610695 290030 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0214 21:52:15.610994 290030 kubeadm.go:310] [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
I0214 21:52:25.610563 290030 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0214 21:52:25.610936 290030 kubeadm.go:310] [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
I0214 21:52:45.609973 290030 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0214 21:52:45.610256 290030 kubeadm.go:310] [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
I0214 21:53:25.611196 290030 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0214 21:53:25.611464 290030 kubeadm.go:310] [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
I0214 21:53:25.611485 290030 kubeadm.go:310]
I0214 21:53:25.611526 290030 kubeadm.go:310] Unfortunately, an error has occurred:
I0214 21:53:25.611608 290030 kubeadm.go:310] timed out waiting for the condition
I0214 21:53:25.611626 290030 kubeadm.go:310]
I0214 21:53:25.611654 290030 kubeadm.go:310] This error is likely caused by:
I0214 21:53:25.611683 290030 kubeadm.go:310] - The kubelet is not running
I0214 21:53:25.611823 290030 kubeadm.go:310] - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
I0214 21:53:25.611835 290030 kubeadm.go:310]
I0214 21:53:25.611973 290030 kubeadm.go:310] If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
I0214 21:53:25.612027 290030 kubeadm.go:310] - 'systemctl status kubelet'
I0214 21:53:25.612072 290030 kubeadm.go:310] - 'journalctl -xeu kubelet'
I0214 21:53:25.612097 290030 kubeadm.go:310]
I0214 21:53:25.612292 290030 kubeadm.go:310] Additionally, a control plane component may have crashed or exited when started by the container runtime.
I0214 21:53:25.612412 290030 kubeadm.go:310] To troubleshoot, list all containers using your preferred container runtimes CLI.
I0214 21:53:25.612422 290030 kubeadm.go:310]
I0214 21:53:25.612535 290030 kubeadm.go:310] Here is one example how you may list all Kubernetes containers running in cri-o/containerd using crictl:
I0214 21:53:25.612653 290030 kubeadm.go:310] - 'crictl --runtime-endpoint /var/run/crio/crio.sock ps -a | grep kube | grep -v pause'
I0214 21:53:25.612760 290030 kubeadm.go:310] Once you have found the failing container, you can inspect its logs with:
I0214 21:53:25.612856 290030 kubeadm.go:310] - 'crictl --runtime-endpoint /var/run/crio/crio.sock logs CONTAINERID'
I0214 21:53:25.612867 290030 kubeadm.go:310]
I0214 21:53:25.613059 290030 kubeadm.go:310] [WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
I0214 21:53:25.613187 290030 kubeadm.go:310] error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
I0214 21:53:25.613306 290030 kubeadm.go:310] To see the stack trace of this error execute with --v=5 or higher
W0214 21:53:25.613482 290030 out.go:270] ! initialization failed, will try again: wait: /bin/bash -c "sudo env PATH="/var/lib/minikube/binaries/v1.20.0:$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,NumCPU,Mem": Process exited with status 1
stdout:
[init] Using Kubernetes version: v1.20.0
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[certs] Using certificateDir folder "/var/lib/minikube/certs"
[certs] Using existing ca certificate authority
[certs] Using existing apiserver certificate and key on disk
[certs] Generating "apiserver-kubelet-client" certificate and key
[certs] Generating "front-proxy-ca" certificate and key
[certs] Generating "front-proxy-client" certificate and key
[certs] Generating "etcd/ca" certificate and key
[certs] Generating "etcd/server" certificate and key
[certs] etcd/server serving cert is signed for DNS names [localhost old-k8s-version-201745] and IPs [192.168.72.19 127.0.0.1 ::1]
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [localhost old-k8s-version-201745] and IPs [192.168.72.19 127.0.0.1 ::1]
[certs] Generating "etcd/healthcheck-client" certificate and key
[certs] Generating "apiserver-etcd-client" certificate and key
[certs] Generating "sa" key and public key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
Unfortunately, an error has occurred:
timed out waiting for the condition
This error is likely caused by:
- The kubelet is not running
- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
- 'systemctl status kubelet'
- 'journalctl -xeu kubelet'
Additionally, a control plane component may have crashed or exited when started by the container runtime.
To troubleshoot, list all containers using your preferred container runtimes CLI.
Here is one example how you may list all Kubernetes containers running in cri-o/containerd using crictl:
- 'crictl --runtime-endpoint /var/run/crio/crio.sock ps -a | grep kube | grep -v pause'
Once you have found the failing container, you can inspect its logs with:
- 'crictl --runtime-endpoint /var/run/crio/crio.sock logs CONTAINERID'
stderr:
[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
To see the stack trace of this error execute with --v=5 or higher
! initialization failed, will try again: wait: /bin/bash -c "sudo env PATH="/var/lib/minikube/binaries/v1.20.0:$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,NumCPU,Mem": Process exited with status 1
stdout:
[init] Using Kubernetes version: v1.20.0
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[certs] Using certificateDir folder "/var/lib/minikube/certs"
[certs] Using existing ca certificate authority
[certs] Using existing apiserver certificate and key on disk
[certs] Generating "apiserver-kubelet-client" certificate and key
[certs] Generating "front-proxy-ca" certificate and key
[certs] Generating "front-proxy-client" certificate and key
[certs] Generating "etcd/ca" certificate and key
[certs] Generating "etcd/server" certificate and key
[certs] etcd/server serving cert is signed for DNS names [localhost old-k8s-version-201745] and IPs [192.168.72.19 127.0.0.1 ::1]
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [localhost old-k8s-version-201745] and IPs [192.168.72.19 127.0.0.1 ::1]
[certs] Generating "etcd/healthcheck-client" certificate and key
[certs] Generating "apiserver-etcd-client" certificate and key
[certs] Generating "sa" key and public key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
Unfortunately, an error has occurred:
timed out waiting for the condition
This error is likely caused by:
- The kubelet is not running
- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
- 'systemctl status kubelet'
- 'journalctl -xeu kubelet'
Additionally, a control plane component may have crashed or exited when started by the container runtime.
To troubleshoot, list all containers using your preferred container runtimes CLI.
Here is one example how you may list all Kubernetes containers running in cri-o/containerd using crictl:
- 'crictl --runtime-endpoint /var/run/crio/crio.sock ps -a | grep kube | grep -v pause'
Once you have found the failing container, you can inspect its logs with:
- 'crictl --runtime-endpoint /var/run/crio/crio.sock logs CONTAINERID'
stderr:
[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
To see the stack trace of this error execute with --v=5 or higher
I0214 21:53:25.613560 290030 ssh_runner.go:195] Run: /bin/bash -c "sudo env PATH="/var/lib/minikube/binaries/v1.20.0:$PATH" kubeadm reset --cri-socket /var/run/crio/crio.sock --force"
I0214 21:53:26.871600 290030 ssh_runner.go:235] Completed: /bin/bash -c "sudo env PATH="/var/lib/minikube/binaries/v1.20.0:$PATH" kubeadm reset --cri-socket /var/run/crio/crio.sock --force": (1.257992755s)
I0214 21:53:26.871711 290030 ssh_runner.go:195] Run: sudo systemctl is-active --quiet service kubelet
I0214 21:53:26.886378 290030 ssh_runner.go:195] Run: sudo ls -la /etc/kubernetes/admin.conf /etc/kubernetes/kubelet.conf /etc/kubernetes/controller-manager.conf /etc/kubernetes/scheduler.conf
I0214 21:53:26.896124 290030 kubeadm.go:155] config check failed, skipping stale config cleanup: sudo ls -la /etc/kubernetes/admin.conf /etc/kubernetes/kubelet.conf /etc/kubernetes/controller-manager.conf /etc/kubernetes/scheduler.conf: Process exited with status 2
stdout:
stderr:
ls: cannot access '/etc/kubernetes/admin.conf': No such file or directory
ls: cannot access '/etc/kubernetes/kubelet.conf': No such file or directory
ls: cannot access '/etc/kubernetes/controller-manager.conf': No such file or directory
ls: cannot access '/etc/kubernetes/scheduler.conf': No such file or directory
I0214 21:53:26.896143 290030 kubeadm.go:157] found existing configuration files:
I0214 21:53:26.896182 290030 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/admin.conf
I0214 21:53:26.906123 290030 kubeadm.go:163] "https://control-plane.minikube.internal:8443" may not be in /etc/kubernetes/admin.conf - will remove: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/admin.conf: Process exited with status 2
stdout:
stderr:
grep: /etc/kubernetes/admin.conf: No such file or directory
I0214 21:53:26.906171 290030 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/admin.conf
I0214 21:53:26.915623 290030 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/kubelet.conf
I0214 21:53:26.924730 290030 kubeadm.go:163] "https://control-plane.minikube.internal:8443" may not be in /etc/kubernetes/kubelet.conf - will remove: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/kubelet.conf: Process exited with status 2
stdout:
stderr:
grep: /etc/kubernetes/kubelet.conf: No such file or directory
I0214 21:53:26.924786 290030 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/kubelet.conf
I0214 21:53:26.934146 290030 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/controller-manager.conf
I0214 21:53:26.944196 290030 kubeadm.go:163] "https://control-plane.minikube.internal:8443" may not be in /etc/kubernetes/controller-manager.conf - will remove: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/controller-manager.conf: Process exited with status 2
stdout:
stderr:
grep: /etc/kubernetes/controller-manager.conf: No such file or directory
I0214 21:53:26.944238 290030 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/controller-manager.conf
I0214 21:53:26.954196 290030 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/scheduler.conf
I0214 21:53:26.964349 290030 kubeadm.go:163] "https://control-plane.minikube.internal:8443" may not be in /etc/kubernetes/scheduler.conf - will remove: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/scheduler.conf: Process exited with status 2
stdout:
stderr:
grep: /etc/kubernetes/scheduler.conf: No such file or directory
I0214 21:53:26.964399 290030 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/scheduler.conf
I0214 21:53:26.975587 290030 ssh_runner.go:286] Start: /bin/bash -c "sudo env PATH="/var/lib/minikube/binaries/v1.20.0:$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,NumCPU,Mem"
I0214 21:53:27.048326 290030 kubeadm.go:310] [init] Using Kubernetes version: v1.20.0
I0214 21:53:27.048373 290030 kubeadm.go:310] [preflight] Running pre-flight checks
I0214 21:53:27.206497 290030 kubeadm.go:310] [preflight] Pulling images required for setting up a Kubernetes cluster
I0214 21:53:27.206651 290030 kubeadm.go:310] [preflight] This might take a minute or two, depending on the speed of your internet connection
I0214 21:53:27.206816 290030 kubeadm.go:310] [preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
I0214 21:53:27.383228 290030 kubeadm.go:310] [certs] Using certificateDir folder "/var/lib/minikube/certs"
I0214 21:53:27.385217 290030 out.go:235] - Generating certificates and keys ...
I0214 21:53:27.385322 290030 kubeadm.go:310] [certs] Using existing ca certificate authority
I0214 21:53:27.385384 290030 kubeadm.go:310] [certs] Using existing apiserver certificate and key on disk
I0214 21:53:27.385458 290030 kubeadm.go:310] [certs] Using existing apiserver-kubelet-client certificate and key on disk
I0214 21:53:27.385510 290030 kubeadm.go:310] [certs] Using existing front-proxy-ca certificate authority
I0214 21:53:27.385570 290030 kubeadm.go:310] [certs] Using existing front-proxy-client certificate and key on disk
I0214 21:53:27.385617 290030 kubeadm.go:310] [certs] Using existing etcd/ca certificate authority
I0214 21:53:27.385671 290030 kubeadm.go:310] [certs] Using existing etcd/server certificate and key on disk
I0214 21:53:27.385733 290030 kubeadm.go:310] [certs] Using existing etcd/peer certificate and key on disk
I0214 21:53:27.385843 290030 kubeadm.go:310] [certs] Using existing etcd/healthcheck-client certificate and key on disk
I0214 21:53:27.385981 290030 kubeadm.go:310] [certs] Using existing apiserver-etcd-client certificate and key on disk
I0214 21:53:27.386036 290030 kubeadm.go:310] [certs] Using the existing "sa" key
I0214 21:53:27.386108 290030 kubeadm.go:310] [kubeconfig] Using kubeconfig folder "/etc/kubernetes"
I0214 21:53:27.545840 290030 kubeadm.go:310] [kubeconfig] Writing "admin.conf" kubeconfig file
I0214 21:53:27.644111 290030 kubeadm.go:310] [kubeconfig] Writing "kubelet.conf" kubeconfig file
I0214 21:53:28.191186 290030 kubeadm.go:310] [kubeconfig] Writing "controller-manager.conf" kubeconfig file
I0214 21:53:28.249994 290030 kubeadm.go:310] [kubeconfig] Writing "scheduler.conf" kubeconfig file
I0214 21:53:28.265248 290030 kubeadm.go:310] [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
I0214 21:53:28.265972 290030 kubeadm.go:310] [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
I0214 21:53:28.266046 290030 kubeadm.go:310] [kubelet-start] Starting the kubelet
I0214 21:53:28.392734 290030 kubeadm.go:310] [control-plane] Using manifest folder "/etc/kubernetes/manifests"
I0214 21:53:28.394451 290030 out.go:235] - Booting up control plane ...
I0214 21:53:28.394587 290030 kubeadm.go:310] [control-plane] Creating static Pod manifest for "kube-apiserver"
I0214 21:53:28.402752 290030 kubeadm.go:310] [control-plane] Creating static Pod manifest for "kube-controller-manager"
I0214 21:53:28.403873 290030 kubeadm.go:310] [control-plane] Creating static Pod manifest for "kube-scheduler"
I0214 21:53:28.404643 290030 kubeadm.go:310] [etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
I0214 21:53:28.408763 290030 kubeadm.go:310] [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
I0214 21:54:08.411434 290030 kubeadm.go:310] [kubelet-check] Initial timeout of 40s passed.
I0214 21:54:08.411652 290030 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0214 21:54:08.411899 290030 kubeadm.go:310] [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
I0214 21:54:13.412787 290030 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0214 21:54:13.413031 290030 kubeadm.go:310] [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
I0214 21:54:23.413691 290030 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0214 21:54:23.413900 290030 kubeadm.go:310] [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
I0214 21:54:43.413423 290030 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0214 21:54:43.413689 290030 kubeadm.go:310] [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
I0214 21:55:23.412955 290030 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0214 21:55:23.413232 290030 kubeadm.go:310] [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
I0214 21:55:23.413250 290030 kubeadm.go:310]
I0214 21:55:23.413325 290030 kubeadm.go:310] Unfortunately, an error has occurred:
I0214 21:55:23.413407 290030 kubeadm.go:310] timed out waiting for the condition
I0214 21:55:23.413428 290030 kubeadm.go:310]
I0214 21:55:23.413471 290030 kubeadm.go:310] This error is likely caused by:
I0214 21:55:23.413537 290030 kubeadm.go:310] - The kubelet is not running
I0214 21:55:23.413694 290030 kubeadm.go:310] - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
I0214 21:55:23.413705 290030 kubeadm.go:310]
I0214 21:55:23.413858 290030 kubeadm.go:310] If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
I0214 21:55:23.413909 290030 kubeadm.go:310] - 'systemctl status kubelet'
I0214 21:55:23.413960 290030 kubeadm.go:310] - 'journalctl -xeu kubelet'
I0214 21:55:23.413970 290030 kubeadm.go:310]
I0214 21:55:23.414121 290030 kubeadm.go:310] Additionally, a control plane component may have crashed or exited when started by the container runtime.
I0214 21:55:23.414245 290030 kubeadm.go:310] To troubleshoot, list all containers using your preferred container runtimes CLI.
I0214 21:55:23.414260 290030 kubeadm.go:310]
I0214 21:55:23.414427 290030 kubeadm.go:310] Here is one example how you may list all Kubernetes containers running in cri-o/containerd using crictl:
I0214 21:55:23.414545 290030 kubeadm.go:310] - 'crictl --runtime-endpoint /var/run/crio/crio.sock ps -a | grep kube | grep -v pause'
I0214 21:55:23.414659 290030 kubeadm.go:310] Once you have found the failing container, you can inspect its logs with:
I0214 21:55:23.414746 290030 kubeadm.go:310] - 'crictl --runtime-endpoint /var/run/crio/crio.sock logs CONTAINERID'
I0214 21:55:23.414753 290030 kubeadm.go:310]
I0214 21:55:23.415747 290030 kubeadm.go:310] [WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
I0214 21:55:23.415865 290030 kubeadm.go:310] error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
I0214 21:55:23.415941 290030 kubeadm.go:310] To see the stack trace of this error execute with --v=5 or higher
I0214 21:55:23.416022 290030 kubeadm.go:394] duration metric: took 3m55.636912816s to StartCluster
I0214 21:55:23.416076 290030 cri.go:54] listing CRI containers in root : {State:all Name:kube-apiserver Namespaces:[]}
I0214 21:55:23.416139 290030 ssh_runner.go:195] Run: sudo crictl ps -a --quiet --name=kube-apiserver
I0214 21:55:23.472700 290030 cri.go:89] found id: ""
I0214 21:55:23.472725 290030 logs.go:282] 0 containers: []
W0214 21:55:23.472736 290030 logs.go:284] No container was found matching "kube-apiserver"
I0214 21:55:23.472745 290030 cri.go:54] listing CRI containers in root : {State:all Name:etcd Namespaces:[]}
I0214 21:55:23.472803 290030 ssh_runner.go:195] Run: sudo crictl ps -a --quiet --name=etcd
I0214 21:55:23.512255 290030 cri.go:89] found id: ""
I0214 21:55:23.512280 290030 logs.go:282] 0 containers: []
W0214 21:55:23.512291 290030 logs.go:284] No container was found matching "etcd"
I0214 21:55:23.512301 290030 cri.go:54] listing CRI containers in root : {State:all Name:coredns Namespaces:[]}
I0214 21:55:23.512358 290030 ssh_runner.go:195] Run: sudo crictl ps -a --quiet --name=coredns
I0214 21:55:23.548981 290030 cri.go:89] found id: ""
I0214 21:55:23.549000 290030 logs.go:282] 0 containers: []
W0214 21:55:23.549008 290030 logs.go:284] No container was found matching "coredns"
I0214 21:55:23.549014 290030 cri.go:54] listing CRI containers in root : {State:all Name:kube-scheduler Namespaces:[]}
I0214 21:55:23.549051 290030 ssh_runner.go:195] Run: sudo crictl ps -a --quiet --name=kube-scheduler
I0214 21:55:23.611827 290030 cri.go:89] found id: ""
I0214 21:55:23.611868 290030 logs.go:282] 0 containers: []
W0214 21:55:23.611878 290030 logs.go:284] No container was found matching "kube-scheduler"
I0214 21:55:23.611889 290030 cri.go:54] listing CRI containers in root : {State:all Name:kube-proxy Namespaces:[]}
I0214 21:55:23.611953 290030 ssh_runner.go:195] Run: sudo crictl ps -a --quiet --name=kube-proxy
I0214 21:55:23.647207 290030 cri.go:89] found id: ""
I0214 21:55:23.647234 290030 logs.go:282] 0 containers: []
W0214 21:55:23.647241 290030 logs.go:284] No container was found matching "kube-proxy"
I0214 21:55:23.647248 290030 cri.go:54] listing CRI containers in root : {State:all Name:kube-controller-manager Namespaces:[]}
I0214 21:55:23.647298 290030 ssh_runner.go:195] Run: sudo crictl ps -a --quiet --name=kube-controller-manager
I0214 21:55:23.683110 290030 cri.go:89] found id: ""
I0214 21:55:23.683134 290030 logs.go:282] 0 containers: []
W0214 21:55:23.683154 290030 logs.go:284] No container was found matching "kube-controller-manager"
I0214 21:55:23.683163 290030 cri.go:54] listing CRI containers in root : {State:all Name:kindnet Namespaces:[]}
I0214 21:55:23.683222 290030 ssh_runner.go:195] Run: sudo crictl ps -a --quiet --name=kindnet
I0214 21:55:23.727591 290030 cri.go:89] found id: ""
I0214 21:55:23.727625 290030 logs.go:282] 0 containers: []
W0214 21:55:23.727638 290030 logs.go:284] No container was found matching "kindnet"
I0214 21:55:23.727652 290030 logs.go:123] Gathering logs for container status ...
I0214 21:55:23.727669 290030 ssh_runner.go:195] Run: /bin/bash -c "sudo `which crictl || echo crictl` ps -a || sudo docker ps -a"
I0214 21:55:23.783249 290030 logs.go:123] Gathering logs for kubelet ...
I0214 21:55:23.783278 290030 ssh_runner.go:195] Run: /bin/bash -c "sudo journalctl -u kubelet -n 400"
I0214 21:55:23.847415 290030 logs.go:123] Gathering logs for dmesg ...
I0214 21:55:23.847443 290030 ssh_runner.go:195] Run: /bin/bash -c "sudo dmesg -PH -L=never --level warn,err,crit,alert,emerg | tail -n 400"
I0214 21:55:23.862277 290030 logs.go:123] Gathering logs for describe nodes ...
I0214 21:55:23.862315 290030 ssh_runner.go:195] Run: /bin/bash -c "sudo /var/lib/minikube/binaries/v1.20.0/kubectl describe nodes --kubeconfig=/var/lib/minikube/kubeconfig"
W0214 21:55:24.008635 290030 logs.go:130] failed describe nodes: command: /bin/bash -c "sudo /var/lib/minikube/binaries/v1.20.0/kubectl describe nodes --kubeconfig=/var/lib/minikube/kubeconfig" /bin/bash -c "sudo /var/lib/minikube/binaries/v1.20.0/kubectl describe nodes --kubeconfig=/var/lib/minikube/kubeconfig": Process exited with status 1
stdout:
stderr:
The connection to the server localhost:8443 was refused - did you specify the right host or port?
output:
** stderr **
The connection to the server localhost:8443 was refused - did you specify the right host or port?
** /stderr **
I0214 21:55:24.008659 290030 logs.go:123] Gathering logs for CRI-O ...
I0214 21:55:24.008674 290030 ssh_runner.go:195] Run: /bin/bash -c "sudo journalctl -u crio -n 400"
W0214 21:55:24.122731 290030 out.go:418] Error starting cluster: wait: /bin/bash -c "sudo env PATH="/var/lib/minikube/binaries/v1.20.0:$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,NumCPU,Mem": Process exited with status 1
stdout:
[init] Using Kubernetes version: v1.20.0
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[certs] Using certificateDir folder "/var/lib/minikube/certs"
[certs] Using existing ca certificate authority
[certs] Using existing apiserver certificate and key on disk
[certs] Using existing apiserver-kubelet-client certificate and key on disk
[certs] Using existing front-proxy-ca certificate authority
[certs] Using existing front-proxy-client certificate and key on disk
[certs] Using existing etcd/ca certificate authority
[certs] Using existing etcd/server certificate and key on disk
[certs] Using existing etcd/peer certificate and key on disk
[certs] Using existing etcd/healthcheck-client certificate and key on disk
[certs] Using existing apiserver-etcd-client certificate and key on disk
[certs] Using the existing "sa" key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
Unfortunately, an error has occurred:
timed out waiting for the condition
This error is likely caused by:
- The kubelet is not running
- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
- 'systemctl status kubelet'
- 'journalctl -xeu kubelet'
Additionally, a control plane component may have crashed or exited when started by the container runtime.
To troubleshoot, list all containers using your preferred container runtimes CLI.
Here is one example how you may list all Kubernetes containers running in cri-o/containerd using crictl:
- 'crictl --runtime-endpoint /var/run/crio/crio.sock ps -a | grep kube | grep -v pause'
Once you have found the failing container, you can inspect its logs with:
- 'crictl --runtime-endpoint /var/run/crio/crio.sock logs CONTAINERID'
stderr:
[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
To see the stack trace of this error execute with --v=5 or higher
W0214 21:55:24.122793 290030 out.go:270] *
*
W0214 21:55:24.122854 290030 out.go:270] X Error starting cluster: wait: /bin/bash -c "sudo env PATH="/var/lib/minikube/binaries/v1.20.0:$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,NumCPU,Mem": Process exited with status 1
stdout:
[init] Using Kubernetes version: v1.20.0
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[certs] Using certificateDir folder "/var/lib/minikube/certs"
[certs] Using existing ca certificate authority
[certs] Using existing apiserver certificate and key on disk
[certs] Using existing apiserver-kubelet-client certificate and key on disk
[certs] Using existing front-proxy-ca certificate authority
[certs] Using existing front-proxy-client certificate and key on disk
[certs] Using existing etcd/ca certificate authority
[certs] Using existing etcd/server certificate and key on disk
[certs] Using existing etcd/peer certificate and key on disk
[certs] Using existing etcd/healthcheck-client certificate and key on disk
[certs] Using existing apiserver-etcd-client certificate and key on disk
[certs] Using the existing "sa" key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
Unfortunately, an error has occurred:
timed out waiting for the condition
This error is likely caused by:
- The kubelet is not running
- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
- 'systemctl status kubelet'
- 'journalctl -xeu kubelet'
Additionally, a control plane component may have crashed or exited when started by the container runtime.
To troubleshoot, list all containers using your preferred container runtimes CLI.
Here is one example how you may list all Kubernetes containers running in cri-o/containerd using crictl:
- 'crictl --runtime-endpoint /var/run/crio/crio.sock ps -a | grep kube | grep -v pause'
Once you have found the failing container, you can inspect its logs with:
- 'crictl --runtime-endpoint /var/run/crio/crio.sock logs CONTAINERID'
stderr:
[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
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.0:$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,NumCPU,Mem": Process exited with status 1
stdout:
[init] Using Kubernetes version: v1.20.0
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[certs] Using certificateDir folder "/var/lib/minikube/certs"
[certs] Using existing ca certificate authority
[certs] Using existing apiserver certificate and key on disk
[certs] Using existing apiserver-kubelet-client certificate and key on disk
[certs] Using existing front-proxy-ca certificate authority
[certs] Using existing front-proxy-client certificate and key on disk
[certs] Using existing etcd/ca certificate authority
[certs] Using existing etcd/server certificate and key on disk
[certs] Using existing etcd/peer certificate and key on disk
[certs] Using existing etcd/healthcheck-client certificate and key on disk
[certs] Using existing apiserver-etcd-client certificate and key on disk
[certs] Using the existing "sa" key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
Unfortunately, an error has occurred:
timed out waiting for the condition
This error is likely caused by:
- The kubelet is not running
- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
- 'systemctl status kubelet'
- 'journalctl -xeu kubelet'
Additionally, a control plane component may have crashed or exited when started by the container runtime.
To troubleshoot, list all containers using your preferred container runtimes CLI.
Here is one example how you may list all Kubernetes containers running in cri-o/containerd using crictl:
- 'crictl --runtime-endpoint /var/run/crio/crio.sock ps -a | grep kube | grep -v pause'
Once you have found the failing container, you can inspect its logs with:
- 'crictl --runtime-endpoint /var/run/crio/crio.sock logs CONTAINERID'
stderr:
[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
To see the stack trace of this error execute with --v=5 or higher
W0214 21:55:24.122868 290030 out.go:270] *
*
W0214 21:55:24.123785 290030 out.go:293] ╭─────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ * If the above advice does not help, please let us know: │
│ https://github.com/kubernetes/minikube/issues/new/choose │
│ │
│ * Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue. │
│ │
╰─────────────────────────────────────────────────────────────────────────────────────────────╯
╭─────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ * If the above advice does not help, please let us know: │
│ https://github.com/kubernetes/minikube/issues/new/choose │
│ │
│ * Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue. │
│ │
╰─────────────────────────────────────────────────────────────────────────────────────────────╯
I0214 21:55:24.126783 290030 out.go:201]
W0214 21:55:24.127954 290030 out.go:270] X Exiting due to K8S_KUBELET_NOT_RUNNING: wait: /bin/bash -c "sudo env PATH="/var/lib/minikube/binaries/v1.20.0:$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,NumCPU,Mem": Process exited with status 1
stdout:
[init] Using Kubernetes version: v1.20.0
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[certs] Using certificateDir folder "/var/lib/minikube/certs"
[certs] Using existing ca certificate authority
[certs] Using existing apiserver certificate and key on disk
[certs] Using existing apiserver-kubelet-client certificate and key on disk
[certs] Using existing front-proxy-ca certificate authority
[certs] Using existing front-proxy-client certificate and key on disk
[certs] Using existing etcd/ca certificate authority
[certs] Using existing etcd/server certificate and key on disk
[certs] Using existing etcd/peer certificate and key on disk
[certs] Using existing etcd/healthcheck-client certificate and key on disk
[certs] Using existing apiserver-etcd-client certificate and key on disk
[certs] Using the existing "sa" key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
Unfortunately, an error has occurred:
timed out waiting for the condition
This error is likely caused by:
- The kubelet is not running
- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
- 'systemctl status kubelet'
- 'journalctl -xeu kubelet'
Additionally, a control plane component may have crashed or exited when started by the container runtime.
To troubleshoot, list all containers using your preferred container runtimes CLI.
Here is one example how you may list all Kubernetes containers running in cri-o/containerd using crictl:
- 'crictl --runtime-endpoint /var/run/crio/crio.sock ps -a | grep kube | grep -v pause'
Once you have found the failing container, you can inspect its logs with:
- 'crictl --runtime-endpoint /var/run/crio/crio.sock logs CONTAINERID'
stderr:
[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
To see the stack trace of this error execute with --v=5 or higher
X Exiting due to K8S_KUBELET_NOT_RUNNING: wait: /bin/bash -c "sudo env PATH="/var/lib/minikube/binaries/v1.20.0:$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,NumCPU,Mem": Process exited with status 1
stdout:
[init] Using Kubernetes version: v1.20.0
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[certs] Using certificateDir folder "/var/lib/minikube/certs"
[certs] Using existing ca certificate authority
[certs] Using existing apiserver certificate and key on disk
[certs] Using existing apiserver-kubelet-client certificate and key on disk
[certs] Using existing front-proxy-ca certificate authority
[certs] Using existing front-proxy-client certificate and key on disk
[certs] Using existing etcd/ca certificate authority
[certs] Using existing etcd/server certificate and key on disk
[certs] Using existing etcd/peer certificate and key on disk
[certs] Using existing etcd/healthcheck-client certificate and key on disk
[certs] Using existing apiserver-etcd-client certificate and key on disk
[certs] Using the existing "sa" key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
Unfortunately, an error has occurred:
timed out waiting for the condition
This error is likely caused by:
- The kubelet is not running
- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
- 'systemctl status kubelet'
- 'journalctl -xeu kubelet'
Additionally, a control plane component may have crashed or exited when started by the container runtime.
To troubleshoot, list all containers using your preferred container runtimes CLI.
Here is one example how you may list all Kubernetes containers running in cri-o/containerd using crictl:
- 'crictl --runtime-endpoint /var/run/crio/crio.sock ps -a | grep kube | grep -v pause'
Once you have found the failing container, you can inspect its logs with:
- 'crictl --runtime-endpoint /var/run/crio/crio.sock logs CONTAINERID'
stderr:
[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
To see the stack trace of this error execute with --v=5 or higher
W0214 21:55:24.128011 290030 out.go:270] * Suggestion: Check output of 'journalctl -xeu kubelet', try passing --extra-config=kubelet.cgroup-driver=systemd to minikube start
* Suggestion: Check output of 'journalctl -xeu kubelet', try passing --extra-config=kubelet.cgroup-driver=systemd to minikube start
W0214 21:55:24.128038 290030 out.go:270] * Related issue: https://github.com/kubernetes/minikube/issues/4172
* Related issue: https://github.com/kubernetes/minikube/issues/4172
I0214 21:55:24.129339 290030 out.go:201]
** /stderr **
start_stop_delete_test.go:186: failed starting minikube -first start-. args "out/minikube-linux-amd64 start -p old-k8s-version-201745 --memory=2200 --alsologtostderr --wait=true --kvm-network=default --kvm-qemu-uri=qemu:///system --disable-driver-mounts --keep-context=false --driver=kvm2 --container-runtime=crio --kubernetes-version=v1.20.0": exit status 109
helpers_test.go:222: -----------------------post-mortem--------------------------------
helpers_test.go:239: (dbg) Run: out/minikube-linux-amd64 status --format={{.Host}} -p old-k8s-version-201745 -n old-k8s-version-201745
helpers_test.go:239: (dbg) Non-zero exit: out/minikube-linux-amd64 status --format={{.Host}} -p old-k8s-version-201745 -n old-k8s-version-201745: exit status 6 (267.034686ms)
-- stdout --
Running
WARNING: Your kubectl is pointing to stale minikube-vm.
To fix the kubectl context, run `minikube update-context`
-- /stdout --
** stderr **
E0214 21:55:24.446934 293631 status.go:458] kubeconfig endpoint: get endpoint: "old-k8s-version-201745" does not appear in /home/jenkins/minikube-integration/20315-243456/kubeconfig
** /stderr **
helpers_test.go:239: status error: exit status 6 (may be ok)
helpers_test.go:241: "old-k8s-version-201745" host is not running, skipping log retrieval (state="Running\nWARNING: Your kubectl is pointing to stale minikube-vm.\nTo fix the kubectl context, run `minikube update-context`")
--- FAIL: TestStartStop/group/old-k8s-version/serial/FirstStart (333.95s)