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

    xcp having issues with dates for vms

    Scheduled Pinned Locked Moved Solved Xen Orchestra
    date
    8 Posts 4 Posters 519 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.
    • D Offline
      damjank
      last edited by

      Hello,

      I found another strange thing - take a look at the attached screenshot:

      Screenshot 2023-02-20 at 15.34.53.png

      It is utterly new host, within new pool. The date on the host itself is OK, is shows correct time started and all functions are working OK.

      So - does anyone have any idea what is this and how it came to be?

      Thx, rgD

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

        @damjank The problem should be fixed on master, please keep us posted if you have any issues 🙂

        https://github.com/vatesfr/xen-orchestra/commit/473d091fa841dd2af5e0ebeeef530418e1e645ba

        0 julien-f committed to vatesfr/xen-orchestra
        fix(xapi/parseDateTime): handle date objects (#6701)
        
        Fixes zammad#12622 zammad#13106 zammad#13136 zammad#13162
        D 1 Reply Last reply Reply Quote 1
        • DarkbeldinD Offline
          Darkbeldin Vates 🪐 Pro Support Team @damjank
          last edited by

          @damjank If I remember correctly you just need to restart your xo-server to solve this.
          On your XOA VM systemctl restart xo-server.
          Are you also sure your host as been restarted after update?

          D 1 Reply Last reply Reply Quote 0
          • D Offline
            damjank @Darkbeldin
            last edited by

            @Darkbeldin OMG, that actually worked 😄 thank you!!!

            DarkbeldinD 1 Reply Last reply Reply Quote 0
            • DarkbeldinD Offline
              Darkbeldin Vates 🪐 Pro Support Team @damjank
              last edited by

              @damjank 😁

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

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

                  FYIW, the apparent root cause is that -for whatever reason- XAPI is sending timestamp with milliseconds instead of just seconds (we expect always seconds) but maybe at some point XO is connecting early during XAPI boot process and get a wrong answer.

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

                    @damjank The problem should be fixed on master, please keep us posted if you have any issues 🙂

                    https://github.com/vatesfr/xen-orchestra/commit/473d091fa841dd2af5e0ebeeef530418e1e645ba

                    0 julien-f committed to vatesfr/xen-orchestra
                    fix(xapi/parseDateTime): handle date objects (#6701)
                    
                    Fixes zammad#12622 zammad#13106 zammad#13136 zammad#13162
                    D 1 Reply Last reply Reply Quote 1
                    • D Offline
                      damjank @julien-f
                      last edited by

                      @julien-f thank you, much appreciated!

                      1 Reply Last reply Reply Quote 0
                      • olivierlambertO olivierlambert marked this topic as a question on
                      • olivierlambertO olivierlambert has marked this topic as solved on
                      • First post
                        Last post