1.8b1: Can't filter servers by owner correctly if owner is subset of another owner

Bug #1441864 reported by Larry Michel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
1.8
Fix Released
Low
Blake Rouse

Bug Description

We have following list of owners:

oil, oil-slave-1, oil-slave-2, ..., oil-slave-9, oil-slave-10, oil-slave-11, oil-slave-12

It works for oil-slave-2 to oil-slave-12 but does not work for oil. oil returns all nodes deployed by owners in that list and oil-slave-1 returns all servers deployed by oil-slave-1, oil-slave-10, oil-slave-11 and oil-slave-12

Tags: ui ux oil

Related branches

Revision history for this message
Blake Rouse (blake-rouse) wrote :

I don't want to match specifically on a term in a search because it makes the live search sucky. Example being if the owner is "oil" and I start typing "owner:o" and nothing shows up until I get to "owner:oil".

Only way I can think about fixing this is to:

1. Rename your users. :-)

OR

2. We give a specifier saying it needs to be an exact match. Like "owner:=oil". Don't know if I really like the "=" maybe come up with something better.

Changed in maas:
status: New → Triaged
importance: Undecided → Low
tags: added: ui ux
Changed in maas:
milestone: none → 1.8.0
Revision history for this message
Larry Michel (lmic) wrote :

Here's an interesting scenario. If I click on commissioning status then my list contains the server that failed commissioning. According to this example, the commissioning state would still apply to a server that's already failed commissioning which is not accurate. Since "commissioning" is in "Failed commissioning" then that's consistent with what we've seen with tag filtering.

tags:(hw-sm15k-former-hwok) status:(Commissioning)

FQDN | MAC Power Status Owner Cores RAM (GB) Disks Storage (GB)
hayward-28.oil Failed commissioning 8 16 2 429.0
hayward-55.oil Failed commissioning 8 32 2 429.0

Revision history for this message
Blake Rouse (blake-rouse) wrote :

The agreed upon way of doing this is to place "=" before each search entry by default using the filters.

Changed in maas:
milestone: 1.8.0 → 1.9.0
Changed in maas:
status: Triaged → In Progress
assignee: nobody → Blake Rouse (blake-rouse)
Changed in maas:
status: In Progress → Fix Committed
Revision history for this message
Blake Rouse (blake-rouse) wrote :

This already landed in 1.8. Must have forgot to link the branch to this bug. I am unable to find that exact merge but I checked the 1.8 code and it is present.

Changed in maas:
status: Fix Committed → Fix Released
no longer affects: maas
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.