I confirmed the policy check for router operation works well as we expected.
When I did not get an expected result, I did the following: (1) start devstack with unmodified policy.json (2) edit /etc/quantum/policy.json (3) visit q-svc screen and restart quantum-server.
This time I did (1) edit /opt/stack/quantum/etc/policy.json (2) start devstack.
In devstack deployment both /opt/stack/quantum/etc/policy.json and /etc/quantum/policy.json exist and utils.find_config_file() finds /opt/stack/quantum/etc/policy.json first. This is the reason I could not get an expected. result.
Hi Salvatore,
I confirmed the policy check for router operation works well as we expected.
When I did not get an expected result, I did the following: (1) start devstack with unmodified policy.json (2) edit /etc/quantum/ policy. json (3) visit q-svc screen and restart quantum-server.
This time I did (1) edit /opt/stack/ quantum/ etc/policy. json (2) start devstack.
In devstack deployment both /opt/stack/ quantum/ etc/policy. json and /etc/quantum/ policy. json exist and utils.find_ config_ file() finds /opt/stack/ quantum/ etc/policy. json first. This is the reason I could not get an expected. result.