glance member-create doesn't complain when tenant_id doesn't exist

[Jaroslav Henner]

# glance image-create --name temporary_test --id 0bfbc34b-0ec8-4802-8f61-f45f0613fb54
# glance member-create --can-share 0bfbc34b-0ec8-4802-8f61-f45f0613fb54 'I do not exist!'
# echo $?
0
# glance image-delete 0bfbc34b-0ec8-4802-8f61-f45f0613fb54

I expected it to return something greater than 0

[Kent Wang (k.wang)]

Looks like there is a similar problem with nova: https://bugs.launchpad.net/nova/+bug/1317515
and going off the work that's been done with that bug, looks like the keystone authentication may have performance issues

[Belmiro Moreira (moreira-belmiro-email-lists)]

This is an important bug that users frequently run into.

Our users usually use the project name when sharing images.
Because there is no project validation, glance accepts any value.

This is confusing to the user, because the project name is correct and it's accepted.
Also, shown when performing glance "glance member-list" the "Member ID" shows the correct project name.

[Belmiro Moreira (moreira-belmiro-email-lists)]

@k.wang are you still working on this?
We are happy to help.

[Abhishek Kekane (abhishek-kekane)]

AFAIK this by design, feel free to bring this as a topic in upcoming Yoga PTG.
https://etherpad.opendev.org/p/yoga-ptg-glance-planning