Comment 5 for bug 1938927

@Adam Thanks for both your responses; really appreciate it. I don't know how I missed `maas LOGIN machines power-parameters`...

@Amy Apologies for the delay getting back to you; please see my next comment (https://bugs.launchpad.net/maas/+bug/1938927/comments/6) for the requested screenshots.

I realise that my findings aren't clearly stated here (discussed internally instead), so starting again below.

With MAAS 2.7.2 (STS MAAS, 2.7.2 (8283-g.72f2ee59d-0ubuntu1~18.04.1)) I found that filtering by power IP address worked, then filtering by serial didn't. I reloaded a few times and it eventually filtered by serial successfully. Despite connecting over our VPN, I don't believe that connectivity was the issue given that when MAAS goes down or the connection is lost, the web UI immediately displays "Connection lost, reconnecting...", but I could be wrong.

I then tried searching for the power address in MAAS 3.0 and this time it worked. Likely by pure coincidence, when I tried this to create the bug report initially. I'm using the 3.0/stable snap, (3.0.0-10029-g.986ea3e45, 2021-06-22 (15003)). Looking at my command history I last restarted MAAS (`sudo snap restart maas`) on 2021-08-12, which is right in the middle of testing/working on this case, so it is possible that a restart resolved the issue.

I couldn't test filtering by serial locally as the machine is not a real one (and thus couldn't be commissioned to obtain a serial number).

Please find attached screenshots from 2.7.2 and from 3.0.0.

From the customer's end the following still needs to be done based on the above:

- Restart MAAS and try again

- Clear browser cache/cookies/etc. and try again

- Try a different browser