##### SUMMARY

Tonight many of my roles started failing CI tests, and after an hour or so I tracked down the problem to an old version of the `geerlingguy.php` role being installed. The current version on Galaxy (see https://galaxy.ansible.com/geerlingguy/php) is 3.7.0.

But Molecule was downloading the release prior to that, 3.6.3.

I also tested manually installing the role (without specifying a version) on two other fresh environments—in _both_ cases, it still downloaded the old not-current version, 3.6.3.

So... either the Galaxy API and the Galaxy UI are out of sync, or something is wrong with Ansible's `ansible-galaxy` command, and it's causing older-than-latest versions of at least one role to be downloaded...

##### ISSUE TYPE

- Bug Report

##### COMPONENT NAME

ansible-galaxy

##### ANSIBLE VERSION

```
ansible 2.9.0
  config file = None
  configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/lib/python2.7/dist-packages/ansible
  executable location = /usr/local/bin/ansible
  python version = 2.7.15+ (default, Oct  7 2019, 17:39:04) [GCC 7.4.0]
```

##### CONFIGURATION

```
N/A (no changes)
```

##### OS / ENVIRONMENT

  - Ubuntu 18.04: fail (3.6.3)
  - Ubuntu 16.04: fail (3.6.3)
  - Debian 10: fail (3.6.3)
  - Debian 9: fail (3.6.3)
  - Debian 8: success (3.7.0)
  - CentOS 8: success (3.7.0)
  - CentOS 7: fail (3.6.3)

Ansible 2.9.0 was used in each environment, installed via Pip. Very weird. I even ran the test in a fresh new Debian 8 and CentOS 8 environment 3 times each, and it was successful every time. And I ran the other tests at least twice each and they failed every time... so it doesn't _seem_ to be a cache-related issue in the API.

##### STEPS TO REPRODUCE

  1. `ansible-galaxy install geerlingguy.php`

##### EXPECTED RESULTS

The latest version of the role (3.7.0) should be installed.

##### ACTUAL RESULTS

An older version of the role (3.6.3) was installed.

Note that the proper version _was_ installed on CentOS 8 and Debian 8... but none of the other OSes I tested, all confirmed to be running Ansible 2.9.0, installed via Pip.
wait = 2
        while timeout == 0 or (time.time() - start) < timeout:
            data = self._call_galaxy(full_url, method='GET', auth_required=True,
                                     error_context_msg='Error when getting import task results at %s' % full_url)
            state = data.get('state', 'waiting')
            if data.get('finished_at', None):
                break
            display.vvv('Galaxy import process has a status of %s, wait %d seconds before trying again'
                        % (state, wait))
            time.sleep(wait)
            
            wait = min(30, wait * 1.5)
        if state == 'waiting':
            raise AnsibleError("Timeout while waiting for the Galaxy import process to finish, check progress at '%s'"
                               % to_native(full_url))
        for message in data.get('messages', []):
            level = message['level']
            if level == 'error':
                display.error("Galaxy import error message: %s" % message['message'])
            elif level == 'warning':
                display.warning("Galaxy import warning message: %s" % message['message'])
            else:
                display.vvv("Galaxy import message: %s - %s" % (level, message['message']))
        if state == 'failed':
            code = to_native(data['error'].get('code', 'UNKNOWN'))
            description = to_native(
                data['error'].get('description', "Unknown error, see %s for more details" % full_url))
            raise AnsibleError("Galaxy import process failed: %s (Code: %s)" % (description, code))
    @g_connect(['v2', 'v3'])
    def get_collection_version_metadata(self, namespace, name, version):