Command site-install needs a higher bootstrap level to run - you will need to invoke drush from a more functional Drupal environment to run this command. #132

haynescw · 2016-06-08T18:40:57Z

When using the most recent version of blt and drupal vm, i get to the point where i am running ./blt.sh local:setup. during this process it errors but doenst give a good error msg so i ran the command manually to see what was happening, the result was "Command site-install needs a higher bootstrap level to run - you will need to invoke drush from a more functional Drupal environment to run this command." I think this command is being ran form the roject root when it should be ran from the docroot of th drupal site.

grasmash · 2016-06-08T20:28:29Z

Running the same command manually may give you a different result because running a target via blt.sh may actually execute the command in a different directory than your current working directory. What command did you run? What was the initial error? If it's a drush command, you likely need to execute it from the docroot. Otherwise drush can't find Drupal.

haynescw · 2016-06-08T20:36:57Z

Its it the drush install site command. Im running it again to get the error output from that for you.

haynescw · 2016-06-08T21:03:10Z

project > setup:drupal:install:

[drush] Executing '/Users/XXXXX/Documents/Clients/XXXXXX/dev/blted8/vendor/bin/drush @blted8.local --site-name="BLTed 8" --site-mail="no-reply@acquia.com" --account-name="admin" --account-pass="admin" --account-mail="no-reply@acquia.com" --l="default" --nocolor --yes --verbose site-install "lightning" "install_configure_form.update_status_module='array(FALSE,FALSE)'"'...

