Install fails on BOA/Drush/Aegir - No migration found with machine name PanopolyDemoNode

I haven't tried this with BOA (because I don't use it), but with plain Aegir you can just retry the install - it'll work the second time. :-)

I haven't been able to track down the root cause, but it has to do with Apps downloading the module. If the module is already present, then it'll find the migration just fine! Maybe we have to force Apps to clear the cache after downloading a new module or something like that?

I think it's because you're using the 2.x-dev version of Migrate:

https://github.com/lsolesen/panopolicious/blob/7.x-1.x/drupal-org.make#L153

Unfortunately, the demo code stuff only works with Migrate 2.5, not the 2.6 or the latest dev.

This isn't just related to BOA. This is a problem with drush site-install.
Not that I normally use drush si, but this is an annoying issue when trying to quickly spin up an instance of panopoly.

This occurs with both dev and stable versions of panopoly. I am using drush 6.2.0

@scresante: I agree, it is annoying. :-) However, the work around is really easy, which is why I haven't personally devoted more time to this issue.

What we do in the Travis-CI tests (which uses "drush si") is simply do "drush dl panopoly_demo" before attempting to install.

Like I said above:

I haven't been able to track down the root cause, but it has to do with Apps downloading the module. If the module is already present, then it'll find the migration just fine! Maybe we have to force Apps to clear the cache after downloading a new module or something like that?

If anyone has the time to dig into Apps and Migrate to figure out what's happening - that'd be much appreciated!

I can verify installing a new site with the panopoly profile using Aegir on a BOA installation will succeed if the panopoly_demo module is added to the distribution.

If it is not present then your first attempt will fail. Simply retry and it will succeed the second time because the first attempt will have downloaded it for you already.

I would think the panopoly distribution/profile could simply be pre-loaded with this module and then there would be no more of these failed first attempts. Although it is quite easy to copy/download the module into place before your first install.

BOA (head) adds panopoly_demo automatically to avoid this problem: https://github.com/omega8cc/boa/blob/master/aegir/scripts/AegirSetupC.sh...

I agree that panopoly_demo should be included by default. Otherwise it becomes an Apps Failure Demo :)

Thanks!

However, this is a bug with Migrate in Apps during drush install - I think the goal should be fixing that bug, not committing the work-around. If anyone has the time to find the root cause, that would be much appreciated. :-)

Just confirming dsnopek's find in #10/

Since we've updated both Apps (#2374727: update to apps beta20) and Migrate (#2412317: Update to Migrate 2.7), I came here to re-test if this problem is still happening. I found a new bug:

#2430921: Failing to download 'panopoly_demo' when installing via 'drush si': "Downloading updates failed:Failed to download from "

But after fixing that, everything appears to be working for me!

Could someone who had this problem in the past download the latest 7.x-1.x-dev release and see if the problem is fixed for you now?

In any case, the fact that we introduced this regression at all shows that we desperately need tests for this functionality, so I created a new issue for that:

#2430925: Test allowing Apps to pull in the panopoly_demo module when running via Drush

Thanks for everyone's patience with this issue! It sucks that it got introduced in the first place, and sorry it took so long to fix.

Heh, I just noticed that this was reported February 22, 2014 - so, we fixed it in less than 1 year, but by only a day. :-)

Nice! Thank you :)

I'm going to mark this as fixed. If anyone is still having this problem with the latest -dev, then please re-open!