Steps to reproduce it:
- Startup master with a fresh database
Some upgrade processes run, for example:
And others that don't print traces such the one related to _configurationUpgradeStepFactory in RSSWebUpgrade are executed when it's not needed.
Those upgrade process are not executed.
For web modules, we need to specify the upgrade path for clean installations, that upgrade path has to run from 0.0.0 to the latest defined schema version, however we usually forget to update it. Just check the previous examples.
To solve it we should either:
- Review all web upgrade processes and create a SF rule to avoid future mistakes or
- Create a framework to avoid to have to update that upgrade path anytime (preferred)