Ticket view error

[pleshkov@…]

For example: ​http://svn.flylinkdc.ru/trac/ticket/293

Trac detected an internal error: Python Traceback

Traceback (most recent call last):
  File "/usr/local/lib/python2.5/site-packages/trac/web/main.py", line 406, in dispatch_request
    dispatcher.dispatch(req)
  File "/usr/local/lib/python2.5/site-packages/trac/web/main.py", line 237, in dispatch
    resp = chosen_handler.process_request(req)
  File "/usr/local/lib/python2.5/site-packages/trac/ticket/web_ui.py", line 313, in process_request
    get_reporter_id(req, 'author'))
  File "/usr/local/lib/python2.5/site-packages/trac/ticket/web_ui.py", line 669, in _insert_ticket_data
    actions = TicketSystem(self.env).get_available_actions(ticket, req.perm)
  File "/usr/local/lib/python2.5/site-packages/trac/ticket/api.py", line 83, in get_available_actions
    return [action for action in actions.get(ticket['status'], ['leave'])
  File "/usr/local/lib/python2.5/site-packages/trac/ticket/model.py", line 104, in __getitem__
    return self.values[name]
KeyError: 'status'

How I can fix this problem?

[Emmanuel Blot]

A ticket without a status: it looks like your Trac DB is in trouble.

Can you execute the following command: open a shell window and use the 'sqlite3' tool to dump the ticket information:

cd trac_project_path/db
sqlite3 trac.db
select * from ticket where id=293;
.quit

[pleshkov@…]

I use MySQL database for store data:

mysql> select * from ticket where id=293;
+-----+-------------+------------+------------+-------------+----------+----------+-------+---------------------+------+---------+----------
-----------------+--------+------------+---------+------------------------------------------------------------------------------------------
-------+----------+
| id  | type        | time       | changetime | component   | severity | priority | owner | reporter            | cc   | version | milestone
                 | status | resolution | summary | description
       | keywords |
+-----+-------------+------------+------------+-------------+----------+----------+-------+---------------------+------+---------+----------
-----------------+--------+------------+---------+------------------------------------------------------------------------------------------
-------+----------+
| 293 | ??????????? | 1199489654 | 1199489654 | FlyLinkDC++ | NULL     | ???????  | ppa   | panto_975@pochta.ru |      | ?????   | ????????
????? ?????????? | NULL   | NULL       | ??????  | ??? ??????? ?? ?????? ??????????? ?????? ? ?????????? ? ?????? ??????? ???? ?? ??????? ??
?????? |          |
+-----+-------------+------------+------------+-------------+----------+----------+-------+---------------------+------+---------+----------
-----------------+--------+------------+---------+------------------------------------------------------------------------------------------
-------+----------+
1 row in set (0.01 sec)
mysql> select status from ticket where id=293;
+--------+
| status |
+--------+
| NULL   |
+--------+

[osimons]

Do a select for;

select id, status from ticket where status is NULL or status = '';

Status should never be empty - a ticket always has a state. It starts as 'new' and ends as 'closed', with varying states inbetween.

Do you see a pattern in the invalid tickets? Any hint of what has happed to your Trac that may have caused this? Have you migrated data? Installed plugins? Anything?

To fix the tickets, I suggest you just update your ticket table, and set status to new for all tickets that does not have a resolution, and all tickets to closed that has a resolution. Do selects to make sure the subsets make sense, and: Backup :-)

Please report back with any findings on what may have caused this. If no more information is provided, there realistically is not much more to be done for this issue from a Trac point-of-view.

[pleshkov@…]

I'm upgrade my trac to Trac 0.11b1 and problem has gone away :) thx.

[osimons]

Reopen to change resolution.

[osimons]

And closing with new resolution.