XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Latest commit smoked NFS remotes

    Scheduled Pinned Locked Moved Backup
    22 Posts 4 Posters 1.9k Views 3 Watching
    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.
    • A Offline
      Andrew Top contributor @julien-f
      last edited by

      @julien-f Working again. Thanks.

      F 1 Reply Last reply Reply Quote 2
      • F Offline
        fataugie @Andrew
        last edited by fataugie

        @Andrew
        So on release 5cf5d on the master, there was a strange issue of when you create a backup job, fill everything in and hit save, the first time it would not save the schedule. Edit the job, and the schedule was not there....so I recreate the schedule and hit save again. This time, the schedule was saved, but the retention count reverts to either null or zero (nothing is shown in the gui), and if you try to run it would complain that you can't have a blank retention in the schedule section. Edit the job again and change the retention and then....if you hit save, is everything finally committed properly.

        In the meantime, I see four more commits have taken place on the Xen Orchestra so I'm updating and will test once that's complete and report my results.

        Thanks for all the hard work guys!

        UPDATE: No joy, same progression through the failures to create a backup job.

        julien-fJ 1 Reply Last reply Reply Quote 0
        • olivierlambertO Offline
          olivierlambert Vates 🪐 Co-Founder CEO
          last edited by

          @fataugie I can confirm and reproduce this bug, thanks for the report!

          F 1 Reply Last reply Reply Quote 0
          • julien-fJ Offline
            julien-f Vates 🪐 Co-Founder XO Team @fataugie
            last edited by

            @fataugie Investigating.

            1 Reply Last reply Reply Quote 0
            • F Offline
              fataugie @olivierlambert
              last edited by

              @olivierlambert said in Latest commit smoked NFS remotes:

              @fataugie I can confirm and reproduce this bug, thanks for the report!

              No problem....If I had any idea how to submit via Github, I would have there....but I'm a novice at best with Git

              julien-fJ 1 Reply Last reply Reply Quote 0
              • olivierlambertO Offline
                olivierlambert Vates 🪐 Co-Founder CEO
                last edited by olivierlambert

                Don't worry, since it's easy to trigger, your report is very valuable even if on this thread and not on Github. Thanks again!

                1 Reply Last reply Reply Quote 0
                • julien-fJ Offline
                  julien-f Vates 🪐 Co-Founder XO Team @fataugie
                  last edited by

                  @fataugie Should be fixed, let me know if there are any issues left!

                  https://github.com/vatesfr/xen-orchestra/commit/194db8d0dd28ccfd058c97e8c16b32d853b26cf8

                  0 julien-f committed to vatesfr/xen-orchestra
                  fix(xo-server/Redis#{add,update}): return complete record
                  
                  Introduced by 32afd5c46
                  
                  Fixes https://xcp-ng.org/forum/post/68664
                  
                  The returned record should not be serialized and should contain the identifier.
                  F 2 Replies Last reply Reply Quote 2
                  • F Offline
                    fataugie @julien-f
                    last edited by

                    @julien-f said in Latest commit smoked NFS remotes:

                    @fataugie Should be fixed, let me know if there are any issues left!

                    https://github.com/vatesfr/xen-orchestra/commit/194db8d0dd28ccfd058c97e8c16b32d853b26cf8

                    Will do! Thanks for the quick attention.
                    I'm currently remote and my network has decided to not let me in so it will be probably 10+ hours until I can get the update installed and tested. I'll report back one way or the other asap.
                    Thanks

                    1 Reply Last reply Reply Quote 0
                    • F Offline
                      fataugie @julien-f
                      last edited by

                      @julien-f OK, it seems to be fixed. I created a job and kicked it off manually and no issues, it seems to be back to normal.
                      Thanks again!

                      1 Reply Last reply Reply Quote 1
                      • olivierlambertO Offline
                        olivierlambert Vates 🪐 Co-Founder CEO
                        last edited by

                        Thank you for your report! 👍

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post