Unable to patch VCFA (Automation) to 9.0.1 - LCMVMSP10036

Products

• VCF Operations

Issue/Introduction

• Checking the coredns logs located on the VMSP appliance at /var/log/containers/, entries similar to the following are seen:
  
  [ERROR] plugin/errors: 2 <VCF_Ops_for_Logs_FQDN>. AAAA: read udp <Internal_IP>:44826-><DNS_Server_IP>:53: i/o timeout
[ERROR] plugin/errors: 2 <VCF_Fleet_Mgmt_FQDN>. AAAA: read udp <Internal_IP>:52597-><DNS_Server_IP>:53: i/o timeout
[ERROR] plugin/errors: 2 <MGMT_VC_FQDN>. AAAA: read udp <Internal_IP>:56021-><DNS_Server_IP>:53: i/o timeout
[ERROR] plugin/errors: 2 <WLD_VC_FQDN>. AAAA: read udp <Internal_IP>:58133-><DNS_Server_IP>:53: i/o timeout
[ERROR] plugin/errors: 2 <VCFA_FQDN>. AAAA: read udp <Internal_IP>:38744-><DNS_Server_IP>:53: i/o timeout
[ERROR] plugin/errors: 2 <NSX_FQDN>. AAAA: read udp <Internal_IP>:49745-><DNS_Server_IP>:53: i/o timeout
  
  
• Attempting to resolve the same addresses using nslookup on the VMSP appliance fails.
• Attempting to ping/curl to the same addresses on the VMSP appliance succeeds but there is a visible delay in DNS resolution.

Environment

VCF Operations 9.0.1

Cause

Delays in DNS resolution, likely due to DNS forwarding / DNS recursion.

Resolution

1. An alternative DNS server which performed DNS resolution quicker was chosen.
   This server was added at: VCF Operations >> Fleet Management >> Lifecycle >> VCF Management >> Settings >> DNS
   
   
2. As this task is related to patching VCFA, it is also necessary to change the DNS configuration on the component level.
   VCF Operations >> Fleet Management >> Lifecycle >> Components
   Select the component (Automation), click the ellipsis (...) and then "Update DNS Configuration"
   
   
3. At this point a new task will being to update the DNS configuration.
   During this task, there is a synthetic check. 
   The synthetic check is expected to not complete due to the DNS issue.
   The synthetic check will time out after ~30 minutes.
   When it times out, Retry with the option to skip the synthetic check set to true.
   
   
4. A new version of the Automation appliance will be deployed with the updated configuration.
   Once this is deployed the new appliance will be using the re-configured DNS server and the automation component will display that it is upgraded to version 9.0.1 (VCF Operations >> Fleet Management >> Lifecycle >> Components)