HCX appliance log bundle collection fails due to host name resolution failure

Products

• VMware HCX

Issue/Introduction

• When generating a log bundle with the "Collect logs for Appliances" option selected, the operation appears to complete successfully in the UI.
• However, when extracting the downloaded log bundle, there are no files found under the directory: <log_bundle_path>/tmp/Fleet-Appliance-<timestamp>/<service_mesh_name>/
• You see similar logs in /common/logs/admin/app.log on HCX Manager.
  

  <timestamp> [TechSupportService_SvcThread-5719, Ent: HybridityAdmin, , TxId: <UUID>] ERROR c.v.v.h.CollectFleetComponentTechSupportJob- Failed to collect fleet log for appliance Type
  HCX-NET-EXT, resourceId servicemesh-<UUID>
  java.net.UnknownHostException: <Host_FQDN>
          at java.base/java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:229)
          at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
          at java.base/java.net.Socket.connect(Socket.java:609)
          at java.base/sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:305)
          at java.base/sun.security.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:173)
          at java.base/sun.net.NetworkClient.doConnect(NetworkClient.java:182)
          at java.base/sun.net.www.http.HttpClient.openServer(HttpClient.java:509)
          at java.base/sun.net.www.http.HttpClient.openServer(HttpClient.java:604)
          at java.base/sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:266)
          at java.base/sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:373)
          at java.base/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:207)
          at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1187)
          at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1081)
          at java.base/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:193)
          at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1592)
          at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1520)
          at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:250)
          at com.vmware.vchs.hybridity.adapters.vsphere.vim.GuestOperationFacet.getData(GuestOperationFacet.java:66)
          at com.vmware.vchs.hybridity.adapters.vsphere.vim.GuestOperationFacet.downloadGuestFile(GuestOperationFacet.java:49)
          at com.vmware.vchs.hybridity.CollectFleetComponentTechSupportJob.downloadFile(CollectFleetComponentTechSupportJob.java:142)
          at com.vmware.vchs.hybridity.CollectFleetComponentTechSupportJob.doRetryDownload(CollectFleetComponentTechSupportJob.java:90)
          at com.vmware.vchs.hybridity.CollectFleetComponentTechSupportJob.run(CollectFleetComponentTechSupportJob.java:63)
          at com.vmware.vchs.hybridity.messaging.LoggingJobWrapper.run(LoggingJobWrapper.java:41)
          at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
          at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
          at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
          at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
          at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
          at java.base/java.lang.Thread.run(Thread.java:829)

Environment

VMware HCX

Cause

This issue occurs because the HCX Manager is unable to resolve the hostname of the target host. As a result, the system fails to retrieve the log bundle for the HCX Appliance running on that specific host.

Resolution

Review the DNS settings to ensure that the HCX Manager can successfully resolve the target host's name (FQDN).