You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ansible --versionansible-playbook [core 2.14.4] [...] python version = 3.9.18 [GCC 8.5.0 20210514 (Red Hat 8.5.0-20)] (/usr/bin/python3) jinja version = 3.1.3 libyaml = Trueansible-galaxy collection listinfra.ah_configuration:2.0.6Private Automation Hub versionServer version 4.9.1Pulp Ansible Version 0.20.3Pulp Core Version 3.28.23Galaxy Importer 0.4.18Ansible Automation Platform 2.4
ansible installation method: EE
OS / ENVIRONMENT
Running through Ansible Automation Platform node-install on RHEL8, installed both AAP & PAH.
Desired Behavior
Role should be idempotent and not receive an error.
Actual Behavior
If the namespace already exists, it randomly fails on a HTTP 403 error. Same if it is the only role called by dispatch.
If said namespace is manually deleted, it is recreated successfully.
If PUT is done manually through curl with same parameters, it is 200 OK.
Failing on "Create Namespace | Wait for finish the namespace creation"
You don't have permission to PUT to /api/galaxy/v3/namespaces/XXX_system/ (HTTP 403).File "/tmp/ansible_ah_namespace_payload_yyy/ansible_ah_namespace_payload.zip/ansible_collections/infra/ah_configuration/plugin/module_utils/ah_module.py", line 224, in make_request response = self.session.open( File "/tmp/ansible_ah.../module_utils/urls.py", line 1557, in open r = urllib_request [...]
Same problem using directly 'infra.ah_configuration.namespace' role.
It seems that a 403 is returned when no change is applied, though I do not have this problem using curl 🤔
Summary
When using 'namespace' role, through dispatch, I randomly get a HTTP 403 error on PUT request.
Issue Type
Ansible, Collection, Private Automation Hub details
OS / ENVIRONMENT
Running through Ansible Automation Platform node-install on RHEL8, installed both AAP & PAH.
Desired Behavior
Role should be idempotent and not receive an error.
Actual Behavior
If the namespace already exists, it randomly fails on a HTTP 403 error. Same if it is the only role called by dispatch.
If said namespace is manually deleted, it is recreated successfully.
If PUT is done manually through curl with same parameters, it is 200 OK.
Failing on "Create Namespace | Wait for finish the namespace creation"
I have 4 different namespaces declared (names changed only), and others succeed while one randomly fails (they are "finished": "1").
STEPS TO REPRODUCE
The text was updated successfully, but these errors were encountered: