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

    "An error has occurred" message on every VM's Disks tab

    Scheduled Pinned Locked Moved Xen Orchestra
    5 Posts 2 Posters 234 Views
    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.
    • JamfoFLJ
      JamfoFL
      last edited by

      Good afternoon and happy holidays!

      I am currently running XO from sources. Commit #bb3b8 (just ran the update before submitting this ticket at 12:05 PM Eastern Time on 12/08/2023).

      Everything had been working normally, and is still working for the most part, until I updated the latest commits back on Monday afternoon. Since then, I get the following on the Disks tab for every VM on every host:
      b6909e10-860c-4c3f-9fd1-1af0e5fb9b94-image.png

      Updating to the latest available commit at the time of typing, #bb3b8, has not fixed the issue. This is the only tab in all of Orchestra that is not working properly. I also have found that if I go to the Local Storage for each host and go to the Disks tab from that location, I can see each of the disks, no problem.

      So, something seems to be preventing the data from being displayed on that single tab for all VMs on all hosts. This has not affected the operation of any VM or had any other side effects; just the display of disk information on that one tab in the VM itself is broken.

      I welcome any suggestions! Thank you all!

      A 1 Reply Last reply Reply Quote 0
      • A
        Andrew Top contributor @JamfoFL
        last edited by

        @JamfoFL I just updated XO from commit 2dcb5 to commit bb3b8 and it's still working correctly for me. Did you update anything else on the OS? What version of Node are you running?

        JamfoFLJ 1 Reply Last reply Reply Quote 0
        • JamfoFLJ
          JamfoFL @Andrew
          last edited by

          @Andrew Thank you for the quick reply!

          I have two redundant copies of Orchestra so I can test and have the same error message on both.

          On copy number one, I am still on an older commit, #4a5bc. This one is running on Node v18.18.2.

          On copy number two, I am on the latest commit, #bb3b8. This one is also running on Node v18.18.2.

          Nothing was changed on either version of Orchestra or the underlying Ubuntu OS, only the commit was updated. Was there some kind of update to Node that needs to be applied manually?

          Thanks once again!

          A 1 Reply Last reply Reply Quote 0
          • A
            Andrew Top contributor @JamfoFL
            last edited by

            @JamfoFL Current Node version is v18.19.0, but that should not matter as v18.18.2 is good enough. Maybe XO is having problems talking to XCP. You can try a toolstack restart on XCP and reboot XO.

            JamfoFLJ 1 Reply Last reply Reply Quote 0
            • JamfoFLJ
              JamfoFL @Andrew
              last edited by

              @Andrew Thank you Andrew... sorry it took me a while to get back to you. It seems every time I have to go and update Node they change the method you need to do so and it takes me forever to figure out what I'm supposed to do.

              I still haven't figured that out, but that's on me. However, restarting the toolstack did not fix the issue, but restarting the XO Ubuntu host server did.

              I've not seen anything like that before, where I've had to reboot the entire host server after applying commits... but if it works, I shall not argue!

              Thank you again for all of your help. I hope you have a wonderful weekend and a fantastic holiday season.

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