Juju status with selector matching on ports substring

[Haw Loeung]

Hi,

Juju status incorrectly matches on the open "Ports". For example, if you have a bunch of machines with 5666/tcp for NRPE, "juju status 566" matches them all.

I found out by running "juju status 19 21 26" and it returned machine 6. This was because machine 6 had 19103/tcp as one of it's open ports.

If it's a planned feature, it's a silly one and undocumented:

"""
<selector> selects machines, units or applications from the model to display.
Wildcard characters (*) enable multiple entities to be matched at the same
time.
"""

[Ian Booth (wallyworld)]

status filtering has always been somewhat hit and miss sadly

[Vitaly Antonenko (anvial)]

https://github.com/juju/juju/pull/14610

[Haw Loeung (hloeung)]

"""
juju status 707
juju status 7070
juju status 7070/t

707 selector shouldn't show the status of the parca unit
7070 and 7070/t selectors should show the status of the parca unit
"""

I feel that "juju status 7070" shouldn't return machine with port 7070. In fact, I think if we wanted it to return machines with specific ports, it should be something like "juju status tcp/7070" or "juju status udp/7070".

My reasoning is this, say we have machine 80 and all we wanted was that. A user would probably use "juju status 80" but little do they know, they now also get all units with "tcp/80" exposed.

[Vitaly Antonenko (anvial)]

https://github.com/juju/juju/pull/14899

[Vitaly Antonenko (anvial)]

Now we correctly operate with port ranges, and we need to fully specify protocol to filter by ports