I can confirm that this is still a problem on stable/newton. It has likely *always* been a problem on stable newton due to insufficient testing. The RuleProcessor object expects a mapping_id to be passed with the rules [0]. We are passing both of those values in all version except stable/newton [1].
Looks like a fix was merged in during the Ocata development cycle [2]. There is a backport up for review to stable/newton [3] that will fix the issue.
I'll propose a new stable/newton release as soon as it merged.
I can confirm that this is still a problem on stable/newton. It has likely *always* been a problem on stable newton due to insufficient testing. The RuleProcessor object expects a mapping_id to be passed with the rules [0]. We are passing both of those values in all version except stable/newton [1].
Looks like a fix was merged in during the Ocata development cycle [2]. There is a backport up for review to stable/newton [3] that will fix the issue.
I'll propose a new stable/newton release as soon as it merged.
[0] https:/ /github. com/openstack/ keystone/ blob/stable/ newton/ keystone/ federation/ utils.py# L415 /github. com/openstack/ keystone/ blob/stable/ newton/ keystone/ cmd/cli. py#L1143 /github. com/openstack/ keystone/ commit/ f2d0f8c9ab38172 a6e37b02339eac5 9da911435c /review. openstack. org/#/c/ 466873/ 1
[1] https:/
[2] https:/
[3] https:/