The bug hasn't been fixed completely. Indeed, the error message now makes sense for column-name-references on known policy tables, but the old message shows up for something that's not known to be either a policy table or a datasource table.
$ openstack congress policy rule create classification 'a :- w(id=y)'
Syntax error for rule::Literal w(id=y) uses column references, but 'classification' does not reference a datasource policy (HTTP 400) (Request-ID: req-30b0f225-0dfe-428a-967d-27ab9a2ff722)
[correct]
$ openstack congress policy rule create classification 'a :- action:w(id=y)'
Syntax error for rule::Literal action:w(id=y) uses column references, but 'action' does not reference a datasource policy (HTTP 400) (Request-ID: req-b34ef4c2-4710-4263-8ba4-832a38a43716)
[correct]
$ openstack congress policy rule create classification 'a :- blah:w(id=y)'
Rule already exists::(1008) Rule already exists (HTTP 409) (Request-ID: req-f5b5f25a-40cc-4278-ad7b-cc49d9a72779)
[misleading, old message]
The bug hasn't been fixed completely. Indeed, the error message now makes sense for column- name-references on known policy tables, but the old message shows up for something that's not known to be either a policy table or a datasource table.
$ openstack congress policy rule create classification 'a :- w(id=y)' 0dfe-428a- 967d-27ab9a2ff7 22)
Syntax error for rule::Literal w(id=y) uses column references, but 'classification' does not reference a datasource policy (HTTP 400) (Request-ID: req-30b0f225-
[correct]
$ openstack congress policy rule create classification 'a :- action:w(id=y)' 4710-4263- 8ba4-832a38a437 16)
Syntax error for rule::Literal action:w(id=y) uses column references, but 'action' does not reference a datasource policy (HTTP 400) (Request-ID: req-b34ef4c2-
[correct]
$ openstack congress policy rule create classification 'a :- blah:w(id=y)' 40cc-4278- ad7b-cc49d9a727 79)
Rule already exists::(1008) Rule already exists (HTTP 409) (Request-ID: req-f5b5f25a-
[misleading, old message]