VVV: MariaDB provisioning fails and causing VVV to not provision sites

Expected Behavior

Fresh install of VVV would provision all custom sites specified in vvv-custom.yml and those sites would work normally as would all default sites provisioned by VVV including the VVV Dashboard.

Current Behavior

While provisioning, the script throws errors when its trying to set up MariaDB. Once the script has finished running, no sites are found to be provisioned including the VVV Dashboard.

Steps to Reproduce (for bugs)

Do a clean install of VVV on develop branch.
Once provisioning is done, check for http://vvv.test in browser.

Installation log: https://gist.github.com/coolamit/981d3e35081a88c35a3178aa044d6e04

Your Environment

VVV version: v3.0.0-git::develop
VVV Git Branch: develop
Vagrant version: 2.2.4
VM Provider name: VirtualBox
VM Provider version: 5.2.28
Operating System and version: Windows 10 Pro

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 61 (39 by maintainers)

Most upvoted comments

Done! Now if it’s running on trusty it’ll halt provisioning and tell you what to do

tomjn on May 7, 2019

@tomjn It’s working 😃

mathieuhays on May 15, 2019

I made a PR to auto-move the backups folder to the right location https://github.com/Varying-Vagrant-Vagrants/VVV/pull/1808

tomjn on May 15, 2019

No worries @coolamit I saw that, but I hadn’t realised it would still attempt to provision on 14

tomjn on May 7, 2019