NetworkUnavailable - Could not create route about hetzner-k3s HOT 38 CLOSED

Hi! :)

Did you try to create more than one cluster in the same Hetzner project by chance?

from hetzner-k3s.

i created one and then deleted it via hetzner-k3s delete-cluster.
I Test it Again with a new Project.

from hetzner-k3s.

Perhaps something concerning the network wasn't deleted correctly for some reason or you created a new cluster very quickly soon after deleting one. The only case I've had problems with network routes was when I tried to create more than one cluster in the same project. This is because both clusters try to create routes for the same cidr. I thought of making it configurable but I think it's better to have one cluster per project. Let me know how it goes :)

from hetzner-k3s.

Same Problem after New Deployment and Hetzner Project.

Super cool how fast it goes !!!

from hetzner-k3s.

Yeah it's pretty quick, I love it. When I test stuff I create and delete clusters in no time :D

As for your problem, what do you see in the events/notifications in the Hetzner console?

from hetzner-k3s.

In the Hetzner Console all Looks god.

I have already considered whether it is possibly due to the Ruby installation?
I tried it first with a M1 Mac, which unfortunately does not work because of Ruby ...
and i use now a Fresh Ubuntu Install...

from hetzner-k3s.

I've also got an M1 :)

If the cluster was created successfully without any errors I doubt it's a problem with Ruby etc.

Seems that someone else has reported the same error in the Hetzner's CCM project hetznercloud/hcloud-cloud-controller-manager#225 and hetznercloud/hcloud-cloud-controller-manager#165

It's weird because it never happened to me from what I can remember.

Did you just create a new project and a new cluster in it? Or did you create a cluster again after deleting another one? Did you see any errors in the output of the installer?

from hetzner-k3s.

Also are the servers attached to the private network?

from hetzner-k3s.

I have created a completely new Hetzner project without server etc.
I have only created a new API key.

I'll create a new project and send you the API token by mail, it would be interesting if it runs in your invirment without problems.

from hetzner-k3s.

Super weird. I just created a cluster twice both in Nuremberg and Helsinki just in case is something on Hetzner's side that is causing problems at the moment, but everything works fine and the routes were created correctly in both cases.

Yeah if you can share a token I can try from here with a small cluster and see if it happens to me too. Just make sure you don't create a cluster in the same project at the same time :)

from hetzner-k3s.

I received the token, am about to try. Gimme a minute

from hetzner-k3s.

I created a cluster with your token successfully. No errors, all pods started and the routes were created just fine. I'll send you the kubeconfig so you can see it.

from hetzner-k3s.

no Warningns... all works fine.
I think it must be the Ruby installation?

from hetzner-k3s.

Well everything is possible at this point :D Which version of Ruby are you using? I'm also planning to create some all-in-one binaries that include the Ruby runtime, so that the user doesn't need to deal with Ruby directly if they are not familiar with it.

How did you install Ruby? But did you get any errors while creating the cluster?

from hetzner-k3s.

i Recive sometimes this Error

/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/hetzner-k3s-0.3.2/lib/hetzner/k3s/cluster.rb:401: warning: Passing the keyword argument as the last hash parameter is deprecated
/var/lib/gems/2.7.0/gems/k8s-ruby-0.10.5/lib/k8s/resource.rb:45: warning: The called method `initialize' is defined here

I install a Fresh Ubuntu and then

--> sudo apt-get install ruby-full

ruby -v
ruby 2.7.0p0 (2019-12-25 revision 647ee6f091) [x86_64-linux-gnu]

gem -v
3.1.2

gcc --version
gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0

Full Error :

Deploying Hetzner Cloud Controller Manager...
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/hetzner-k3s-0.3.2/lib/hetzner/k3s/cluster.rb:322: warning: Passing the keyword argument as the last hash parameter is deprecated
/var/lib/gems/2.7.0/gems/k8s-ruby-0.10.5/lib/k8s/resource.rb:45: warning: The called method initialize' is defined here /var/lib/gems/2.7.0/gems/recursive-open-struct-1.1.3/lib/recursive_open_struct.rb:188: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call /var/lib/gems/2.7.0/gems/k8s-ruby-0.10.5/lib/k8s/resource.rb:45: warning: The called method initialize' is defined here
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
...Cloud Controller Manager deployed

Deploying Hetzner CSI Driver...
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/hetzner-k3s-0.3.2/lib/hetzner/k3s/cluster.rb:401: warning: Passing the keyword argument as the last hash parameter is deprecated
/var/lib/gems/2.7.0/gems/k8s-ruby-0.10.5/lib/k8s/resource.rb:45: warning: The called method initialize' is defined here /var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &blockinstead /var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use&blockinstead /var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use&blockinstead /var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use&blockinstead /var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use&blockinstead /var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use&blockinstead /var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use&block` instead
...CSI Driver deployed

