Highlighted
Enthusiast
Enthusiast

vROPS 8 Upgrade Bug?

I have run into the below error in both my lab and production environments when running the assessment tool. It's not clear what is failing on the checks. I did open a support case this morning but wanted to also post here...

vrop_error.jpg

22 Replies
Highlighted
Commander
Commander

I had a similar thing. It would seem that the upgrade to 8.0 runs the precheck as part of the upgrade now as well If the pre check fails on something the upgrade will also fail. it looks like you are failing on the same thing i was here is the end of the list you cant see. guessing it may be a browser bug

pastedImage_0.png

The strange thing for me was my admin account had not expired. I checked bu su admin on each host and it worked fine. I got around it by changing my admin password

0 Kudos
Highlighted
Enthusiast
Enthusiast

Hello!

I just installed the Assessment Tool a second time and it reports no issues. But the Update from 7.5 to 8.0 fails...

pastedImage_0.png

Drink coffee.. Do stupid things faster with more energy...
0 Kudos
Highlighted
Enthusiast
Enthusiast

So I was waiting to post until I was for sure, but I had also discovered after looking at the logs it was getting hung up on the admin account even though it is not expired. I changed the account password in the LAB environment earlier this morning and the upgrade finally started. It's been running for a few hours now, longer than expected since this was a simple LAB deployment with not much data.

0 Kudos
Highlighted
Enthusiast
Enthusiast

Here we go....

VMware Knowledge Base

Upgrade to vRealize Operations Manager 8.0 fails due to the admin or root account password (75195)

"That is a known show stopper for the upgrade to 8.0, and there's 2 different "admin" accounts - one for the UI and one for the OS. They should both have the same password, but if you reset the admin password via the UI, I do not believe it changes it on the OS. "

Highlighted
Commander
Commander

My lab took about 3h for the upgrade. Dont forget this is also a OS migration to photon so i expected it to take a while

0 Kudos
Highlighted
Enthusiast
Enthusiast

Found the Solution... if the root Disk (Harddisk 1) is smaller than 20 GB the setup can not create the Paration Table.

Drink coffee.. Do stupid things faster with more energy...
0 Kudos
Highlighted
Enthusiast
Enthusiast

Upgrade from 7.5 to 8.0 stuck at stage 4/9.

During upgrade it creates an new partition /photo-live with a size of 4.3GB.
a few moments later this new partition is 100% used an upgrade stops:

pastedImage_0.png

Funny thing is, that prechecks are okay:

pastedImage_1.png

Does anyone see the same behaviour?

0 Kudos
Highlighted
Enthusiast
Enthusiast

The update takes a while just wait. /dev/sdc1 ist a mounted ISO as far as i know.

Drink coffee.. Do stupid things faster with more energy...
0 Kudos
Highlighted
Enthusiast
Enthusiast

Hi Robert

Thanks for your reply.

/dev/sdc1 was empty after creation and then filled up in 1-2 minutes.

It's already running for about 4 hours, but I will wait until tommorrow morning. It's only my test-system.

Highlighted
Contributor
Contributor

after I changed Admin  password, it stucked in"4 of 9" for 24 hours.

It may have some bug

0 Kudos
Highlighted
Contributor
Contributor

I have the same situation,stucked at 4/9 more than 24 hours。

0 Kudos
Highlighted
Immortal
Immortal

You folks need to open support requests.

0 Kudos
Highlighted
Enthusiast
Enthusiast

Hi there

Opened a support-case this morning.

Hope this will be solved soon.

0 Kudos
Highlighted
Contributor
Contributor

Hello all!

yes, it´s probably a bug, but I managed to solve it.
Have you installed a custom certificate? It was my case.
Just follow this KB article to solve it: https://kb.vmware.com/s/article/2105229
After reloading the default certificate I was able to upgrade from version 7.5 to 8.0 without issues.
Note: the appliance will restart during the upgrade process. You will have to login again at the admin interface. It will continue on step 5 after the reboot.

When the installation is finished, you can reinstall your custom certificate.
Hope this helps. Also hope VMware to solve this.

0 Kudos
Highlighted
Enthusiast
Enthusiast

My 'lab' environment did stick as well at 4/9 for over 24 hours. I eventually blew it away and created fresh as it was just a vanilla deployment. I did however proceed with my upgrade for my production environment and it completed without any issues.

0 Kudos
Highlighted
Contributor
Contributor

After resetting the pw I had to run $VMWARE_PYTHON_BIN $VCOPS_BASE/../vmware-vcopssuite/utilities/sliceConfiguration/bin/vcopsSetAdminPassword.py --reset to get mine to work properly.

Then I passed the assessment...

Then now its hung at .pak files

status shows :

$VMWARE_PYTHON_BIN $ALIVE_BASE/../vmware-vcopssuite/utilities/pakManager/bin/vcopsPakManager.py --action query_pak_files                                       [

    {

        "pak": "vRealizeOperationsManagerEnterprise-80014857694"

    },

    {

        "pak": "VMwarevSphere-7513165964"

    },

    {

        "pak": "MPforLogInsight-7513165958"

    },

    {

        "pak": "ep-ops-ad-103031471"

    },

    {

        "pak": "MPforvRealizeAutomation-7010098145"

    },

    {

        "pak": "AppOSUCPAdapter-8014857707"

...... etc .... manually bringing the pak's back online did not work. I do have a ticket now open

0 Kudos
Highlighted
Contributor
Contributor

Hi all,

I had the same problems and I solved it as follows:

- first back up the appliance

- I had to change the root and admin password

- to increase partition size / dev / sda i used kb https://kb.vmware.com/s/article/75298

If you use Application Remote Collector, it should also be updated https://docs.vmware.com/en/vRealize-Operations-Manager/8.0/com.vmware.vcom.config.doc/GUID-AF30EB3B-... -8AEC-AB44E7E42875.html

I hope this help!

0 Kudos
Highlighted
Enthusiast
Enthusiast

Hi all

I've got news from the support today.

https://kb.vmware.com/s/article/75327  was the solution for me.

Upgrade ran through without any errors.

Hope  this will help you guys.

bye

0 Kudos
Highlighted
Contributor
Contributor

Good day to all.

I was trying to perform the upgrade (from 7.5.0.13165947 to 8.0.0.14857694) and kept failing at step 4 of 9.  My hard disk 1 was at 20GB so I did not suspect it as being the culprit (VM articles about disk space mention to bring it up to 20GB).  Well it turns out I was mistaken.  Added 10GB to it and upgrade went flawlessly.

Hope this can help someone too.

0 Kudos