wangxiyuan, I have reproduced this issue with user as admin in proj1. If we look at lines [0], [1] same 'filters' object is being used at both places and this 'filters' object is updated on call from [0] to [2] by deleting 'all_tenants' entry from it. So when a call is made from [1] to [3] in the next flow, it doesn't have 'all_tenants' in filters even though user is admin then execution goes to else block at [4].
wangxiyuan, I have reproduced this issue with user as admin in proj1. If we look at lines [0], [1] same 'filters' object is being used at both places and this 'filters' object is updated on call from [0] to [2] by deleting 'all_tenants' entry from it. So when a call is made from [1] to [3] in the next flow, it doesn't have 'all_tenants' in filters even though user is admin then execution goes to else block at [4].
[0] https:/ /github. com/openstack/ cinder/ blob/master/ cinder/ api/contrib/ consistencygrou ps.py#L138 /github. com/openstack/ cinder/ blob/master/ cinder/ api/contrib/ consistencygrou ps.py#L142
[1] https:/
[2] https:/ /github. com/openstack/ cinder/ blob/master/ cinder/ consistencygrou p/api.py# L711 /github. com/openstack/ cinder/ blob/master/ cinder/ group/api. py#L760 /github. com/openstack/ cinder/ blob/master/ cinder/ group/api. py#L774
[3] https:/
[4] https:/