ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Xen Orchestra - Community Edition - Installing with Yarn

    IT Discussion
    xen orchestra updater ubuntu 16.10 xenorchestra xenserver xen orchestra community xo xoce xcp-ng debian ubuntu
    22
    296
    83.0k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • DustinB3403D
      DustinB3403 @notverypunny
      last edited by DustinB3403

      @notverypunny OKay, no worries.

      Export your config file. Build a new XO installation and import the config file. Actually no. That won't work. God im tired.

      Just restore your VM from 4 days ago. Assuming you are backing up XO.

      It's a 10 minute process.

      1 Reply Last reply Reply Quote 0
      • DustinB3403D
        DustinB3403
        last edited by DustinB3403

        Although to ask the question, why haven't you made a GH issue?

        Could be affecting way more people than has been noticed here (and on the XO forums).

        1 Reply Last reply Reply Quote 0
        • DustinB3403D
          DustinB3403
          last edited by

          @notverypunny and @Danp please provide any reports to this GH issue. https://github.com/vatesfr/xen-orchestra/issues/3873

          1 Reply Last reply Reply Quote 0
          • DustinB3403D
            DustinB3403
            last edited by

            Problem solved.

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

            Please look at the information posted here for an answer.

            notverypunnyN 1 Reply Last reply Reply Quote 0
            • notverypunnyN
              notverypunny @DustinB3403
              last edited by

              @DustinB3403 The github issue was closed out before I could interject... I added to the thread and they seem to be saying that it might be something else... still going to try creating a new job, might be simpler than redoing the XO install

              DustinB3403D 1 Reply Last reply Reply Quote 0
              • DustinB3403D
                DustinB3403 @notverypunny
                last edited by DustinB3403

                @notverypunny Post details here.

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

                notverypunnyN 1 Reply Last reply Reply Quote 0
                • notverypunnyN
                  notverypunny @DustinB3403
                  last edited by

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

                  @notverypunny Post details here.

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

                  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

                  1 Reply Last reply Reply Quote 0
                  • DanpD
                    Danp
                    last edited by

                    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

                    DustinB3403D 1 Reply Last reply Reply Quote 0
                    • DustinB3403D
                      DustinB3403 @Danp
                      last edited by

                      @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.

                      1 Reply Last reply Reply Quote 0
                      • DustinB3403D
                        DustinB3403
                        last edited by

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

                        DanpD 1 Reply Last reply Reply Quote 0
                        • DanpD
                          Danp @DustinB3403
                          last edited by Danp

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

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

                          These don't appear to be the same issues to me.

                          DustinB3403D 1 Reply Last reply Reply Quote 0
                          • DustinB3403D
                            DustinB3403 @Danp
                            last edited by DustinB3403

                            @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.

                            DanpD 1 Reply Last reply Reply Quote 0
                            • DanpD
                              Danp @DustinB3403
                              last edited by

                              @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:

                              DustinB3403D 1 Reply Last reply Reply Quote 0
                              • DustinB3403D
                                DustinB3403 @Danp
                                last edited by

                                @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:

                                ....

                                1 Reply Last reply Reply Quote 0
                                • DanpD
                                  Danp
                                  last edited by

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

                                  1 Reply Last reply Reply Quote 2
                                  • geek-babaG
                                    geek-baba
                                    last edited by

                                    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.
                                    
                                    DanpD 1 Reply Last reply Reply Quote 0
                                    • DanpD
                                      Danp @geek-baba
                                      last edited by

                                      @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-babaG 1 Reply Last reply Reply Quote 2
                                      • geek-babaG
                                        geek-baba @Danp
                                        last edited by

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

                                        1 Reply Last reply Reply Quote 1
                                        • travisdh1T
                                          travisdh1 @DustinB3403
                                          last edited by

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

                                          dbeatoD B 2 Replies Last reply Reply Quote 2
                                          • dbeatoD
                                            dbeato @travisdh1
                                            last edited by

                                            @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 🙂

                                            travisdh1T DustinB3403D 2 Replies Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 4
                                            • 5
                                            • 14
                                            • 15
                                            • 1 / 15
                                            • First post
                                              Last post