From: jhe2 <jhe2@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Ansible get_url does not work
Date: Wed, 29 Nov 2023 09:23:40 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47483@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1518 bytes --]
New issue by jhe2 on void-packages repository
https://github.com/void-linux/void-packages/issues/47483
Description:
### Is this a new report?
Yes
### System Info
Void 6.5.11_1 x86_64 AuthenticAMD uptodate rrmFFFFFFFFFF
### Package(s) Affected
ansible-8.0.0_2
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
When using the Ansible `get_url` module, the module should fetch the resource at the specified URL.
### Actual behaviour
Instead of fetching the URL, it fails with an error message: "An unknown error occurred: HTTPSConnection.__init__() got an unexpected keyword argument 'cert_file'".
The `cert_file` argument to `http.client.HTTPSConnection` was dropped in Python 3.12. The problem could possibly be caused by an outdated version of `python3-urllib`, which is used by the `get_url` module.
### Steps to reproduce
With Ansible installed, try using the `get_url` module, e.g.
```
ansible -i inventory -m get_url -a '{ "dest": "/tmp", "url": "https://duck.com/"}' localhost
```
This results in the following error:
```
localhost | FAILED! => {
"changed": false,
"dest": "/tmp",
"elapsed": 0,
"gid": 0,
"group": "root",
"mode": "01777",
"msg": "An unknown error occurred: HTTPSConnection.__init__() got an unexpected keyword argument 'cert_file'",
"owner": "root",
"size": 320,
"state": "directory",
"uid": 0,
"url": "https://duck.com/"
}
```
next reply other threads:[~2023-11-29 8:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 8:23 jhe2 [this message]
2023-11-29 9:00 ` classabbyamp
2023-12-01 13:04 ` dataCobra
2023-12-02 21:24 ` [ISSUE] [CLOSED] " classabbyamp
2024-05-03 9:45 ` panticz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47483@inbox.vuxu.org \
--to=jhe2@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).