Deploying k3s System Upgrade Controller...
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
/var/lib/gems/2.7.0/gems/dry-types-0.13.4/lib/dry/types/hash/schema.rb:151: warning: Capturing the given block using Proc.new is deprecated; use &block instead
...k3s System Upgrade Controller deployed

from hetzner-k3s.

I see. Can you try installing Ruby with rbenv instead? See https://github.com/rbenv/rbenv

apt install rbenv

Then to verify the installation:

curl -fsSL https://github.com/rbenv/rbenv-installer/raw/main/bin/rbenv-doctor | bash

Then install Ruby 2.7.4 (I haven't tested with 3.x yet)

rbenv install 2.7.4 && ruby global 2.7.4

Finally check that the version of Ruby is correct with ruby -v.

Then try creating a cluster again in a new project and let me know.

from hetzner-k3s.

I test it now with

ruby -v
ruby 2.7.4p191 (2021-07-07 revision a21a3b7d23) [x86_64-linux]

on a Fresh Ubuntu and Hetzner Project.

Until the installation i dont have Errors or Warnings...
The only problem is, the network is still Unavailable

from hetzner-k3s.

I test it now with

ruby -v
ruby 2.7.4p191 (2021-07-07 revision a21a3b7d23) [x86_64-linux]

on a Fresh Ubuntu and Hetzner Project.

Until the installation i dont have Errors or Warnings...
The only problem is, the network is still Unavailable

No weird messages in the ouput of the installer? I don't know what could be causing this, never happened to me. It would be super weird if it were somehow related to Ruby on Linux or something like that. But if all the resources are created correctly and the cloud controller manager is also installed correctly it can't be Ruby.

Can you share more from the logs of the controller manager pod?

from hetzner-k3s.

Also which Hetzner location are you using? Are you using Falkenstein by chance? It's the only one I haven't tried and I'm wondering if there is something different about it somehow.

from hetzner-k3s.

Just tried with Falkenstein, no problems with that either.

from hetzner-k3s.

Hey I was able to reproduce the problem on Linux and I think I found a fix :) I will release a new version tonight after my day job :)

from hetzner-k3s.

@Agilitytime Actually I release 0.3.3 already with a tiny change. So to test:

• install rbenv and Ruby 2.74
• ensure Ruby 2.7.4 is active (ruby -v)
• install the hetzner-k3s gem again so it updates the executable
• try again creating a cluster (delete the previous if any and wait a little bit before creating a new one if in the same project)

Let me know how it goes.

from hetzner-k3s.

I install the New Version and also create a New Project...
but stil the same Problem. )=

from hetzner-k3s.

it must be a problem with Ubuntu...
i did it now with CentOS and there it runs without problems!
all ruby versions are the same

from hetzner-k3s.

I did my tests with Ubuntu, so it's unlikely. I did the tests with a VPS. I will try again, maybe I missed something else that I did during my tests.

from hetzner-k3s.

I tried again with a fresh Ubuntu VPS and all works just fine. Can you try again following these instructions?

apt update
apt install -y git-core build-essential openssl libssl-dev zlib1g-dev
git clone https://github.com/rbenv/rbenv.git ~/.rbenv
echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bash_profile
source ~/.bash_profile
rbenv init
source ~/.bash_profile
git clone https://github.com/rbenv/ruby-build.git "$(rbenv root)"/plugins/ruby-build
rbenv install 2.7.4
rbenv global 2.7.4
ruby -v (check that it says 2.7.4)
ssh-keygen (unless you have a key already)

