Something in rc17 release breaks Drupal VM's CI builds

[geerlingguy]

Issue title

The issue title should comply with the following structure:

[ console ] Drupal VM's CI builds started failing a few hours ago on April 23, 2017 (seems to coincide with the Drupal Console rc17 release...).

Problem/Motivation

Besides the dreaded 500 error that pops up from time to time (#3233), Drupal VM's CI tests are normally run anywhere between 20-100 times per day, and it's a decent bellwether for other upstream software that might be breaking things...

It seems that all builds that include Drupal Console are failing after rc17 with the following error:

TASK [geerlingguy.drupal-console : Run Drupal Console init.] *******************
fatal: [localhost]: FAILED! => {"changed": true, "cmd": "php /usr/local/bin/drupal init", "delta": "0:00:00.062620", "end": "2017-04-24 01:22:32.724793", "failed": true, "rc": 1, "start": "2017-04-24 01:22:32.662173", "stderr": "", "stderr_lines": [], "stdout": "Could not find Drupal in the current path.", "stdout_lines": ["Could not find Drupal in the current path."]}

(More succinctly, Could not find Drupal in the current path.).

Example failed build: https://travis-ci.org/geerlingguy/drupal-vm/jobs/225029757

How to reproduce

1. Download Drupal VM.

2. Create a config.yml file with the following contents:

   installed_extras:
   - drupalconsole
   - drush
   - mailhog

3. Run vagrant up.

Solution

Figure out what's changed that causes the drupal init to fail. If it's something we should do differently in terms of a global install, maybe help figure out the upstream solution in the geerlingguy.drupal-console role: https://github.com/geerlingguy/ansible-role-drupal-console

[geerlingguy]

Closing as a duplicate of #3279