Going from 2.0.9 to 2.1.1 does not update platforms [#2134329]

I've installed BOA-2.0.9 headand then upgraded directly to 2.1.1 with barracuda up-head which went fine through all options (I've made full install with all additional options, Zend OpCache, nginx, SPDY, Percona /which didn't install for wheezy - why?/) on Debian Wheezy VPS 1GB/1CPU on DigitalOcean.

While next step should be octopus up-head all it didn't work, just said This Aegir Instance is already up to date!

So I issued octopus up-head o1 platforms and then got platforms upgraded.

Was I supposed to go over 2.1.0 first to get everything in order? I think it should detect better if platform upgrade is needed?

Comments

Comment #1

omega8cc CreditAttribution: omega8cc commented 13 November 2013 at 12:52

Thanks for the report. I guess it is a bug, because we have replaced internal control file with file stat check to deny serial Octopus upgrades on the same day, which could create duplicate platforms nodes etc, but we have made that check too aggressive with 30 days instead of 1 day as a minimum required, which can be overridden by specifying the upgrade mode with aegir|platforms|both explicitly.

Comment #2

omega8cc CreditAttribution: omega8cc commented 13 November 2013 at 13:01

Project:	Barracuda	» Octopus
Version:	6.x-2.x-dev	» 6.x-2.0-rc11
Component:	Aegir Master Instance	» Code
Status:	Active	» Fixed

Fixed in http://drupalcode.org/project/octopus.git/commit/61b8f78

Note that you should have run octopus up-stable all both and otherwise octopus up-stable. There is no head at the moment available.

For Barracuda specific problems please open separate issue with all required install logs attached.

Comment #3

MacMladen CreditAttribution: MacMladen commented 14 November 2013 at 08:31

Thank for the fix, it apparently work for me anyway.

But this remark

you should have run octopus up-stable all both and otherwise octopus up-stable. There is no head at the moment available.

left me a bit confused: if there are no-head available, should the script warn and stop? Or offer to continue but under stable? (maybe state potential risk?)

Somewhere you did note that head is also stable and can be used without a problem. I made quite a few test installs and found head working with more recent versions so I went with that.

I did not like using 7.24-dev version on sites (it is reporting errors always in status about version) and was more glad to find that new versions are 7.23

Aegir is a universe complexity by itself and BOA just adds a galaxy or two to that complexity and you are making wonderful job for small web shops like mine and thank you a bunch. Sometimes it is very hard for me to understand how/why are you doing it for free but then I figure out that rarely will someone be able to use that to jeopardize your business and if someone is skilled enough, then one can do it without BOA anyway.

As I am (trying to be) a frequent speaker on Drupal events in region, as I learn enough, I will preach using BOA and Aegir to community. Even more, I will organize a workshop for using BOA in both production and local dev (virtual box) to have easier experimenting with distributions and code, even more so, I am finding that BOA may work even for one site or small shop.

For that purpose, my own business is my guinea pig :D

Comment #4

omega8cc CreditAttribution: omega8cc commented 14 November 2013 at 10:37

Thank you for your kind words!

As for the recommended version to use, you should always use stable if it has been just released, because we often delay reverting the HEAD to actual HEAD mode, so even when you run up-head, it runs up-stable effectively, until there is a commit saying "Back to HEAD".

As for why we are doing it for free etc, it is explained on our website at: https://omega8.cc/options -- we believe that for its target audience BOA is something which can only get better with each release if it is widely used, without any restrictions. It is also a great way to give back to the community.

Please let us know @omega8cc on Twitter when you will give some presentation! Thanks!

Comment #5

MacMladen CreditAttribution: MacMladen commented 14 November 2013 at 11:35

And I wholeheartedly agree with that! Actually, feedback from community is of a higher quality than from clients as we can help in educated way, not only to seek help on issues or shout in anger ;)

I still have a lot to learn but this is the path I decided to take with my own business as server build seems rock solid and all my research ended up as being lower than offered by BOA. The main idea with Drupal (and BOA and FOSS) is not to reinvent the wheel but to channel energy into progress and I support that.

I love teaching and lecturing, already done one workshop on Drupal Commerce, preparing one on local development and organizing one on SASS. Aegir would be included in local development as a little case study and then I will try to make a workshop ('build high performance, security server and deployment factory in a day!') that will hopefully turn into something worth presenting to wider audience. Maybe buys me a ticket to some conference and a beer too ;)