Migration to 10.2 gets stuck in infinite loop

[fotiDim]

Trying to migrate a site from a 10.1 platform to 10.2. Migration never ends but also doesn't throw an error. The log becomes longer as time passes and seems it repeats itself. Notice how many times Loading drushrc "/data/disk/o1/static/10.2.5b/web/sites/all/drush/drushrc.php" into "drupal" scope. is printed. I tried waiting for it for 30 minutes. It just never ends. This has been happening with BOA 5.1 and 5.2 lite. logs.txt

[omega8cc]

Have you run successful Octopus upgrade after Barracuda upgrade?

_{Sent with GitHawk}

[omega8cc]

Please don’t flood the issue with logs. Any logs should be attached.

_{Sent with GitHawk}

[fotiDim]

I did octopus up-lite all force, reboot, let all platforms verify, and tried the migration again. It then worked. Thank you.

I have spent countless hours trying to troubleshoot this... 😖 Every when are we supposed to run octopus up-lite all force? Is that documented somewhere or could it be automated?

[omega8cc]

It’s documented very clearly in detail..

https://github.com/omega8cc/boa/blob/7e6f15bab9b3093e63c8af9bd2788f5794374a2e/docs/UPGRADE.txt#L138

As you can see you also have to run barracuda full upgrade (not just system) when new release is available.

We haven’t added command to run chained upgrades for both barracuda and octopus but perhaps we should make it chained by default?

_{Sent with GitHawk}

[fotiDim]

I have followed the instructions of Automatic BOA System Major Upgrade Tool. I assumed that Important Notes for Standard/Manual BOA Upgrade was only needed for manual upgrades. Regardless of that, site upgrades from Drupal 9 to 10.1 worked fine, therefore I didn't expect 10.2 to fail because I missed running the octopus upgrade command.

Yes, chaining it would be best. Or maybe there should be a parent command that runs both.

Some general feedback regarding the documentation... While extensive, it still makes it easy to miss important information. What I suggest:

• Format it as markdown so that we get proper rich text when viewing it on Github
• Have indexes which link to all the sections
• Link to the important bits from the main repo readme

[omega8cc]

The automatic tool is only for major system upgrades and not for BOA upgrades..

It’s already on the list: https://github.com/omega8cc/boa/blob/7e6f15bab9b3093e63c8af9bd2788f5794374a2e/ROADMAP.txt#L34

_{Sent with GitHawk}