However if your Tower/AWX container runs on different port published (e.g. -p 8088:8013) you will get Connection refused because port that Tower/AWX actually listen to is unavailable from outside.
Tower/AWX itself always returns urls with trailing slash.
Connection refused example with cURL:
curl -L -v --request GET \
--url https://myhost/api/v2/hosts/1/ansible_facts \
--header 'authorization: Basic mybase64' \
--header 'content-type: application/json'
* Trying ip:443...
* Connected to myhost (ip) port 443 (#0)
* SSL certificate verify ok.
> GET /api/v2/hosts/1/ansible_facts HTTP/2
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 301
< location: http://myhost:8013/api/v2/hosts/1/ansible_facts/
* Ignoring the response-body
* Connection #0 to host myhost left intact
* Issue another request to this URL: 'http://myhost:8013/api/v2/hosts/1/ansible_facts/'
* Trying ip:8013...
* connect to ip port 8013 failed: Connection refused
* Failed to connect to myhost port 8013 after 45 ms: Connection refused
With towerlib it makes not possible to get job dynamic values:
q = tower.get_job_by_id(1)
test = q.status # ConnectionError Exception here
I believe this redirect is redundant so I fixed all urls that I can find 🙂
Urls without trailing slash get redirect from Tower host to url with it: https://docs.ansible.com/ansible-tower/3.8.4/html/towerapi/conventions.html .
However if your Tower/AWX container runs on different port published (e.g.
-p 8088:8013) you will getConnection refusedbecause port that Tower/AWX actually listen to is unavailable from outside.Tower/AWX itself always returns urls with trailing slash.
Connection refused example with cURL:
With towerlib it makes not possible to get job dynamic values:
I believe this redirect is redundant so I fixed all urls that I can find 🙂