Closed ghost closed 9 years ago
I had a similar issue with the mysql role, but it got a little further for me before it failed. I have my output in this issue https://github.com/GetValkyrie/valkyrie/issues/65
I don't know the cause either, but attempting to treat the symptoms, I switched the getvalkyrie.mysql role to geerlingguy.mysql role pinned to the 1.5.2 release and it ran successfully.
I have the fork here if you want to try it out https://github.com/RealLukeMartin/valkyrie
I finally fixed this one.
Long story short, the problem wasn't in Valkyrie source. For the record, if you encounter this error, just run a $ vagrant plugin update vagrant-triggers
.
Closing.
I am getting this now, after the PR is applied, and my tree looks the same...
goddamn Vagrant
Yea I feel like somethings are getting cached strangely sometimes. You might have already tried this, but if not:
Try removing ~/.drush/valkyrie
and ~/.drush/cache/valkyrie
Then run git clone https://github.com/GetValkyrie/valkyrie.git ~/.drush/valkyrie --recursive
and drush cc drush
Then drush vnew
after that and I believe it will work, let me know if this still doesn't work though.
thanks for the support, that fixed it !
I'm currently facing a 100% reproducible problem during the
drush vnew
process:In the VM, the
/vagrant/.valkyrie/valkyrie/vagrant/ansible/roles/getvalkyrie.mysql/
directory is empty (as isgetvalkyrie.drush/
):On the host however, the corresponding directory has expected content:
User/group is good, so accessing these files should not be a problem.
Any clue how to debug this, since logs seems to be not very helpful?