You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My apply fails at module.kube-hetzner.null_resource.kustomization, but i can then ssh into the box and execute the command just fine. I am guessing it executes too quickly - could it be that the step should wait for the port to be open?
As a workaround, i inserted a sleep 60 in front of the first kubectl, which helped but is clearly suboptimal.
Please note i am using terraform cloud with remote execution, although the README advises to use local execution - i don't think this is the cause of my problem though.
Log-excerpt:
Connecting to remote host via SSH...
Host: <redacted>
User: root
Password: false
Private key: true
Certificate: false
SSH Agent: false
Checking Host Key: false
Target Platform: unix
Connected!
+ kubectl -n kube-system create secret generic hcloud --from-literal=token=<redacted> --from-literal=network=<redacted> --dry-run=client -o yaml
+ kubectl apply -f -
[36mINFO[0m[0000] Acquiring lock file /var/lib/rancher/k3s/data/.lock
[36mINFO[0m[0000] Preparing data dir /var/lib/rancher/k3s/data/cc73cc54f96e096349faa656c251469ebefa4f9ab0d3f356ea6895ff145dcd1e
[36mINFO[0m[0000] Acquiring lock file /var/lib/rancher/k3s/data/.lock
The connection to the server localhost:8080 was refused - did you specify the right host or port?
This discussion was converted from issue #487 on January 10, 2023 21:34.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
My apply fails at
module.kube-hetzner.null_resource.kustomization
, but i can then ssh into the box and execute the command just fine. I am guessing it executes too quickly - could it be that the step should wait for the port to be open?As a workaround, i inserted a
sleep 60
in front of the first kubectl, which helped but is clearly suboptimal.Please note i am using terraform cloud with remote execution, although the README advises to use local execution - i don't think this is the cause of my problem though.
Log-excerpt:
Beta Was this translation helpful? Give feedback.
All reactions