github-actions[bot]
commented
1 month ago Hi there @bjarnef!
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'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
- If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
- We'll replicate the issue to ensure that the problem is as described.
- We'll decide whether the behavior is an issue or if the behavior is intended.
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:
bjarnef
Danielh21
Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)
12.0.0
Bug summary
On a Umbraco Cloud project we struggled a lot with timeout in migration from latest v10 to v12.0.0.
Initially it worked fine with a slim version of database, but after a restore of the live database locally, we had to increase connection timeout in connection string locally, but it succeeded.
However after deployment to Development (and later Live) environment, we could never get this to run successfully on Umbraco Cloud because the connection timeout before migration finished. https://github.com/umbraco/Umbraco-CMS/blob/v13/dev/src/Umbraco.Infrastructure/Migrations/Upgrade/UmbracoPlan.cs#L66-L89
I guess it was due the amount of content as there are a lot or course and category nodes.
However to solved this we had to deployment changes to Development, connect project on local to development with increased connection timeout, run migration and afterwards restart application.
We have to do the same for live environment.
Unfortunately there doesn't seen to be an option to increase connection timeout on Umbraco Cloud in this scenario and Azure has a harder limit than localhost.
I wonder if there is any option to trigger migration one at the time? or perhaps run one manually at the time on Umbraco Cloud as it sometimes seems to be an issue in projects on Umbraco Cloud with much content. But I guess it may also be an issue on traditional Azure.
Specifics
No response
Steps to reproduce
Run migration for a project with a lot on content on Umbraco Cloud (Azure) from latest v10 to v12.0.0 (or latest v12, but we used 12.0.0 to limit the number of migrations it needed to run).
Expected result / actual result
No response