keypair quota error

[zhaolihui]

Description
===========
The nova quota-show was error in key_pairs when add keypair.

Steps to reproduce
==================
1.nova keypair-add k_001
2.nova keypair-list
3.nova quota-show --detail

Expected result
===============
It is correct with key_pairs in_use.

Actual result
=============
Follow command "nova keypair-add k_001", keypair-list display k_001,
but "nova quota-show --detail" was not correct with keypair in_use value.

Environment
===========
1. Devstack with newton version

[jichenjc (jichenjc)]

nova --debug quota-show --user 843b5d1e1c1243babbec558c47823219 --detail

even I use --user will get same result after create one pair, it's still 0

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/403529

[Sean Dague (sdague)]

Automatically discovered version newton in description. If this is incorrect, please update the description to include 'nova version: ...'

[OpenStack Infra (hudson-openstack)]

Change abandoned by Sean Dague (<email address hidden>) on branch: master
Review: https://review.openstack.org/403529
Reason: This review is > 4 weeks without comment, and is not mergable in it's current state. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

[Sean Dague (sdague)]

There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments.

[Alex Xu (xuhj)]

There is a discussion on the Mail-list http://lists.openstack.org/pipermail/openstack-dev/2018-July/132459.html

Sounds like the only thing we can do immediately is updating the API doc https://developer.openstack.org/api-ref/compute/#quota-sets-os-quota-sets about the keypairs in-use field means nothing.

[Ghanshyam Mann (ghanshyammann)]

Yeah, i agree on that plan. As mriedem mentioned in ML about considering the Barbican for keypair business, we should consider that if we are modifying or enhancing the keypair.

For this bug, i will also suggest to update the doc to clear the meaning of 'is-use' field. And later if needed we can think of Barbican support with spec discussion.

[melanie witt (melwitt)]

There is a doc patch proposed for this at https://review.openstack.org/590081

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/590081
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fac7d6f2d23afa94983ab3b09d4c101d85a653d0
Submitter: Zuul
Branch: master

commit fac7d6f2d23afa94983ab3b09d4c101d85a653d0
Author: Vishakha Agarwal <email address hidden>
Date: Thu Aug 9 08:41:36 2018 +0530

    Quota details for key_pair "in_use" is 0.

    This patch updates the api-ref for 'in_use'
    field of quota details for keypair which is
    always 0 as it is user dependant parameter.

    Closes-Bug: #1644457
    Change-Id: I0323c411126314ddf3d689dc3120b039256ae81a

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.