Thanks

from hetzner-k3s.

On this way it Works without Problems!!! =)
i hgave use GCC insteate of build-essential this was the problem i think ?

from hetzner-k3s.

@Agilitytime Even easier, I have created a Docker image so you don't have to deal with Ruby at all. It's in the README but the short version is that you can run the create/delete/upgrade commands as follows:

docker run --rm -it -v ${PWD}:/cluster -v ${HOME}/.ssh:/tmp/.ssh vitobotta/hetzner-k3s create-cluster --config-file /cluster/test.yaml

You run this from the directory where you have the config file for the cluster, and you need to set the kubeconfig path to /cluster/kubeconfig.

This should make things much easier for who doesn't have Ruby etc :) Please try it and let me know. Thanks!

from hetzner-k3s.

docker run --rm -it -v ${PWD}:/cluster -v ${HOME}/.skm/ApiRancher:/tmp/.ssh vitobotta/hetzner-k3s create-cluster --config-file /cluster/cluster_config.yaml
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
Traceback (most recent call last):
9: from /usr/local/bundle/bin/hetzner-k3s:23:in <main>' 8: from /usr/local/bundle/bin/hetzner-k3s:23:in load'
7: from /usr/local/bundle/gems/hetzner-k3s-0.3.3/exe/hetzner-k3s:4:in <top (required)>' 6: from /usr/local/bundle/gems/thor-1.1.0/lib/thor/base.rb:485:in start'
5: from /usr/local/bundle/gems/thor-1.1.0/lib/thor.rb:392:in dispatch' 4: from /usr/local/bundle/gems/thor-1.1.0/lib/thor/invocation.rb:127:in invoke_command'
3: from /usr/local/bundle/gems/thor-1.1.0/lib/thor/command.rb:27:in run' 2: from /usr/local/bundle/gems/hetzner-k3s-0.3.3/lib/hetzner/k3s/cli.rb:18:in create_cluster'
1: from /usr/local/bundle/gems/hetzner-k3s-0.3.3/lib/hetzner/k3s/cli.rb:79:in validate_config_file' /usr/local/bundle/gems/hetzner-k3s-0.3.3/lib/hetzner/k3s/cli.rb:159:in validate_location': undefined method `include?' for false:FalseClass (NoMethodError)

unfortunately brings an error.
/cluster/kubeconfig and SSH Key location are correct

from hetzner-k3s.

Just to be sure, you are running the command from inside the directory with the config file, and the file is named cluster_config.yaml? Just to be sure :D

from hetzner-k3s.

from hetzner-k3s.

That error indicates that you have specified a wrong location for the servers. It should either nbg1 (Nuremberg), or fsn1 (Falkenstein) or hel1 (Helsinki). It's also possible that the location is correct but the tool couldn't temporarily fetch the available locations from the Hetzner API. I'd try again.

from hetzner-k3s.

BTW I tried with the Docker image again now and it seems to work fine.

from hetzner-k3s.

With The docker Image i Have Problems with SSL...
But it is Possible that the Timeout is to Shurt, i test the Docker image now with a VPS

Ps: the certificate is created in Hetzner

<Thread:0x000000400cbd33e0 /usr/local/bundle/gems/hetzner-k3s-0.3.3/lib/hetzner/k3s/cluster.rb:146 run> terminated with exception (report_on_exception is true): Traceback (most recent call last): 28: from /usr/local/bundle/gems/hetzner-k3s-0.3.3/lib/hetzner/k3s/cluster.rb:146:in block (2 levels) in create_resources'
27: from /usr/local/bundle/gems/hetzner-k3s-0.3.3/lib/hetzner/k3s/cluster.rb:448:in wait_for_ssh' 26: from /usr/local/lib/ruby/2.7.0/timeout.rb:110:in timeout'
25: from /usr/local/lib/ruby/2.7.0/timeout.rb:33:in catch' 24: from /usr/local/lib/ruby/2.7.0/timeout.rb:33:in catch'
23: from /usr/local/lib/ruby/2.7.0/timeout.rb:33:in block in catch' 22: from /usr/local/lib/ruby/2.7.0/timeout.rb:95:in block in timeout'
21: from /usr/local/bundle/gems/hetzner-k3s-0.3.3/lib/hetzner/k3s/cluster.rb:453:in block in wait_for_ssh' 20: from /usr/local/bundle/gems/hetzner-k3s-0.3.3/lib/hetzner/k3s/cluster.rb:453:in loop'
19: from /usr/local/bundle/gems/hetzner-k3s-0.3.3/lib/hetzner/k3s/cluster.rb:454:in block (2 levels) in wait_for_ssh' 18: from /usr/local/bundle/gems/hetzner-k3s-0.3.3/lib/hetzner/k3s/cluster.rb:468:in ssh'
17: from /usr/local/bundle/gems/net-ssh-6.1.0/lib/net/ssh.rb:261:in start' 16: from /usr/local/bundle/gems/net-ssh-6.1.0/lib/net/ssh.rb:261:in ensure in start'
15: from /usr/local/bundle/gems/net-ssh-6.1.0/lib/net/ssh/connection/session.rb:126:in close' 14: from /usr/local/bundle/gems/net-ssh-6.1.0/lib/net/ssh/connection/session.rb:180:in loop'
13: from /usr/local/bundle/gems/net-ssh-6.1.0/lib/net/ssh/connection/session.rb:180:in loop' 12: from /usr/local/bundle/gems/net-ssh-6.1.0/lib/net/ssh/connection/session.rb:180:in block in loop'
11: from /usr/local/bundle/gems/net-ssh-6.1.0/lib/net/ssh/connection/session.rb:227:in process' 10: from /usr/local/bundle/gems/net-ssh-6.1.0/lib/net/ssh/connection/event_loop.rb:28:in process'
9: from /usr/local/bundle/gems/net-ssh-6.1.0/lib/net/ssh/connection/event_loop.rb:100:in ev_preprocess' 8: from /usr/local/bundle/gems/net-ssh-6.1.0/lib/net/ssh/connection/event_loop.rb:100:in each'
7: from /usr/local/bundle/gems/net-ssh-6.1.0/lib/net/ssh/connection/session.rb:248:in ev_preprocess' 6: from /usr/local/bundle/gems/net-ssh-6.1.0/lib/net/ssh/connection/session.rb:545:in dispatch_incoming_packets'
5: from /usr/local/bundle/gems/net-ssh-6.1.0/lib/net/ssh/transport/session.rb:190:in poll_message' 4: from /usr/local/bundle/gems/net-ssh-6.1.0/lib/net/ssh/transport/session.rb:190:in loop'
3: from /usr/local/bundle/gems/net-ssh-6.1.0/lib/net/ssh/transport/session.rb:193:in block in poll_message' 2: from /usr/local/bundle/gems/net-ssh-6.1.0/lib/net/ssh/transport/packet_stream.rb:90:in next_packet'
1: from /usr/local/bundle/gems/net-ssh-6.1.0/lib/net/ssh/transport/packet_stream.rb:75:in available_for_read?' /usr/local/bundle/gems/net-ssh-6.1.0/lib/net/ssh/transport/packet_stream.rb:75:in select': closed stream (IOError)`

from hetzner-k3s.

When a timeout occurs the SSH command is retried automatically. What you got is an IOError, which usually happens when there is an interruption of the connection or other network related thing (I think).

v0.3.6 now retries SSH commands when IOError occurs, so please try again but specify the v0.3.6 tag for the Docker image.

So this time you tried with Docker from an Hetzner VPS?

from hetzner-k3s.

Can you also share the config you're using (remember to remove the token)?

from hetzner-k3s.

With version v0.3.7 it works without problems. =)

from hetzner-k3s.

Glad to hear! I'm closing this but feel free to open another one if you still run into issues.

from hetzner-k3s.