vCenter upgrade problem from 6.0 to 6.5

[jasekera]

Hi guys,

I want to migrate my vCenter server from version 6.0 to 6.5U2. Because, when I restart my vCenter v6.0, the service (vmware-vpxd) is locked and I must manually repair that (Afterwards everything is fine). Of course, I want to upgrade because of other good updates.  I know, that migration is divided into 2 sections. First is installation of new appliance (successfully done) and second is migration from older installation to fresh installation. I have a problem with a pre-upgrade check. I had a problem, that I have a duplicate names for vDS and portgroups something like this (VMware Knowledge Base).​ I didn't repair it manually via database commands, but directly via vCenter's web interface - just renamed it. Afterwards, the new problem has became as you can see in picture attached below.

So, the I downloaded logs and in CollectRequirements_com.vmware.vcdb_2018_07_09_08_14 I can see a problem with Exception: global name 'exceptions' is not defined. Is it a real problem? Do you have any idea how to repair that? Should I attach any other logs?

Thanks in advance.

Jakub

[msripada]

Do you have update manager pointed to the same database server but different instance?

Guess It could not read contents from VUM ..

Can you stop vum and remove it from mob and try the upgrade.. ensure to have vcenter and db snapshot

VMware Knowledge Base

thanks,

MS

[Raj1988]

Ya. Remove VUM .Also check vcdb_req.err if this has anything.

[jasekera]

Hi guys,

I think, that I have not installed any update manager (but I am not sure). It have to be on any and only Windows machine (e.g Windows Server 2012) right? If I search for services.msc on my Windows server machine I found only this:

When I connect to IP_address/mob I can see this:

So, I think that I don't have installed update Manager. Is there a way to better confirm my opinion?

I have a idea, because currently I have vCenter v6.0 and build 3634794 as you can see on the picture below. Just try to patch directly to Update 3e (if possible) and the upgrade directly to vCenter v6.5U2. What do you think?

Thank you for your answer.

Jakub

[jasekera]

Hi Ajay,

please refer to my answer below and there I attached logs and vcdb_req.out returned exit code 0 as you can see below.

Jakub

[msripada]

You need to go to content - > extension manager -> share the screenshot of it or look for vcintegrity in that list of extensions

[Raj1988]

Follow this to remove Update Manager "com.vmware.vcIntegrity" . VMware Knowledge Base

vcdb_req_err.txt has

Password for user postgres:

psql.bin: fe_sendauth: no password supplied

share the file pgpass.conf .

C:\Windows\System32\config\systemprofile\AppData\Roaming\postgresql\pgpass.conf

pgpass.conf file should have the db user and pasword . I believe the file has no password or is empty.

Please update .

[jasekera]

Hi guys,

as you can see below I don't have extension about integrity.

and I didn't find C:\Windows\System32\config\systemprofile\AppData\Roaming\postgresql\pgpass.conf file on my Windows Server 2012 R2. I successfully updated my vCenter appliance into VC-6.0.0U3f-Appliance, but the same problem.

When I am logged directly into SSH shell vCenter appliance v.6.0 I saw this:

Should I create a file with postgres password or any another idea?

Thank you in advance.

Jakub

[jasekera]

Hi guys,

there is a CollectRequirements_com.vmware.vcdb_2018_07_13_15_50.log, anyone can help, please?

2018-07-13T15:50:08.891Z INFO vcdb.const Configuring log folder paths in /var/log/vmware/upgrade

2018-07-13T15:50:08.892Z INFO vcdb.const Retrieving DB type...

2018-07-13T15:50:08.892Z INFO vcdb.const DB type retrieved: PostgreSQL

2018-07-13T15:50:09.34Z INFO vcdb.const Retrieving DB user...

2018-07-13T15:50:09.163Z INFO vcdb.const DB user retrieved: vc

2018-07-13T15:50:10.25Z INFO vcdb.const Retrieving DB password...

2018-07-13T15:50:10.384Z INFO vcdb.const DB password retrieved: ****

2018-07-13T15:50:10.430Z INFO vcdb.const Applying DBM constraints fix..

2018-07-13T15:50:10.496Z INFO vcdb.const DBM fix applied.

2018-07-13T15:50:10.508Z INFO vcdb.const Validating source embedded schema...

2018-07-13T15:50:19.489Z INFO vcdb.const Souce embedded schema validation completed.

2018-07-13T15:50:19.503Z INFO vcdb.const read_db_value:

2018-07-13T15:50:19.503Z ERROR __main__ Upgrade Phase 'vcdb:CollectRequirements' failed. Exception: global name 'exceptions' is not defined

Traceback (most recent call last):

  File "/tmp/vmware-root/tmpvmware134/payload/componentPhaseLauncher.py", line 438, in main

    executionResult = systemExtension(exeContext)

  File "/tmp/vmware-root/tmpvmware134/libs/sdk/extensions.py", line 94, in __call__

    result = self.extension(*args)

  File "/tmp/vmware-root/tmpvmware134/libs/sdk/extensions.py", line 110, in _func

    return func(*args)

  File "/tmp/vmware-root/tmpvmware134/payload/component-scripts/vcdb/__init__.py", line 12, in do_collect_upgrade_requirements

    req = do_linux_collect_req(context)

  File "/tmp/vmware-root/tmpvmware134/payload/component-scripts/vcdb/vcdb_collect_requirements_functions.py", line 298, in do_linux_collect_req

    sizeCore, sizeSet, sizeCoreET = core_set_size_postgres()

  File "/tmp/vmware-root/tmpvmware134/payload/component-scripts/vcdb/vcdb_db_utils.py", line 234, in core_set_size_postgres

    sizeCore = num(get_psql_query_result(sqlCore))

  File "/tmp/vmware-root/tmpvmware134/payload/component-scripts/vcdb/vcdb_db_utils.py", line 36, in num

    except exceptions.ValueError:

NameError: global name 'exceptions' is not defined

Jakub

[daphnissov]

Open a support case with VMware.

[jasekera]

Hi guys,

anyone with solution or advice?

Jakub