Kirill,
it is issue of each separate project, not library. Library does everything correctly.
Each project should start storing "domain_id" in DB models as it is done with "project_id" and "user_id".
Only then, it will be possible to use it with "oslo.policy" library.
So, for everyone, it is not "spam", each of assigned projects DOES have bug, that is "not complete support of keystone API v3".
And before marking it as "not affecting" need to verify it first. Steps for reproducing are defined in buyg report.
Kirill,
it is issue of each separate project, not library. Library does everything correctly.
Each project should start storing "domain_id" in DB models as it is done with "project_id" and "user_id".
Only then, it will be possible to use it with "oslo.policy" library.
So, for everyone, it is not "spam", each of assigned projects DOES have bug, that is "not complete support of keystone API v3".
And before marking it as "not affecting" need to verify it first. Steps for reproducing are defined in buyg report.