Uday_Mantri
Enthusiast
Enthusiast

Up-gradation Issues of vROPs 7.5 to vROPs 8.0.1

Jump to solution

We were trying to upgrade vRealize Operations version from 7.5 to 8.0.1.

While performing the same, we got stuck in between the activity, at stage 5 and from there it was not proceeding further. All the pre-reqs are checked and on their place however upgradation got stuck.

pastedImage_0.png

We had considered all the pre-requisites of up-gradation, deleted all the impacted Management Packs, tried to upgrade it keeping the cluster offline and even online but it still gets stuck and does not proceed beyond stage 5. All the pre-checks have been confirmed.

pastedImage_1.png

pastedImage_2.png

pastedImage_5.png

Please help in identifying the issue.

0 Kudos
1 Solution

Accepted Solutions
Uday_Mantri
Enthusiast
Enthusiast

Hi Rick,

Thank You for helping out.

We have already considered the above mentioned KB article along with the known password issue while upgrading, VMware Knowledge Base article 75195.

Actually, we had to open case with VMware and the issue got resolved. There was a problem in controller.properties file at /usr/lib/vmware-vcops/user/conf/controller.

There is a property in this file, "deleteNotExisting=", this property was commented in our 1 node cluster and its default value is false.

We had to uncomment it, set its value to "deleteNotExisting=false" and save the file. After saving it, we set the root/admin password to never expire and performed the upgrade again by removing all the impacted Management Packs (considered Impacted Management Pack list by running the Upgrade Assessment Tool). The upgrade went smoothly.

This particular property entry doesn't come under pre-check, it is supposed to be either true or false and not blank. This value is about removing the entry of a resource from vROPs that was already removed from vCenter earlier.

It seems this value was changed at some point of time earlier to blank and was causing the upgrade to fail. This value does not have any impact on the product.

View solution in original post

0 Kudos
2 Replies
RickVerstegen
Expert
Expert

Do you use IPv6?

Have a look at this article: VMware Knowledge Base

Also check if you have enough disk space available for the upgrade:

VMware Knowledge Base

Blog: https://rickverstegen84.wordpress.com/ Twitter: https://twitter.com/verstegenrick
0 Kudos
Uday_Mantri
Enthusiast
Enthusiast

Hi Rick,

Thank You for helping out.

We have already considered the above mentioned KB article along with the known password issue while upgrading, VMware Knowledge Base article 75195.

Actually, we had to open case with VMware and the issue got resolved. There was a problem in controller.properties file at /usr/lib/vmware-vcops/user/conf/controller.

There is a property in this file, "deleteNotExisting=", this property was commented in our 1 node cluster and its default value is false.

We had to uncomment it, set its value to "deleteNotExisting=false" and save the file. After saving it, we set the root/admin password to never expire and performed the upgrade again by removing all the impacted Management Packs (considered Impacted Management Pack list by running the Upgrade Assessment Tool). The upgrade went smoothly.

This particular property entry doesn't come under pre-check, it is supposed to be either true or false and not blank. This value is about removing the entry of a resource from vROPs that was already removed from vCenter earlier.

It seems this value was changed at some point of time earlier to blank and was causing the upgrade to fail. This value does not have any impact on the product.

View solution in original post

0 Kudos