=== 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-233759 --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
start_stop_delete_test.go:184: (dbg) Non-zero exit: out/minikube-linux-amd64 start -p old-k8s-version-233759 --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 (4m47.394480408s)
-- stdout --
* [old-k8s-version-233759] minikube v1.35.0 on Ubuntu 20.04 (kvm/amd64)
- MINIKUBE_LOCATION=20451
- MINIKUBE_SUPPRESS_DOCKER_PERFORMANCE=true
- KUBECONFIG=/home/jenkins/minikube-integration/20451-887294/kubeconfig
- MINIKUBE_HOME=/home/jenkins/minikube-integration/20451-887294/.minikube
- MINIKUBE_BIN=out/minikube-linux-amd64
- MINIKUBE_FORCE_SYSTEMD=
* Using the kvm2 driver based on user configuration
* Starting "old-k8s-version-233759" primary control-plane node in "old-k8s-version-233759" 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 **
I0224 13:17:15.742460 945004 out.go:345] Setting OutFile to fd 1 ...
I0224 13:17:15.742593 945004 out.go:392] TERM=,COLORTERM=, which probably does not support color
I0224 13:17:15.742603 945004 out.go:358] Setting ErrFile to fd 2...
I0224 13:17:15.742607 945004 out.go:392] TERM=,COLORTERM=, which probably does not support color
I0224 13:17:15.742821 945004 root.go:338] Updating PATH: /home/jenkins/minikube-integration/20451-887294/.minikube/bin
I0224 13:17:15.743454 945004 out.go:352] Setting JSON to false
I0224 13:17:15.744645 945004 start.go:129] hostinfo: {"hostname":"ubuntu-20-agent-11","uptime":10777,"bootTime":1740392259,"procs":297,"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"}
I0224 13:17:15.744757 945004 start.go:139] virtualization: kvm guest
I0224 13:17:15.747180 945004 out.go:177] * [old-k8s-version-233759] minikube v1.35.0 on Ubuntu 20.04 (kvm/amd64)
I0224 13:17:15.748552 945004 out.go:177] - MINIKUBE_LOCATION=20451
I0224 13:17:15.748567 945004 notify.go:220] Checking for updates...
I0224 13:17:15.751586 945004 out.go:177] - MINIKUBE_SUPPRESS_DOCKER_PERFORMANCE=true
I0224 13:17:15.753222 945004 out.go:177] - KUBECONFIG=/home/jenkins/minikube-integration/20451-887294/kubeconfig
I0224 13:17:15.754512 945004 out.go:177] - MINIKUBE_HOME=/home/jenkins/minikube-integration/20451-887294/.minikube
I0224 13:17:15.755914 945004 out.go:177] - MINIKUBE_BIN=out/minikube-linux-amd64
I0224 13:17:15.757300 945004 out.go:177] - MINIKUBE_FORCE_SYSTEMD=
I0224 13:17:15.759178 945004 config.go:182] Loaded profile config "bridge-799329": Driver=kvm2, ContainerRuntime=crio, KubernetesVersion=v1.32.2
I0224 13:17:15.759324 945004 config.go:182] Loaded profile config "enable-default-cni-799329": Driver=kvm2, ContainerRuntime=crio, KubernetesVersion=v1.32.2
I0224 13:17:15.759450 945004 config.go:182] Loaded profile config "flannel-799329": Driver=kvm2, ContainerRuntime=crio, KubernetesVersion=v1.32.2
I0224 13:17:15.759619 945004 driver.go:394] Setting default libvirt URI to qemu:///system
I0224 13:17:15.799815 945004 out.go:177] * Using the kvm2 driver based on user configuration
I0224 13:17:15.801531 945004 start.go:297] selected driver: kvm2
I0224 13:17:15.801566 945004 start.go:901] validating driver "kvm2" against <nil>
I0224 13:17:15.801583 945004 start.go:912] status for kvm2: {Installed:true Healthy:true Running:true NeedsImprovement:false Error:<nil> Reason: Fix: Doc: Version:}
I0224 13:17:15.802332 945004 install.go:52] acquiring lock: {Name:mk900956b073697a4aa6c80a27c6bb0742a99a53 Clock:{} Delay:500ms Timeout:10m0s Cancel:<nil>}
I0224 13:17:15.802435 945004 install.go:117] Validating docker-machine-driver-kvm2, PATH=/home/jenkins/minikube-integration/20451-887294/.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
I0224 13:17:15.819290 945004 install.go:137] /home/jenkins/workspace/KVM_Linux_crio_integration/out/docker-machine-driver-kvm2 version is 1.35.0
I0224 13:17:15.819357 945004 start_flags.go:310] no existing cluster config was found, will generate one from the flags
I0224 13:17:15.819738 945004 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]
I0224 13:17:15.819804 945004 cni.go:84] Creating CNI manager for ""
I0224 13:17:15.819873 945004 cni.go:146] "kvm2" driver + "crio" runtime found, recommending bridge
I0224 13:17:15.819886 945004 start_flags.go:319] Found "bridge CNI" CNI - setting NetworkPlugin=cni
I0224 13:17:15.819966 945004 start.go:340] cluster config:
{Name:old-k8s-version-233759 KeepContext:false EmbedCerts:false MinikubeISO: KicBaseImage:gcr.io/k8s-minikube/kicbase-builds:v0.0.46-1740046583-20436@sha256:b4324ef42fab4e243d39dd69028f243606b2fa4379f6ec916c89e512f68338f4 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-233759 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}
I0224 13:17:15.820126 945004 iso.go:125] acquiring lock: {Name:mk57408cca66a96a13d93cda43cdfac6e61aef3f Clock:{} Delay:500ms Timeout:10m0s Cancel:<nil>}
I0224 13:17:15.822177 945004 out.go:177] * Starting "old-k8s-version-233759" primary control-plane node in "old-k8s-version-233759" cluster
I0224 13:17:15.823470 945004 preload.go:131] Checking if preload exists for k8s version v1.20.0 and runtime crio
I0224 13:17:15.823527 945004 preload.go:146] Found local preload: /home/jenkins/minikube-integration/20451-887294/.minikube/cache/preloaded-tarball/preloaded-images-k8s-v18-v1.20.0-cri-o-overlay-amd64.tar.lz4
I0224 13:17:15.823542 945004 cache.go:56] Caching tarball of preloaded images
I0224 13:17:15.823681 945004 preload.go:172] Found /home/jenkins/minikube-integration/20451-887294/.minikube/cache/preloaded-tarball/preloaded-images-k8s-v18-v1.20.0-cri-o-overlay-amd64.tar.lz4 in cache, skipping download
I0224 13:17:15.823697 945004 cache.go:59] Finished verifying existence of preloaded tar for v1.20.0 on crio
I0224 13:17:15.823808 945004 profile.go:143] Saving config to /home/jenkins/minikube-integration/20451-887294/.minikube/profiles/old-k8s-version-233759/config.json ...
I0224 13:17:15.823837 945004 lock.go:35] WriteFile acquiring /home/jenkins/minikube-integration/20451-887294/.minikube/profiles/old-k8s-version-233759/config.json: {Name:mk0170c135264270baf9117fb286234a29f0cbf1 Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0224 13:17:15.823992 945004 start.go:360] acquireMachinesLock for old-k8s-version-233759: {Name:mk023761b01bb629a1acd40bc8104cc517b0e15b Clock:{} Delay:500ms Timeout:13m0s Cancel:<nil>}
I0224 13:17:27.858912 945004 start.go:364] duration metric: took 12.034859607s to acquireMachinesLock for "old-k8s-version-233759"
I0224 13:17:27.859042 945004 start.go:93] Provisioning new machine with config: &{Name:old-k8s-version-233759 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-1740046583-20436@sha256:b4324ef42fab4e243d39dd69028f243606b2fa4379f6ec916c89e512f68338f4 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-233759 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}
I0224 13:17:27.859186 945004 start.go:125] createHost starting for "" (driver="kvm2")
I0224 13:17:27.861274 945004 out.go:235] * Creating kvm2 VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
I0224 13:17:27.861585 945004 main.go:141] libmachine: Found binary path at /home/jenkins/workspace/KVM_Linux_crio_integration/out/docker-machine-driver-kvm2
I0224 13:17:27.861697 945004 main.go:141] libmachine: Launching plugin server for driver kvm2
I0224 13:17:27.879388 945004 main.go:141] libmachine: Plugin server listening at address 127.0.0.1:42577
I0224 13:17:27.879834 945004 main.go:141] libmachine: () Calling .GetVersion
I0224 13:17:27.880502 945004 main.go:141] libmachine: Using API Version 1
I0224 13:17:27.880528 945004 main.go:141] libmachine: () Calling .SetConfigRaw
I0224 13:17:27.880884 945004 main.go:141] libmachine: () Calling .GetMachineName
I0224 13:17:27.881094 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetMachineName
I0224 13:17:27.881237 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .DriverName
I0224 13:17:27.881457 945004 start.go:159] libmachine.API.Create for "old-k8s-version-233759" (driver="kvm2")
I0224 13:17:27.881497 945004 client.go:168] LocalClient.Create starting
I0224 13:17:27.881537 945004 main.go:141] libmachine: Reading certificate data from /home/jenkins/minikube-integration/20451-887294/.minikube/certs/ca.pem
I0224 13:17:27.881594 945004 main.go:141] libmachine: Decoding PEM data...
I0224 13:17:27.881616 945004 main.go:141] libmachine: Parsing certificate...
I0224 13:17:27.881689 945004 main.go:141] libmachine: Reading certificate data from /home/jenkins/minikube-integration/20451-887294/.minikube/certs/cert.pem
I0224 13:17:27.881716 945004 main.go:141] libmachine: Decoding PEM data...
I0224 13:17:27.881735 945004 main.go:141] libmachine: Parsing certificate...
I0224 13:17:27.881761 945004 main.go:141] libmachine: Running pre-create checks...
I0224 13:17:27.881774 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .PreCreateCheck
I0224 13:17:27.882156 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetConfigRaw
I0224 13:17:27.882680 945004 main.go:141] libmachine: Creating machine...
I0224 13:17:27.882698 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .Create
I0224 13:17:27.882864 945004 main.go:141] libmachine: (old-k8s-version-233759) creating KVM machine...
I0224 13:17:27.882881 945004 main.go:141] libmachine: (old-k8s-version-233759) creating network...
I0224 13:17:27.884266 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | found existing default KVM network
I0224 13:17:27.885834 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | I0224 13:17:27.885623 945120 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:virbr4 IfaceIPv4:192.168.39.1 IfaceMTU:1500 IfaceMAC:52:54:00:97:6f:50} reservation:<nil>}
I0224 13:17:27.887097 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | I0224 13:17:27.887000 945120 network.go:206] using free private subnet 192.168.50.0/24: &{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: IfaceIPv4: IfaceMTU:0 IfaceMAC:} reservation:0xc000286a40}
I0224 13:17:27.887124 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | created network xml:
I0224 13:17:27.887133 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | <network>
I0224 13:17:27.887145 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | <name>mk-old-k8s-version-233759</name>
I0224 13:17:27.887157 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | <dns enable='no'/>
I0224 13:17:27.887165 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG |
I0224 13:17:27.887174 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | <ip address='192.168.50.1' netmask='255.255.255.0'>
I0224 13:17:27.887192 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | <dhcp>
I0224 13:17:27.887210 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | <range start='192.168.50.2' end='192.168.50.253'/>
I0224 13:17:27.887215 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | </dhcp>
I0224 13:17:27.887219 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | </ip>
I0224 13:17:27.887227 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG |
I0224 13:17:27.887233 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | </network>
I0224 13:17:27.887243 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG |
I0224 13:17:27.893594 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | trying to create private KVM network mk-old-k8s-version-233759 192.168.50.0/24...
I0224 13:17:27.987269 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | private KVM network mk-old-k8s-version-233759 192.168.50.0/24 created
I0224 13:17:27.987323 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | I0224 13:17:27.987227 945120 common.go:144] Making disk image using store path: /home/jenkins/minikube-integration/20451-887294/.minikube
I0224 13:17:27.987343 945004 main.go:141] libmachine: (old-k8s-version-233759) setting up store path in /home/jenkins/minikube-integration/20451-887294/.minikube/machines/old-k8s-version-233759 ...
I0224 13:17:27.987356 945004 main.go:141] libmachine: (old-k8s-version-233759) building disk image from file:///home/jenkins/minikube-integration/20451-887294/.minikube/cache/iso/amd64/minikube-v1.35.0-amd64.iso
I0224 13:17:27.987426 945004 main.go:141] libmachine: (old-k8s-version-233759) Downloading /home/jenkins/minikube-integration/20451-887294/.minikube/cache/boot2docker.iso from file:///home/jenkins/minikube-integration/20451-887294/.minikube/cache/iso/amd64/minikube-v1.35.0-amd64.iso...
I0224 13:17:28.295831 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | I0224 13:17:28.295676 945120 common.go:151] Creating ssh key: /home/jenkins/minikube-integration/20451-887294/.minikube/machines/old-k8s-version-233759/id_rsa...
I0224 13:17:28.350938 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | I0224 13:17:28.350740 945120 common.go:157] Creating raw disk image: /home/jenkins/minikube-integration/20451-887294/.minikube/machines/old-k8s-version-233759/old-k8s-version-233759.rawdisk...
I0224 13:17:28.350980 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | Writing magic tar header
I0224 13:17:28.351002 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | Writing SSH key tar header
I0224 13:17:28.351014 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | I0224 13:17:28.350938 945120 common.go:171] Fixing permissions on /home/jenkins/minikube-integration/20451-887294/.minikube/machines/old-k8s-version-233759 ...
I0224 13:17:28.351071 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | checking permissions on dir: /home/jenkins/minikube-integration/20451-887294/.minikube/machines/old-k8s-version-233759
I0224 13:17:28.351182 945004 main.go:141] libmachine: (old-k8s-version-233759) setting executable bit set on /home/jenkins/minikube-integration/20451-887294/.minikube/machines/old-k8s-version-233759 (perms=drwx------)
I0224 13:17:28.351214 945004 main.go:141] libmachine: (old-k8s-version-233759) setting executable bit set on /home/jenkins/minikube-integration/20451-887294/.minikube/machines (perms=drwxr-xr-x)
I0224 13:17:28.351227 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | checking permissions on dir: /home/jenkins/minikube-integration/20451-887294/.minikube/machines
I0224 13:17:28.351242 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | checking permissions on dir: /home/jenkins/minikube-integration/20451-887294/.minikube
I0224 13:17:28.351256 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | checking permissions on dir: /home/jenkins/minikube-integration/20451-887294
I0224 13:17:28.351285 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | checking permissions on dir: /home/jenkins/minikube-integration
I0224 13:17:28.351303 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | checking permissions on dir: /home/jenkins
I0224 13:17:28.351315 945004 main.go:141] libmachine: (old-k8s-version-233759) setting executable bit set on /home/jenkins/minikube-integration/20451-887294/.minikube (perms=drwxr-xr-x)
I0224 13:17:28.351333 945004 main.go:141] libmachine: (old-k8s-version-233759) setting executable bit set on /home/jenkins/minikube-integration/20451-887294 (perms=drwxrwxr-x)
I0224 13:17:28.351346 945004 main.go:141] libmachine: (old-k8s-version-233759) setting executable bit set on /home/jenkins/minikube-integration (perms=drwxrwxr-x)
I0224 13:17:28.351360 945004 main.go:141] libmachine: (old-k8s-version-233759) setting executable bit set on /home/jenkins (perms=drwxr-xr-x)
I0224 13:17:28.351371 945004 main.go:141] libmachine: (old-k8s-version-233759) creating domain...
I0224 13:17:28.351384 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | checking permissions on dir: /home
I0224 13:17:28.351401 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | skipping /home - not owner
I0224 13:17:28.353011 945004 main.go:141] libmachine: (old-k8s-version-233759) define libvirt domain using xml:
I0224 13:17:28.353042 945004 main.go:141] libmachine: (old-k8s-version-233759) <domain type='kvm'>
I0224 13:17:28.353055 945004 main.go:141] libmachine: (old-k8s-version-233759) <name>old-k8s-version-233759</name>
I0224 13:17:28.353062 945004 main.go:141] libmachine: (old-k8s-version-233759) <memory unit='MiB'>2200</memory>
I0224 13:17:28.353097 945004 main.go:141] libmachine: (old-k8s-version-233759) <vcpu>2</vcpu>
I0224 13:17:28.353104 945004 main.go:141] libmachine: (old-k8s-version-233759) <features>
I0224 13:17:28.353111 945004 main.go:141] libmachine: (old-k8s-version-233759) <acpi/>
I0224 13:17:28.353119 945004 main.go:141] libmachine: (old-k8s-version-233759) <apic/>
I0224 13:17:28.353128 945004 main.go:141] libmachine: (old-k8s-version-233759) <pae/>
I0224 13:17:28.353139 945004 main.go:141] libmachine: (old-k8s-version-233759)
I0224 13:17:28.353147 945004 main.go:141] libmachine: (old-k8s-version-233759) </features>
I0224 13:17:28.353157 945004 main.go:141] libmachine: (old-k8s-version-233759) <cpu mode='host-passthrough'>
I0224 13:17:28.353165 945004 main.go:141] libmachine: (old-k8s-version-233759)
I0224 13:17:28.353174 945004 main.go:141] libmachine: (old-k8s-version-233759) </cpu>
I0224 13:17:28.353181 945004 main.go:141] libmachine: (old-k8s-version-233759) <os>
I0224 13:17:28.353188 945004 main.go:141] libmachine: (old-k8s-version-233759) <type>hvm</type>
I0224 13:17:28.353195 945004 main.go:141] libmachine: (old-k8s-version-233759) <boot dev='cdrom'/>
I0224 13:17:28.353202 945004 main.go:141] libmachine: (old-k8s-version-233759) <boot dev='hd'/>
I0224 13:17:28.353211 945004 main.go:141] libmachine: (old-k8s-version-233759) <bootmenu enable='no'/>
I0224 13:17:28.353245 945004 main.go:141] libmachine: (old-k8s-version-233759) </os>
I0224 13:17:28.353258 945004 main.go:141] libmachine: (old-k8s-version-233759) <devices>
I0224 13:17:28.353264 945004 main.go:141] libmachine: (old-k8s-version-233759) <disk type='file' device='cdrom'>
I0224 13:17:28.353281 945004 main.go:141] libmachine: (old-k8s-version-233759) <source file='/home/jenkins/minikube-integration/20451-887294/.minikube/machines/old-k8s-version-233759/boot2docker.iso'/>
I0224 13:17:28.353292 945004 main.go:141] libmachine: (old-k8s-version-233759) <target dev='hdc' bus='scsi'/>
I0224 13:17:28.353300 945004 main.go:141] libmachine: (old-k8s-version-233759) <readonly/>
I0224 13:17:28.353339 945004 main.go:141] libmachine: (old-k8s-version-233759) </disk>
I0224 13:17:28.353349 945004 main.go:141] libmachine: (old-k8s-version-233759) <disk type='file' device='disk'>
I0224 13:17:28.353363 945004 main.go:141] libmachine: (old-k8s-version-233759) <driver name='qemu' type='raw' cache='default' io='threads' />
I0224 13:17:28.353382 945004 main.go:141] libmachine: (old-k8s-version-233759) <source file='/home/jenkins/minikube-integration/20451-887294/.minikube/machines/old-k8s-version-233759/old-k8s-version-233759.rawdisk'/>
I0224 13:17:28.353393 945004 main.go:141] libmachine: (old-k8s-version-233759) <target dev='hda' bus='virtio'/>
I0224 13:17:28.353405 945004 main.go:141] libmachine: (old-k8s-version-233759) </disk>
I0224 13:17:28.353412 945004 main.go:141] libmachine: (old-k8s-version-233759) <interface type='network'>
I0224 13:17:28.353421 945004 main.go:141] libmachine: (old-k8s-version-233759) <source network='mk-old-k8s-version-233759'/>
I0224 13:17:28.353433 945004 main.go:141] libmachine: (old-k8s-version-233759) <model type='virtio'/>
I0224 13:17:28.353442 945004 main.go:141] libmachine: (old-k8s-version-233759) </interface>
I0224 13:17:28.353449 945004 main.go:141] libmachine: (old-k8s-version-233759) <interface type='network'>
I0224 13:17:28.353459 945004 main.go:141] libmachine: (old-k8s-version-233759) <source network='default'/>
I0224 13:17:28.353475 945004 main.go:141] libmachine: (old-k8s-version-233759) <model type='virtio'/>
I0224 13:17:28.353483 945004 main.go:141] libmachine: (old-k8s-version-233759) </interface>
I0224 13:17:28.353490 945004 main.go:141] libmachine: (old-k8s-version-233759) <serial type='pty'>
I0224 13:17:28.353497 945004 main.go:141] libmachine: (old-k8s-version-233759) <target port='0'/>
I0224 13:17:28.353503 945004 main.go:141] libmachine: (old-k8s-version-233759) </serial>
I0224 13:17:28.353510 945004 main.go:141] libmachine: (old-k8s-version-233759) <console type='pty'>
I0224 13:17:28.353517 945004 main.go:141] libmachine: (old-k8s-version-233759) <target type='serial' port='0'/>
I0224 13:17:28.353525 945004 main.go:141] libmachine: (old-k8s-version-233759) </console>
I0224 13:17:28.353532 945004 main.go:141] libmachine: (old-k8s-version-233759) <rng model='virtio'>
I0224 13:17:28.353541 945004 main.go:141] libmachine: (old-k8s-version-233759) <backend model='random'>/dev/random</backend>
I0224 13:17:28.353546 945004 main.go:141] libmachine: (old-k8s-version-233759) </rng>
I0224 13:17:28.353553 945004 main.go:141] libmachine: (old-k8s-version-233759)
I0224 13:17:28.353560 945004 main.go:141] libmachine: (old-k8s-version-233759)
I0224 13:17:28.353568 945004 main.go:141] libmachine: (old-k8s-version-233759) </devices>
I0224 13:17:28.353575 945004 main.go:141] libmachine: (old-k8s-version-233759) </domain>
I0224 13:17:28.353586 945004 main.go:141] libmachine: (old-k8s-version-233759)
I0224 13:17:28.358316 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:db:a8:2a in network default
I0224 13:17:28.359036 945004 main.go:141] libmachine: (old-k8s-version-233759) starting domain...
I0224 13:17:28.359060 945004 main.go:141] libmachine: (old-k8s-version-233759) ensuring networks are active...
I0224 13:17:28.359073 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:28.359965 945004 main.go:141] libmachine: (old-k8s-version-233759) Ensuring network default is active
I0224 13:17:28.360284 945004 main.go:141] libmachine: (old-k8s-version-233759) Ensuring network mk-old-k8s-version-233759 is active
I0224 13:17:28.360917 945004 main.go:141] libmachine: (old-k8s-version-233759) getting domain XML...
I0224 13:17:28.361871 945004 main.go:141] libmachine: (old-k8s-version-233759) creating domain...
I0224 13:17:29.886797 945004 main.go:141] libmachine: (old-k8s-version-233759) waiting for IP...
I0224 13:17:29.887724 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:29.888350 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | unable to find current IP address of domain old-k8s-version-233759 in network mk-old-k8s-version-233759
I0224 13:17:29.888445 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | I0224 13:17:29.888339 945120 retry.go:31] will retry after 303.200538ms: waiting for domain to come up
I0224 13:17:30.192931 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:30.193619 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | unable to find current IP address of domain old-k8s-version-233759 in network mk-old-k8s-version-233759
I0224 13:17:30.193652 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | I0224 13:17:30.193536 945120 retry.go:31] will retry after 283.160935ms: waiting for domain to come up
I0224 13:17:30.479651 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:30.481371 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | unable to find current IP address of domain old-k8s-version-233759 in network mk-old-k8s-version-233759
I0224 13:17:30.481503 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | I0224 13:17:30.481223 945120 retry.go:31] will retry after 431.155314ms: waiting for domain to come up
I0224 13:17:30.919957 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:30.921790 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | unable to find current IP address of domain old-k8s-version-233759 in network mk-old-k8s-version-233759
I0224 13:17:30.921820 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | I0224 13:17:30.921488 945120 retry.go:31] will retry after 405.534023ms: waiting for domain to come up
I0224 13:17:31.328495 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:31.329165 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | unable to find current IP address of domain old-k8s-version-233759 in network mk-old-k8s-version-233759
I0224 13:17:31.329195 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | I0224 13:17:31.329073 945120 retry.go:31] will retry after 688.860859ms: waiting for domain to come up
I0224 13:17:32.019628 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:32.020357 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | unable to find current IP address of domain old-k8s-version-233759 in network mk-old-k8s-version-233759
I0224 13:17:32.020397 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | I0224 13:17:32.020249 945120 retry.go:31] will retry after 689.039505ms: waiting for domain to come up
I0224 13:17:32.710929 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:32.711886 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | unable to find current IP address of domain old-k8s-version-233759 in network mk-old-k8s-version-233759
I0224 13:17:32.711922 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | I0224 13:17:32.711826 945120 retry.go:31] will retry after 943.914165ms: waiting for domain to come up
I0224 13:17:33.657784 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:33.658421 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | unable to find current IP address of domain old-k8s-version-233759 in network mk-old-k8s-version-233759
I0224 13:17:33.658454 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | I0224 13:17:33.658369 945120 retry.go:31] will retry after 1.170515464s: waiting for domain to come up
I0224 13:17:34.830568 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:34.831166 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | unable to find current IP address of domain old-k8s-version-233759 in network mk-old-k8s-version-233759
I0224 13:17:34.831195 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | I0224 13:17:34.831109 945120 retry.go:31] will retry after 1.769736633s: waiting for domain to come up
I0224 13:17:36.602705 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:36.603308 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | unable to find current IP address of domain old-k8s-version-233759 in network mk-old-k8s-version-233759
I0224 13:17:36.603369 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | I0224 13:17:36.603269 945120 retry.go:31] will retry after 2.127975088s: waiting for domain to come up
I0224 13:17:38.732692 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:38.733297 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | unable to find current IP address of domain old-k8s-version-233759 in network mk-old-k8s-version-233759
I0224 13:17:38.733395 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | I0224 13:17:38.733288 945120 retry.go:31] will retry after 2.009247602s: waiting for domain to come up
I0224 13:17:40.745296 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:40.745911 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | unable to find current IP address of domain old-k8s-version-233759 in network mk-old-k8s-version-233759
I0224 13:17:40.746000 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | I0224 13:17:40.745906 945120 retry.go:31] will retry after 3.432197671s: waiting for domain to come up
I0224 13:17:44.179450 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:44.179938 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | unable to find current IP address of domain old-k8s-version-233759 in network mk-old-k8s-version-233759
I0224 13:17:44.179968 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | I0224 13:17:44.179894 945120 retry.go:31] will retry after 2.947733435s: waiting for domain to come up
I0224 13:17:47.131058 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:47.131623 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | unable to find current IP address of domain old-k8s-version-233759 in network mk-old-k8s-version-233759
I0224 13:17:47.131658 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | I0224 13:17:47.131601 945120 retry.go:31] will retry after 4.839258566s: waiting for domain to come up
I0224 13:17:51.978765 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:51.979917 945004 main.go:141] libmachine: (old-k8s-version-233759) found domain IP: 192.168.50.62
I0224 13:17:51.979939 945004 main.go:141] libmachine: (old-k8s-version-233759) reserving static IP address...
I0224 13:17:51.979992 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has current primary IP address 192.168.50.62 and MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:51.980907 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | unable to find host DHCP lease matching {name: "old-k8s-version-233759", mac: "52:54:00:cd:a9:f6", ip: "192.168.50.62"} in network mk-old-k8s-version-233759
I0224 13:17:52.141888 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | Getting to WaitForSSH function...
I0224 13:17:52.141947 945004 main.go:141] libmachine: (old-k8s-version-233759) reserved static IP address 192.168.50.62 for domain old-k8s-version-233759
I0224 13:17:52.141970 945004 main.go:141] libmachine: (old-k8s-version-233759) waiting for SSH...
I0224 13:17:52.160494 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:52.160530 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:cd:a9:f6", ip: ""} in network mk-old-k8s-version-233759: {Iface:virbr2 ExpiryTime:2025-02-24 14:17:45 +0000 UTC Type:0 Mac:52:54:00:cd:a9:f6 Iaid: IPaddr:192.168.50.62 Prefix:24 Hostname:minikube Clientid:01:52:54:00:cd:a9:f6}
I0224 13:17:52.160549 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined IP address 192.168.50.62 and MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:52.161736 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | Using SSH client type: external
I0224 13:17:52.161764 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | Using SSH private key: /home/jenkins/minikube-integration/20451-887294/.minikube/machines/old-k8s-version-233759/id_rsa (-rw-------)
I0224 13:17:52.161796 945004 main.go:141] libmachine: (old-k8s-version-233759) 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.50.62 -o IdentitiesOnly=yes -i /home/jenkins/minikube-integration/20451-887294/.minikube/machines/old-k8s-version-233759/id_rsa -p 22] /usr/bin/ssh <nil>}
I0224 13:17:52.161805 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | About to run SSH command:
I0224 13:17:52.161817 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | exit 0
I0224 13:17:52.314521 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | SSH cmd err, output: <nil>:
I0224 13:17:52.314807 945004 main.go:141] libmachine: (old-k8s-version-233759) KVM machine creation complete
I0224 13:17:52.315225 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetConfigRaw
I0224 13:17:52.316095 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .DriverName
I0224 13:17:52.316392 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .DriverName
I0224 13:17:52.316640 945004 main.go:141] libmachine: Waiting for machine to be running, this may take a few minutes...
I0224 13:17:52.316660 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetState
I0224 13:17:52.319149 945004 main.go:141] libmachine: Detecting operating system of created instance...
I0224 13:17:52.319168 945004 main.go:141] libmachine: Waiting for SSH to be available...
I0224 13:17:52.319175 945004 main.go:141] libmachine: Getting to WaitForSSH function...
I0224 13:17:52.319183 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHHostname
I0224 13:17:52.325888 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:52.327199 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:cd:a9:f6", ip: ""} in network mk-old-k8s-version-233759: {Iface:virbr2 ExpiryTime:2025-02-24 14:17:45 +0000 UTC Type:0 Mac:52:54:00:cd:a9:f6 Iaid: IPaddr:192.168.50.62 Prefix:24 Hostname:old-k8s-version-233759 Clientid:01:52:54:00:cd:a9:f6}
I0224 13:17:52.327231 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined IP address 192.168.50.62 and MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:52.329576 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHPort
I0224 13:17:52.329810 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHKeyPath
I0224 13:17:52.329957 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHKeyPath
I0224 13:17:52.330130 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHUsername
I0224 13:17:52.330302 945004 main.go:141] libmachine: Using SSH client type: native
I0224 13:17:52.330575 945004 main.go:141] libmachine: &{{{<nil> 0 [] [] []} docker [0x865ca0] 0x868980 <nil> [] 0s} 192.168.50.62 22 <nil> <nil>}
I0224 13:17:52.330585 945004 main.go:141] libmachine: About to run SSH command:
exit 0
I0224 13:17:52.471197 945004 main.go:141] libmachine: SSH cmd err, output: <nil>:
I0224 13:17:52.471231 945004 main.go:141] libmachine: Detecting the provisioner...
I0224 13:17:52.471243 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHHostname
I0224 13:17:52.475214 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:52.475811 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:cd:a9:f6", ip: ""} in network mk-old-k8s-version-233759: {Iface:virbr2 ExpiryTime:2025-02-24 14:17:45 +0000 UTC Type:0 Mac:52:54:00:cd:a9:f6 Iaid: IPaddr:192.168.50.62 Prefix:24 Hostname:old-k8s-version-233759 Clientid:01:52:54:00:cd:a9:f6}
I0224 13:17:52.475848 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined IP address 192.168.50.62 and MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:52.476182 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHPort
I0224 13:17:52.476376 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHKeyPath
I0224 13:17:52.476636 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHKeyPath
I0224 13:17:52.476813 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHUsername
I0224 13:17:52.477010 945004 main.go:141] libmachine: Using SSH client type: native
I0224 13:17:52.477252 945004 main.go:141] libmachine: &{{{<nil> 0 [] [] []} docker [0x865ca0] 0x868980 <nil> [] 0s} 192.168.50.62 22 <nil> <nil>}
I0224 13:17:52.477265 945004 main.go:141] libmachine: About to run SSH command:
cat /etc/os-release
I0224 13:17:52.662099 945004 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"
I0224 13:17:52.662194 945004 main.go:141] libmachine: found compatible host: buildroot
I0224 13:17:52.662204 945004 main.go:141] libmachine: Provisioning with buildroot...
I0224 13:17:52.662216 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetMachineName
I0224 13:17:52.662524 945004 buildroot.go:166] provisioning hostname "old-k8s-version-233759"
I0224 13:17:52.662551 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetMachineName
I0224 13:17:52.662732 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHHostname
I0224 13:17:52.668638 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:52.669352 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:cd:a9:f6", ip: ""} in network mk-old-k8s-version-233759: {Iface:virbr2 ExpiryTime:2025-02-24 14:17:45 +0000 UTC Type:0 Mac:52:54:00:cd:a9:f6 Iaid: IPaddr:192.168.50.62 Prefix:24 Hostname:old-k8s-version-233759 Clientid:01:52:54:00:cd:a9:f6}
I0224 13:17:52.669379 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined IP address 192.168.50.62 and MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:52.669631 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHPort
I0224 13:17:52.669813 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHKeyPath
I0224 13:17:52.669960 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHKeyPath
I0224 13:17:52.670074 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHUsername
I0224 13:17:52.670238 945004 main.go:141] libmachine: Using SSH client type: native
I0224 13:17:52.670490 945004 main.go:141] libmachine: &{{{<nil> 0 [] [] []} docker [0x865ca0] 0x868980 <nil> [] 0s} 192.168.50.62 22 <nil> <nil>}
I0224 13:17:52.670503 945004 main.go:141] libmachine: About to run SSH command:
sudo hostname old-k8s-version-233759 && echo "old-k8s-version-233759" | sudo tee /etc/hostname
I0224 13:17:52.842524 945004 main.go:141] libmachine: SSH cmd err, output: <nil>: old-k8s-version-233759
I0224 13:17:52.842564 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHHostname
I0224 13:17:52.846380 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:52.846869 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:cd:a9:f6", ip: ""} in network mk-old-k8s-version-233759: {Iface:virbr2 ExpiryTime:2025-02-24 14:17:45 +0000 UTC Type:0 Mac:52:54:00:cd:a9:f6 Iaid: IPaddr:192.168.50.62 Prefix:24 Hostname:old-k8s-version-233759 Clientid:01:52:54:00:cd:a9:f6}
I0224 13:17:52.846899 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined IP address 192.168.50.62 and MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:52.847439 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHPort
I0224 13:17:52.847666 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHKeyPath
I0224 13:17:52.847808 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHKeyPath
I0224 13:17:52.847940 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHUsername
I0224 13:17:52.848128 945004 main.go:141] libmachine: Using SSH client type: native
I0224 13:17:52.848348 945004 main.go:141] libmachine: &{{{<nil> 0 [] [] []} docker [0x865ca0] 0x868980 <nil> [] 0s} 192.168.50.62 22 <nil> <nil>}
I0224 13:17:52.848370 945004 main.go:141] libmachine: About to run SSH command:
if ! grep -xq '.*\sold-k8s-version-233759' /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-233759/g' /etc/hosts;
else
echo '127.0.1.1 old-k8s-version-233759' | sudo tee -a /etc/hosts;
fi
fi
I0224 13:17:53.010876 945004 main.go:141] libmachine: SSH cmd err, output: <nil>:
I0224 13:17:53.010912 945004 buildroot.go:172] set auth options {CertDir:/home/jenkins/minikube-integration/20451-887294/.minikube CaCertPath:/home/jenkins/minikube-integration/20451-887294/.minikube/certs/ca.pem CaPrivateKeyPath:/home/jenkins/minikube-integration/20451-887294/.minikube/certs/ca-key.pem CaCertRemotePath:/etc/docker/ca.pem ServerCertPath:/home/jenkins/minikube-integration/20451-887294/.minikube/machines/server.pem ServerKeyPath:/home/jenkins/minikube-integration/20451-887294/.minikube/machines/server-key.pem ClientKeyPath:/home/jenkins/minikube-integration/20451-887294/.minikube/certs/key.pem ServerCertRemotePath:/etc/docker/server.pem ServerKeyRemotePath:/etc/docker/server-key.pem ClientCertPath:/home/jenkins/minikube-integration/20451-887294/.minikube/certs/cert.pem ServerCertSANs:[] StorePath:/home/jenkins/minikube-integration/20451-887294/.minikube}
I0224 13:17:53.010935 945004 buildroot.go:174] setting up certificates
I0224 13:17:53.010949 945004 provision.go:84] configureAuth start
I0224 13:17:53.010962 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetMachineName
I0224 13:17:53.011310 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetIP
I0224 13:17:53.049366 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:53.051782 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:cd:a9:f6", ip: ""} in network mk-old-k8s-version-233759: {Iface:virbr2 ExpiryTime:2025-02-24 14:17:45 +0000 UTC Type:0 Mac:52:54:00:cd:a9:f6 Iaid: IPaddr:192.168.50.62 Prefix:24 Hostname:old-k8s-version-233759 Clientid:01:52:54:00:cd:a9:f6}
I0224 13:17:53.051830 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined IP address 192.168.50.62 and MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:53.052168 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHHostname
I0224 13:17:53.055074 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:53.056030 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:cd:a9:f6", ip: ""} in network mk-old-k8s-version-233759: {Iface:virbr2 ExpiryTime:2025-02-24 14:17:45 +0000 UTC Type:0 Mac:52:54:00:cd:a9:f6 Iaid: IPaddr:192.168.50.62 Prefix:24 Hostname:old-k8s-version-233759 Clientid:01:52:54:00:cd:a9:f6}
I0224 13:17:53.056058 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined IP address 192.168.50.62 and MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:53.056311 945004 provision.go:143] copyHostCerts
I0224 13:17:53.056381 945004 exec_runner.go:144] found /home/jenkins/minikube-integration/20451-887294/.minikube/key.pem, removing ...
I0224 13:17:53.056391 945004 exec_runner.go:203] rm: /home/jenkins/minikube-integration/20451-887294/.minikube/key.pem
I0224 13:17:53.056475 945004 exec_runner.go:151] cp: /home/jenkins/minikube-integration/20451-887294/.minikube/certs/key.pem --> /home/jenkins/minikube-integration/20451-887294/.minikube/key.pem (1679 bytes)
I0224 13:17:53.056612 945004 exec_runner.go:144] found /home/jenkins/minikube-integration/20451-887294/.minikube/ca.pem, removing ...
I0224 13:17:53.056623 945004 exec_runner.go:203] rm: /home/jenkins/minikube-integration/20451-887294/.minikube/ca.pem
I0224 13:17:53.056656 945004 exec_runner.go:151] cp: /home/jenkins/minikube-integration/20451-887294/.minikube/certs/ca.pem --> /home/jenkins/minikube-integration/20451-887294/.minikube/ca.pem (1082 bytes)
I0224 13:17:53.056725 945004 exec_runner.go:144] found /home/jenkins/minikube-integration/20451-887294/.minikube/cert.pem, removing ...
I0224 13:17:53.056731 945004 exec_runner.go:203] rm: /home/jenkins/minikube-integration/20451-887294/.minikube/cert.pem
I0224 13:17:53.056753 945004 exec_runner.go:151] cp: /home/jenkins/minikube-integration/20451-887294/.minikube/certs/cert.pem --> /home/jenkins/minikube-integration/20451-887294/.minikube/cert.pem (1123 bytes)
I0224 13:17:53.056819 945004 provision.go:117] generating server cert: /home/jenkins/minikube-integration/20451-887294/.minikube/machines/server.pem ca-key=/home/jenkins/minikube-integration/20451-887294/.minikube/certs/ca.pem private-key=/home/jenkins/minikube-integration/20451-887294/.minikube/certs/ca-key.pem org=jenkins.old-k8s-version-233759 san=[127.0.0.1 192.168.50.62 localhost minikube old-k8s-version-233759]
I0224 13:17:53.306354 945004 provision.go:177] copyRemoteCerts
I0224 13:17:53.306479 945004 ssh_runner.go:195] Run: sudo mkdir -p /etc/docker /etc/docker /etc/docker
I0224 13:17:53.306537 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHHostname
I0224 13:17:53.309920 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:53.310434 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:cd:a9:f6", ip: ""} in network mk-old-k8s-version-233759: {Iface:virbr2 ExpiryTime:2025-02-24 14:17:45 +0000 UTC Type:0 Mac:52:54:00:cd:a9:f6 Iaid: IPaddr:192.168.50.62 Prefix:24 Hostname:old-k8s-version-233759 Clientid:01:52:54:00:cd:a9:f6}
I0224 13:17:53.310485 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined IP address 192.168.50.62 and MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:53.310720 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHPort
I0224 13:17:53.310916 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHKeyPath
I0224 13:17:53.311067 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHUsername
I0224 13:17:53.311219 945004 sshutil.go:53] new ssh client: &{IP:192.168.50.62 Port:22 SSHKeyPath:/home/jenkins/minikube-integration/20451-887294/.minikube/machines/old-k8s-version-233759/id_rsa Username:docker}
I0224 13:17:53.448296 945004 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20451-887294/.minikube/certs/ca.pem --> /etc/docker/ca.pem (1082 bytes)
I0224 13:17:53.499693 945004 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20451-887294/.minikube/machines/server.pem --> /etc/docker/server.pem (1233 bytes)
I0224 13:17:53.545730 945004 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20451-887294/.minikube/machines/server-key.pem --> /etc/docker/server-key.pem (1679 bytes)
I0224 13:17:53.598012 945004 provision.go:87] duration metric: took 587.047358ms to configureAuth
I0224 13:17:53.598048 945004 buildroot.go:189] setting minikube options for container-runtime
I0224 13:17:53.598298 945004 config.go:182] Loaded profile config "old-k8s-version-233759": Driver=kvm2, ContainerRuntime=crio, KubernetesVersion=v1.20.0
I0224 13:17:53.598396 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHHostname
I0224 13:17:53.604979 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:53.605661 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:cd:a9:f6", ip: ""} in network mk-old-k8s-version-233759: {Iface:virbr2 ExpiryTime:2025-02-24 14:17:45 +0000 UTC Type:0 Mac:52:54:00:cd:a9:f6 Iaid: IPaddr:192.168.50.62 Prefix:24 Hostname:old-k8s-version-233759 Clientid:01:52:54:00:cd:a9:f6}
I0224 13:17:53.605694 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined IP address 192.168.50.62 and MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:53.606083 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHPort
I0224 13:17:53.606293 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHKeyPath
I0224 13:17:53.606452 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHKeyPath
I0224 13:17:53.606587 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHUsername
I0224 13:17:53.606751 945004 main.go:141] libmachine: Using SSH client type: native
I0224 13:17:53.607004 945004 main.go:141] libmachine: &{{{<nil> 0 [] [] []} docker [0x865ca0] 0x868980 <nil> [] 0s} 192.168.50.62 22 <nil> <nil>}
I0224 13:17:53.607035 945004 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
I0224 13:17:53.953926 945004 main.go:141] libmachine: SSH cmd err, output: <nil>:
CRIO_MINIKUBE_OPTIONS='--insecure-registry 10.96.0.0/12 '
I0224 13:17:53.953957 945004 main.go:141] libmachine: Checking connection to Docker...
I0224 13:17:53.953968 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetURL
I0224 13:17:53.958647 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | using libvirt version 6000000
I0224 13:17:53.961627 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:53.962069 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:cd:a9:f6", ip: ""} in network mk-old-k8s-version-233759: {Iface:virbr2 ExpiryTime:2025-02-24 14:17:45 +0000 UTC Type:0 Mac:52:54:00:cd:a9:f6 Iaid: IPaddr:192.168.50.62 Prefix:24 Hostname:old-k8s-version-233759 Clientid:01:52:54:00:cd:a9:f6}
I0224 13:17:53.962096 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined IP address 192.168.50.62 and MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:53.962516 945004 main.go:141] libmachine: Docker is up and running!
I0224 13:17:53.962532 945004 main.go:141] libmachine: Reticulating splines...
I0224 13:17:53.962540 945004 client.go:171] duration metric: took 26.081034577s to LocalClient.Create
I0224 13:17:53.962565 945004 start.go:167] duration metric: took 26.081111938s to libmachine.API.Create "old-k8s-version-233759"
I0224 13:17:53.962578 945004 start.go:293] postStartSetup for "old-k8s-version-233759" (driver="kvm2")
I0224 13:17:53.962594 945004 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]
I0224 13:17:53.962624 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .DriverName
I0224 13:17:53.962956 945004 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
I0224 13:17:53.962988 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHHostname
I0224 13:17:53.967171 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:53.967658 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:cd:a9:f6", ip: ""} in network mk-old-k8s-version-233759: {Iface:virbr2 ExpiryTime:2025-02-24 14:17:45 +0000 UTC Type:0 Mac:52:54:00:cd:a9:f6 Iaid: IPaddr:192.168.50.62 Prefix:24 Hostname:old-k8s-version-233759 Clientid:01:52:54:00:cd:a9:f6}
I0224 13:17:53.967693 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined IP address 192.168.50.62 and MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:53.967914 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHPort
I0224 13:17:53.968096 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHKeyPath
I0224 13:17:53.968248 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHUsername
I0224 13:17:53.968349 945004 sshutil.go:53] new ssh client: &{IP:192.168.50.62 Port:22 SSHKeyPath:/home/jenkins/minikube-integration/20451-887294/.minikube/machines/old-k8s-version-233759/id_rsa Username:docker}
I0224 13:17:54.114753 945004 ssh_runner.go:195] Run: cat /etc/os-release
I0224 13:17:54.133682 945004 info.go:137] Remote host: Buildroot 2023.02.9
I0224 13:17:54.133719 945004 filesync.go:126] Scanning /home/jenkins/minikube-integration/20451-887294/.minikube/addons for local assets ...
I0224 13:17:54.133824 945004 filesync.go:126] Scanning /home/jenkins/minikube-integration/20451-887294/.minikube/files for local assets ...
I0224 13:17:54.133924 945004 filesync.go:149] local asset: /home/jenkins/minikube-integration/20451-887294/.minikube/files/etc/ssl/certs/8945642.pem -> 8945642.pem in /etc/ssl/certs
I0224 13:17:54.134055 945004 ssh_runner.go:195] Run: sudo mkdir -p /etc/ssl/certs
I0224 13:17:54.158449 945004 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20451-887294/.minikube/files/etc/ssl/certs/8945642.pem --> /etc/ssl/certs/8945642.pem (1708 bytes)
I0224 13:17:54.203188 945004 start.go:296] duration metric: took 240.588266ms for postStartSetup
I0224 13:17:54.203256 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetConfigRaw
I0224 13:17:54.204135 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetIP
I0224 13:17:54.208651 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:54.209357 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:cd:a9:f6", ip: ""} in network mk-old-k8s-version-233759: {Iface:virbr2 ExpiryTime:2025-02-24 14:17:45 +0000 UTC Type:0 Mac:52:54:00:cd:a9:f6 Iaid: IPaddr:192.168.50.62 Prefix:24 Hostname:old-k8s-version-233759 Clientid:01:52:54:00:cd:a9:f6}
I0224 13:17:54.209391 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined IP address 192.168.50.62 and MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:54.209823 945004 profile.go:143] Saving config to /home/jenkins/minikube-integration/20451-887294/.minikube/profiles/old-k8s-version-233759/config.json ...
I0224 13:17:54.210100 945004 start.go:128] duration metric: took 26.350893185s to createHost
I0224 13:17:54.210131 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHHostname
I0224 13:17:54.213441 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:54.213893 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:cd:a9:f6", ip: ""} in network mk-old-k8s-version-233759: {Iface:virbr2 ExpiryTime:2025-02-24 14:17:45 +0000 UTC Type:0 Mac:52:54:00:cd:a9:f6 Iaid: IPaddr:192.168.50.62 Prefix:24 Hostname:old-k8s-version-233759 Clientid:01:52:54:00:cd:a9:f6}
I0224 13:17:54.213926 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined IP address 192.168.50.62 and MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:54.214192 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHPort
I0224 13:17:54.214421 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHKeyPath
I0224 13:17:54.214616 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHKeyPath
I0224 13:17:54.214787 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHUsername
I0224 13:17:54.215010 945004 main.go:141] libmachine: Using SSH client type: native
I0224 13:17:54.215246 945004 main.go:141] libmachine: &{{{<nil> 0 [] [] []} docker [0x865ca0] 0x868980 <nil> [] 0s} 192.168.50.62 22 <nil> <nil>}
I0224 13:17:54.215264 945004 main.go:141] libmachine: About to run SSH command:
date +%s.%N
I0224 13:17:54.373901 945004 main.go:141] libmachine: SSH cmd err, output: <nil>: 1740403074.350152857
I0224 13:17:54.373927 945004 fix.go:216] guest clock: 1740403074.350152857
I0224 13:17:54.373935 945004 fix.go:229] Guest: 2025-02-24 13:17:54.350152857 +0000 UTC Remote: 2025-02-24 13:17:54.210114228 +0000 UTC m=+38.509082179 (delta=140.038629ms)
I0224 13:17:54.373961 945004 fix.go:200] guest clock delta is within tolerance: 140.038629ms
I0224 13:17:54.373973 945004 start.go:83] releasing machines lock for "old-k8s-version-233759", held for 26.514978656s
I0224 13:17:54.373999 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .DriverName
I0224 13:17:54.376016 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetIP
I0224 13:17:54.380430 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:54.380851 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:cd:a9:f6", ip: ""} in network mk-old-k8s-version-233759: {Iface:virbr2 ExpiryTime:2025-02-24 14:17:45 +0000 UTC Type:0 Mac:52:54:00:cd:a9:f6 Iaid: IPaddr:192.168.50.62 Prefix:24 Hostname:old-k8s-version-233759 Clientid:01:52:54:00:cd:a9:f6}
I0224 13:17:54.380889 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined IP address 192.168.50.62 and MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:54.381391 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .DriverName
I0224 13:17:54.382027 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .DriverName
I0224 13:17:54.382244 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .DriverName
I0224 13:17:54.382318 945004 ssh_runner.go:195] Run: curl -sS -m 2 https://registry.k8s.io/
I0224 13:17:54.382370 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHHostname
I0224 13:17:54.382618 945004 ssh_runner.go:195] Run: cat /version.json
I0224 13:17:54.382650 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHHostname
I0224 13:17:54.386743 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:54.387110 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:cd:a9:f6", ip: ""} in network mk-old-k8s-version-233759: {Iface:virbr2 ExpiryTime:2025-02-24 14:17:45 +0000 UTC Type:0 Mac:52:54:00:cd:a9:f6 Iaid: IPaddr:192.168.50.62 Prefix:24 Hostname:old-k8s-version-233759 Clientid:01:52:54:00:cd:a9:f6}
I0224 13:17:54.387139 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined IP address 192.168.50.62 and MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:54.387831 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHPort
I0224 13:17:54.388430 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHKeyPath
I0224 13:17:54.388634 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHUsername
I0224 13:17:54.388810 945004 sshutil.go:53] new ssh client: &{IP:192.168.50.62 Port:22 SSHKeyPath:/home/jenkins/minikube-integration/20451-887294/.minikube/machines/old-k8s-version-233759/id_rsa Username:docker}
I0224 13:17:54.396179 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:54.396303 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:cd:a9:f6", ip: ""} in network mk-old-k8s-version-233759: {Iface:virbr2 ExpiryTime:2025-02-24 14:17:45 +0000 UTC Type:0 Mac:52:54:00:cd:a9:f6 Iaid: IPaddr:192.168.50.62 Prefix:24 Hostname:old-k8s-version-233759 Clientid:01:52:54:00:cd:a9:f6}
I0224 13:17:54.396334 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined IP address 192.168.50.62 and MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:54.396543 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHPort
I0224 13:17:54.396787 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHKeyPath
I0224 13:17:54.396970 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetSSHUsername
I0224 13:17:54.397183 945004 sshutil.go:53] new ssh client: &{IP:192.168.50.62 Port:22 SSHKeyPath:/home/jenkins/minikube-integration/20451-887294/.minikube/machines/old-k8s-version-233759/id_rsa Username:docker}
I0224 13:17:54.500508 945004 ssh_runner.go:195] Run: systemctl --version
I0224 13:17:54.508444 945004 ssh_runner.go:195] Run: sudo sh -c "podman version >/dev/null"
I0224 13:17:54.771322 945004 ssh_runner.go:195] Run: sh -c "stat /etc/cni/net.d/*loopback.conf*"
W0224 13:17:54.785669 945004 cni.go:209] loopback cni configuration skipped: "/etc/cni/net.d/*loopback.conf*" not found
I0224 13:17:54.785753 945004 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" ;
I0224 13:17:54.825480 945004 cni.go:262] disabled [/etc/cni/net.d/87-podman-bridge.conflist] bridge cni config(s)
I0224 13:17:54.825514 945004 start.go:495] detecting cgroup driver to use...
I0224 13:17:54.825597 945004 ssh_runner.go:195] Run: sudo systemctl stop -f containerd
I0224 13:17:54.849931 945004 ssh_runner.go:195] Run: sudo systemctl is-active --quiet service containerd
I0224 13:17:54.870586 945004 docker.go:217] disabling cri-docker service (if available) ...
I0224 13:17:54.870643 945004 ssh_runner.go:195] Run: sudo systemctl stop -f cri-docker.socket
I0224 13:17:54.889741 945004 ssh_runner.go:195] Run: sudo systemctl stop -f cri-docker.service
I0224 13:17:54.910249 945004 ssh_runner.go:195] Run: sudo systemctl disable cri-docker.socket
I0224 13:17:55.092703 945004 ssh_runner.go:195] Run: sudo systemctl mask cri-docker.service
I0224 13:17:55.309600 945004 docker.go:233] disabling docker service ...
I0224 13:17:55.309682 945004 ssh_runner.go:195] Run: sudo systemctl stop -f docker.socket
I0224 13:17:55.335052 945004 ssh_runner.go:195] Run: sudo systemctl stop -f docker.service
I0224 13:17:55.351706 945004 ssh_runner.go:195] Run: sudo systemctl disable docker.socket
I0224 13:17:55.513009 945004 ssh_runner.go:195] Run: sudo systemctl mask docker.service
I0224 13:17:55.656811 945004 ssh_runner.go:195] Run: sudo systemctl is-active --quiet service docker
I0224 13:17:55.673154 945004 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"
I0224 13:17:55.699944 945004 crio.go:59] configure cri-o to use "registry.k8s.io/pause:3.2" pause image...
I0224 13:17:55.700011 945004 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"
I0224 13:17:55.714897 945004 crio.go:70] configuring cri-o to use "cgroupfs" as cgroup driver...
I0224 13:17:55.714994 945004 ssh_runner.go:195] Run: sh -c "sudo sed -i 's|^.*cgroup_manager = .*$|cgroup_manager = "cgroupfs"|' /etc/crio/crio.conf.d/02-crio.conf"
I0224 13:17:55.727627 945004 ssh_runner.go:195] Run: sh -c "sudo sed -i '/conmon_cgroup = .*/d' /etc/crio/crio.conf.d/02-crio.conf"
I0224 13:17:55.741411 945004 ssh_runner.go:195] Run: sh -c "sudo sed -i '/cgroup_manager = .*/a conmon_cgroup = "pod"' /etc/crio/crio.conf.d/02-crio.conf"
I0224 13:17:55.753525 945004 ssh_runner.go:195] Run: sh -c "sudo rm -rf /etc/cni/net.mk"
I0224 13:17:55.765249 945004 ssh_runner.go:195] Run: sudo sysctl net.bridge.bridge-nf-call-iptables
I0224 13:17:55.775604 945004 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
I0224 13:17:55.775683 945004 ssh_runner.go:195] Run: sudo modprobe br_netfilter
I0224 13:17:55.791615 945004 ssh_runner.go:195] Run: sudo sh -c "echo 1 > /proc/sys/net/ipv4/ip_forward"
I0224 13:17:55.803928 945004 ssh_runner.go:195] Run: sudo systemctl daemon-reload
I0224 13:17:55.965378 945004 ssh_runner.go:195] Run: sudo systemctl restart crio
I0224 13:17:56.096758 945004 start.go:542] Will wait 60s for socket path /var/run/crio/crio.sock
I0224 13:17:56.096841 945004 ssh_runner.go:195] Run: stat /var/run/crio/crio.sock
I0224 13:17:56.103941 945004 start.go:563] Will wait 60s for crictl version
I0224 13:17:56.104011 945004 ssh_runner.go:195] Run: which crictl
I0224 13:17:56.109077 945004 ssh_runner.go:195] Run: sudo /usr/bin/crictl version
I0224 13:17:56.158314 945004 start.go:579] Version: 0.1.0
RuntimeName: cri-o
RuntimeVersion: 1.29.1
RuntimeApiVersion: v1
I0224 13:17:56.158424 945004 ssh_runner.go:195] Run: crio --version
I0224 13:17:56.191215 945004 ssh_runner.go:195] Run: crio --version
I0224 13:17:56.224896 945004 out.go:177] * Preparing Kubernetes v1.20.0 on CRI-O 1.29.1 ...
I0224 13:17:56.226406 945004 main.go:141] libmachine: (old-k8s-version-233759) Calling .GetIP
I0224 13:17:56.229684 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:56.230159 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:cd:a9:f6", ip: ""} in network mk-old-k8s-version-233759: {Iface:virbr2 ExpiryTime:2025-02-24 14:17:45 +0000 UTC Type:0 Mac:52:54:00:cd:a9:f6 Iaid: IPaddr:192.168.50.62 Prefix:24 Hostname:old-k8s-version-233759 Clientid:01:52:54:00:cd:a9:f6}
I0224 13:17:56.230192 945004 main.go:141] libmachine: (old-k8s-version-233759) DBG | domain old-k8s-version-233759 has defined IP address 192.168.50.62 and MAC address 52:54:00:cd:a9:f6 in network mk-old-k8s-version-233759
I0224 13:17:56.230460 945004 ssh_runner.go:195] Run: grep 192.168.50.1 host.minikube.internal$ /etc/hosts
I0224 13:17:56.236322 945004 ssh_runner.go:195] Run: /bin/bash -c "{ grep -v $'\thost.minikube.internal$' "/etc/hosts"; echo "192.168.50.1 host.minikube.internal"; } > /tmp/h.$$; sudo cp /tmp/h.$$ "/etc/hosts""
I0224 13:17:56.251231 945004 kubeadm.go:883] updating cluster {Name:old-k8s-version-233759 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-1740046583-20436@sha256:b4324ef42fab4e243d39dd69028f243606b2fa4379f6ec916c89e512f68338f4 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-233759 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.50.62 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} ...
I0224 13:17:56.251394 945004 preload.go:131] Checking if preload exists for k8s version v1.20.0 and runtime crio
I0224 13:17:56.251467 945004 ssh_runner.go:195] Run: sudo crictl images --output json
I0224 13:17:56.291390 945004 crio.go:510] couldn't find preloaded image for "registry.k8s.io/kube-apiserver:v1.20.0". assuming images are not preloaded.
I0224 13:17:56.291479 945004 ssh_runner.go:195] Run: which lz4
I0224 13:17:56.295985 945004 ssh_runner.go:195] Run: stat -c "%s %y" /preloaded.tar.lz4
I0224 13:17:56.301374 945004 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
I0224 13:17:56.301432 945004 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20451-887294/.minikube/cache/preloaded-tarball/preloaded-images-k8s-v18-v1.20.0-cri-o-overlay-amd64.tar.lz4 --> /preloaded.tar.lz4 (473237281 bytes)
I0224 13:17:58.186983 945004 crio.go:462] duration metric: took 1.891039595s to copy over tarball
I0224 13:17:58.187077 945004 ssh_runner.go:195] Run: sudo tar --xattrs --xattrs-include security.capability -I lz4 -C /var -xf /preloaded.tar.lz4
I0224 13:18:01.187997 945004 ssh_runner.go:235] Completed: sudo tar --xattrs --xattrs-include security.capability -I lz4 -C /var -xf /preloaded.tar.lz4: (3.000875101s)
I0224 13:18:01.188045 945004 crio.go:469] duration metric: took 3.001022456s to extract the tarball
I0224 13:18:01.188056 945004 ssh_runner.go:146] rm: /preloaded.tar.lz4
I0224 13:18:01.235493 945004 ssh_runner.go:195] Run: sudo crictl images --output json
I0224 13:18:01.291224 945004 crio.go:510] couldn't find preloaded image for "registry.k8s.io/kube-apiserver:v1.20.0". assuming images are not preloaded.
I0224 13:18:01.291257 945004 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]
I0224 13:18:01.291346 945004 image.go:135] retrieving image: registry.k8s.io/kube-proxy:v1.20.0
I0224 13:18:01.291384 945004 image.go:135] retrieving image: registry.k8s.io/etcd:3.4.13-0
I0224 13:18:01.291387 945004 image.go:135] retrieving image: registry.k8s.io/kube-scheduler:v1.20.0
I0224 13:18:01.291408 945004 image.go:135] retrieving image: registry.k8s.io/kube-controller-manager:v1.20.0
I0224 13:18:01.291335 945004 image.go:135] retrieving image: gcr.io/k8s-minikube/storage-provisioner:v5
I0224 13:18:01.291457 945004 image.go:135] retrieving image: registry.k8s.io/kube-apiserver:v1.20.0
I0224 13:18:01.291468 945004 image.go:135] retrieving image: registry.k8s.io/coredns:1.7.0
I0224 13:18:01.291374 945004 image.go:135] retrieving image: registry.k8s.io/pause:3.2
I0224 13:18:01.292827 945004 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
I0224 13:18:01.292827 945004 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
I0224 13:18:01.292859 945004 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
I0224 13:18:01.292900 945004 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
I0224 13:18:01.292829 945004 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
I0224 13:18:01.292829 945004 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
I0224 13:18:01.292833 945004 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
I0224 13:18:01.292831 945004 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
I0224 13:18:01.467016 945004 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} registry.k8s.io/etcd:3.4.13-0
I0224 13:18:01.474491 945004 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} registry.k8s.io/kube-controller-manager:v1.20.0
I0224 13:18:01.489091 945004 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} registry.k8s.io/pause:3.2
I0224 13:18:01.511769 945004 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} registry.k8s.io/kube-proxy:v1.20.0
I0224 13:18:01.529903 945004 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} registry.k8s.io/coredns:1.7.0
I0224 13:18:01.531106 945004 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} registry.k8s.io/kube-scheduler:v1.20.0
I0224 13:18:01.541731 945004 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} registry.k8s.io/kube-apiserver:v1.20.0
I0224 13:18:01.578785 945004 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
I0224 13:18:01.578841 945004 cri.go:218] Removing image: registry.k8s.io/kube-controller-manager:v1.20.0
I0224 13:18:01.578893 945004 ssh_runner.go:195] Run: which crictl
I0224 13:18:01.579302 945004 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
I0224 13:18:01.579363 945004 cri.go:218] Removing image: registry.k8s.io/etcd:3.4.13-0
I0224 13:18:01.579410 945004 ssh_runner.go:195] Run: which crictl
I0224 13:18:01.673882 945004 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
I0224 13:18:01.673942 945004 cri.go:218] Removing image: registry.k8s.io/pause:3.2
I0224 13:18:01.673994 945004 ssh_runner.go:195] Run: which crictl
I0224 13:18:01.694367 945004 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
I0224 13:18:01.694417 945004 cri.go:218] Removing image: registry.k8s.io/kube-proxy:v1.20.0
I0224 13:18:01.694461 945004 ssh_runner.go:195] Run: which crictl
I0224 13:18:01.708313 945004 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
I0224 13:18:01.708363 945004 cri.go:218] Removing image: registry.k8s.io/coredns:1.7.0
I0224 13:18:01.708393 945004 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
I0224 13:18:01.708420 945004 cri.go:218] Removing image: registry.k8s.io/kube-apiserver:v1.20.0
I0224 13:18:01.708431 945004 ssh_runner.go:195] Run: which crictl
I0224 13:18:01.708447 945004 ssh_runner.go:195] Run: which crictl
I0224 13:18:01.708500 945004 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-controller-manager:v1.20.0
I0224 13:18:01.708315 945004 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
I0224 13:18:01.708538 945004 cri.go:218] Removing image: registry.k8s.io/kube-scheduler:v1.20.0
I0224 13:18:01.708571 945004 ssh_runner.go:195] Run: which crictl
I0224 13:18:01.708579 945004 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/etcd:3.4.13-0
I0224 13:18:01.708622 945004 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/pause:3.2
I0224 13:18:01.708650 945004 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-proxy:v1.20.0
I0224 13:18:01.732902 945004 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-scheduler:v1.20.0
I0224 13:18:01.837346 945004 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-controller-manager:v1.20.0
I0224 13:18:01.851889 945004 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/coredns:1.7.0
I0224 13:18:01.852016 945004 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-proxy:v1.20.0
I0224 13:18:01.852036 945004 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-apiserver:v1.20.0
I0224 13:18:01.852049 945004 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/pause:3.2
I0224 13:18:01.857538 945004 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/etcd:3.4.13-0
I0224 13:18:01.890246 945004 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-scheduler:v1.20.0
I0224 13:18:02.025217 945004 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-controller-manager:v1.20.0
I0224 13:18:02.025272 945004 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/pause:3.2
I0224 13:18:02.039056 945004 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-proxy:v1.20.0
I0224 13:18:02.039137 945004 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/coredns:1.7.0
I0224 13:18:02.039187 945004 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/etcd:3.4.13-0
I0224 13:18:02.039137 945004 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-apiserver:v1.20.0
I0224 13:18:02.054781 945004 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-scheduler:v1.20.0
I0224 13:18:02.165346 945004 cache_images.go:289] Loading image from: /home/jenkins/minikube-integration/20451-887294/.minikube/cache/images/amd64/registry.k8s.io/kube-controller-manager_v1.20.0
I0224 13:18:02.198952 945004 cache_images.go:289] Loading image from: /home/jenkins/minikube-integration/20451-887294/.minikube/cache/images/amd64/registry.k8s.io/pause_3.2
I0224 13:18:02.222149 945004 cache_images.go:289] Loading image from: /home/jenkins/minikube-integration/20451-887294/.minikube/cache/images/amd64/registry.k8s.io/kube-proxy_v1.20.0
I0224 13:18:02.222231 945004 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/coredns:1.7.0
I0224 13:18:02.222278 945004 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-apiserver:v1.20.0
I0224 13:18:02.222306 945004 cache_images.go:289] Loading image from: /home/jenkins/minikube-integration/20451-887294/.minikube/cache/images/amd64/registry.k8s.io/etcd_3.4.13-0
I0224 13:18:02.222359 945004 cache_images.go:289] Loading image from: /home/jenkins/minikube-integration/20451-887294/.minikube/cache/images/amd64/registry.k8s.io/kube-scheduler_v1.20.0
I0224 13:18:02.281708 945004 cache_images.go:289] Loading image from: /home/jenkins/minikube-integration/20451-887294/.minikube/cache/images/amd64/registry.k8s.io/coredns_1.7.0
I0224 13:18:02.282743 945004 cache_images.go:289] Loading image from: /home/jenkins/minikube-integration/20451-887294/.minikube/cache/images/amd64/registry.k8s.io/kube-apiserver_v1.20.0
I0224 13:18:02.517668 945004 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} gcr.io/k8s-minikube/storage-provisioner:v5
I0224 13:18:02.668962 945004 cache_images.go:92] duration metric: took 1.377683538s to LoadCachedImages
W0224 13:18:02.669086 945004 out.go:270] X Unable to load cached images: LoadCachedImages: stat /home/jenkins/minikube-integration/20451-887294/.minikube/cache/images/amd64/registry.k8s.io/kube-controller-manager_v1.20.0: no such file or directory
X Unable to load cached images: LoadCachedImages: stat /home/jenkins/minikube-integration/20451-887294/.minikube/cache/images/amd64/registry.k8s.io/kube-controller-manager_v1.20.0: no such file or directory
I0224 13:18:02.669107 945004 kubeadm.go:934] updating node { 192.168.50.62 8443 v1.20.0 crio true true} ...
I0224 13:18:02.669251 945004 kubeadm.go:946] 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-233759 --kubeconfig=/etc/kubernetes/kubelet.conf --network-plugin=cni --node-ip=192.168.50.62
[Install]
config:
{KubernetesVersion:v1.20.0 ClusterName:old-k8s-version-233759 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:}
I0224 13:18:02.669362 945004 ssh_runner.go:195] Run: crio config
I0224 13:18:02.732105 945004 cni.go:84] Creating CNI manager for ""
I0224 13:18:02.732133 945004 cni.go:146] "kvm2" driver + "crio" runtime found, recommending bridge
I0224 13:18:02.732146 945004 kubeadm.go:84] Using pod CIDR: 10.244.0.0/16
I0224 13:18:02.732165 945004 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.50.62 APIServerPort:8443 KubernetesVersion:v1.20.0 EtcdDataDir:/var/lib/minikube/etcd EtcdExtraArgs:map[] ClusterName:old-k8s-version-233759 NodeName:old-k8s-version-233759 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.50.62"]]} {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.50.62 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}
I0224 13:18:02.732296 945004 kubeadm.go:195] kubeadm config:
apiVersion: kubeadm.k8s.io/v1beta2
kind: InitConfiguration
localAPIEndpoint:
advertiseAddress: 192.168.50.62
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-233759"
kubeletExtraArgs:
node-ip: 192.168.50.62
taints: []
---
apiVersion: kubeadm.k8s.io/v1beta2
kind: ClusterConfiguration
apiServer:
certSANs: ["127.0.0.1", "localhost", "192.168.50.62"]
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
I0224 13:18:02.732354 945004 ssh_runner.go:195] Run: sudo ls /var/lib/minikube/binaries/v1.20.0
I0224 13:18:02.743754 945004 binaries.go:44] Found k8s binaries, skipping transfer
I0224 13:18:02.743834 945004 ssh_runner.go:195] Run: sudo mkdir -p /etc/systemd/system/kubelet.service.d /lib/systemd/system /var/tmp/minikube
I0224 13:18:02.755843 945004 ssh_runner.go:362] scp memory --> /etc/systemd/system/kubelet.service.d/10-kubeadm.conf (429 bytes)
I0224 13:18:02.778032 945004 ssh_runner.go:362] scp memory --> /lib/systemd/system/kubelet.service (352 bytes)
I0224 13:18:02.800580 945004 ssh_runner.go:362] scp memory --> /var/tmp/minikube/kubeadm.yaml.new (2120 bytes)
I0224 13:18:02.822614 945004 ssh_runner.go:195] Run: grep 192.168.50.62 control-plane.minikube.internal$ /etc/hosts
I0224 13:18:02.828657 945004 ssh_runner.go:195] Run: /bin/bash -c "{ grep -v $'\tcontrol-plane.minikube.internal$' "/etc/hosts"; echo "192.168.50.62 control-plane.minikube.internal"; } > /tmp/h.$$; sudo cp /tmp/h.$$ "/etc/hosts""
I0224 13:18:02.846365 945004 ssh_runner.go:195] Run: sudo systemctl daemon-reload
I0224 13:18:02.999461 945004 ssh_runner.go:195] Run: sudo systemctl start kubelet
I0224 13:18:03.018785 945004 certs.go:68] Setting up /home/jenkins/minikube-integration/20451-887294/.minikube/profiles/old-k8s-version-233759 for IP: 192.168.50.62
I0224 13:18:03.018825 945004 certs.go:194] generating shared ca certs ...
I0224 13:18:03.018848 945004 certs.go:226] acquiring lock for ca certs: {Name:mk38777c6b180f63d1816020cff79a01106ddf33 Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0224 13:18:03.019045 945004 certs.go:235] skipping valid "minikubeCA" ca cert: /home/jenkins/minikube-integration/20451-887294/.minikube/ca.key
I0224 13:18:03.019103 945004 certs.go:235] skipping valid "proxyClientCA" ca cert: /home/jenkins/minikube-integration/20451-887294/.minikube/proxy-client-ca.key
I0224 13:18:03.019118 945004 certs.go:256] generating profile certs ...
I0224 13:18:03.019197 945004 certs.go:363] generating signed profile cert for "minikube-user": /home/jenkins/minikube-integration/20451-887294/.minikube/profiles/old-k8s-version-233759/client.key
I0224 13:18:03.019229 945004 crypto.go:68] Generating cert /home/jenkins/minikube-integration/20451-887294/.minikube/profiles/old-k8s-version-233759/client.crt with IP's: []
I0224 13:18:03.201466 945004 crypto.go:156] Writing cert to /home/jenkins/minikube-integration/20451-887294/.minikube/profiles/old-k8s-version-233759/client.crt ...
I0224 13:18:03.201500 945004 lock.go:35] WriteFile acquiring /home/jenkins/minikube-integration/20451-887294/.minikube/profiles/old-k8s-version-233759/client.crt: {Name:mk001e2a8dc5966322582bc822c20c2332b4560d Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0224 13:18:03.201701 945004 crypto.go:164] Writing key to /home/jenkins/minikube-integration/20451-887294/.minikube/profiles/old-k8s-version-233759/client.key ...
I0224 13:18:03.201716 945004 lock.go:35] WriteFile acquiring /home/jenkins/minikube-integration/20451-887294/.minikube/profiles/old-k8s-version-233759/client.key: {Name:mk09415b12227826438fe31f8751fa04619e4abf Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0224 13:18:03.201830 945004 certs.go:363] generating signed profile cert for "minikube": /home/jenkins/minikube-integration/20451-887294/.minikube/profiles/old-k8s-version-233759/apiserver.key.e3d4d6a2
I0224 13:18:03.201849 945004 crypto.go:68] Generating cert /home/jenkins/minikube-integration/20451-887294/.minikube/profiles/old-k8s-version-233759/apiserver.crt.e3d4d6a2 with IP's: [10.96.0.1 127.0.0.1 10.0.0.1 192.168.50.62]
I0224 13:18:03.417858 945004 crypto.go:156] Writing cert to /home/jenkins/minikube-integration/20451-887294/.minikube/profiles/old-k8s-version-233759/apiserver.crt.e3d4d6a2 ...
I0224 13:18:03.417900 945004 lock.go:35] WriteFile acquiring /home/jenkins/minikube-integration/20451-887294/.minikube/profiles/old-k8s-version-233759/apiserver.crt.e3d4d6a2: {Name:mk0b92438d6251322d9046df3750461465a983d2 Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0224 13:18:03.418091 945004 crypto.go:164] Writing key to /home/jenkins/minikube-integration/20451-887294/.minikube/profiles/old-k8s-version-233759/apiserver.key.e3d4d6a2 ...
I0224 13:18:03.418111 945004 lock.go:35] WriteFile acquiring /home/jenkins/minikube-integration/20451-887294/.minikube/profiles/old-k8s-version-233759/apiserver.key.e3d4d6a2: {Name:mkce48f0fc2c9f8c55dc36f706bf97ce392f169c Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0224 13:18:03.418220 945004 certs.go:381] copying /home/jenkins/minikube-integration/20451-887294/.minikube/profiles/old-k8s-version-233759/apiserver.crt.e3d4d6a2 -> /home/jenkins/minikube-integration/20451-887294/.minikube/profiles/old-k8s-version-233759/apiserver.crt
I0224 13:18:03.418329 945004 certs.go:385] copying /home/jenkins/minikube-integration/20451-887294/.minikube/profiles/old-k8s-version-233759/apiserver.key.e3d4d6a2 -> /home/jenkins/minikube-integration/20451-887294/.minikube/profiles/old-k8s-version-233759/apiserver.key
I0224 13:18:03.418414 945004 certs.go:363] generating signed profile cert for "aggregator": /home/jenkins/minikube-integration/20451-887294/.minikube/profiles/old-k8s-version-233759/proxy-client.key
I0224 13:18:03.418434 945004 crypto.go:68] Generating cert /home/jenkins/minikube-integration/20451-887294/.minikube/profiles/old-k8s-version-233759/proxy-client.crt with IP's: []
I0224 13:18:03.562529 945004 crypto.go:156] Writing cert to /home/jenkins/minikube-integration/20451-887294/.minikube/profiles/old-k8s-version-233759/proxy-client.crt ...
I0224 13:18:03.562582 945004 lock.go:35] WriteFile acquiring /home/jenkins/minikube-integration/20451-887294/.minikube/profiles/old-k8s-version-233759/proxy-client.crt: {Name:mka58cd88f5015ce0a03c89f2df585658f84c842 Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0224 13:18:03.562819 945004 crypto.go:164] Writing key to /home/jenkins/minikube-integration/20451-887294/.minikube/profiles/old-k8s-version-233759/proxy-client.key ...
I0224 13:18:03.562847 945004 lock.go:35] WriteFile acquiring /home/jenkins/minikube-integration/20451-887294/.minikube/profiles/old-k8s-version-233759/proxy-client.key: {Name:mk3e03c21de40f3db90eb877880fc296422fa9bb Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0224 13:18:03.563140 945004 certs.go:484] found cert: /home/jenkins/minikube-integration/20451-887294/.minikube/certs/894564.pem (1338 bytes)
W0224 13:18:03.563210 945004 certs.go:480] ignoring /home/jenkins/minikube-integration/20451-887294/.minikube/certs/894564_empty.pem, impossibly tiny 0 bytes
I0224 13:18:03.563226 945004 certs.go:484] found cert: /home/jenkins/minikube-integration/20451-887294/.minikube/certs/ca-key.pem (1679 bytes)
I0224 13:18:03.563259 945004 certs.go:484] found cert: /home/jenkins/minikube-integration/20451-887294/.minikube/certs/ca.pem (1082 bytes)
I0224 13:18:03.563293 945004 certs.go:484] found cert: /home/jenkins/minikube-integration/20451-887294/.minikube/certs/cert.pem (1123 bytes)
I0224 13:18:03.563324 945004 certs.go:484] found cert: /home/jenkins/minikube-integration/20451-887294/.minikube/certs/key.pem (1679 bytes)
I0224 13:18:03.563385 945004 certs.go:484] found cert: /home/jenkins/minikube-integration/20451-887294/.minikube/files/etc/ssl/certs/8945642.pem (1708 bytes)
I0224 13:18:03.564234 945004 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20451-887294/.minikube/ca.crt --> /var/lib/minikube/certs/ca.crt (1111 bytes)
I0224 13:18:03.596881 945004 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20451-887294/.minikube/ca.key --> /var/lib/minikube/certs/ca.key (1679 bytes)
I0224 13:18:03.626821 945004 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20451-887294/.minikube/proxy-client-ca.crt --> /var/lib/minikube/certs/proxy-client-ca.crt (1119 bytes)
I0224 13:18:03.658392 945004 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20451-887294/.minikube/proxy-client-ca.key --> /var/lib/minikube/certs/proxy-client-ca.key (1679 bytes)
I0224 13:18:03.692597 945004 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20451-887294/.minikube/profiles/old-k8s-version-233759/apiserver.crt --> /var/lib/minikube/certs/apiserver.crt (1432 bytes)
I0224 13:18:03.723788 945004 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20451-887294/.minikube/profiles/old-k8s-version-233759/apiserver.key --> /var/lib/minikube/certs/apiserver.key (1675 bytes)
I0224 13:18:03.756287 945004 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20451-887294/.minikube/profiles/old-k8s-version-233759/proxy-client.crt --> /var/lib/minikube/certs/proxy-client.crt (1147 bytes)
I0224 13:18:03.789845 945004 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20451-887294/.minikube/profiles/old-k8s-version-233759/proxy-client.key --> /var/lib/minikube/certs/proxy-client.key (1675 bytes)
I0224 13:18:03.824019 945004 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20451-887294/.minikube/files/etc/ssl/certs/8945642.pem --> /usr/share/ca-certificates/8945642.pem (1708 bytes)
I0224 13:18:03.875546 945004 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20451-887294/.minikube/ca.crt --> /usr/share/ca-certificates/minikubeCA.pem (1111 bytes)
I0224 13:18:03.912517 945004 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20451-887294/.minikube/certs/894564.pem --> /usr/share/ca-certificates/894564.pem (1338 bytes)
I0224 13:18:03.948178 945004 ssh_runner.go:362] scp memory --> /var/lib/minikube/kubeconfig (738 bytes)
I0224 13:18:03.978582 945004 ssh_runner.go:195] Run: openssl version
I0224 13:18:03.985656 945004 ssh_runner.go:195] Run: sudo /bin/bash -c "test -s /usr/share/ca-certificates/8945642.pem && ln -fs /usr/share/ca-certificates/8945642.pem /etc/ssl/certs/8945642.pem"
I0224 13:18:04.001442 945004 ssh_runner.go:195] Run: ls -la /usr/share/ca-certificates/8945642.pem
I0224 13:18:04.008540 945004 certs.go:528] hashing: -rw-r--r-- 1 root root 1708 Feb 24 12:09 /usr/share/ca-certificates/8945642.pem
I0224 13:18:04.008618 945004 ssh_runner.go:195] Run: openssl x509 -hash -noout -in /usr/share/ca-certificates/8945642.pem
I0224 13:18:04.016827 945004 ssh_runner.go:195] Run: sudo /bin/bash -c "test -L /etc/ssl/certs/3ec20f2e.0 || ln -fs /etc/ssl/certs/8945642.pem /etc/ssl/certs/3ec20f2e.0"
I0224 13:18:04.033745 945004 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"
I0224 13:18:04.053653 945004 ssh_runner.go:195] Run: ls -la /usr/share/ca-certificates/minikubeCA.pem
I0224 13:18:04.061633 945004 certs.go:528] hashing: -rw-r--r-- 1 root root 1111 Feb 24 12:01 /usr/share/ca-certificates/minikubeCA.pem
I0224 13:18:04.061712 945004 ssh_runner.go:195] Run: openssl x509 -hash -noout -in /usr/share/ca-certificates/minikubeCA.pem
I0224 13:18:04.075375 945004 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"
I0224 13:18:04.099930 945004 ssh_runner.go:195] Run: sudo /bin/bash -c "test -s /usr/share/ca-certificates/894564.pem && ln -fs /usr/share/ca-certificates/894564.pem /etc/ssl/certs/894564.pem"
I0224 13:18:04.119493 945004 ssh_runner.go:195] Run: ls -la /usr/share/ca-certificates/894564.pem
I0224 13:18:04.126899 945004 certs.go:528] hashing: -rw-r--r-- 1 root root 1338 Feb 24 12:09 /usr/share/ca-certificates/894564.pem
I0224 13:18:04.126975 945004 ssh_runner.go:195] Run: openssl x509 -hash -noout -in /usr/share/ca-certificates/894564.pem
I0224 13:18:04.138064 945004 ssh_runner.go:195] Run: sudo /bin/bash -c "test -L /etc/ssl/certs/51391683.0 || ln -fs /etc/ssl/certs/894564.pem /etc/ssl/certs/51391683.0"
I0224 13:18:04.154183 945004 ssh_runner.go:195] Run: stat /var/lib/minikube/certs/apiserver-kubelet-client.crt
I0224 13:18:04.161423 945004 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
I0224 13:18:04.161504 945004 kubeadm.go:392] StartCluster: {Name:old-k8s-version-233759 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-1740046583-20436@sha256:b4324ef42fab4e243d39dd69028f243606b2fa4379f6ec916c89e512f68338f4 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-233759 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.50.62 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}
I0224 13:18:04.161620 945004 cri.go:54] listing CRI containers in root : {State:paused Name: Namespaces:[kube-system]}
I0224 13:18:04.161676 945004 ssh_runner.go:195] Run: sudo -s eval "crictl ps -a --quiet --label io.kubernetes.pod.namespace=kube-system"
I0224 13:18:04.214397 945004 cri.go:89] found id: ""
I0224 13:18:04.214485 945004 ssh_runner.go:195] Run: sudo ls /var/lib/kubelet/kubeadm-flags.env /var/lib/kubelet/config.yaml /var/lib/minikube/etcd
I0224 13:18:04.227439 945004 ssh_runner.go:195] Run: sudo cp /var/tmp/minikube/kubeadm.yaml.new /var/tmp/minikube/kubeadm.yaml
I0224 13:18:04.240814 945004 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
I0224 13:18:04.254486 945004 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
I0224 13:18:04.254517 945004 kubeadm.go:157] found existing configuration files:
I0224 13:18:04.254583 945004 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/admin.conf
I0224 13:18:04.266397 945004 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
I0224 13:18:04.266529 945004 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/admin.conf
I0224 13:18:04.280404 945004 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/kubelet.conf
I0224 13:18:04.293362 945004 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
I0224 13:18:04.293453 945004 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/kubelet.conf
I0224 13:18:04.309134 945004 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/controller-manager.conf
I0224 13:18:04.323939 945004 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
I0224 13:18:04.324036 945004 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/controller-manager.conf
I0224 13:18:04.339200 945004 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/scheduler.conf
I0224 13:18:04.353873 945004 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
I0224 13:18:04.353947 945004 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/scheduler.conf
I0224 13:18:04.369058 945004 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"
I0224 13:18:04.526964 945004 kubeadm.go:310] [init] Using Kubernetes version: v1.20.0
I0224 13:18:04.527076 945004 kubeadm.go:310] [preflight] Running pre-flight checks
I0224 13:18:04.705688 945004 kubeadm.go:310] [preflight] Pulling images required for setting up a Kubernetes cluster
I0224 13:18:04.705830 945004 kubeadm.go:310] [preflight] This might take a minute or two, depending on the speed of your internet connection
I0224 13:18:04.705935 945004 kubeadm.go:310] [preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
I0224 13:18:04.964087 945004 kubeadm.go:310] [certs] Using certificateDir folder "/var/lib/minikube/certs"
I0224 13:18:04.967415 945004 out.go:235] - Generating certificates and keys ...
I0224 13:18:04.967551 945004 kubeadm.go:310] [certs] Using existing ca certificate authority
I0224 13:18:04.967642 945004 kubeadm.go:310] [certs] Using existing apiserver certificate and key on disk
I0224 13:18:05.162198 945004 kubeadm.go:310] [certs] Generating "apiserver-kubelet-client" certificate and key
I0224 13:18:05.288582 945004 kubeadm.go:310] [certs] Generating "front-proxy-ca" certificate and key
I0224 13:18:05.717764 945004 kubeadm.go:310] [certs] Generating "front-proxy-client" certificate and key
I0224 13:18:05.854692 945004 kubeadm.go:310] [certs] Generating "etcd/ca" certificate and key
I0224 13:18:06.119230 945004 kubeadm.go:310] [certs] Generating "etcd/server" certificate and key
I0224 13:18:06.124513 945004 kubeadm.go:310] [certs] etcd/server serving cert is signed for DNS names [localhost old-k8s-version-233759] and IPs [192.168.50.62 127.0.0.1 ::1]
I0224 13:18:06.229995 945004 kubeadm.go:310] [certs] Generating "etcd/peer" certificate and key
I0224 13:18:06.230483 945004 kubeadm.go:310] [certs] etcd/peer serving cert is signed for DNS names [localhost old-k8s-version-233759] and IPs [192.168.50.62 127.0.0.1 ::1]
I0224 13:18:06.354283 945004 kubeadm.go:310] [certs] Generating "etcd/healthcheck-client" certificate and key
I0224 13:18:06.492995 945004 kubeadm.go:310] [certs] Generating "apiserver-etcd-client" certificate and key
I0224 13:18:06.656842 945004 kubeadm.go:310] [certs] Generating "sa" key and public key
I0224 13:18:06.657157 945004 kubeadm.go:310] [kubeconfig] Using kubeconfig folder "/etc/kubernetes"
I0224 13:18:06.948443 945004 kubeadm.go:310] [kubeconfig] Writing "admin.conf" kubeconfig file
I0224 13:18:07.278090 945004 kubeadm.go:310] [kubeconfig] Writing "kubelet.conf" kubeconfig file
I0224 13:18:07.697152 945004 kubeadm.go:310] [kubeconfig] Writing "controller-manager.conf" kubeconfig file
I0224 13:18:07.818115 945004 kubeadm.go:310] [kubeconfig] Writing "scheduler.conf" kubeconfig file
I0224 13:18:07.847194 945004 kubeadm.go:310] [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
I0224 13:18:07.849008 945004 kubeadm.go:310] [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
I0224 13:18:07.849141 945004 kubeadm.go:310] [kubelet-start] Starting the kubelet
I0224 13:18:08.006408 945004 kubeadm.go:310] [control-plane] Using manifest folder "/etc/kubernetes/manifests"
I0224 13:18:08.008474 945004 out.go:235] - Booting up control plane ...
I0224 13:18:08.008648 945004 kubeadm.go:310] [control-plane] Creating static Pod manifest for "kube-apiserver"
I0224 13:18:08.022644 945004 kubeadm.go:310] [control-plane] Creating static Pod manifest for "kube-controller-manager"
I0224 13:18:08.023842 945004 kubeadm.go:310] [control-plane] Creating static Pod manifest for "kube-scheduler"
I0224 13:18:08.024631 945004 kubeadm.go:310] [etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
I0224 13:18:08.031849 945004 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
I0224 13:18:48.028953 945004 kubeadm.go:310] [kubelet-check] Initial timeout of 40s passed.
I0224 13:18:48.030040 945004 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0224 13:18:48.030273 945004 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.
I0224 13:18:53.031170 945004 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0224 13:18:53.031407 945004 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.
I0224 13:19:03.032512 945004 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0224 13:19:03.032791 945004 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.
I0224 13:19:23.033943 945004 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0224 13:19:23.034223 945004 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.
I0224 13:20:03.034532 945004 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0224 13:20:03.034921 945004 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.
I0224 13:20:03.034938 945004 kubeadm.go:310]
I0224 13:20:03.034991 945004 kubeadm.go:310] Unfortunately, an error has occurred:
I0224 13:20:03.035047 945004 kubeadm.go:310] timed out waiting for the condition
I0224 13:20:03.035063 945004 kubeadm.go:310]
I0224 13:20:03.035114 945004 kubeadm.go:310] This error is likely caused by:
I0224 13:20:03.035155 945004 kubeadm.go:310] - The kubelet is not running
I0224 13:20:03.035292 945004 kubeadm.go:310] - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
I0224 13:20:03.035300 945004 kubeadm.go:310]
I0224 13:20:03.035386 945004 kubeadm.go:310] If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
I0224 13:20:03.035412 945004 kubeadm.go:310] - 'systemctl status kubelet'
I0224 13:20:03.035440 945004 kubeadm.go:310] - 'journalctl -xeu kubelet'
I0224 13:20:03.035444 945004 kubeadm.go:310]
I0224 13:20:03.035531 945004 kubeadm.go:310] Additionally, a control plane component may have crashed or exited when started by the container runtime.
I0224 13:20:03.035641 945004 kubeadm.go:310] To troubleshoot, list all containers using your preferred container runtimes CLI.
I0224 13:20:03.035650 945004 kubeadm.go:310]
I0224 13:20:03.035745 945004 kubeadm.go:310] Here is one example how you may list all Kubernetes containers running in cri-o/containerd using crictl:
I0224 13:20:03.035812 945004 kubeadm.go:310] - 'crictl --runtime-endpoint /var/run/crio/crio.sock ps -a | grep kube | grep -v pause'
I0224 13:20:03.035869 945004 kubeadm.go:310] Once you have found the failing container, you can inspect its logs with:
I0224 13:20:03.035923 945004 kubeadm.go:310] - 'crictl --runtime-endpoint /var/run/crio/crio.sock logs CONTAINERID'
I0224 13:20:03.035928 945004 kubeadm.go:310]
I0224 13:20:03.037286 945004 kubeadm.go:310] [WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
I0224 13:20:03.037423 945004 kubeadm.go:310] error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
I0224 13:20:03.037573 945004 kubeadm.go:310] To see the stack trace of this error execute with --v=5 or higher
W0224 13:20:03.037760 945004 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-233759] and IPs [192.168.50.62 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-233759] and IPs [192.168.50.62 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-233759] and IPs [192.168.50.62 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-233759] and IPs [192.168.50.62 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
I0224 13:20:03.037809 945004 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"
I0224 13:20:05.550944 945004 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": (2.51308936s)
I0224 13:20:05.551032 945004 ssh_runner.go:195] Run: sudo systemctl is-active --quiet service kubelet
I0224 13:20:05.573897 945004 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
I0224 13:20:05.589789 945004 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
I0224 13:20:05.589816 945004 kubeadm.go:157] found existing configuration files:
I0224 13:20:05.589877 945004 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/admin.conf
I0224 13:20:05.603814 945004 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
I0224 13:20:05.603874 945004 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/admin.conf
I0224 13:20:05.616321 945004 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/kubelet.conf
I0224 13:20:05.628882 945004 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
I0224 13:20:05.628960 945004 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/kubelet.conf
I0224 13:20:05.640030 945004 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/controller-manager.conf
I0224 13:20:05.651228 945004 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
I0224 13:20:05.651330 945004 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/controller-manager.conf
I0224 13:20:05.663377 945004 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/scheduler.conf
I0224 13:20:05.674241 945004 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
I0224 13:20:05.674314 945004 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/scheduler.conf
I0224 13:20:05.685918 945004 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"
I0224 13:20:05.924941 945004 kubeadm.go:310] [WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
I0224 13:22:02.153073 945004 kubeadm.go:310] error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
I0224 13:22:02.153232 945004 kubeadm.go:310] To see the stack trace of this error execute with --v=5 or higher
I0224 13:22:02.154991 945004 kubeadm.go:310] [init] Using Kubernetes version: v1.20.0
I0224 13:22:02.155058 945004 kubeadm.go:310] [preflight] Running pre-flight checks
I0224 13:22:02.155147 945004 kubeadm.go:310] [preflight] Pulling images required for setting up a Kubernetes cluster
I0224 13:22:02.155279 945004 kubeadm.go:310] [preflight] This might take a minute or two, depending on the speed of your internet connection
I0224 13:22:02.155372 945004 kubeadm.go:310] [preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
I0224 13:22:02.155495 945004 kubeadm.go:310] [certs] Using certificateDir folder "/var/lib/minikube/certs"
I0224 13:22:02.327389 945004 out.go:235] - Generating certificates and keys ...
I0224 13:22:02.327536 945004 kubeadm.go:310] [certs] Using existing ca certificate authority
I0224 13:22:02.327589 945004 kubeadm.go:310] [certs] Using existing apiserver certificate and key on disk
I0224 13:22:02.327686 945004 kubeadm.go:310] [certs] Using existing apiserver-kubelet-client certificate and key on disk
I0224 13:22:02.327747 945004 kubeadm.go:310] [certs] Using existing front-proxy-ca certificate authority
I0224 13:22:02.327810 945004 kubeadm.go:310] [certs] Using existing front-proxy-client certificate and key on disk
I0224 13:22:02.327857 945004 kubeadm.go:310] [certs] Using existing etcd/ca certificate authority
I0224 13:22:02.327933 945004 kubeadm.go:310] [certs] Using existing etcd/server certificate and key on disk
I0224 13:22:02.328000 945004 kubeadm.go:310] [certs] Using existing etcd/peer certificate and key on disk
I0224 13:22:02.328064 945004 kubeadm.go:310] [certs] Using existing etcd/healthcheck-client certificate and key on disk
I0224 13:22:02.328194 945004 kubeadm.go:310] [certs] Using existing apiserver-etcd-client certificate and key on disk
I0224 13:22:02.328269 945004 kubeadm.go:310] [certs] Using the existing "sa" key
I0224 13:22:02.328356 945004 kubeadm.go:310] [kubeconfig] Using kubeconfig folder "/etc/kubernetes"
I0224 13:22:02.328452 945004 kubeadm.go:310] [kubeconfig] Writing "admin.conf" kubeconfig file
I0224 13:22:02.328534 945004 kubeadm.go:310] [kubeconfig] Writing "kubelet.conf" kubeconfig file
I0224 13:22:02.328633 945004 kubeadm.go:310] [kubeconfig] Writing "controller-manager.conf" kubeconfig file
I0224 13:22:02.328721 945004 kubeadm.go:310] [kubeconfig] Writing "scheduler.conf" kubeconfig file
I0224 13:22:02.328843 945004 kubeadm.go:310] [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
I0224 13:22:02.328913 945004 kubeadm.go:310] [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
I0224 13:22:02.328946 945004 kubeadm.go:310] [kubelet-start] Starting the kubelet
I0224 13:22:02.329013 945004 kubeadm.go:310] [control-plane] Using manifest folder "/etc/kubernetes/manifests"
I0224 13:22:02.330393 945004 out.go:235] - Booting up control plane ...
I0224 13:22:02.330531 945004 kubeadm.go:310] [control-plane] Creating static Pod manifest for "kube-apiserver"
I0224 13:22:02.330663 945004 kubeadm.go:310] [control-plane] Creating static Pod manifest for "kube-controller-manager"
I0224 13:22:02.330772 945004 kubeadm.go:310] [control-plane] Creating static Pod manifest for "kube-scheduler"
I0224 13:22:02.330888 945004 kubeadm.go:310] [etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
I0224 13:22:02.331113 945004 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
I0224 13:22:02.331193 945004 kubeadm.go:310] [kubelet-check] Initial timeout of 40s passed.
I0224 13:22:02.331291 945004 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0224 13:22:02.331515 945004 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.
I0224 13:22:02.331581 945004 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0224 13:22:02.331828 945004 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.
I0224 13:22:02.331943 945004 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0224 13:22:02.332181 945004 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.
I0224 13:22:02.332283 945004 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0224 13:22:02.332537 945004 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.
I0224 13:22:02.332638 945004 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0224 13:22:02.332845 945004 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.
I0224 13:22:02.332856 945004 kubeadm.go:310]
I0224 13:22:02.332910 945004 kubeadm.go:310] Unfortunately, an error has occurred:
I0224 13:22:02.332967 945004 kubeadm.go:310] timed out waiting for the condition
I0224 13:22:02.332976 945004 kubeadm.go:310]
I0224 13:22:02.333024 945004 kubeadm.go:310] This error is likely caused by:
I0224 13:22:02.333075 945004 kubeadm.go:310] - The kubelet is not running
I0224 13:22:02.333170 945004 kubeadm.go:310] - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
I0224 13:22:02.333180 945004 kubeadm.go:310]
I0224 13:22:02.333318 945004 kubeadm.go:310] If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
I0224 13:22:02.333367 945004 kubeadm.go:310] - 'systemctl status kubelet'
I0224 13:22:02.333445 945004 kubeadm.go:310] - 'journalctl -xeu kubelet'
I0224 13:22:02.333465 945004 kubeadm.go:310]
I0224 13:22:02.333603 945004 kubeadm.go:310] Additionally, a control plane component may have crashed or exited when started by the container runtime.
I0224 13:22:02.333707 945004 kubeadm.go:310] To troubleshoot, list all containers using your preferred container runtimes CLI.
I0224 13:22:02.333718 945004 kubeadm.go:310]
I0224 13:22:02.333862 945004 kubeadm.go:310] Here is one example how you may list all Kubernetes containers running in cri-o/containerd using crictl:
I0224 13:22:02.333954 945004 kubeadm.go:310] - 'crictl --runtime-endpoint /var/run/crio/crio.sock ps -a | grep kube | grep -v pause'
I0224 13:22:02.334074 945004 kubeadm.go:310] Once you have found the failing container, you can inspect its logs with:
I0224 13:22:02.334194 945004 kubeadm.go:310] - 'crictl --runtime-endpoint /var/run/crio/crio.sock logs CONTAINERID'
I0224 13:22:02.334230 945004 kubeadm.go:310]
I0224 13:22:02.334286 945004 kubeadm.go:394] duration metric: took 3m58.172788032s to StartCluster
I0224 13:22:02.334343 945004 cri.go:54] listing CRI containers in root : {State:all Name:kube-apiserver Namespaces:[]}
I0224 13:22:02.334421 945004 ssh_runner.go:195] Run: sudo crictl ps -a --quiet --name=kube-apiserver
I0224 13:22:02.388338 945004 cri.go:89] found id: ""
I0224 13:22:02.388375 945004 logs.go:282] 0 containers: []
W0224 13:22:02.388388 945004 logs.go:284] No container was found matching "kube-apiserver"
I0224 13:22:02.388398 945004 cri.go:54] listing CRI containers in root : {State:all Name:etcd Namespaces:[]}
I0224 13:22:02.388481 945004 ssh_runner.go:195] Run: sudo crictl ps -a --quiet --name=etcd
I0224 13:22:02.436717 945004 cri.go:89] found id: ""
I0224 13:22:02.436766 945004 logs.go:282] 0 containers: []
W0224 13:22:02.436779 945004 logs.go:284] No container was found matching "etcd"
I0224 13:22:02.436787 945004 cri.go:54] listing CRI containers in root : {State:all Name:coredns Namespaces:[]}
I0224 13:22:02.436862 945004 ssh_runner.go:195] Run: sudo crictl ps -a --quiet --name=coredns
I0224 13:22:02.478061 945004 cri.go:89] found id: ""
I0224 13:22:02.478097 945004 logs.go:282] 0 containers: []
W0224 13:22:02.478110 945004 logs.go:284] No container was found matching "coredns"
I0224 13:22:02.478119 945004 cri.go:54] listing CRI containers in root : {State:all Name:kube-scheduler Namespaces:[]}
I0224 13:22:02.478190 945004 ssh_runner.go:195] Run: sudo crictl ps -a --quiet --name=kube-scheduler
I0224 13:22:02.518871 945004 cri.go:89] found id: ""
I0224 13:22:02.518907 945004 logs.go:282] 0 containers: []
W0224 13:22:02.518919 945004 logs.go:284] No container was found matching "kube-scheduler"
I0224 13:22:02.518926 945004 cri.go:54] listing CRI containers in root : {State:all Name:kube-proxy Namespaces:[]}
I0224 13:22:02.518997 945004 ssh_runner.go:195] Run: sudo crictl ps -a --quiet --name=kube-proxy
I0224 13:22:02.566684 945004 cri.go:89] found id: ""
I0224 13:22:02.566717 945004 logs.go:282] 0 containers: []
W0224 13:22:02.566730 945004 logs.go:284] No container was found matching "kube-proxy"
I0224 13:22:02.566738 945004 cri.go:54] listing CRI containers in root : {State:all Name:kube-controller-manager Namespaces:[]}
I0224 13:22:02.566807 945004 ssh_runner.go:195] Run: sudo crictl ps -a --quiet --name=kube-controller-manager
I0224 13:22:02.611361 945004 cri.go:89] found id: ""
I0224 13:22:02.611401 945004 logs.go:282] 0 containers: []
W0224 13:22:02.611411 945004 logs.go:284] No container was found matching "kube-controller-manager"
I0224 13:22:02.611418 945004 cri.go:54] listing CRI containers in root : {State:all Name:kindnet Namespaces:[]}
I0224 13:22:02.611486 945004 ssh_runner.go:195] Run: sudo crictl ps -a --quiet --name=kindnet
I0224 13:22:02.666829 945004 cri.go:89] found id: ""
I0224 13:22:02.666864 945004 logs.go:282] 0 containers: []
W0224 13:22:02.666878 945004 logs.go:284] No container was found matching "kindnet"
I0224 13:22:02.666892 945004 logs.go:123] Gathering logs for kubelet ...
I0224 13:22:02.666909 945004 ssh_runner.go:195] Run: /bin/bash -c "sudo journalctl -u kubelet -n 400"
I0224 13:22:02.727119 945004 logs.go:123] Gathering logs for dmesg ...
I0224 13:22:02.727164 945004 ssh_runner.go:195] Run: /bin/bash -c "sudo dmesg -PH -L=never --level warn,err,crit,alert,emerg | tail -n 400"
I0224 13:22:02.745040 945004 logs.go:123] Gathering logs for describe nodes ...
I0224 13:22:02.745083 945004 ssh_runner.go:195] Run: /bin/bash -c "sudo /var/lib/minikube/binaries/v1.20.0/kubectl describe nodes --kubeconfig=/var/lib/minikube/kubeconfig"
W0224 13:22:02.892216 945004 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 **
I0224 13:22:02.892249 945004 logs.go:123] Gathering logs for CRI-O ...
I0224 13:22:02.892266 945004 ssh_runner.go:195] Run: /bin/bash -c "sudo journalctl -u crio -n 400"
I0224 13:22:03.016379 945004 logs.go:123] Gathering logs for container status ...
I0224 13:22:03.016427 945004 ssh_runner.go:195] Run: /bin/bash -c "sudo `which crictl || echo crictl` ps -a || sudo docker ps -a"
W0224 13:22:03.073254 945004 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
W0224 13:22:03.073351 945004 out.go:270] *
*
W0224 13:22:03.073470 945004 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
W0224 13:22:03.073521 945004 out.go:270] *
*
W0224 13:22:03.074812 945004 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. │
│ │
╰─────────────────────────────────────────────────────────────────────────────────────────────╯
I0224 13:22:03.078706 945004 out.go:201]
W0224 13:22:03.080145 945004 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
W0224 13:22:03.080215 945004 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
W0224 13:22:03.080244 945004 out.go:270] * Related issue: https://github.com/kubernetes/minikube/issues/4172
* Related issue: https://github.com/kubernetes/minikube/issues/4172
I0224 13:22:03.081936 945004 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-233759 --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-233759 -n old-k8s-version-233759
helpers_test.go:239: (dbg) Non-zero exit: out/minikube-linux-amd64 status --format={{.Host}} -p old-k8s-version-233759 -n old-k8s-version-233759: exit status 6 (247.613285ms)
-- stdout --
Running
WARNING: Your kubectl is pointing to stale minikube-vm.
To fix the kubectl context, run `minikube update-context`
-- /stdout --
** stderr **
E0224 13:22:03.382163 952395 status.go:458] kubeconfig endpoint: get endpoint: "old-k8s-version-233759" does not appear in /home/jenkins/minikube-integration/20451-887294/kubeconfig
** /stderr **
helpers_test.go:239: status error: exit status 6 (may be ok)
helpers_test.go:241: "old-k8s-version-233759" 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 (287.71s)