Seems like the client we have in this test can list other users' keypairs: https://opendev.org/openstack/tempest/src/commit/89a6811cd060bdec92f5efa1e53fd90b3961982a/tempest/api/compute/admin/test_keypairs_v210.py#L41-L44
however, the admin client we use in 'tempest cleanup' can't do that, it always lists its own keypairs (even if user_id is passed).
---
the only thing that is different between the manager in the 'tempest cleanup' and the manager in the mentioned test is the credential sourcing mechanism, the test gets the admin manager somehow from this (credentials set to ['primary', 'admin']): https://opendev.org/openstack/tempest/src/commit/89a6811cd060bdec92f5efa1e53fd90b3961982a/tempest/api/compute/admin/test_keypairs_v210.py#L27-L33
while the 'tempest cleanup' gets it using this method: https://opendev.org/openstack/tempest/src/commit/89a6811cd060bdec92f5efa1e53fd90b3961982a/tempest/cmd/cleanup.py#L182-L183
Seems like the client we have in this test can list other users' keypairs: /opendev. org/openstack/ tempest/ src/commit/ 89a6811cd060bde c92f5efa1e53fd9 0b3961982a/ tempest/ api/compute/ admin/test_ keypairs_ v210.py# L41-L44
https:/
however, the admin client we use in 'tempest cleanup' can't do that, it always lists its own keypairs (even if user_id is passed).
---
the only thing that is different between the manager in the 'tempest cleanup' and the manager in the mentioned test is the credential sourcing mechanism, the test gets the admin manager somehow from this (credentials set to ['primary', 'admin']): /opendev. org/openstack/ tempest/ src/commit/ 89a6811cd060bde c92f5efa1e53fd9 0b3961982a/ tempest/ api/compute/ admin/test_ keypairs_ v210.py# L27-L33
https:/
while the 'tempest cleanup' gets it using this method: /opendev. org/openstack/ tempest/ src/commit/ 89a6811cd060bde c92f5efa1e53fd9 0b3961982a/ tempest/ cmd/cleanup. py#L182- L183
https:/