Context
Per the SC//HyperCore 9.8.2 release notes, HyperCore has required TLS 1.3 for REST API HTTPS
requests since version 9.6, deprecating TLS 1.2. The release notes flag this as a risk for older
control-node environments and third-party integrations generally.
This has already been exercised successfully against a real 9.7.7 cluster (which is TLS-1.3-only,
since the requirement started at 9.6) via the collection's normal integration test run — so basic
connectivity from a reasonably current control node is confirmed working, not a known bug.
Requirement
Confirm that TLS 1.3 negotiates successfully from every control-node environment currently exercised
in CI (whatever OS/Python/OpenSSL combinations that covers today, including any older lanes kept as
best-effort per the version-window issue), against a 9.6+ target. Document whatever minimum
OS/Python/OpenSSL requirement this implies for collection users — TLS 1.3 generally requires Python
3.7+ with OpenSSL 1.1.1+; some older base images (e.g. default OpenSSL on older RHEL/CentOS
releases) may not qualify regardless of which Python version is layered on top.
This is a verification/documentation task, not a known defect — no fix should be needed unless the
check turns up an actual failure.
Reference (not a spec)
Directly relevant to whatever Ansible-core/Python floor is landed on via the version-reconciliation
issue, since that's the same "what control-node environments do we actually support" question from
a different angle.
Context
Per the SC//HyperCore 9.8.2 release notes, HyperCore has required TLS 1.3 for REST API HTTPS
requests since version 9.6, deprecating TLS 1.2. The release notes flag this as a risk for older
control-node environments and third-party integrations generally.
This has already been exercised successfully against a real 9.7.7 cluster (which is TLS-1.3-only,
since the requirement started at 9.6) via the collection's normal integration test run — so basic
connectivity from a reasonably current control node is confirmed working, not a known bug.
Requirement
Confirm that TLS 1.3 negotiates successfully from every control-node environment currently exercised
in CI (whatever OS/Python/OpenSSL combinations that covers today, including any older lanes kept as
best-effort per the version-window issue), against a 9.6+ target. Document whatever minimum
OS/Python/OpenSSL requirement this implies for collection users — TLS 1.3 generally requires Python
3.7+ with OpenSSL 1.1.1+; some older base images (e.g. default OpenSSL on older RHEL/CentOS
releases) may not qualify regardless of which Python version is layered on top.
This is a verification/documentation task, not a known defect — no fix should be needed unless the
check turns up an actual failure.
Reference (not a spec)
Directly relevant to whatever Ansible-core/Python floor is landed on via the version-reconciliation
issue, since that's the same "what control-node environments do we actually support" question from
a different angle.