This is glanceclient output, but it's happening at the api level.
demo! glance --os-image-api-version 2 member-list --image-id a96be11e-8536-4910-92cb-de50aa19dfe6
+--------------------------------------+----------------------------------+----------+
| Image ID | Member ID | Status |
+--------------------------------------+----------------------------------+----------+
| a96be11e-8536-4910-92cb-de50aa19dfe6 | | pending |
| a96be11e-8536-4910-92cb-de50aa19dfe6 | 8989447062e04a818baf9e073fd04fa7 | rejected |
| a96be11e-8536-4910-92cb-de50aa19dfe6 | 8989447062e04a818baf9e073fd04fa7 | pending |
| a96be11e-8536-4910-92cb-de50aa19dfe6 | 8989447062e04a818baf9e073fd04fa7 | pending |
+--------------------------------------+----------------------------------+----------+
demo! glance --os-image-api-version 2 member-delete a96be11e-8536-4910-92cb-de50aa19dfe6 8989447062e04a818baf9e073fd04fa7
demo! glance --os-image-api-version 2 member-list --image-id a96be11e-8536-4910-92cb-de50aa19dfe6+--------------------------------------+----------------------------------+---------+
| Image ID | Member ID | Status |
+--------------------------------------+----------------------------------+---------+
| a96be11e-8536-4910-92cb-de50aa19dfe6 | | pending |
| a96be11e-8536-4910-92cb-de50aa19dfe6 | 8989447062e04a818baf9e073fd04fa7 | pending |
| a96be11e-8536-4910-92cb-de50aa19dfe6 | 8989447062e04a818baf9e073fd04fa7 | pending |
+--------------------------------------+----------------------------------+---------+
So the workaround is to delete them all. As far as I can tell, when the member does an image-list, the visibility is controlled by the status of the first occurrence of the tenantId. Same thing when the member updates his/her status.
Fix proposed to branch: master /review. openstack. org/48496
Review: https:/