I put in /etc/profile and not to bashrc because i can't execute it i don't know why. Have you tried to put in your /etc/profile of your PSC source AND destination (its important on both ) ? Thi Wondered if anyone has seen this, before I file a support ticket. Not sure how/why these checks are even running again on phase 2, but I see no viable workaround. For more details check out the server logs." The error surfaced to the installers is "Cannot collect upgrade requirements. This problem occurs due to missing dependency shared library path.īut this README item covers the fix for the FIRST phase on the original PSC you're upgrading, and does not anticipate the check failing on the NEW PSC you are deploying to. The upgrade of a vCenter Server Appliance might fail before the export phase and the error log shows: /opt/vmware/share/vami/vami_get_network: error while loading shared libraries: libvami-common.so: cannot open shared object file: No such file or directory. The upgrade of a vCenter Server Appliance might fail because a dependency shared library path is missing We manage to get past all the phase 1 export stuff - when we hit phase 2 (copying data over), the pre-upgrade checks run again and fail on a well-known issue in the README: Upgrading an external PSC from 6.0 to 6.5. Been beating our heads against this for a day.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |