5 Replies Latest reply on Jun 5, 2019 7:32 AM by rm_bk

    VCSA 6.7U2 VAMI Update Fails With "Check the URL and try again"

    rm_bk Lurker

      My VCSA can't connect to the update source.  Tailing /var/log/vmware/applmgmt/applmgmt.log reveals:

       

      2019-04-18T19:10:49.671 [19010]ERROR:vmware.appliance.update.update_functions:Can't read JSON file /etc/applmgmt/appliance/software_update_state.conf [Errno 2] No such file or directory: '/etc/applmgmt/appliance/software_update_state.conf'

       

      Not sure if that's related.  Later I see:

       

      2019-04-18T19:11:00.264 [19010]DEBUG:vmware.appliance.update.update_functions:runCommandAndCheckResult failed: LocalizableException({'id': 'com.vmware.appliance.update.download_failed', 'args': [], 'default_message': 'Download failed'}, '', '--2019-04-18 15:10:50--  https://vapp-updates.vmware.com/vai-catalog/valm/vmw/8d167796-34d5-4899-be0a-6daade4005a3/upgrade_info.xml\nResolving vapp-updates.vmware.com... 184.27.136.35, 2600:1402:f000:385::2ef, 2600:1402:f000:3a1::2ef\nConnecting to vapp-updates.vmware.com|184.27.136.35|:443... failed: Connection timed out.\nConnecting to vapp-updates.vmware.com|2600:1402:f000:385::2ef|:443... failed: Network is unreachable.\nConnecting to vapp-updates.vmware.com|2600:1402:f000:3a1::2ef|:443... failed: Network is unreachable.\n')

      2019-04-18T19:11:00.264 [19010]DEBUG:vmware.appliance.update.update_b2b:Index file not present for the url https://vapp-updates.vmware.com/vai-catalog/valm/vmw/8d167796-34d5-4899-be0a-6daade4005a3/upgrade_info.xml

       

      But when I curl to those URL's from the VAMI bash shell, I can retrieve them just fine.  What gives?  We do use a proxy server.  When I refresh the VAMI update page to retry, netstat reveals:

       

      tcp 01 contoso:47782 as-40816.engx.vmw:httpsSYN_SENT
      tcp 01 contoso:46324 a104-74-67-235:www-httpSYN_SENT
      tcp 01 contoso:33058 a104-74-67-235.de:httpsSYN_SENT

       

      Oopsie, it's not using our proxy.  But curl is definitely using it.  /etc/sysconfig/proxy is present and properly formatted per kb article -- both http and https are present.  Wat do?