@DustinB3403 thanks for helping out and resolving the issue! I cant thank you enough for the time you spent (remote-ing into the machine yesterday and helping all day today via private messages).

For the larger community it looks like if you create a new config.yaml file, XO will register that as config source and any changes after that is not taken into the account, you should use the default config file created by the script (i.e. /opt/xo-server/.xo-server.yaml) to start with or update the installation using the update script and then manually update the default config file.

Re: Xen Orchestra - Community Edition - Installing with Yarn

Hi - anyone tried XOSAN with XO Community edition? I use a Adaptec raid controller and I keep having issues with it.

@Danp worked like a charm! Updated flawlessly and also repo signature is fixed now!

Hi - with the introduction new channels, should we add the option in the script to choose...
Release channel
As a user, you can now make a choice between two different release channels:

Stable
The stable channel is intended to be a version of Xen Orchestra that is already a month old (and therefore will benefit from one month of community feedback and various fixes). This way, users more concerned with the stability of their appliance will have the option to stay on a slightly older (and tested) version of XO (still supported by our pro support).

Latest
The latest channel will include all the latest improvements available in Xen Orchestra. It is basically the old "default" channel before you could choose. The version available in latest has already been QA'd by our team, but issues may still occur once deployed in vastly varying environments as our user base has.

@Danp worked like a charm! Updated flawlessly and also repo signature is fixed now!

I am seeing another issue with yarn repo signature, I assume the script would be impacted too, did not try to update as I see folks complaining about 5.33.

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23E7166788B63E1E
W: Failed to fetch https://dl.yarnpkg.com/debian/dists/stable/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23E7166788B63E1E
W: Some index files failed to download. They have been ignored, or old ones used instead.

@dustinb3403 Thanks was about to post the logs here and saw your reply, posted on github.

@dustinb3403 said in Xen Orchestra - Community Edition - Installing with Yarn:

https://github.com/Jarli01/xenorchestra_installer/pull/26

I was able to install on 18.04.1, its says successfully installed but for whatever reason not able to access it via the browser. Ran the updated script as well, that was successful too, still not able to access via web browser. Its a fresh install. Very weird...

Hi - anyone tried XOSAN with XO Community edition? I use a Adaptec raid controller and I keep having issues with it.

Re: Xen Orchestra - Community Edition - Installing with Yarn

Hi - anyone tried XOSAN with XO Community edition? I use a Adaptec raid controller and I keep having issues with it.

@danp

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# 

@danp no not working, I meant the yarn command was successful but XOC still not starting

@danp It was in home directory with todays modify date.

yarn gave error so I did sudo yarn and it showed success.