1 Reply Latest reply on Oct 25, 2019 4:08 AM by GBartsch

    Upgrade vCenter Server Appliance 6.0 to 6.5 fails due to "Pre-upgrade check error"

    zhoury Lurker

      Hi,

      I want to upgrade our vCenter Server Appliance from Version 6.0.0 Build 4749546 to Version 6.5 Build 5973321(U1).

       

      At first, upgrade to 6.5, the following error occurs:

      2017-11-06 07:53:08,043 - vCSACliInstallLogger - ERROR - Pre-upgrade check error: 1. Title: DNS server maps host name 193.160.31.42 to address(es) 10 kw-mx.gw.nic.fujitsu.com.,10 yt-mx.gw.nic.fujitsu.com. which seems to be assign not to eth0 ip address or not a local ip address.

      2017-11-06 07:53:08,043 - vCSACliInstallLogger - ERROR - Pre-upgrade check error: 1. Details: DNS server maps host name 193.160.31.42 to address(es) 10 kw-mx.gw.nic.fujitsu.com.,10 yt-mx.gw.nic.fujitsu.com. which seems to be assign not to eth0 ip address or not a local ip address.

      2017-11-06 07:53:08,043 - vCSACliInstallLogger - ERROR - Pre-upgrade check error: 1. Suggested Resolution: Update appliance /etc/hosts or /etc/resolv.conf file to properly access DNS servers or update appliance DNS servers with the proper host name mapping or configure right network configuration on eth0. To check if DNS has record about local host name, execute `dig 193.160.31.42 +short` locally on the appliance, or `nslookup 193.160.31.42` on a windows machine.

      2017-11-06 07:53:08,043 - vCSACliInstallLogger - WARNING - Pre-upgrade check warning: 1. Problem ID: cls.collect_requirements.warning.uid_mismatch

      2017-11-06 07:53:08,043 - vCSACliInstallLogger - WARNING - Pre-upgrade check warning: 1. Title: User vdcs does not have the expected uid 1006

      2017-11-06 07:53:08,043 - vCSACliInstallLogger - WARNING - Pre-upgrade check warning: 1. Suggested Resolution: Please refer to the corresponding KB article.

      2017-11-06 07:53:08,043 - vCSACliInstallLogger - WARNING - Pre-upgrade check warning: 2. Title: The newly deployed appliance FQDN will be set to 193.160.31.42, although the legacy appliance FQDN is set to www.evcp.com. This might result in inability to access the appliance through FQDN www.evcp.com

      2017-11-06 07:53:08,043 - vCSACliInstallLogger - WARNING - Pre-upgrade check warning: 2. Details: The newly deployed appliance FQDN will be set to 193.160.31.42, although the legacy appliance FQDN is set to www.evcp.com. This might result in inability to access the appliance through FQDN www.evcp.com

      2017-11-06 07:53:08,043 - vCSACliInstallLogger - WARNING - Pre-upgrade check warning: 2. Suggested Resolution: To preserve current appliance FQDN, verify that the FQDN matches the configuration of the vCenter Single Sign-On and the vCenter Server certificates. To verify that the FQDN is DNS resolvable - execute `dig www.evcp.com +short` locally on the appliance, or `nslookup www.evcp.com` on a windows machine

       

      Then, I change the DNS of the vcsa 6.0(193.160.31.42) and upgrade again, the following error occurs:

      2017-11-06 08:53:08,464 - vCSACliInstallLogger - ERROR - Pre-upgrade check error: 1. Problem ID: ur.sourceVC.cannotAuthenticate

      2017-11-06 08:53:08,464 - vCSACliInstallLogger - ERROR - Pre-upgrade check error: 1. Title: Failed to authenticate to the legacy vCenter Server using the provided credentials.

      2017-11-06 08:53:08,464 - vCSACliInstallLogger - ERROR - Pre-upgrade check error: 1. Details: A problem occurred during authentication to the legacy vCenter Server using the provided credentials.

      2017-11-06 08:53:08,465 - vCSACliInstallLogger - ERROR - Pre-upgrade check error: 1. Suggested Resolution: Verify that the legacy vCenter Server is up and running. Verify that you provided the correct vCenter Single Sign-On credentials.

      2017-11-06 08:53:08,465 - vCSACliInstallLogger - ERROR - Pre-upgrade check error: 2. Title: Cannot collect component requirements. For more details check out the server logs

       

      At this time,login the vsphere client fails due to "503".

       

      Next,I reboot the vcsa6.0 and I can login successfully and the result of execute "nslookup 193.160.31.42" is "Server:193.160.31.28 Address:193.160.31.28#53 42.31.160.193.in-addr.arpa name = vcsa.evcp.com.".

      So, I upgrade again,and the following error occurs:

      2017-11-06 09:31:01,871 - vCSACliInstallLogger - ERROR - Pre-upgrade check error: 2. Title: Host name 193.160.31.42 is not DNS resolvable, but matches the machine certificates. If you do not configure a valid DNS resolvable hostname mapping, then you might not be able to connect to the vCSA afterwards

      2017-11-06 09:31:01,872 - vCSACliInstallLogger - ERROR - Pre-upgrade check error: 2. Details: Host name 193.160.31.42 is not DNS resolvable, but matches the machine certificates. If you do not configure a valid DNS resolvable hostname mapping, then you might not be able to connect to the vCSA afterwards

      2017-11-06 09:31:01,872 - vCSACliInstallLogger - ERROR - Pre-upgrade check error: 2. Suggested Resolution: Either update appliance /etc/hosts or /etc/resolv.conf file to properly access DNS servers or update appliance DNS servers with the proper host name mapping. To check if DNS server has record about local host name, execute `dig 193.160.31.42 +short` locally on the appliance, or `nslookup 193.160.31.42` on a windows machine.

      2017-11-06 09:31:01,872 - vCSACliInstallLogger - WARNING - Pre-upgrade check warning: 1. Problem ID: cls.collect_requirements.warning.uid_mismatch

      2017-11-06 09:31:01,873 - vCSACliInstallLogger - WARNING - Pre-upgrade check warning: 1. Title: User vdcs does not have the expected uid 1006

      2017-11-06 09:31:01,873 - vCSACliInstallLogger - WARNING - Pre-upgrade check warning: 1. Suggested Resolution: Please refer to the corresponding KB article.

      2017-11-06 09:31:01,873 - vCSACliInstallLogger - WARNING - Pre-upgrade check warning: 2. Title: The newly deployed appliance FQDN will be set to 193.160.31.42, although the legacy appliance FQDN is set to vcsa.evcp.com. This might result in inability to access the appliance through FQDN vcsa.evcp.com

      2017-11-06 09:31:01,873 - vCSACliInstallLogger - WARNING - Pre-upgrade check warning: 2. Details: The newly deployed appliance FQDN will be set to 193.160.31.42, although the legacy appliance FQDN is set to vcsa.evcp.com. This might result in inability to access the appliance through FQDN vcsa.evcp.com

      2017-11-06 09:31:01,873 - vCSACliInstallLogger - WARNING - Pre-upgrade check warning: 2. Suggested Resolution: To preserve current appliance FQDN, verify that the FQDN matches the configuration of the vCenter Single Sign-On and the vCenter Server certificates. To verify that the FQDN is DNS resolvable - execute `dig vcsa.evcp.com +short` locally on the appliance, or `nslookup vcsa.evcp.com` on a windows machine

       

      (attach:upgrade specification JSON file)

       

      Anyone has an idea or had the same problem?

       

      Greetings

      - Christopher