Continuing my investigation: 1) I used an "older" installation of Congress on OpenStack. The oslo.messaging version is 4.6.2.dev9, whereas the version on my brand new DevStack installation is 5.10.0. I ran the same CLI policy commands and no traceback was returned. 2) With a new devstack installation and the latest Congress code, confirmed that API and CLI calls to datasource and schema do not return traceback when invalid IDs are passed. "datasource" appears to be the only one of the three displaying user-friendly error information as expected. 3) The error/not found handling bug seems to be across all the Policy CLI and API calls. I put more info and examples into the Launchpad bug entry: https://bugs.launchpad.net/congress/+bug/1620868 (This is a bug where I would really love to be able to remotely debug using PyCharm instead of the pdb command line debugger.) I don't know oslo.messaging or the Congress code base well enough to know exactly why the Policy error response is different from datasource and schema. I will continue to dig through the code and hopefully find a solution. aimee On Sun, Sep 11, 2016 at 2:30 PM, Tim Hinrichs <tim at styra.com> wrote: > The Api node on Oslo-messaging sends a request to the policy node asking for > say policy alpha. The policy node raises an exception, which Oslo returns to > the API node. I'd imagine there is some way to have the Ali node extract the > original exception or tell Oslo to return the only the original exception. > > Tim > On Thu, Sep 8, 2016 at 2:04 PM Aimee Ukasick <aimeeu.opensource at gmail.com> > wrote: >> >> All -- >> >> https://bugs.launchpad.net/congress/+bug/1620868 >> >> I stepped through the code with the pdb. I can't find anything wrong >> in the CongressException >> code. >> >> The traceback is being added by oslo_messaging/rpc/server.py in >> _process_incoming >> This call that is throwing an exception: res = >> self.dispatcher.dispatch(message) but I haven't >> determined why. >> >> https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/rpc/server.py#L134 >> >> https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/rpc/server.py#L142 >> >> console output here: http://paste.openstack.org/show/569334/ >> >> >> I can't figure out why oslo.messaging is throwing an exception, I >> assume I should go into the API and CLI cod and prevent the traceback >> from being displayed. >> >> Thoughts? Suggestions? Epiphanies? >> >> aimee >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: OpenStack-dev-request at 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-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >