Closed dlehrman closed 1 week ago
cc @TSKushal @bhavya06 @jyundt @mraineri @rajeevkallur @renxulei @tomasg2012 @xmadsen click here for bot help
The failing CI tests are complaining about FATAL: A Python version was not specified for environment
, which seems to be an issue with the CI test configuration.
The failing CI tests are complaining about
FATAL: A Python version was not specified for environment
, which seems to be an issue with the CI test configuration.
ansible-core devel updated their supported platforms (https://github.com/ansible/ansible/commit/dad6f077319d993c0fa440dd426174a54f034c53), I'll need to adjust CI to that...
The code changes themselves look good to me though; thanks for submitting this!
✅ Backport PR branch: patchback/backports/stable-9/0d50131d5ea8f1e82948b47daa4828432e5ddacf/pr-8533
Backported as https://github.com/ansible-collections/community.general/pull/8548
🤖 @patchback I'm built with octomachinery and my source is open — https://github.com/sanitizers/patchback-github-app.
@dlehrman thanks for your contribution! @mraineri thanks for reviewing!
SUMMARY
Adds an option for ciphers to the redfish modules and aligns with the ciphers option of the ansible.builtin.uri and community.crypto.get_certificate modules.
ISSUE TYPE
COMPONENT NAME
ADDITIONAL INFORMATION
I use Ansible to manage various device types (e.g. PDU's, BMC's, etc) that only support legacy ciphers and/or do not support >2048 bit certificates. For some of these devices, depending on the Ansible controller, the redfish modules were experiencing a handshake failure, though I could still interact them with CLI or GUI web browsers (curl, Chrome, Firefox).
Without manually setting ciphers (example endpoint uses 2048 bit cert, TLSv1.2 / ECDHE-RSA-AES256-SHA, cannot be changed):
After manually setting ciphers to "HIGH":
Relevant task:
Ansible controller properties: