)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"56d27532cc51f7c7eaeefc88e87a00f48e7c2a02","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"7a0fa406_5ee287cc","updated":"2026-06-02 14:40:10.000000000","message":"This feels like a bug in Nova, and not something we should be papering over in SDK. Keypair quotas have always been a weird thing in Nova since they are (iirc) the only quota items that are per-user rather than per-project/tenant. I believe they are being heavily reworked [with unified limits](https://specs.openstack.org/openstack/nova-specs/specs/yoga/implemented/unified-limits-nova.html#no-per-user-limits). Perhaps it would make more sense to omit this column entirely? If not, we likely want to fix this at source, in nova.","commit_id":"e78ca08ee22e2f8c642a0ff07d9c4b34c0e91bd9"},{"author":{"_account_id":39044,"name":"Alicja Filipek","display_name":"alaf01","email":"alicja.filipek@cleura.com","username":"alaf01"},"change_message_id":"d91345ac9ba5c9477333fedd73b8e5d35eb4025c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"197a55a3_505e672c","in_reply_to":"52ac6786_f37d6a39","updated":"2026-06-03 11:55:48.000000000","message":"I went for option (b) and updated the implementation and set the key pair usage row to \u0027N/A\u0027. I think leaving it in the table makes sense, as the key pair limits might be relevant to the user, and the user can see at least the \u0027limit\u0027 column.","commit_id":"e78ca08ee22e2f8c642a0ff07d9c4b34c0e91bd9"},{"author":{"_account_id":39044,"name":"Alicja Filipek","display_name":"alaf01","email":"alicja.filipek@cleura.com","username":"alaf01"},"change_message_id":"b87f6145dc5a54a866f9220e0c69e693945b251c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"52ac6786_f37d6a39","in_reply_to":"7a0fa406_5ee287cc","updated":"2026-06-02 15:37:16.000000000","message":"Currently, python-openstackclient returns the wrong value for key-pair. I believe that it is better to remove the column entirely than to show the wrong values. However, currently, there are some quotas for the key-pairs per user, so the command should list them in the output.\nI would not say it is a Nova bug. They handle key pairs per user, not per project, by design, so they are unable to show the key pair quotas. They even support the \"user_id\" parameter, but it is impossible to simply add it as a parameter, as the quotas will be per user, not per project. Maybe omitting the column entirely by default and adding the parameter to the command in case the user is interested in the key-pairs quota would be a solution?","commit_id":"e78ca08ee22e2f8c642a0ff07d9c4b34c0e91bd9"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"4f5e260ddfe573f29152b491626f1c1be814a4f8","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"f9bf8a86_d46ad378","in_reply_to":"7a0fa406_5ee287cc","updated":"2026-06-02 14:53:03.000000000","message":"I forgot about [this note from the api-ref](https://docs.openstack.org/api-ref/compute/#show-the-detail-of-quota):\n\n\u003e  Note\n\u003e \n\u003e `in_use` field value for keypair quota details is always zero. In Nova, key_pairs are a user-level resource, not a project- level resource, so for legacy reasons, the keypair in-use information is not counted.\n\nSo I\u0027m definitely more inclined to either (a) not report this row or (b) do something like set it to null to make it more obvious what\u0027s happening. I don\u0027t think there\u0027s enough value here to do this change client-side","commit_id":"e78ca08ee22e2f8c642a0ff07d9c4b34c0e91bd9"}]}