Filters not working correctly

RicknTX1

Hello....

I'm running the from sources build (latest) of XO in my lab. Over the past few months releases, I've noticed that the filter feature I used to have is no longer working like it has in the past.

For example.. Whenever I used to want to bring up all of the guests on a specific host (running or not) .. I used to click on "Home" and in the "VM" view... then in the filter at the top of the screen. In the search, I'd put something like the full name or partial name of the host (e.g. xcp-ng-004 or perhaps ng-004) and it would instantly show a list of guest machines that XO located. This was handy whenever I wanted to quickly get a list of guests on a host that I might have just powered back on. I could then go down the list and select to power them up.

A few months ago, I noticed that it won't do that anymore and shows completely random results of what I actually wanted.

Does anyone know if there was some code change possibly that might have broken this ability possibly? It was a quick and easy way to list all of the guests on a host or get to a specific group of guests in short order.

It appears that the search is only targeting perhaps the guest name and description fields where before it would also search the host column as well in this view.

Thanks for an amazing product and all of the great work here!

julien-f

@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.

olivierlambert

Hi,

Can you give a concrete example so we can check what's going on?

RicknTX1

@olivierlambert Hello... Sure.. Do you need a screenshot example or something specific? Happy to help in anyway I can here for you...

RicknTX1

Easy steps to reproduce things:

Click "Home"
Make sure view is "VM"
In Filters, clear out "power_state:running" and replace with the name of one of your hosts or a partial name (e.g. host is xcp-ng-004 - key in xcp-ng-004 or ng-004).
The results will come up empty or with odd results not related to the search intended.

Workaround for now:
Click "Home"
Make sure view is "VM"
In Filters, select "Hosts" and find your Host to get the filtered listing.
NOTE... this will only show power_state:running since that is in there actively, to get all you have to clear out that from the Filters box.

RicknTX1

Typing in the friendly name of the host returns zero results...

Selecting Host and finding it will show only running devices for that Host:

olivierlambert

Let me ask @julien-f to take a look

julien-f

@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`.

RicknTX1

@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-f

@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-f

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.

RicknTX1

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-f

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

RicknTX1

@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-f

@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.

RicknTX1

@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!