I've setup 3 7.6 vRA/vRO environments (lab, test, and prod) for a migration from 7.5 to 7.6 . All 3 are vRA 7.6 + HF19 and vRO with the vco-188.8.131.526135113-17222700.noarch.rpm update applied. I've already migrated my lab and test environments and prod is still a fresh build awaiting migration.
I'm seeing variation in all 3 environments on many of the plugin versions. I would expect them all to be exactly the same. For example:
Is anyone aware of a known issue of any sort? It appears to me as if the test environment has the most up to date versions in all cases and has a VCO plugin version of 184.108.40.20622702 which is in alignment with the numbers following the - in the patch name of vco-220.127.116.116135113-17222700.noarch.rpm. Both of the other deployments are showing 18.104.22.16823317 as the VCO plugin version.
These were all built at the same time but one difference is the migration from 7.5 to 7.6 in the lab environment the vRA/vRO hotfixes were not applied it was all GA. For the test migration vRA+vRO plugins were applied prior to the migration being run. I did not record the plugin levels prior to running the migration but I'm nearly positive I had confirmed everything was at the same level so I'm wondering if the migration "fixed" something? Unfortunately I would not be able to confirm without reverting to a snapshot which I'm not keen to do at the moment as I've got everything working and would hate for a slip to cause me a bunch of grief if this is easily fixable... like I can just pull the plugins from test and install them in the other environments and call it a day.
Thanks for your response. As I said in my original post I'm aware I can simply update them this way but I want to get at the root of why, during the patching, I've resulted in this strange mix of versions. I'll open case with VMware and see where support goes with this then I'll update this thread.