Edgewall Software
Modify

Opened 5 months ago

Last modified 7 weeks ago

#11370 new defect

Attachments not migrated on Trac upgrade

Reported by: rjollos Owned by:
Priority: normal Milestone: next-stable-1.0.x
Component: attachment Version:
Severity: normal Keywords: upgrade db28
Cc: cbidwell@…
Release Notes:
API Changes:

Description (last modified by rjollos)

We've had a number of reports that attachments are not migrated when upgrading Trac. I thought it was time to finally make a list of these and open a ticket for investigation:

It appears that the db28.py step is somehow failing.

Attachments (0)

Change History (9)

comment:1 Changed 5 months ago by rjollos

  • Description modified (diff)

comment:2 Changed 5 months ago by rjollos

  • Keywords db28 added

comment:3 follow-up: Changed 4 months ago by cbidwell@…

I'm having issues with this. I've upgraded to 1.0.1 but still can't get my attachments to migrate over. Am I missing something?

comment:4 in reply to: ↑ 3 Changed 4 months ago by rjollos

Replying to cbidwell@…:

I'm having issues with this. I've upgraded to 1.0.1 but still can't get my attachments to migrate over. Am I missing something?

You are not missing anything. We've seen the issue several times, but haven't diagnosed the cause. Could you provide more details to help us?:

  • Trac version upgrading from
  • Platform information

Is there anything in the trac.log file with regard to the failed upgrade step?

comment:5 Changed 4 months ago by rjollos

  • Cc cbidwell@… added

comment:6 Changed 4 months ago by cbidwell@…

Sure. I upgraded from 0.12.2 → 1.0. Then from 1.0 → 1.0.1 using easy_install for both. Running on RHEL 6.5 x86_64. I did not see anything relevant in trac.log.

comment:7 Changed 4 months ago by cbidwell@…

Is there a way to run db28.py manually to get this to work?

comment:8 Changed 4 months ago by rjollos

Is there a files directory in the environment directory? Do you still have the console output available so that you could check for messages starting with Unable to move attachment? It looks like the messages may be printed but not logged: tags/trac-1.0.1/trac/upgrades/db28.py@:87-89#L75.

The other possibility that Jun mentioned in th:#11151 is that the step is being skipped entirely due to the early return: tags/trac-1.0.1/trac/upgrades/db28.py@:26. We could at least log something there to try and narrow down the problem.

See th:comment:2:ticket:11151 for information on running the upgrade step manually.

comment:9 Changed 7 weeks ago by rjollos

Someone added a nice FAQ entry for this issue. Thanks anonymous! :)

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as new The ticket will remain with no owner.
as The resolution will be set. Next status will be 'closed'.
The owner will be changed from (none) to anonymous. Next status will be 'assigned'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.