-
Bug
-
Resolution: Obsolete
-
Normal
-
None
-
2.1.3
-
None
-
None
-
False
-
-
False
-
-
We are doing performance testing in the following env -> https://beta-galaxy-stage.ansible.com and we have encounter the following bug
Collection name: arista.avd:
- Error when getting available collection versions for galaxy ansible2.13 arista.avd from beta
- Skipping Galaxy server https:. an unexpected galaxy ansible2.13 error when getting available versions of collection
nansible.netcommon: [Errno 104] 1
Connection reset by peer
nERROR! Unexpected Exception, this is probably a bug: [Errno 104] Connection reset by peer
n'")
Collection name: community.general
ERROR! Error when getting available collection
galaxy ansible2.13 versions for community.general from beta (https:. (HTTP Code: 504, Message: Gateway 2
Timeout Code: Unknown)
n'")
Collection name: *ansible.windows *
Unknown 2 error when attempting to call Galaxy at \'https://beta-galaxy- stage.ansible.com/api/v3/plugin/ansible/content/published/collections/index/ansible/wind ows/versions/?limit=10&offset=20\': The read operation timed out
n"')
Collection name: ansible.netcommon
ERROR! Error when finding available api versions 1 from beta (https:. (HTTP Code: 504, Message: Gateway Timeout)
n'")
Collection name: elfelip.keycloak
ERROR! Error when getting collection version
galaxy ansible2.13 metadata for elfelip.keycloak:0.1.3 from beta (https:. (HTTP Code: 504, Message: 2
Gateway Timeout Code: Unknown)
n'")
Collection name: dkraklan.terraform_vmware_vm
ERROR! Error when getting available galaxy ansible2.13 collection versions for dkraklan.terraform_vmware_vm from beta (https:. (HTTP Code: 1
504, Message: Gateway Timeout Code: Unknown)
n'")
- is blocked by
-
AAH-2346 namespace metadata queries are eating database CPU
- Closed