=== RUN TestStartStop/group/old-k8s-version/serial/FirstStart
start_stop_delete_test.go:186: (dbg) Run: out/minikube-linux-amd64 start -p old-k8s-version-239115 --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:186: (dbg) Non-zero exit: out/minikube-linux-amd64 start -p old-k8s-version-239115 --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 (5m20.560595266s)
-- stdout --
* [old-k8s-version-239115] minikube v1.33.1 on Ubuntu 20.04 (kvm/amd64)
- MINIKUBE_LOCATION=19355
- MINIKUBE_SUPPRESS_DOCKER_PERFORMANCE=true
- KUBECONFIG=/home/jenkins/minikube-integration/19355-121704/kubeconfig
- MINIKUBE_HOME=/home/jenkins/minikube-integration/19355-121704/.minikube
- MINIKUBE_BIN=out/minikube-linux-amd64
- MINIKUBE_FORCE_SYSTEMD=
* Using the kvm2 driver based on user configuration
* Starting "old-k8s-version-239115" primary control-plane node in "old-k8s-version-239115" 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 **
I0731 20:48:03.182230 180868 out.go:291] Setting OutFile to fd 1 ...
I0731 20:48:03.182484 180868 out.go:338] TERM=,COLORTERM=, which probably does not support color
I0731 20:48:03.182493 180868 out.go:304] Setting ErrFile to fd 2...
I0731 20:48:03.182497 180868 out.go:338] TERM=,COLORTERM=, which probably does not support color
I0731 20:48:03.182682 180868 root.go:338] Updating PATH: /home/jenkins/minikube-integration/19355-121704/.minikube/bin
I0731 20:48:03.183246 180868 out.go:298] Setting JSON to false
I0731 20:48:03.184271 180868 start.go:129] hostinfo: {"hostname":"ubuntu-20-agent-11","uptime":9019,"bootTime":1722449864,"procs":274,"os":"linux","platform":"ubuntu","platformFamily":"debian","platformVersion":"20.04","kernelVersion":"5.15.0-1065-gcp","kernelArch":"x86_64","virtualizationSystem":"kvm","virtualizationRole":"guest","hostId":"591c9f12-2938-3743-e2bf-c56a050d43d1"}
I0731 20:48:03.184340 180868 start.go:139] virtualization: kvm guest
I0731 20:48:03.186745 180868 out.go:177] * [old-k8s-version-239115] minikube v1.33.1 on Ubuntu 20.04 (kvm/amd64)
I0731 20:48:03.188384 180868 out.go:177] - MINIKUBE_LOCATION=19355
I0731 20:48:03.188389 180868 notify.go:220] Checking for updates...
I0731 20:48:03.191232 180868 out.go:177] - MINIKUBE_SUPPRESS_DOCKER_PERFORMANCE=true
I0731 20:48:03.192691 180868 out.go:177] - KUBECONFIG=/home/jenkins/minikube-integration/19355-121704/kubeconfig
I0731 20:48:03.194206 180868 out.go:177] - MINIKUBE_HOME=/home/jenkins/minikube-integration/19355-121704/.minikube
I0731 20:48:03.195616 180868 out.go:177] - MINIKUBE_BIN=out/minikube-linux-amd64
I0731 20:48:03.197076 180868 out.go:177] - MINIKUBE_FORCE_SYSTEMD=
I0731 20:48:03.199090 180868 config.go:182] Loaded profile config "bridge-341849": Driver=kvm2, ContainerRuntime=crio, KubernetesVersion=v1.30.3
I0731 20:48:03.199242 180868 config.go:182] Loaded profile config "enable-default-cni-341849": Driver=kvm2, ContainerRuntime=crio, KubernetesVersion=v1.30.3
I0731 20:48:03.199380 180868 config.go:182] Loaded profile config "flannel-341849": Driver=kvm2, ContainerRuntime=crio, KubernetesVersion=v1.30.3
I0731 20:48:03.199511 180868 driver.go:392] Setting default libvirt URI to qemu:///system
I0731 20:48:03.238148 180868 out.go:177] * Using the kvm2 driver based on user configuration
I0731 20:48:03.239347 180868 start.go:297] selected driver: kvm2
I0731 20:48:03.239365 180868 start.go:901] validating driver "kvm2" against <nil>
I0731 20:48:03.239380 180868 start.go:912] status for kvm2: {Installed:true Healthy:true Running:true NeedsImprovement:false Error:<nil> Reason: Fix: Doc: Version:}
I0731 20:48:03.240087 180868 install.go:52] acquiring lock: {Name:mk900956b073697a4aa6c80a27c6bb0742a99a53 Clock:{} Delay:500ms Timeout:10m0s Cancel:<nil>}
I0731 20:48:03.240179 180868 install.go:117] Validating docker-machine-driver-kvm2, PATH=/home/jenkins/minikube-integration/19355-121704/.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
I0731 20:48:03.256180 180868 install.go:137] /home/jenkins/minikube-integration/19355-121704/.minikube/bin/docker-machine-driver-kvm2 version is 1.33.1
I0731 20:48:03.256239 180868 start_flags.go:310] no existing cluster config was found, will generate one from the flags
I0731 20:48:03.256512 180868 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]
I0731 20:48:03.256581 180868 cni.go:84] Creating CNI manager for ""
I0731 20:48:03.256596 180868 cni.go:146] "kvm2" driver + "crio" runtime found, recommending bridge
I0731 20:48:03.256613 180868 start_flags.go:319] Found "bridge CNI" CNI - setting NetworkPlugin=cni
I0731 20:48:03.256695 180868 start.go:340] cluster config:
{Name:old-k8s-version-239115 KeepContext:false EmbedCerts:false MinikubeISO: KicBaseImage:gcr.io/k8s-minikube/kicbase-builds:v0.0.44-1721902582-19326@sha256:540fb5dc7f38be17ff5276a38dfe6c8a4b1d9ba1c27c62244e6eebd7e37696e7 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-239115 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}
I0731 20:48:03.256849 180868 iso.go:125] acquiring lock: {Name:mk69fc0fe37180b19ce91307b5e12ab2d0bd69fb Clock:{} Delay:500ms Timeout:10m0s Cancel:<nil>}
I0731 20:48:03.258748 180868 out.go:177] * Starting "old-k8s-version-239115" primary control-plane node in "old-k8s-version-239115" cluster
I0731 20:48:03.259970 180868 preload.go:131] Checking if preload exists for k8s version v1.20.0 and runtime crio
I0731 20:48:03.260012 180868 preload.go:146] Found local preload: /home/jenkins/minikube-integration/19355-121704/.minikube/cache/preloaded-tarball/preloaded-images-k8s-v18-v1.20.0-cri-o-overlay-amd64.tar.lz4
I0731 20:48:03.260026 180868 cache.go:56] Caching tarball of preloaded images
I0731 20:48:03.260106 180868 preload.go:172] Found /home/jenkins/minikube-integration/19355-121704/.minikube/cache/preloaded-tarball/preloaded-images-k8s-v18-v1.20.0-cri-o-overlay-amd64.tar.lz4 in cache, skipping download
I0731 20:48:03.260119 180868 cache.go:59] Finished verifying existence of preloaded tar for v1.20.0 on crio
I0731 20:48:03.260218 180868 profile.go:143] Saving config to /home/jenkins/minikube-integration/19355-121704/.minikube/profiles/old-k8s-version-239115/config.json ...
I0731 20:48:03.260242 180868 lock.go:35] WriteFile acquiring /home/jenkins/minikube-integration/19355-121704/.minikube/profiles/old-k8s-version-239115/config.json: {Name:mk18e6ee90358393c1765236e4370234f1775c75 Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0731 20:48:03.260387 180868 start.go:360] acquireMachinesLock for old-k8s-version-239115: {Name:mk0ee20c9dba367bb5e62f6affdfe6f589095d2a Clock:{} Delay:500ms Timeout:13m0s Cancel:<nil>}
I0731 20:48:47.566264 180868 start.go:364] duration metric: took 44.305829613s to acquireMachinesLock for "old-k8s-version-239115"
I0731 20:48:47.566338 180868 start.go:93] Provisioning new machine with config: &{Name:old-k8s-version-239115 KeepContext:false EmbedCerts:false MinikubeISO:https://storage.googleapis.com/minikube-builds/iso/19355/minikube-v1.33.1-1722420371-19355-amd64.iso KicBaseImage:gcr.io/k8s-minikube/kicbase-builds:v0.0.44-1721902582-19326@sha256:540fb5dc7f38be17ff5276a38dfe6c8a4b1d9ba1c27c62244e6eebd7e37696e7 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 KubernetesConfi
g:{KubernetesVersion:v1.20.0 ClusterName:old-k8s-version-239115 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 MountUID: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}
I0731 20:48:47.566433 180868 start.go:125] createHost starting for "" (driver="kvm2")
I0731 20:48:47.568910 180868 out.go:204] * Creating kvm2 VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
I0731 20:48:47.569102 180868 main.go:141] libmachine: Found binary path at /home/jenkins/minikube-integration/19355-121704/.minikube/bin/docker-machine-driver-kvm2
I0731 20:48:47.569162 180868 main.go:141] libmachine: Launching plugin server for driver kvm2
I0731 20:48:47.586187 180868 main.go:141] libmachine: Plugin server listening at address 127.0.0.1:36379
I0731 20:48:47.586631 180868 main.go:141] libmachine: () Calling .GetVersion
I0731 20:48:47.587139 180868 main.go:141] libmachine: Using API Version 1
I0731 20:48:47.587181 180868 main.go:141] libmachine: () Calling .SetConfigRaw
I0731 20:48:47.587525 180868 main.go:141] libmachine: () Calling .GetMachineName
I0731 20:48:47.587743 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetMachineName
I0731 20:48:47.587910 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .DriverName
I0731 20:48:47.588058 180868 start.go:159] libmachine.API.Create for "old-k8s-version-239115" (driver="kvm2")
I0731 20:48:47.588088 180868 client.go:168] LocalClient.Create starting
I0731 20:48:47.588122 180868 main.go:141] libmachine: Reading certificate data from /home/jenkins/minikube-integration/19355-121704/.minikube/certs/ca.pem
I0731 20:48:47.588161 180868 main.go:141] libmachine: Decoding PEM data...
I0731 20:48:47.588177 180868 main.go:141] libmachine: Parsing certificate...
I0731 20:48:47.588259 180868 main.go:141] libmachine: Reading certificate data from /home/jenkins/minikube-integration/19355-121704/.minikube/certs/cert.pem
I0731 20:48:47.588291 180868 main.go:141] libmachine: Decoding PEM data...
I0731 20:48:47.588305 180868 main.go:141] libmachine: Parsing certificate...
I0731 20:48:47.588336 180868 main.go:141] libmachine: Running pre-create checks...
I0731 20:48:47.588356 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .PreCreateCheck
I0731 20:48:47.588753 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetConfigRaw
I0731 20:48:47.589199 180868 main.go:141] libmachine: Creating machine...
I0731 20:48:47.589218 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .Create
I0731 20:48:47.589382 180868 main.go:141] libmachine: (old-k8s-version-239115) Creating KVM machine...
I0731 20:48:47.590643 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | found existing default KVM network
I0731 20:48:47.591902 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | I0731 20:48:47.591744 182545 network.go:211] skipping subnet 192.168.39.0/24 that is taken: &{IP:192.168.39.0 Netmask:255.255.255.0 Prefix:24 CIDR:192.168.39.0/24 Gateway:192.168.39.1 ClientMin:192.168.39.2 ClientMax:192.168.39.254 Broadcast:192.168.39.255 IsPrivate:true Interface:{IfaceName:virbr1 IfaceIPv4:192.168.39.1 IfaceMTU:1500 IfaceMAC:52:54:00:6d:4b:76} reservation:<nil>}
I0731 20:48:47.592737 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | I0731 20:48:47.592635 182545 network.go:211] skipping subnet 192.168.50.0/24 that is taken: &{IP:192.168.50.0 Netmask:255.255.255.0 Prefix:24 CIDR:192.168.50.0/24 Gateway:192.168.50.1 ClientMin:192.168.50.2 ClientMax:192.168.50.254 Broadcast:192.168.50.255 IsPrivate:true Interface:{IfaceName:virbr2 IfaceIPv4:192.168.50.1 IfaceMTU:1500 IfaceMAC:52:54:00:ed:c8:e9} reservation:<nil>}
I0731 20:48:47.593688 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | I0731 20:48:47.593589 182545 network.go:206] using free private subnet 192.168.61.0/24: &{IP:192.168.61.0 Netmask:255.255.255.0 Prefix:24 CIDR:192.168.61.0/24 Gateway:192.168.61.1 ClientMin:192.168.61.2 ClientMax:192.168.61.254 Broadcast:192.168.61.255 IsPrivate:true Interface:{IfaceName: IfaceIPv4: IfaceMTU:0 IfaceMAC:} reservation:0xc0002ae960}
I0731 20:48:47.593709 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | created network xml:
I0731 20:48:47.593719 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | <network>
I0731 20:48:47.593727 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | <name>mk-old-k8s-version-239115</name>
I0731 20:48:47.593737 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | <dns enable='no'/>
I0731 20:48:47.593747 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG |
I0731 20:48:47.593762 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | <ip address='192.168.61.1' netmask='255.255.255.0'>
I0731 20:48:47.593773 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | <dhcp>
I0731 20:48:47.593787 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | <range start='192.168.61.2' end='192.168.61.253'/>
I0731 20:48:47.593797 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | </dhcp>
I0731 20:48:47.593813 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | </ip>
I0731 20:48:47.593828 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG |
I0731 20:48:47.593841 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | </network>
I0731 20:48:47.593849 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG |
I0731 20:48:47.599805 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | trying to create private KVM network mk-old-k8s-version-239115 192.168.61.0/24...
I0731 20:48:47.671786 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | private KVM network mk-old-k8s-version-239115 192.168.61.0/24 created
I0731 20:48:47.671820 180868 main.go:141] libmachine: (old-k8s-version-239115) Setting up store path in /home/jenkins/minikube-integration/19355-121704/.minikube/machines/old-k8s-version-239115 ...
I0731 20:48:47.671851 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | I0731 20:48:47.671747 182545 common.go:145] Making disk image using store path: /home/jenkins/minikube-integration/19355-121704/.minikube
I0731 20:48:47.671863 180868 main.go:141] libmachine: (old-k8s-version-239115) Building disk image from file:///home/jenkins/minikube-integration/19355-121704/.minikube/cache/iso/amd64/minikube-v1.33.1-1722420371-19355-amd64.iso
I0731 20:48:47.671879 180868 main.go:141] libmachine: (old-k8s-version-239115) Downloading /home/jenkins/minikube-integration/19355-121704/.minikube/cache/boot2docker.iso from file:///home/jenkins/minikube-integration/19355-121704/.minikube/cache/iso/amd64/minikube-v1.33.1-1722420371-19355-amd64.iso...
I0731 20:48:47.932403 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | I0731 20:48:47.932234 182545 common.go:152] Creating ssh key: /home/jenkins/minikube-integration/19355-121704/.minikube/machines/old-k8s-version-239115/id_rsa...
I0731 20:48:48.063956 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | I0731 20:48:48.063778 182545 common.go:158] Creating raw disk image: /home/jenkins/minikube-integration/19355-121704/.minikube/machines/old-k8s-version-239115/old-k8s-version-239115.rawdisk...
I0731 20:48:48.063998 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | Writing magic tar header
I0731 20:48:48.064017 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | Writing SSH key tar header
I0731 20:48:48.064031 180868 main.go:141] libmachine: (old-k8s-version-239115) Setting executable bit set on /home/jenkins/minikube-integration/19355-121704/.minikube/machines/old-k8s-version-239115 (perms=drwx------)
I0731 20:48:48.064046 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | I0731 20:48:48.063901 182545 common.go:172] Fixing permissions on /home/jenkins/minikube-integration/19355-121704/.minikube/machines/old-k8s-version-239115 ...
I0731 20:48:48.064064 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | Checking permissions on dir: /home/jenkins/minikube-integration/19355-121704/.minikube/machines/old-k8s-version-239115
I0731 20:48:48.064074 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | Checking permissions on dir: /home/jenkins/minikube-integration/19355-121704/.minikube/machines
I0731 20:48:48.064091 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | Checking permissions on dir: /home/jenkins/minikube-integration/19355-121704/.minikube
I0731 20:48:48.064105 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | Checking permissions on dir: /home/jenkins/minikube-integration/19355-121704
I0731 20:48:48.064121 180868 main.go:141] libmachine: (old-k8s-version-239115) Setting executable bit set on /home/jenkins/minikube-integration/19355-121704/.minikube/machines (perms=drwxr-xr-x)
I0731 20:48:48.064134 180868 main.go:141] libmachine: (old-k8s-version-239115) Setting executable bit set on /home/jenkins/minikube-integration/19355-121704/.minikube (perms=drwxr-xr-x)
I0731 20:48:48.064141 180868 main.go:141] libmachine: (old-k8s-version-239115) Setting executable bit set on /home/jenkins/minikube-integration/19355-121704 (perms=drwxrwxr-x)
I0731 20:48:48.064148 180868 main.go:141] libmachine: (old-k8s-version-239115) Setting executable bit set on /home/jenkins/minikube-integration (perms=drwxrwxr-x)
I0731 20:48:48.064166 180868 main.go:141] libmachine: (old-k8s-version-239115) Setting executable bit set on /home/jenkins (perms=drwxr-xr-x)
I0731 20:48:48.064177 180868 main.go:141] libmachine: (old-k8s-version-239115) Creating domain...
I0731 20:48:48.064185 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | Checking permissions on dir: /home/jenkins/minikube-integration
I0731 20:48:48.064192 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | Checking permissions on dir: /home/jenkins
I0731 20:48:48.064199 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | Checking permissions on dir: /home
I0731 20:48:48.064206 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | Skipping /home - not owner
I0731 20:48:48.065523 180868 main.go:141] libmachine: (old-k8s-version-239115) define libvirt domain using xml:
I0731 20:48:48.065545 180868 main.go:141] libmachine: (old-k8s-version-239115) <domain type='kvm'>
I0731 20:48:48.065555 180868 main.go:141] libmachine: (old-k8s-version-239115) <name>old-k8s-version-239115</name>
I0731 20:48:48.065563 180868 main.go:141] libmachine: (old-k8s-version-239115) <memory unit='MiB'>2200</memory>
I0731 20:48:48.065572 180868 main.go:141] libmachine: (old-k8s-version-239115) <vcpu>2</vcpu>
I0731 20:48:48.065579 180868 main.go:141] libmachine: (old-k8s-version-239115) <features>
I0731 20:48:48.065587 180868 main.go:141] libmachine: (old-k8s-version-239115) <acpi/>
I0731 20:48:48.065596 180868 main.go:141] libmachine: (old-k8s-version-239115) <apic/>
I0731 20:48:48.065603 180868 main.go:141] libmachine: (old-k8s-version-239115) <pae/>
I0731 20:48:48.065608 180868 main.go:141] libmachine: (old-k8s-version-239115)
I0731 20:48:48.065629 180868 main.go:141] libmachine: (old-k8s-version-239115) </features>
I0731 20:48:48.065643 180868 main.go:141] libmachine: (old-k8s-version-239115) <cpu mode='host-passthrough'>
I0731 20:48:48.065667 180868 main.go:141] libmachine: (old-k8s-version-239115)
I0731 20:48:48.065677 180868 main.go:141] libmachine: (old-k8s-version-239115) </cpu>
I0731 20:48:48.065686 180868 main.go:141] libmachine: (old-k8s-version-239115) <os>
I0731 20:48:48.065693 180868 main.go:141] libmachine: (old-k8s-version-239115) <type>hvm</type>
I0731 20:48:48.065702 180868 main.go:141] libmachine: (old-k8s-version-239115) <boot dev='cdrom'/>
I0731 20:48:48.065714 180868 main.go:141] libmachine: (old-k8s-version-239115) <boot dev='hd'/>
I0731 20:48:48.065723 180868 main.go:141] libmachine: (old-k8s-version-239115) <bootmenu enable='no'/>
I0731 20:48:48.065733 180868 main.go:141] libmachine: (old-k8s-version-239115) </os>
I0731 20:48:48.065742 180868 main.go:141] libmachine: (old-k8s-version-239115) <devices>
I0731 20:48:48.065753 180868 main.go:141] libmachine: (old-k8s-version-239115) <disk type='file' device='cdrom'>
I0731 20:48:48.065890 180868 main.go:141] libmachine: (old-k8s-version-239115) <source file='/home/jenkins/minikube-integration/19355-121704/.minikube/machines/old-k8s-version-239115/boot2docker.iso'/>
I0731 20:48:48.065924 180868 main.go:141] libmachine: (old-k8s-version-239115) <target dev='hdc' bus='scsi'/>
I0731 20:48:48.065945 180868 main.go:141] libmachine: (old-k8s-version-239115) <readonly/>
I0731 20:48:48.065957 180868 main.go:141] libmachine: (old-k8s-version-239115) </disk>
I0731 20:48:48.065968 180868 main.go:141] libmachine: (old-k8s-version-239115) <disk type='file' device='disk'>
I0731 20:48:48.065982 180868 main.go:141] libmachine: (old-k8s-version-239115) <driver name='qemu' type='raw' cache='default' io='threads' />
I0731 20:48:48.066002 180868 main.go:141] libmachine: (old-k8s-version-239115) <source file='/home/jenkins/minikube-integration/19355-121704/.minikube/machines/old-k8s-version-239115/old-k8s-version-239115.rawdisk'/>
I0731 20:48:48.066018 180868 main.go:141] libmachine: (old-k8s-version-239115) <target dev='hda' bus='virtio'/>
I0731 20:48:48.066040 180868 main.go:141] libmachine: (old-k8s-version-239115) </disk>
I0731 20:48:48.066056 180868 main.go:141] libmachine: (old-k8s-version-239115) <interface type='network'>
I0731 20:48:48.066065 180868 main.go:141] libmachine: (old-k8s-version-239115) <source network='mk-old-k8s-version-239115'/>
I0731 20:48:48.066076 180868 main.go:141] libmachine: (old-k8s-version-239115) <model type='virtio'/>
I0731 20:48:48.066108 180868 main.go:141] libmachine: (old-k8s-version-239115) </interface>
I0731 20:48:48.066139 180868 main.go:141] libmachine: (old-k8s-version-239115) <interface type='network'>
I0731 20:48:48.066154 180868 main.go:141] libmachine: (old-k8s-version-239115) <source network='default'/>
I0731 20:48:48.066166 180868 main.go:141] libmachine: (old-k8s-version-239115) <model type='virtio'/>
I0731 20:48:48.066190 180868 main.go:141] libmachine: (old-k8s-version-239115) </interface>
I0731 20:48:48.066203 180868 main.go:141] libmachine: (old-k8s-version-239115) <serial type='pty'>
I0731 20:48:48.066227 180868 main.go:141] libmachine: (old-k8s-version-239115) <target port='0'/>
I0731 20:48:48.066246 180868 main.go:141] libmachine: (old-k8s-version-239115) </serial>
I0731 20:48:48.066259 180868 main.go:141] libmachine: (old-k8s-version-239115) <console type='pty'>
I0731 20:48:48.066270 180868 main.go:141] libmachine: (old-k8s-version-239115) <target type='serial' port='0'/>
I0731 20:48:48.066279 180868 main.go:141] libmachine: (old-k8s-version-239115) </console>
I0731 20:48:48.066288 180868 main.go:141] libmachine: (old-k8s-version-239115) <rng model='virtio'>
I0731 20:48:48.066298 180868 main.go:141] libmachine: (old-k8s-version-239115) <backend model='random'>/dev/random</backend>
I0731 20:48:48.066307 180868 main.go:141] libmachine: (old-k8s-version-239115) </rng>
I0731 20:48:48.066314 180868 main.go:141] libmachine: (old-k8s-version-239115)
I0731 20:48:48.066324 180868 main.go:141] libmachine: (old-k8s-version-239115)
I0731 20:48:48.066332 180868 main.go:141] libmachine: (old-k8s-version-239115) </devices>
I0731 20:48:48.066342 180868 main.go:141] libmachine: (old-k8s-version-239115) </domain>
I0731 20:48:48.066354 180868 main.go:141] libmachine: (old-k8s-version-239115)
I0731 20:48:48.071100 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:88:44:fd in network default
I0731 20:48:48.071785 180868 main.go:141] libmachine: (old-k8s-version-239115) Ensuring networks are active...
I0731 20:48:48.071810 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:48:48.072592 180868 main.go:141] libmachine: (old-k8s-version-239115) Ensuring network default is active
I0731 20:48:48.072913 180868 main.go:141] libmachine: (old-k8s-version-239115) Ensuring network mk-old-k8s-version-239115 is active
I0731 20:48:48.073454 180868 main.go:141] libmachine: (old-k8s-version-239115) Getting domain xml...
I0731 20:48:48.074176 180868 main.go:141] libmachine: (old-k8s-version-239115) Creating domain...
I0731 20:48:49.488996 180868 main.go:141] libmachine: (old-k8s-version-239115) Waiting to get IP...
I0731 20:48:49.489793 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:48:49.490343 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | unable to find current IP address of domain old-k8s-version-239115 in network mk-old-k8s-version-239115
I0731 20:48:49.490407 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | I0731 20:48:49.490323 182545 retry.go:31] will retry after 275.883979ms: waiting for machine to come up
I0731 20:48:49.768116 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:48:49.768692 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | unable to find current IP address of domain old-k8s-version-239115 in network mk-old-k8s-version-239115
I0731 20:48:49.768720 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | I0731 20:48:49.768637 182545 retry.go:31] will retry after 279.063587ms: waiting for machine to come up
I0731 20:48:50.049035 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:48:50.049660 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | unable to find current IP address of domain old-k8s-version-239115 in network mk-old-k8s-version-239115
I0731 20:48:50.049690 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | I0731 20:48:50.049611 182545 retry.go:31] will retry after 326.399608ms: waiting for machine to come up
I0731 20:48:50.378022 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:48:50.378696 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | unable to find current IP address of domain old-k8s-version-239115 in network mk-old-k8s-version-239115
I0731 20:48:50.378726 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | I0731 20:48:50.378661 182545 retry.go:31] will retry after 499.056133ms: waiting for machine to come up
I0731 20:48:50.879306 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:48:50.879726 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | unable to find current IP address of domain old-k8s-version-239115 in network mk-old-k8s-version-239115
I0731 20:48:50.879752 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | I0731 20:48:50.879676 182545 retry.go:31] will retry after 605.727662ms: waiting for machine to come up
I0731 20:48:51.486746 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:48:51.487275 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | unable to find current IP address of domain old-k8s-version-239115 in network mk-old-k8s-version-239115
I0731 20:48:51.487303 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | I0731 20:48:51.487231 182545 retry.go:31] will retry after 820.139591ms: waiting for machine to come up
I0731 20:48:52.309453 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:48:52.309983 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | unable to find current IP address of domain old-k8s-version-239115 in network mk-old-k8s-version-239115
I0731 20:48:52.310005 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | I0731 20:48:52.309910 182545 retry.go:31] will retry after 935.415763ms: waiting for machine to come up
I0731 20:48:53.247658 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:48:53.248184 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | unable to find current IP address of domain old-k8s-version-239115 in network mk-old-k8s-version-239115
I0731 20:48:53.248207 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | I0731 20:48:53.248116 182545 retry.go:31] will retry after 977.024217ms: waiting for machine to come up
I0731 20:48:54.227117 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:48:54.227585 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | unable to find current IP address of domain old-k8s-version-239115 in network mk-old-k8s-version-239115
I0731 20:48:54.227626 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | I0731 20:48:54.227532 182545 retry.go:31] will retry after 1.55095842s: waiting for machine to come up
I0731 20:48:55.780284 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:48:55.780752 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | unable to find current IP address of domain old-k8s-version-239115 in network mk-old-k8s-version-239115
I0731 20:48:55.780781 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | I0731 20:48:55.780725 182545 retry.go:31] will retry after 2.277142213s: waiting for machine to come up
I0731 20:48:58.059835 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:48:58.060356 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | unable to find current IP address of domain old-k8s-version-239115 in network mk-old-k8s-version-239115
I0731 20:48:58.060385 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | I0731 20:48:58.060294 182545 retry.go:31] will retry after 2.184891535s: waiting for machine to come up
I0731 20:49:00.246698 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:00.247237 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | unable to find current IP address of domain old-k8s-version-239115 in network mk-old-k8s-version-239115
I0731 20:49:00.247281 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | I0731 20:49:00.247189 182545 retry.go:31] will retry after 2.752490743s: waiting for machine to come up
I0731 20:49:03.001602 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:03.002080 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | unable to find current IP address of domain old-k8s-version-239115 in network mk-old-k8s-version-239115
I0731 20:49:03.002121 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | I0731 20:49:03.002022 182545 retry.go:31] will retry after 4.306167039s: waiting for machine to come up
I0731 20:49:07.313287 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:07.313835 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | unable to find current IP address of domain old-k8s-version-239115 in network mk-old-k8s-version-239115
I0731 20:49:07.313863 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | I0731 20:49:07.313789 182545 retry.go:31] will retry after 4.00724258s: waiting for machine to come up
I0731 20:49:11.322498 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:11.323058 180868 main.go:141] libmachine: (old-k8s-version-239115) Found IP for machine: 192.168.61.51
I0731 20:49:11.323086 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has current primary IP address 192.168.61.51 and MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:11.323095 180868 main.go:141] libmachine: (old-k8s-version-239115) Reserving static IP address...
I0731 20:49:11.323490 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | unable to find host DHCP lease matching {name: "old-k8s-version-239115", mac: "52:54:00:5a:70:0d", ip: "192.168.61.51"} in network mk-old-k8s-version-239115
I0731 20:49:11.399586 180868 main.go:141] libmachine: (old-k8s-version-239115) Reserved static IP address: 192.168.61.51
I0731 20:49:11.399621 180868 main.go:141] libmachine: (old-k8s-version-239115) Waiting for SSH to be available...
I0731 20:49:11.399632 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | Getting to WaitForSSH function...
I0731 20:49:11.402443 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:11.402756 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | unable to find host DHCP lease matching {name: "", mac: "52:54:00:5a:70:0d", ip: ""} in network mk-old-k8s-version-239115
I0731 20:49:11.402795 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | unable to find defined IP address of network mk-old-k8s-version-239115 interface with MAC address 52:54:00:5a:70:0d
I0731 20:49:11.402837 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | Using SSH client type: external
I0731 20:49:11.402861 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | Using SSH private key: /home/jenkins/minikube-integration/19355-121704/.minikube/machines/old-k8s-version-239115/id_rsa (-rw-------)
I0731 20:49:11.402939 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | &{[-F /dev/null -o ConnectionAttempts=3 -o ConnectTimeout=10 -o ControlMaster=no -o ControlPath=none -o LogLevel=quiet -o PasswordAuthentication=no -o ServerAliveInterval=60 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null docker@ -o IdentitiesOnly=yes -i /home/jenkins/minikube-integration/19355-121704/.minikube/machines/old-k8s-version-239115/id_rsa -p 22] /usr/bin/ssh <nil>}
I0731 20:49:11.402962 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | About to run SSH command:
I0731 20:49:11.402975 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | exit 0
I0731 20:49:11.406843 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | SSH cmd err, output: exit status 255:
I0731 20:49:11.406869 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | Error getting ssh command 'exit 0' : ssh command error:
I0731 20:49:11.406880 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | command : exit 0
I0731 20:49:11.406889 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | err : exit status 255
I0731 20:49:11.406900 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | output :
I0731 20:49:14.407861 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | Getting to WaitForSSH function...
I0731 20:49:14.410154 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:14.410543 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:5a:70:0d", ip: ""} in network mk-old-k8s-version-239115: {Iface:virbr3 ExpiryTime:2024-07-31 21:49:04 +0000 UTC Type:0 Mac:52:54:00:5a:70:0d Iaid: IPaddr:192.168.61.51 Prefix:24 Hostname:old-k8s-version-239115 Clientid:01:52:54:00:5a:70:0d}
I0731 20:49:14.410569 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined IP address 192.168.61.51 and MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:14.410695 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | Using SSH client type: external
I0731 20:49:14.410723 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | Using SSH private key: /home/jenkins/minikube-integration/19355-121704/.minikube/machines/old-k8s-version-239115/id_rsa (-rw-------)
I0731 20:49:14.410751 180868 main.go:141] libmachine: (old-k8s-version-239115) 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.61.51 -o IdentitiesOnly=yes -i /home/jenkins/minikube-integration/19355-121704/.minikube/machines/old-k8s-version-239115/id_rsa -p 22] /usr/bin/ssh <nil>}
I0731 20:49:14.410767 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | About to run SSH command:
I0731 20:49:14.410782 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | exit 0
I0731 20:49:14.533713 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | SSH cmd err, output: <nil>:
I0731 20:49:14.533969 180868 main.go:141] libmachine: (old-k8s-version-239115) KVM machine creation complete!
I0731 20:49:14.534257 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetConfigRaw
I0731 20:49:14.534820 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .DriverName
I0731 20:49:14.535016 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .DriverName
I0731 20:49:14.535174 180868 main.go:141] libmachine: Waiting for machine to be running, this may take a few minutes...
I0731 20:49:14.535191 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetState
I0731 20:49:14.536423 180868 main.go:141] libmachine: Detecting operating system of created instance...
I0731 20:49:14.536440 180868 main.go:141] libmachine: Waiting for SSH to be available...
I0731 20:49:14.536448 180868 main.go:141] libmachine: Getting to WaitForSSH function...
I0731 20:49:14.536457 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHHostname
I0731 20:49:14.539053 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:14.539556 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:5a:70:0d", ip: ""} in network mk-old-k8s-version-239115: {Iface:virbr3 ExpiryTime:2024-07-31 21:49:04 +0000 UTC Type:0 Mac:52:54:00:5a:70:0d Iaid: IPaddr:192.168.61.51 Prefix:24 Hostname:old-k8s-version-239115 Clientid:01:52:54:00:5a:70:0d}
I0731 20:49:14.539586 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined IP address 192.168.61.51 and MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:14.539772 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHPort
I0731 20:49:14.539948 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHKeyPath
I0731 20:49:14.540168 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHKeyPath
I0731 20:49:14.540300 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHUsername
I0731 20:49:14.540467 180868 main.go:141] libmachine: Using SSH client type: native
I0731 20:49:14.540675 180868 main.go:141] libmachine: &{{{<nil> 0 [] [] []} docker [0x82da80] 0x8307e0 <nil> [] 0s} 192.168.61.51 22 <nil> <nil>}
I0731 20:49:14.540688 180868 main.go:141] libmachine: About to run SSH command:
exit 0
I0731 20:49:14.640810 180868 main.go:141] libmachine: SSH cmd err, output: <nil>:
I0731 20:49:14.640847 180868 main.go:141] libmachine: Detecting the provisioner...
I0731 20:49:14.640860 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHHostname
I0731 20:49:14.644046 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:14.644429 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:5a:70:0d", ip: ""} in network mk-old-k8s-version-239115: {Iface:virbr3 ExpiryTime:2024-07-31 21:49:04 +0000 UTC Type:0 Mac:52:54:00:5a:70:0d Iaid: IPaddr:192.168.61.51 Prefix:24 Hostname:old-k8s-version-239115 Clientid:01:52:54:00:5a:70:0d}
I0731 20:49:14.644476 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined IP address 192.168.61.51 and MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:14.644595 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHPort
I0731 20:49:14.644786 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHKeyPath
I0731 20:49:14.644941 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHKeyPath
I0731 20:49:14.645098 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHUsername
I0731 20:49:14.645289 180868 main.go:141] libmachine: Using SSH client type: native
I0731 20:49:14.645537 180868 main.go:141] libmachine: &{{{<nil> 0 [] [] []} docker [0x82da80] 0x8307e0 <nil> [] 0s} 192.168.61.51 22 <nil> <nil>}
I0731 20:49:14.645552 180868 main.go:141] libmachine: About to run SSH command:
cat /etc/os-release
I0731 20:49:14.746678 180868 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"
I0731 20:49:14.746821 180868 main.go:141] libmachine: found compatible host: buildroot
I0731 20:49:14.746837 180868 main.go:141] libmachine: Provisioning with buildroot...
I0731 20:49:14.746845 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetMachineName
I0731 20:49:14.747094 180868 buildroot.go:166] provisioning hostname "old-k8s-version-239115"
I0731 20:49:14.747120 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetMachineName
I0731 20:49:14.747342 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHHostname
I0731 20:49:14.750149 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:14.750647 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:5a:70:0d", ip: ""} in network mk-old-k8s-version-239115: {Iface:virbr3 ExpiryTime:2024-07-31 21:49:04 +0000 UTC Type:0 Mac:52:54:00:5a:70:0d Iaid: IPaddr:192.168.61.51 Prefix:24 Hostname:old-k8s-version-239115 Clientid:01:52:54:00:5a:70:0d}
I0731 20:49:14.750675 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined IP address 192.168.61.51 and MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:14.750959 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHPort
I0731 20:49:14.751157 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHKeyPath
I0731 20:49:14.751316 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHKeyPath
I0731 20:49:14.751450 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHUsername
I0731 20:49:14.751606 180868 main.go:141] libmachine: Using SSH client type: native
I0731 20:49:14.751829 180868 main.go:141] libmachine: &{{{<nil> 0 [] [] []} docker [0x82da80] 0x8307e0 <nil> [] 0s} 192.168.61.51 22 <nil> <nil>}
I0731 20:49:14.751843 180868 main.go:141] libmachine: About to run SSH command:
sudo hostname old-k8s-version-239115 && echo "old-k8s-version-239115" | sudo tee /etc/hostname
I0731 20:49:14.868815 180868 main.go:141] libmachine: SSH cmd err, output: <nil>: old-k8s-version-239115
I0731 20:49:14.868848 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHHostname
I0731 20:49:14.871854 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:14.872149 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:5a:70:0d", ip: ""} in network mk-old-k8s-version-239115: {Iface:virbr3 ExpiryTime:2024-07-31 21:49:04 +0000 UTC Type:0 Mac:52:54:00:5a:70:0d Iaid: IPaddr:192.168.61.51 Prefix:24 Hostname:old-k8s-version-239115 Clientid:01:52:54:00:5a:70:0d}
I0731 20:49:14.872197 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined IP address 192.168.61.51 and MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:14.872334 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHPort
I0731 20:49:14.872575 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHKeyPath
I0731 20:49:14.872730 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHKeyPath
I0731 20:49:14.872898 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHUsername
I0731 20:49:14.873057 180868 main.go:141] libmachine: Using SSH client type: native
I0731 20:49:14.873277 180868 main.go:141] libmachine: &{{{<nil> 0 [] [] []} docker [0x82da80] 0x8307e0 <nil> [] 0s} 192.168.61.51 22 <nil> <nil>}
I0731 20:49:14.873296 180868 main.go:141] libmachine: About to run SSH command:
if ! grep -xq '.*\sold-k8s-version-239115' /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-239115/g' /etc/hosts;
else
echo '127.0.1.1 old-k8s-version-239115' | sudo tee -a /etc/hosts;
fi
fi
I0731 20:49:14.983434 180868 main.go:141] libmachine: SSH cmd err, output: <nil>:
I0731 20:49:14.983469 180868 buildroot.go:172] set auth options {CertDir:/home/jenkins/minikube-integration/19355-121704/.minikube CaCertPath:/home/jenkins/minikube-integration/19355-121704/.minikube/certs/ca.pem CaPrivateKeyPath:/home/jenkins/minikube-integration/19355-121704/.minikube/certs/ca-key.pem CaCertRemotePath:/etc/docker/ca.pem ServerCertPath:/home/jenkins/minikube-integration/19355-121704/.minikube/machines/server.pem ServerKeyPath:/home/jenkins/minikube-integration/19355-121704/.minikube/machines/server-key.pem ClientKeyPath:/home/jenkins/minikube-integration/19355-121704/.minikube/certs/key.pem ServerCertRemotePath:/etc/docker/server.pem ServerKeyRemotePath:/etc/docker/server-key.pem ClientCertPath:/home/jenkins/minikube-integration/19355-121704/.minikube/certs/cert.pem ServerCertSANs:[] StorePath:/home/jenkins/minikube-integration/19355-121704/.minikube}
I0731 20:49:14.983511 180868 buildroot.go:174] setting up certificates
I0731 20:49:14.983524 180868 provision.go:84] configureAuth start
I0731 20:49:14.983539 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetMachineName
I0731 20:49:14.983887 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetIP
I0731 20:49:14.986591 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:14.986896 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:5a:70:0d", ip: ""} in network mk-old-k8s-version-239115: {Iface:virbr3 ExpiryTime:2024-07-31 21:49:04 +0000 UTC Type:0 Mac:52:54:00:5a:70:0d Iaid: IPaddr:192.168.61.51 Prefix:24 Hostname:old-k8s-version-239115 Clientid:01:52:54:00:5a:70:0d}
I0731 20:49:14.986928 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined IP address 192.168.61.51 and MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:14.987059 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHHostname
I0731 20:49:14.989183 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:14.989538 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:5a:70:0d", ip: ""} in network mk-old-k8s-version-239115: {Iface:virbr3 ExpiryTime:2024-07-31 21:49:04 +0000 UTC Type:0 Mac:52:54:00:5a:70:0d Iaid: IPaddr:192.168.61.51 Prefix:24 Hostname:old-k8s-version-239115 Clientid:01:52:54:00:5a:70:0d}
I0731 20:49:14.989577 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined IP address 192.168.61.51 and MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:14.989711 180868 provision.go:143] copyHostCerts
I0731 20:49:14.989773 180868 exec_runner.go:144] found /home/jenkins/minikube-integration/19355-121704/.minikube/key.pem, removing ...
I0731 20:49:14.989789 180868 exec_runner.go:203] rm: /home/jenkins/minikube-integration/19355-121704/.minikube/key.pem
I0731 20:49:14.989843 180868 exec_runner.go:151] cp: /home/jenkins/minikube-integration/19355-121704/.minikube/certs/key.pem --> /home/jenkins/minikube-integration/19355-121704/.minikube/key.pem (1675 bytes)
I0731 20:49:14.989926 180868 exec_runner.go:144] found /home/jenkins/minikube-integration/19355-121704/.minikube/ca.pem, removing ...
I0731 20:49:14.989934 180868 exec_runner.go:203] rm: /home/jenkins/minikube-integration/19355-121704/.minikube/ca.pem
I0731 20:49:14.989953 180868 exec_runner.go:151] cp: /home/jenkins/minikube-integration/19355-121704/.minikube/certs/ca.pem --> /home/jenkins/minikube-integration/19355-121704/.minikube/ca.pem (1082 bytes)
I0731 20:49:14.990005 180868 exec_runner.go:144] found /home/jenkins/minikube-integration/19355-121704/.minikube/cert.pem, removing ...
I0731 20:49:14.990013 180868 exec_runner.go:203] rm: /home/jenkins/minikube-integration/19355-121704/.minikube/cert.pem
I0731 20:49:14.990029 180868 exec_runner.go:151] cp: /home/jenkins/minikube-integration/19355-121704/.minikube/certs/cert.pem --> /home/jenkins/minikube-integration/19355-121704/.minikube/cert.pem (1123 bytes)
I0731 20:49:14.990111 180868 provision.go:117] generating server cert: /home/jenkins/minikube-integration/19355-121704/.minikube/machines/server.pem ca-key=/home/jenkins/minikube-integration/19355-121704/.minikube/certs/ca.pem private-key=/home/jenkins/minikube-integration/19355-121704/.minikube/certs/ca-key.pem org=jenkins.old-k8s-version-239115 san=[127.0.0.1 192.168.61.51 localhost minikube old-k8s-version-239115]
I0731 20:49:15.170692 180868 provision.go:177] copyRemoteCerts
I0731 20:49:15.170761 180868 ssh_runner.go:195] Run: sudo mkdir -p /etc/docker /etc/docker /etc/docker
I0731 20:49:15.170786 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHHostname
I0731 20:49:15.173594 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:15.173971 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:5a:70:0d", ip: ""} in network mk-old-k8s-version-239115: {Iface:virbr3 ExpiryTime:2024-07-31 21:49:04 +0000 UTC Type:0 Mac:52:54:00:5a:70:0d Iaid: IPaddr:192.168.61.51 Prefix:24 Hostname:old-k8s-version-239115 Clientid:01:52:54:00:5a:70:0d}
I0731 20:49:15.174003 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined IP address 192.168.61.51 and MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:15.174246 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHPort
I0731 20:49:15.174456 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHKeyPath
I0731 20:49:15.174639 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHUsername
I0731 20:49:15.174770 180868 sshutil.go:53] new ssh client: &{IP:192.168.61.51 Port:22 SSHKeyPath:/home/jenkins/minikube-integration/19355-121704/.minikube/machines/old-k8s-version-239115/id_rsa Username:docker}
I0731 20:49:15.256125 180868 ssh_runner.go:362] scp /home/jenkins/minikube-integration/19355-121704/.minikube/machines/server-key.pem --> /etc/docker/server-key.pem (1675 bytes)
I0731 20:49:15.283580 180868 ssh_runner.go:362] scp /home/jenkins/minikube-integration/19355-121704/.minikube/certs/ca.pem --> /etc/docker/ca.pem (1082 bytes)
I0731 20:49:15.309503 180868 ssh_runner.go:362] scp /home/jenkins/minikube-integration/19355-121704/.minikube/machines/server.pem --> /etc/docker/server.pem (1233 bytes)
I0731 20:49:15.335838 180868 provision.go:87] duration metric: took 352.29786ms to configureAuth
I0731 20:49:15.335880 180868 buildroot.go:189] setting minikube options for container-runtime
I0731 20:49:15.336131 180868 config.go:182] Loaded profile config "old-k8s-version-239115": Driver=kvm2, ContainerRuntime=crio, KubernetesVersion=v1.20.0
I0731 20:49:15.336283 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHHostname
I0731 20:49:15.339328 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:15.339794 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:5a:70:0d", ip: ""} in network mk-old-k8s-version-239115: {Iface:virbr3 ExpiryTime:2024-07-31 21:49:04 +0000 UTC Type:0 Mac:52:54:00:5a:70:0d Iaid: IPaddr:192.168.61.51 Prefix:24 Hostname:old-k8s-version-239115 Clientid:01:52:54:00:5a:70:0d}
I0731 20:49:15.339824 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined IP address 192.168.61.51 and MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:15.340037 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHPort
I0731 20:49:15.340232 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHKeyPath
I0731 20:49:15.340407 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHKeyPath
I0731 20:49:15.340551 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHUsername
I0731 20:49:15.340825 180868 main.go:141] libmachine: Using SSH client type: native
I0731 20:49:15.341012 180868 main.go:141] libmachine: &{{{<nil> 0 [] [] []} docker [0x82da80] 0x8307e0 <nil> [] 0s} 192.168.61.51 22 <nil> <nil>}
I0731 20:49:15.341029 180868 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
I0731 20:49:15.620211 180868 main.go:141] libmachine: SSH cmd err, output: <nil>:
CRIO_MINIKUBE_OPTIONS='--insecure-registry 10.96.0.0/12 '
I0731 20:49:15.620251 180868 main.go:141] libmachine: Checking connection to Docker...
I0731 20:49:15.620264 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetURL
I0731 20:49:15.621625 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | Using libvirt version 6000000
I0731 20:49:15.623988 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:15.624294 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:5a:70:0d", ip: ""} in network mk-old-k8s-version-239115: {Iface:virbr3 ExpiryTime:2024-07-31 21:49:04 +0000 UTC Type:0 Mac:52:54:00:5a:70:0d Iaid: IPaddr:192.168.61.51 Prefix:24 Hostname:old-k8s-version-239115 Clientid:01:52:54:00:5a:70:0d}
I0731 20:49:15.624324 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined IP address 192.168.61.51 and MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:15.624470 180868 main.go:141] libmachine: Docker is up and running!
I0731 20:49:15.624487 180868 main.go:141] libmachine: Reticulating splines...
I0731 20:49:15.624496 180868 client.go:171] duration metric: took 28.036396515s to LocalClient.Create
I0731 20:49:15.624523 180868 start.go:167] duration metric: took 28.036467385s to libmachine.API.Create "old-k8s-version-239115"
I0731 20:49:15.624546 180868 start.go:293] postStartSetup for "old-k8s-version-239115" (driver="kvm2")
I0731 20:49:15.624560 180868 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]
I0731 20:49:15.624584 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .DriverName
I0731 20:49:15.624892 180868 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
I0731 20:49:15.624924 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHHostname
I0731 20:49:15.627101 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:15.627398 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:5a:70:0d", ip: ""} in network mk-old-k8s-version-239115: {Iface:virbr3 ExpiryTime:2024-07-31 21:49:04 +0000 UTC Type:0 Mac:52:54:00:5a:70:0d Iaid: IPaddr:192.168.61.51 Prefix:24 Hostname:old-k8s-version-239115 Clientid:01:52:54:00:5a:70:0d}
I0731 20:49:15.627427 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined IP address 192.168.61.51 and MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:15.627554 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHPort
I0731 20:49:15.627752 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHKeyPath
I0731 20:49:15.627921 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHUsername
I0731 20:49:15.628085 180868 sshutil.go:53] new ssh client: &{IP:192.168.61.51 Port:22 SSHKeyPath:/home/jenkins/minikube-integration/19355-121704/.minikube/machines/old-k8s-version-239115/id_rsa Username:docker}
I0731 20:49:15.708166 180868 ssh_runner.go:195] Run: cat /etc/os-release
I0731 20:49:15.713088 180868 info.go:137] Remote host: Buildroot 2023.02.9
I0731 20:49:15.713117 180868 filesync.go:126] Scanning /home/jenkins/minikube-integration/19355-121704/.minikube/addons for local assets ...
I0731 20:49:15.713202 180868 filesync.go:126] Scanning /home/jenkins/minikube-integration/19355-121704/.minikube/files for local assets ...
I0731 20:49:15.713303 180868 filesync.go:149] local asset: /home/jenkins/minikube-integration/19355-121704/.minikube/files/etc/ssl/certs/1288912.pem -> 1288912.pem in /etc/ssl/certs
I0731 20:49:15.713453 180868 ssh_runner.go:195] Run: sudo mkdir -p /etc/ssl/certs
I0731 20:49:15.723940 180868 ssh_runner.go:362] scp /home/jenkins/minikube-integration/19355-121704/.minikube/files/etc/ssl/certs/1288912.pem --> /etc/ssl/certs/1288912.pem (1708 bytes)
I0731 20:49:15.754576 180868 start.go:296] duration metric: took 130.011597ms for postStartSetup
I0731 20:49:15.754643 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetConfigRaw
I0731 20:49:15.755301 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetIP
I0731 20:49:15.758245 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:15.758625 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:5a:70:0d", ip: ""} in network mk-old-k8s-version-239115: {Iface:virbr3 ExpiryTime:2024-07-31 21:49:04 +0000 UTC Type:0 Mac:52:54:00:5a:70:0d Iaid: IPaddr:192.168.61.51 Prefix:24 Hostname:old-k8s-version-239115 Clientid:01:52:54:00:5a:70:0d}
I0731 20:49:15.758658 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined IP address 192.168.61.51 and MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:15.758970 180868 profile.go:143] Saving config to /home/jenkins/minikube-integration/19355-121704/.minikube/profiles/old-k8s-version-239115/config.json ...
I0731 20:49:15.759228 180868 start.go:128] duration metric: took 28.192781051s to createHost
I0731 20:49:15.759256 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHHostname
I0731 20:49:15.761496 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:15.761803 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:5a:70:0d", ip: ""} in network mk-old-k8s-version-239115: {Iface:virbr3 ExpiryTime:2024-07-31 21:49:04 +0000 UTC Type:0 Mac:52:54:00:5a:70:0d Iaid: IPaddr:192.168.61.51 Prefix:24 Hostname:old-k8s-version-239115 Clientid:01:52:54:00:5a:70:0d}
I0731 20:49:15.761831 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined IP address 192.168.61.51 and MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:15.761936 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHPort
I0731 20:49:15.762113 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHKeyPath
I0731 20:49:15.762271 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHKeyPath
I0731 20:49:15.762381 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHUsername
I0731 20:49:15.762500 180868 main.go:141] libmachine: Using SSH client type: native
I0731 20:49:15.762669 180868 main.go:141] libmachine: &{{{<nil> 0 [] [] []} docker [0x82da80] 0x8307e0 <nil> [] 0s} 192.168.61.51 22 <nil> <nil>}
I0731 20:49:15.762679 180868 main.go:141] libmachine: About to run SSH command:
date +%s.%N
I0731 20:49:15.862275 180868 main.go:141] libmachine: SSH cmd err, output: <nil>: 1722458955.839039667
I0731 20:49:15.862298 180868 fix.go:216] guest clock: 1722458955.839039667
I0731 20:49:15.862305 180868 fix.go:229] Guest: 2024-07-31 20:49:15.839039667 +0000 UTC Remote: 2024-07-31 20:49:15.759241805 +0000 UTC m=+72.612524077 (delta=79.797862ms)
I0731 20:49:15.862325 180868 fix.go:200] guest clock delta is within tolerance: 79.797862ms
I0731 20:49:15.862331 180868 start.go:83] releasing machines lock for "old-k8s-version-239115", held for 28.296041184s
I0731 20:49:15.862353 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .DriverName
I0731 20:49:15.862658 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetIP
I0731 20:49:15.865581 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:15.865969 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:5a:70:0d", ip: ""} in network mk-old-k8s-version-239115: {Iface:virbr3 ExpiryTime:2024-07-31 21:49:04 +0000 UTC Type:0 Mac:52:54:00:5a:70:0d Iaid: IPaddr:192.168.61.51 Prefix:24 Hostname:old-k8s-version-239115 Clientid:01:52:54:00:5a:70:0d}
I0731 20:49:15.866013 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined IP address 192.168.61.51 and MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:15.866185 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .DriverName
I0731 20:49:15.866765 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .DriverName
I0731 20:49:15.866972 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .DriverName
I0731 20:49:15.867074 180868 ssh_runner.go:195] Run: curl -sS -m 2 https://registry.k8s.io/
I0731 20:49:15.867120 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHHostname
I0731 20:49:15.867245 180868 ssh_runner.go:195] Run: cat /version.json
I0731 20:49:15.867270 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHHostname
I0731 20:49:15.869970 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:15.870338 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:5a:70:0d", ip: ""} in network mk-old-k8s-version-239115: {Iface:virbr3 ExpiryTime:2024-07-31 21:49:04 +0000 UTC Type:0 Mac:52:54:00:5a:70:0d Iaid: IPaddr:192.168.61.51 Prefix:24 Hostname:old-k8s-version-239115 Clientid:01:52:54:00:5a:70:0d}
I0731 20:49:15.870410 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined IP address 192.168.61.51 and MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:15.870443 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:15.870569 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHPort
I0731 20:49:15.870741 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHKeyPath
I0731 20:49:15.870888 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:5a:70:0d", ip: ""} in network mk-old-k8s-version-239115: {Iface:virbr3 ExpiryTime:2024-07-31 21:49:04 +0000 UTC Type:0 Mac:52:54:00:5a:70:0d Iaid: IPaddr:192.168.61.51 Prefix:24 Hostname:old-k8s-version-239115 Clientid:01:52:54:00:5a:70:0d}
I0731 20:49:15.870912 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined IP address 192.168.61.51 and MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:15.870923 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHUsername
I0731 20:49:15.871088 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHPort
I0731 20:49:15.871098 180868 sshutil.go:53] new ssh client: &{IP:192.168.61.51 Port:22 SSHKeyPath:/home/jenkins/minikube-integration/19355-121704/.minikube/machines/old-k8s-version-239115/id_rsa Username:docker}
I0731 20:49:15.871254 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHKeyPath
I0731 20:49:15.871403 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetSSHUsername
I0731 20:49:15.871551 180868 sshutil.go:53] new ssh client: &{IP:192.168.61.51 Port:22 SSHKeyPath:/home/jenkins/minikube-integration/19355-121704/.minikube/machines/old-k8s-version-239115/id_rsa Username:docker}
I0731 20:49:15.950965 180868 ssh_runner.go:195] Run: systemctl --version
I0731 20:49:15.979478 180868 ssh_runner.go:195] Run: sudo sh -c "podman version >/dev/null"
I0731 20:49:16.157005 180868 ssh_runner.go:195] Run: sh -c "stat /etc/cni/net.d/*loopback.conf*"
W0731 20:49:16.164075 180868 cni.go:209] loopback cni configuration skipped: "/etc/cni/net.d/*loopback.conf*" not found
I0731 20:49:16.164155 180868 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" ;
I0731 20:49:16.182439 180868 cni.go:262] disabled [/etc/cni/net.d/87-podman-bridge.conflist] bridge cni config(s)
I0731 20:49:16.182480 180868 start.go:495] detecting cgroup driver to use...
I0731 20:49:16.182553 180868 ssh_runner.go:195] Run: sudo systemctl stop -f containerd
I0731 20:49:16.206510 180868 ssh_runner.go:195] Run: sudo systemctl is-active --quiet service containerd
I0731 20:49:16.221774 180868 docker.go:217] disabling cri-docker service (if available) ...
I0731 20:49:16.221846 180868 ssh_runner.go:195] Run: sudo systemctl stop -f cri-docker.socket
I0731 20:49:16.242932 180868 ssh_runner.go:195] Run: sudo systemctl stop -f cri-docker.service
I0731 20:49:16.260890 180868 ssh_runner.go:195] Run: sudo systemctl disable cri-docker.socket
I0731 20:49:16.400206 180868 ssh_runner.go:195] Run: sudo systemctl mask cri-docker.service
I0731 20:49:16.568845 180868 docker.go:233] disabling docker service ...
I0731 20:49:16.568903 180868 ssh_runner.go:195] Run: sudo systemctl stop -f docker.socket
I0731 20:49:16.585322 180868 ssh_runner.go:195] Run: sudo systemctl stop -f docker.service
I0731 20:49:16.598790 180868 ssh_runner.go:195] Run: sudo systemctl disable docker.socket
I0731 20:49:16.739005 180868 ssh_runner.go:195] Run: sudo systemctl mask docker.service
I0731 20:49:16.866788 180868 ssh_runner.go:195] Run: sudo systemctl is-active --quiet service docker
I0731 20:49:16.881945 180868 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"
I0731 20:49:16.902431 180868 crio.go:59] configure cri-o to use "registry.k8s.io/pause:3.2" pause image...
I0731 20:49:16.902497 180868 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"
I0731 20:49:16.912716 180868 crio.go:70] configuring cri-o to use "cgroupfs" as cgroup driver...
I0731 20:49:16.912790 180868 ssh_runner.go:195] Run: sh -c "sudo sed -i 's|^.*cgroup_manager = .*$|cgroup_manager = "cgroupfs"|' /etc/crio/crio.conf.d/02-crio.conf"
I0731 20:49:16.923492 180868 ssh_runner.go:195] Run: sh -c "sudo sed -i '/conmon_cgroup = .*/d' /etc/crio/crio.conf.d/02-crio.conf"
I0731 20:49:16.934312 180868 ssh_runner.go:195] Run: sh -c "sudo sed -i '/cgroup_manager = .*/a conmon_cgroup = "pod"' /etc/crio/crio.conf.d/02-crio.conf"
I0731 20:49:16.945068 180868 ssh_runner.go:195] Run: sh -c "sudo rm -rf /etc/cni/net.mk"
I0731 20:49:16.958577 180868 ssh_runner.go:195] Run: sudo sysctl net.bridge.bridge-nf-call-iptables
I0731 20:49:16.970338 180868 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
I0731 20:49:16.970403 180868 ssh_runner.go:195] Run: sudo modprobe br_netfilter
I0731 20:49:16.983942 180868 ssh_runner.go:195] Run: sudo sh -c "echo 1 > /proc/sys/net/ipv4/ip_forward"
I0731 20:49:16.993979 180868 ssh_runner.go:195] Run: sudo systemctl daemon-reload
I0731 20:49:17.115305 180868 ssh_runner.go:195] Run: sudo systemctl restart crio
I0731 20:49:17.296878 180868 start.go:542] Will wait 60s for socket path /var/run/crio/crio.sock
I0731 20:49:17.296970 180868 ssh_runner.go:195] Run: stat /var/run/crio/crio.sock
I0731 20:49:17.301806 180868 start.go:563] Will wait 60s for crictl version
I0731 20:49:17.301868 180868 ssh_runner.go:195] Run: which crictl
I0731 20:49:17.306029 180868 ssh_runner.go:195] Run: sudo /usr/bin/crictl version
I0731 20:49:17.359143 180868 start.go:579] Version: 0.1.0
RuntimeName: cri-o
RuntimeVersion: 1.29.1
RuntimeApiVersion: v1
I0731 20:49:17.359224 180868 ssh_runner.go:195] Run: crio --version
I0731 20:49:17.389713 180868 ssh_runner.go:195] Run: crio --version
I0731 20:49:17.425359 180868 out.go:177] * Preparing Kubernetes v1.20.0 on CRI-O 1.29.1 ...
I0731 20:49:17.426668 180868 main.go:141] libmachine: (old-k8s-version-239115) Calling .GetIP
I0731 20:49:17.430106 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:17.430547 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:5a:70:0d", ip: ""} in network mk-old-k8s-version-239115: {Iface:virbr3 ExpiryTime:2024-07-31 21:49:04 +0000 UTC Type:0 Mac:52:54:00:5a:70:0d Iaid: IPaddr:192.168.61.51 Prefix:24 Hostname:old-k8s-version-239115 Clientid:01:52:54:00:5a:70:0d}
I0731 20:49:17.430578 180868 main.go:141] libmachine: (old-k8s-version-239115) DBG | domain old-k8s-version-239115 has defined IP address 192.168.61.51 and MAC address 52:54:00:5a:70:0d in network mk-old-k8s-version-239115
I0731 20:49:17.430815 180868 ssh_runner.go:195] Run: grep 192.168.61.1 host.minikube.internal$ /etc/hosts
I0731 20:49:17.435123 180868 ssh_runner.go:195] Run: /bin/bash -c "{ grep -v $'\thost.minikube.internal$' "/etc/hosts"; echo "192.168.61.1 host.minikube.internal"; } > /tmp/h.$$; sudo cp /tmp/h.$$ "/etc/hosts""
I0731 20:49:17.449161 180868 kubeadm.go:883] updating cluster {Name:old-k8s-version-239115 KeepContext:false EmbedCerts:false MinikubeISO:https://storage.googleapis.com/minikube-builds/iso/19355/minikube-v1.33.1-1722420371-19355-amd64.iso KicBaseImage:gcr.io/k8s-minikube/kicbase-builds:v0.0.44-1721902582-19326@sha256:540fb5dc7f38be17ff5276a38dfe6c8a4b1d9ba1c27c62244e6eebd7e37696e7 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:{KubernetesVersio
n:v1.20.0 ClusterName:old-k8s-version-239115 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.61.51 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:[] Mo
untPort:0 MountType:9p MountUID:docker BinaryMirror: DisableOptimizations:false DisableMetrics:false CustomQemuFirmwarePath: SocketVMnetClientPath: SocketVMnetPath: StaticIP: SSHAuthSock: SSHAgentPID:0 GPUs: AutoPauseInterval:1m0s} ...
I0731 20:49:17.449278 180868 preload.go:131] Checking if preload exists for k8s version v1.20.0 and runtime crio
I0731 20:49:17.449357 180868 ssh_runner.go:195] Run: sudo crictl images --output json
I0731 20:49:17.485042 180868 crio.go:510] couldn't find preloaded image for "registry.k8s.io/kube-apiserver:v1.20.0". assuming images are not preloaded.
I0731 20:49:17.485115 180868 ssh_runner.go:195] Run: which lz4
I0731 20:49:17.490267 180868 ssh_runner.go:195] Run: stat -c "%s %y" /preloaded.tar.lz4
I0731 20:49:17.495397 180868 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
I0731 20:49:17.495432 180868 ssh_runner.go:362] scp /home/jenkins/minikube-integration/19355-121704/.minikube/cache/preloaded-tarball/preloaded-images-k8s-v18-v1.20.0-cri-o-overlay-amd64.tar.lz4 --> /preloaded.tar.lz4 (473237281 bytes)
I0731 20:49:19.321488 180868 crio.go:462] duration metric: took 1.831258201s to copy over tarball
I0731 20:49:19.321588 180868 ssh_runner.go:195] Run: sudo tar --xattrs --xattrs-include security.capability -I lz4 -C /var -xf /preloaded.tar.lz4
I0731 20:49:22.719379 180868 ssh_runner.go:235] Completed: sudo tar --xattrs --xattrs-include security.capability -I lz4 -C /var -xf /preloaded.tar.lz4: (3.397721815s)
I0731 20:49:22.719408 180868 crio.go:469] duration metric: took 3.397874265s to extract the tarball
I0731 20:49:22.719418 180868 ssh_runner.go:146] rm: /preloaded.tar.lz4
I0731 20:49:22.767503 180868 ssh_runner.go:195] Run: sudo crictl images --output json
I0731 20:49:22.866995 180868 crio.go:510] couldn't find preloaded image for "registry.k8s.io/kube-apiserver:v1.20.0". assuming images are not preloaded.
I0731 20:49:22.867026 180868 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]
I0731 20:49:22.867128 180868 image.go:134] retrieving image: gcr.io/k8s-minikube/storage-provisioner:v5
I0731 20:49:22.867130 180868 image.go:134] retrieving image: registry.k8s.io/kube-proxy:v1.20.0
I0731 20:49:22.867187 180868 image.go:134] retrieving image: registry.k8s.io/kube-scheduler:v1.20.0
I0731 20:49:22.867195 180868 image.go:134] retrieving image: registry.k8s.io/pause:3.2
I0731 20:49:22.867159 180868 image.go:134] retrieving image: registry.k8s.io/coredns:1.7.0
I0731 20:49:22.867223 180868 image.go:134] retrieving image: registry.k8s.io/kube-controller-manager:v1.20.0
I0731 20:49:22.867235 180868 image.go:134] retrieving image: registry.k8s.io/kube-apiserver:v1.20.0
I0731 20:49:22.867137 180868 image.go:134] retrieving image: registry.k8s.io/etcd:3.4.13-0
I0731 20:49:22.869130 180868 image.go:177] daemon lookup for registry.k8s.io/pause:3.2: Error response from daemon: No such image: registry.k8s.io/pause:3.2
I0731 20:49:22.869157 180868 image.go:177] 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
I0731 20:49:22.869157 180868 image.go:177] 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
I0731 20:49:22.869186 180868 image.go:177] 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
I0731 20:49:22.869197 180868 image.go:177] daemon lookup for registry.k8s.io/coredns:1.7.0: Error response from daemon: No such image: registry.k8s.io/coredns:1.7.0
I0731 20:49:22.869221 180868 image.go:177] daemon lookup for gcr.io/k8s-minikube/storage-provisioner:v5: Error response from daemon: No such image: gcr.io/k8s-minikube/storage-provisioner:v5
I0731 20:49:22.869236 180868 image.go:177] 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
I0731 20:49:22.869245 180868 image.go:177] 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
I0731 20:49:23.021261 180868 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} registry.k8s.io/kube-proxy:v1.20.0
I0731 20:49:23.059839 180868 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} registry.k8s.io/pause:3.2
I0731 20:49:23.061711 180868 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
I0731 20:49:23.061763 180868 cri.go:218] Removing image: registry.k8s.io/kube-proxy:v1.20.0
I0731 20:49:23.061818 180868 ssh_runner.go:195] Run: which crictl
I0731 20:49:23.087957 180868 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} registry.k8s.io/coredns:1.7.0
I0731 20:49:23.096075 180868 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} registry.k8s.io/kube-scheduler:v1.20.0
I0731 20:49:23.108858 180868 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-proxy:v1.20.0
I0731 20:49:23.108949 180868 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
I0731 20:49:23.108990 180868 cri.go:218] Removing image: registry.k8s.io/pause:3.2
I0731 20:49:23.109032 180868 ssh_runner.go:195] Run: which crictl
I0731 20:49:23.190652 180868 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
I0731 20:49:23.190708 180868 cri.go:218] Removing image: registry.k8s.io/coredns:1.7.0
I0731 20:49:23.190763 180868 ssh_runner.go:195] Run: which crictl
I0731 20:49:23.199604 180868 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
I0731 20:49:23.199646 180868 cri.go:218] Removing image: registry.k8s.io/kube-scheduler:v1.20.0
I0731 20:49:23.199695 180868 ssh_runner.go:195] Run: which crictl
I0731 20:49:23.199705 180868 cache_images.go:289] Loading image from: /home/jenkins/minikube-integration/19355-121704/.minikube/cache/images/amd64/registry.k8s.io/kube-proxy_v1.20.0
I0731 20:49:23.199808 180868 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/pause:3.2
I0731 20:49:23.199836 180868 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/coredns:1.7.0
I0731 20:49:23.209291 180868 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} registry.k8s.io/kube-controller-manager:v1.20.0
I0731 20:49:23.209604 180868 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} registry.k8s.io/kube-apiserver:v1.20.0
I0731 20:49:23.215217 180868 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} registry.k8s.io/etcd:3.4.13-0
I0731 20:49:23.287502 180868 cache_images.go:289] Loading image from: /home/jenkins/minikube-integration/19355-121704/.minikube/cache/images/amd64/registry.k8s.io/coredns_1.7.0
I0731 20:49:23.287617 180868 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-scheduler:v1.20.0
I0731 20:49:23.317718 180868 cache_images.go:289] Loading image from: /home/jenkins/minikube-integration/19355-121704/.minikube/cache/images/amd64/registry.k8s.io/pause_3.2
I0731 20:49:23.346917 180868 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
I0731 20:49:23.346992 180868 cri.go:218] Removing image: registry.k8s.io/kube-controller-manager:v1.20.0
I0731 20:49:23.347047 180868 ssh_runner.go:195] Run: which crictl
I0731 20:49:23.368821 180868 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
I0731 20:49:23.368865 180868 cri.go:218] Removing image: registry.k8s.io/kube-apiserver:v1.20.0
I0731 20:49:23.368914 180868 ssh_runner.go:195] Run: which crictl
I0731 20:49:23.373798 180868 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
I0731 20:49:23.373842 180868 cri.go:218] Removing image: registry.k8s.io/etcd:3.4.13-0
I0731 20:49:23.373886 180868 ssh_runner.go:195] Run: which crictl
I0731 20:49:23.378512 180868 cache_images.go:289] Loading image from: /home/jenkins/minikube-integration/19355-121704/.minikube/cache/images/amd64/registry.k8s.io/kube-scheduler_v1.20.0
I0731 20:49:23.378585 180868 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-controller-manager:v1.20.0
I0731 20:49:23.381379 180868 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/etcd:3.4.13-0
I0731 20:49:23.381481 180868 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-apiserver:v1.20.0
I0731 20:49:23.426272 180868 cache_images.go:289] Loading image from: /home/jenkins/minikube-integration/19355-121704/.minikube/cache/images/amd64/registry.k8s.io/kube-controller-manager_v1.20.0
I0731 20:49:23.446002 180868 cache_images.go:289] Loading image from: /home/jenkins/minikube-integration/19355-121704/.minikube/cache/images/amd64/registry.k8s.io/etcd_3.4.13-0
I0731 20:49:23.454381 180868 cache_images.go:289] Loading image from: /home/jenkins/minikube-integration/19355-121704/.minikube/cache/images/amd64/registry.k8s.io/kube-apiserver_v1.20.0
I0731 20:49:23.778486 180868 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} gcr.io/k8s-minikube/storage-provisioner:v5
I0731 20:49:23.922158 180868 cache_images.go:92] duration metric: took 1.055111179s to LoadCachedImages
W0731 20:49:23.922254 180868 out.go:239] X Unable to load cached images: LoadCachedImages: stat /home/jenkins/minikube-integration/19355-121704/.minikube/cache/images/amd64/registry.k8s.io/kube-proxy_v1.20.0: no such file or directory
X Unable to load cached images: LoadCachedImages: stat /home/jenkins/minikube-integration/19355-121704/.minikube/cache/images/amd64/registry.k8s.io/kube-proxy_v1.20.0: no such file or directory
I0731 20:49:23.922267 180868 kubeadm.go:934] updating node { 192.168.61.51 8443 v1.20.0 crio true true} ...
I0731 20:49:23.922404 180868 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-239115 --kubeconfig=/etc/kubernetes/kubelet.conf --network-plugin=cni --node-ip=192.168.61.51
[Install]
config:
{KubernetesVersion:v1.20.0 ClusterName:old-k8s-version-239115 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:}
I0731 20:49:23.922511 180868 ssh_runner.go:195] Run: crio config
I0731 20:49:23.992620 180868 cni.go:84] Creating CNI manager for ""
I0731 20:49:23.992646 180868 cni.go:146] "kvm2" driver + "crio" runtime found, recommending bridge
I0731 20:49:23.992659 180868 kubeadm.go:84] Using pod CIDR: 10.244.0.0/16
I0731 20:49:23.992685 180868 kubeadm.go:181] kubeadm options: {CertDir:/var/lib/minikube/certs ServiceCIDR:10.96.0.0/12 PodSubnet:10.244.0.0/16 AdvertiseAddress:192.168.61.51 APIServerPort:8443 KubernetesVersion:v1.20.0 EtcdDataDir:/var/lib/minikube/etcd EtcdExtraArgs:map[] ClusterName:old-k8s-version-239115 NodeName:old-k8s-version-239115 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.61.51"]]} {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.61.51 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}
I0731 20:49:23.992964 180868 kubeadm.go:187] kubeadm config:
apiVersion: kubeadm.k8s.io/v1beta2
kind: InitConfiguration
localAPIEndpoint:
advertiseAddress: 192.168.61.51
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-239115"
kubeletExtraArgs:
node-ip: 192.168.61.51
taints: []
---
apiVersion: kubeadm.k8s.io/v1beta2
kind: ClusterConfiguration
apiServer:
certSANs: ["127.0.0.1", "localhost", "192.168.61.51"]
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
I0731 20:49:23.993061 180868 ssh_runner.go:195] Run: sudo ls /var/lib/minikube/binaries/v1.20.0
I0731 20:49:24.007236 180868 binaries.go:44] Found k8s binaries, skipping transfer
I0731 20:49:24.007311 180868 ssh_runner.go:195] Run: sudo mkdir -p /etc/systemd/system/kubelet.service.d /lib/systemd/system /var/tmp/minikube
I0731 20:49:24.017859 180868 ssh_runner.go:362] scp memory --> /etc/systemd/system/kubelet.service.d/10-kubeadm.conf (429 bytes)
I0731 20:49:24.041131 180868 ssh_runner.go:362] scp memory --> /lib/systemd/system/kubelet.service (352 bytes)
I0731 20:49:24.060443 180868 ssh_runner.go:362] scp memory --> /var/tmp/minikube/kubeadm.yaml.new (2120 bytes)
I0731 20:49:24.081858 180868 ssh_runner.go:195] Run: grep 192.168.61.51 control-plane.minikube.internal$ /etc/hosts
I0731 20:49:24.087325 180868 ssh_runner.go:195] Run: /bin/bash -c "{ grep -v $'\tcontrol-plane.minikube.internal$' "/etc/hosts"; echo "192.168.61.51 control-plane.minikube.internal"; } > /tmp/h.$$; sudo cp /tmp/h.$$ "/etc/hosts""
I0731 20:49:24.104843 180868 ssh_runner.go:195] Run: sudo systemctl daemon-reload
I0731 20:49:24.268405 180868 ssh_runner.go:195] Run: sudo systemctl start kubelet
I0731 20:49:24.292251 180868 certs.go:68] Setting up /home/jenkins/minikube-integration/19355-121704/.minikube/profiles/old-k8s-version-239115 for IP: 192.168.61.51
I0731 20:49:24.292278 180868 certs.go:194] generating shared ca certs ...
I0731 20:49:24.292300 180868 certs.go:226] acquiring lock for ca certs: {Name:mk321e55c51459eef33684f5f907e6de3f519b09 Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0731 20:49:24.292560 180868 certs.go:235] skipping valid "minikubeCA" ca cert: /home/jenkins/minikube-integration/19355-121704/.minikube/ca.key
I0731 20:49:24.292645 180868 certs.go:235] skipping valid "proxyClientCA" ca cert: /home/jenkins/minikube-integration/19355-121704/.minikube/proxy-client-ca.key
I0731 20:49:24.292661 180868 certs.go:256] generating profile certs ...
I0731 20:49:24.292750 180868 certs.go:363] generating signed profile cert for "minikube-user": /home/jenkins/minikube-integration/19355-121704/.minikube/profiles/old-k8s-version-239115/client.key
I0731 20:49:24.292769 180868 crypto.go:68] Generating cert /home/jenkins/minikube-integration/19355-121704/.minikube/profiles/old-k8s-version-239115/client.crt with IP's: []
I0731 20:49:24.588977 180868 crypto.go:156] Writing cert to /home/jenkins/minikube-integration/19355-121704/.minikube/profiles/old-k8s-version-239115/client.crt ...
I0731 20:49:24.589017 180868 lock.go:35] WriteFile acquiring /home/jenkins/minikube-integration/19355-121704/.minikube/profiles/old-k8s-version-239115/client.crt: {Name:mk31ffb3d18c5f0788419774544bcda595753544 Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0731 20:49:24.589259 180868 crypto.go:164] Writing key to /home/jenkins/minikube-integration/19355-121704/.minikube/profiles/old-k8s-version-239115/client.key ...
I0731 20:49:24.589281 180868 lock.go:35] WriteFile acquiring /home/jenkins/minikube-integration/19355-121704/.minikube/profiles/old-k8s-version-239115/client.key: {Name:mk7cc49529eb8756b1cb804c6c11337d96a036db Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0731 20:49:24.589423 180868 certs.go:363] generating signed profile cert for "minikube": /home/jenkins/minikube-integration/19355-121704/.minikube/profiles/old-k8s-version-239115/apiserver.key.072d7f83
I0731 20:49:24.589446 180868 crypto.go:68] Generating cert /home/jenkins/minikube-integration/19355-121704/.minikube/profiles/old-k8s-version-239115/apiserver.crt.072d7f83 with IP's: [10.96.0.1 127.0.0.1 10.0.0.1 192.168.61.51]
I0731 20:49:24.950738 180868 crypto.go:156] Writing cert to /home/jenkins/minikube-integration/19355-121704/.minikube/profiles/old-k8s-version-239115/apiserver.crt.072d7f83 ...
I0731 20:49:24.950772 180868 lock.go:35] WriteFile acquiring /home/jenkins/minikube-integration/19355-121704/.minikube/profiles/old-k8s-version-239115/apiserver.crt.072d7f83: {Name:mk1267c33021ce69fcd1f868be09b05d8c4557e9 Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0731 20:49:24.950948 180868 crypto.go:164] Writing key to /home/jenkins/minikube-integration/19355-121704/.minikube/profiles/old-k8s-version-239115/apiserver.key.072d7f83 ...
I0731 20:49:24.950964 180868 lock.go:35] WriteFile acquiring /home/jenkins/minikube-integration/19355-121704/.minikube/profiles/old-k8s-version-239115/apiserver.key.072d7f83: {Name:mk696a9938beae2f47fa52aa0f4e064bccb90f02 Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0731 20:49:24.951031 180868 certs.go:381] copying /home/jenkins/minikube-integration/19355-121704/.minikube/profiles/old-k8s-version-239115/apiserver.crt.072d7f83 -> /home/jenkins/minikube-integration/19355-121704/.minikube/profiles/old-k8s-version-239115/apiserver.crt
I0731 20:49:24.951099 180868 certs.go:385] copying /home/jenkins/minikube-integration/19355-121704/.minikube/profiles/old-k8s-version-239115/apiserver.key.072d7f83 -> /home/jenkins/minikube-integration/19355-121704/.minikube/profiles/old-k8s-version-239115/apiserver.key
I0731 20:49:24.951154 180868 certs.go:363] generating signed profile cert for "aggregator": /home/jenkins/minikube-integration/19355-121704/.minikube/profiles/old-k8s-version-239115/proxy-client.key
I0731 20:49:24.951169 180868 crypto.go:68] Generating cert /home/jenkins/minikube-integration/19355-121704/.minikube/profiles/old-k8s-version-239115/proxy-client.crt with IP's: []
I0731 20:49:25.113577 180868 crypto.go:156] Writing cert to /home/jenkins/minikube-integration/19355-121704/.minikube/profiles/old-k8s-version-239115/proxy-client.crt ...
I0731 20:49:25.113605 180868 lock.go:35] WriteFile acquiring /home/jenkins/minikube-integration/19355-121704/.minikube/profiles/old-k8s-version-239115/proxy-client.crt: {Name:mk26293cb994c024f9dced96ccd471e68c5b5853 Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0731 20:49:25.113789 180868 crypto.go:164] Writing key to /home/jenkins/minikube-integration/19355-121704/.minikube/profiles/old-k8s-version-239115/proxy-client.key ...
I0731 20:49:25.113807 180868 lock.go:35] WriteFile acquiring /home/jenkins/minikube-integration/19355-121704/.minikube/profiles/old-k8s-version-239115/proxy-client.key: {Name:mk7e1f36ba276800d6a1fe2a0c02ec2a4840a84e Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0731 20:49:25.114041 180868 certs.go:484] found cert: /home/jenkins/minikube-integration/19355-121704/.minikube/certs/128891.pem (1338 bytes)
W0731 20:49:25.114084 180868 certs.go:480] ignoring /home/jenkins/minikube-integration/19355-121704/.minikube/certs/128891_empty.pem, impossibly tiny 0 bytes
I0731 20:49:25.114095 180868 certs.go:484] found cert: /home/jenkins/minikube-integration/19355-121704/.minikube/certs/ca-key.pem (1679 bytes)
I0731 20:49:25.114117 180868 certs.go:484] found cert: /home/jenkins/minikube-integration/19355-121704/.minikube/certs/ca.pem (1082 bytes)
I0731 20:49:25.114139 180868 certs.go:484] found cert: /home/jenkins/minikube-integration/19355-121704/.minikube/certs/cert.pem (1123 bytes)
I0731 20:49:25.114160 180868 certs.go:484] found cert: /home/jenkins/minikube-integration/19355-121704/.minikube/certs/key.pem (1675 bytes)
I0731 20:49:25.114197 180868 certs.go:484] found cert: /home/jenkins/minikube-integration/19355-121704/.minikube/files/etc/ssl/certs/1288912.pem (1708 bytes)
I0731 20:49:25.114744 180868 ssh_runner.go:362] scp /home/jenkins/minikube-integration/19355-121704/.minikube/ca.crt --> /var/lib/minikube/certs/ca.crt (1111 bytes)
I0731 20:49:25.153524 180868 ssh_runner.go:362] scp /home/jenkins/minikube-integration/19355-121704/.minikube/ca.key --> /var/lib/minikube/certs/ca.key (1679 bytes)
I0731 20:49:25.183001 180868 ssh_runner.go:362] scp /home/jenkins/minikube-integration/19355-121704/.minikube/proxy-client-ca.crt --> /var/lib/minikube/certs/proxy-client-ca.crt (1119 bytes)
I0731 20:49:25.214008 180868 ssh_runner.go:362] scp /home/jenkins/minikube-integration/19355-121704/.minikube/proxy-client-ca.key --> /var/lib/minikube/certs/proxy-client-ca.key (1679 bytes)
I0731 20:49:25.246071 180868 ssh_runner.go:362] scp /home/jenkins/minikube-integration/19355-121704/.minikube/profiles/old-k8s-version-239115/apiserver.crt --> /var/lib/minikube/certs/apiserver.crt (1432 bytes)
I0731 20:49:25.275789 180868 ssh_runner.go:362] scp /home/jenkins/minikube-integration/19355-121704/.minikube/profiles/old-k8s-version-239115/apiserver.key --> /var/lib/minikube/certs/apiserver.key (1679 bytes)
I0731 20:49:25.306971 180868 ssh_runner.go:362] scp /home/jenkins/minikube-integration/19355-121704/.minikube/profiles/old-k8s-version-239115/proxy-client.crt --> /var/lib/minikube/certs/proxy-client.crt (1147 bytes)
I0731 20:49:25.345543 180868 ssh_runner.go:362] scp /home/jenkins/minikube-integration/19355-121704/.minikube/profiles/old-k8s-version-239115/proxy-client.key --> /var/lib/minikube/certs/proxy-client.key (1679 bytes)
I0731 20:49:25.371632 180868 ssh_runner.go:362] scp /home/jenkins/minikube-integration/19355-121704/.minikube/files/etc/ssl/certs/1288912.pem --> /usr/share/ca-certificates/1288912.pem (1708 bytes)
I0731 20:49:25.399333 180868 ssh_runner.go:362] scp /home/jenkins/minikube-integration/19355-121704/.minikube/ca.crt --> /usr/share/ca-certificates/minikubeCA.pem (1111 bytes)
I0731 20:49:25.430873 180868 ssh_runner.go:362] scp /home/jenkins/minikube-integration/19355-121704/.minikube/certs/128891.pem --> /usr/share/ca-certificates/128891.pem (1338 bytes)
I0731 20:49:25.457316 180868 ssh_runner.go:362] scp memory --> /var/lib/minikube/kubeconfig (738 bytes)
I0731 20:49:25.477205 180868 ssh_runner.go:195] Run: openssl version
I0731 20:49:25.485518 180868 ssh_runner.go:195] Run: sudo /bin/bash -c "test -s /usr/share/ca-certificates/1288912.pem && ln -fs /usr/share/ca-certificates/1288912.pem /etc/ssl/certs/1288912.pem"
I0731 20:49:25.500541 180868 ssh_runner.go:195] Run: ls -la /usr/share/ca-certificates/1288912.pem
I0731 20:49:25.506466 180868 certs.go:528] hashing: -rw-r--r-- 1 root root 1708 Jul 31 19:42 /usr/share/ca-certificates/1288912.pem
I0731 20:49:25.506535 180868 ssh_runner.go:195] Run: openssl x509 -hash -noout -in /usr/share/ca-certificates/1288912.pem
I0731 20:49:25.514922 180868 ssh_runner.go:195] Run: sudo /bin/bash -c "test -L /etc/ssl/certs/3ec20f2e.0 || ln -fs /etc/ssl/certs/1288912.pem /etc/ssl/certs/3ec20f2e.0"
I0731 20:49:25.533045 180868 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"
I0731 20:49:25.545612 180868 ssh_runner.go:195] Run: ls -la /usr/share/ca-certificates/minikubeCA.pem
I0731 20:49:25.552926 180868 certs.go:528] hashing: -rw-r--r-- 1 root root 1111 Jul 31 19:29 /usr/share/ca-certificates/minikubeCA.pem
I0731 20:49:25.553075 180868 ssh_runner.go:195] Run: openssl x509 -hash -noout -in /usr/share/ca-certificates/minikubeCA.pem
I0731 20:49:25.559850 180868 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"
I0731 20:49:25.573668 180868 ssh_runner.go:195] Run: sudo /bin/bash -c "test -s /usr/share/ca-certificates/128891.pem && ln -fs /usr/share/ca-certificates/128891.pem /etc/ssl/certs/128891.pem"
I0731 20:49:25.588905 180868 ssh_runner.go:195] Run: ls -la /usr/share/ca-certificates/128891.pem
I0731 20:49:25.595050 180868 certs.go:528] hashing: -rw-r--r-- 1 root root 1338 Jul 31 19:42 /usr/share/ca-certificates/128891.pem
I0731 20:49:25.595122 180868 ssh_runner.go:195] Run: openssl x509 -hash -noout -in /usr/share/ca-certificates/128891.pem
I0731 20:49:25.601308 180868 ssh_runner.go:195] Run: sudo /bin/bash -c "test -L /etc/ssl/certs/51391683.0 || ln -fs /etc/ssl/certs/128891.pem /etc/ssl/certs/51391683.0"
I0731 20:49:25.615905 180868 ssh_runner.go:195] Run: stat /var/lib/minikube/certs/apiserver-kubelet-client.crt
I0731 20:49:25.621440 180868 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
I0731 20:49:25.621501 180868 kubeadm.go:392] StartCluster: {Name:old-k8s-version-239115 KeepContext:false EmbedCerts:false MinikubeISO:https://storage.googleapis.com/minikube-builds/iso/19355/minikube-v1.33.1-1722420371-19355-amd64.iso KicBaseImage:gcr.io/k8s-minikube/kicbase-builds:v0.0.44-1721902582-19326@sha256:540fb5dc7f38be17ff5276a38dfe6c8a4b1d9ba1c27c62244e6eebd7e37696e7 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:v
1.20.0 ClusterName:old-k8s-version-239115 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.61.51 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:[] Mount
Port:0 MountType:9p MountUID:docker BinaryMirror: DisableOptimizations:false DisableMetrics:false CustomQemuFirmwarePath: SocketVMnetClientPath: SocketVMnetPath: StaticIP: SSHAuthSock: SSHAgentPID:0 GPUs: AutoPauseInterval:1m0s}
I0731 20:49:25.621598 180868 cri.go:54] listing CRI containers in root : {State:paused Name: Namespaces:[kube-system]}
I0731 20:49:25.621661 180868 ssh_runner.go:195] Run: sudo -s eval "crictl ps -a --quiet --label io.kubernetes.pod.namespace=kube-system"
I0731 20:49:25.666334 180868 cri.go:89] found id: ""
I0731 20:49:25.666405 180868 ssh_runner.go:195] Run: sudo ls /var/lib/kubelet/kubeadm-flags.env /var/lib/kubelet/config.yaml /var/lib/minikube/etcd
I0731 20:49:25.676565 180868 ssh_runner.go:195] Run: sudo cp /var/tmp/minikube/kubeadm.yaml.new /var/tmp/minikube/kubeadm.yaml
I0731 20:49:25.686598 180868 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
I0731 20:49:25.696479 180868 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
I0731 20:49:25.696504 180868 kubeadm.go:157] found existing configuration files:
I0731 20:49:25.696562 180868 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/admin.conf
I0731 20:49:25.705862 180868 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
I0731 20:49:25.705921 180868 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/admin.conf
I0731 20:49:25.716071 180868 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/kubelet.conf
I0731 20:49:25.727150 180868 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
I0731 20:49:25.727222 180868 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/kubelet.conf
I0731 20:49:25.740558 180868 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/controller-manager.conf
I0731 20:49:25.751029 180868 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
I0731 20:49:25.751095 180868 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/controller-manager.conf
I0731 20:49:25.760898 180868 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/scheduler.conf
I0731 20:49:25.770187 180868 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
I0731 20:49:25.770280 180868 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/scheduler.conf
I0731 20:49:25.780324 180868 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"
I0731 20:49:25.908332 180868 kubeadm.go:310] [init] Using Kubernetes version: v1.20.0
I0731 20:49:25.908389 180868 kubeadm.go:310] [preflight] Running pre-flight checks
I0731 20:49:26.121653 180868 kubeadm.go:310] [preflight] Pulling images required for setting up a Kubernetes cluster
I0731 20:49:26.121798 180868 kubeadm.go:310] [preflight] This might take a minute or two, depending on the speed of your internet connection
I0731 20:49:26.121920 180868 kubeadm.go:310] [preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
I0731 20:49:26.406879 180868 kubeadm.go:310] [certs] Using certificateDir folder "/var/lib/minikube/certs"
I0731 20:49:26.409794 180868 out.go:204] - Generating certificates and keys ...
I0731 20:49:26.409870 180868 kubeadm.go:310] [certs] Using existing ca certificate authority
I0731 20:49:26.409925 180868 kubeadm.go:310] [certs] Using existing apiserver certificate and key on disk
I0731 20:49:26.534002 180868 kubeadm.go:310] [certs] Generating "apiserver-kubelet-client" certificate and key
I0731 20:49:26.656899 180868 kubeadm.go:310] [certs] Generating "front-proxy-ca" certificate and key
I0731 20:49:27.321362 180868 kubeadm.go:310] [certs] Generating "front-proxy-client" certificate and key
I0731 20:49:27.902952 180868 kubeadm.go:310] [certs] Generating "etcd/ca" certificate and key
I0731 20:49:28.166936 180868 kubeadm.go:310] [certs] Generating "etcd/server" certificate and key
I0731 20:49:28.167115 180868 kubeadm.go:310] [certs] etcd/server serving cert is signed for DNS names [localhost old-k8s-version-239115] and IPs [192.168.61.51 127.0.0.1 ::1]
I0731 20:49:28.665588 180868 kubeadm.go:310] [certs] Generating "etcd/peer" certificate and key
I0731 20:49:28.665877 180868 kubeadm.go:310] [certs] etcd/peer serving cert is signed for DNS names [localhost old-k8s-version-239115] and IPs [192.168.61.51 127.0.0.1 ::1]
I0731 20:49:28.752233 180868 kubeadm.go:310] [certs] Generating "etcd/healthcheck-client" certificate and key
I0731 20:49:28.807285 180868 kubeadm.go:310] [certs] Generating "apiserver-etcd-client" certificate and key
I0731 20:49:29.256440 180868 kubeadm.go:310] [certs] Generating "sa" key and public key
I0731 20:49:29.256893 180868 kubeadm.go:310] [kubeconfig] Using kubeconfig folder "/etc/kubernetes"
I0731 20:49:29.384639 180868 kubeadm.go:310] [kubeconfig] Writing "admin.conf" kubeconfig file
I0731 20:49:29.483424 180868 kubeadm.go:310] [kubeconfig] Writing "kubelet.conf" kubeconfig file
I0731 20:49:29.838468 180868 kubeadm.go:310] [kubeconfig] Writing "controller-manager.conf" kubeconfig file
I0731 20:49:30.155030 180868 kubeadm.go:310] [kubeconfig] Writing "scheduler.conf" kubeconfig file
I0731 20:49:30.177979 180868 kubeadm.go:310] [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
I0731 20:49:30.178879 180868 kubeadm.go:310] [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
I0731 20:49:30.179112 180868 kubeadm.go:310] [kubelet-start] Starting the kubelet
I0731 20:49:30.363130 180868 kubeadm.go:310] [control-plane] Using manifest folder "/etc/kubernetes/manifests"
I0731 20:49:30.365106 180868 out.go:204] - Booting up control plane ...
I0731 20:49:30.365224 180868 kubeadm.go:310] [control-plane] Creating static Pod manifest for "kube-apiserver"
I0731 20:49:30.376451 180868 kubeadm.go:310] [control-plane] Creating static Pod manifest for "kube-controller-manager"
I0731 20:49:30.381712 180868 kubeadm.go:310] [control-plane] Creating static Pod manifest for "kube-scheduler"
I0731 20:49:30.381822 180868 kubeadm.go:310] [etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
I0731 20:49:30.392486 180868 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
I0731 20:50:10.389392 180868 kubeadm.go:310] [kubelet-check] Initial timeout of 40s passed.
I0731 20:50:10.390281 180868 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0731 20:50:10.390544 180868 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.
I0731 20:50:15.390236 180868 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0731 20:50:15.390461 180868 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.
I0731 20:50:25.390205 180868 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0731 20:50:25.390456 180868 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.
I0731 20:50:45.389885 180868 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0731 20:50:45.390119 180868 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.
I0731 20:51:25.392273 180868 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0731 20:51:25.392835 180868 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.
I0731 20:51:25.392857 180868 kubeadm.go:310]
I0731 20:51:25.392953 180868 kubeadm.go:310] Unfortunately, an error has occurred:
I0731 20:51:25.393045 180868 kubeadm.go:310] timed out waiting for the condition
I0731 20:51:25.393053 180868 kubeadm.go:310]
I0731 20:51:25.393117 180868 kubeadm.go:310] This error is likely caused by:
I0731 20:51:25.393195 180868 kubeadm.go:310] - The kubelet is not running
I0731 20:51:25.393519 180868 kubeadm.go:310] - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
I0731 20:51:25.393554 180868 kubeadm.go:310]
I0731 20:51:25.393778 180868 kubeadm.go:310] If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
I0731 20:51:25.393856 180868 kubeadm.go:310] - 'systemctl status kubelet'
I0731 20:51:25.393929 180868 kubeadm.go:310] - 'journalctl -xeu kubelet'
I0731 20:51:25.393939 180868 kubeadm.go:310]
I0731 20:51:25.394181 180868 kubeadm.go:310] Additionally, a control plane component may have crashed or exited when started by the container runtime.
I0731 20:51:25.394367 180868 kubeadm.go:310] To troubleshoot, list all containers using your preferred container runtimes CLI.
I0731 20:51:25.394374 180868 kubeadm.go:310]
I0731 20:51:25.394607 180868 kubeadm.go:310] Here is one example how you may list all Kubernetes containers running in cri-o/containerd using crictl:
I0731 20:51:25.394795 180868 kubeadm.go:310] - 'crictl --runtime-endpoint /var/run/crio/crio.sock ps -a | grep kube | grep -v pause'
I0731 20:51:25.395832 180868 kubeadm.go:310] Once you have found the failing container, you can inspect its logs with:
I0731 20:51:25.396176 180868 kubeadm.go:310] - 'crictl --runtime-endpoint /var/run/crio/crio.sock logs CONTAINERID'
I0731 20:51:25.396211 180868 kubeadm.go:310]
I0731 20:51:25.396366 180868 kubeadm.go:310] [WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
I0731 20:51:25.396472 180868 kubeadm.go:310] error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
W0731 20:51:25.396663 180868 out.go:239] ! 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-239115] and IPs [192.168.61.51 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-239115] and IPs [192.168.61.51 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-239115] and IPs [192.168.61.51 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-239115] and IPs [192.168.61.51 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
I0731 20:51:25.396718 180868 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"
I0731 20:51:25.396670 180868 kubeadm.go:310] To see the stack trace of this error execute with --v=5 or higher
I0731 20:51:26.515397 180868 ssh_runner.go:235] Completed: /bin/bash -c "sudo env PATH="/var/lib/minikube/binaries/v1.20.0:$PATH" kubeadm reset --cri-socket /var/run/crio/crio.sock --force": (1.118652718s)
I0731 20:51:26.515470 180868 ssh_runner.go:195] Run: sudo systemctl is-active --quiet service kubelet
I0731 20:51:26.530145 180868 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
I0731 20:51:26.539834 180868 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
I0731 20:51:26.539860 180868 kubeadm.go:157] found existing configuration files:
I0731 20:51:26.539903 180868 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/admin.conf
I0731 20:51:26.549303 180868 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
I0731 20:51:26.549377 180868 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/admin.conf
I0731 20:51:26.558372 180868 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/kubelet.conf
I0731 20:51:26.567508 180868 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
I0731 20:51:26.567568 180868 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/kubelet.conf
I0731 20:51:26.576363 180868 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/controller-manager.conf
I0731 20:51:26.585043 180868 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
I0731 20:51:26.585096 180868 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/controller-manager.conf
I0731 20:51:26.594455 180868 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/scheduler.conf
I0731 20:51:26.603558 180868 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
I0731 20:51:26.603611 180868 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/scheduler.conf
I0731 20:51:26.612533 180868 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"
I0731 20:51:26.687344 180868 kubeadm.go:310] [init] Using Kubernetes version: v1.20.0
I0731 20:51:26.687438 180868 kubeadm.go:310] [preflight] Running pre-flight checks
I0731 20:51:26.833243 180868 kubeadm.go:310] [preflight] Pulling images required for setting up a Kubernetes cluster
I0731 20:51:26.833441 180868 kubeadm.go:310] [preflight] This might take a minute or two, depending on the speed of your internet connection
I0731 20:51:26.833557 180868 kubeadm.go:310] [preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
I0731 20:51:27.027290 180868 kubeadm.go:310] [certs] Using certificateDir folder "/var/lib/minikube/certs"
I0731 20:51:27.029260 180868 out.go:204] - Generating certificates and keys ...
I0731 20:51:27.029400 180868 kubeadm.go:310] [certs] Using existing ca certificate authority
I0731 20:51:27.029485 180868 kubeadm.go:310] [certs] Using existing apiserver certificate and key on disk
I0731 20:51:27.029589 180868 kubeadm.go:310] [certs] Using existing apiserver-kubelet-client certificate and key on disk
I0731 20:51:27.029696 180868 kubeadm.go:310] [certs] Using existing front-proxy-ca certificate authority
I0731 20:51:27.029809 180868 kubeadm.go:310] [certs] Using existing front-proxy-client certificate and key on disk
I0731 20:51:27.029886 180868 kubeadm.go:310] [certs] Using existing etcd/ca certificate authority
I0731 20:51:27.029973 180868 kubeadm.go:310] [certs] Using existing etcd/server certificate and key on disk
I0731 20:51:27.030625 180868 kubeadm.go:310] [certs] Using existing etcd/peer certificate and key on disk
I0731 20:51:27.031592 180868 kubeadm.go:310] [certs] Using existing etcd/healthcheck-client certificate and key on disk
I0731 20:51:27.032608 180868 kubeadm.go:310] [certs] Using existing apiserver-etcd-client certificate and key on disk
I0731 20:51:27.032951 180868 kubeadm.go:310] [certs] Using the existing "sa" key
I0731 20:51:27.033041 180868 kubeadm.go:310] [kubeconfig] Using kubeconfig folder "/etc/kubernetes"
I0731 20:51:27.385389 180868 kubeadm.go:310] [kubeconfig] Writing "admin.conf" kubeconfig file
I0731 20:51:27.734973 180868 kubeadm.go:310] [kubeconfig] Writing "kubelet.conf" kubeconfig file
I0731 20:51:27.872101 180868 kubeadm.go:310] [kubeconfig] Writing "controller-manager.conf" kubeconfig file
I0731 20:51:27.932272 180868 kubeadm.go:310] [kubeconfig] Writing "scheduler.conf" kubeconfig file
I0731 20:51:27.949087 180868 kubeadm.go:310] [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
I0731 20:51:27.951595 180868 kubeadm.go:310] [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
I0731 20:51:27.951650 180868 kubeadm.go:310] [kubelet-start] Starting the kubelet
I0731 20:51:28.098197 180868 kubeadm.go:310] [control-plane] Using manifest folder "/etc/kubernetes/manifests"
I0731 20:51:28.100353 180868 out.go:204] - Booting up control plane ...
I0731 20:51:28.100539 180868 kubeadm.go:310] [control-plane] Creating static Pod manifest for "kube-apiserver"
I0731 20:51:28.113571 180868 kubeadm.go:310] [control-plane] Creating static Pod manifest for "kube-controller-manager"
I0731 20:51:28.115075 180868 kubeadm.go:310] [control-plane] Creating static Pod manifest for "kube-scheduler"
I0731 20:51:28.117209 180868 kubeadm.go:310] [etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
I0731 20:51:28.120336 180868 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
I0731 20:52:08.123316 180868 kubeadm.go:310] [kubelet-check] Initial timeout of 40s passed.
I0731 20:52:08.123567 180868 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0731 20:52:08.123838 180868 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.
I0731 20:52:13.124560 180868 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0731 20:52:13.124789 180868 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.
I0731 20:52:23.124668 180868 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0731 20:52:23.124866 180868 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.
I0731 20:52:43.123825 180868 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0731 20:52:43.124041 180868 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.
I0731 20:53:23.123561 180868 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0731 20:53:23.123782 180868 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.
I0731 20:53:23.123813 180868 kubeadm.go:310]
I0731 20:53:23.123915 180868 kubeadm.go:310] Unfortunately, an error has occurred:
I0731 20:53:23.123977 180868 kubeadm.go:310] timed out waiting for the condition
I0731 20:53:23.123989 180868 kubeadm.go:310]
I0731 20:53:23.124032 180868 kubeadm.go:310] This error is likely caused by:
I0731 20:53:23.124083 180868 kubeadm.go:310] - The kubelet is not running
I0731 20:53:23.124214 180868 kubeadm.go:310] - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
I0731 20:53:23.124224 180868 kubeadm.go:310]
I0731 20:53:23.124347 180868 kubeadm.go:310] If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
I0731 20:53:23.124396 180868 kubeadm.go:310] - 'systemctl status kubelet'
I0731 20:53:23.124434 180868 kubeadm.go:310] - 'journalctl -xeu kubelet'
I0731 20:53:23.124448 180868 kubeadm.go:310]
I0731 20:53:23.124591 180868 kubeadm.go:310] Additionally, a control plane component may have crashed or exited when started by the container runtime.
I0731 20:53:23.124712 180868 kubeadm.go:310] To troubleshoot, list all containers using your preferred container runtimes CLI.
I0731 20:53:23.124725 180868 kubeadm.go:310]
I0731 20:53:23.124878 180868 kubeadm.go:310] Here is one example how you may list all Kubernetes containers running in cri-o/containerd using crictl:
I0731 20:53:23.124989 180868 kubeadm.go:310] - 'crictl --runtime-endpoint /var/run/crio/crio.sock ps -a | grep kube | grep -v pause'
I0731 20:53:23.125099 180868 kubeadm.go:310] Once you have found the failing container, you can inspect its logs with:
I0731 20:53:23.125197 180868 kubeadm.go:310] - 'crictl --runtime-endpoint /var/run/crio/crio.sock logs CONTAINERID'
I0731 20:53:23.125210 180868 kubeadm.go:310]
I0731 20:53:23.125936 180868 kubeadm.go:310] [WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
I0731 20:53:23.126053 180868 kubeadm.go:310] error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
I0731 20:53:23.126156 180868 kubeadm.go:310] To see the stack trace of this error execute with --v=5 or higher
I0731 20:53:23.126231 180868 kubeadm.go:394] duration metric: took 3m57.5047371s to StartCluster
I0731 20:53:23.126276 180868 cri.go:54] listing CRI containers in root : {State:all Name:kube-apiserver Namespaces:[]}
I0731 20:53:23.126325 180868 ssh_runner.go:195] Run: sudo crictl ps -a --quiet --name=kube-apiserver
I0731 20:53:23.169161 180868 cri.go:89] found id: ""
I0731 20:53:23.169194 180868 logs.go:276] 0 containers: []
W0731 20:53:23.169209 180868 logs.go:278] No container was found matching "kube-apiserver"
I0731 20:53:23.169218 180868 cri.go:54] listing CRI containers in root : {State:all Name:etcd Namespaces:[]}
I0731 20:53:23.169281 180868 ssh_runner.go:195] Run: sudo crictl ps -a --quiet --name=etcd
I0731 20:53:23.203823 180868 cri.go:89] found id: ""
I0731 20:53:23.203853 180868 logs.go:276] 0 containers: []
W0731 20:53:23.203860 180868 logs.go:278] No container was found matching "etcd"
I0731 20:53:23.203866 180868 cri.go:54] listing CRI containers in root : {State:all Name:coredns Namespaces:[]}
I0731 20:53:23.203917 180868 ssh_runner.go:195] Run: sudo crictl ps -a --quiet --name=coredns
I0731 20:53:23.237868 180868 cri.go:89] found id: ""
I0731 20:53:23.237900 180868 logs.go:276] 0 containers: []
W0731 20:53:23.237910 180868 logs.go:278] No container was found matching "coredns"
I0731 20:53:23.237919 180868 cri.go:54] listing CRI containers in root : {State:all Name:kube-scheduler Namespaces:[]}
I0731 20:53:23.237987 180868 ssh_runner.go:195] Run: sudo crictl ps -a --quiet --name=kube-scheduler
I0731 20:53:23.271146 180868 cri.go:89] found id: ""
I0731 20:53:23.271180 180868 logs.go:276] 0 containers: []
W0731 20:53:23.271192 180868 logs.go:278] No container was found matching "kube-scheduler"
I0731 20:53:23.271200 180868 cri.go:54] listing CRI containers in root : {State:all Name:kube-proxy Namespaces:[]}
I0731 20:53:23.271266 180868 ssh_runner.go:195] Run: sudo crictl ps -a --quiet --name=kube-proxy
I0731 20:53:23.308232 180868 cri.go:89] found id: ""
I0731 20:53:23.308265 180868 logs.go:276] 0 containers: []
W0731 20:53:23.308277 180868 logs.go:278] No container was found matching "kube-proxy"
I0731 20:53:23.308285 180868 cri.go:54] listing CRI containers in root : {State:all Name:kube-controller-manager Namespaces:[]}
I0731 20:53:23.308343 180868 ssh_runner.go:195] Run: sudo crictl ps -a --quiet --name=kube-controller-manager
I0731 20:53:23.342021 180868 cri.go:89] found id: ""
I0731 20:53:23.342055 180868 logs.go:276] 0 containers: []
W0731 20:53:23.342066 180868 logs.go:278] No container was found matching "kube-controller-manager"
I0731 20:53:23.342074 180868 cri.go:54] listing CRI containers in root : {State:all Name:kindnet Namespaces:[]}
I0731 20:53:23.342140 180868 ssh_runner.go:195] Run: sudo crictl ps -a --quiet --name=kindnet
I0731 20:53:23.376147 180868 cri.go:89] found id: ""
I0731 20:53:23.376179 180868 logs.go:276] 0 containers: []
W0731 20:53:23.376186 180868 logs.go:278] No container was found matching "kindnet"
I0731 20:53:23.376197 180868 logs.go:123] Gathering logs for kubelet ...
I0731 20:53:23.376210 180868 ssh_runner.go:195] Run: /bin/bash -c "sudo journalctl -u kubelet -n 400"
I0731 20:53:23.426993 180868 logs.go:123] Gathering logs for dmesg ...
I0731 20:53:23.427027 180868 ssh_runner.go:195] Run: /bin/bash -c "sudo dmesg -PH -L=never --level warn,err,crit,alert,emerg | tail -n 400"
I0731 20:53:23.441193 180868 logs.go:123] Gathering logs for describe nodes ...
I0731 20:53:23.441223 180868 ssh_runner.go:195] Run: /bin/bash -c "sudo /var/lib/minikube/binaries/v1.20.0/kubectl describe nodes --kubeconfig=/var/lib/minikube/kubeconfig"
W0731 20:53:23.547960 180868 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 **
I0731 20:53:23.547985 180868 logs.go:123] Gathering logs for CRI-O ...
I0731 20:53:23.548001 180868 ssh_runner.go:195] Run: /bin/bash -c "sudo journalctl -u crio -n 400"
I0731 20:53:23.645069 180868 logs.go:123] Gathering logs for container status ...
I0731 20:53:23.645107 180868 ssh_runner.go:195] Run: /bin/bash -c "sudo `which crictl || echo crictl` ps -a || sudo docker ps -a"
W0731 20:53:23.690657 180868 out.go:364] 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
W0731 20:53:23.690704 180868 out.go:239] *
*
W0731 20:53:23.690773 180868 out.go:239] 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
W0731 20:53:23.690793 180868 out.go:239] *
*
W0731 20:53:23.691555 180868 out.go:239] ╭─────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ * 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. │
│ │
╰─────────────────────────────────────────────────────────────────────────────────────────────╯
I0731 20:53:23.694711 180868 out.go:177]
W0731 20:53:23.696265 180868 out.go:239] 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
W0731 20:53:23.696325 180868 out.go:239] * 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
W0731 20:53:23.696348 180868 out.go:239] * Related issue: https://github.com/kubernetes/minikube/issues/4172
* Related issue: https://github.com/kubernetes/minikube/issues/4172
I0731 20:53:23.698023 180868 out.go:177]
** /stderr **
start_stop_delete_test.go:188: failed starting minikube -first start-. args "out/minikube-linux-amd64 start -p old-k8s-version-239115 --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-239115 -n old-k8s-version-239115
helpers_test.go:239: (dbg) Non-zero exit: out/minikube-linux-amd64 status --format={{.Host}} -p old-k8s-version-239115 -n old-k8s-version-239115: exit status 6 (217.395629ms)
-- stdout --
Running
WARNING: Your kubectl is pointing to stale minikube-vm.
To fix the kubectl context, run `minikube update-context`
-- /stdout --
** stderr **
E0731 20:53:23.956949 187576 status.go:417] kubeconfig endpoint: get endpoint: "old-k8s-version-239115" does not appear in /home/jenkins/minikube-integration/19355-121704/kubeconfig
** /stderr **
helpers_test.go:239: status error: exit status 6 (may be ok)
helpers_test.go:241: "old-k8s-version-239115" 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 (320.83s)