Trac stuck in "environment needs to be upgraded" since deleting a T&E report

[ben3@…]

Trac Error:

Trac Error

TracError: The Trac Environment needs to be upgraded.

Run "trac-admin /srv/trac/project upgrade"

Log message:

2008-12-01 10:03:57,860 Trac[loader] DEBUG: Loading roadmaphours from 
/usr/lib/python2.4/site-packages/RoadmapHours-0.5-py2.4.egg
--snip--
2008-12-01 10:03:57,900 Trac[api] DEBUG: T&E needs upgrades for the following 
reports: Set([('040c9025-7641-4d18-96ad-2b26b4095566', 16)])
2008-12-01 10:03:57,905 Trac[api] DEBUG: NEEDS UP?: sys:False, rep:True, stats:False, 
fields:False, man:False
2008-12-01 10:03:57,910 Trac[api] DEBUG: T&E needs upgrades for the following 
reports: Set([('040c9025-7641-4d18-96ad-2b26b4095566', 16)])
2008-12-01 10:03:57,910 Trac[env] WARNING: Component 
<timingandestimationplugin.api.TimeTrackingSetupParticipant object at 0x2b0e146f5410> 
requires environment upgrade

I'm not sure what's caused it, but I seem to remember deleting a report by accident a few days ago. Not sure why it'll have broken this severely though?

Disabling the plugin and all of its components fixes the problem

I'm running Trac 0.11 on CentOS 5.2, with Python 2.4.

[ben3@…]

Just to add, I've run the upgrade command but had no success

[ben3@…]

Enabling all components except TimeTrackingSetupParticipant fixes things

[Russ Tyndall]

Ughh... The setup code has consistently proven to be the most difficult to get correct.

Probably the easiest way to get your environment back to working normally is to go delete the row with uuid:040c9025-7641-4d18-96ad-2b26b4095566 from the custom_report table.

My guess is that when the report was deleted it was not removed from the custom report table so the program is essentially finding the report half installed.

I may at somepoint try to tackle the bugs in the setup script that are causing this problem, but for now, you should at least be able to get it upgraded so that the setupparticipant will not complain constantly.

OTOH you wont really need the setup participant until you upgrade and you could just fix the problem then.

HTH, Russ

[Thomas Wagner]

I can confirm this bug after deleting a report. Running the upgrade it says the report is already newer.

MfG Watho

[Russ Tyndall]

A few people are having this problem, but unfortunately I am very busy at work at the moment, and so will not be able to fix this for a week or two more. I would suggest using the above fix (disabling the SetupParticipant) until I can get it fixed.

[koen]

any progress on this one ? Two different trac environments here suffer from this behaviour. At first, running the upgrade seemed to work or at least trac recovered after a few refreshes. But this time, it seems to have given up completely.

thx for the effort;

[fatorres2004@…]

Hi.. I resolved this problem by this way: 1) Connect to trac.db (sqliteadmin) 2) Open report Table 3) view column Id and insert id row lost (in my case row with Id = 12) 4) upgrade trac env (trac-admin ... upgrade)

Report for T&E (csv format) id,author,title,query,description 10,Timing and Estimation Plugin,Ticket Work Summary_{Reports Must Be Accessed From the Management Screen 11,Timing and Estimation Plugin,Milestone Work Summary}Reports Must Be Accessed From the Management Screen 12,Timing and Estimation Plugin,Developer Work Summary_{Reports Must Be Accessed From the Management Screen 13,Timing and Estimation Plugin,Ticket Hours}Reports Must Be Accessed From the Management Screen 14,Timing and Estimation Plugin,Ticket Hours with Description_{Reports Must Be Accessed From the Management Screen 15,Timing and Estimation Plugin,Ticket Hours Grouped By Component}Reports Must Be Accessed From the Management Screen 16,Timing and Estimation Plugin,Ticket Hours Grouped By Component with Description_{Reports Must Be Accessed From the Management Screen 17,Timing and Estimation Plugin,Ticket Hours Grouped By Milestone}Reports Must Be Accessed From the Management Screen 18,Timing and Estimation Plugin,Ticket Hours Grouped By MileStone with Description_{Reports Must Be Accessed From the Management Screen}

[Russ Tyndall]

(In [5491]) fixes #4184 Reworked the report upgrade code to allow deletion of reports. If the report version is updated the report is reinstalled.

[Russ Tyndall]

If you continue to experience these problems after a reinstall of the new version, please reopen the ticket with some log messages to help me track down the problem.

I will be porting these changes to the permissions branch shortly.

[Russ Tyndall]

(In [5493]) re #4184 ported changes to permissions branch and fixed a missing function ref in reportmanager