Ticket #11611 (confirmed Bug)
upgrade from 3.3.5 to 4.0.4/4.0.7 fails on unrestrictedTraverse
Reported by: | mhammill | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 4.x |
Component: | Upgrade/Migration | Version: | 4.0 |
Keywords: | Cc: |
Description
Dry run migration to Plone 4.0.4 from Plone 3.3.5 on our site (which has been running Plone since 2.5.0 days) gives the attached traceback and fails migration. I originally thought the problem was the "TextIndex" problem described on http://plone.293351.n2.nabble.com/Upgrade-from-3-2-2-to-4-0-2-fails-td5993451.html but changing Title and Description indices to ZCTextIndex did not clear up the problem. Preparations to the 3.3.5 site before attempting migration, in addition to the ZCTextIndex change mentioned, were: (1) export from 3.3.5 to clean 3.3.5; (2) clear and rebuild catalog after ZCTextIndex. I got similar errors when I previously tried migration to 4.0.0, and 4.0.3.
Attachments: traceback, system info
Attachments
Change History
Changed 5 years ago by mhammill
-
attachment
plone4_migration_report_failure.txt
added
Changed 5 years ago by mhammill
-
attachment
plone4_migration_sysinfo.txt
added
A little additional systems info
comment:1 Changed 5 years ago by mhammill
- Summary changed from upgrade from 3.3.5 to 4.0.4 fails on unrestrictedTraverse to upgrade from 3.3.5 to 4.0.4/4.0.7 fails on unrestrictedTraverse
I am updating the summary to reflect the fact that we are *still* are blocked from upgrading from 3.3.5 to 4.0.x. Same error. The instance being upgraded contains 5 plone sites. 2 of the 5 upgrade to 4.0.7 without any problem. For the 3 that fail, the name of a user account is always listed (e.g., in the above "edlund" is a user on the system). In each of the 3, it is a different user listed. I did not find anything odd about these three users, or their Members/username directories. I would be great to get some feedback on this bug. Three months is starting to feel like a rather long time.
Dry run migration report traceback