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

    Filters not working correctly

    Scheduled Pinned Locked Moved Solved Management
    15 Posts 3 Posters 486 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.
    • olivierlambertO Offline
      olivierlambert Vates 🪐 Co-Founder CEO
      last edited by

      Let me ask @julien-f to take a look

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

        @RicknTX1 The previous behavior was a bug which had a number of issues, it was fixed by https://github.com/vatesfr/xen-orchestra/commit/1b6ec2c54

        It would indeed be nice to support this but it's not a priority at the moment: https://github.com/vatesfr/xen-orchestra/issues/2104

        julien-f created this issue in vatesfr/xen-orchestra

        open [Complex matcher] add automatic link resolution #2104

        0 julien-f committed to vatesfr/xen-orchestra
        fix(xo-web/home): don't search in linked objects (#6881)
        
        Introduced by 59289840697eedd39429246d856201261865dc4a
        
        For instance, searching the UUID of a running VM was showing all other VMs on the same host due to the UUID being present in their `container.residentVms`.
        R 1 Reply Last reply Reply Quote 0
        • R Offline
          RicknTX1 @julien-f
          last edited by

          @julien-f Ahh ok.. Good to know!

          Right now, in the given state I haven't found means to getting a list of active running and non-running machines for a given host.

          Using the Home / VM List and selecting Hosts under filters, then grabbing the host in there only shows actively running machines. If I've just powered up the hosts and want to quickly filter all machines as I did in the past under the bug, I cannot.

          Right now... The only way to get a list of everything is to remove power_state:running, but that gets ugly quickly as it shows literally every machine and you have to find/seek manually down the list to take action on those guests.

          Beyond that, I'm having to switch over to the host and pull up XOLite which gives me a bit quicker of a chance to see the machines and power them up before going back to XO.

          Thank you for getting back to me on this.. it was definitely a nice feature (cough cough bug) that worked well. We'll see what's to come in the features of the future 🙂

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

            @RicknTX1 I have made a change that should suite your need: https://github.com/vatesfr/xen-orchestra/commit/1718649e0c6e18fd01b6cb3fb3c6f740214decc4

            Please keep me posted if you have any issues 🙂

            0 julien-f committed to vatesfr/xen-orchestra
            feat(xo-server/vm.$container): points to host if VDI on local SR
            
            Fixes https://xcp-ng.org/forum/post/71769
            julien-fJ 1 Reply Last reply Reply Quote 0
            • julien-fJ Offline
              julien-f Vates 🪐 Co-Founder XO Team @julien-f
              last edited by

              Keep in mind than non-running VMs on shared SRs are not in a host and therefore will only be visible when filtering by pool.

              1 Reply Last reply Reply Quote 0
              • R Offline
                RicknTX1
                last edited by

                Amazing work!

                All of my guest machines are local, no shared SRs for now in the lab. This should get things back on track again!

                Do I just need to do another git checkout/git pull --ff-only as noted in the "From the sources" section of the documentation to get the change and build it in?

                Thanks again for doing this!! I've all but gone completely away from xcp-center with the amazing work in xo and xolite that has been done. I know that's the goal anyhow!

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

                  @RicknTX1 Yes, you need to fetch latest changes and rebuild.

                  R 1 Reply Last reply Reply Quote 0
                  • R Offline
                    RicknTX1 @julien-f
                    last edited by

                    @julien-f Hello.. I went ahead and did a pull/build this morning using the from sources steps I usually apply from the documentation.

                    I'm showing XO commit b8919 and upon testing, it doesn't appear to be providing results if I simply type in the host name in there or partial hostname. I gave the XO a reboot for good measure as well.

                    Any other tests I can run here or way possible to be sure I have the latest update with the adjustment in there? Maybe I missed a step?

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

                      @RicknTX1 I was unclear, you cannot use a hostname as it is related to the issue I linked before. BUT, the host selector should work for halted VMs.

                      R 1 Reply Last reply Reply Quote 0
                      • R Offline
                        RicknTX1 @julien-f
                        last edited by

                        @julien-f Ahh.. perfect!

                        This a huge help until the other matter can be dealt with. I see it now and the testing is successful with this change.

                        Thank you again to you and the team!

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