--trace option causes Internal Server Error

[Tim Hinrichs]

When asking for a row listing, the --trace option throws a 500.

styra@ubuntu:~/devstack$ ocp rule list alice
// ID: be6a17d7-5b66-4edf-a984-b776acdf6edf
// Name: None
p(x) :- nova:hosts(host_name=x)

styra@ubuntu:~/devstack$ ocp row list alice p
+--------+
| Col0 |
+--------+
| ubuntu |
+--------+
styra@ubuntu:~/devstack$ ocp row list alice p --trace
Internal server error (HTTP 500) (Request-ID: req-0e636f76-278b-4920-948a-e894a66b5053)

[Tim Hinrichs (thinrichs)]

Interestingly, the --trace option works fine with the simulate command.

[Tim Hinrichs (thinrichs)]

Log error was ...

2016-03-17 09:49:43.724 ERROR congress.api.application [req-7135aef3-2fa9-4388-8dd9-67b125e68130 admin 71ac0e21b68243e68323f3f0d340face] Traceback (most recent call last):
  File "/opt/stack/congress/congress/api/application.py", line 51, in __call__
    response = handler.handle_request(request)
  File "/opt/stack/congress/congress/api/webservice.py", line 404, in handle_request
    return self.list_members(request)
  File "/opt/stack/congress/congress/api/webservice.py", line 430, in list_members
    context=self._get_context(request))
  File "/opt/stack/congress/congress/api/row_model.py", line 93, in get_items
    result[0] = [{'data': tuple(x['data'])} for x in result[0]]
TypeError: 'tuple' object does not support item assignment

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/294190

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/294190
Committed: https://git.openstack.org/cgit/openstack/congress/commit/?id=7c2f4132b9693e7969e704cb9914963274c2c4a1
Submitter: Jenkins
Branch: master

commit 7c2f4132b9693e7969e704cb9914963274c2c4a1
Author: Madhu Mohan Nelemane <email address hidden>
Date: Thu Mar 17 18:21:25 2016 +0100

    Fix for tuple assignment causing 500 Error

    Change-Id: Ia58641970b85033759cf27a7aa6eb4bf4a75fa6e
    Closes-Bug: #1558662

[Thierry Carrez (ttx)]

This issue was fixed in the openstack/congress 3.0.0.0rc1 release candidate.