[SOLVED] ]5.2.2 -> 5.2.3 upgrade: KeyError: 'plone.staticresources.upgrades:1006'

Plone Support
1

I have two identical Plone 5.2.2 setups. One of them can not be upgraded:

Traceback (innermost last):
  Module ZPublisher.WSGIPublisher, line 162, in transaction_pubevents
  Module ZPublisher.WSGIPublisher, line 371, in publish_module
  Module ZPublisher.WSGIPublisher, line 274, in publish
  Module ZPublisher.mapply, line 85, in mapply
  Module ZPublisher.WSGIPublisher, line 63, in call_object
  Module Products.CMFPlone.browser.admin, line 310, in __call__
  Module <string>, line 3, in upgrade
  Module AccessControl.requestmethod, line 88, in _curried
  Module Products.CMFPlone.MigrationTool, line 315, in upgrade
  Module Products.CMFPlone.MigrationTool, line 84, in upgrade_all
  Module Products.GenericSetup.tool, line 1164, in upgradeProfile
  Module Products.GenericSetup.upgrade, line 203, in doStep
  Module Products.GenericSetup.tool, line 400, in runAllImportStepsFromProfile
   - __traceback_info__: profile-plone.staticresources.upgrades:1006
  Module Products.GenericSetup.tool, line 1458, in _runImportStepsFromContext
  Module Products.GenericSetup.tool, line 1205, in _getImportContext
  Module Products.GenericSetup.registry, line 702, in getProfileInfo
KeyError: 'plone.staticresources.upgrades:1006'

Any idea?

2

That's strange. I could not see any profile name 1006 in plone.staticresources code. Do you see any invalid import steps in the "Manage" tab of portal_setup?

3

I see two upgrade steps:

  • CMFPlone 5209 -> 52010 (Plone 5.2.3)
  • CMFEditions 4 -> 4 (which makes no sense)
4

Oh, someone had the same issue already :clown_face: - but with 5.2.1 -> 5.2.2

5

The solution is as stated here: run the 5209 -> 5210 upgrade step in portal_setup manually and not through portal_migration

6

Ah ... this is where the wrong upgrade profile comes from Bugfix: Register upgrade step for the correct profile · plone/plone.patternslib@1968e51 · GitHub