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

    XO From Source Bug in version 5.26.0

    IT Discussion
    xoce xoa xo source 5.26.0 xen orchestra xen orchestra community bug report
    3
    15
    1.4k
    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.
    • B
      bnrstnr
      last edited by

      Yeah, I can try whatever you want.

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

        @bnrstnr try updating.

        🙂

        Take snaps via xcp-ng center so you can revert should you need to.

        1 Reply Last reply Reply Quote 0
        • B
          bnrstnr
          last edited by

          Running the update script right now.

          Are you guys able to get to the login screen at all? I had to rebuild both of my XOCE VMs from scratch early last week (maybe the week before, it says 12 days uptime) because updating them broke something.

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

            @bnrstnr said in XO From Source Bug in version 5.26.0:

            Running the update script right now.

            Are you guys able to get to the login screen at all? I had to rebuild both of my XOCE VMs from scratch early last week (maybe the week before, it says 12 days uptime) because updating them broke something.

            We can get to the login screen yes, but we cannot login (with any credentials) and as well we can't reset the password for the credentials.

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

              My production VM kept working as expected until I logged out. That's when I first encountered the issue with logging in.

              B 1 Reply Last reply Reply Quote 0
              • B
                bnrstnr @Danp
                last edited by bnrstnr

                @danp said in XO From Source Bug in version 5.26.0:

                My production VM kept working as expected until I logged out. That's when I first encountered the issue with logging in.

                I had to create a new user yesterday (while still on an older build of 5.26.0), I must have logged in and out for testing at least 5 times.

                1 Reply Last reply Reply Quote 0
                • B
                  bnrstnr
                  last edited by

                  Update finished just now and once I logged out, I was NOT able to log back in. "Invalid credentials"

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

                    @bnrstnr said in XO From Source Bug in version 5.26.0:

                    Update finished just now and once I logged out, I was NOT able to log back in. "Invalid credentials"

                    So the same issue, something within the last round of changes is causing this to new and existing users. OK, just revert and don't update.

                    Keep an eye on my GH as well as the XO GH pages.

                    1 Reply Last reply Reply Quote 0
                    • B
                      bnrstnr
                      last edited by

                      I'll try to check logs and see when exactly the last time I updated was. Maybe it can help determine which commits broke it

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

                        Oddly 5.26.0 was released 12 days ago, so if you build on release day and your system works, than it was something within that 11 day span.

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

                          JIC anyone needs help to get back up and running, this worked for me --

                          git checkout 0ad6c073ee1538887e13ebec7d3420fcace4d86e
                          yarn; yarn build
                          sudo systemctl restart xo-server.service
                          
                          DanpD 1 Reply Last reply Reply Quote 3
                          • DanpD
                            Danp @Danp
                            last edited by

                            This issue is now resolved. I had to issue the command git checkout master before the standard upgrade process would work again.

                            1 Reply Last reply Reply Quote 3
                            • 1 / 1
                            • First post
                              Last post