Juju status with selector matching on ports substring
Bug #1988709 reported by
Haw Loeung
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Medium
|
Vitaly Antonenko |
Bug Description
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.
"""
Changed in juju: | |
assignee: | nobody → Vitaly Antonenko (anvial) |
Changed in juju: | |
status: | Triaged → In Progress |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Changed in juju: | |
status: | New → Triaged |
Changed in juju: | |
milestone: | 2.9.35 → 2.9.37 |
Changed in juju: | |
milestone: | 2.9.37 → 2.9.38 |
Changed in juju: | |
status: | Triaged → In Progress |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
status filtering has always been somewhat hit and miss sadly