vSatellite 'unable to remote...no such host' (Solution)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

vSatellite 'unable to remote...no such host' (Solution)

L0 Member

I've installed a vSatellite on a Ubuntu VM in our GCP tenant to help managed cloud-based workloads. As a standard practice, we build VMs with a traditional FQDN in Cloud DNS in a Shared VPC / Inter-connect topology. When trying to create a new Machine type and using the remote machine's FQDN, Venafi returns:

 

"An error occurred while attempting to connect to the machine. The error message was 'unable to remote: unknown error Post "https://<FQDN>:5985/wsman": dial tcp: lookup <FQDN> on 10.43.0.10:53: no such host'"

 

I found this is due to the local K3s CoreDNS not having a resolver pointed to GCPs link-local metadata server IP (169.254.169.254). Tried a couple of different solutions, but directly editing the CoreDNS config-map was lost each time the server was rebooted or the vSatellite was restarted. The better solution was to add add the following configuration files to the /etc/rancher/k3s directory since these don't seem to be touched during restarts.

$ sudo tee -a /etc/rancher/k3s/resolv.conf <<EOF nameserver 169.254.169.254 EOF$ sudo tee -a /etc/rancher/k3s/config.yaml <<EOF kubelet-arg: - "resolv-conf=/etc/rancher/k3s/resolv.conf" EOF

Just wanted to share in case anybody else out there has run into something similar with their Cloud provider.

0 REPLIES 0
  • 10 Views
  • 0 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!