Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
While listing the podman volume dangling=true filter shoul be added.
Version-Release number of selected component (if applicable):
Podman 1.6.4
How reproducible:
Always
Steps to Reproduce:
1.podman volume ls -f dangling=true
2.
3.
Actual results:
Error: invalid filter: dangling is an invalid filter
Expected results:
It should ist the podman volumes.
Additional info:
This is on RHEL 7.6
I can reproduce this bug on podman-1.6.4-23.module+el8.3.0+8377+eff33c85.x86_64,
and verifiy it on podman-2.2.1-2.module+el8.3.1+9107+df0d2892.x86_64.
1. podman-1.6.4-23.module+el8.3.0+8377+eff33c85.x86_64
[root@hp-dl360g9-03 ~]# podman volume ls -f dangling=true
Error: invalid filter: dangling is an invalid filter
2. podman-2.2.1-2.module+el8.3.1+9107+df0d2892.x86_64
[root@hp-dl360g9-03 ~]# podman volume ls -f dangling=true
DRIVER VOLUME NAME
local 12cc71b935b10ba5108e5fb7347ff15048577a4dcc9c569ce41e696bb4da5159
local 1a75f3868aaa82b33ab6ca69f7483939272b6d43a7e47afe7348fb3c80338d5e
local 31b65b097edd9c7153a444982a370c486813cf482b74954253c5eb79498dac5c
local 31b78761b203e5468fff82a4f5cd842709edc26a7a0194eab6adbe154ec19394
local 33af4b94579c8944e1a15ad73e42c449c053ef62c8fc4e9b9d887d124c8ab71a
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: container-tools:rhel8 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2021:0531
Comment 27Red Hat Bugzilla
2023-09-15 00:32:24 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days