Xen Orchestra - Community Edition - Installing with Yarn
-
@DustinB3403 said in Xen Orchestra - Community Edition - Installing with Yarn:
@notverypunny Post details here.
Done.... I'll be interested to see if there's a solution beyond re-creating the jobs.... not the end of the world, but not exactly elegant
-
I had to roll back to 5.32, because I was still receiving errors after recreating the job. Here's one example --
Jan 17 14:36:31 ubuntu xo-server[19796]: 2019-01-17T20:36:31.133Z - xo:xapi - [DEBUG] exporting VDI xxxxxxx Jan 17 14:36:31 ubuntu xo-server[19796]: 2019-01-17T20:36:31.349Z - xo:xo-server - [WARN] possibly unhandled rejection Jan 17 14:36:31 ubuntu xo-server[19796]: { error: Jan 17 14:36:31 ubuntu xo-server[19796]: { TypeError: Cannot read property 'join' of undefined Jan 17 14:36:31 ubuntu xo-server[19796]: at new XapiError (/opt/xen-orchestra/packages/xen-api/src/index.js:92:28) Jan 17 14:36:31 ubuntu xo-server[19796]: at wrapError (/opt/xen-orchestra/packages/xen-api/src/index.js:113:9) Jan 17 14:36:31 ubuntu xo-server[19796]: at _call.catch.error (/opt/xen-orchestra/packages/xen-api/src/index.js:1129:18) Jan 17 14:36:31 ubuntu xo-server[19796]: at tryCatcher (/opt/xen-orchestra/node_modules/bluebird/js/release/util.js:16:23) Jan 17 14:36:31 ubuntu xo-server[19796]: at Promise._settlePromiseFromHandler (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:512:31) Jan 17 14:36:31 ubuntu xo-server[19796]: at Promise._settlePromise (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:569:18) Jan 17 14:36:31 ubuntu xo-server[19796]: at Promise._settlePromise0 (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:614:10) Jan 17 14:36:31 ubuntu xo-server[19796]: at Promise._settlePromises (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:690:18) Jan 17 14:36:31 ubuntu xo-server[19796]: at _drainQueueStep (/opt/xen-orchestra/node_modules/bluebird/js/release/async.js:138:12) Jan 17 14:36:31 ubuntu xo-server[19796]: at _drainQueue (/opt/xen-orchestra/node_modules/bluebird/js/release/async.js:131:9) Jan 17 14:36:31 ubuntu xo-server[19796]: at Async._drainQueues (/opt/xen-orchestra/node_modules/bluebird/js/release/async.js:147:5) Jan 17 14:36:31 ubuntu xo-server[19796]: at Immediate.Async.drainQueues (/opt/xen-orchestra/node_modules/bluebird/js/release/async.js:17:14) Jan 17 14:36:31 ubuntu xo-server[19796]: at runCallback (timers.js:810:20) Jan 17 14:36:31 ubuntu xo-server[19796]: at tryOnImmediate (timers.js:768:5) Jan 17 14:36:31 ubuntu xo-server[19796]: at processImmediate [as _immediateCallback] (timers.js:745:5) Jan 17 14:36:31 ubuntu xo-server[19796]: [Symbol(originalCallSite)]: Jan 17 14:36:31 ubuntu xo-server[19796]: [ CallSite {}, Jan 17 14:36:31 ubuntu xo-server[19796]: CallSite {}, Jan 17 14:36:31 ubuntu xo-server[19796]: CallSite {} ], Jan 17 14:36:31 ubuntu xo-server[19796]: [Symbol(mutatedCallSite)]: Jan 17 14:36:31 ubuntu xo-server[19796]: [ [Object], Jan 17 14:36:31 ubuntu xo-server[19796]: [Object], Jan 17 14:36:31 ubuntu xo-server[19796]: CallSite {}, Jan 17 14:36:31 ubuntu xo-server[19796]: CallSite {} ] } }Retesting now with 5.32
-
@Danp Julien thinks he knows what it is and plans to fix it tomorrow if you can wait.
Or keep a copy of this installation around for testing.
-
-
@DustinB3403 said in Xen Orchestra - Community Edition - Installing with Yarn:
These don't appear to be the same issues to me.
-
@Danp So you are seeing a different issue. Can you create an issue on GH?
Edit: I assumed you were experiencing the same issue that @notverypunny was seeing.
-
@DustinB3403 said in Xen Orchestra - Community Edition - Installing with Yarn:
Can you create an issue on GH?
I can. Not sure if I will. :face_with_stuck-out_tongue_closed_eyes:
-
@Danp said in Xen Orchestra - Community Edition - Installing with Yarn:
@DustinB3403 said in Xen Orchestra - Community Edition - Installing with Yarn:
Can you create an issue on GH?
I can. Not sure if I will. :face_with_stuck-out_tongue_closed_eyes:
....
-
-
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. -
@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:
-
@Danp worked like a charm! Updated flawlessly and also repo signature is fixed now!
-
@DustinB3403 Got this running on my home lab box tonight. Worked great.
-
@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
-
@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!
-
@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.
-
@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.
-
@bnrstnr Actually, that should be fixed now as well.
-
@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.
-
@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.
