=== RUN TestStartStop/group/old-k8s-version/serial/FirstStart
start_stop_delete_test.go:184: (dbg) Run: out/minikube-linux-amd64 start -p old-k8s-version-257500 --memory=2200 --alsologtostderr --wait=true --kvm-network=default --kvm-qemu-uri=qemu:///system --disable-driver-mounts --keep-context=false --driver=kvm2 --container-runtime=crio --kubernetes-version=v1.20.0
start_stop_delete_test.go:184: (dbg) Non-zero exit: out/minikube-linux-amd64 start -p old-k8s-version-257500 --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 (4m35.11205923s)
-- stdout --
* [old-k8s-version-257500] minikube v1.35.0 on Ubuntu 20.04 (kvm/amd64)
- MINIKUBE_LOCATION=20604
- MINIKUBE_SUPPRESS_DOCKER_PERFORMANCE=true
- KUBECONFIG=/home/jenkins/minikube-integration/20604-141129/kubeconfig
- MINIKUBE_HOME=/home/jenkins/minikube-integration/20604-141129/.minikube
- MINIKUBE_BIN=out/minikube-linux-amd64
- MINIKUBE_FORCE_SYSTEMD=
* Using the kvm2 driver based on user configuration
* Starting "old-k8s-version-257500" primary control-plane node in "old-k8s-version-257500" 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 **
I0408 19:22:54.486979 198268 out.go:345] Setting OutFile to fd 1 ...
I0408 19:22:54.487144 198268 out.go:392] TERM=,COLORTERM=, which probably does not support color
I0408 19:22:54.487157 198268 out.go:358] Setting ErrFile to fd 2...
I0408 19:22:54.487163 198268 out.go:392] TERM=,COLORTERM=, which probably does not support color
I0408 19:22:54.487361 198268 root.go:338] Updating PATH: /home/jenkins/minikube-integration/20604-141129/.minikube/bin
I0408 19:22:54.487996 198268 out.go:352] Setting JSON to false
I0408 19:22:54.489149 198268 start.go:129] hostinfo: {"hostname":"ubuntu-20-agent-2","uptime":11120,"bootTime":1744129055,"procs":294,"os":"linux","platform":"ubuntu","platformFamily":"debian","platformVersion":"20.04","kernelVersion":"5.15.0-1078-gcp","kernelArch":"x86_64","virtualizationSystem":"kvm","virtualizationRole":"guest","hostId":"591c9f12-2938-3743-e2bf-c56a050d43d1"}
I0408 19:22:54.489278 198268 start.go:139] virtualization: kvm guest
I0408 19:22:54.491403 198268 out.go:177] * [old-k8s-version-257500] minikube v1.35.0 on Ubuntu 20.04 (kvm/amd64)
I0408 19:22:54.492765 198268 out.go:177] - MINIKUBE_LOCATION=20604
I0408 19:22:54.492803 198268 notify.go:220] Checking for updates...
I0408 19:22:54.495399 198268 out.go:177] - MINIKUBE_SUPPRESS_DOCKER_PERFORMANCE=true
I0408 19:22:54.496860 198268 out.go:177] - KUBECONFIG=/home/jenkins/minikube-integration/20604-141129/kubeconfig
I0408 19:22:54.498552 198268 out.go:177] - MINIKUBE_HOME=/home/jenkins/minikube-integration/20604-141129/.minikube
I0408 19:22:54.500016 198268 out.go:177] - MINIKUBE_BIN=out/minikube-linux-amd64
I0408 19:22:54.501379 198268 out.go:177] - MINIKUBE_FORCE_SYSTEMD=
I0408 19:22:54.503015 198268 config.go:182] Loaded profile config "bridge-880875": Driver=kvm2, ContainerRuntime=crio, KubernetesVersion=v1.32.2
I0408 19:22:54.503127 198268 config.go:182] Loaded profile config "enable-default-cni-880875": Driver=kvm2, ContainerRuntime=crio, KubernetesVersion=v1.32.2
I0408 19:22:54.503229 198268 config.go:182] Loaded profile config "flannel-880875": Driver=kvm2, ContainerRuntime=crio, KubernetesVersion=v1.32.2
I0408 19:22:54.503356 198268 driver.go:394] Setting default libvirt URI to qemu:///system
I0408 19:22:54.543540 198268 out.go:177] * Using the kvm2 driver based on user configuration
I0408 19:22:54.544948 198268 start.go:297] selected driver: kvm2
I0408 19:22:54.544969 198268 start.go:901] validating driver "kvm2" against <nil>
I0408 19:22:54.544982 198268 start.go:912] status for kvm2: {Installed:true Healthy:true Running:true NeedsImprovement:false Error:<nil> Reason: Fix: Doc: Version:}
I0408 19:22:54.546021 198268 install.go:52] acquiring lock: {Name:mk900956b073697a4aa6c80a27c6bb0742a99a53 Clock:{} Delay:500ms Timeout:10m0s Cancel:<nil>}
I0408 19:22:54.546123 198268 install.go:117] Validating docker-machine-driver-kvm2, PATH=/home/jenkins/minikube-integration/20604-141129/.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
I0408 19:22:54.564477 198268 install.go:137] /home/jenkins/workspace/KVM_Linux_crio_integration/out/docker-machine-driver-kvm2 version is 1.35.0
I0408 19:22:54.564549 198268 start_flags.go:310] no existing cluster config was found, will generate one from the flags
I0408 19:22:54.564800 198268 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]
I0408 19:22:54.564833 198268 cni.go:84] Creating CNI manager for ""
I0408 19:22:54.564862 198268 cni.go:146] "kvm2" driver + "crio" runtime found, recommending bridge
I0408 19:22:54.564870 198268 start_flags.go:319] Found "bridge CNI" CNI - setting NetworkPlugin=cni
I0408 19:22:54.564932 198268 start.go:340] cluster config:
{Name:old-k8s-version-257500 KeepContext:false EmbedCerts:false MinikubeISO: KicBaseImage:gcr.io/k8s-minikube/kicbase-builds:v0.0.46-1744107393-20604@sha256:2430533582a8c08f907b2d5976c79bd2e672b4f3d4484088c99b839f3175ed6a 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-257500 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}
I0408 19:22:54.565056 198268 iso.go:125] acquiring lock: {Name:mk6f89956dcd0ccd06b3c273592988c0e077c69a Clock:{} Delay:500ms Timeout:10m0s Cancel:<nil>}
I0408 19:22:54.567977 198268 out.go:177] * Starting "old-k8s-version-257500" primary control-plane node in "old-k8s-version-257500" cluster
I0408 19:22:54.569593 198268 preload.go:131] Checking if preload exists for k8s version v1.20.0 and runtime crio
I0408 19:22:54.569675 198268 preload.go:146] Found local preload: /home/jenkins/minikube-integration/20604-141129/.minikube/cache/preloaded-tarball/preloaded-images-k8s-v18-v1.20.0-cri-o-overlay-amd64.tar.lz4
I0408 19:22:54.569691 198268 cache.go:56] Caching tarball of preloaded images
I0408 19:22:54.569815 198268 preload.go:172] Found /home/jenkins/minikube-integration/20604-141129/.minikube/cache/preloaded-tarball/preloaded-images-k8s-v18-v1.20.0-cri-o-overlay-amd64.tar.lz4 in cache, skipping download
I0408 19:22:54.569845 198268 cache.go:59] Finished verifying existence of preloaded tar for v1.20.0 on crio
I0408 19:22:54.569993 198268 profile.go:143] Saving config to /home/jenkins/minikube-integration/20604-141129/.minikube/profiles/old-k8s-version-257500/config.json ...
I0408 19:22:54.570026 198268 lock.go:35] WriteFile acquiring /home/jenkins/minikube-integration/20604-141129/.minikube/profiles/old-k8s-version-257500/config.json: {Name:mkf300ac4e6cded789cf7d57c4a37d251a5d2db3 Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0408 19:22:54.570236 198268 start.go:360] acquireMachinesLock for old-k8s-version-257500: {Name:mk9f7a747fe5c51efa93431b771c455683360918 Clock:{} Delay:500ms Timeout:13m0s Cancel:<nil>}
I0408 19:22:57.328370 198268 start.go:364] duration metric: took 2.758095814s to acquireMachinesLock for "old-k8s-version-257500"
I0408 19:22:57.328471 198268 start.go:93] Provisioning new machine with config: &{Name:old-k8s-version-257500 KeepContext:false EmbedCerts:false MinikubeISO:https://storage.googleapis.com/minikube/iso/minikube-v1.35.0-amd64.iso KicBaseImage:gcr.io/k8s-minikube/kicbase-builds:v0.0.46-1744107393-20604@sha256:2430533582a8c08f907b2d5976c79bd2e672b4f3d4484088c99b839f3175ed6a Memory:2200 CPUs:2 DiskSize:20000 Driver:kvm2 HyperkitVpnKitSock: HyperkitVSockPorts:[] DockerEnv:[] ContainerVolumeMounts:[] InsecureRegistry:[] RegistryMirror:[] HostOnlyCIDR:192.168.59.1/24 HypervVirtualSwitch: HypervUseExternalSwitch:false HypervExternalAdapter: KVMNetwork:default KVMQemuURI:qemu:///system KVMGPU:false KVMHidden:false KVMNUMACount:1 APIServerPort:8443 DockerOpt:[] DisableDriverMounts:true NFSShare:[] NFSSharesRoot:/nfsshares UUID: NoVTXCheck:false DNSProxy:false HostDNSResolver:true HostOnlyNicType:virtio NatNicType:virtio SSHIPAddress: SSHUser:root SSHKey: SSHPort:22 KubernetesConfig:{KubernetesVersion:v1.20.0 C
lusterName:old-k8s-version-257500 Namespace:default APIServerHAVIP: APIServerName:minikubeCA APIServerNames:[] APIServerIPs:[] DNSDomain:cluster.local ContainerRuntime:crio CRISocket: NetworkPlugin:cni FeatureGates: ServiceCIDR:10.96.0.0/12 ImageRepository: LoadBalancerStartIP: LoadBalancerEndIP: CustomIngressCert: RegistryAliases: ExtraOptions:[] ShouldLoadCachedImages:true EnableDefaultCNI:false CNI:} Nodes:[{Name: IP: Port:8443 KubernetesVersion:v1.20.0 ContainerRuntime:crio ControlPlane:true Worker:true}] Addons:map[] CustomAddonImages:map[] CustomAddonRegistries:map[] VerifyComponents:map[apiserver:true apps_running:true default_sa:true extra:true kubelet:true node_ready:true system_pods:true] StartHostTimeout:6m0s ScheduledStop:<nil> ExposedPorts:[] ListenAddress: Network: Subnet: MultiNodeRequested:false ExtraDisks:0 CertExpiration:26280h0m0s Mount:false MountString:/home/jenkins:/minikube-host Mount9PVersion:9p2000.L MountGID:docker MountIP: MountMSize:262144 MountOptions:[] MountPort:0 MountType:9p M
ountUID:docker BinaryMirror: DisableOptimizations:false DisableMetrics:false CustomQemuFirmwarePath: SocketVMnetClientPath: SocketVMnetPath: StaticIP: SSHAuthSock: SSHAgentPID:0 GPUs: AutoPauseInterval:1m0s} &{Name: IP: Port:8443 KubernetesVersion:v1.20.0 ContainerRuntime:crio ControlPlane:true Worker:true}
I0408 19:22:57.328668 198268 start.go:125] createHost starting for "" (driver="kvm2")
I0408 19:22:57.330829 198268 out.go:235] * Creating kvm2 VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
I0408 19:22:57.331182 198268 main.go:141] libmachine: Found binary path at /home/jenkins/workspace/KVM_Linux_crio_integration/out/docker-machine-driver-kvm2
I0408 19:22:57.331270 198268 main.go:141] libmachine: Launching plugin server for driver kvm2
I0408 19:22:57.353786 198268 main.go:141] libmachine: Plugin server listening at address 127.0.0.1:45677
I0408 19:22:57.354448 198268 main.go:141] libmachine: () Calling .GetVersion
I0408 19:22:57.355138 198268 main.go:141] libmachine: Using API Version 1
I0408 19:22:57.355157 198268 main.go:141] libmachine: () Calling .SetConfigRaw
I0408 19:22:57.355545 198268 main.go:141] libmachine: () Calling .GetMachineName
I0408 19:22:57.355768 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetMachineName
I0408 19:22:57.355947 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .DriverName
I0408 19:22:57.356127 198268 start.go:159] libmachine.API.Create for "old-k8s-version-257500" (driver="kvm2")
I0408 19:22:57.356156 198268 client.go:168] LocalClient.Create starting
I0408 19:22:57.356196 198268 main.go:141] libmachine: Reading certificate data from /home/jenkins/minikube-integration/20604-141129/.minikube/certs/ca.pem
I0408 19:22:57.356254 198268 main.go:141] libmachine: Decoding PEM data...
I0408 19:22:57.356278 198268 main.go:141] libmachine: Parsing certificate...
I0408 19:22:57.356374 198268 main.go:141] libmachine: Reading certificate data from /home/jenkins/minikube-integration/20604-141129/.minikube/certs/cert.pem
I0408 19:22:57.356412 198268 main.go:141] libmachine: Decoding PEM data...
I0408 19:22:57.356431 198268 main.go:141] libmachine: Parsing certificate...
I0408 19:22:57.356457 198268 main.go:141] libmachine: Running pre-create checks...
I0408 19:22:57.356472 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .PreCreateCheck
I0408 19:22:57.356898 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetConfigRaw
I0408 19:22:57.357407 198268 main.go:141] libmachine: Creating machine...
I0408 19:22:57.357425 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .Create
I0408 19:22:57.357627 198268 main.go:141] libmachine: (old-k8s-version-257500) creating KVM machine...
I0408 19:22:57.357644 198268 main.go:141] libmachine: (old-k8s-version-257500) creating network...
I0408 19:22:57.359455 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | found existing default KVM network
I0408 19:22:57.361142 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | I0408 19:22:57.360884 198418 network.go:206] using free private subnet 192.168.39.0/24: &{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: IfaceIPv4: IfaceMTU:0 IfaceMAC:} reservation:0xc000113380}
I0408 19:22:57.361175 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | created network xml:
I0408 19:22:57.361190 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | <network>
I0408 19:22:57.361199 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | <name>mk-old-k8s-version-257500</name>
I0408 19:22:57.361242 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | <dns enable='no'/>
I0408 19:22:57.361260 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG |
I0408 19:22:57.361272 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | <ip address='192.168.39.1' netmask='255.255.255.0'>
I0408 19:22:57.361284 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | <dhcp>
I0408 19:22:57.361292 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | <range start='192.168.39.2' end='192.168.39.253'/>
I0408 19:22:57.361300 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | </dhcp>
I0408 19:22:57.361312 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | </ip>
I0408 19:22:57.361331 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG |
I0408 19:22:57.361343 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | </network>
I0408 19:22:57.361353 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG |
I0408 19:22:57.368527 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | trying to create private KVM network mk-old-k8s-version-257500 192.168.39.0/24...
I0408 19:22:57.472174 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | private KVM network mk-old-k8s-version-257500 192.168.39.0/24 created
I0408 19:22:57.472328 198268 main.go:141] libmachine: (old-k8s-version-257500) setting up store path in /home/jenkins/minikube-integration/20604-141129/.minikube/machines/old-k8s-version-257500 ...
I0408 19:22:57.472368 198268 main.go:141] libmachine: (old-k8s-version-257500) building disk image from file:///home/jenkins/minikube-integration/20604-141129/.minikube/cache/iso/amd64/minikube-v1.35.0-amd64.iso
I0408 19:22:57.472388 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | I0408 19:22:57.472333 198418 common.go:144] Making disk image using store path: /home/jenkins/minikube-integration/20604-141129/.minikube
I0408 19:22:57.472595 198268 main.go:141] libmachine: (old-k8s-version-257500) Downloading /home/jenkins/minikube-integration/20604-141129/.minikube/cache/boot2docker.iso from file:///home/jenkins/minikube-integration/20604-141129/.minikube/cache/iso/amd64/minikube-v1.35.0-amd64.iso...
I0408 19:22:57.824507 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | I0408 19:22:57.824327 198418 common.go:151] Creating ssh key: /home/jenkins/minikube-integration/20604-141129/.minikube/machines/old-k8s-version-257500/id_rsa...
I0408 19:22:58.413626 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | I0408 19:22:58.413468 198418 common.go:157] Creating raw disk image: /home/jenkins/minikube-integration/20604-141129/.minikube/machines/old-k8s-version-257500/old-k8s-version-257500.rawdisk...
I0408 19:22:58.413659 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | Writing magic tar header
I0408 19:22:58.413675 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | Writing SSH key tar header
I0408 19:22:58.413687 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | I0408 19:22:58.413655 198418 common.go:171] Fixing permissions on /home/jenkins/minikube-integration/20604-141129/.minikube/machines/old-k8s-version-257500 ...
I0408 19:22:58.413858 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | checking permissions on dir: /home/jenkins/minikube-integration/20604-141129/.minikube/machines/old-k8s-version-257500
I0408 19:22:58.413883 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | checking permissions on dir: /home/jenkins/minikube-integration/20604-141129/.minikube/machines
I0408 19:22:58.413903 198268 main.go:141] libmachine: (old-k8s-version-257500) setting executable bit set on /home/jenkins/minikube-integration/20604-141129/.minikube/machines/old-k8s-version-257500 (perms=drwx------)
I0408 19:22:58.413918 198268 main.go:141] libmachine: (old-k8s-version-257500) setting executable bit set on /home/jenkins/minikube-integration/20604-141129/.minikube/machines (perms=drwxr-xr-x)
I0408 19:22:58.413937 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | checking permissions on dir: /home/jenkins/minikube-integration/20604-141129/.minikube
I0408 19:22:58.414041 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | checking permissions on dir: /home/jenkins/minikube-integration/20604-141129
I0408 19:22:58.414078 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | checking permissions on dir: /home/jenkins/minikube-integration
I0408 19:22:58.414093 198268 main.go:141] libmachine: (old-k8s-version-257500) setting executable bit set on /home/jenkins/minikube-integration/20604-141129/.minikube (perms=drwxr-xr-x)
I0408 19:22:58.414115 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | checking permissions on dir: /home/jenkins
I0408 19:22:58.414134 198268 main.go:141] libmachine: (old-k8s-version-257500) setting executable bit set on /home/jenkins/minikube-integration/20604-141129 (perms=drwxrwxr-x)
I0408 19:22:58.414146 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | checking permissions on dir: /home
I0408 19:22:58.414156 198268 main.go:141] libmachine: (old-k8s-version-257500) setting executable bit set on /home/jenkins/minikube-integration (perms=drwxrwxr-x)
I0408 19:22:58.414173 198268 main.go:141] libmachine: (old-k8s-version-257500) setting executable bit set on /home/jenkins (perms=drwxr-xr-x)
I0408 19:22:58.414182 198268 main.go:141] libmachine: (old-k8s-version-257500) creating domain...
I0408 19:22:58.414195 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | skipping /home - not owner
I0408 19:22:58.415697 198268 main.go:141] libmachine: (old-k8s-version-257500) define libvirt domain using xml:
I0408 19:22:58.415725 198268 main.go:141] libmachine: (old-k8s-version-257500) <domain type='kvm'>
I0408 19:22:58.415736 198268 main.go:141] libmachine: (old-k8s-version-257500) <name>old-k8s-version-257500</name>
I0408 19:22:58.415747 198268 main.go:141] libmachine: (old-k8s-version-257500) <memory unit='MiB'>2200</memory>
I0408 19:22:58.415766 198268 main.go:141] libmachine: (old-k8s-version-257500) <vcpu>2</vcpu>
I0408 19:22:58.415775 198268 main.go:141] libmachine: (old-k8s-version-257500) <features>
I0408 19:22:58.415814 198268 main.go:141] libmachine: (old-k8s-version-257500) <acpi/>
I0408 19:22:58.415839 198268 main.go:141] libmachine: (old-k8s-version-257500) <apic/>
I0408 19:22:58.415855 198268 main.go:141] libmachine: (old-k8s-version-257500) <pae/>
I0408 19:22:58.415866 198268 main.go:141] libmachine: (old-k8s-version-257500)
I0408 19:22:58.415879 198268 main.go:141] libmachine: (old-k8s-version-257500) </features>
I0408 19:22:58.415887 198268 main.go:141] libmachine: (old-k8s-version-257500) <cpu mode='host-passthrough'>
I0408 19:22:58.415897 198268 main.go:141] libmachine: (old-k8s-version-257500)
I0408 19:22:58.415904 198268 main.go:141] libmachine: (old-k8s-version-257500) </cpu>
I0408 19:22:58.415915 198268 main.go:141] libmachine: (old-k8s-version-257500) <os>
I0408 19:22:58.415925 198268 main.go:141] libmachine: (old-k8s-version-257500) <type>hvm</type>
I0408 19:22:58.415935 198268 main.go:141] libmachine: (old-k8s-version-257500) <boot dev='cdrom'/>
I0408 19:22:58.415949 198268 main.go:141] libmachine: (old-k8s-version-257500) <boot dev='hd'/>
I0408 19:22:58.415962 198268 main.go:141] libmachine: (old-k8s-version-257500) <bootmenu enable='no'/>
I0408 19:22:58.415971 198268 main.go:141] libmachine: (old-k8s-version-257500) </os>
I0408 19:22:58.415980 198268 main.go:141] libmachine: (old-k8s-version-257500) <devices>
I0408 19:22:58.415991 198268 main.go:141] libmachine: (old-k8s-version-257500) <disk type='file' device='cdrom'>
I0408 19:22:58.416007 198268 main.go:141] libmachine: (old-k8s-version-257500) <source file='/home/jenkins/minikube-integration/20604-141129/.minikube/machines/old-k8s-version-257500/boot2docker.iso'/>
I0408 19:22:58.416023 198268 main.go:141] libmachine: (old-k8s-version-257500) <target dev='hdc' bus='scsi'/>
I0408 19:22:58.416035 198268 main.go:141] libmachine: (old-k8s-version-257500) <readonly/>
I0408 19:22:58.416045 198268 main.go:141] libmachine: (old-k8s-version-257500) </disk>
I0408 19:22:58.416118 198268 main.go:141] libmachine: (old-k8s-version-257500) <disk type='file' device='disk'>
I0408 19:22:58.416156 198268 main.go:141] libmachine: (old-k8s-version-257500) <driver name='qemu' type='raw' cache='default' io='threads' />
I0408 19:22:58.416181 198268 main.go:141] libmachine: (old-k8s-version-257500) <source file='/home/jenkins/minikube-integration/20604-141129/.minikube/machines/old-k8s-version-257500/old-k8s-version-257500.rawdisk'/>
I0408 19:22:58.416248 198268 main.go:141] libmachine: (old-k8s-version-257500) <target dev='hda' bus='virtio'/>
I0408 19:22:58.416281 198268 main.go:141] libmachine: (old-k8s-version-257500) </disk>
I0408 19:22:58.416294 198268 main.go:141] libmachine: (old-k8s-version-257500) <interface type='network'>
I0408 19:22:58.416306 198268 main.go:141] libmachine: (old-k8s-version-257500) <source network='mk-old-k8s-version-257500'/>
I0408 19:22:58.416317 198268 main.go:141] libmachine: (old-k8s-version-257500) <model type='virtio'/>
I0408 19:22:58.416330 198268 main.go:141] libmachine: (old-k8s-version-257500) </interface>
I0408 19:22:58.416342 198268 main.go:141] libmachine: (old-k8s-version-257500) <interface type='network'>
I0408 19:22:58.416356 198268 main.go:141] libmachine: (old-k8s-version-257500) <source network='default'/>
I0408 19:22:58.416367 198268 main.go:141] libmachine: (old-k8s-version-257500) <model type='virtio'/>
I0408 19:22:58.416379 198268 main.go:141] libmachine: (old-k8s-version-257500) </interface>
I0408 19:22:58.416400 198268 main.go:141] libmachine: (old-k8s-version-257500) <serial type='pty'>
I0408 19:22:58.416428 198268 main.go:141] libmachine: (old-k8s-version-257500) <target port='0'/>
I0408 19:22:58.416452 198268 main.go:141] libmachine: (old-k8s-version-257500) </serial>
I0408 19:22:58.416466 198268 main.go:141] libmachine: (old-k8s-version-257500) <console type='pty'>
I0408 19:22:58.416483 198268 main.go:141] libmachine: (old-k8s-version-257500) <target type='serial' port='0'/>
I0408 19:22:58.416494 198268 main.go:141] libmachine: (old-k8s-version-257500) </console>
I0408 19:22:58.416504 198268 main.go:141] libmachine: (old-k8s-version-257500) <rng model='virtio'>
I0408 19:22:58.416517 198268 main.go:141] libmachine: (old-k8s-version-257500) <backend model='random'>/dev/random</backend>
I0408 19:22:58.416531 198268 main.go:141] libmachine: (old-k8s-version-257500) </rng>
I0408 19:22:58.416543 198268 main.go:141] libmachine: (old-k8s-version-257500)
I0408 19:22:58.416554 198268 main.go:141] libmachine: (old-k8s-version-257500)
I0408 19:22:58.416581 198268 main.go:141] libmachine: (old-k8s-version-257500) </devices>
I0408 19:22:58.416611 198268 main.go:141] libmachine: (old-k8s-version-257500) </domain>
I0408 19:22:58.416644 198268 main.go:141] libmachine: (old-k8s-version-257500)
I0408 19:22:58.422053 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:23:10:39 in network default
I0408 19:22:58.422876 198268 main.go:141] libmachine: (old-k8s-version-257500) starting domain...
I0408 19:22:58.422901 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:22:58.422911 198268 main.go:141] libmachine: (old-k8s-version-257500) ensuring networks are active...
I0408 19:22:58.423813 198268 main.go:141] libmachine: (old-k8s-version-257500) Ensuring network default is active
I0408 19:22:58.424371 198268 main.go:141] libmachine: (old-k8s-version-257500) Ensuring network mk-old-k8s-version-257500 is active
I0408 19:22:58.425152 198268 main.go:141] libmachine: (old-k8s-version-257500) getting domain XML...
I0408 19:22:58.426180 198268 main.go:141] libmachine: (old-k8s-version-257500) creating domain...
I0408 19:23:00.259676 198268 main.go:141] libmachine: (old-k8s-version-257500) waiting for IP...
I0408 19:23:00.260816 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:00.261614 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | unable to find current IP address of domain old-k8s-version-257500 in network mk-old-k8s-version-257500
I0408 19:23:00.261637 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | I0408 19:23:00.261517 198418 retry.go:31] will retry after 252.097451ms: waiting for domain to come up
I0408 19:23:00.515222 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:00.515896 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | unable to find current IP address of domain old-k8s-version-257500 in network mk-old-k8s-version-257500
I0408 19:23:00.515925 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | I0408 19:23:00.515870 198418 retry.go:31] will retry after 319.135243ms: waiting for domain to come up
I0408 19:23:00.836637 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:00.837210 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | unable to find current IP address of domain old-k8s-version-257500 in network mk-old-k8s-version-257500
I0408 19:23:00.837233 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | I0408 19:23:00.837135 198418 retry.go:31] will retry after 426.211637ms: waiting for domain to come up
I0408 19:23:01.269963 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:01.270004 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | unable to find current IP address of domain old-k8s-version-257500 in network mk-old-k8s-version-257500
I0408 19:23:01.270022 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | I0408 19:23:01.267802 198418 retry.go:31] will retry after 588.844985ms: waiting for domain to come up
I0408 19:23:01.858988 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:01.859597 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | unable to find current IP address of domain old-k8s-version-257500 in network mk-old-k8s-version-257500
I0408 19:23:01.859624 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | I0408 19:23:01.859587 198418 retry.go:31] will retry after 507.01837ms: waiting for domain to come up
I0408 19:23:02.368482 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:02.369185 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | unable to find current IP address of domain old-k8s-version-257500 in network mk-old-k8s-version-257500
I0408 19:23:02.369218 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | I0408 19:23:02.369091 198418 retry.go:31] will retry after 622.779742ms: waiting for domain to come up
I0408 19:23:02.994197 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:02.994637 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | unable to find current IP address of domain old-k8s-version-257500 in network mk-old-k8s-version-257500
I0408 19:23:02.994670 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | I0408 19:23:02.994604 198418 retry.go:31] will retry after 822.166675ms: waiting for domain to come up
I0408 19:23:03.818936 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:03.819345 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | unable to find current IP address of domain old-k8s-version-257500 in network mk-old-k8s-version-257500
I0408 19:23:03.819403 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | I0408 19:23:03.819327 198418 retry.go:31] will retry after 1.466030512s: waiting for domain to come up
I0408 19:23:05.291061 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:05.291959 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | unable to find current IP address of domain old-k8s-version-257500 in network mk-old-k8s-version-257500
I0408 19:23:05.292014 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | I0408 19:23:05.291974 198418 retry.go:31] will retry after 1.196386795s: waiting for domain to come up
I0408 19:23:06.490231 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:06.490771 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | unable to find current IP address of domain old-k8s-version-257500 in network mk-old-k8s-version-257500
I0408 19:23:06.490805 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | I0408 19:23:06.490742 198418 retry.go:31] will retry after 2.060880175s: waiting for domain to come up
I0408 19:23:08.553694 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:08.554352 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | unable to find current IP address of domain old-k8s-version-257500 in network mk-old-k8s-version-257500
I0408 19:23:08.554383 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | I0408 19:23:08.554313 198418 retry.go:31] will retry after 2.309267043s: waiting for domain to come up
I0408 19:23:10.867001 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:10.867743 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | unable to find current IP address of domain old-k8s-version-257500 in network mk-old-k8s-version-257500
I0408 19:23:10.867771 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | I0408 19:23:10.867640 198418 retry.go:31] will retry after 2.516284552s: waiting for domain to come up
I0408 19:23:13.385497 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:13.386287 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | unable to find current IP address of domain old-k8s-version-257500 in network mk-old-k8s-version-257500
I0408 19:23:13.386319 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | I0408 19:23:13.386249 198418 retry.go:31] will retry after 3.697797392s: waiting for domain to come up
I0408 19:23:17.087212 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:17.087715 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | unable to find current IP address of domain old-k8s-version-257500 in network mk-old-k8s-version-257500
I0408 19:23:17.087742 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | I0408 19:23:17.087665 198418 retry.go:31] will retry after 4.688868315s: waiting for domain to come up
I0408 19:23:21.779009 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:21.779579 198268 main.go:141] libmachine: (old-k8s-version-257500) found domain IP: 192.168.39.192
I0408 19:23:21.779602 198268 main.go:141] libmachine: (old-k8s-version-257500) reserving static IP address...
I0408 19:23:21.779626 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has current primary IP address 192.168.39.192 and MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:21.779977 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | unable to find host DHCP lease matching {name: "old-k8s-version-257500", mac: "52:54:00:00:35:99", ip: "192.168.39.192"} in network mk-old-k8s-version-257500
I0408 19:23:21.884100 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | Getting to WaitForSSH function...
I0408 19:23:21.884132 198268 main.go:141] libmachine: (old-k8s-version-257500) reserved static IP address 192.168.39.192 for domain old-k8s-version-257500
I0408 19:23:21.884144 198268 main.go:141] libmachine: (old-k8s-version-257500) waiting for SSH...
I0408 19:23:21.887711 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:21.888240 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:00:35:99", ip: ""} in network mk-old-k8s-version-257500: {Iface:virbr1 ExpiryTime:2025-04-08 20:23:15 +0000 UTC Type:0 Mac:52:54:00:00:35:99 Iaid: IPaddr:192.168.39.192 Prefix:24 Hostname:minikube Clientid:01:52:54:00:00:35:99}
I0408 19:23:21.888281 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined IP address 192.168.39.192 and MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:21.888590 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | Using SSH client type: external
I0408 19:23:21.888618 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | Using SSH private key: /home/jenkins/minikube-integration/20604-141129/.minikube/machines/old-k8s-version-257500/id_rsa (-rw-------)
I0408 19:23:21.888651 198268 main.go:141] libmachine: (old-k8s-version-257500) 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.39.192 -o IdentitiesOnly=yes -i /home/jenkins/minikube-integration/20604-141129/.minikube/machines/old-k8s-version-257500/id_rsa -p 22] /usr/bin/ssh <nil>}
I0408 19:23:21.888666 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | About to run SSH command:
I0408 19:23:21.888711 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | exit 0
I0408 19:23:22.022079 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | SSH cmd err, output: <nil>:
I0408 19:23:22.022403 198268 main.go:141] libmachine: (old-k8s-version-257500) KVM machine creation complete
I0408 19:23:22.022785 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetConfigRaw
I0408 19:23:22.023452 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .DriverName
I0408 19:23:22.023696 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .DriverName
I0408 19:23:22.023880 198268 main.go:141] libmachine: Waiting for machine to be running, this may take a few minutes...
I0408 19:23:22.023895 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetState
I0408 19:23:22.025734 198268 main.go:141] libmachine: Detecting operating system of created instance...
I0408 19:23:22.025754 198268 main.go:141] libmachine: Waiting for SSH to be available...
I0408 19:23:22.025762 198268 main.go:141] libmachine: Getting to WaitForSSH function...
I0408 19:23:22.025771 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHHostname
I0408 19:23:22.028302 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:22.028701 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:00:35:99", ip: ""} in network mk-old-k8s-version-257500: {Iface:virbr1 ExpiryTime:2025-04-08 20:23:15 +0000 UTC Type:0 Mac:52:54:00:00:35:99 Iaid: IPaddr:192.168.39.192 Prefix:24 Hostname:old-k8s-version-257500 Clientid:01:52:54:00:00:35:99}
I0408 19:23:22.028732 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined IP address 192.168.39.192 and MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:22.029051 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHPort
I0408 19:23:22.029306 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHKeyPath
I0408 19:23:22.029497 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHKeyPath
I0408 19:23:22.029650 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHUsername
I0408 19:23:22.029810 198268 main.go:141] libmachine: Using SSH client type: native
I0408 19:23:22.030096 198268 main.go:141] libmachine: &{{{<nil> 0 [] [] []} docker [0x836360] 0x839060 <nil> [] 0s} 192.168.39.192 22 <nil> <nil>}
I0408 19:23:22.030111 198268 main.go:141] libmachine: About to run SSH command:
exit 0
I0408 19:23:22.145329 198268 main.go:141] libmachine: SSH cmd err, output: <nil>:
I0408 19:23:22.145355 198268 main.go:141] libmachine: Detecting the provisioner...
I0408 19:23:22.145364 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHHostname
I0408 19:23:22.148681 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:22.149071 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:00:35:99", ip: ""} in network mk-old-k8s-version-257500: {Iface:virbr1 ExpiryTime:2025-04-08 20:23:15 +0000 UTC Type:0 Mac:52:54:00:00:35:99 Iaid: IPaddr:192.168.39.192 Prefix:24 Hostname:old-k8s-version-257500 Clientid:01:52:54:00:00:35:99}
I0408 19:23:22.149106 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined IP address 192.168.39.192 and MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:22.149331 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHPort
I0408 19:23:22.149556 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHKeyPath
I0408 19:23:22.149746 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHKeyPath
I0408 19:23:22.149973 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHUsername
I0408 19:23:22.150198 198268 main.go:141] libmachine: Using SSH client type: native
I0408 19:23:22.150486 198268 main.go:141] libmachine: &{{{<nil> 0 [] [] []} docker [0x836360] 0x839060 <nil> [] 0s} 192.168.39.192 22 <nil> <nil>}
I0408 19:23:22.150503 198268 main.go:141] libmachine: About to run SSH command:
cat /etc/os-release
I0408 19:23:22.271539 198268 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"
I0408 19:23:22.271592 198268 main.go:141] libmachine: found compatible host: buildroot
I0408 19:23:22.271600 198268 main.go:141] libmachine: Provisioning with buildroot...
I0408 19:23:22.271611 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetMachineName
I0408 19:23:22.271897 198268 buildroot.go:166] provisioning hostname "old-k8s-version-257500"
I0408 19:23:22.271927 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetMachineName
I0408 19:23:22.272140 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHHostname
I0408 19:23:22.275245 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:22.275598 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:00:35:99", ip: ""} in network mk-old-k8s-version-257500: {Iface:virbr1 ExpiryTime:2025-04-08 20:23:15 +0000 UTC Type:0 Mac:52:54:00:00:35:99 Iaid: IPaddr:192.168.39.192 Prefix:24 Hostname:old-k8s-version-257500 Clientid:01:52:54:00:00:35:99}
I0408 19:23:22.275626 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined IP address 192.168.39.192 and MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:22.275819 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHPort
I0408 19:23:22.276029 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHKeyPath
I0408 19:23:22.276218 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHKeyPath
I0408 19:23:22.276381 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHUsername
I0408 19:23:22.276568 198268 main.go:141] libmachine: Using SSH client type: native
I0408 19:23:22.276774 198268 main.go:141] libmachine: &{{{<nil> 0 [] [] []} docker [0x836360] 0x839060 <nil> [] 0s} 192.168.39.192 22 <nil> <nil>}
I0408 19:23:22.276787 198268 main.go:141] libmachine: About to run SSH command:
sudo hostname old-k8s-version-257500 && echo "old-k8s-version-257500" | sudo tee /etc/hostname
I0408 19:23:22.414223 198268 main.go:141] libmachine: SSH cmd err, output: <nil>: old-k8s-version-257500
I0408 19:23:22.414264 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHHostname
I0408 19:23:22.417368 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:22.417856 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:00:35:99", ip: ""} in network mk-old-k8s-version-257500: {Iface:virbr1 ExpiryTime:2025-04-08 20:23:15 +0000 UTC Type:0 Mac:52:54:00:00:35:99 Iaid: IPaddr:192.168.39.192 Prefix:24 Hostname:old-k8s-version-257500 Clientid:01:52:54:00:00:35:99}
I0408 19:23:22.417891 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined IP address 192.168.39.192 and MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:22.418187 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHPort
I0408 19:23:22.418447 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHKeyPath
I0408 19:23:22.418755 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHKeyPath
I0408 19:23:22.419072 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHUsername
I0408 19:23:22.419382 198268 main.go:141] libmachine: Using SSH client type: native
I0408 19:23:22.419682 198268 main.go:141] libmachine: &{{{<nil> 0 [] [] []} docker [0x836360] 0x839060 <nil> [] 0s} 192.168.39.192 22 <nil> <nil>}
I0408 19:23:22.419714 198268 main.go:141] libmachine: About to run SSH command:
if ! grep -xq '.*\sold-k8s-version-257500' /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-257500/g' /etc/hosts;
else
echo '127.0.1.1 old-k8s-version-257500' | sudo tee -a /etc/hosts;
fi
fi
I0408 19:23:22.543436 198268 main.go:141] libmachine: SSH cmd err, output: <nil>:
I0408 19:23:22.543480 198268 buildroot.go:172] set auth options {CertDir:/home/jenkins/minikube-integration/20604-141129/.minikube CaCertPath:/home/jenkins/minikube-integration/20604-141129/.minikube/certs/ca.pem CaPrivateKeyPath:/home/jenkins/minikube-integration/20604-141129/.minikube/certs/ca-key.pem CaCertRemotePath:/etc/docker/ca.pem ServerCertPath:/home/jenkins/minikube-integration/20604-141129/.minikube/machines/server.pem ServerKeyPath:/home/jenkins/minikube-integration/20604-141129/.minikube/machines/server-key.pem ClientKeyPath:/home/jenkins/minikube-integration/20604-141129/.minikube/certs/key.pem ServerCertRemotePath:/etc/docker/server.pem ServerKeyRemotePath:/etc/docker/server-key.pem ClientCertPath:/home/jenkins/minikube-integration/20604-141129/.minikube/certs/cert.pem ServerCertSANs:[] StorePath:/home/jenkins/minikube-integration/20604-141129/.minikube}
I0408 19:23:22.543508 198268 buildroot.go:174] setting up certificates
I0408 19:23:22.543523 198268 provision.go:84] configureAuth start
I0408 19:23:22.543541 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetMachineName
I0408 19:23:22.543863 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetIP
I0408 19:23:22.547129 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:22.547493 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:00:35:99", ip: ""} in network mk-old-k8s-version-257500: {Iface:virbr1 ExpiryTime:2025-04-08 20:23:15 +0000 UTC Type:0 Mac:52:54:00:00:35:99 Iaid: IPaddr:192.168.39.192 Prefix:24 Hostname:old-k8s-version-257500 Clientid:01:52:54:00:00:35:99}
I0408 19:23:22.547528 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined IP address 192.168.39.192 and MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:22.547715 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHHostname
I0408 19:23:22.550477 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:22.550845 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:00:35:99", ip: ""} in network mk-old-k8s-version-257500: {Iface:virbr1 ExpiryTime:2025-04-08 20:23:15 +0000 UTC Type:0 Mac:52:54:00:00:35:99 Iaid: IPaddr:192.168.39.192 Prefix:24 Hostname:old-k8s-version-257500 Clientid:01:52:54:00:00:35:99}
I0408 19:23:22.550881 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined IP address 192.168.39.192 and MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:22.551105 198268 provision.go:143] copyHostCerts
I0408 19:23:22.551174 198268 exec_runner.go:144] found /home/jenkins/minikube-integration/20604-141129/.minikube/key.pem, removing ...
I0408 19:23:22.551202 198268 exec_runner.go:203] rm: /home/jenkins/minikube-integration/20604-141129/.minikube/key.pem
I0408 19:23:22.551291 198268 exec_runner.go:151] cp: /home/jenkins/minikube-integration/20604-141129/.minikube/certs/key.pem --> /home/jenkins/minikube-integration/20604-141129/.minikube/key.pem (1679 bytes)
I0408 19:23:22.551395 198268 exec_runner.go:144] found /home/jenkins/minikube-integration/20604-141129/.minikube/ca.pem, removing ...
I0408 19:23:22.551404 198268 exec_runner.go:203] rm: /home/jenkins/minikube-integration/20604-141129/.minikube/ca.pem
I0408 19:23:22.551428 198268 exec_runner.go:151] cp: /home/jenkins/minikube-integration/20604-141129/.minikube/certs/ca.pem --> /home/jenkins/minikube-integration/20604-141129/.minikube/ca.pem (1082 bytes)
I0408 19:23:22.551482 198268 exec_runner.go:144] found /home/jenkins/minikube-integration/20604-141129/.minikube/cert.pem, removing ...
I0408 19:23:22.551489 198268 exec_runner.go:203] rm: /home/jenkins/minikube-integration/20604-141129/.minikube/cert.pem
I0408 19:23:22.551508 198268 exec_runner.go:151] cp: /home/jenkins/minikube-integration/20604-141129/.minikube/certs/cert.pem --> /home/jenkins/minikube-integration/20604-141129/.minikube/cert.pem (1123 bytes)
I0408 19:23:22.551564 198268 provision.go:117] generating server cert: /home/jenkins/minikube-integration/20604-141129/.minikube/machines/server.pem ca-key=/home/jenkins/minikube-integration/20604-141129/.minikube/certs/ca.pem private-key=/home/jenkins/minikube-integration/20604-141129/.minikube/certs/ca-key.pem org=jenkins.old-k8s-version-257500 san=[127.0.0.1 192.168.39.192 localhost minikube old-k8s-version-257500]
I0408 19:23:22.615251 198268 provision.go:177] copyRemoteCerts
I0408 19:23:22.615312 198268 ssh_runner.go:195] Run: sudo mkdir -p /etc/docker /etc/docker /etc/docker
I0408 19:23:22.615344 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHHostname
I0408 19:23:22.618556 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:22.618878 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:00:35:99", ip: ""} in network mk-old-k8s-version-257500: {Iface:virbr1 ExpiryTime:2025-04-08 20:23:15 +0000 UTC Type:0 Mac:52:54:00:00:35:99 Iaid: IPaddr:192.168.39.192 Prefix:24 Hostname:old-k8s-version-257500 Clientid:01:52:54:00:00:35:99}
I0408 19:23:22.618904 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined IP address 192.168.39.192 and MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:22.619149 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHPort
I0408 19:23:22.619385 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHKeyPath
I0408 19:23:22.619576 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHUsername
I0408 19:23:22.619902 198268 sshutil.go:53] new ssh client: &{IP:192.168.39.192 Port:22 SSHKeyPath:/home/jenkins/minikube-integration/20604-141129/.minikube/machines/old-k8s-version-257500/id_rsa Username:docker}
I0408 19:23:22.708550 198268 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20604-141129/.minikube/machines/server-key.pem --> /etc/docker/server-key.pem (1675 bytes)
I0408 19:23:22.737542 198268 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20604-141129/.minikube/certs/ca.pem --> /etc/docker/ca.pem (1082 bytes)
I0408 19:23:22.765989 198268 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20604-141129/.minikube/machines/server.pem --> /etc/docker/server.pem (1233 bytes)
I0408 19:23:22.792663 198268 provision.go:87] duration metric: took 249.121134ms to configureAuth
I0408 19:23:22.792695 198268 buildroot.go:189] setting minikube options for container-runtime
I0408 19:23:22.792866 198268 config.go:182] Loaded profile config "old-k8s-version-257500": Driver=kvm2, ContainerRuntime=crio, KubernetesVersion=v1.20.0
I0408 19:23:22.792959 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHHostname
I0408 19:23:22.795599 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:22.796034 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:00:35:99", ip: ""} in network mk-old-k8s-version-257500: {Iface:virbr1 ExpiryTime:2025-04-08 20:23:15 +0000 UTC Type:0 Mac:52:54:00:00:35:99 Iaid: IPaddr:192.168.39.192 Prefix:24 Hostname:old-k8s-version-257500 Clientid:01:52:54:00:00:35:99}
I0408 19:23:22.796067 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined IP address 192.168.39.192 and MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:22.796278 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHPort
I0408 19:23:22.796494 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHKeyPath
I0408 19:23:22.796632 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHKeyPath
I0408 19:23:22.796790 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHUsername
I0408 19:23:22.796948 198268 main.go:141] libmachine: Using SSH client type: native
I0408 19:23:22.797193 198268 main.go:141] libmachine: &{{{<nil> 0 [] [] []} docker [0x836360] 0x839060 <nil> [] 0s} 192.168.39.192 22 <nil> <nil>}
I0408 19:23:22.797217 198268 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
I0408 19:23:23.039418 198268 main.go:141] libmachine: SSH cmd err, output: <nil>:
CRIO_MINIKUBE_OPTIONS='--insecure-registry 10.96.0.0/12 '
I0408 19:23:23.039446 198268 main.go:141] libmachine: Checking connection to Docker...
I0408 19:23:23.039454 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetURL
I0408 19:23:23.040904 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | using libvirt version 6000000
I0408 19:23:23.043249 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:23.043573 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:00:35:99", ip: ""} in network mk-old-k8s-version-257500: {Iface:virbr1 ExpiryTime:2025-04-08 20:23:15 +0000 UTC Type:0 Mac:52:54:00:00:35:99 Iaid: IPaddr:192.168.39.192 Prefix:24 Hostname:old-k8s-version-257500 Clientid:01:52:54:00:00:35:99}
I0408 19:23:23.043604 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined IP address 192.168.39.192 and MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:23.043754 198268 main.go:141] libmachine: Docker is up and running!
I0408 19:23:23.043768 198268 main.go:141] libmachine: Reticulating splines...
I0408 19:23:23.043778 198268 client.go:171] duration metric: took 25.687612742s to LocalClient.Create
I0408 19:23:23.043815 198268 start.go:167] duration metric: took 25.687688223s to libmachine.API.Create "old-k8s-version-257500"
I0408 19:23:23.043828 198268 start.go:293] postStartSetup for "old-k8s-version-257500" (driver="kvm2")
I0408 19:23:23.043839 198268 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]
I0408 19:23:23.043861 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .DriverName
I0408 19:23:23.044113 198268 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
I0408 19:23:23.044154 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHHostname
I0408 19:23:23.046265 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:23.046574 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:00:35:99", ip: ""} in network mk-old-k8s-version-257500: {Iface:virbr1 ExpiryTime:2025-04-08 20:23:15 +0000 UTC Type:0 Mac:52:54:00:00:35:99 Iaid: IPaddr:192.168.39.192 Prefix:24 Hostname:old-k8s-version-257500 Clientid:01:52:54:00:00:35:99}
I0408 19:23:23.046602 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined IP address 192.168.39.192 and MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:23.046792 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHPort
I0408 19:23:23.047025 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHKeyPath
I0408 19:23:23.047226 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHUsername
I0408 19:23:23.047402 198268 sshutil.go:53] new ssh client: &{IP:192.168.39.192 Port:22 SSHKeyPath:/home/jenkins/minikube-integration/20604-141129/.minikube/machines/old-k8s-version-257500/id_rsa Username:docker}
I0408 19:23:23.136573 198268 ssh_runner.go:195] Run: cat /etc/os-release
I0408 19:23:23.141186 198268 info.go:137] Remote host: Buildroot 2023.02.9
I0408 19:23:23.141213 198268 filesync.go:126] Scanning /home/jenkins/minikube-integration/20604-141129/.minikube/addons for local assets ...
I0408 19:23:23.141301 198268 filesync.go:126] Scanning /home/jenkins/minikube-integration/20604-141129/.minikube/files for local assets ...
I0408 19:23:23.141418 198268 filesync.go:149] local asset: /home/jenkins/minikube-integration/20604-141129/.minikube/files/etc/ssl/certs/1484872.pem -> 1484872.pem in /etc/ssl/certs
I0408 19:23:23.141520 198268 ssh_runner.go:195] Run: sudo mkdir -p /etc/ssl/certs
I0408 19:23:23.152534 198268 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20604-141129/.minikube/files/etc/ssl/certs/1484872.pem --> /etc/ssl/certs/1484872.pem (1708 bytes)
I0408 19:23:23.179311 198268 start.go:296] duration metric: took 135.466005ms for postStartSetup
I0408 19:23:23.179373 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetConfigRaw
I0408 19:23:23.180021 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetIP
I0408 19:23:23.183311 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:23.183685 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:00:35:99", ip: ""} in network mk-old-k8s-version-257500: {Iface:virbr1 ExpiryTime:2025-04-08 20:23:15 +0000 UTC Type:0 Mac:52:54:00:00:35:99 Iaid: IPaddr:192.168.39.192 Prefix:24 Hostname:old-k8s-version-257500 Clientid:01:52:54:00:00:35:99}
I0408 19:23:23.183715 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined IP address 192.168.39.192 and MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:23.183928 198268 profile.go:143] Saving config to /home/jenkins/minikube-integration/20604-141129/.minikube/profiles/old-k8s-version-257500/config.json ...
I0408 19:23:23.184146 198268 start.go:128] duration metric: took 25.855460195s to createHost
I0408 19:23:23.184173 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHHostname
I0408 19:23:23.186838 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:23.187320 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:00:35:99", ip: ""} in network mk-old-k8s-version-257500: {Iface:virbr1 ExpiryTime:2025-04-08 20:23:15 +0000 UTC Type:0 Mac:52:54:00:00:35:99 Iaid: IPaddr:192.168.39.192 Prefix:24 Hostname:old-k8s-version-257500 Clientid:01:52:54:00:00:35:99}
I0408 19:23:23.187354 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined IP address 192.168.39.192 and MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:23.187531 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHPort
I0408 19:23:23.187748 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHKeyPath
I0408 19:23:23.187957 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHKeyPath
I0408 19:23:23.188141 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHUsername
I0408 19:23:23.188322 198268 main.go:141] libmachine: Using SSH client type: native
I0408 19:23:23.188536 198268 main.go:141] libmachine: &{{{<nil> 0 [] [] []} docker [0x836360] 0x839060 <nil> [] 0s} 192.168.39.192 22 <nil> <nil>}
I0408 19:23:23.188547 198268 main.go:141] libmachine: About to run SSH command:
date +%s.%N
I0408 19:23:23.302916 198268 main.go:141] libmachine: SSH cmd err, output: <nil>: 1744140203.270140486
I0408 19:23:23.302943 198268 fix.go:216] guest clock: 1744140203.270140486
I0408 19:23:23.302951 198268 fix.go:229] Guest: 2025-04-08 19:23:23.270140486 +0000 UTC Remote: 2025-04-08 19:23:23.184159141 +0000 UTC m=+28.738075788 (delta=85.981345ms)
I0408 19:23:23.302973 198268 fix.go:200] guest clock delta is within tolerance: 85.981345ms
I0408 19:23:23.302978 198268 start.go:83] releasing machines lock for "old-k8s-version-257500", held for 25.974551999s
I0408 19:23:23.303002 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .DriverName
I0408 19:23:23.303338 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetIP
I0408 19:23:23.306523 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:23.306927 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:00:35:99", ip: ""} in network mk-old-k8s-version-257500: {Iface:virbr1 ExpiryTime:2025-04-08 20:23:15 +0000 UTC Type:0 Mac:52:54:00:00:35:99 Iaid: IPaddr:192.168.39.192 Prefix:24 Hostname:old-k8s-version-257500 Clientid:01:52:54:00:00:35:99}
I0408 19:23:23.306960 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined IP address 192.168.39.192 and MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:23.307159 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .DriverName
I0408 19:23:23.307803 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .DriverName
I0408 19:23:23.307992 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .DriverName
I0408 19:23:23.308094 198268 ssh_runner.go:195] Run: curl -sS -m 2 https://registry.k8s.io/
I0408 19:23:23.308151 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHHostname
I0408 19:23:23.308302 198268 ssh_runner.go:195] Run: cat /version.json
I0408 19:23:23.308331 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHHostname
I0408 19:23:23.311045 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:23.311273 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:23.311448 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:00:35:99", ip: ""} in network mk-old-k8s-version-257500: {Iface:virbr1 ExpiryTime:2025-04-08 20:23:15 +0000 UTC Type:0 Mac:52:54:00:00:35:99 Iaid: IPaddr:192.168.39.192 Prefix:24 Hostname:old-k8s-version-257500 Clientid:01:52:54:00:00:35:99}
I0408 19:23:23.311480 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined IP address 192.168.39.192 and MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:23.311716 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHPort
I0408 19:23:23.311827 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:00:35:99", ip: ""} in network mk-old-k8s-version-257500: {Iface:virbr1 ExpiryTime:2025-04-08 20:23:15 +0000 UTC Type:0 Mac:52:54:00:00:35:99 Iaid: IPaddr:192.168.39.192 Prefix:24 Hostname:old-k8s-version-257500 Clientid:01:52:54:00:00:35:99}
I0408 19:23:23.311857 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined IP address 192.168.39.192 and MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:23.311885 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHKeyPath
I0408 19:23:23.312031 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHUsername
I0408 19:23:23.312155 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHPort
I0408 19:23:23.312232 198268 sshutil.go:53] new ssh client: &{IP:192.168.39.192 Port:22 SSHKeyPath:/home/jenkins/minikube-integration/20604-141129/.minikube/machines/old-k8s-version-257500/id_rsa Username:docker}
I0408 19:23:23.312331 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHKeyPath
I0408 19:23:23.312466 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetSSHUsername
I0408 19:23:23.312575 198268 sshutil.go:53] new ssh client: &{IP:192.168.39.192 Port:22 SSHKeyPath:/home/jenkins/minikube-integration/20604-141129/.minikube/machines/old-k8s-version-257500/id_rsa Username:docker}
I0408 19:23:23.427008 198268 ssh_runner.go:195] Run: systemctl --version
I0408 19:23:23.435398 198268 ssh_runner.go:195] Run: sudo sh -c "podman version >/dev/null"
I0408 19:23:23.603163 198268 ssh_runner.go:195] Run: sh -c "stat /etc/cni/net.d/*loopback.conf*"
W0408 19:23:23.610194 198268 cni.go:209] loopback cni configuration skipped: "/etc/cni/net.d/*loopback.conf*" not found
I0408 19:23:23.610287 198268 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" ;
I0408 19:23:23.630960 198268 cni.go:262] disabled [/etc/cni/net.d/87-podman-bridge.conflist] bridge cni config(s)
I0408 19:23:23.630992 198268 start.go:495] detecting cgroup driver to use...
I0408 19:23:23.631090 198268 ssh_runner.go:195] Run: sudo systemctl stop -f containerd
I0408 19:23:23.651120 198268 ssh_runner.go:195] Run: sudo systemctl is-active --quiet service containerd
I0408 19:23:23.673114 198268 docker.go:217] disabling cri-docker service (if available) ...
I0408 19:23:23.673206 198268 ssh_runner.go:195] Run: sudo systemctl stop -f cri-docker.socket
I0408 19:23:23.690310 198268 ssh_runner.go:195] Run: sudo systemctl stop -f cri-docker.service
I0408 19:23:23.705740 198268 ssh_runner.go:195] Run: sudo systemctl disable cri-docker.socket
I0408 19:23:23.838354 198268 ssh_runner.go:195] Run: sudo systemctl mask cri-docker.service
I0408 19:23:24.019183 198268 docker.go:233] disabling docker service ...
I0408 19:23:24.019280 198268 ssh_runner.go:195] Run: sudo systemctl stop -f docker.socket
I0408 19:23:24.037475 198268 ssh_runner.go:195] Run: sudo systemctl stop -f docker.service
I0408 19:23:24.052806 198268 ssh_runner.go:195] Run: sudo systemctl disable docker.socket
I0408 19:23:24.189727 198268 ssh_runner.go:195] Run: sudo systemctl mask docker.service
I0408 19:23:24.321405 198268 ssh_runner.go:195] Run: sudo systemctl is-active --quiet service docker
I0408 19:23:24.338042 198268 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"
I0408 19:23:24.359088 198268 crio.go:59] configure cri-o to use "registry.k8s.io/pause:3.2" pause image...
I0408 19:23:24.359172 198268 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"
I0408 19:23:24.370522 198268 crio.go:70] configuring cri-o to use "cgroupfs" as cgroup driver...
I0408 19:23:24.370589 198268 ssh_runner.go:195] Run: sh -c "sudo sed -i 's|^.*cgroup_manager = .*$|cgroup_manager = "cgroupfs"|' /etc/crio/crio.conf.d/02-crio.conf"
I0408 19:23:24.381615 198268 ssh_runner.go:195] Run: sh -c "sudo sed -i '/conmon_cgroup = .*/d' /etc/crio/crio.conf.d/02-crio.conf"
I0408 19:23:24.394160 198268 ssh_runner.go:195] Run: sh -c "sudo sed -i '/cgroup_manager = .*/a conmon_cgroup = "pod"' /etc/crio/crio.conf.d/02-crio.conf"
I0408 19:23:24.408189 198268 ssh_runner.go:195] Run: sh -c "sudo rm -rf /etc/cni/net.mk"
I0408 19:23:24.421533 198268 ssh_runner.go:195] Run: sudo sysctl net.bridge.bridge-nf-call-iptables
I0408 19:23:24.434496 198268 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
I0408 19:23:24.434574 198268 ssh_runner.go:195] Run: sudo modprobe br_netfilter
I0408 19:23:24.448630 198268 ssh_runner.go:195] Run: sudo sh -c "echo 1 > /proc/sys/net/ipv4/ip_forward"
I0408 19:23:24.460694 198268 ssh_runner.go:195] Run: sudo systemctl daemon-reload
I0408 19:23:24.607345 198268 ssh_runner.go:195] Run: sudo systemctl restart crio
I0408 19:23:24.715626 198268 start.go:542] Will wait 60s for socket path /var/run/crio/crio.sock
I0408 19:23:24.715724 198268 ssh_runner.go:195] Run: stat /var/run/crio/crio.sock
I0408 19:23:24.720702 198268 start.go:563] Will wait 60s for crictl version
I0408 19:23:24.720777 198268 ssh_runner.go:195] Run: which crictl
I0408 19:23:24.724856 198268 ssh_runner.go:195] Run: sudo /usr/bin/crictl version
I0408 19:23:24.774777 198268 start.go:579] Version: 0.1.0
RuntimeName: cri-o
RuntimeVersion: 1.29.1
RuntimeApiVersion: v1
I0408 19:23:24.774863 198268 ssh_runner.go:195] Run: crio --version
I0408 19:23:24.810759 198268 ssh_runner.go:195] Run: crio --version
I0408 19:23:24.846180 198268 out.go:177] * Preparing Kubernetes v1.20.0 on CRI-O 1.29.1 ...
I0408 19:23:24.847563 198268 main.go:141] libmachine: (old-k8s-version-257500) Calling .GetIP
I0408 19:23:24.851396 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:24.851771 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | found host DHCP lease matching {name: "", mac: "52:54:00:00:35:99", ip: ""} in network mk-old-k8s-version-257500: {Iface:virbr1 ExpiryTime:2025-04-08 20:23:15 +0000 UTC Type:0 Mac:52:54:00:00:35:99 Iaid: IPaddr:192.168.39.192 Prefix:24 Hostname:old-k8s-version-257500 Clientid:01:52:54:00:00:35:99}
I0408 19:23:24.851812 198268 main.go:141] libmachine: (old-k8s-version-257500) DBG | domain old-k8s-version-257500 has defined IP address 192.168.39.192 and MAC address 52:54:00:00:35:99 in network mk-old-k8s-version-257500
I0408 19:23:24.852130 198268 ssh_runner.go:195] Run: grep 192.168.39.1 host.minikube.internal$ /etc/hosts
I0408 19:23:24.856407 198268 ssh_runner.go:195] Run: /bin/bash -c "{ grep -v $'\thost.minikube.internal$' "/etc/hosts"; echo "192.168.39.1 host.minikube.internal"; } > /tmp/h.$$; sudo cp /tmp/h.$$ "/etc/hosts""
I0408 19:23:24.869143 198268 kubeadm.go:883] updating cluster {Name:old-k8s-version-257500 KeepContext:false EmbedCerts:false MinikubeISO:https://storage.googleapis.com/minikube/iso/minikube-v1.35.0-amd64.iso KicBaseImage:gcr.io/k8s-minikube/kicbase-builds:v0.0.46-1744107393-20604@sha256:2430533582a8c08f907b2d5976c79bd2e672b4f3d4484088c99b839f3175ed6a 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-257500 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.39.192 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 MountU
ID:docker BinaryMirror: DisableOptimizations:false DisableMetrics:false CustomQemuFirmwarePath: SocketVMnetClientPath: SocketVMnetPath: StaticIP: SSHAuthSock: SSHAgentPID:0 GPUs: AutoPauseInterval:1m0s} ...
I0408 19:23:24.869282 198268 preload.go:131] Checking if preload exists for k8s version v1.20.0 and runtime crio
I0408 19:23:24.869419 198268 ssh_runner.go:195] Run: sudo crictl images --output json
I0408 19:23:24.905724 198268 crio.go:510] couldn't find preloaded image for "registry.k8s.io/kube-apiserver:v1.20.0". assuming images are not preloaded.
I0408 19:23:24.905809 198268 ssh_runner.go:195] Run: which lz4
I0408 19:23:24.911444 198268 ssh_runner.go:195] Run: stat -c "%s %y" /preloaded.tar.lz4
I0408 19:23:24.916094 198268 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
I0408 19:23:24.916132 198268 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20604-141129/.minikube/cache/preloaded-tarball/preloaded-images-k8s-v18-v1.20.0-cri-o-overlay-amd64.tar.lz4 --> /preloaded.tar.lz4 (473237281 bytes)
I0408 19:23:26.526560 198268 crio.go:462] duration metric: took 1.615148878s to copy over tarball
I0408 19:23:26.526639 198268 ssh_runner.go:195] Run: sudo tar --xattrs --xattrs-include security.capability -I lz4 -C /var -xf /preloaded.tar.lz4
I0408 19:23:29.552291 198268 ssh_runner.go:235] Completed: sudo tar --xattrs --xattrs-include security.capability -I lz4 -C /var -xf /preloaded.tar.lz4: (3.025617318s)
I0408 19:23:29.552328 198268 crio.go:469] duration metric: took 3.025732532s to extract the tarball
I0408 19:23:29.552350 198268 ssh_runner.go:146] rm: /preloaded.tar.lz4
I0408 19:23:29.597563 198268 ssh_runner.go:195] Run: sudo crictl images --output json
I0408 19:23:29.660613 198268 crio.go:510] couldn't find preloaded image for "registry.k8s.io/kube-apiserver:v1.20.0". assuming images are not preloaded.
I0408 19:23:29.660658 198268 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]
I0408 19:23:29.660758 198268 image.go:135] retrieving image: gcr.io/k8s-minikube/storage-provisioner:v5
I0408 19:23:29.660835 198268 image.go:135] retrieving image: registry.k8s.io/kube-proxy:v1.20.0
I0408 19:23:29.660868 198268 image.go:135] retrieving image: registry.k8s.io/pause:3.2
I0408 19:23:29.660926 198268 image.go:135] retrieving image: registry.k8s.io/coredns:1.7.0
I0408 19:23:29.661135 198268 image.go:135] retrieving image: registry.k8s.io/kube-scheduler:v1.20.0
I0408 19:23:29.660845 198268 image.go:135] retrieving image: registry.k8s.io/etcd:3.4.13-0
I0408 19:23:29.661198 198268 image.go:135] retrieving image: registry.k8s.io/kube-controller-manager:v1.20.0
I0408 19:23:29.661364 198268 image.go:135] retrieving image: registry.k8s.io/kube-apiserver:v1.20.0
I0408 19:23:29.663247 198268 image.go:178] daemon lookup for gcr.io/k8s-minikube/storage-provisioner:v5: Error response from daemon: No such image: gcr.io/k8s-minikube/storage-provisioner:v5
I0408 19:23:29.663342 198268 image.go:178] daemon lookup for registry.k8s.io/pause:3.2: Error response from daemon: No such image: registry.k8s.io/pause:3.2
I0408 19:23:29.663388 198268 image.go:178] daemon lookup for registry.k8s.io/kube-scheduler:v1.20.0: Error response from daemon: No such image: registry.k8s.io/kube-scheduler:v1.20.0
I0408 19:23:29.663446 198268 image.go:178] daemon lookup for registry.k8s.io/coredns:1.7.0: Error response from daemon: No such image: registry.k8s.io/coredns:1.7.0
I0408 19:23:29.663519 198268 image.go:178] daemon lookup for registry.k8s.io/etcd:3.4.13-0: Error response from daemon: No such image: registry.k8s.io/etcd:3.4.13-0
I0408 19:23:29.663248 198268 image.go:178] daemon lookup for registry.k8s.io/kube-apiserver:v1.20.0: Error response from daemon: No such image: registry.k8s.io/kube-apiserver:v1.20.0
I0408 19:23:29.663622 198268 image.go:178] daemon lookup for registry.k8s.io/kube-controller-manager:v1.20.0: Error response from daemon: No such image: registry.k8s.io/kube-controller-manager:v1.20.0
I0408 19:23:29.663638 198268 image.go:178] daemon lookup for registry.k8s.io/kube-proxy:v1.20.0: Error response from daemon: No such image: registry.k8s.io/kube-proxy:v1.20.0
I0408 19:23:29.820807 198268 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} registry.k8s.io/kube-scheduler:v1.20.0
I0408 19:23:29.823138 198268 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} registry.k8s.io/coredns:1.7.0
I0408 19:23:29.829431 198268 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} registry.k8s.io/etcd:3.4.13-0
I0408 19:23:29.831173 198268 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} registry.k8s.io/kube-controller-manager:v1.20.0
I0408 19:23:29.837494 198268 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} registry.k8s.io/kube-apiserver:v1.20.0
I0408 19:23:29.842532 198268 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} registry.k8s.io/kube-proxy:v1.20.0
I0408 19:23:29.868870 198268 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} registry.k8s.io/pause:3.2
I0408 19:23:29.993745 198268 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
I0408 19:23:29.993816 198268 cri.go:218] Removing image: registry.k8s.io/kube-scheduler:v1.20.0
I0408 19:23:29.993890 198268 ssh_runner.go:195] Run: which crictl
I0408 19:23:30.037859 198268 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
I0408 19:23:30.037927 198268 cri.go:218] Removing image: registry.k8s.io/coredns:1.7.0
I0408 19:23:30.037981 198268 ssh_runner.go:195] Run: which crictl
I0408 19:23:30.078324 198268 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
I0408 19:23:30.078380 198268 cri.go:218] Removing image: registry.k8s.io/etcd:3.4.13-0
I0408 19:23:30.078441 198268 ssh_runner.go:195] Run: which crictl
I0408 19:23:30.085441 198268 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
I0408 19:23:30.085509 198268 cri.go:218] Removing image: registry.k8s.io/kube-controller-manager:v1.20.0
I0408 19:23:30.085537 198268 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
I0408 19:23:30.085607 198268 cri.go:218] Removing image: registry.k8s.io/kube-apiserver:v1.20.0
I0408 19:23:30.085563 198268 ssh_runner.go:195] Run: which crictl
I0408 19:23:30.085664 198268 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
I0408 19:23:30.085715 198268 cri.go:218] Removing image: registry.k8s.io/kube-proxy:v1.20.0
I0408 19:23:30.085667 198268 ssh_runner.go:195] Run: which crictl
I0408 19:23:30.085756 198268 ssh_runner.go:195] Run: which crictl
I0408 19:23:30.101573 198268 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-scheduler:v1.20.0
I0408 19:23:30.101657 198268 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/coredns:1.7.0
I0408 19:23:30.101708 198268 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-proxy:v1.20.0
I0408 19:23:30.101666 198268 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/etcd:3.4.13-0
I0408 19:23:30.101772 198268 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-apiserver:v1.20.0
I0408 19:23:30.101775 198268 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-controller-manager:v1.20.0
I0408 19:23:30.101952 198268 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
I0408 19:23:30.102000 198268 cri.go:218] Removing image: registry.k8s.io/pause:3.2
I0408 19:23:30.102040 198268 ssh_runner.go:195] Run: which crictl
I0408 19:23:30.243533 198268 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/pause:3.2
I0408 19:23:30.243700 198268 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-proxy:v1.20.0
I0408 19:23:30.244011 198268 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/coredns:1.7.0
I0408 19:23:30.256788 198268 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-apiserver:v1.20.0
I0408 19:23:30.256840 198268 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-scheduler:v1.20.0
I0408 19:23:30.256842 198268 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-controller-manager:v1.20.0
I0408 19:23:30.256909 198268 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/etcd:3.4.13-0
I0408 19:23:30.396800 198268 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/pause:3.2
I0408 19:23:30.396856 198268 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-proxy:v1.20.0
I0408 19:23:30.396890 198268 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/coredns:1.7.0
I0408 19:23:30.400137 198268 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-controller-manager:v1.20.0
I0408 19:23:30.400178 198268 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-apiserver:v1.20.0
I0408 19:23:30.418748 198268 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/kube-scheduler:v1.20.0
I0408 19:23:30.418862 198268 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/etcd:3.4.13-0
I0408 19:23:30.572667 198268 cache_images.go:289] Loading image from: /home/jenkins/minikube-integration/20604-141129/.minikube/cache/images/amd64/registry.k8s.io/coredns_1.7.0
I0408 19:23:30.572740 198268 ssh_runner.go:195] Run: sudo /usr/bin/crictl rmi registry.k8s.io/pause:3.2
I0408 19:23:30.572760 198268 cache_images.go:289] Loading image from: /home/jenkins/minikube-integration/20604-141129/.minikube/cache/images/amd64/registry.k8s.io/kube-proxy_v1.20.0
I0408 19:23:30.572767 198268 cache_images.go:289] Loading image from: /home/jenkins/minikube-integration/20604-141129/.minikube/cache/images/amd64/registry.k8s.io/kube-controller-manager_v1.20.0
I0408 19:23:30.572852 198268 cache_images.go:289] Loading image from: /home/jenkins/minikube-integration/20604-141129/.minikube/cache/images/amd64/registry.k8s.io/kube-apiserver_v1.20.0
I0408 19:23:30.578788 198268 cache_images.go:289] Loading image from: /home/jenkins/minikube-integration/20604-141129/.minikube/cache/images/amd64/registry.k8s.io/kube-scheduler_v1.20.0
I0408 19:23:30.582283 198268 cache_images.go:289] Loading image from: /home/jenkins/minikube-integration/20604-141129/.minikube/cache/images/amd64/registry.k8s.io/etcd_3.4.13-0
I0408 19:23:30.616477 198268 cache_images.go:289] Loading image from: /home/jenkins/minikube-integration/20604-141129/.minikube/cache/images/amd64/registry.k8s.io/pause_3.2
I0408 19:23:31.200126 198268 ssh_runner.go:195] Run: sudo podman image inspect --format {{.Id}} gcr.io/k8s-minikube/storage-provisioner:v5
I0408 19:23:31.344888 198268 cache_images.go:92] duration metric: took 1.684207564s to LoadCachedImages
W0408 19:23:31.345001 198268 out.go:270] X Unable to load cached images: LoadCachedImages: stat /home/jenkins/minikube-integration/20604-141129/.minikube/cache/images/amd64/registry.k8s.io/coredns_1.7.0: no such file or directory
X Unable to load cached images: LoadCachedImages: stat /home/jenkins/minikube-integration/20604-141129/.minikube/cache/images/amd64/registry.k8s.io/coredns_1.7.0: no such file or directory
I0408 19:23:31.345062 198268 kubeadm.go:934] updating node { 192.168.39.192 8443 v1.20.0 crio true true} ...
I0408 19:23:31.345194 198268 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-257500 --kubeconfig=/etc/kubernetes/kubelet.conf --network-plugin=cni --node-ip=192.168.39.192
[Install]
config:
{KubernetesVersion:v1.20.0 ClusterName:old-k8s-version-257500 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:}
I0408 19:23:31.345273 198268 ssh_runner.go:195] Run: crio config
I0408 19:23:31.392266 198268 cni.go:84] Creating CNI manager for ""
I0408 19:23:31.392291 198268 cni.go:146] "kvm2" driver + "crio" runtime found, recommending bridge
I0408 19:23:31.392303 198268 kubeadm.go:84] Using pod CIDR: 10.244.0.0/16
I0408 19:23:31.392323 198268 kubeadm.go:189] kubeadm options: {CertDir:/var/lib/minikube/certs ServiceCIDR:10.96.0.0/12 PodSubnet:10.244.0.0/16 AdvertiseAddress:192.168.39.192 APIServerPort:8443 KubernetesVersion:v1.20.0 EtcdDataDir:/var/lib/minikube/etcd EtcdExtraArgs:map[] ClusterName:old-k8s-version-257500 NodeName:old-k8s-version-257500 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.39.192"]]} {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.39.192 CgroupDriver:cgroupfs ClientCAFile:/var/lib/minikube/certs/ca.crt St
aticPodPath:/etc/kubernetes/manifests ControlPlaneAddress:control-plane.minikube.internal KubeProxyOptions:map[] ResolvConfSearchRegression:false KubeletConfigOpts:map[hairpinMode:hairpin-veth runtimeRequestTimeout:15m] PrependCriSocketUnix:false}
I0408 19:23:31.392444 198268 kubeadm.go:195] kubeadm config:
apiVersion: kubeadm.k8s.io/v1beta2
kind: InitConfiguration
localAPIEndpoint:
advertiseAddress: 192.168.39.192
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-257500"
kubeletExtraArgs:
node-ip: 192.168.39.192
taints: []
---
apiVersion: kubeadm.k8s.io/v1beta2
kind: ClusterConfiguration
apiServer:
certSANs: ["127.0.0.1", "localhost", "192.168.39.192"]
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
I0408 19:23:31.392512 198268 ssh_runner.go:195] Run: sudo ls /var/lib/minikube/binaries/v1.20.0
I0408 19:23:31.403913 198268 binaries.go:44] Found k8s binaries, skipping transfer
I0408 19:23:31.404003 198268 ssh_runner.go:195] Run: sudo mkdir -p /etc/systemd/system/kubelet.service.d /lib/systemd/system /var/tmp/minikube
I0408 19:23:31.416163 198268 ssh_runner.go:362] scp memory --> /etc/systemd/system/kubelet.service.d/10-kubeadm.conf (430 bytes)
I0408 19:23:31.435133 198268 ssh_runner.go:362] scp memory --> /lib/systemd/system/kubelet.service (352 bytes)
I0408 19:23:31.454898 198268 ssh_runner.go:362] scp memory --> /var/tmp/minikube/kubeadm.yaml.new (2123 bytes)
I0408 19:23:31.474208 198268 ssh_runner.go:195] Run: grep 192.168.39.192 control-plane.minikube.internal$ /etc/hosts
I0408 19:23:31.478567 198268 ssh_runner.go:195] Run: /bin/bash -c "{ grep -v $'\tcontrol-plane.minikube.internal$' "/etc/hosts"; echo "192.168.39.192 control-plane.minikube.internal"; } > /tmp/h.$$; sudo cp /tmp/h.$$ "/etc/hosts""
I0408 19:23:31.492473 198268 ssh_runner.go:195] Run: sudo systemctl daemon-reload
I0408 19:23:31.630774 198268 ssh_runner.go:195] Run: sudo systemctl start kubelet
I0408 19:23:31.649621 198268 certs.go:68] Setting up /home/jenkins/minikube-integration/20604-141129/.minikube/profiles/old-k8s-version-257500 for IP: 192.168.39.192
I0408 19:23:31.649653 198268 certs.go:194] generating shared ca certs ...
I0408 19:23:31.649677 198268 certs.go:226] acquiring lock for ca certs: {Name:mkd37ce74a5e6f5f5300314397402f7d571fc230 Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0408 19:23:31.649919 198268 certs.go:235] skipping valid "minikubeCA" ca cert: /home/jenkins/minikube-integration/20604-141129/.minikube/ca.key
I0408 19:23:31.650002 198268 certs.go:235] skipping valid "proxyClientCA" ca cert: /home/jenkins/minikube-integration/20604-141129/.minikube/proxy-client-ca.key
I0408 19:23:31.650020 198268 certs.go:256] generating profile certs ...
I0408 19:23:31.650106 198268 certs.go:363] generating signed profile cert for "minikube-user": /home/jenkins/minikube-integration/20604-141129/.minikube/profiles/old-k8s-version-257500/client.key
I0408 19:23:31.650143 198268 crypto.go:68] Generating cert /home/jenkins/minikube-integration/20604-141129/.minikube/profiles/old-k8s-version-257500/client.crt with IP's: []
I0408 19:23:31.806158 198268 crypto.go:156] Writing cert to /home/jenkins/minikube-integration/20604-141129/.minikube/profiles/old-k8s-version-257500/client.crt ...
I0408 19:23:31.806197 198268 lock.go:35] WriteFile acquiring /home/jenkins/minikube-integration/20604-141129/.minikube/profiles/old-k8s-version-257500/client.crt: {Name:mk45d755b04d80cedc15880e1b9f2e2228a8675a Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0408 19:23:31.806442 198268 crypto.go:164] Writing key to /home/jenkins/minikube-integration/20604-141129/.minikube/profiles/old-k8s-version-257500/client.key ...
I0408 19:23:31.806466 198268 lock.go:35] WriteFile acquiring /home/jenkins/minikube-integration/20604-141129/.minikube/profiles/old-k8s-version-257500/client.key: {Name:mkd5bbc1876de7ec95b0872c873e7cfd11033ac2 Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0408 19:23:31.806563 198268 certs.go:363] generating signed profile cert for "minikube": /home/jenkins/minikube-integration/20604-141129/.minikube/profiles/old-k8s-version-257500/apiserver.key.31857a68
I0408 19:23:31.806579 198268 crypto.go:68] Generating cert /home/jenkins/minikube-integration/20604-141129/.minikube/profiles/old-k8s-version-257500/apiserver.crt.31857a68 with IP's: [10.96.0.1 127.0.0.1 10.0.0.1 192.168.39.192]
I0408 19:23:31.855748 198268 crypto.go:156] Writing cert to /home/jenkins/minikube-integration/20604-141129/.minikube/profiles/old-k8s-version-257500/apiserver.crt.31857a68 ...
I0408 19:23:31.855785 198268 lock.go:35] WriteFile acquiring /home/jenkins/minikube-integration/20604-141129/.minikube/profiles/old-k8s-version-257500/apiserver.crt.31857a68: {Name:mk18ddd6b97f730b997a9f6f77ba1476fa33d0d2 Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0408 19:23:31.915942 198268 crypto.go:164] Writing key to /home/jenkins/minikube-integration/20604-141129/.minikube/profiles/old-k8s-version-257500/apiserver.key.31857a68 ...
I0408 19:23:31.915997 198268 lock.go:35] WriteFile acquiring /home/jenkins/minikube-integration/20604-141129/.minikube/profiles/old-k8s-version-257500/apiserver.key.31857a68: {Name:mk07bfe97f9ed0efbc4a928d924c9911ba0d2072 Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0408 19:23:31.916169 198268 certs.go:381] copying /home/jenkins/minikube-integration/20604-141129/.minikube/profiles/old-k8s-version-257500/apiserver.crt.31857a68 -> /home/jenkins/minikube-integration/20604-141129/.minikube/profiles/old-k8s-version-257500/apiserver.crt
I0408 19:23:31.916290 198268 certs.go:385] copying /home/jenkins/minikube-integration/20604-141129/.minikube/profiles/old-k8s-version-257500/apiserver.key.31857a68 -> /home/jenkins/minikube-integration/20604-141129/.minikube/profiles/old-k8s-version-257500/apiserver.key
I0408 19:23:31.916377 198268 certs.go:363] generating signed profile cert for "aggregator": /home/jenkins/minikube-integration/20604-141129/.minikube/profiles/old-k8s-version-257500/proxy-client.key
I0408 19:23:31.916403 198268 crypto.go:68] Generating cert /home/jenkins/minikube-integration/20604-141129/.minikube/profiles/old-k8s-version-257500/proxy-client.crt with IP's: []
I0408 19:23:31.997341 198268 crypto.go:156] Writing cert to /home/jenkins/minikube-integration/20604-141129/.minikube/profiles/old-k8s-version-257500/proxy-client.crt ...
I0408 19:23:31.997376 198268 lock.go:35] WriteFile acquiring /home/jenkins/minikube-integration/20604-141129/.minikube/profiles/old-k8s-version-257500/proxy-client.crt: {Name:mk45e17f8e69f045f8390f6daf440be261ae351a Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0408 19:23:31.997583 198268 crypto.go:164] Writing key to /home/jenkins/minikube-integration/20604-141129/.minikube/profiles/old-k8s-version-257500/proxy-client.key ...
I0408 19:23:31.997603 198268 lock.go:35] WriteFile acquiring /home/jenkins/minikube-integration/20604-141129/.minikube/profiles/old-k8s-version-257500/proxy-client.key: {Name:mk8067dd56dc5132b5490374f5c956c6ac16b3be Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0408 19:23:31.997828 198268 certs.go:484] found cert: /home/jenkins/minikube-integration/20604-141129/.minikube/certs/148487.pem (1338 bytes)
W0408 19:23:31.997920 198268 certs.go:480] ignoring /home/jenkins/minikube-integration/20604-141129/.minikube/certs/148487_empty.pem, impossibly tiny 0 bytes
I0408 19:23:31.997973 198268 certs.go:484] found cert: /home/jenkins/minikube-integration/20604-141129/.minikube/certs/ca-key.pem (1675 bytes)
I0408 19:23:31.998007 198268 certs.go:484] found cert: /home/jenkins/minikube-integration/20604-141129/.minikube/certs/ca.pem (1082 bytes)
I0408 19:23:31.998041 198268 certs.go:484] found cert: /home/jenkins/minikube-integration/20604-141129/.minikube/certs/cert.pem (1123 bytes)
I0408 19:23:31.998073 198268 certs.go:484] found cert: /home/jenkins/minikube-integration/20604-141129/.minikube/certs/key.pem (1679 bytes)
I0408 19:23:31.998136 198268 certs.go:484] found cert: /home/jenkins/minikube-integration/20604-141129/.minikube/files/etc/ssl/certs/1484872.pem (1708 bytes)
I0408 19:23:31.998705 198268 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20604-141129/.minikube/ca.crt --> /var/lib/minikube/certs/ca.crt (1111 bytes)
I0408 19:23:32.026121 198268 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20604-141129/.minikube/ca.key --> /var/lib/minikube/certs/ca.key (1679 bytes)
I0408 19:23:32.053644 198268 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20604-141129/.minikube/proxy-client-ca.crt --> /var/lib/minikube/certs/proxy-client-ca.crt (1119 bytes)
I0408 19:23:32.081631 198268 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20604-141129/.minikube/proxy-client-ca.key --> /var/lib/minikube/certs/proxy-client-ca.key (1675 bytes)
I0408 19:23:32.110132 198268 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20604-141129/.minikube/profiles/old-k8s-version-257500/apiserver.crt --> /var/lib/minikube/certs/apiserver.crt (1432 bytes)
I0408 19:23:32.139641 198268 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20604-141129/.minikube/profiles/old-k8s-version-257500/apiserver.key --> /var/lib/minikube/certs/apiserver.key (1675 bytes)
I0408 19:23:32.168328 198268 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20604-141129/.minikube/profiles/old-k8s-version-257500/proxy-client.crt --> /var/lib/minikube/certs/proxy-client.crt (1147 bytes)
I0408 19:23:32.195832 198268 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20604-141129/.minikube/profiles/old-k8s-version-257500/proxy-client.key --> /var/lib/minikube/certs/proxy-client.key (1675 bytes)
I0408 19:23:32.235708 198268 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20604-141129/.minikube/files/etc/ssl/certs/1484872.pem --> /usr/share/ca-certificates/1484872.pem (1708 bytes)
I0408 19:23:32.265767 198268 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20604-141129/.minikube/ca.crt --> /usr/share/ca-certificates/minikubeCA.pem (1111 bytes)
I0408 19:23:32.298869 198268 ssh_runner.go:362] scp /home/jenkins/minikube-integration/20604-141129/.minikube/certs/148487.pem --> /usr/share/ca-certificates/148487.pem (1338 bytes)
I0408 19:23:32.330536 198268 ssh_runner.go:362] scp memory --> /var/lib/minikube/kubeconfig (738 bytes)
I0408 19:23:32.352749 198268 ssh_runner.go:195] Run: openssl version
I0408 19:23:32.359702 198268 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"
I0408 19:23:32.373414 198268 ssh_runner.go:195] Run: ls -la /usr/share/ca-certificates/minikubeCA.pem
I0408 19:23:32.378932 198268 certs.go:528] hashing: -rw-r--r-- 1 root root 1111 Apr 8 18:13 /usr/share/ca-certificates/minikubeCA.pem
I0408 19:23:32.379022 198268 ssh_runner.go:195] Run: openssl x509 -hash -noout -in /usr/share/ca-certificates/minikubeCA.pem
I0408 19:23:32.386112 198268 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"
I0408 19:23:32.399099 198268 ssh_runner.go:195] Run: sudo /bin/bash -c "test -s /usr/share/ca-certificates/148487.pem && ln -fs /usr/share/ca-certificates/148487.pem /etc/ssl/certs/148487.pem"
I0408 19:23:32.413296 198268 ssh_runner.go:195] Run: ls -la /usr/share/ca-certificates/148487.pem
I0408 19:23:32.419161 198268 certs.go:528] hashing: -rw-r--r-- 1 root root 1338 Apr 8 18:21 /usr/share/ca-certificates/148487.pem
I0408 19:23:32.419344 198268 ssh_runner.go:195] Run: openssl x509 -hash -noout -in /usr/share/ca-certificates/148487.pem
I0408 19:23:32.426596 198268 ssh_runner.go:195] Run: sudo /bin/bash -c "test -L /etc/ssl/certs/51391683.0 || ln -fs /etc/ssl/certs/148487.pem /etc/ssl/certs/51391683.0"
I0408 19:23:32.440855 198268 ssh_runner.go:195] Run: sudo /bin/bash -c "test -s /usr/share/ca-certificates/1484872.pem && ln -fs /usr/share/ca-certificates/1484872.pem /etc/ssl/certs/1484872.pem"
I0408 19:23:32.454836 198268 ssh_runner.go:195] Run: ls -la /usr/share/ca-certificates/1484872.pem
I0408 19:23:32.460898 198268 certs.go:528] hashing: -rw-r--r-- 1 root root 1708 Apr 8 18:21 /usr/share/ca-certificates/1484872.pem
I0408 19:23:32.460999 198268 ssh_runner.go:195] Run: openssl x509 -hash -noout -in /usr/share/ca-certificates/1484872.pem
I0408 19:23:32.467879 198268 ssh_runner.go:195] Run: sudo /bin/bash -c "test -L /etc/ssl/certs/3ec20f2e.0 || ln -fs /etc/ssl/certs/1484872.pem /etc/ssl/certs/3ec20f2e.0"
I0408 19:23:32.481823 198268 ssh_runner.go:195] Run: stat /var/lib/minikube/certs/apiserver-kubelet-client.crt
I0408 19:23:32.495716 198268 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
I0408 19:23:32.495796 198268 kubeadm.go:392] StartCluster: {Name:old-k8s-version-257500 KeepContext:false EmbedCerts:false MinikubeISO:https://storage.googleapis.com/minikube/iso/minikube-v1.35.0-amd64.iso KicBaseImage:gcr.io/k8s-minikube/kicbase-builds:v0.0.46-1744107393-20604@sha256:2430533582a8c08f907b2d5976c79bd2e672b4f3d4484088c99b839f3175ed6a Memory:2200 CPUs:2 DiskSize:20000 Driver:kvm2 HyperkitVpnKitSock: HyperkitVSockPorts:[] DockerEnv:[] ContainerVolumeMounts:[] InsecureRegistry:[] RegistryMirror:[] HostOnlyCIDR:192.168.59.1/24 HypervVirtualSwitch: HypervUseExternalSwitch:false HypervExternalAdapter: KVMNetwork:default KVMQemuURI:qemu:///system KVMGPU:false KVMHidden:false KVMNUMACount:1 APIServerPort:8443 DockerOpt:[] DisableDriverMounts:true NFSShare:[] NFSSharesRoot:/nfsshares UUID: NoVTXCheck:false DNSProxy:false HostDNSResolver:true HostOnlyNicType:virtio NatNicType:virtio SSHIPAddress: SSHUser:root SSHKey: SSHPort:22 KubernetesConfig:{KubernetesVersion:v1.20.0 ClusterName:old-k8s-ver
sion-257500 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.39.192 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}
I0408 19:23:32.495899 198268 cri.go:54] listing CRI containers in root : {State:paused Name: Namespaces:[kube-system]}
I0408 19:23:32.495974 198268 ssh_runner.go:195] Run: sudo -s eval "crictl ps -a --quiet --label io.kubernetes.pod.namespace=kube-system"
I0408 19:23:32.553680 198268 cri.go:89] found id: ""
I0408 19:23:32.553769 198268 ssh_runner.go:195] Run: sudo ls /var/lib/kubelet/kubeadm-flags.env /var/lib/kubelet/config.yaml /var/lib/minikube/etcd
I0408 19:23:32.569007 198268 ssh_runner.go:195] Run: sudo cp /var/tmp/minikube/kubeadm.yaml.new /var/tmp/minikube/kubeadm.yaml
I0408 19:23:32.595043 198268 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
I0408 19:23:32.612386 198268 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
I0408 19:23:32.612416 198268 kubeadm.go:157] found existing configuration files:
I0408 19:23:32.612496 198268 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/admin.conf
I0408 19:23:32.626178 198268 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
I0408 19:23:32.626263 198268 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/admin.conf
I0408 19:23:32.639861 198268 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/kubelet.conf
I0408 19:23:32.653888 198268 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
I0408 19:23:32.653980 198268 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/kubelet.conf
I0408 19:23:32.668055 198268 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/controller-manager.conf
I0408 19:23:32.681469 198268 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
I0408 19:23:32.681565 198268 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/controller-manager.conf
I0408 19:23:32.692056 198268 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/scheduler.conf
I0408 19:23:32.703438 198268 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
I0408 19:23:32.703521 198268 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/scheduler.conf
I0408 19:23:32.714732 198268 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"
I0408 19:23:32.855799 198268 kubeadm.go:310] [init] Using Kubernetes version: v1.20.0
I0408 19:23:32.855922 198268 kubeadm.go:310] [preflight] Running pre-flight checks
I0408 19:23:33.012405 198268 kubeadm.go:310] [preflight] Pulling images required for setting up a Kubernetes cluster
I0408 19:23:33.012614 198268 kubeadm.go:310] [preflight] This might take a minute or two, depending on the speed of your internet connection
I0408 19:23:33.012795 198268 kubeadm.go:310] [preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
I0408 19:23:33.203729 198268 kubeadm.go:310] [certs] Using certificateDir folder "/var/lib/minikube/certs"
I0408 19:23:33.243479 198268 out.go:235] - Generating certificates and keys ...
I0408 19:23:33.243635 198268 kubeadm.go:310] [certs] Using existing ca certificate authority
I0408 19:23:33.243734 198268 kubeadm.go:310] [certs] Using existing apiserver certificate and key on disk
I0408 19:23:33.298939 198268 kubeadm.go:310] [certs] Generating "apiserver-kubelet-client" certificate and key
I0408 19:23:33.516332 198268 kubeadm.go:310] [certs] Generating "front-proxy-ca" certificate and key
I0408 19:23:33.713926 198268 kubeadm.go:310] [certs] Generating "front-proxy-client" certificate and key
I0408 19:23:33.831222 198268 kubeadm.go:310] [certs] Generating "etcd/ca" certificate and key
I0408 19:23:34.075445 198268 kubeadm.go:310] [certs] Generating "etcd/server" certificate and key
I0408 19:23:34.075747 198268 kubeadm.go:310] [certs] etcd/server serving cert is signed for DNS names [localhost old-k8s-version-257500] and IPs [192.168.39.192 127.0.0.1 ::1]
I0408 19:23:34.189108 198268 kubeadm.go:310] [certs] Generating "etcd/peer" certificate and key
I0408 19:23:34.189518 198268 kubeadm.go:310] [certs] etcd/peer serving cert is signed for DNS names [localhost old-k8s-version-257500] and IPs [192.168.39.192 127.0.0.1 ::1]
I0408 19:23:34.288792 198268 kubeadm.go:310] [certs] Generating "etcd/healthcheck-client" certificate and key
I0408 19:23:34.521228 198268 kubeadm.go:310] [certs] Generating "apiserver-etcd-client" certificate and key
I0408 19:23:34.650768 198268 kubeadm.go:310] [certs] Generating "sa" key and public key
I0408 19:23:34.651037 198268 kubeadm.go:310] [kubeconfig] Using kubeconfig folder "/etc/kubernetes"
I0408 19:23:35.027371 198268 kubeadm.go:310] [kubeconfig] Writing "admin.conf" kubeconfig file
I0408 19:23:35.393159 198268 kubeadm.go:310] [kubeconfig] Writing "kubelet.conf" kubeconfig file
I0408 19:23:35.532438 198268 kubeadm.go:310] [kubeconfig] Writing "controller-manager.conf" kubeconfig file
I0408 19:23:35.867864 198268 kubeadm.go:310] [kubeconfig] Writing "scheduler.conf" kubeconfig file
I0408 19:23:35.886846 198268 kubeadm.go:310] [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
I0408 19:23:35.888411 198268 kubeadm.go:310] [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
I0408 19:23:35.888476 198268 kubeadm.go:310] [kubelet-start] Starting the kubelet
I0408 19:23:36.075511 198268 kubeadm.go:310] [control-plane] Using manifest folder "/etc/kubernetes/manifests"
I0408 19:23:36.077026 198268 out.go:235] - Booting up control plane ...
I0408 19:23:36.077181 198268 kubeadm.go:310] [control-plane] Creating static Pod manifest for "kube-apiserver"
I0408 19:23:36.088640 198268 kubeadm.go:310] [control-plane] Creating static Pod manifest for "kube-controller-manager"
I0408 19:23:36.088785 198268 kubeadm.go:310] [control-plane] Creating static Pod manifest for "kube-scheduler"
I0408 19:23:36.091643 198268 kubeadm.go:310] [etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
I0408 19:23:36.096978 198268 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
I0408 19:24:16.087492 198268 kubeadm.go:310] [kubelet-check] Initial timeout of 40s passed.
I0408 19:24:16.088782 198268 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0408 19:24:16.089059 198268 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.
I0408 19:24:21.089265 198268 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0408 19:24:21.089558 198268 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.
I0408 19:24:31.088668 198268 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0408 19:24:31.088875 198268 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.
I0408 19:24:51.088156 198268 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0408 19:24:51.088439 198268 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.
I0408 19:25:31.088832 198268 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0408 19:25:31.089066 198268 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.
I0408 19:25:31.089094 198268 kubeadm.go:310]
I0408 19:25:31.089146 198268 kubeadm.go:310] Unfortunately, an error has occurred:
I0408 19:25:31.089240 198268 kubeadm.go:310] timed out waiting for the condition
I0408 19:25:31.089257 198268 kubeadm.go:310]
I0408 19:25:31.089306 198268 kubeadm.go:310] This error is likely caused by:
I0408 19:25:31.089368 198268 kubeadm.go:310] - The kubelet is not running
I0408 19:25:31.089474 198268 kubeadm.go:310] - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
I0408 19:25:31.089482 198268 kubeadm.go:310]
I0408 19:25:31.089608 198268 kubeadm.go:310] If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
I0408 19:25:31.089657 198268 kubeadm.go:310] - 'systemctl status kubelet'
I0408 19:25:31.089706 198268 kubeadm.go:310] - 'journalctl -xeu kubelet'
I0408 19:25:31.089721 198268 kubeadm.go:310]
I0408 19:25:31.089879 198268 kubeadm.go:310] Additionally, a control plane component may have crashed or exited when started by the container runtime.
I0408 19:25:31.089967 198268 kubeadm.go:310] To troubleshoot, list all containers using your preferred container runtimes CLI.
I0408 19:25:31.089975 198268 kubeadm.go:310]
I0408 19:25:31.090061 198268 kubeadm.go:310] Here is one example how you may list all Kubernetes containers running in cri-o/containerd using crictl:
I0408 19:25:31.090199 198268 kubeadm.go:310] - 'crictl --runtime-endpoint /var/run/crio/crio.sock ps -a | grep kube | grep -v pause'
I0408 19:25:31.090325 198268 kubeadm.go:310] Once you have found the failing container, you can inspect its logs with:
I0408 19:25:31.090421 198268 kubeadm.go:310] - 'crictl --runtime-endpoint /var/run/crio/crio.sock logs CONTAINERID'
I0408 19:25:31.090438 198268 kubeadm.go:310]
I0408 19:25:31.090783 198268 kubeadm.go:310] [WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
I0408 19:25:31.090911 198268 kubeadm.go:310] error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
I0408 19:25:31.090984 198268 kubeadm.go:310] To see the stack trace of this error execute with --v=5 or higher
W0408 19:25:31.091137 198268 out.go:270] ! initialization failed, will try again: wait: /bin/bash -c "sudo env PATH="/var/lib/minikube/binaries/v1.20.0:$PATH" kubeadm init --config /var/tmp/minikube/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--var-lib-minikube,DirAvailable--var-lib-minikube-etcd,FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml,FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml,FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml,FileAvailable--etc-kubernetes-manifests-etcd.yaml,Port-10250,Swap,NumCPU,Mem": Process exited with status 1
stdout:
[init] Using Kubernetes version: v1.20.0
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[certs] Using certificateDir folder "/var/lib/minikube/certs"
[certs] Using existing ca certificate authority
[certs] Using existing apiserver certificate and key on disk
[certs] Generating "apiserver-kubelet-client" certificate and key
[certs] Generating "front-proxy-ca" certificate and key
[certs] Generating "front-proxy-client" certificate and key
[certs] Generating "etcd/ca" certificate and key
[certs] Generating "etcd/server" certificate and key
[certs] etcd/server serving cert is signed for DNS names [localhost old-k8s-version-257500] and IPs [192.168.39.192 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-257500] and IPs [192.168.39.192 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-257500] and IPs [192.168.39.192 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-257500] and IPs [192.168.39.192 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
I0408 19:25:31.091190 198268 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"
I0408 19:25:32.683968 198268 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.592751928s)
I0408 19:25:32.684044 198268 ssh_runner.go:195] Run: sudo systemctl is-active --quiet service kubelet
I0408 19:25:32.698260 198268 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
I0408 19:25:32.708236 198268 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
I0408 19:25:32.708261 198268 kubeadm.go:157] found existing configuration files:
I0408 19:25:32.708320 198268 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/admin.conf
I0408 19:25:32.719269 198268 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
I0408 19:25:32.719341 198268 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/admin.conf
I0408 19:25:32.730661 198268 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/kubelet.conf
I0408 19:25:32.740895 198268 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
I0408 19:25:32.740970 198268 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/kubelet.conf
I0408 19:25:32.751222 198268 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/controller-manager.conf
I0408 19:25:32.761613 198268 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
I0408 19:25:32.761681 198268 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/controller-manager.conf
I0408 19:25:32.772347 198268 ssh_runner.go:195] Run: sudo grep https://control-plane.minikube.internal:8443 /etc/kubernetes/scheduler.conf
I0408 19:25:32.781868 198268 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
I0408 19:25:32.781935 198268 ssh_runner.go:195] Run: sudo rm -f /etc/kubernetes/scheduler.conf
I0408 19:25:32.792627 198268 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"
I0408 19:25:32.865592 198268 kubeadm.go:310] [init] Using Kubernetes version: v1.20.0
I0408 19:25:32.865676 198268 kubeadm.go:310] [preflight] Running pre-flight checks
I0408 19:25:33.010348 198268 kubeadm.go:310] [preflight] Pulling images required for setting up a Kubernetes cluster
I0408 19:25:33.010522 198268 kubeadm.go:310] [preflight] This might take a minute or two, depending on the speed of your internet connection
I0408 19:25:33.010637 198268 kubeadm.go:310] [preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
I0408 19:25:33.194579 198268 kubeadm.go:310] [certs] Using certificateDir folder "/var/lib/minikube/certs"
I0408 19:25:33.197058 198268 out.go:235] - Generating certificates and keys ...
I0408 19:25:33.197214 198268 kubeadm.go:310] [certs] Using existing ca certificate authority
I0408 19:25:33.197330 198268 kubeadm.go:310] [certs] Using existing apiserver certificate and key on disk
I0408 19:25:33.197474 198268 kubeadm.go:310] [certs] Using existing apiserver-kubelet-client certificate and key on disk
I0408 19:25:33.197573 198268 kubeadm.go:310] [certs] Using existing front-proxy-ca certificate authority
I0408 19:25:33.197670 198268 kubeadm.go:310] [certs] Using existing front-proxy-client certificate and key on disk
I0408 19:25:33.197755 198268 kubeadm.go:310] [certs] Using existing etcd/ca certificate authority
I0408 19:25:33.197850 198268 kubeadm.go:310] [certs] Using existing etcd/server certificate and key on disk
I0408 19:25:33.197952 198268 kubeadm.go:310] [certs] Using existing etcd/peer certificate and key on disk
I0408 19:25:33.198053 198268 kubeadm.go:310] [certs] Using existing etcd/healthcheck-client certificate and key on disk
I0408 19:25:33.198167 198268 kubeadm.go:310] [certs] Using existing apiserver-etcd-client certificate and key on disk
I0408 19:25:33.198240 198268 kubeadm.go:310] [certs] Using the existing "sa" key
I0408 19:25:33.198337 198268 kubeadm.go:310] [kubeconfig] Using kubeconfig folder "/etc/kubernetes"
I0408 19:25:33.434760 198268 kubeadm.go:310] [kubeconfig] Writing "admin.conf" kubeconfig file
I0408 19:25:33.584982 198268 kubeadm.go:310] [kubeconfig] Writing "kubelet.conf" kubeconfig file
I0408 19:25:33.686825 198268 kubeadm.go:310] [kubeconfig] Writing "controller-manager.conf" kubeconfig file
I0408 19:25:33.758031 198268 kubeadm.go:310] [kubeconfig] Writing "scheduler.conf" kubeconfig file
I0408 19:25:33.773017 198268 kubeadm.go:310] [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
I0408 19:25:33.774499 198268 kubeadm.go:310] [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
I0408 19:25:33.774564 198268 kubeadm.go:310] [kubelet-start] Starting the kubelet
I0408 19:25:33.923574 198268 kubeadm.go:310] [control-plane] Using manifest folder "/etc/kubernetes/manifests"
I0408 19:25:33.925790 198268 out.go:235] - Booting up control plane ...
I0408 19:25:33.925939 198268 kubeadm.go:310] [control-plane] Creating static Pod manifest for "kube-apiserver"
I0408 19:25:33.931094 198268 kubeadm.go:310] [control-plane] Creating static Pod manifest for "kube-controller-manager"
I0408 19:25:33.932182 198268 kubeadm.go:310] [control-plane] Creating static Pod manifest for "kube-scheduler"
I0408 19:25:33.932863 198268 kubeadm.go:310] [etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
I0408 19:25:33.935212 198268 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
I0408 19:26:13.937251 198268 kubeadm.go:310] [kubelet-check] Initial timeout of 40s passed.
I0408 19:26:13.937346 198268 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0408 19:26:13.937600 198268 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.
I0408 19:26:18.937813 198268 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0408 19:26:18.938102 198268 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.
I0408 19:26:28.938493 198268 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0408 19:26:28.938766 198268 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.
I0408 19:26:48.937954 198268 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0408 19:26:48.938281 198268 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.
I0408 19:27:28.937730 198268 kubeadm.go:310] [kubelet-check] It seems like the kubelet isn't running or healthy.
I0408 19:27:28.938020 198268 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.
I0408 19:27:28.938042 198268 kubeadm.go:310]
I0408 19:27:28.938117 198268 kubeadm.go:310] Unfortunately, an error has occurred:
I0408 19:27:28.938221 198268 kubeadm.go:310] timed out waiting for the condition
I0408 19:27:28.938233 198268 kubeadm.go:310]
I0408 19:27:28.938284 198268 kubeadm.go:310] This error is likely caused by:
I0408 19:27:28.938332 198268 kubeadm.go:310] - The kubelet is not running
I0408 19:27:28.938455 198268 kubeadm.go:310] - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
I0408 19:27:28.938464 198268 kubeadm.go:310]
I0408 19:27:28.938590 198268 kubeadm.go:310] If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
I0408 19:27:28.938636 198268 kubeadm.go:310] - 'systemctl status kubelet'
I0408 19:27:28.938677 198268 kubeadm.go:310] - 'journalctl -xeu kubelet'
I0408 19:27:28.938686 198268 kubeadm.go:310]
I0408 19:27:28.938817 198268 kubeadm.go:310] Additionally, a control plane component may have crashed or exited when started by the container runtime.
I0408 19:27:28.938929 198268 kubeadm.go:310] To troubleshoot, list all containers using your preferred container runtimes CLI.
I0408 19:27:28.938942 198268 kubeadm.go:310]
I0408 19:27:28.939146 198268 kubeadm.go:310] Here is one example how you may list all Kubernetes containers running in cri-o/containerd using crictl:
I0408 19:27:28.939295 198268 kubeadm.go:310] - 'crictl --runtime-endpoint /var/run/crio/crio.sock ps -a | grep kube | grep -v pause'
I0408 19:27:28.939403 198268 kubeadm.go:310] Once you have found the failing container, you can inspect its logs with:
I0408 19:27:28.939512 198268 kubeadm.go:310] - 'crictl --runtime-endpoint /var/run/crio/crio.sock logs CONTAINERID'
I0408 19:27:28.939524 198268 kubeadm.go:310]
I0408 19:27:28.939674 198268 kubeadm.go:310] [WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
I0408 19:27:28.939801 198268 kubeadm.go:310] error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
I0408 19:27:28.939903 198268 kubeadm.go:310] To see the stack trace of this error execute with --v=5 or higher
I0408 19:27:28.940019 198268 kubeadm.go:394] duration metric: took 3m56.444226801s to StartCluster
I0408 19:27:28.940072 198268 cri.go:54] listing CRI containers in root : {State:all Name:kube-apiserver Namespaces:[]}
I0408 19:27:28.940141 198268 ssh_runner.go:195] Run: sudo crictl ps -a --quiet --name=kube-apiserver
I0408 19:27:28.975973 198268 cri.go:89] found id: ""
I0408 19:27:28.976008 198268 logs.go:282] 0 containers: []
W0408 19:27:28.976018 198268 logs.go:284] No container was found matching "kube-apiserver"
I0408 19:27:28.976024 198268 cri.go:54] listing CRI containers in root : {State:all Name:etcd Namespaces:[]}
I0408 19:27:28.976091 198268 ssh_runner.go:195] Run: sudo crictl ps -a --quiet --name=etcd
I0408 19:27:29.012032 198268 cri.go:89] found id: ""
I0408 19:27:29.012061 198268 logs.go:282] 0 containers: []
W0408 19:27:29.012072 198268 logs.go:284] No container was found matching "etcd"
I0408 19:27:29.012082 198268 cri.go:54] listing CRI containers in root : {State:all Name:coredns Namespaces:[]}
I0408 19:27:29.012164 198268 ssh_runner.go:195] Run: sudo crictl ps -a --quiet --name=coredns
I0408 19:27:29.052580 198268 cri.go:89] found id: ""
I0408 19:27:29.052612 198268 logs.go:282] 0 containers: []
W0408 19:27:29.052622 198268 logs.go:284] No container was found matching "coredns"
I0408 19:27:29.052631 198268 cri.go:54] listing CRI containers in root : {State:all Name:kube-scheduler Namespaces:[]}
I0408 19:27:29.052711 198268 ssh_runner.go:195] Run: sudo crictl ps -a --quiet --name=kube-scheduler
I0408 19:27:29.091349 198268 cri.go:89] found id: ""
I0408 19:27:29.091383 198268 logs.go:282] 0 containers: []
W0408 19:27:29.091395 198268 logs.go:284] No container was found matching "kube-scheduler"
I0408 19:27:29.091404 198268 cri.go:54] listing CRI containers in root : {State:all Name:kube-proxy Namespaces:[]}
I0408 19:27:29.091467 198268 ssh_runner.go:195] Run: sudo crictl ps -a --quiet --name=kube-proxy
I0408 19:27:29.128088 198268 cri.go:89] found id: ""
I0408 19:27:29.128120 198268 logs.go:282] 0 containers: []
W0408 19:27:29.128128 198268 logs.go:284] No container was found matching "kube-proxy"
I0408 19:27:29.128134 198268 cri.go:54] listing CRI containers in root : {State:all Name:kube-controller-manager Namespaces:[]}
I0408 19:27:29.128202 198268 ssh_runner.go:195] Run: sudo crictl ps -a --quiet --name=kube-controller-manager
I0408 19:27:29.163947 198268 cri.go:89] found id: ""
I0408 19:27:29.163984 198268 logs.go:282] 0 containers: []
W0408 19:27:29.163995 198268 logs.go:284] No container was found matching "kube-controller-manager"
I0408 19:27:29.164004 198268 cri.go:54] listing CRI containers in root : {State:all Name:kindnet Namespaces:[]}
I0408 19:27:29.164078 198268 ssh_runner.go:195] Run: sudo crictl ps -a --quiet --name=kindnet
I0408 19:27:29.197717 198268 cri.go:89] found id: ""
I0408 19:27:29.197754 198268 logs.go:282] 0 containers: []
W0408 19:27:29.197766 198268 logs.go:284] No container was found matching "kindnet"
I0408 19:27:29.197779 198268 logs.go:123] Gathering logs for describe nodes ...
I0408 19:27:29.197795 198268 ssh_runner.go:195] Run: /bin/bash -c "sudo /var/lib/minikube/binaries/v1.20.0/kubectl describe nodes --kubeconfig=/var/lib/minikube/kubeconfig"
W0408 19:27:29.315828 198268 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 **
I0408 19:27:29.315856 198268 logs.go:123] Gathering logs for CRI-O ...
I0408 19:27:29.315874 198268 ssh_runner.go:195] Run: /bin/bash -c "sudo journalctl -u crio -n 400"
I0408 19:27:29.425555 198268 logs.go:123] Gathering logs for container status ...
I0408 19:27:29.425608 198268 ssh_runner.go:195] Run: /bin/bash -c "sudo `which crictl || echo crictl` ps -a || sudo docker ps -a"
I0408 19:27:29.466712 198268 logs.go:123] Gathering logs for kubelet ...
I0408 19:27:29.466746 198268 ssh_runner.go:195] Run: /bin/bash -c "sudo journalctl -u kubelet -n 400"
I0408 19:27:29.518983 198268 logs.go:123] Gathering logs for dmesg ...
I0408 19:27:29.519028 198268 ssh_runner.go:195] Run: /bin/bash -c "sudo dmesg -PH -L=never --level warn,err,crit,alert,emerg | tail -n 400"
W0408 19:27:29.536355 198268 out.go:418] Error starting cluster: wait: /bin/bash -c "sudo env PATH="/var/lib/minikube/binaries/v1.20.0:$PATH" kubeadm init --config /var/tmp/minikube/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--var-lib-minikube,DirAvailable--var-lib-minikube-etcd,FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml,FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml,FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml,FileAvailable--etc-kubernetes-manifests-etcd.yaml,Port-10250,Swap,NumCPU,Mem": Process exited with status 1
stdout:
[init] Using Kubernetes version: v1.20.0
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[certs] Using certificateDir folder "/var/lib/minikube/certs"
[certs] Using existing ca certificate authority
[certs] Using existing apiserver certificate and key on disk
[certs] Using existing apiserver-kubelet-client certificate and key on disk
[certs] Using existing front-proxy-ca certificate authority
[certs] Using existing front-proxy-client certificate and key on disk
[certs] Using existing etcd/ca certificate authority
[certs] Using existing etcd/server certificate and key on disk
[certs] Using existing etcd/peer certificate and key on disk
[certs] Using existing etcd/healthcheck-client certificate and key on disk
[certs] Using existing apiserver-etcd-client certificate and key on disk
[certs] Using the existing "sa" key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
Unfortunately, an error has occurred:
timed out waiting for the condition
This error is likely caused by:
- The kubelet is not running
- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
- 'systemctl status kubelet'
- 'journalctl -xeu kubelet'
Additionally, a control plane component may have crashed or exited when started by the container runtime.
To troubleshoot, list all containers using your preferred container runtimes CLI.
Here is one example how you may list all Kubernetes containers running in cri-o/containerd using crictl:
- 'crictl --runtime-endpoint /var/run/crio/crio.sock ps -a | grep kube | grep -v pause'
Once you have found the failing container, you can inspect its logs with:
- 'crictl --runtime-endpoint /var/run/crio/crio.sock logs CONTAINERID'
stderr:
[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
To see the stack trace of this error execute with --v=5 or higher
W0408 19:27:29.536480 198268 out.go:270] *
*
W0408 19:27:29.536561 198268 out.go:270] X Error starting cluster: wait: /bin/bash -c "sudo env PATH="/var/lib/minikube/binaries/v1.20.0:$PATH" kubeadm init --config /var/tmp/minikube/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--var-lib-minikube,DirAvailable--var-lib-minikube-etcd,FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml,FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml,FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml,FileAvailable--etc-kubernetes-manifests-etcd.yaml,Port-10250,Swap,NumCPU,Mem": Process exited with status 1
stdout:
[init] Using Kubernetes version: v1.20.0
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[certs] Using certificateDir folder "/var/lib/minikube/certs"
[certs] Using existing ca certificate authority
[certs] Using existing apiserver certificate and key on disk
[certs] Using existing apiserver-kubelet-client certificate and key on disk
[certs] Using existing front-proxy-ca certificate authority
[certs] Using existing front-proxy-client certificate and key on disk
[certs] Using existing etcd/ca certificate authority
[certs] Using existing etcd/server certificate and key on disk
[certs] Using existing etcd/peer certificate and key on disk
[certs] Using existing etcd/healthcheck-client certificate and key on disk
[certs] Using existing apiserver-etcd-client certificate and key on disk
[certs] Using the existing "sa" key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
Unfortunately, an error has occurred:
timed out waiting for the condition
This error is likely caused by:
- The kubelet is not running
- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
- 'systemctl status kubelet'
- 'journalctl -xeu kubelet'
Additionally, a control plane component may have crashed or exited when started by the container runtime.
To troubleshoot, list all containers using your preferred container runtimes CLI.
Here is one example how you may list all Kubernetes containers running in cri-o/containerd using crictl:
- 'crictl --runtime-endpoint /var/run/crio/crio.sock ps -a | grep kube | grep -v pause'
Once you have found the failing container, you can inspect its logs with:
- 'crictl --runtime-endpoint /var/run/crio/crio.sock logs CONTAINERID'
stderr:
[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
To see the stack trace of this error execute with --v=5 or higher
X Error starting cluster: wait: /bin/bash -c "sudo env PATH="/var/lib/minikube/binaries/v1.20.0:$PATH" kubeadm init --config /var/tmp/minikube/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--var-lib-minikube,DirAvailable--var-lib-minikube-etcd,FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml,FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml,FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml,FileAvailable--etc-kubernetes-manifests-etcd.yaml,Port-10250,Swap,NumCPU,Mem": Process exited with status 1
stdout:
[init] Using Kubernetes version: v1.20.0
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[certs] Using certificateDir folder "/var/lib/minikube/certs"
[certs] Using existing ca certificate authority
[certs] Using existing apiserver certificate and key on disk
[certs] Using existing apiserver-kubelet-client certificate and key on disk
[certs] Using existing front-proxy-ca certificate authority
[certs] Using existing front-proxy-client certificate and key on disk
[certs] Using existing etcd/ca certificate authority
[certs] Using existing etcd/server certificate and key on disk
[certs] Using existing etcd/peer certificate and key on disk
[certs] Using existing etcd/healthcheck-client certificate and key on disk
[certs] Using existing apiserver-etcd-client certificate and key on disk
[certs] Using the existing "sa" key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
Unfortunately, an error has occurred:
timed out waiting for the condition
This error is likely caused by:
- The kubelet is not running
- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
- 'systemctl status kubelet'
- 'journalctl -xeu kubelet'
Additionally, a control plane component may have crashed or exited when started by the container runtime.
To troubleshoot, list all containers using your preferred container runtimes CLI.
Here is one example how you may list all Kubernetes containers running in cri-o/containerd using crictl:
- 'crictl --runtime-endpoint /var/run/crio/crio.sock ps -a | grep kube | grep -v pause'
Once you have found the failing container, you can inspect its logs with:
- 'crictl --runtime-endpoint /var/run/crio/crio.sock logs CONTAINERID'
stderr:
[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
To see the stack trace of this error execute with --v=5 or higher
W0408 19:27:29.536584 198268 out.go:270] *
*
W0408 19:27:29.537786 198268 out.go:293] ╭─────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ * If the above advice does not help, please let us know: │
│ https://github.com/kubernetes/minikube/issues/new/choose │
│ │
│ * Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue. │
│ │
╰─────────────────────────────────────────────────────────────────────────────────────────────╯
╭─────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ * If the above advice does not help, please let us know: │
│ https://github.com/kubernetes/minikube/issues/new/choose │
│ │
│ * Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue. │
│ │
╰─────────────────────────────────────────────────────────────────────────────────────────────╯
I0408 19:27:29.541735 198268 out.go:201]
W0408 19:27:29.543405 198268 out.go:270] X Exiting due to K8S_KUBELET_NOT_RUNNING: wait: /bin/bash -c "sudo env PATH="/var/lib/minikube/binaries/v1.20.0:$PATH" kubeadm init --config /var/tmp/minikube/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--var-lib-minikube,DirAvailable--var-lib-minikube-etcd,FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml,FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml,FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml,FileAvailable--etc-kubernetes-manifests-etcd.yaml,Port-10250,Swap,NumCPU,Mem": Process exited with status 1
stdout:
[init] Using Kubernetes version: v1.20.0
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[certs] Using certificateDir folder "/var/lib/minikube/certs"
[certs] Using existing ca certificate authority
[certs] Using existing apiserver certificate and key on disk
[certs] Using existing apiserver-kubelet-client certificate and key on disk
[certs] Using existing front-proxy-ca certificate authority
[certs] Using existing front-proxy-client certificate and key on disk
[certs] Using existing etcd/ca certificate authority
[certs] Using existing etcd/server certificate and key on disk
[certs] Using existing etcd/peer certificate and key on disk
[certs] Using existing etcd/healthcheck-client certificate and key on disk
[certs] Using existing apiserver-etcd-client certificate and key on disk
[certs] Using the existing "sa" key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
Unfortunately, an error has occurred:
timed out waiting for the condition
This error is likely caused by:
- The kubelet is not running
- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
- 'systemctl status kubelet'
- 'journalctl -xeu kubelet'
Additionally, a control plane component may have crashed or exited when started by the container runtime.
To troubleshoot, list all containers using your preferred container runtimes CLI.
Here is one example how you may list all Kubernetes containers running in cri-o/containerd using crictl:
- 'crictl --runtime-endpoint /var/run/crio/crio.sock ps -a | grep kube | grep -v pause'
Once you have found the failing container, you can inspect its logs with:
- 'crictl --runtime-endpoint /var/run/crio/crio.sock logs CONTAINERID'
stderr:
[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
To see the stack trace of this error execute with --v=5 or higher
X Exiting due to K8S_KUBELET_NOT_RUNNING: wait: /bin/bash -c "sudo env PATH="/var/lib/minikube/binaries/v1.20.0:$PATH" kubeadm init --config /var/tmp/minikube/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--var-lib-minikube,DirAvailable--var-lib-minikube-etcd,FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml,FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml,FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml,FileAvailable--etc-kubernetes-manifests-etcd.yaml,Port-10250,Swap,NumCPU,Mem": Process exited with status 1
stdout:
[init] Using Kubernetes version: v1.20.0
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[certs] Using certificateDir folder "/var/lib/minikube/certs"
[certs] Using existing ca certificate authority
[certs] Using existing apiserver certificate and key on disk
[certs] Using existing apiserver-kubelet-client certificate and key on disk
[certs] Using existing front-proxy-ca certificate authority
[certs] Using existing front-proxy-client certificate and key on disk
[certs] Using existing etcd/ca certificate authority
[certs] Using existing etcd/server certificate and key on disk
[certs] Using existing etcd/peer certificate and key on disk
[certs] Using existing etcd/healthcheck-client certificate and key on disk
[certs] Using existing apiserver-etcd-client certificate and key on disk
[certs] Using the existing "sa" key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
Unfortunately, an error has occurred:
timed out waiting for the condition
This error is likely caused by:
- The kubelet is not running
- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
- 'systemctl status kubelet'
- 'journalctl -xeu kubelet'
Additionally, a control plane component may have crashed or exited when started by the container runtime.
To troubleshoot, list all containers using your preferred container runtimes CLI.
Here is one example how you may list all Kubernetes containers running in cri-o/containerd using crictl:
- 'crictl --runtime-endpoint /var/run/crio/crio.sock ps -a | grep kube | grep -v pause'
Once you have found the failing container, you can inspect its logs with:
- 'crictl --runtime-endpoint /var/run/crio/crio.sock logs CONTAINERID'
stderr:
[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
To see the stack trace of this error execute with --v=5 or higher
W0408 19:27:29.543473 198268 out.go:270] * Suggestion: Check output of 'journalctl -xeu kubelet', try passing --extra-config=kubelet.cgroup-driver=systemd to minikube start
* Suggestion: Check output of 'journalctl -xeu kubelet', try passing --extra-config=kubelet.cgroup-driver=systemd to minikube start
W0408 19:27:29.543512 198268 out.go:270] * Related issue: https://github.com/kubernetes/minikube/issues/4172
* Related issue: https://github.com/kubernetes/minikube/issues/4172
I0408 19:27:29.545289 198268 out.go:201]
** /stderr **
start_stop_delete_test.go:186: failed starting minikube -first start-. args "out/minikube-linux-amd64 start -p old-k8s-version-257500 --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-257500 -n old-k8s-version-257500
helpers_test.go:239: (dbg) Non-zero exit: out/minikube-linux-amd64 status --format={{.Host}} -p old-k8s-version-257500 -n old-k8s-version-257500: exit status 6 (258.616577ms)
-- stdout --
Running
WARNING: Your kubectl is pointing to stale minikube-vm.
To fix the kubectl context, run `minikube update-context`
-- /stdout --
** stderr **
E0408 19:27:29.861148 204892 status.go:458] kubeconfig endpoint: get endpoint: "old-k8s-version-257500" does not appear in /home/jenkins/minikube-integration/20604-141129/kubeconfig
** /stderr **
helpers_test.go:239: status error: exit status 6 (may be ok)
helpers_test.go:241: "old-k8s-version-257500" 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 (275.44s)