In my previous posts I wrote about the upgrade of vCSA (vCenter Server Appliance) from version 5.5 to 6.0.
In all my lab testing the upgrade runs without any errors. On our production site I was doing the upgrade and the migration went fine until the new appliance boots for the first time.
VMware closed my call, because of an unsupported way getting vCenter Server for Windows to the vCSA 5.5. Everything runs in the vCSA 5.5. The upgrade fails and with the migrated database there is no support.
Fortunately the services on the old vCSA 5.5 came up running and I didn’t have to do a lot of work for rollback.
I’ve searched in VMware KB and community. I’ve made several steps (based on the information from KB and community)
- Set only one DNS server in the upgrade wizard
- Add static binding for the temporary name and IP of vCSA
- Truncate history data on the old side
The logfile vpostgres-firstboot.py_10658_stderr.log don’t give much information.
Severall skipped messages, which were also there in my lab tests, and at the end “Upgrade import step failed” and “vPostgres firstboot(action=firstboot) failed”
The other logs inside the vCSA didn’t show me any curious messages, so I’ve decided to open a call at VMware support.
I will update this post with new information as soon as I become them.
Updates ordered descending:
Update 21.07.2015 14:00
The manager has called me. He excused the late call (is he reading my blog :) ?). We can’t escalate our failure, because our support level (Production Support) does not match to root cause analysis.
Update 21.07.2015 07:00
The ticket ist closed with the last posted reason. I’ve tried to get the manager of the support team, but no more reactions :(
Update 09.07.2015 14:09
Received information from Escalation Engineer. The database error is the result of converting the database from Windows vCenter Server to vCSA.
It’s really sad, because the vCSA 5.5.0 runs perfectly with the converted database.
The Support Engineer told me to set up a new installation of vCSA 6 and connect the ESXi servers to it.
Update 03.07.2015 11:27
The Support Engineer escalates the Request and needs additional data
- database embedded or external?
- database manual changed (vor example converted from Windows vCenter DB)?
- log bundle from vCenter 5.5 (kb.vmware.com/kb/1011641)
Update 03.07.2015 10:40
The VMware support contacted me and wants that I increase the amount of memory in the source vCSA from 8GB to 16GB. If I already have 16GB configured I should set it +4GB.
The upgrade wizards runs in the same way and unfortunately in the same error (Memory set to 16GB and after that 20GB for a second test)
Now Support, it’s on you again…
Update 01.07.2015 15:56
The support need some extra time to view all logs I’ve sent.
I should check that passwords for root and firstname.lastname@example.org are valid and not expired…
Weird, if they were expired, how should I authenticate within the upgrade wizard? :(
Hope I’ll get more information tomorrow.
Update 01.07.2015 09:03 – Call opened
VMware acknowledges Support Request
I’ve uploaded the screenshot, the logs generated from my workstation and the files from /var/log to VMware
Now waiting for response