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
{{ message }}
This repository has been archived by the owner on Jul 25, 2022. It is now read-only.
Describe the bug
I got same issue #492 today when I troubleshooting user cluster issue. then use PR #494 to ssh node.
The result exit directly without call cleanup method after port not reachable, which caused security group and ec2 instance resource leakage.
(2/4) Setting up bastion host security group
Kubeconfig under path /home/ttt/.garden/cache/canary/projects/hc-dev/fire-1-1-haas/kubeconfig.yaml contains exec configurations that could contain malicious code. Please only continue if you have verified it to be uncritical
Security Group exists sg-0ca746fd63e9560b3 skipping creation.
(3/4) Creating bastion host and node host security group
Kubeconfig under path /home/ttt/.garden/cache/canary/projects/hc-dev/fire-1-1-haas/kubeconfig.yaml contains exec configurations that could contain malicious code. Please only continue if you have verified it to be uncritical
Bastion Host exists, skipping creation.
Kubeconfig under path /home/ttt/.garden/cache/canary/projects/hc-dev/fire-1-1-haas/kubeconfig.yaml contains exec configurations that could contain malicious code. Please only continue if you have verified it to be uncritical
Kubeconfig under path /home/ttt/.garden/cache/canary/projects/hc-dev/fire-1-1-haas/kubeconfig.yaml contains exec configurations that could contain malicious code. Please only continue if you have verified it to be uncritical
Kubeconfig under path /home/ttt/.garden/cache/canary/projects/hc-dev/fire-1-1-haas/kubeconfig.yaml contains exec configurations that could contain malicious code. Please only continue if you have verified it to be uncritical
SSH Port already opened on Node
waiting for 10 seconds to retry
waiting for 10 seconds to retry
waiting for 10 seconds to retry
waiting for 10 seconds to retry
waiting for 10 seconds to retry
waiting for 10 seconds to retry
waiting for 10 seconds to retry
waiting for 10 seconds to retry
waiting for 10 seconds to retry
waiting for 10 seconds to retry
waiting for 10 seconds to retry
waiting for 10 seconds to retry
2020/12/17 11:57:39 IP 3.122.94.82 port 22 is not reachable
exit status 1
ttt@W-R90PNMJE:~/work/gardenctl$
The text was updated successfully, but these errors were encountered:
Describe the bug
I got same issue #492 today when I troubleshooting user cluster issue. then use PR #494 to ssh node.
The result exit directly without call cleanup method after port not reachable, which caused
security group
andec2 instance
resource leakage.The text was updated successfully, but these errors were encountered: