Open piotrbach opened 5 days ago
Hi there @piotrbach!
Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.
We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.
We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.
Thanks, from your friendly Umbraco GitHub bot :robot: :slightly_smiling_face:
It's worth to mention that we haven't noticed such an issue in the v13.4.1, so this is probably a fresh bug.
Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)
13.5.0
Bug summary
After updating the system from 11.5.0 to 13.5.0, the last migration consistently starts when Umbraco is launched.
This behavior could have serious consequences.
We did not observe this issue in version 11.5.0, where migrations were created.
The problem is evident in the system logs of Umbraco 13.5.0:
[10:08:04 INF] Acquiring MainDom. [10:08:04 INF] Acquired MainDom. [10:08:05 INF] Starting 'DefaultDatabaseMigrationPlan'... [10:08:05 INF] At AddContentTypeIdColumnUmbracoSynchronizedMfCsEntityTableMigration-state [10:08:05 INF] Done [10:08:05 INF] The NuCache IgnoreLocalDb setting is set to 'False' by appsettings.json.
cc: @wtct
Specifics
The migration runs even though the migration was completed more than a year ago, as can be seen in the screenshot from dbo.umbracoKeyValue table:
Below is the code that initializes the migration:
Steps to reproduce
Expected result / actual result
Migrations should be executed only once.