Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
It is no longer possible to even install Aegir system. It fails with:
Command provision-install needs a higher bootstrap level to run - you will need invoke drush from a more [error]
functional Drupal environment to run this command. [2.54 sec, 5.09 MB]
The drush command 'provision-install' could not be executed. [2.54 sec, 5.09 MB] [error]
A Drupal installation directory could not be found [2.54 sec, 5.09 MB] [error]
The last working without issues version is Drush 4.0-rc5.
All tests were performed using Aegir HEAD/master code.
Comment | File | Size | Author |
---|---|---|---|
#11 | 2ef2baad850d0754581f97289cbfc44371bc4437.patch.txt | 1.07 KB | omega8cc |
#7 | provision_drush_cli_context.patch | 1.07 KB | mig5 |
Comments
Comment #1
omega8cc CreditAttribution: omega8cc commentedAnd here is the full debug output:
Comment #2
omega8cc CreditAttribution: omega8cc commentedThe weird thing is also: it creates
hostmaster
andplatform_hostmaster
directories in/var/aegir/config
, while there should be never such directories there. It means that provision has lost its context completely and is looking in a completely wrong places now.Comment #3
greg.1.anderson CreditAttribution: greg.1.anderson commentedDoes Aegir reference the 'options' context directly, either in the hostmaster / provision commands, or via the backend results record? I'm guessing that the answer is 'yes', and your problem was caused by #1011074: Rename 'options' context to 'cli', which was committed in rc6.
Comment #4
Anonymous (not verified) CreditAttribution: Anonymous commentedWe have two references to fetching the 'options' context in Provision:
Should these be changed to drush_get_context('cli') ?
Comment #5
greg.1.anderson CreditAttribution: greg.1.anderson commentedYes, change 'options' to 'cli'.
Comment #6
greg.1.anderson CreditAttribution: greg.1.anderson commentedFor compatibility with drush-3 and drush-4:
Comment #7
Anonymous (not verified) CreditAttribution: Anonymous commentedThanks for the confirmation,
Grace, here's a patch, I just tested Aegir HEAD and it works again with this.
Perhaps we will do a new release of Aegir to coincide with Drush 4.0 that has this patch, since I imagine a few people will want to use the newer Drush on their Aegir systems when it comes out (we hardcode the Drush version in our installer script deliberately to avoid these sorts of surprises on Aegir, same as we do with Drush_Make :) )
I'm also moving this to Provision since it is not Drush's bug.
Comment #8
Anonymous (not verified) CreditAttribution: Anonymous commentedOoh I missed #6, good point, I could commit this then.
Thanks
Comment #9
Anonymous (not verified) CreditAttribution: Anonymous commentedGrace,
This is in provision HEAD now.
Comment #10
omega8cc CreditAttribution: omega8cc commentedOh, thank you Miguel!
Comment #11
omega8cc CreditAttribution: omega8cc commentedThe patch you applied has been truncated and this fix is required: http://gitorious.org/aegir/provision/commit/2ef2baad850d0754581f97289cbf...
Comment #12
Anonymous (not verified) CreditAttribution: Anonymous commentedCrap, thanks, I did something absurd there. reverted and reapplied.