kubernetes-sigs / sig-windows-dev-tools

This is a batteries included local development environment for Kubernetes on Windows.
Apache License 2.0
80 stars 46 forks source link

master branch: make 2 failure - looping with crictl is required for container runtime: exec: "crictl": executable file not found in %PATH% #142

Closed dougsland closed 2 years ago

dougsland commented 2 years ago

Cloning repo

# git clone https://github.com/kubernetes-sigs/sig-windows-dev-tools.git
Cloning into 'sig-windows-dev-tools'...
remote: Enumerating objects: 1264, done.
remote: Counting objects: 100% (597/597), done.
remote: Compressing objects: 100% (367/367), done.
remote: Total 1264 (delta 313), reused 418 (delta 197), pack-reused 667
Receiving objects: 100% (1264/1264), 90.41 MiB | 12.87 MiB/s, done.
Resolving deltas: 100% (650/650), done.
# cd sig-windows-dev-tools/

Cleaning environment

# vagrant destroy --force
cni:
antrea
==> winw1: VM not created. Moving on...
==> controlplane: VM not created. Moving on...

Using make 2

#~/sig-windows-dev-tools# make 2

*********** vagrant up first run done ~~~~ ENTERING WINDOWS BRINGUP LOOP ***
until `vagrant status | grep winw1 | grep -q "running"` ; do vagrant up winw1 || echo failed_win_up ; done
cni:
antrea
Bringing machine 'winw1' up with 'virtualbox' provider...
==> winw1: Importing base box 'FriedrichWilken/Windows_2019-sig-win-dev-tools'...
==> winw1: Matching MAC address for NAT networking...
==> winw1: Checking if box 'FriedrichWilken/Windows_2019-sig-win-dev-tools' version '1.04' is up to date...
==> winw1: Setting the name of the VM: sig-windows-dev-tools_winw1_1642178570697_50689
==> winw1: Fixed port collision for 3389 => 3389. Now on port 2208.
==> winw1: Fixed port collision for 5985 => 55985. Now on port 2209.
==> winw1: Fixed port collision for 5986 => 55986. Now on port 2210.
==> winw1: Fixed port collision for 22 => 2222. Now on port 2211.
==> winw1: Clearing any previously set network interfaces...
==> winw1: Preparing network interfaces based on configuration...
    winw1: Adapter 1: nat
    winw1: Adapter 2: hostonly
==> winw1: Forwarding ports...
    winw1: 3389 (guest) => 2208 (host) (adapter 1)
    winw1: 5985 (guest) => 2209 (host) (adapter 1)
    winw1: 5986 (guest) => 2210 (host) (adapter 1)
    winw1: 22 (guest) => 2211 (host) (adapter 1)
==> winw1: Running 'pre-boot' VM customizations...
==> winw1: Booting VM...
==> winw1: Waiting for machine to boot. This may take a few minutes...
    winw1: WinRM address: 127.0.0.1:2209
    winw1: WinRM username: vagrant
    winw1: WinRM execution_time_limit: PT2H
    winw1: WinRM transport: negotiate
==> winw1: Machine booted and ready!
==> winw1: Checking for guest additions in VM...
==> winw1: Setting hostname...
==> winw1: Waiting for machine to reboot...
==> winw1: Configuring and enabling network interfaces...
==> winw1: Mounting shared folders...
    winw1: C:/forked => /root/sig-windows-dev-tools/forked
    winw1: C:/sync/shared => /root/sig-windows-dev-tools/sync/shared
    winw1: C:/sync/windows => /root/sig-windows-dev-tools/sync/windows
==> winw1: Running provisioner: shell...
    winw1: Running: sync/shared/kubejoin.ps1 as C:\tmp\vagrant-shell.ps1
    winw1: [preflight] Running pre-flight checks
    winw1: [preflight] WARNING: Couldn't create the interface used for talking to the container runtime: crictl is required for container runtime: exec: "crictl": executable file not found in %PATH%
    winw1: error execution phase preflight: couldn't validate the identity of the API Server: could not find a JWS signature in the cluster-info ConfigMap for token ID "qirlpf"
    winw1: To see the stack trace of this error execute with --v=5 or higher
knabben commented 2 years ago

The error comes from winw1: error execution phase preflight: couldn't validate the identity of the API Server: could not find a JWS signature in the cluster-info ConfigMap for token ID "qirlpf", in fact there were multiple machines running with the same ip in the host, cleaning up and using only one work back.

/close

Slack thread: https://kubernetes.slack.com/archives/C0SJ4AFB7/p1642269661023800

k8s-ci-robot commented 2 years ago

@knabben: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/sig-windows-dev-tools/issues/142#issuecomment-1013778024): >The error comes from `winw1: error execution phase preflight: couldn't validate the identity of the API Server: could not find a JWS signature in the cluster-info ConfigMap for token ID "qirlpf"`, in fact there were multiple machines running with the same ip in the host, cleaning up and using only one work back. > >/close > >Slack thread: >https://kubernetes.slack.com/archives/C0SJ4AFB7/p1642269661023800 Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.