[Feedback] First `vagrant up` throws an error while provisioning

[mathiasschopmans]

While trying to boot the machine I got an error as seen in the screenshot:

Here's the plain output for indexability:

TASK [mariadb : Add Key for MariaDB Repository] ********************************
changed: [192.168.33.10]

TASK [mariadb : Add MariaDB-Repository] ****************************************
fatal: [192.168.33.10]: FAILED! => {"changed": false, "failed": true, "module_stderr": "", "module_stdout": "Traceback (most recent call last):\r\n  File \"/tmp/ansible_uwZUY6/ansible_module_apt_repository.py\", line 525, in <module>\r\n    main()\r\n  File \"/tmp/ansible_uwZUY6/ansible_module_apt_repository.py\", line 515, in main\r\n    cache.update()\r\n  File \"/usr/lib/python2.7/dist-packages/apt/cache.py\", line 440, in update\r\n    raise FetchFailedException(e)\r\napt.cache.FetchFailedException: W:Failed to fetch http://mirror3.layerjet.com/mariadb/repo/10.1/ubuntu/dists/trusty/main/binary-amd64/Packages  404  Not Found\r\n, E:Some index files failed to download. They have been ignored, or old ones used instead.\r\n", "msg": "MODULE FAILURE"}

NO MORE HOSTS LEFT *************************************************************

RUNNING HANDLER [nginx : restart nginx] ****************************************
	to retry, use: --limit @/Users/mathiasschopmans/Sites/ongr-vm/vagrant.retry

PLAY RECAP *********************************************************************
192.168.33.10              : ok=20   changed=15   unreachable=0    failed=1   

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

Maybe this can be fixed. I'm trying to move on with vagrant reload --provision

[mathiasschopmans]

Thanks! This was fast. 👍

[mathiasschopmans]

@saimaz @kazgurs
The change broke the CI-Tests.