Loaded alias @blted8.local from file /Users/XXXXX/Documents/Clients/XXXXXX/dev/blted8/drush/site-aliases/drupal-vm.aliases.drushrc.php [notice]
Begin redispatch via drush_invoke_process(). [notice]
Calling proc_open(ssh -o PasswordAuthentication=no -i /Users/XXXXX/.vagrant.d/insecure_private_key vagrant@blted8.localhost 'env COLUMNS=272 drush --local --alias-path=/Users/XXXXX/Documents/Clients/XXXXXX/dev/blted8/drush/site-aliases --nocolor --yes --verbose --uri=default --root=/var/www/blted8/docroot site-install lightning '''install_configure_form.update_status_module='''''''''array(FALSE,FALSE)'''''''''''' --site-name='''BLTed 8''' --site-mail='''no-reply@acquia.com''' --account-name=admin --account-pass=admin --account-mail='''no-reply@acquia.com''' 2>&1' 2>&1);
End redispatch via drush_invoke_process(). [notice]
[drush] [error] Command site-install needs a higher bootstrap level to run - you will need to invoke drush from a more functional Drupal environment to run this command.
[drush] [error] The drush command 'site-install lightning install_configure_form.update_status_module='array(FALSE,FALSE)'' could not be executed.
[phingcall] /Users/XXXXX/Documents/Clients/XXXXXX/dev/blted8/build/core/phing/tasks/setup.xml:73:85: Drush exited with code 1

BUILD FAILED
/Users/XXXXX/Documents/Clients/XXXXXX/dev/blted8/build/core/phing/tasks/local-sync.xml:12:30: Execution of the target buildfile failed. Aborting.

Total time: 42.5293 seconds

CashWilliams · 2016-06-08T21:24:15Z

Are you running this from the host or from inside the VM?

I have a feeling this is an issue with the drush alias files, as they are not fully ironed out for the VM workflow.

haynescw · 2016-06-08T23:08:24Z

I am running this from my mac not drupal vm.

grasmash · 2016-06-09T00:38:03Z

Dumb question, but is the VM running? If you run drush @blted8.local ssh can you login to it?

haynescw · 2016-06-09T00:45:08Z

An error 1 occurred while running the command `ssh -o PasswordAuthentication=no -i /Users/XXXXX/.vagrant.d/insecure_private_key -t vagrant@blted8.localhost 'cd /var/www/blted8/docroot && bash [error]
-l'

haynescw · 2016-06-09T00:53:09Z

I found the generate config file is wrong, in the section

Provide the path to the project root to Vagrant.

vagrant_synced_folders:

Set the local_path for the first synced folder to `../`.

local_path: .
Set the destination to the Acquia Cloud subscription machine name.
destination: /var/www/blted8
type: nfs

local path needs to be set to ../

haynescw · 2016-06-09T01:02:20Z

after updating that line, i can ssh with the drush command like you wanted

haynescw · 2016-06-09T01:05:09Z

Nice, that . to a ../ fixed my issue and it completed the setup task. Thanks @grasmash for thinking of logging in with drush. Really made the difference.

haynescw · 2016-06-09T01:05:21Z

Dont forget to update that line

grasmash · 2016-06-09T01:22:34Z

Hm. I've just run the vagrant up command with it set to . and it worked. Changing to ../ causes the same error for me that you described. Strange. I assume that you used blt vm:init to do the initial configuration?

haynescw · 2016-06-09T03:02:27Z

Yes, I started my entire build from scratch and used all the new changes to the Readme's, which included blt vm:init

grasmash · 2016-06-09T14:02:20Z

My best guess is that you may have an older version of Vagrant. I've found the default config to work on Vagrant 1.8.1, vagrant -v.

haynescw · 2016-06-09T15:55:52Z

This was resolved by one of your commits, when i ran the command again,
after starting all over, fresh pull on everything, and changing my nfs
share to ../ ended up with everything working. If that makes sense.

On Thu, Jun 9, 2016 at 9:02 AM, Matthew Grasmick notifications@github.com
wrote:

My best guess is that you may have an older version of Vagrant. I've found
the default config to work on Vagrant 1.8.1, vagrant -v.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
#132 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/ADeNGa7308x-O5mVe0pej8xSKsVX_RKDks5qKBzugaJpZM4IxRYD
.

grasmash · 2016-06-09T16:09:30Z

The part that confuses me is that you shouldn't need to change the nfs share value.

geerlingguy · 2016-06-09T16:13:36Z

With the latest everything, it should work with .... but maybe @haynescw has an older/not-8.x-latest copy of Bolt/BLT that has some patches applied but others not. Also, Drupal VM had some changes between 2.5.1 -> 3.0.0 -> 3.1.0 that could require some differences with setup.

Note that the way Drupal VM is installed/added on has changed recently too, and the old way required ../ but the current way ..

grasmash · 2016-06-09T16:31:24Z

I'm pretty sure he generated his project with the most recent version of BLT, which pins Drupal VM to ~3.1 and Drupal ~8.1. So, the only think that I can think of that would be different is Vagrant or Virtual Box.

haynescw · 2016-06-09T18:00:56Z

To clarify, when i submit my issues, i do my best to start from scratch. Fresh clone of blt and drupalvm. So if I do get an issue on a build, I do a get pull on blt and see if there are changes. if there is I start completely from scratch to abstract myself for old, outdated code.

kevinquillen · 2016-07-21T15:08:04Z

I also just ran into this very same error.

Are we to run ./blt.sh local:setup from inside the VM, or the hostmachine? Changing the local path did nothing for me. Otherwise I am stuck trying to get BLT to build from the standard setup with lightning.

grasmash · 2016-07-21T15:36:56Z

@kevinquillen Try removing the -r ${DIR}/docroot from drush.wrapper and let me know if that helps.

grasmash · 2016-07-21T15:37:43Z

If not, open a new issue and share your log output and configuration.

kevinquillen · 2016-07-21T15:40:24Z

Running.... that worked. What was the issue there?

On Thu, Jul 21, 2016 at 11:37 AM, Matthew Grasmick <notifications@github.com

wrote:

If not, open a new issue and share your log output and configuration.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#132 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAWGwIfifHHYx3xZeHtSpnJ97obq2Vqpks5qX5JIgaJpZM4IxRYD
.

grasmash · 2016-07-21T15:47:18Z

The -r argument tells drush where the docroot is, but that script is using the host machine's filesystem to set the argument value. Within the VM that causes issues. We should remove it from BLT until we find a more dynamic solution.

sodacrackers · 2017-05-21T05:00:21Z

For anyone else, drush worked for me by using site aliases: drush @mysite.local en some_module -t

haynescw closed this as completed Jun 9, 2016

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Command site-install needs a higher bootstrap level to run - you will need to invoke drush from a more functional Drupal environment to run this command. #132

Command site-install needs a higher bootstrap level to run - you will need to invoke drush from a more functional Drupal environment to run this command. #132

haynescw commented Jun 8, 2016

grasmash commented Jun 8, 2016 •

edited

haynescw commented Jun 8, 2016

haynescw commented Jun 8, 2016

CashWilliams commented Jun 8, 2016

haynescw commented Jun 8, 2016

grasmash commented Jun 9, 2016

haynescw commented Jun 9, 2016 •

edited

haynescw commented Jun 9, 2016

Set the destination to the Acquia Cloud subscription machine name.

haynescw commented Jun 9, 2016

haynescw commented Jun 9, 2016

haynescw commented Jun 9, 2016

grasmash commented Jun 9, 2016

haynescw commented Jun 9, 2016

grasmash commented Jun 9, 2016

haynescw commented Jun 9, 2016

grasmash commented Jun 9, 2016

geerlingguy commented Jun 9, 2016

grasmash commented Jun 9, 2016

haynescw commented Jun 9, 2016

kevinquillen commented Jul 21, 2016 •

edited

grasmash commented Jul 21, 2016

grasmash commented Jul 21, 2016

kevinquillen commented Jul 21, 2016

grasmash commented Jul 21, 2016

sodacrackers commented May 21, 2017

Command site-install needs a higher bootstrap level to run - you will need to invoke drush from a more functional Drupal environment to run this command. #132

Command site-install needs a higher bootstrap level to run - you will need to invoke drush from a more functional Drupal environment to run this command. #132

Comments

haynescw commented Jun 8, 2016

grasmash commented Jun 8, 2016 • edited

haynescw commented Jun 8, 2016

haynescw commented Jun 8, 2016

CashWilliams commented Jun 8, 2016

haynescw commented Jun 8, 2016

grasmash commented Jun 9, 2016

haynescw commented Jun 9, 2016 • edited

haynescw commented Jun 9, 2016

Provide the path to the project root to Vagrant.

Set the local_path for the first synced folder to ../.

Set the destination to the Acquia Cloud subscription machine name.

haynescw commented Jun 9, 2016

haynescw commented Jun 9, 2016

haynescw commented Jun 9, 2016

grasmash commented Jun 9, 2016

haynescw commented Jun 9, 2016

grasmash commented Jun 9, 2016

haynescw commented Jun 9, 2016

grasmash commented Jun 9, 2016

geerlingguy commented Jun 9, 2016

grasmash commented Jun 9, 2016

haynescw commented Jun 9, 2016

kevinquillen commented Jul 21, 2016 • edited

grasmash commented Jul 21, 2016

grasmash commented Jul 21, 2016

kevinquillen commented Jul 21, 2016

grasmash commented Jul 21, 2016

sodacrackers commented May 21, 2017

grasmash commented Jun 8, 2016 •

edited

haynescw commented Jun 9, 2016 •

edited

Set the local_path for the first synced folder to `../`.

kevinquillen commented Jul 21, 2016 •

edited