Hi Su, Try using 'action' instead of 'null'. 'action' is a built-in policy. It's possible that seemingly insignificant changes made the API call more strict and now force the policy you provide to actually exist. Let me know if that doesn't work, and I'll investigate further.
Tim On Tue, Aug 25, 2015 at 5:18 PM Su Zhang <westlif...@gmail.com> wrote: > Hello, > > In simulation examples at > http://congress.readthedocs.org/en/latest/enforcement.html?highlight=simulation > , > the "action_policy" is replaced with "null". However, "null" is not > considered as a valid policy as I keep receiving 400 errors. > Could someone let me know the easiest way to get around this error? > How to create a simple action policy just for test purpose as of now? > > Thanks, > > -- > Su Zhang > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
