Hi to all,
we have this problem with our vmware solution.
We have 2 host dell ( vmware vs. 6.5 ) in cluster, connected to a vcenter appliance at the same version 6.5
we want to uograde the vcenter to 6.7 version.
After the first step, when we insert the network information and than wait with the "pre-upgrade checks" we receive this error:
"
Error
Resolution
Finally i've solved this problem.
I've disconnected - remove from inventory - then re-add to the cluster first one host and then the other, so the vcenter pre-check work correctly.
I think it's something similar to the vcdb cleanup suggested before.
Thank you very much for the support
According to the error found within, you have hosts at 192.168.83.42 and 44 at version 5.5, which aren't supported under 6.7.
WARNING: esx-version -> 5.5.0 host IP: 192.168.83.44
WARNING: esx-version -> 5.5.0 host IP: 192.168.83.42
... nope
Then clearly the vcdb doesn't agree. You may want to open an SR to see how to correct the database entries since you already have hosts at those addresses.
Keeping files on the same local storage is normal behavior. But storing files on two different and local repositories is not entirely normal. So it's worth thinking about - is it really necessary?
I'm sorry, I don't understand your response or what it has to do with this thread. Could you clarify, please?
Hello, Chip.
You are very observant. Indeed, I was mistaken. All work slowly, the state regulator is blocking the sites.
In this topic, I wanted to propose to reboot the vCenter. If it does not reboot for a long time it can help.
Finally i've solved this problem.
I've disconnected - remove from inventory - then re-add to the cluster first one host and then the other, so the vcenter pre-check work correctly.
I think it's something similar to the vcdb cleanup suggested before.
Thank you very much for the support
remove/readd did the trick for us too
thank you most kindly
i have the same problem, on precheck 1 host whith esxi 6.0.0 was 5.5.
i cant delete host from inventory because my veeam backup will nonconsistent.
so, lets start
1)connect to vc over ssh
2)use postgresql to edit vcdb
/opt/vmware/vpostgres/9.4/bin/psql -d VCDB postgres
3)check table for incorrect entry
SELECT ip_address, product_version, product_build FROM vpx_host;
4) if one of your host have incorrect esxi version in db just change it))))) [change version, build and ip to your data]
UPDATE vpx_host SET product_version = '6.0.0' WHERE ip_address = '10.0.0.1';
UPDATE vpx_host SET product_build = '7967664' WHERE ip_address = '10.0.0.1';
5)run again precheck and it will work fine)))
Just wanted to say thanks so much for posting that. I was doing my upgrades at work on a Friday evening and was stuck on this. Your post REALLY helped me out!