Description of problem: There's some situation where it would be easier for the admin user to list and/or delete all keypairs. While we understand that it wasn't implemented because some people might see this as a security issue, I think we should consider the fact that we never see or even store the private key. Also, the admin user can normally access the database and get the information, forcing them to bypass the CLI, or use this kind of hack [1] [1] https://orchestration.io/2016/03/14/listing-all-key-pairs-in-openstack/
This has been accepted upstream and should be included in a future 5.5.0/6.0 release.
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 (Release of components for Red Hat OpenStack Platform 17.0 (Wallaby)), 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/RHEA-2022:6543