CI: Cilium-PR-K8s-1.26-kernel-net-next: Build K8s vm provisioning fail

CI failure
Hitting vm provisioning failures on multiple PRs. Example:
https://jenkins.cilium.io/job/Cilium-PR-K8s-1.26-kernel-net-next/50/
Pipeline steps show that it's hitting a 25m timeout while provisioning the VMs.
09:40:14  + ./print-node-ip.sh
09:40:14  + CILIUM_REGISTRY=<IP_ADDRESS> timeout 25m ./vagrant-ci-start.sh
09:40:14  restarting portmap and nfs-kernel-server services to combat nfs server issues
09:40:14  destroying vms in case this is a retry
09:40:14  ==> k8s1-1.26: VM not created. Moving on...
09:40:15  ==> k8s2-1.26: VM not created. Moving on...
09:40:16  ==> k8s3-1.26: VM not created. Moving on...
09:40:16  boxes available on the node
09:40:16  cilium/ubuntu      (virtualbox, 232)
09:40:16  cilium/ubuntu-4-19 (virtualbox, 69)
09:40:16  cilium/ubuntu-5-4  (virtualbox, 35)
09:40:16  cilium/ubuntu-next (virtualbox, 154)
09:40:16  starting vms
09:40:17  Bringing machine 'k8s1-1.26' up with 'virtualbox' provider...
09:40:17  ==> k8s1-1.26: Running action triggers before up ...
09:40:17  ==> k8s1-1.26: Running trigger...
09:40:17      k8s1-1.26: Running local: Inline script
09:40:17      k8s1-1.26: bash -c 'i=1
09:40:17      k8s1-1.26: k8s_nodes="${K8S_NODES:-2}"
09:40:17      k8s1-1.26: while [ "$i" -le "$k8s_nodes" ]; do
09:40:17      k8s1-1.26:     VBoxManage natnetwork add --netname natnet$i --network <IP_ADDRESS>/16 --ipv6 on --enable
09:40:17      k8s1-1.26:     i=$((i+1))
09:40:17      k8s1-1.26: done 2>/dev/null
09:40:17      k8s1-1.26:
09:40:17      k8s1-1.26: res=0
09:40:17      k8s1-1.26: while [ "$res" == "0" ]; do
09:40:17      k8s1-1.26:     VBoxManage natnetwork remove --netname natnet$i
09:40:17      k8s1-1.26:     res=$?
09:40:17      k8s1-1.26:     i=$((i+1))
09:40:17      k8s1-1.26: done 2>/dev/null
09:40:17      k8s1-1.26: '
09:40:18  ==> k8s1-1.26: Preparing master VM for linked clones...
09:40:18      k8s1-1.26: This is a one time operation. Once the master VM is prepared,
09:40:18      k8s1-1.26: it will be used as a base for linked clones, making the creation
09:40:18      k8s1-1.26: of new VMs take milliseconds on a modern system.
09:40:18  ==> k8s1-1.26: Importing base box 'cilium/ubuntu-next'...
09:42:28
Progress: 10%
Progress: 20%
Progress: 30%
Progress: 40%
Progress: 50%
Progress: 60%
Progress: 90%
==> k8s1-1.26: Cloning VM...
09:42:28
==> k8s1-1.26: Matching MAC address for NAT networking...
09:42:28  ==> k8s1-1.26: Checking if box 'cilium/ubuntu-next' version '154' is up to date...
09:42:28  ==> k8s1-1.26: There was a problem while downloading the metadata for your box
09:42:28  ==> k8s1-1.26: to check for updates. This is not an error, since it is usually due
09:42:28  ==> k8s1-1.26: to temporary network problems. This is just a warning. The problem
09:42:28  ==> k8s1-1.26: encountered was:
09:42:28  ==> k8s1-1.26:
09:42:28  ==> k8s1-1.26: Couldn't open file /home/jenkins/workspace/Cilium-PR-K8s-1.20-kernel-4.9/metadata.json
09:42:28  ==> k8s1-1.26:
09:42:28  ==> k8s1-1.26: If you want to check for box updates, verify your network connection
09:42:28  ==> k8s1-1.26: is valid and try again.
09:42:28  ==> k8s1-1.26: Setting the name of the VM: test_k8s1-126_1669916548558_21720
09:42:29  ==> k8s1-1.26: Clearing any previously set network interfaces...
09:42:29  ==> k8s1-1.26: Preparing network interfaces based on configuration...
09:42:29      k8s1-1.26: Adapter 1: nat
09:42:29      k8s1-1.26: Adapter 2: intnet
09:42:29      k8s1-1.26: Adapter 3: intnet
09:42:29      k8s1-1.26: Adapter 4: hostonly
09:42:29      k8s1-1.26: Adapter 5: hostonly
09:42:29  ==> k8s1-1.26: Forwarding ports...
09:42:29      k8s1-1.26: 3000 (guest) => 3000 (host) (adapter 1)
09:42:29      k8s1-1.26: 6443 (guest) => 9443 (host) (adapter 1)
09:42:29      k8s1-1.26: 22 (guest) => 2222 (host) (adapter 1)
09:42:30  ==> k8s1-1.26: Running 'pre-boot' VM customizations...
09:42:30  ==> k8s1-1.26: Booting VM...
09:42:30  ==> k8s1-1.26: Waiting for machine to boot. This may take a few minutes...
09:42:30      k8s1-1.26: SSH address: <IP_ADDRESS>:2222
09:42:30      k8s1-1.26: SSH username: vagrant
09:42:30      k8s1-1.26: SSH auth method: private key
09:43:05      k8s1-1.26:
09:43:05      k8s1-1.26: Vagrant insecure key detected. Vagrant will automatically replace
09:43:05      k8s1-1.26: this with a newly generated keypair for better security.
09:43:06      k8s1-1.26:
09:43:06      k8s1-1.26: Inserting generated public key within guest...
09:43:06      k8s1-1.26: Removing insecure key from the guest if it's present...
09:43:06      k8s1-1.26: Key inserted! Disconnecting and reconnecting using new SSH key...
09:43:07  ==> k8s1-1.26: Machine booted and ready!
09:43:07  ==> k8s1-1.26: Checking for guest additions in VM...
09:43:07  ==> k8s1-1.26: Setting hostname...
09:43:08  ==> k8s1-1.26: Configuring and enabling network interfaces...
09:43:20  ==> k8s1-1.26: Installing NFS client...
09:45:31  ==> k8s1-1.26: Exporting NFS shared folders...
09:45:31  ==> k8s1-1.26: Preparing to edit /etc/exports.  Your password will be stored unencrypted in /root/.docker/config.json.
09:45:31      k8s1-1.26: Configure a credential helper to remove this warning. See
09:45:31      k8s1-1.26: https://docs.docker.com/engine/reference/commandline/login/#credentials-store
09:45:31      k8s1-1.26:
09:45:31      k8s1-1.26: Login Succeeded
09:45:31      k8s1-1.26: /tmp/vagrant-shell: line 48: helm: command not found
09:45:31      k8s1-1.26: beginning trying up to 10 times function "wget -nv https://get.helm.sh/helm-v3.7.0-linux-amd64.tar.gz"
09:45:31      k8s1-1.26: ***************************************
09:45:31      k8s1-1.26: *
09:45:31      k8s1-1.26: *
09:45:31      k8s1-1.26: * on attempt 0 of function "wget -nv https://get.helm.sh/helm-v3.7.0-linux-amd64.tar.gz"
09:45:31      k8s1-1.26: *
09:45:31      k8s1-1.26: *
09:45:31      k8s1-1.26: ***************************************
09:45:31      k8s1-1.26: 2022-12-01 17:45:31 URL:https://get.helm.sh/helm-v3.7.0-linux-amd64.tar.gz [13861119/13861119] -> "helm-v3.7.0-linux-amd64.tar.gz" [1]
09:45:31      k8s1-1.26: running of "wget -nv https://get.helm.sh/helm-v3.7.0-linux-amd64.tar.gz" successful
09:45:31      k8s1-1.26:
09:45:31      k8s1-1.26:
09:45:31      k8s1-1.26:
09:45:31      k8s1-1.26: linux-amd64/
09:45:31      k8s1-1.26: linux-amd64/helm
09:45:32      k8s1-1.26: linux-amd64/LICENSE
09:45:32      k8s1-1.26: linux-amd64/README.md
09:45:32      k8s1-1.26: version.BuildInfo{Version:"v3.7.0", GitCommit:"eeac83883cb4014fe60267ec6373570374ce770b", GitTreeState:"clean", GoVersion:"go1.16.8"}
09:45:33      k8s1-1.26: updating /etc/resolv.conf
09:45:33      k8s1-1.26: beginning trying up to 10 times function "wget https://packages.cloud.google.com/apt/doc/apt-key.gpg"
09:45:33      k8s1-1.26: ***************************************
09:45:33      k8s1-1.26: *
09:45:33      k8s1-1.26: *
09:45:33      k8s1-1.26: * on attempt 0 of function "wget https://packages.cloud.google.com/apt/doc/apt-key.gpg"
09:45:33      k8s1-1.26: *
09:45:33      k8s1-1.26: *
09:45:33      k8s1-1.26: ***************************************
09:45:33      k8s1-1.26: --2022-12-01 17:45:33--  https://packages.cloud.google.com/apt/doc/apt-key.gpg
09:45:33      k8s1-1.26: Resolving packages.cloud.google.com (packages.cloud.google.com)... <IP_ADDRESS>, 2607:f8b0:4000:819::200e
09:45:33      k8s1-1.26: Connecting to packages.cloud.google.com (packages.cloud.google.com)|<IP_ADDRESS>|:443... connected.
09:45:33      k8s1-1.26: HTTP request sent, awaiting response... 200 OK
09:45:33      k8s1-1.26: Length: 2537 (2.5K) [application/octet-stream]
09:45:33      k8s1-1.26: Saving to: ‘apt-key.gpg’
09:45:33      k8s1-1.26:
09:45:33      k8s1-1.26:      0K ..                                                    100% 6.61M=0s
09:45:33      k8s1-1.26:
09:45:33      k8s1-1.26: 2022-12-01 17:45:33 (6.61 MB/s) - ‘apt-key.gpg’ saved [2537/2537]
09:45:33      k8s1-1.26:
09:45:33      k8s1-1.26: running of "wget https://packages.cloud.google.com/apt/doc/apt-key.gpg" successful
09:45:33      k8s1-1.26:
09:45:33      k8s1-1.26:
09:45:33      k8s1-1.26:
09:45:33      k8s1-1.26: Warning: apt-key output should not be parsed (stdout is not a terminal)
09:45:34      k8s1-1.26: OK
09:45:36      k8s1-1.26: Reading package lists...
09:45:36      k8s1-1.26: Building dependency tree...
09:45:36      k8s1-1.26: Reading state information...
09:45:36      k8s1-1.26: conntrack is already the newest version (1:1.4.5-2).
09:45:36      k8s1-1.26: 0 upgraded, 0 newly installed, 0 to remove and 51 not upgraded.
09:45:36      k8s1-1.26: Hit:1 https://deb.nodesource.com/node_12.x focal InRelease
09:45:36      k8s1-1.26: Hit:3 https://download.docker.com/linux/ubuntu focal InRelease
09:45:36      k8s1-1.26: Get:2 https://packages.cloud.google.com/apt kubernetes-xenial InRelease [9,383 B]
09:46:18      k8s1-1.26: Hit:4 http://us.archive.ubuntu.com/ubuntu focal InRelease
09:46:18      k8s1-1.26: Get:5 http://us.archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB]
09:46:18      k8s1-1.26: Get:6 http://us.archive.ubuntu.com/ubuntu focal-backports InRelease [108 kB]
09:46:18      k8s1-1.26: Get:7 http://us.archive.ubuntu.com/ubuntu focal-security InRelease [114 kB]
09:46:20      k8s1-1.26: Get:8 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [2,258 kB]
09:47:02      k8s1-1.26: Get:9 http://us.archive.ubuntu.com/ubuntu focal-updates/main Translation-en [393 kB]
09:47:14      k8s1-1.26: Get:10 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 c-n-f Metadata [16.1 kB]
09:47:14      k8s1-1.26: Get:11 http://us.archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages [1,453 kB]
09:47:26      k8s1-1.26: Get:12 http://us.archive.ubuntu.com/ubuntu focal-updates/restricted Translation-en [205 kB]
09:47:29      k8s1-1.26: Get:13 http://us.archive.ubuntu.com/ubuntu focal-updates/restricted amd64 c-n-f Metadata [636 B]
09:47:29      k8s1-1.26: Get:14 http://us.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages [1,007 kB]
09:47:58      k8s1-1.26: Get:15 http://us.archive.ubuntu.com/ubuntu focal-updates/universe Translation-en [234 kB]
09:48:07      k8s1-1.26: Get:16 http://us.archive.ubuntu.com/ubuntu focal-updates/universe amd64 c-n-f Metadata [23.2 kB]
09:48:07      k8s1-1.26: Get:17 http://us.archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 Packages [24.4 kB]
09:48:07      k8s1-1.26: Get:18 http://us.archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 c-n-f Metadata [592 B]
09:48:07      k8s1-1.26: Get:19 http://us.archive.ubuntu.com/ubuntu focal-backports/main amd64 Packages [45.7 kB]
09:48:07      k8s1-1.26: Get:20 http://us.archive.ubuntu.com/ubuntu focal-backports/main amd64 c-n-f Metadata [1,420 B]
09:48:07      k8s1-1.26: Get:21 http://us.archive.ubuntu.com/ubuntu focal-backports/universe amd64 Packages [24.0 kB]
09:48:08      k8s1-1.26: Get:22 http://us.archive.ubuntu.com/ubuntu focal-backports/universe Translation-en [16.0 kB]
09:48:08      k8s1-1.26: Get:23 http://us.archive.ubuntu.com/ubuntu focal-backports/universe amd64 c-n-f Metadata [860 B]
09:48:08      k8s1-1.26: Get:24 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages [1,885 kB]
09:48:10      k8s1-1.26: Get:25 http://us.archive.ubuntu.com/ubuntu focal-security/main Translation-en [309 kB]
09:48:10      k8s1-1.26: Get:26 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 c-n-f Metadata [11.4 kB]
09:48:10      k8s1-1.26: Get:27 http://us.archive.ubuntu.com/ubuntu focal-security/restricted amd64 Packages [1,360 kB]
09:48:15      k8s1-1.26: Get:28 http://us.archive.ubuntu.com/ubuntu focal-security/restricted Translation-en [192 kB]
09:48:15      k8s1-1.26: Get:29 http://us.archive.ubuntu.com/ubuntu focal-security/restricted amd64 c-n-f Metadata [640 B]
09:48:15      k8s1-1.26: Get:30 http://us.archive.ubuntu.com/ubuntu focal-security/universe amd64 Packages [777 kB]
09:48:18      k8s1-1.26: Get:31 http://us.archive.ubuntu.com/ubuntu focal-security/universe Translation-en [149 kB]
09:48:19      k8s1-1.26: Get:32 http://us.archive.ubuntu.com/ubuntu focal-security/universe amd64 c-n-f Metadata [16.8 kB]
09:48:19      k8s1-1.26: Get:33 http://us.archive.ubuntu.com/ubuntu focal-security/multiverse amd64 Packages [22.2 kB]
09:48:19      k8s1-1.26: Get:34 http://us.archive.ubuntu.com/ubuntu focal-security/multiverse Translation-en [5,400 B]
09:48:19      k8s1-1.26: Get:35 http://us.archive.ubuntu.com/ubuntu focal-security/multiverse amd64 c-n-f Metadata [516 B]
09:48:25      k8s1-1.26: Fetched 10.8 MB in 2min 43s (66.2 kB/s)
09:48:25      k8s1-1.26: Reading package lists...
09:48:25      k8s1-1.26: Reading package lists...
09:48:25      k8s1-1.26: Building dependency tree...
09:48:25      k8s1-1.26: Reading state information...
09:48:25      k8s1-1.26: E: Version '1.26.0-rc.0*' for 'kubelet' was not found
09:48:25      k8s1-1.26: E: Version '1.26.0-rc.0*' for 'kubeadm' was not found
09:48:25      k8s1-1.26: E: Version '1.26.0-rc.0*' for 'kubectl' was not found
09:48:25      k8s1-1.26: falling back on binary k8s install
09:48:27      k8s1-1.26: 'kubeadm' -> '/usr/bin/kubeadm'
09:48:27      k8s1-1.26: 'kubectl' -> '/usr/bin/kubectl'
09:48:27      k8s1-1.26: 'kubelet' -> '/usr/bin/kubelet'
09:48:28      k8s1-1.26: Created symlink /etc/systemd/system/multi-user.target.wants/kubelet.service → /etc/systemd/system/kubelet.service.
09:48:28      k8s1-1.26: KUBELET_EXTRA_ARGS="--fail-swap-on=false"
09:48:28      k8s1-1.26: W1201 17:48:28.749515   11220 initconfiguration.go:331] [config] WARNING: Ignored YAML document with GroupVersionKind kubeadm.k8s.io/v1beta3, Kind=JoinConfiguration
09:48:28      k8s1-1.26: [init] Using Kubernetes version: v1.26.0-rc.0
09:48:28      k8s1-1.26: [preflight] Running pre-flight checks
09:48:29      k8s1-1.26: 	[WARNING Swap]: swap is enabled; production deployments should disable swap unless testing the NodeSwap feature gate of the kubelet
09:48:29      k8s1-1.26: [preflight] Pulling images required for setting up a Kubernetes cluster
09:48:29      k8s1-1.26: [preflight] This might take a minute or two, depending on the speed of your internet connection
09:48:29      k8s1-1.26: [preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
09:48:29      k8s1-1.26: W1201 17:48:29.022229   11220 images.go:80] could not find officially supported version of etcd for Kubernetes v1.26.0-rc.0, falling back to the nearest etcd version (3.5.5-0)
09:49:19      k8s1-1.26: [certs] Using certificateDir folder "/etc/kubernetes/pki"
09:49:19      k8s1-1.26: [certs] Generating "ca" certificate and key
09:49:19      k8s1-1.26: [certs] Generating "apiserver" certificate and key
09:49:19      k8s1-1.26: [certs] apiserver serving cert is signed for DNS names [k8s1 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [<IP_ADDRESS> <IP_ADDRESS>]
09:49:19      k8s1-1.26: [certs] Generating "apiserver-kubelet-client" certificate and key
09:49:19      k8s1-1.26: [certs] Generating "front-proxy-ca" certificate and key
09:49:19      k8s1-1.26: [certs] Generating "front-proxy-client" certificate and key
09:49:19      k8s1-1.26: [certs] Generating "etcd/ca" certificate and key
09:49:19      k8s1-1.26: [certs] Generating "etcd/server" certificate and key
09:49:19      k8s1-1.26: [certs] etcd/server serving cert is signed for DNS names [k8s1 localhost] and IPs [<IP_ADDRESS> <IP_ADDRESS> ::1]
09:49:19      k8s1-1.26: [certs] Generating "etcd/peer" certificate and key
09:49:19      k8s1-1.26: [certs] etcd/peer serving cert is signed for DNS names [k8s1 localhost] and IPs [<IP_ADDRESS> <IP_ADDRESS> ::1]
09:49:19      k8s1-1.26: [certs] Generating "etcd/healthcheck-client" certificate and key
09:49:19      k8s1-1.26: [certs] Generating "apiserver-etcd-client" certificate and key
09:49:20      k8s1-1.26: [certs] Generating "sa" key and public key
09:49:20      k8s1-1.26: [kubeconfig] Using kubeconfig folder "/etc/kubernetes"
09:49:20      k8s1-1.26: [kubeconfig] Writing "admin.conf" kubeconfig file
09:49:20      k8s1-1.26: [kubeconfig] Writing "kubelet.conf" kubeconfig file
09:49:20      k8s1-1.26: [kubeconfig] Writing "controller-manager.conf" kubeconfig file
09:49:20      k8s1-1.26: [kubeconfig] Writing "scheduler.conf" kubeconfig file
09:49:20      k8s1-1.26: [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
09:49:20      k8s1-1.26: [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
09:49:20      k8s1-1.26: [kubelet-start] Starting the kubelet
09:49:21      k8s1-1.26: [control-plane] Using manifest folder "/etc/kubernetes/manifests"
09:49:21      k8s1-1.26: [control-plane] Creating static Pod manifest for "kube-apiserver"
09:49:21      k8s1-1.26: [control-plane] Creating static Pod manifest for "kube-controller-manager"
09:49:21      k8s1-1.26: [control-plane] Creating static Pod manifest for "kube-scheduler"
09:49:21      k8s1-1.26: [etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
09:49:21      k8s1-1.26: W1201 17:49:20.902744   11220 images.go:80] could not find officially supported version of etcd for Kubernetes v1.26.0-rc.0, falling back to the nearest etcd version (3.5.5-0)
09:49:21      k8s1-1.26: [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
09:49:26      k8s1-1.26: [apiclient] All control plane components are healthy after 5.001999 seconds
09:49:26      k8s1-1.26: [upload-config] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
09:49:26      k8s1-1.26: [kubelet] Creating a ConfigMap "kubelet-config" in namespace kube-system with the configuration for the kubelets in the cluster
09:49:26      k8s1-1.26: [upload-certs] Skipping phase. Please see --upload-certs
09:49:26      k8s1-1.26: [mark-control-plane] Marking the node k8s1 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]
09:49:26      k8s1-1.26: [mark-control-plane] Marking the node k8s1 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]
09:49:27      k8s1-1.26: [bootstrap-token] Using token: 258062.5d84c017c9b2796c
09:49:27      k8s1-1.26: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles
09:49:27      k8s1-1.26: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes
09:49:27      k8s1-1.26: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials
09:49:27      k8s1-1.26: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token
09:49:27      k8s1-1.26: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster
09:49:27      k8s1-1.26: [bootstrap-token] Creating the "cluster-info" ConfigMap in the "kube-public" namespace
09:49:27      k8s1-1.26: [kubelet-finalize] Updating "/etc/kubernetes/kubelet.conf" to point to a rotatable kubelet client certificate and key
09:49:27      k8s1-1.26: [addons] Applied essential addon: CoreDNS
09:49:27      k8s1-1.26:
09:49:27      k8s1-1.26: Your Kubernetes control-plane has initialized successfully!
09:49:27      k8s1-1.26:
09:49:27      k8s1-1.26: To start using your cluster, you need to run the following as a regular user:
09:49:27      k8s1-1.26:
09:49:27      k8s1-1.26:   mkdir -p $HOME/.kube
09:49:27      k8s1-1.26:   sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
09:49:27      k8s1-1.26:   sudo chown $(id -u):$(id -g) $HOME/.kube/config
09:49:27      k8s1-1.26:
09:49:27      k8s1-1.26: Alternatively, if you are the root user, you can run:
09:49:27      k8s1-1.26:
09:49:27      k8s1-1.26:   export KUBECONFIG=/etc/kubernetes/admin.conf
09:49:27      k8s1-1.26:
09:49:27      k8s1-1.26: You should now deploy a pod network to the cluster.
09:49:27      k8s1-1.26: Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
09:49:27      k8s1-1.26:   https://kubernetes.io/docs/concepts/cluster-administration/addons/
09:49:27      k8s1-1.26:
09:49:27      k8s1-1.26: You can now join any number of control-plane nodes by copying certificate authorities
09:49:27      k8s1-1.26: and service account keys on each node and then running the following as root:
09:49:27      k8s1-1.26:
09:49:27      k8s1-1.26:   kubeadm join k8s1:6443 --token 258062.5d84c017c9b2796c \
09:49:27      k8s1-1.26: 	--discovery-token-ca-cert-hash sha256:85353dca76e5a72ab4e7f6ca9a42ff543e5c9edf90bf4349132f0b84f8647a15 \
09:49:27      k8s1-1.26: 	--control-plane
09:49:27      k8s1-1.26:
09:49:27      k8s1-1.26: Then you can join any number of worker nodes by running the following on each as root:
09:49:27      k8s1-1.26:
09:49:27      k8s1-1.26: kubeadm join k8s1:6443 --token 258062.5d84c017c9b2796c \
09:49:27      k8s1-1.26: 	--discovery-token-ca-cert-hash sha256:85353dca76e5a72ab4e7f6ca9a42ff543e5c9edf90bf4349132f0b84f8647a15
09:49:27      k8s1-1.26: error: taint "node-role.kubernetes.io/master" not found
09:49:27      k8s1-1.26: node/k8s1 untainted
09:49:27      k8s1-1.26: serviceaccount "coredns" deleted
09:49:27      k8s1-1.26: Warning: deleting cluster-scoped resources, not scoped to the provided namespace
09:49:27      k8s1-1.26: clusterrole.rbac.authorization.k8s.io "system:coredns" deleted
09:49:27      k8s1-1.26: clusterrolebinding.rbac.authorization.k8s.io "system:coredns" deleted
09:49:27      k8s1-1.26: configmap "coredns" deleted
09:49:27      k8s1-1.26: deployment.apps "coredns" deleted
09:49:27      k8s1-1.26: service "kube-dns" deleted
09:49:28      k8s1-1.26: serviceaccount/coredns created
09:49:28      k8s1-1.26: clusterrole.rbac.authorization.k8s.io/system:coredns created
09:49:28      k8s1-1.26: clusterrolebinding.rbac.authorization.k8s.io/system:coredns created
09:49:28      k8s1-1.26: configmap/coredns created
09:49:28      k8s1-1.26: deployment.apps/coredns created
09:49:28      k8s1-1.26: service/kube-dns created
09:49:28      k8s1-1.26: Downloading all container images needed for tests
09:49:28      k8s1-1.26: not cached in VM: 	docker.io/cilium/demo-client:1.0
09:49:28      k8s1-1.26: pulling: 		docker.io/cilium/demo-client:1.0
09:49:28      k8s1-1.26: not cached in VM: 	docker.io/cilium/demo-httpd:1.0
09:49:28      k8s1-1.26: pulling: 		docker.io/cilium/demo-httpd:1.0
09:49:28      k8s1-1.26: not cached in VM: 	docker.io/cilium/echoserver:1.10.1
09:49:28      k8s1-1.26: pulling: 		docker.io/cilium/echoserver:1.10.1
09:49:28      k8s1-1.26: not cached in VM: 	docker.io/cilium/echoserver-udp:v2020.01.30
09:49:28      k8s1-1.26: pulling: 		docker.io/cilium/echoserver-udp:v2020.01.30
09:49:28      k8s1-1.26: not cached in VM: 	docker.io/cilium/json-mock:1.2
09:49:28      k8s1-1.26: pulling: 		docker.io/cilium/json-mock:1.2
09:49:28      k8s1-1.26: not cached in VM: 	docker.io/cilium/kafkaclient:1.0
09:49:28      k8s1-1.26: pulling: 		docker.io/cilium/kafkaclient:1.0
09:49:28      k8s1-1.26: not cached in VM: 	docker.io/cilium/kafkaproxy:1.0
09:49:28      k8s1-1.26: pulling: 		docker.io/cilium/kafkaproxy:1.0
09:49:28      k8s1-1.26: not cached in VM: 	docker.io/cilium/migrate-svc-test:v0.0.2
09:49:28      k8s1-1.26: pulling: 		docker.io/cilium/migrate-svc-test:v0.0.2
09:49:28      k8s1-1.26: not cached in VM: 	docker.io/cilium/netperf:2.0
09:49:28      k8s1-1.26: pulling: 		docker.io/cilium/netperf:2.0
09:49:28      k8s1-1.26: not cached in VM: 	docker.io/cilium/startup-script:v3
09:49:28      k8s1-1.26: pulling: 		docker.io/cilium/startup-script:v3
09:49:28      k8s1-1.26: not cached in VM: 	docker.io/frrouting/frr:v7.5.1
09:49:28      k8s1-1.26: pulling: 		docker.io/frrouting/frr:v7.5.1
09:49:29      k8s1-1.26: not cached in VM: 	docker.io/istio/examples-bookinfo-details-v1:1.16.2
09:49:29      k8s1-1.26: pulling: 		docker.io/istio/examples-bookinfo-details-v1:1.16.2
09:49:29      k8s1-1.26: not cached in VM: 	docker.io/istio/examples-bookinfo-productpage-v1:0.2.3
09:49:29      k8s1-1.26: pulling: 		docker.io/istio/examples-bookinfo-productpage-v1:0.2.3
09:49:29      k8s1-1.26: not cached in VM: 	docker.io/istio/examples-bookinfo-ratings-v1:1.16.2
09:49:29      k8s1-1.26: pulling: 		docker.io/istio/examples-bookinfo-ratings-v1:1.16.2
09:49:29      k8s1-1.26: not cached in VM: 	docker.io/istio/examples-bookinfo-reviews-v1:1.6.0
09:49:29      k8s1-1.26: pulling: 		docker.io/istio/examples-bookinfo-reviews-v1:1.6.0
09:49:29      k8s1-1.26: not cached in VM: 	docker.io/istio/examples-bookinfo-reviews-v2:1.6.0
09:49:29      k8s1-1.26: pulling: 		docker.io/istio/examples-bookinfo-reviews-v2:1.6.0
09:49:29      k8s1-1.26: not cached in VM: 	docker.io/library/busybox:1.31.1
09:49:29      k8s1-1.26: pulling: 		docker.io/library/busybox:1.31.1
09:49:29      k8s1-1.26: not cached in VM: 	docker.io/tgraf/netperf:v1.0
09:49:29      k8s1-1.26: pulling: 		docker.io/tgraf/netperf:v1.0
09:49:29      k8s1-1.26: not cached in VM: 	quay.io/cilium/cilium-builder:1b8f97cf70e2a4e7b0609f259d9540523c50cc9f
09:49:29      k8s1-1.26: pulling: 		quay.io/cilium/cilium-builder:1b8f97cf70e2a4e7b0609f259d9540523c50cc9f
09:49:29      k8s1-1.26: not cached in VM: 	quay.io/cilium/istio_pilot:1.10.6
09:49:29      k8s1-1.26: pulling: 		quay.io/cilium/istio_pilot:1.10.6
09:49:29      k8s1-1.26: not cached in VM: 	quay.io/cilium/istio_proxy:1.10.6
09:49:29      k8s1-1.26: pulling: 		quay.io/cilium/istio_proxy:1.10.6
09:49:29      k8s1-1.26: not cached in VM: 	quay.io/cilium/log-gatherer:v1.1
09:49:29      k8s1-1.26: pulling: 		quay.io/cilium/log-gatherer:v1.1
09:49:29      k8s1-1.26: not cached in VM: 	quay.io/cilium/test-verifier:2ecf56b4ea57576e9d92d34407898e5d14e80aa3
09:49:29      k8s1-1.26: pulling: 		quay.io/cilium/test-verifier:2ecf56b4ea57576e9d92d34407898e5d14e80aa3
09:49:29      k8s1-1.26: not cached in VM: 	quay.io/coreos/etcd:v3.4.7
09:49:29      k8s1-1.26: pulling: 		quay.io/coreos/etcd:v3.4.7
09:54:58  Bringing machine 'k8s2-1.26' up with 'virtualbox' provider...
09:54:58  ==> k8s2-1.26: Running action triggers before up ...
09:54:58  ==> k8s2-1.26: Running trigger...
09:54:58      k8s2-1.26: Running local: Inline script
09:54:58      k8s2-1.26: bash -c 'i=1
09:54:58      k8s2-1.26: k8s_nodes="${K8S_NODES:-2}"
09:54:58      k8s2-1.26: while [ "$i" -le "$k8s_nodes" ]; do
09:54:58      k8s2-1.26:     VBoxManage natnetwork add --netname natnet$i --network <IP_ADDRESS>/16 --ipv6 on --enable
09:54:58      k8s2-1.26:     i=$((i+1))
09:54:58      k8s2-1.26: done 2>/dev/null
09:54:58      k8s2-1.26:
09:54:58      k8s2-1.26: res=0
09:54:58      k8s2-1.26: while [ "$res" == "0" ]; do
09:54:58      k8s2-1.26:     VBoxManage natnetwork remove --netname natnet$i
09:54:58      k8s2-1.26:     res=$?
09:54:58      k8s2-1.26:     i=$((i+1))
09:54:58      k8s2-1.26: done 2>/dev/null
09:54:58      k8s2-1.26: '
09:54:58  ==> k8s2-1.26: Cloning VM...
09:54:58
==> k8s2-1.26: Matching MAC address for NAT networking...
09:54:58  ==> k8s2-1.26: Checking if box 'cilium/ubuntu-next' version '154' is up to date...
09:54:58  ==> k8s2-1.26: Setting the name of the VM: test_k8s2-126_1669917298073_11022
09:54:58  ==> k8s2-1.26: Fixed port collision for 22 => 2222. Now on port 2200.
09:54:59  ==> k8s2-1.26: Clearing any previously set network interfaces...
09:54:59  ==> k8s2-1.26: Preparing network interfaces based on configuration...
09:54:59      k8s2-1.26: Adapter 1: nat
09:54:59      k8s2-1.26: Adapter 2: intnet
09:54:59      k8s2-1.26: Adapter 3: intnet
09:54:59      k8s2-1.26: Adapter 4: hostonly
09:54:59      k8s2-1.26: Adapter 5: hostonly
09:54:59  ==> k8s2-1.26: Forwarding ports...
09:54:59      k8s2-1.26: 22 (guest) => 2200 (host) (adapter 1)
09:54:59  ==> k8s2-1.26: Running 'pre-boot' VM customizations...
09:54:59  ==> k8s2-1.26: Booting VM...
09:55:00  ==> k8s2-1.26: Waiting for machine to boot. This may take a few minutes...
09:55:00      k8s2-1.26: SSH address: <IP_ADDRESS>:2200
09:55:00      k8s2-1.26: SSH username: vagrant
09:55:00      k8s2-1.26: SSH auth method: private key
09:55:50      k8s2-1.26:
09:55:50      k8s2-1.26: Vagrant insecure key detected. Vagrant will automatically replace
09:55:50      k8s2-1.26: this with a newly generated keypair for better security.
09:55:50      k8s2-1.26:
09:55:50      k8s2-1.26: Inserting generated public key within guest...
09:55:50      k8s2-1.26: Removing insecure key from the guest if it's present...
09:55:50      k8s2-1.26: Key inserted! Disconnecting and reconnecting using new SSH key...
09:55:50  ==> k8s2-1.26: Machine booted and ready!
09:55:50  ==> k8s2-1.26: Checking for guest additions in VM...
09:55:50  ==> k8s2-1.26: Setting hostname...
09:55:50  ==> k8s2-1.26: Configuring and enabling network interfaces...
09:56:00  ==> k8s2-1.26: Installing NFS client...
10:01:59  ==> k8s2-1.26: Exporting NFS shared folders...
10:01:59  ==> k8s2-1.26: Preparing to edit /etc/exports.  Your password will be stored unencrypted in /root/.docker/config.json.
10:01:59      k8s2-1.26: Configure a credential helper to remove this warning. See
10:01:59      k8s2-1.26: https://docs.docker.com/engine/reference/commandline/login/#credentials-store
10:01:59      k8s2-1.26:
10:01:59      k8s2-1.26: Login Succeeded
10:01:59      k8s2-1.26: /tmp/vagrant-shell: line 48: helm: command not found
10:01:59      k8s2-1.26: beginning trying up to 10 times function "wget -nv https://get.helm.sh/helm-v3.7.0-linux-amd64.tar.gz"
10:01:59      k8s2-1.26: ***************************************
10:01:59      k8s2-1.26: *
10:01:59      k8s2-1.26: *
10:01:59      k8s2-1.26: * on attempt 0 of function "wget -nv https://get.helm.sh/helm-v3.7.0-linux-amd64.tar.gz"
10:01:59      k8s2-1.26: *
10:01:59      k8s2-1.26: *
10:01:59      k8s2-1.26: ***************************************
10:01:59      k8s2-1.26: 2022-12-01 18:01:57 URL:https://get.helm.sh/helm-v3.7.0-linux-amd64.tar.gz [13861119/13861119] -> "helm-v3.7.0-linux-amd64.tar.gz" [1]
10:01:59      k8s2-1.26: running of "wget -nv https://get.helm.sh/helm-v3.7.0-linux-amd64.tar.gz" successful
10:01:59      k8s2-1.26:
10:01:59      k8s2-1.26:
10:01:59      k8s2-1.26:
10:01:59      k8s2-1.26: linux-amd64/
10:01:59      k8s2-1.26: linux-amd64/helm
10:01:59      k8s2-1.26: linux-amd64/LICENSE
10:01:59      k8s2-1.26: linux-amd64/README.md
10:01:59      k8s2-1.26: version.BuildInfo{Version:"v3.7.0", GitCommit:"eeac83883cb4014fe60267ec6373570374ce770b", GitTreeState:"clean", GoVersion:"go1.16.8"}
10:01:59      k8s2-1.26: updating /etc/resolv.conf
10:01:59      k8s2-1.26: beginning trying up to 10 times function "wget https://packages.cloud.google.com/apt/doc/apt-key.gpg"
10:01:59      k8s2-1.26: ***************************************
10:01:59      k8s2-1.26: *
10:01:59      k8s2-1.26: *
10:01:59      k8s2-1.26: * on attempt 0 of function "wget https://packages.cloud.google.com/apt/doc/apt-key.gpg"
10:01:59      k8s2-1.26: *
10:01:59      k8s2-1.26: *
10:01:59      k8s2-1.26: ***************************************
10:01:59      k8s2-1.26: --2022-12-01 18:01:59--  https://packages.cloud.google.com/apt/doc/apt-key.gpg
10:01:59      k8s2-1.26: Resolving packages.cloud.google.com (packages.cloud.google.com)... <IP_ADDRESS>, 2607:f8b0:4000:819::200e
10:01:59      k8s2-1.26: Connecting to packages.cloud.google.com (packages.cloud.google.com)|<IP_ADDRESS>|:443... connected.
10:01:59      k8s2-1.26: HTTP request sent, awaiting response... 200 OK
10:01:59      k8s2-1.26: Length: 2537 (2.5K) [application/octet-stream]
10:01:59      k8s2-1.26: Saving to: ‘apt-key.gpg’
10:01:59      k8s2-1.26:
10:01:59      k8s2-1.26:      0K ..                                                    100% 47.5M=0s
10:01:59      k8s2-1.26:
10:01:59      k8s2-1.26: 2022-12-01 18:01:59 (47.5 MB/s) - ‘apt-key.gpg’ saved [2537/2537]
10:01:59      k8s2-1.26:
10:01:59      k8s2-1.26: running of "wget https://packages.cloud.google.com/apt/doc/apt-key.gpg" successful
10:01:59      k8s2-1.26:
10:01:59      k8s2-1.26:
10:01:59      k8s2-1.26:
10:01:59      k8s2-1.26: Warning: apt-key output should not be parsed (stdout is not a terminal)
10:01:59      k8s2-1.26: OK
10:02:01      k8s2-1.26: Reading package lists...
10:02:01      k8s2-1.26: Building dependency tree...
10:02:01      k8s2-1.26: Reading state information...
10:02:02      k8s2-1.26: conntrack is already the newest version (1:1.4.5-2).
10:02:02      k8s2-1.26: 0 upgraded, 0 newly installed, 0 to remove and 71 not upgraded.
10:02:02      k8s2-1.26: Hit:2 https://download.docker.com/linux/ubuntu focal InRelease
10:02:02      k8s2-1.26: Hit:3 https://deb.nodesource.com/node_12.x focal InRelease
10:02:02      k8s2-1.26: Hit:1 https://packages.cloud.google.com/apt kubernetes-xenial InRelease
10:02:03      k8s2-1.26: Hit:4 http://us.archive.ubuntu.com/ubuntu focal InRelease
10:02:03      k8s2-1.26: Hit:5 http://us.archive.ubuntu.com/ubuntu focal-updates InRelease
10:02:03      k8s2-1.26: Hit:6 http://us.archive.ubuntu.com/ubuntu focal-backports InRelease
10:02:03      k8s2-1.26: Hit:7 http://us.archive.ubuntu.com/ubuntu focal-security InRelease
10:02:05      k8s2-1.26: Reading package lists...
10:02:05      k8s2-1.26: Reading package lists...
10:02:05      k8s2-1.26: Building dependency tree...
10:02:05      k8s2-1.26: Reading state information...
10:02:05      k8s2-1.26: E: Version '1.26.0-rc.0*' for 'kubelet' was not found
10:02:05      k8s2-1.26: E: Version '1.26.0-rc.0*' for 'kubeadm' was not found
10:02:05      k8s2-1.26: E: Version '1.26.0-rc.0*' for 'kubectl' was not found
10:02:05      k8s2-1.26: falling back on binary k8s install
10:02:07      k8s2-1.26: 'kubeadm' -> '/usr/bin/kubeadm'
10:02:07      k8s2-1.26: 'kubectl' -> '/usr/bin/kubectl'
10:02:07      k8s2-1.26: 'kubelet' -> '/usr/bin/kubelet'
10:02:08      k8s2-1.26: Created symlink /etc/systemd/system/multi-user.target.wants/kubelet.service → /etc/systemd/system/kubelet.service.
10:02:08      k8s2-1.26: KUBELET_EXTRA_ARGS="--fail-swap-on=false"
10:02:08      k8s2-1.26: [preflight] Running pre-flight checks
10:02:08      k8s2-1.26: 	[WARNING Swap]: swap is enabled; production deployments should disable swap unless testing the NodeSwap feature gate of the kubelet
10:02:08      k8s2-1.26: [preflight] Reading configuration from the cluster...
10:02:08      k8s2-1.26: [preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
10:02:09      k8s2-1.26: W1201 18:02:08.856193   11485 configset.go:78] Warning: No kubeproxy.config.k8s.io/v1alpha1 config is loaded. Continuing without it: configmaps "kube-proxy" is forbidden: User "system:bootstrap:258062" cannot get resource "configmaps" in API group "" in the namespace "kube-system"
10:02:09      k8s2-1.26: [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
10:02:09      k8s2-1.26: [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
10:02:09      k8s2-1.26: [kubelet-start] Starting the kubelet
10:02:09      k8s2-1.26: [kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...
10:02:23      k8s2-1.26:
10:02:23      k8s2-1.26: This node has joined the cluster:
10:02:23      k8s2-1.26: * Certificate signing request was sent to apiserver and a response was received.
10:02:23      k8s2-1.26: * The Kubelet was informed of the new secure connection details.
10:02:23      k8s2-1.26:
10:02:23      k8s2-1.26: Run 'kubectl get nodes' on the control-plane to see this node join the cluster.
10:02:23      k8s2-1.26:
10:02:23  Bringing machine 'k8s3-1.26' up with 'virtualbox' provider...
10:02:23  ==> k8s3-1.26: Running action triggers before up ...
10:02:23  ==> k8s3-1.26: Running trigger...
10:02:23      k8s3-1.26: Running local: Inline script
10:02:23      k8s3-1.26: bash -c 'i=1
10:02:23      k8s3-1.26: k8s_nodes="${K8S_NODES:-2}"
10:02:23      k8s3-1.26: while [ "$i" -le "$k8s_nodes" ]; do
10:02:23      k8s3-1.26:     VBoxManage natnetwork add --netname natnet$i --network <IP_ADDRESS>/16 --ipv6 on --enable
10:02:23      k8s3-1.26:     i=$((i+1))
10:02:23      k8s3-1.26: done 2>/dev/null
10:02:23      k8s3-1.26:
10:02:23      k8s3-1.26: res=0
10:02:23      k8s3-1.26: while [ "$res" == "0" ]; do
10:02:23      k8s3-1.26:     VBoxManage natnetwork remove --netname natnet$i
10:02:23      k8s3-1.26:     res=$?
10:02:23      k8s3-1.26:     i=$((i+1))
10:02:23      k8s3-1.26: done 2>/dev/null
10:02:23      k8s3-1.26: '
10:02:24  ==> k8s3-1.26: Cloning VM...
10:02:24
==> k8s3-1.26: Matching MAC address for NAT networking...
10:02:24  ==> k8s3-1.26: Checking if box 'cilium/ubuntu-next' version '154' is up to date...
10:02:24  ==> k8s3-1.26: Setting the name of the VM: test_k8s3-126_1669917744801_491
10:02:25  ==> k8s3-1.26: Fixed port collision for 22 => 2222. Now on port 2201.
10:02:25  ==> k8s3-1.26: Clearing any previously set network interfaces...
10:02:26  ==> k8s3-1.26: Preparing network interfaces based on configuration...
10:02:26      k8s3-1.26: Adapter 1: nat
10:02:26      k8s3-1.26: Adapter 2: intnet
10:02:26      k8s3-1.26: Adapter 3: intnet
10:02:26      k8s3-1.26: Adapter 4: hostonly
10:02:26      k8s3-1.26: Adapter 5: hostonly
10:02:26  ==> k8s3-1.26: Forwarding ports...
10:02:26      k8s3-1.26: 22 (guest) => 2201 (host) (adapter 1)
10:02:26  ==> k8s3-1.26: Running 'pre-boot' VM customizations...
10:02:26  ==> k8s3-1.26: Booting VM...
10:02:27  ==> k8s3-1.26: Waiting for machine to boot. This may take a few minutes...
10:02:27      k8s3-1.26: SSH address: <IP_ADDRESS>:2201
10:02:27      k8s3-1.26: SSH username: vagrant
10:02:27      k8s3-1.26: SSH auth method: private key
10:03:17      k8s3-1.26: Warning: Connection reset. Retrying...
10:03:17      k8s3-1.26:
10:03:17      k8s3-1.26: Vagrant insecure key detected. Vagrant will automatically replace
10:03:17      k8s3-1.26: this with a newly generated keypair for better security.
10:03:17      k8s3-1.26:
10:03:17      k8s3-1.26: Inserting generated public key within guest...
10:03:17      k8s3-1.26: Removing insecure key from the guest if it's present...
10:03:17      k8s3-1.26: Key inserted! Disconnecting and reconnecting using new SSH key...
10:03:18  ==> k8s3-1.26: Machine booted and ready!
10:03:18  ==> k8s3-1.26: Checking for guest additions in VM...
10:03:18  ==> k8s3-1.26: Setting hostname...
10:03:18  ==> k8s3-1.26: Configuring and enabling network interfaces...
10:03:39  ==> k8s3-1.26: Installing NFS client...

First VM took about 12 mins to bootstrap:
09:42:28
�[KProgress: 10%
�[KProgress: 20%
�[KProgress: 30%
�[KProgress: 40%
�[KProgress: 50%
�[KProgress: 60%
�[KProgress: 90%
�[K==> k8s1-1.26: Cloning VM...
09:42:28

...
09:54:58  ==> k8s2-1.26: Cloning VM...

The third VM starts about 8 mins after the second:
10:02:24  ==> k8s3-1.26: Cloning VM...

Even if all three VMs took 8 mins to spin up, that is very close to the 25m timeout.

Similar run on master recently took 13m for the whole process:
https://jenkins.cilium.io/job/cilium-master-k8s-1.26-kernel-net-next/2392/execution/node/88/log/
17:07:12  + ./print-node-ip.sh
17:07:12  + CILIUM_REGISTRY=<IP_ADDRESS> timeout 25m ./vagrant-ci-start.sh
17:07:12  restarting portmap and nfs-kernel-server services to combat nfs server issues
17:07:13  destroying vms in case this is a retry
17:07:14  ==> k8s1-1.26: VM not created. Moving on...
17:07:15  ==> k8s2-1.26: VM not created. Moving on...
17:07:15  ==> k8s3-1.26: VM not created. Moving on...
17:07:15  boxes available on the node
17:07:15  cilium/ubuntu      (virtualbox, 232)
17:07:15  cilium/ubuntu-4-19 (virtualbox, 69)
17:07:15  cilium/ubuntu-5-4  (virtualbox, 35)
17:07:15  cilium/ubuntu-next (virtualbox, 154)
17:07:15  starting vms
17:07:16  Bringing machine 'k8s1-1.26' up with 'virtualbox' provider...
17:07:16  ==> k8s1-1.26: Running action triggers before up ...
17:07:16  ==> k8s1-1.26: Running trigger...
17:07:16      k8s1-1.26: Running local: Inline script
17:07:16      k8s1-1.26: bash -c 'i=1
17:07:16      k8s1-1.26: k8s_nodes="${K8S_NODES:-2}"
17:07:16      k8s1-1.26: while [ "$i" -le "$k8s_nodes" ]; do
17:07:16      k8s1-1.26:     VBoxManage natnetwork add --netname natnet$i --network <IP_ADDRESS>/16 --ipv6 on --enable
17:07:16      k8s1-1.26:     i=$((i+1))
17:07:16      k8s1-1.26: done 2>/dev/null
17:07:16      k8s1-1.26:
17:07:16      k8s1-1.26: res=0
17:07:16      k8s1-1.26: while [ "$res" == "0" ]; do
17:07:16      k8s1-1.26:     VBoxManage natnetwork remove --netname natnet$i
17:07:16      k8s1-1.26:     res=$?
17:07:16      k8s1-1.26:     i=$((i+1))
17:07:16      k8s1-1.26: done 2>/dev/null
17:07:16      k8s1-1.26: '
17:07:17  ==> k8s1-1.26: Preparing master VM for linked clones...
17:07:17      k8s1-1.26: This is a one time operation. Once the master VM is prepared,
17:07:17      k8s1-1.26: it will be used as a base for linked clones, making the creation
17:07:17      k8s1-1.26: of new VMs take milliseconds on a modern system.
17:07:17  ==> k8s1-1.26: Importing base box 'cilium/ubuntu-next'...
17:09:23
Progress: 10%
Progress: 20%
Progress: 30%
Progress: 40%
Progress: 50%
Progress: 60%
Progress: 90%
==> k8s1-1.26: Cloning VM...
17:09:23
==> k8s1-1.26: Matching MAC address for NAT networking...
17:09:23  ==> k8s1-1.26: Checking if box 'cilium/ubuntu-next' version '154' is up to date...
17:09:24  ==> k8s1-1.26: Setting the name of the VM: test_k8s1-126_1669770563999_26647
17:09:24  Vagrant is currently configured to create VirtualBox synced folders with
17:09:24  the `SharedFoldersEnableSymlinksCreate` option enabled. If the Vagrant
17:09:24  guest is not trusted, you may want to disable this option. For more
17:09:24  information on this option, please refer to the VirtualBox manual:
17:09:24
17:09:24    https://www.virtualbox.org/manual/ch04.html#sharedfolders
17:09:24
17:09:24  This option can be disabled globally with an environment variable:
17:09:24
17:09:24    VAGRANT_DISABLE_VBOXSYMLINKCREATE=1
17:09:24
17:09:24  or on a per folder basis within the Vagrantfile:
17:09:24
17:09:24    config.vm.synced_folder '/host/path', '/guest/path', SharedFoldersEnableSymlinksCreate: false
17:09:25  ==> k8s1-1.26: Clearing any previously set network interfaces...
17:09:25  ==> k8s1-1.26: Preparing network interfaces based on configuration...
17:09:25      k8s1-1.26: Adapter 1: nat
17:09:25      k8s1-1.26: Adapter 2: intnet
17:09:25      k8s1-1.26: Adapter 3: intnet
17:09:25      k8s1-1.26: Adapter 4: hostonly
17:09:25      k8s1-1.26: Adapter 5: hostonly
17:09:25  ==> k8s1-1.26: Forwarding ports...
17:09:25      k8s1-1.26: 3000 (guest) => 3000 (host) (adapter 1)
17:09:25      k8s1-1.26: 6443 (guest) => 9443 (host) (adapter 1)
17:09:25      k8s1-1.26: 22 (guest) => 2222 (host) (adapter 1)
17:09:25  ==> k8s1-1.26: Running 'pre-boot' VM customizations...
17:09:26  ==> k8s1-1.26: Booting VM...
17:09:26  ==> k8s1-1.26: Waiting for machine to boot. This may take a few minutes...
17:09:26      k8s1-1.26: SSH address: <IP_ADDRESS>:2222
17:09:26      k8s1-1.26: SSH username: vagrant
17:09:26      k8s1-1.26: SSH auth method: private key
17:10:08      k8s1-1.26:
17:10:08      k8s1-1.26: Vagrant insecure key detected. Vagrant will automatically replace
17:10:08      k8s1-1.26: this with a newly generated keypair for better security.
17:10:08      k8s1-1.26:
17:10:08      k8s1-1.26: Inserting generated public key within guest...
17:10:08      k8s1-1.26: Removing insecure key from the guest if it's present...
17:10:08      k8s1-1.26: Key inserted! Disconnecting and reconnecting using new SSH key...
17:10:08  ==> k8s1-1.26: Machine booted and ready!
17:10:08  ==> k8s1-1.26: Checking for guest additions in VM...
17:10:08  ==> k8s1-1.26: Setting hostname...
17:10:08  ==> k8s1-1.26: Configuring and enabling network interfaces...
17:10:16  ==> k8s1-1.26: Installing NFS client...
17:10:34  ==> k8s1-1.26: Exporting NFS shared folders...
17:10:34  ==> k8s1-1.26: Preparing to edit /etc/exports.  Your password will be stored unencrypted in /root/.docker/config.json.
17:10:38      k8s1-1.26: Configure a credential helper to remove this warning. See
17:10:38      k8s1-1.26: https://docs.docker.com/engine/reference/commandline/login/#credentials-store
17:10:38      k8s1-1.26:
17:10:38      k8s1-1.26: Login Succeeded
17:10:38      k8s1-1.26: /tmp/vagrant-shell: line 48: helm: command not found
17:10:38      k8s1-1.26: beginning trying up to 10 times function "wget -nv https://get.helm.sh/helm-v3.7.0-linux-amd64.tar.gz"
17:10:38      k8s1-1.26: ***************************************
17:10:38      k8s1-1.26: *
17:10:38      k8s1-1.26: *
17:10:38      k8s1-1.26: * on attempt 0 of function "wget -nv https://get.helm.sh/helm-v3.7.0-linux-amd64.tar.gz"
17:10:38      k8s1-1.26: *
17:10:38      k8s1-1.26: *
17:10:38      k8s1-1.26: ***************************************
17:10:38      k8s1-1.26: 2022-11-30 01:10:38 URL:https://get.helm.sh/helm-v3.7.0-linux-amd64.tar.gz [13861119/13861119] -> "helm-v3.7.0-linux-amd64.tar.gz" [1]
17:10:38      k8s1-1.26: running of "wget -nv https://get.helm.sh/helm-v3.7.0-linux-amd64.tar.gz" successful
17:10:38      k8s1-1.26:
17:10:38      k8s1-1.26:
17:10:38      k8s1-1.26:
17:10:38      k8s1-1.26: linux-amd64/
17:10:38      k8s1-1.26: linux-amd64/helm
17:10:38      k8s1-1.26: linux-amd64/LICENSE
17:10:38      k8s1-1.26: linux-amd64/README.md
17:10:38      k8s1-1.26: version.BuildInfo{Version:"v3.7.0", GitCommit:"eeac83883cb4014fe60267ec6373570374ce770b", GitTreeState:"clean", GoVersion:"go1.16.8"}
17:10:40      k8s1-1.26: updating /etc/resolv.conf
17:10:40      k8s1-1.26: beginning trying up to 10 times function "wget https://packages.cloud.google.com/apt/doc/apt-key.gpg"
17:10:40      k8s1-1.26: ***************************************
17:10:40      k8s1-1.26: *
17:10:40      k8s1-1.26: *
17:10:40      k8s1-1.26: * on attempt 0 of function "wget https://packages.cloud.google.com/apt/doc/apt-key.gpg"
17:10:40      k8s1-1.26: *
17:10:40      k8s1-1.26: *
17:10:40      k8s1-1.26: ***************************************
17:10:40      k8s1-1.26: --2022-11-30 01:10:39--  https://packages.cloud.google.com/apt/doc/apt-key.gpg
17:10:40      k8s1-1.26: Resolving packages.cloud.google.com (packages.cloud.google.com)... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
17:10:40      k8s1-1.26: Connecting to packages.cloud.google.com (packages.cloud.google.com)|<IP_ADDRESS>|:443... connected.
17:10:40      k8s1-1.26: HTTP request sent, awaiting response... 200 OK
17:10:40      k8s1-1.26: Length: 2537 (2.5K) [application/octet-stream]
17:10:40      k8s1-1.26: Saving to: ‘apt-key.gpg’
17:10:40      k8s1-1.26:
17:10:40      k8s1-1.26:      0K ..                                                    100% 62.5M=0s
17:10:40      k8s1-1.26:
17:10:40      k8s1-1.26: 2022-11-30 01:10:39 (62.5 MB/s) - ‘apt-key.gpg’ saved [2537/2537]
17:10:40      k8s1-1.26:
17:10:40      k8s1-1.26: running of "wget https://packages.cloud.google.com/apt/doc/apt-key.gpg" successful
17:10:40      k8s1-1.26:
17:10:40      k8s1-1.26:
17:10:40      k8s1-1.26:
17:10:40      k8s1-1.26: Warning: apt-key output should not be parsed (stdout is not a terminal)
17:10:40      k8s1-1.26: OK
17:10:44      k8s1-1.26: Reading package lists...
17:10:44      k8s1-1.26: Building dependency tree...
17:10:44      k8s1-1.26: Reading state information...
17:10:44      k8s1-1.26: conntrack is already the newest version (1:1.4.5-2).
17:10:44      k8s1-1.26: 0 upgraded, 0 newly installed, 0 to remove and 70 not upgraded.
17:10:44      k8s1-1.26: Hit:2 https://download.docker.com/linux/ubuntu focal InRelease
17:10:44      k8s1-1.26: Hit:3 https://deb.nodesource.com/node_12.x focal InRelease
17:10:44      k8s1-1.26: Hit:4 http://us.archive.ubuntu.com/ubuntu focal InRelease
17:10:44      k8s1-1.26: Hit:1 https://packages.cloud.google.com/apt kubernetes-xenial InRelease
17:10:44      k8s1-1.26: Hit:5 http://us.archive.ubuntu.com/ubuntu focal-updates InRelease
17:10:44      k8s1-1.26: Hit:6 http://us.archive.ubuntu.com/ubuntu focal-backports InRelease
17:10:44      k8s1-1.26: Hit:7 http://us.archive.ubuntu.com/ubuntu focal-security InRelease
17:10:46      k8s1-1.26: Reading package lists...
17:10:46      k8s1-1.26: Reading package lists...
17:10:46      k8s1-1.26: Building dependency tree...
17:10:46      k8s1-1.26: Reading state information...
17:10:46      k8s1-1.26: E: Version '1.26.0-rc.0*' for 'kubelet' was not found
17:10:46      k8s1-1.26: E: Version '1.26.0-rc.0*' for 'kubeadm' was not found
17:10:46      k8s1-1.26: E: Version '1.26.0-rc.0*' for 'kubectl' was not found
17:10:46      k8s1-1.26: falling back on binary k8s install
17:10:49      k8s1-1.26: 'kubeadm' -> '/usr/bin/kubeadm'
17:10:49      k8s1-1.26: 'kubectl' -> '/usr/bin/kubectl'
17:10:49      k8s1-1.26: 'kubelet' -> '/usr/bin/kubelet'
17:10:49      k8s1-1.26: Created symlink /etc/systemd/system/multi-user.target.wants/kubelet.service → /etc/systemd/system/kubelet.service.
17:10:49      k8s1-1.26: KUBELET_EXTRA_ARGS="--fail-swap-on=false"
17:10:50      k8s1-1.26: W1130 01:10:50.124213   11466 initconfiguration.go:331] [config] WARNING: Ignored YAML document with GroupVersionKind kubeadm.k8s.io/v1beta3, Kind=JoinConfiguration
17:10:50      k8s1-1.26: [init] Using Kubernetes version: v1.26.0-rc.0
17:10:50      k8s1-1.26: [preflight] Running pre-flight checks
17:10:50      k8s1-1.26: 	[WARNING Swap]: swap is enabled; production deployments should disable swap unless testing the NodeSwap feature gate of the kubelet
17:10:51      k8s1-1.26: [preflight] Pulling images required for setting up a Kubernetes cluster
17:10:51      k8s1-1.26: [preflight] This might take a minute or two, depending on the speed of your internet connection
17:10:51      k8s1-1.26: [preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
17:10:51      k8s1-1.26: W1130 01:10:50.773135   11466 images.go:80] could not find officially supported version of etcd for Kubernetes v1.26.0-rc.0, falling back to the nearest etcd version (3.5.5-0)
17:11:41      k8s1-1.26: [certs] Using certificateDir folder "/etc/kubernetes/pki"
17:11:41      k8s1-1.26: [certs] Generating "ca" certificate and key
17:11:41      k8s1-1.26: [certs] Generating "apiserver" certificate and key
17:11:41      k8s1-1.26: [certs] apiserver serving cert is signed for DNS names [k8s1 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [<IP_ADDRESS> <IP_ADDRESS>]
17:11:41      k8s1-1.26: [certs] Generating "apiserver-kubelet-client" certificate and key
17:11:41      k8s1-1.26: [certs] Generating "front-proxy-ca" certificate and key
17:11:41      k8s1-1.26: [certs] Generating "front-proxy-client" certificate and key
17:11:41      k8s1-1.26: [certs] Generating "etcd/ca" certificate and key
17:11:41      k8s1-1.26: [certs] Generating "etcd/server" certificate and key
17:11:41      k8s1-1.26: [certs] etcd/server serving cert is signed for DNS names [k8s1 localhost] and IPs [<IP_ADDRESS> <IP_ADDRESS> ::1]
17:11:41      k8s1-1.26: [certs] Generating "etcd/peer" certificate and key
17:11:41      k8s1-1.26: [certs] etcd/peer serving cert is signed for DNS names [k8s1 localhost] and IPs [<IP_ADDRESS> <IP_ADDRESS> ::1]
17:11:41      k8s1-1.26: [certs] Generating "etcd/healthcheck-client" certificate and key
17:11:41      k8s1-1.26: [certs] Generating "apiserver-etcd-client" certificate and key
17:11:41      k8s1-1.26: [certs] Generating "sa" key and public key
17:11:41      k8s1-1.26: [kubeconfig] Using kubeconfig folder "/etc/kubernetes"
17:11:41      k8s1-1.26: [kubeconfig] Writing "admin.conf" kubeconfig file
17:11:41      k8s1-1.26: [kubeconfig] Writing "kubelet.conf" kubeconfig file
17:11:41      k8s1-1.26: [kubeconfig] Writing "controller-manager.conf" kubeconfig file
17:11:41      k8s1-1.26: [kubeconfig] Writing "scheduler.conf" kubeconfig file
17:11:41      k8s1-1.26: [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
17:11:41      k8s1-1.26: [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
17:11:41      k8s1-1.26: [kubelet-start] Starting the kubelet
17:11:41      k8s1-1.26: [control-plane] Using manifest folder "/etc/kubernetes/manifests"
17:11:41      k8s1-1.26: [control-plane] Creating static Pod manifest for "kube-apiserver"
17:11:41      k8s1-1.26: [control-plane] Creating static Pod manifest for "kube-controller-manager"
17:11:41      k8s1-1.26: [control-plane] Creating static Pod manifest for "kube-scheduler"
17:11:41      k8s1-1.26: [etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
17:11:41      k8s1-1.26: W1130 01:11:40.646274   11466 images.go:80] could not find officially supported version of etcd for Kubernetes v1.26.0-rc.0, falling back to the nearest etcd version (3.5.5-0)
17:11:41      k8s1-1.26: [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
17:11:45      k8s1-1.26: [apiclient] All control plane components are healthy after 5.001605 seconds
17:11:45      k8s1-1.26: [upload-config] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
17:11:45      k8s1-1.26: [kubelet] Creating a ConfigMap "kubelet-config" in namespace kube-system with the configuration for the kubelets in the cluster
17:11:46      k8s1-1.26: [upload-certs] Skipping phase. Please see --upload-certs
17:11:46      k8s1-1.26: [mark-control-plane] Marking the node k8s1 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]
17:11:46      k8s1-1.26: [mark-control-plane] Marking the node k8s1 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]
17:11:47      k8s1-1.26: [bootstrap-token] Using token: 258062.5d84c017c9b2796c
17:11:47      k8s1-1.26: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles
17:11:47      k8s1-1.26: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes
17:11:47      k8s1-1.26: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials
17:11:47      k8s1-1.26: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token
17:11:47      k8s1-1.26: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster
17:11:47      k8s1-1.26: [bootstrap-token] Creating the "cluster-info" ConfigMap in the "kube-public" namespace
17:11:47      k8s1-1.26: [kubelet-finalize] Updating "/etc/kubernetes/kubelet.conf" to point to a rotatable kubelet client certificate and key
17:11:47      k8s1-1.26: [addons] Applied essential addon: CoreDNS
17:11:47      k8s1-1.26:
17:11:47      k8s1-1.26: Your Kubernetes control-plane has initialized successfully!
17:11:47      k8s1-1.26:
17:11:47      k8s1-1.26: To start using your cluster, you need to run the following as a regular user:
17:11:47      k8s1-1.26:
17:11:47      k8s1-1.26:   mkdir -p $HOME/.kube
17:11:47      k8s1-1.26:   sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
17:11:47      k8s1-1.26:   sudo chown $(id -u):$(id -g) $HOME/.kube/config
17:11:47      k8s1-1.26:
17:11:47      k8s1-1.26: Alternatively, if you are the root user, you can run:
17:11:47      k8s1-1.26:
17:11:47      k8s1-1.26:   export KUBECONFIG=/etc/kubernetes/admin.conf
17:11:47      k8s1-1.26:
17:11:47      k8s1-1.26: You should now deploy a pod network to the cluster.
17:11:47      k8s1-1.26: Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
17:11:47      k8s1-1.26:   https://kubernetes.io/docs/concepts/cluster-administration/addons/
17:11:47      k8s1-1.26:
17:11:47      k8s1-1.26: You can now join any number of control-plane nodes by copying certificate authorities
17:11:47      k8s1-1.26: and service account keys on each node and then running the following as root:
17:11:47      k8s1-1.26:
17:11:47      k8s1-1.26:   kubeadm join k8s1:6443 --token 258062.5d84c017c9b2796c \
17:11:47      k8s1-1.26: 	--discovery-token-ca-cert-hash sha256:805feaf97e9d664a2d5c12671e17a158a231b9e2dcb4905d26b58577483331f7 \
17:11:47      k8s1-1.26: 	--control-plane
17:11:47      k8s1-1.26:
17:11:47      k8s1-1.26: Then you can join any number of worker nodes by running the following on each as root:
17:11:47      k8s1-1.26:
17:11:47      k8s1-1.26: kubeadm join k8s1:6443 --token 258062.5d84c017c9b2796c \
17:11:47      k8s1-1.26: 	--discovery-token-ca-cert-hash sha256:805feaf97e9d664a2d5c12671e17a158a231b9e2dcb4905d26b58577483331f7
17:11:47      k8s1-1.26: error: taint "node-role.kubernetes.io/master" not found
17:11:47      k8s1-1.26: node/k8s1 untainted
17:11:47      k8s1-1.26: serviceaccount "coredns" deleted
17:11:47      k8s1-1.26: Warning: deleting cluster-scoped resources, not scoped to the provided namespace
17:11:47      k8s1-1.26: clusterrole.rbac.authorization.k8s.io "system:coredns" deleted
17:11:47      k8s1-1.26: clusterrolebinding.rbac.authorization.k8s.io "system:coredns" deleted
17:11:47      k8s1-1.26: configmap "coredns" deleted
17:11:47      k8s1-1.26: deployment.apps "coredns" deleted
17:11:47      k8s1-1.26: service "kube-dns" deleted
17:11:47      k8s1-1.26: serviceaccount/coredns created
17:11:47      k8s1-1.26: clusterrole.rbac.authorization.k8s.io/system:coredns created
17:11:47      k8s1-1.26: clusterrolebinding.rbac.authorization.k8s.io/system:coredns created
17:11:47      k8s1-1.26: configmap/coredns created
17:11:47      k8s1-1.26: deployment.apps/coredns created
17:11:47      k8s1-1.26: service/kube-dns created
17:11:47      k8s1-1.26: Downloading all container images needed for tests
17:11:48      k8s1-1.26: not cached in VM: 	docker.io/cilium/demo-client:1.0
17:11:48      k8s1-1.26: pulling: 		docker.io/cilium/demo-client:1.0
17:11:48      k8s1-1.26: not cached in VM: 	docker.io/cilium/demo-httpd:1.0
17:11:48      k8s1-1.26: pulling: 		docker.io/cilium/demo-httpd:1.0
17:11:48      k8s1-1.26: not cached in VM: 	docker.io/cilium/echoserver:1.10.1
17:11:48      k8s1-1.26: pulling: 		docker.io/cilium/echoserver:1.10.1
17:11:48      k8s1-1.26: not cached in VM: 	docker.io/cilium/echoserver-udp:v2020.01.30
17:11:48      k8s1-1.26: pulling: 		docker.io/cilium/echoserver-udp:v2020.01.30
17:11:48      k8s1-1.26: not cached in VM: 	docker.io/cilium/json-mock:1.2
17:11:48      k8s1-1.26: pulling: 		docker.io/cilium/json-mock:1.2
17:11:48      k8s1-1.26: not cached in VM: 	docker.io/cilium/kafkaclient:1.0
17:11:48      k8s1-1.26: pulling: 		docker.io/cilium/kafkaclient:1.0
17:11:48      k8s1-1.26: not cached in VM: 	docker.io/cilium/kafkaproxy:1.0
17:11:48      k8s1-1.26: pulling: 		docker.io/cilium/kafkaproxy:1.0
17:11:48      k8s1-1.26: not cached in VM: 	docker.io/cilium/migrate-svc-test:v0.0.2
17:11:48      k8s1-1.26: pulling: 		docker.io/cilium/migrate-svc-test:v0.0.2
17:11:48      k8s1-1.26: not cached in VM: 	docker.io/cilium/netperf:2.0
17:11:48      k8s1-1.26: pulling: 		docker.io/cilium/netperf:2.0
17:11:48      k8s1-1.26: not cached in VM: 	docker.io/cilium/startup-script:v3
17:11:48      k8s1-1.26: pulling: 		docker.io/cilium/startup-script:v3
17:11:48      k8s1-1.26: not cached in VM: 	docker.io/frrouting/frr:v7.5.1
17:11:48      k8s1-1.26: pulling: 		docker.io/frrouting/frr:v7.5.1
17:11:48      k8s1-1.26: not cached in VM: 	docker.io/istio/examples-bookinfo-details-v1:1.16.2
17:11:48      k8s1-1.26: pulling: 		docker.io/istio/examples-bookinfo-details-v1:1.16.2
17:11:48      k8s1-1.26: not cached in VM: 	docker.io/istio/examples-bookinfo-productpage-v1:0.2.3
17:11:48      k8s1-1.26: pulling: 		docker.io/istio/examples-bookinfo-productpage-v1:0.2.3
17:11:48      k8s1-1.26: not cached in VM: 	docker.io/istio/examples-bookinfo-ratings-v1:1.16.2
17:11:48      k8s1-1.26: pulling: 		docker.io/istio/examples-bookinfo-ratings-v1:1.16.2
17:11:48      k8s1-1.26: not cached in VM: 	docker.io/istio/examples-bookinfo-reviews-v1:1.6.0
17:11:48      k8s1-1.26: pulling: 		docker.io/istio/examples-bookinfo-reviews-v1:1.6.0
17:11:48      k8s1-1.26: not cached in VM: 	docker.io/istio/examples-bookinfo-reviews-v2:1.6.0
17:11:48      k8s1-1.26: pulling: 		docker.io/istio/examples-bookinfo-reviews-v2:1.6.0
17:11:48      k8s1-1.26: not cached in VM: 	docker.io/library/busybox:1.31.1
17:11:48      k8s1-1.26: pulling: 		docker.io/library/busybox:1.31.1
17:11:48      k8s1-1.26: not cached in VM: 	docker.io/tgraf/netperf:v1.0
17:11:48      k8s1-1.26: pulling: 		docker.io/tgraf/netperf:v1.0
17:11:48      k8s1-1.26: not cached in VM: 	quay.io/cilium/cilium-builder:1b8f97cf70e2a4e7b0609f259d9540523c50cc9f
17:11:48      k8s1-1.26: pulling: 		quay.io/cilium/cilium-builder:1b8f97cf70e2a4e7b0609f259d9540523c50cc9f
17:11:48      k8s1-1.26: not cached in VM: 	quay.io/cilium/istio_pilot:1.10.6
17:11:48      k8s1-1.26: pulling: 		quay.io/cilium/istio_pilot:1.10.6
17:11:48      k8s1-1.26: not cached in VM: 	quay.io/cilium/istio_proxy:1.10.6
17:11:48      k8s1-1.26: pulling: 		quay.io/cilium/istio_proxy:1.10.6
17:11:48      k8s1-1.26: not cached in VM: 	quay.io/cilium/log-gatherer:v1.1
17:11:48      k8s1-1.26: pulling: 		quay.io/cilium/log-gatherer:v1.1
17:11:48      k8s1-1.26: not cached in VM: 	quay.io/cilium/test-verifier:2ecf56b4ea57576e9d92d34407898e5d14e80aa3
17:11:48      k8s1-1.26: pulling: 		quay.io/cilium/test-verifier:2ecf56b4ea57576e9d92d34407898e5d14e80aa3
17:11:48      k8s1-1.26: not cached in VM: 	quay.io/coreos/etcd:v3.4.7
17:11:48      k8s1-1.26: pulling: 		quay.io/coreos/etcd:v3.4.7
17:17:02  Bringing machine 'k8s2-1.26' up with 'virtualbox' provider...
17:17:02  ==> k8s2-1.26: Running action triggers before up ...
17:17:02  ==> k8s2-1.26: Running trigger...
17:17:02      k8s2-1.26: Running local: Inline script
17:17:02      k8s2-1.26: bash -c 'i=1
17:17:02      k8s2-1.26: k8s_nodes="${K8S_NODES:-2}"
17:17:02      k8s2-1.26: while [ "$i" -le "$k8s_nodes" ]; do
17:17:02      k8s2-1.26:     VBoxManage natnetwork add --netname natnet$i --network <IP_ADDRESS>/16 --ipv6 on --enable
17:17:02      k8s2-1.26:     i=$((i+1))
17:17:02      k8s2-1.26: done 2>/dev/null
17:17:02      k8s2-1.26:
17:17:02      k8s2-1.26: res=0
17:17:02      k8s2-1.26: while [ "$res" == "0" ]; do
17:17:02      k8s2-1.26:     VBoxManage natnetwork remove --netname natnet$i
17:17:02      k8s2-1.26:     res=$?
17:17:02      k8s2-1.26:     i=$((i+1))
17:17:02      k8s2-1.26: done 2>/dev/null
17:17:02      k8s2-1.26: '
17:17:02  ==> k8s2-1.26: Cloning VM...
17:17:02
==> k8s2-1.26: Matching MAC address for NAT networking...
17:17:02  ==> k8s2-1.26: Checking if box 'cilium/ubuntu-next' version '154' is up to date...
17:17:02  ==> k8s2-1.26: Setting the name of the VM: test_k8s2-126_1669771008608_98609
17:17:02  ==> k8s2-1.26: Fixed port collision for 22 => 2222. Now on port 2200.
17:17:02  ==> k8s2-1.26: Clearing any previously set network interfaces...
17:17:02  ==> k8s2-1.26: Preparing network interfaces based on configuration...
17:17:02      k8s2-1.26: Adapter 1: nat
17:17:02      k8s2-1.26: Adapter 2: intnet
17:17:02      k8s2-1.26: Adapter 3: intnet
17:17:02      k8s2-1.26: Adapter 4: hostonly
17:17:02      k8s2-1.26: Adapter 5: hostonly
17:17:02  ==> k8s2-1.26: Forwarding ports...
17:17:02      k8s2-1.26: 22 (guest) => 2200 (host) (adapter 1)
17:17:02  ==> k8s2-1.26: Running 'pre-boot' VM customizations...
17:17:02  ==> k8s2-1.26: Booting VM...
17:17:02  ==> k8s2-1.26: Waiting for machine to boot. This may take a few minutes...
17:17:02      k8s2-1.26: SSH address: <IP_ADDRESS>:2200
17:17:02      k8s2-1.26: SSH username: vagrant
17:17:02      k8s2-1.26: SSH auth method: private key
17:17:22      k8s2-1.26: Warning: Connection reset. Retrying...
17:17:22      k8s2-1.26: Warning: Remote connection disconnect. Retrying...
17:17:28      k8s2-1.26:
17:17:28      k8s2-1.26: Vagrant insecure key detected. Vagrant will automatically replace
17:17:28      k8s2-1.26: this with a newly generated keypair for better security.
17:17:28      k8s2-1.26:
17:17:28      k8s2-1.26: Inserting generated public key within guest...
17:17:28      k8s2-1.26: Removing insecure key from the guest if it's present...
17:17:28      k8s2-1.26: Key inserted! Disconnecting and reconnecting using new SSH key...
17:17:29  ==> k8s2-1.26: Machine booted and ready!
17:17:29  ==> k8s2-1.26: Checking for guest additions in VM...
17:17:29  ==> k8s2-1.26: Setting hostname...
17:17:30  ==> k8s2-1.26: Configuring and enabling network interfaces...
17:17:44  ==> k8s2-1.26: Installing NFS client...
17:17:59  ==> k8s2-1.26: Exporting NFS shared folders...
17:17:59  ==> k8s2-1.26: Preparing to edit /etc/exports.  Your password will be stored unencrypted in /root/.docker/config.json.
17:18:04      k8s2-1.26: Configure a credential helper to remove this warning. See
17:18:04      k8s2-1.26: https://docs.docker.com/engine/reference/commandline/login/#credentials-store
17:18:04      k8s2-1.26:
17:18:04      k8s2-1.26: Login Succeeded
17:18:04      k8s2-1.26: /tmp/vagrant-shell: line 48: helm: command not found
17:18:04      k8s2-1.26: beginning trying up to 10 times function "wget -nv https://get.helm.sh/helm-v3.7.0-linux-amd64.tar.gz"
17:18:04      k8s2-1.26: ***************************************
17:18:04      k8s2-1.26: *
17:18:04      k8s2-1.26: *
17:18:04      k8s2-1.26: * on attempt 0 of function "wget -nv https://get.helm.sh/helm-v3.7.0-linux-amd64.tar.gz"
17:18:04      k8s2-1.26: *
17:18:04      k8s2-1.26: *
17:18:04      k8s2-1.26: ***************************************
17:18:04      k8s2-1.26: 2022-11-30 01:18:04 URL:https://get.helm.sh/helm-v3.7.0-linux-amd64.tar.gz [13861119/13861119] -> "helm-v3.7.0-linux-amd64.tar.gz" [1]
17:18:04      k8s2-1.26: running of "wget -nv https://get.helm.sh/helm-v3.7.0-linux-amd64.tar.gz" successful
17:18:04      k8s2-1.26:
17:18:04      k8s2-1.26:
17:18:04      k8s2-1.26:
17:18:04      k8s2-1.26: linux-amd64/
17:18:04      k8s2-1.26: linux-amd64/helm
17:18:04      k8s2-1.26: linux-amd64/LICENSE
17:18:04      k8s2-1.26: linux-amd64/README.md
17:18:04      k8s2-1.26: version.BuildInfo{Version:"v3.7.0", GitCommit:"eeac83883cb4014fe60267ec6373570374ce770b", GitTreeState:"clean", GoVersion:"go1.16.8"}
17:18:06      k8s2-1.26: updating /etc/resolv.conf
17:18:06      k8s2-1.26: beginning trying up to 10 times function "wget https://packages.cloud.google.com/apt/doc/apt-key.gpg"
17:18:06      k8s2-1.26: ***************************************
17:18:06      k8s2-1.26: *
17:18:06      k8s2-1.26: *
17:18:06      k8s2-1.26: * on attempt 0 of function "wget https://packages.cloud.google.com/apt/doc/apt-key.gpg"
17:18:06      k8s2-1.26: *
17:18:06      k8s2-1.26: *
17:18:06      k8s2-1.26: ***************************************
17:18:06      k8s2-1.26: --2022-11-30 01:18:06--  https://packages.cloud.google.com/apt/doc/apt-key.gpg
17:18:06      k8s2-1.26: Resolving packages.cloud.google.com (packages.cloud.google.com)... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
17:18:06      k8s2-1.26: Connecting to packages.cloud.google.com (packages.cloud.google.com)|<IP_ADDRESS>|:443... connected.
17:18:06      k8s2-1.26: HTTP request sent, awaiting response... 200 OK
17:18:06      k8s2-1.26: Length: 2537 (2.5K) [application/octet-stream]
17:18:06      k8s2-1.26: Saving to: ‘apt-key.gpg’
17:18:06      k8s2-1.26:
17:18:06      k8s2-1.26:      0K ..                                                    100% 45.6M=0s
17:18:06      k8s2-1.26:
17:18:06      k8s2-1.26: 2022-11-30 01:18:06 (45.6 MB/s) - ‘apt-key.gpg’ saved [2537/2537]
17:18:06      k8s2-1.26:
17:18:06      k8s2-1.26: running of "wget https://packages.cloud.google.com/apt/doc/apt-key.gpg" successful
17:18:06      k8s2-1.26:
17:18:06      k8s2-1.26:
17:18:06      k8s2-1.26:
17:18:06      k8s2-1.26: Warning: apt-key output should not be parsed (stdout is not a terminal)
17:18:06      k8s2-1.26: OK
17:18:09      k8s2-1.26: Reading package lists...
17:18:09      k8s2-1.26: Building dependency tree...
17:18:09      k8s2-1.26: Reading state information...
17:18:09      k8s2-1.26: conntrack is already the newest version (1:1.4.5-2).
17:18:09      k8s2-1.26: 0 upgraded, 0 newly installed, 0 to remove and 70 not upgraded.
17:18:10      k8s2-1.26: Hit:2 https://deb.nodesource.com/node_12.x focal InRelease
17:18:10      k8s2-1.26: Hit:3 https://download.docker.com/linux/ubuntu focal InRelease
17:18:10      k8s2-1.26: Hit:1 https://packages.cloud.google.com/apt kubernetes-xenial InRelease
17:18:10      k8s2-1.26: Hit:4 http://us.archive.ubuntu.com/ubuntu focal InRelease
17:18:10      k8s2-1.26: Hit:5 http://us.archive.ubuntu.com/ubuntu focal-updates InRelease
17:18:10      k8s2-1.26: Hit:6 http://us.archive.ubuntu.com/ubuntu focal-backports InRelease
17:18:10      k8s2-1.26: Hit:7 http://us.archive.ubuntu.com/ubuntu focal-security InRelease
17:18:12      k8s2-1.26: Reading package lists...
17:18:12      k8s2-1.26: Reading package lists...
17:18:12      k8s2-1.26: Building dependency tree...
17:18:12      k8s2-1.26: Reading state information...
17:18:12      k8s2-1.26: E: Version '1.26.0-rc.0*' for 'kubelet' was not found
17:18:12      k8s2-1.26: E: Version '1.26.0-rc.0*' for 'kubeadm' was not found
17:18:12      k8s2-1.26: E: Version '1.26.0-rc.0*' for 'kubectl' was not found
17:18:12      k8s2-1.26: falling back on binary k8s install
17:18:14      k8s2-1.26: 'kubeadm' -> '/usr/bin/kubeadm'
17:18:14      k8s2-1.26: 'kubectl' -> '/usr/bin/kubectl'
17:18:14      k8s2-1.26: 'kubelet' -> '/usr/bin/kubelet'
17:18:15      k8s2-1.26: Created symlink /etc/systemd/system/multi-user.target.wants/kubelet.service → /etc/systemd/system/kubelet.service.
17:18:15      k8s2-1.26: KUBELET_EXTRA_ARGS="--fail-swap-on=false"
17:18:16      k8s2-1.26: [preflight] Running pre-flight checks
17:18:17      k8s2-1.26: 	[WARNING Swap]: swap is enabled; production deployments should disable swap unless testing the NodeSwap feature gate of the kubelet
17:18:17      k8s2-1.26: [preflight] Reading configuration from the cluster...
17:18:17      k8s2-1.26: [preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
17:18:17      k8s2-1.26: W1130 01:18:17.631434   11453 configset.go:78] Warning: No kubeproxy.config.k8s.io/v1alpha1 config is loaded. Continuing without it: configmaps "kube-proxy" is forbidden: User "system:bootstrap:258062" cannot get resource "configmaps" in API group "" in the namespace "kube-system"
17:18:17      k8s2-1.26: [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
17:18:17      k8s2-1.26: [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
17:18:17      k8s2-1.26: [kubelet-start] Starting the kubelet
17:18:18      k8s2-1.26: [kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...
17:18:32      k8s2-1.26:
17:18:32      k8s2-1.26: This node has joined the cluster:
17:18:32      k8s2-1.26: * Certificate signing request was sent to apiserver and a response was received.
17:18:32      k8s2-1.26: * The Kubelet was informed of the new secure connection details.
17:18:32      k8s2-1.26:
17:18:32      k8s2-1.26: Run 'kubectl get nodes' on the control-plane to see this node join the cluster.
17:18:32      k8s2-1.26:
17:18:32  Bringing machine 'k8s3-1.26' up with 'virtualbox' provider...
17:18:32  ==> k8s3-1.26: Running action triggers before up ...
17:18:32  ==> k8s3-1.26: Running trigger...
17:18:32      k8s3-1.26: Running local: Inline script
17:18:32      k8s3-1.26: bash -c 'i=1
17:18:32      k8s3-1.26: k8s_nodes="${K8S_NODES:-2}"
17:18:32      k8s3-1.26: while [ "$i" -le "$k8s_nodes" ]; do
17:18:32      k8s3-1.26:     VBoxManage natnetwork add --netname natnet$i --network <IP_ADDRESS>/16 --ipv6 on --enable
17:18:32      k8s3-1.26:     i=$((i+1))
17:18:32      k8s3-1.26: done 2>/dev/null
17:18:32      k8s3-1.26:
17:18:32      k8s3-1.26: res=0
17:18:32      k8s3-1.26: while [ "$res" == "0" ]; do
17:18:32      k8s3-1.26:     VBoxManage natnetwork remove --netname natnet$i
17:18:32      k8s3-1.26:     res=$?
17:18:32      k8s3-1.26:     i=$((i+1))
17:18:32      k8s3-1.26: done 2>/dev/null
17:18:32      k8s3-1.26: '
17:18:33  ==> k8s3-1.26: Cloning VM...
17:18:33
==> k8s3-1.26: Matching MAC address for NAT networking...
17:18:33  ==> k8s3-1.26: Checking if box 'cilium/ubuntu-next' version '154' is up to date...
17:18:33  ==> k8s3-1.26: Setting the name of the VM: test_k8s3-126_1669771113517_93178
17:18:33  ==> k8s3-1.26: Fixed port collision for 22 => 2222. Now on port 2201.
17:18:34  ==> k8s3-1.26: Clearing any previously set network interfaces...
17:18:34  ==> k8s3-1.26: Preparing network interfaces based on configuration...
17:18:34      k8s3-1.26: Adapter 1: nat
17:18:34      k8s3-1.26: Adapter 2: intnet
17:18:34      k8s3-1.26: Adapter 3: intnet
17:18:34      k8s3-1.26: Adapter 4: hostonly
17:18:34      k8s3-1.26: Adapter 5: hostonly
17:18:34  ==> k8s3-1.26: Forwarding ports...
17:18:35      k8s3-1.26: 22 (guest) => 2201 (host) (adapter 1)
17:18:35  ==> k8s3-1.26: Running 'pre-boot' VM customizations...
17:18:35  ==> k8s3-1.26: Booting VM...
17:18:35  ==> k8s3-1.26: Waiting for machine to boot. This may take a few minutes...
17:18:35      k8s3-1.26: SSH address: <IP_ADDRESS>:2201
17:18:35      k8s3-1.26: SSH username: vagrant
17:18:35      k8s3-1.26: SSH auth method: private key
17:19:28      k8s3-1.26:
17:19:28      k8s3-1.26: Vagrant insecure key detected. Vagrant will automatically replace
17:19:28      k8s3-1.26: this with a newly generated keypair for better security.
17:19:28      k8s3-1.26:
17:19:28      k8s3-1.26: Inserting generated public key within guest...
17:19:28      k8s3-1.26: Removing insecure key from the guest if it's present...
17:19:28      k8s3-1.26: Key inserted! Disconnecting and reconnecting using new SSH key...
17:19:28  ==> k8s3-1.26: Machine booted and ready!
17:19:28  ==> k8s3-1.26: Checking for guest additions in VM...
17:19:28  ==> k8s3-1.26: Setting hostname...
17:19:28  ==> k8s3-1.26: Configuring and enabling network interfaces...
17:19:45  ==> k8s3-1.26: Installing NFS client...
17:20:02  ==> k8s3-1.26: Exporting NFS shared folders...
17:20:02  ==> k8s3-1.26: Preparing to edit /etc/exports.  Your password will be stored unencrypted in /root/.docker/config.json.
17:20:08      k8s3-1.26: Configure a credential helper to remove this warning. See
17:20:08      k8s3-1.26: https://docs.docker.com/engine/reference/commandline/login/#credentials-store
17:20:08      k8s3-1.26:
17:20:08      k8s3-1.26: Login Succeeded
17:20:08      k8s3-1.26: /tmp/vagrant-shell: line 48: helm: command not found
17:20:08      k8s3-1.26: beginning trying up to 10 times function "wget -nv https://get.helm.sh/helm-v3.7.0-linux-amd64.tar.gz"
17:20:08      k8s3-1.26: ***************************************
17:20:08      k8s3-1.26: *
17:20:08      k8s3-1.26: *
17:20:08      k8s3-1.26: * on attempt 0 of function "wget -nv https://get.helm.sh/helm-v3.7.0-linux-amd64.tar.gz"
17:20:08      k8s3-1.26: *
17:20:08      k8s3-1.26: *
17:20:08      k8s3-1.26: ***************************************
17:20:08      k8s3-1.26: 2022-11-30 01:20:08 URL:https://get.helm.sh/helm-v3.7.0-linux-amd64.tar.gz [13861119/13861119] -> "helm-v3.7.0-linux-amd64.tar.gz" [1]
17:20:08      k8s3-1.26: running of "wget -nv https://get.helm.sh/helm-v3.7.0-linux-amd64.tar.gz" successful
17:20:08      k8s3-1.26:
17:20:08      k8s3-1.26:
17:20:08      k8s3-1.26:
17:20:08      k8s3-1.26: linux-amd64/
17:20:08      k8s3-1.26: linux-amd64/helm
17:20:08      k8s3-1.26: linux-amd64/LICENSE
17:20:08      k8s3-1.26: linux-amd64/README.md
17:20:08      k8s3-1.26: version.BuildInfo{Version:"v3.7.0", GitCommit:"eeac83883cb4014fe60267ec6373570374ce770b", GitTreeState:"clean", GoVersion:"go1.16.8"}
17:20:10      k8s3-1.26: updating /etc/resolv.conf
17:20:10      k8s3-1.26: beginning trying up to 10 times function "wget https://packages.cloud.google.com/apt/doc/apt-key.gpg"
17:20:10      k8s3-1.26: ***************************************
17:20:10      k8s3-1.26: *
17:20:10      k8s3-1.26: *
17:20:10      k8s3-1.26: * on attempt 0 of function "wget https://packages.cloud.google.com/apt/doc/apt-key.gpg"
17:20:10      k8s3-1.26: *
17:20:10      k8s3-1.26: *
17:20:10      k8s3-1.26: ***************************************
17:20:10      k8s3-1.26: --2022-11-30 01:20:10--  https://packages.cloud.google.com/apt/doc/apt-key.gpg
17:20:10      k8s3-1.26: Resolving packages.cloud.google.com (packages.cloud.google.com)... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
17:20:10      k8s3-1.26: Connecting to packages.cloud.google.com (packages.cloud.google.com)|<IP_ADDRESS>|:443... connected.
17:20:10      k8s3-1.26: HTTP request sent, awaiting response... 200 OK
17:20:10      k8s3-1.26: Length: 2537 (2.5K) [application/octet-stream]
17:20:10      k8s3-1.26: Saving to: ‘apt-key.gpg’
17:20:10      k8s3-1.26:
17:20:10      k8s3-1.26:      0K ..                                                    100% 10.2M=0s
17:20:10      k8s3-1.26:
17:20:10      k8s3-1.26: 2022-11-30 01:20:10 (10.2 MB/s) - ‘apt-key.gpg’ saved [2537/2537]
17:20:10      k8s3-1.26:
17:20:10      k8s3-1.26: running of "wget https://packages.cloud.google.com/apt/doc/apt-key.gpg" successful
17:20:10      k8s3-1.26:
17:20:10      k8s3-1.26:
17:20:10      k8s3-1.26:
17:20:10      k8s3-1.26: Warning: apt-key output should not be parsed (stdout is not a terminal)
17:20:10      k8s3-1.26: OK
17:20:12      k8s3-1.26: Reading package lists...
17:20:12      k8s3-1.26: Building dependency tree...
17:20:12      k8s3-1.26: Reading state information...
17:20:12      k8s3-1.26: conntrack is already the newest version (1:1.4.5-2).
17:20:12      k8s3-1.26: 0 upgraded, 0 newly installed, 0 to remove and 70 not upgraded.
17:20:12      k8s3-1.26: Hit:2 https://download.docker.com/linux/ubuntu focal InRelease
17:20:12      k8s3-1.26: Hit:3 https://deb.nodesource.com/node_12.x focal InRelease
17:20:12      k8s3-1.26: Hit:1 https://packages.cloud.google.com/apt kubernetes-xenial InRelease
17:20:12      k8s3-1.26: Hit:4 http://us.archive.ubuntu.com/ubuntu focal InRelease
17:20:12      k8s3-1.26: Hit:5 http://us.archive.ubuntu.com/ubuntu focal-updates InRelease
17:20:13      k8s3-1.26: Hit:6 http://us.archive.ubuntu.com/ubuntu focal-backports InRelease
17:20:13      k8s3-1.26: Hit:7 http://us.archive.ubuntu.com/ubuntu focal-security InRelease
17:20:15      k8s3-1.26: Reading package lists...
17:20:15      k8s3-1.26: Reading package lists...
17:20:15      k8s3-1.26: Building dependency tree...
17:20:15      k8s3-1.26: Reading state information...
17:20:15      k8s3-1.26: E: Version '1.26.0-rc.0*' for 'kubelet' was not found
17:20:15      k8s3-1.26: E: Version '1.26.0-rc.0*' for 'kubeadm' was not found
17:20:15      k8s3-1.26: E: Version '1.26.0-rc.0*' for 'kubectl' was not found
17:20:15      k8s3-1.26: falling back on binary k8s install
17:20:18      k8s3-1.26: 'kubeadm' -> '/usr/bin/kubeadm'
17:20:18      k8s3-1.26: 'kubectl' -> '/usr/bin/kubectl'
17:20:18      k8s3-1.26: 'kubelet' -> '/usr/bin/kubelet'
17:20:18      k8s3-1.26: Created symlink /etc/systemd/system/multi-user.target.wants/kubelet.service → /etc/systemd/system/kubelet.service.
17:20:18      k8s3-1.26: KUBELET_EXTRA_ARGS="--fail-swap-on=false"
17:20:19      k8s3-1.26: [preflight] Running pre-flight checks
17:20:20      k8s3-1.26: 	[WARNING Swap]: swap is enabled; production deployments should disable swap unless testing the NodeSwap feature gate of the kubelet
17:20:20      k8s3-1.26: [preflight] Reading configuration from the cluster...
17:20:20      k8s3-1.26: [preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
17:20:21      k8s3-1.26: W1130 01:20:20.853036   11276 configset.go:78] Warning: No kubeproxy.config.k8s.io/v1alpha1 config is loaded. Continuing without it: configmaps "kube-proxy" is forbidden: User "system:bootstrap:258062" cannot get resource "configmaps" in API group "" in the namespace "kube-system"
17:20:21      k8s3-1.26: [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
17:20:21      k8s3-1.26: [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
17:20:21      k8s3-1.26: [kubelet-start] Starting the kubelet
17:20:21      k8s3-1.26: [kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...
17:20:36      k8s3-1.26:
17:20:36      k8s3-1.26: This node has joined the cluster:
17:20:36      k8s3-1.26: * Certificate signing request was sent to apiserver and a response was received.
17:20:36      k8s3-1.26: * The Kubelet was informed of the new secure connection details.
17:20:36      k8s3-1.26:
17:20:36      k8s3-1.26: Run 'kubectl get nodes' on the control-plane to see this node join the cluster.
17:20:36      k8s3-1.26:
17:20:38  getting vagrant kubeconfig from provisioned vagrant cluster into vagrant-kubeconfig
17:20:41  checking whether kubeconfig works for vagrant cluster
17:20:41  NAME   STATUS     ROLES           AGE     VERSION
17:20:41  k8s1   NotReady   control-plane   8m57s   v1.26.0-rc.0
17:20:41  k8s2   NotReady   <none>          2m10s   v1.26.0-rc.0
17:20:41  k8s3   NotReady   <none>          7s      v1.26.0-rc.0
17:20:41  NAME   STATUS     ROLES           AGE     VERSION
17:20:41  k8s1   NotReady   control-plane   8m57s   v1.26.0-rc.0
17:20:41  k8s2   NotReady   <none>          2m10s   v1.26.0-rc.0
17:20:41  k8s3   NotReady   <none>          7s      v1.26.0-rc.0
17:20:41  adding local docker registry to cluster
17:20:42  WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: vagrant-kubeconfig
17:20:42  WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: vagrant-kubeconfig
17:20:42  daemonset.apps/registry-adder created
17:20:42  labeling nodes
17:20:42  node/k8s1 labeled
17:20:42  node/k8s2 labeled
17:20:42  node/k8s3 labeled

On the latest version, this took a long time:
09:56:00  ==> k8s2-1.26: Installing NFS client...
10:01:59  ==> k8s2-1.26: Exporting NFS shared folders...

And for the third VM, that is the step that times out.

I have also noticed some trouble with fetching Ubuntu packages in various jobs. This may or may not be related to this issue.


Add non-blocking CI stages that run tests with Intelligent Test Runner

What does this PR do?
Adds CI stages that run tests with Intelligent Test Runner.
The new "ITR-enabled" stages are executed in parallel with the existing ones, and will not fail the pipeline.
The goal is to run ITR for some time in this "non-blocking" mode alongside the regular test executions, and observe how it behaves in this repo.
If everything is well, the old stages will eventually be dropped and replaced with the ITR ones.
Motivation
Dogfooding Intelligent Test Runner in DD SDK Android repo.
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report

Merging #1844 (d1cfb1d) into develop (c925c52) will decrease coverage by 0.01%.
The diff coverage is n/a.

:exclamation: Current head d1cfb1d differs from pull request most recent head 1482816. Consider uploading reports for the commit 1482816 to get more accurate results

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1844      +/-   ##
===========================================
- Coverage    83.41%   83.40%   -0.01%
===========================================
  Files          467      467
  Lines        16530    16534       +4
  Branches      2498     2498
===========================================
+ Hits         13788    13790       +2
- Misses        2050     2058       +8
+ Partials       692      686       -6

see 25 files with indirect coverage changes

Cancelling this for now, as skipping tests with ITR interferes with Codecov reporting


chore(codeowners): add jessie

Summary

Add @jessieyan as a reviewer

:tada: This PR is included in version 2.11.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


System.Text.Json cannot deserialize Polynomial coefficients correctly

Since the coefficients have a private setter than System.Text.Json cannot correctly deserialize the object.
Either the setter can be made public or add JsonInclude attribute.
Would you be open to include support for this in NET5?
#if NET5_0_OR_GREATER
using System.Text.Json.Serialization;
#endif

namespace MathNet.Numerics
{

    public class Polynomial : IFormattable, IEquatable<Polynomial>, ICloneable
    {
        /// <summary>
        /// The coefficients of the polynomial in a
        /// </summary>
        [DataMember(Order = 1)]
#if NET5_0_OR_GREATER
        [JsonInclude]
#endif
        public double[] Coefficients { get; private set; }

I can submit a PR if you agree with the solution :)

Yes, that looks fine to me, thanks.
I suspect we may have the same problem also in a few other places.

I can look through and find them :)

FYI JsonInclude was only added in NET5.0 and System.Text.Json is only available in NET Standard and NET Framework as a NuGet package.
Not sure it is worth adding a NuGet package to include support for it in older runtimes.

No, it's fine to do this only with net5.0 and newer. Being able to do that was one of the main reasons of adding a proper net5.0 build in the first place (instead of just relying on netstandard2.0).

Actually looking through the code, there is not that many places it makes sense to add. I basically found one in DescriptiveStatistics 😅
Currently vector and matrix cannot be (de)serialized as they are abstract and properly easier to (de)serialize as array/list and cast into a vector or matrix.
Palf being a mix of public and private fields is not something System.Text.Json can serialize.

I thought the concrete vector and matrix storage types were serializable - in practice that's not very usable/helpful though I guess.

I can try again to see what needs to be done to make it serializable for System.Text.Json

DenseVectorStorage is easy though that is relative, not so much the SparseVectorStorage.
But to make DenseVectorStorage You have to do something like this
        [DataMember(Order = 1)]
#if NET5_0_OR_GREATER
        public T[] Data { get; init; }
#else
        public readonly T[] Data;
#endif

...

#if NET5_0_OR_GREATER
        [JsonConstructor]
        public DenseVectorStorage(T[] data) : base(data.Length)
        {
            Data = data;
        }
#endif


Separate task specific configs from main genesis config

Looking at https://github.com/tumblr/genesis/blob/master/testenv/bootbox/web/config/config.yml.sample
I think the framework should separate the configuration directives necessary for the framework to function (read: ipxe, genesis_server, gem, collins, ntp server) from the specific configuration directives that are consumed by tasks (i.e. virident, bios_settings, verify_tool). Each task may or may not rely on some specific configuration (i.e. configure_virident wants to know what firmware tarballs there are, or what version to install), and can ask for that specific config before running. I want to avoid having a single large yaml config that has every setting for every task. It becomes difficult to identify which task depends on which config directives (as we have seen with visioner).
I would be happy to start breaking this apart and writing a config fetch mechanism that runs before each task.  @maddalab @roymarantz @defect

Thoughts on just including the configs inside the tasks themselves? Is there a strong benefit to having them be externalized outside the tasks?

@jsjohnst In out operation, tasks are static while the config is generated based on information from other sources.


WIP: Various little upgrades

I have not collapsed the 3 stores. Here is the related issue to discuss https://github.com/cosmos/sdk-module-tutorial/issues/1 @jackzampolin

Like this, and going to merge these changes. I'll open another PR later today to try to move this from module based to app based.


Reorganize MicroService unit tests

Fixes #10356
Complement to https://github.com/dmwm/WMCore/pull/10357
Status
ready
Description
Reorganize the microservice unit tests as well - according to the src files organization - which I completely missed in the main PR #10357.
In addition to that, I ran code reformat on most of those modules.
Is it backward compatible (if not, which system it affects?)
yes
Related PRs
Complement to https://github.com/dmwm/WMCore/pull/10357
External dependencies / deployment changes
none

Only test files and pylint fixes, so not even bothering in requesting for a review. Merging.

thanks @amaltaro


[Bug] Does not work well with resource pack fonts

Description: I tried to use a resource pack from this modpack which adds a resource pack font to make the font smooth. But, I found with this mod that the font that the resource pack adds looks really broken.
With the mod (GUI Scale 27):

Without the mod (GUI Scale 3):

I've noticed that the grass block in the background also looks weird in your first screenshot:

The transition between the texels should be sharp, but this cannot possibly be caused by the mod. Can you also test version 1.1.0 with GUI Scale 300%?

Well, the resource pack does change the grass texture so it could be that but the max I can go is GUI Scale 49x so I will try that.

Here are the screenshots with GUI Scale 49:

I think what I'll do is add a setting to disable the font rendering changes

Version 1.2.0 adds an option to disable the font smoothing. I haven't tried it with a hi res font but I consider this fixed. Let me know if its still an issue.

See #6

Fixed in 1.2.1


Adding Boyer- moore voting algorithm

Hey @aaryahjolia I want to add the Boyer voting Algorithm. Please assign me this issue. Thank you!

Please assign this issue to me

@AnmolChauhan123 bro please raise another issue. I will work on it. Thank you.

Alright broo... No issue
On Sat, 20 May, 2023, 15:13 Sumit Kumar Rai, @.***>
wrote:

@AnmolChauhan123 https://github.com/AnmolChauhan123 bro please raise
another issue. I will work on it. Thank you.
—
Reply to this email directly, view it on GitHub
https://github.com/aaryahjolia/dsa_competitive-coding/issues/281#issuecomment-1555875096,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASPIY5FZHPJYLHT4HJ6BIBLXHCG4VANCNFSM6AAAAAAYISKSXM
.
You are receiving this because you were mentioned.Message ID:
@.***>


Support serving UI under subdomain

Describe the bug
Link to Slack thread where I originally asked this question.
I want to host the Temporal UI at the root path of a subdomain, e.g. temporal.[mydomain].com, using host-based routing in ALB.
This is important because I can't avoid subdomains in the URL, even if I hosted the UI at a specific path, e.g. [mydomain].com/temporal, since I also have a staging environment where the UI will be hosted at staging.[mydomain].com/temporal.
When I configure host-based routing in ALB to route temporal.[mydomain].com to the frontend service, I have two options to configure the frontend service.

With TEMPORAL_UI_PUBLIC_PATH=/, the page fails to fetch the JS resources in the browser because the HTML returned from the server contains // in front of the JS bundles, e.g.

<link rel="modulepreload" href="//_app/immutable/entry/start.XNU22-I9.js">

This tells the browser to ignore the same origin rule, and the requests instead get sent to https://_app/immutable/entry/start.XNU22-I9.js which doesn't exist.

With TEMPORAL_UI_PUBLIC_PATH=temporal.[mydomain].com, now the UI can fetch the bundles linked in the HTML, but then fails to load the JS.

E.g. this file temporal.[mydomain].com]/_app/immutable/entry/start.XNU22-I9.js contains:
import{c as a}from"../chunks/entry.npYmAy9v.js";export{a as start};

The referenced file does exist and contains a load of JS, if I go to it directly, i.e. temporal.[mydomain].com/_app/immutable/chunks/entry.npYmAy9v.js. But it fails to load in the browser:
(index):26 Uncaught (in promise) TypeError: Failed to resolve module specifier 'temporal.[mydomain].com/_app/immutable/entry/start.XNU22-I9.js'
    at (index):26:14

To Reproduce
Steps to reproduce the behavior:

Host Temporal Frontend service (I've got it on ECS) with TEMPORAL_UI_PUBLIC_PATH=/
Configure load balancer to forward requests matching the host and path, e.g. with ALB listener rule:

  condition {
    host_header {
      values = ["temporal.${local.domain_name}"]
    }
  }

  condition {
    path_pattern {
      values = [
        "/*",
      ]
    }
  }

Visit Temporal UI in the browser, e.g. https://temporal.[mydomain].com

Expected behavior
The frontend SPA should respect the same origin rule and fetch resources from TEMPORAL_UI_PUBLIC_PATH on the same domain (including subdomains) it originated.
Screenshots
N/a
Desktop (please complete the following information):

OS: MacOS 14.6 (23G80)
Browser: Version 127.0.6533.89 (Official Build) (arm64)

Additional context
N/A

OK I've figured it out. You can deploy on a subdomain, but setting TEMPORAL_UI_PUBLIC_PATH=/ completely breaks the UI. Leaving the env var unset fixes the issue.
The reason this breaks the deployment is because setting the TEMPORAL_UI_PUBLIC_PATH=/ causes the HTML to render the link tags in the HTML meta with an extra /.
The ui-server project contains the links in question that fetch the JS bundles. If you set the public path, what actually gets rendered is:
		<link rel="modulepreload" href="//_app/immutable/entry/start.PkAQ5dFz.js">
		<link rel="modulepreload" href="//_app/immutable/chunks/entry.wLcqREKA.js">
		<link rel="modulepreload" href="//_app/immutable/chunks/scheduler.1T9hOnFr.js">
		<link rel="modulepreload" href="//_app/immutable/chunks/paths.IPjQg0PU.js">
		<link rel="modulepreload" href="//_app/immutable/chunks/control.pJ1mnnAb.js">
		<link rel="modulepreload" href="//_app/immutable/entry/app.2gko0slu.js">
		<link rel="modulepreload" href="//_app/immutable/chunks/index.cVovwi_s.js">

Which tells the browser to ignore the same origin hostname completely and fetch the resources as:
		<link rel="modulepreload" href="https://_app/immutable/entry/start.PkAQ5dFz.js">
		<link rel="modulepreload" href="https://_app/immutable/chunks/entry.wLcqREKA.js">
		...

So setting the public path when you're using subdomains should be avoided. This tripped me up for several hours today, as I would expect a public path of "/" to mean the root path of the same origin.

I don't know if this has been fixed but setting public path seems to work for us.
There is one small issue however, the "home" button (temporal logo top left) redirects to base host url which results in a 404


[bug] translatable content not displayed correctly

What happened?
This is not a bug report as the package does not support spatie/laravel-translatable support, but more of of a question.
Currently, when using this with translatable content, the diff view displays all translations as raw json
see image below.

and it would through an error when stripTags is set to true
public function shouldStripTags(): bool
{
        return false;
 }

I was wondering if there is a way to display the data decoded correctly without the json, or you could point me in the right direction I would really appreciate it.
How to reproduce the bug
Create translatable model and add translations to it. then attempt to view the revisions.
Package Version
0.0.9
PHP Version
8.3.8
Laravel Version
11.20.0
Which operating systems does with happen with?
No response
Notes
No response

Theres an issue with translation

Hey,
This package does not support arrays or translations for now.
But I am looking to add those features. I might re-write and change things and would be available for Filament v4.

Hey @abbasmashaddy72
Please create a separate issue for the problem you are seeing.

a default revision is being created automatically, even though it's not needed

A default version is created only when you are saving a model and if it does not already have a state in versions table. This is required/need to atleast have the current state of the model before saving the new state. However, you can disable this behaviour by setting keep_original_version to false in config file or you can easily override this behaviour in your Models by overriding the methods.


feat: extras for the action

Close #797. Requires #795.

IMO, once can use:
    - name: Setup uv
      uses: yezz123/setup-uv@v4

And get pip, so for now, I think that's probably fine, keeps the action simple.


fixes #23 - link's href not updated

Link's href attribute was referenced during instantiation and link kept pointing to that url even if anchor's href was dynamically changed.
You can update tests if you want do - I didn't know how to run them nor I wanted to mess up the prettiness :)

@fourpixels sorry, I completely missed the fact that you posted this PR. Is your problem now resolved?

Yeah it is :)