##### 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.
url = _urljoin(self.api_server, self.available_api_versions['v1'], "notification_secrets")
        data = self._call_galaxy(url, auth_required=True)
        return data
    @g_connect(['v1'])
    def remove_secret(self, secret_id):
        url = _urljoin(self.api_server, self.available_api_versions['v1'], "notification_secrets", secret_id) + '/'
        data = self._call_galaxy(url, auth_required=True, method='DELETE')
        return data
    @g_connect(['v1'])
    def delete_role(self, github_user, github_repo):
        url = _urljoin(self.api_server, self.available_api_versions['v1'], "removerole",
                       "?github_user=%s&github_repo=%s" % (github_user, github_repo))
        data = self._call_galaxy(url, auth_required=True, method='DELETE')
        return data
    
    @g_connect(['v2', 'v3'])
    def publish_collection(self, collection_path):
        """
        Publishes a collection to a Galaxy server and returns the import task URI.
        :param collection_path: The path to the collection tarball to publish.
        :return: The import task URI that contains the import results.
        """
        display.display("Publishing collection artifact '%s' to %s %s" % (collection_path, self.name, self.api_server))
        b_collection_path = to_bytes(collection_path, errors='surrogate_or_strict')
        if not os.path.exists(b_collection_path):
            raise AnsibleError("The collection path specified '%s' does not exist." % to_native(collection_path))
        elif not tarfile.is_tarfile(b_collection_path):
            raise AnsibleError("The collection path specified '%s' is not a tarball, use 'ansible-galaxy collection "
                               "build' to create a proper release artifact." % to_native(collection_path))
        with open(b_collection_path, 'rb') as collection_tar: