Updating XenOrchestra to 5.11
- 
 @shwetkprabhat So is XO working now? FYI, you'll need to issue sudo bashbefore theyarncommand.
- 
 @danp no not working, I meant the yarn command was successful but XOC still not starting 
- 
 @shwetkprabhat Post the output from the following -- sudo bash cd /opt/xo-server rm -rf node_modules yarn
- 
 xoa@xo:~$ sudo bash [sudo] password for xoa: root@xo:~# cd /opt/xo-server root@xo:/opt/xo-server# rm -rf node_modules root@xo:/opt/xo-server# yarn yarn install v0.27.5 [1/4] Resolving packages... [2/4] Fetching packages... error Command failed. Exit code: 128 Command: git Arguments: pull Directory: /usr/local/share/.cache/yarn/v1/.tmp/9c352cb3d905b22933aca1779127b89c Output: error: Pull is not possible because you have unmerged files. hint: Fix them up in the work tree, and then use 'git add/rm <file>' hint: as appropriate to mark resolution and make a commit. fatal: Exiting because of an unresolved conflict. info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command. root@xo:/opt/xo-server#
- 
 Does it help if you enter yarn cache clearbefore hand?
- 
 Why not simply build a new installation? Do you have your configuration backed up? 
- 
 @dustinb3403 said in Updating XenOrchestra to 5.11: Why not simply build a new installation? Do you have your configuration backed up? Good idea, do it the DevOps "burn it down" way. Save the headache of pupates. 
- 
 Updates, damn autocorrect. 
- 
 As much as it's taken to get to this point. I would've already had a new clean instance built. I know @Danp will get you sorted, but if this is production can you afford this amount of down time? 
- 
 Agreed that it would be simpler to just build a new VM. Still, it would be nice to know why it is failing.  
- 
 @danp said in Updating XenOrchestra to 5.11: Agreed that it would be simpler to just build a new VM. Still, it would be nice to know why it is failing.  Avoiding going down the rabbit hole is nice too...  
- 
 FWIW, xo-server updated to 5.11.1 without issue. 



