VMware Cloud Community
qc4vmware
Virtuoso
Virtuoso

Anyone successful at upgrading 6.0.1 to 6.1 in a distributed install?

I'm just curious if anyone on here has been successful in upgrading a distributed install.  We have 2 nodes running the model manager web behind a vip, 2 nodes running the manager service + DEM Orchestrator behind a vip, and additional nodes running DEM workers and agents.  vCAC CAFE servers are also behind a VIP (3 nodes)This all installed without much of a hitch as a fresh install but the upgrade to 6.1 is not cooperating.  Here is the end of the install log showing the error:

C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\DeployRepository.xml(864,5): error MSB3073: The command ""C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\RepoUtil.exe" Model-Uninstall -f DynamicOps.ManagementModel.dll -v" exited with code 1.

[11/7/2014 7:36:04 PM]Done Building Project "C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\DeployRepository.xml" (InstallRepoModel target(s)) -- FAILED.

[11/7/2014 7:36:04 PM]

[11/7/2014 7:36:04 PM]Build FAILED.

[11/7/2014 7:36:04 PM]

[11/7/2014 7:36:04 PM]"C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\DeployRepository.xml" (InstallRepoModel target) (1) ->

[11/7/2014 7:36:04 PM](UnInstallRepoModel target) ->

[11/7/2014 7:36:04 PM]  C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\DeployRepository.xml(864,5): error MSB3073: The command ""C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\RepoUtil.exe" Model-Uninstall -f DynamicOps.ManagementModel.dll -v" exited with code 1.

[11/7/2014 7:36:04 PM]

[11/7/2014 7:36:04 PM]    0 Warning(s)

[11/7/2014 7:36:04 PM]    1 Error(s)

[11/7/2014 7:36:04 PM]

[11/7/2014 7:36:04 PM]Time Elapsed 00:00:37.84

[11/7/2014 7:36:04 PM]Failed to initialize repository

I have built out a couple of fresh 6.0.1 environments and this is a consistent error.  My next plan is to try building out a distributed install but not use an load balancers in the mix to eliminate that as an issue.  Our lab which was a simple install upgraded with no issues

Tags (2)
3 Replies
pizzle85
Expert
Expert

did you ever find a resolution to this? i'm experiencing the same issue upgrading a 6.1.1 distributed install to 6.2.

0 Kudos
sbeaver
Leadership
Leadership

I would give this a try, when upgrading the 1st node, remove the second from the LB.  I have had issues when I keep all the nodes behind the LB during the upgrade

Steve Beaver
VMware Communities User Moderator
VMware vExpert 2009 - 2020
VMware NSX vExpert - 2019 - 2020
====
Co-Author of "VMware ESX Essentials in the Virtual Data Center"
(ISBN:1420070274) from Auerbach
Come check out my blog: [www.virtualizationpractice.com/blog|http://www.virtualizationpractice.com/blog/]
Come follow me on twitter http://www.twitter.com/sbeaver

**The Cloud is a journey, not a project.**
pizzle85
Expert
Expert

Thanks sbeaver, that resolved the issue!

Just to clarify, I have two IaaS Web servers and two IaaS MGR servers which include DEM and Agents. I initially installed the model manager on WEB1 (not really sure if this matters). I stopped the WWW service on WEB2 (which took it out of service on the LB) then re-ran the update on WEB1 and it was successful.

0 Kudos