Xen Orchestra - Community Edition - Installing with Yarn

Danp

https://github.com/vatesfr/xen-orchestra/issues/3880

geek-baba

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.

Danp

@shwetkprabhat I recently updated the script to deal with the expired repo key. Let us know if you run into any issues when you do update. :smiling_face:

geek-baba

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

travisdh1

@DustinB3403 Got this running on my home lab box tonight. Worked great.

dbeato

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

@DustinB3403 Got this running on my home lab box tonight. Worked great.

Let us know how your backups are working

travisdh1

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

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

@DustinB3403 Got this running on my home lab box tonight. Worked great.

Let us know how your backups are working

Hah, I'll have to try hooking it to my B2 first. Might be "interesting" all around with the backups!

DustinB3403

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

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

@DustinB3403 Got this running on my home lab box tonight. Worked great.

Let us know how your backups are working

There was an issue that was just patched yesterday that affected backups.

So you may need to update.

bnrstnr

@travisdh1 Make sure you use 2 vcpu in your XOCE VM if you want to use Delta backups, I believe they won't merge otherwise.

Danp

@bnrstnr Actually, that should be fixed now as well.

DustinB3403

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

@bnrstnr Actually, that should be fixed now as well.

Was that a bug? I was under the impression it was a new requirement.

bnrstnr

@Danp As of last week it was still affecting me. If he wants to try with 1, it can easily be adjusted later and it just starts working.

DustinB3403

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

@Danp As of last week it was still affecting me. If he wants to try with 1, it can easily be adjusted later and it just starts working.

We could likely create a check for 1 cpu and raise a flag for it with an optional "continue" during the installation script.

Not sure if it's worthwhile.

Danp

@DustinB3403 Yes, it was a bug in Jest library, which has since been fixed. They bumped the version requirements yesterday, so a rebuild should now require v24 (I think) or greater.

Danp

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

We could likely create a check for 1 cpu and raise a flag for it with an optional "continue" during the installation script.

Not sure if it's worthwhile.

Not worth the effort IMO. You could add a comment to the troubleshooting section.

bnrstnr

I was thinking about adding the check because the XOA VM is built with 2 cpu, just to keep it consistent with the devs.

DustinB3403

I've updated the troubleshooting docs with the new dependencies and system performance and general troubleshooting.

DustinB3403

This command would tell the user (us) how many CPU's the host has.

cat /proc/cpuinfo | grep siblings | uniq

But again, not sure if we want to start requiring more than 1 vCPU for this since the system does work with just the 1. Maybe leaving this to the troubleshooting documentation is best.

bnrstnr

There may be another issue updating to 5.37.0. Just killed my XOCE, reverting to snapshot now and looking into things.

EDIT: Yep, there's an issue with Babel
https://github.com/vatesfr/xen-orchestra/issues/4052

geek-baba

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.