Bug 2151284
| Summary: | Use the certificate role to create the cert and the key | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Sergei Petrosian <spetrosi> |
| Component: | ansible-collection-microsoft-sql | Assignee: | Sergei Petrosian <spetrosi> |
| Status: | CLOSED ERRATA | QA Contact: | Daniel Yeisley <dyeisley> |
| Severity: | unspecified | Docs Contact: | Alexandra Nikandrova <anikandr> |
| Priority: | unspecified | ||
| Version: | 9.2 | CC: | dyeisley |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ansible-collection-microsoft-sql-1.3.0-1.el9 | Doc Type: | Enhancement |
| Doc Text: |
.Microsoft SQL Server Ansible role can generate TLS certificates
Previously, you needed to generate a TLS certificate and a private key on the nodes manually before configuring the Microsoft SQL Ansible role. With this update, the Microsoft SQL Server Ansible role can use the `redhat.rhel_system_roles.certificate` role for that purpose. Now, you can set the `mssql_tls_certificates` variable in the format of the `certificate_requests` variable of the `certificate` role to generate a TLS certificate and a private key on the node.
|
Story Points: | --- |
| Clone Of: | 2144852 | Environment: | |
| Last Closed: | 2023-05-09 07:53:38 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 2144852 | ||
| Bug Blocks: | |||
|
Comment 4
Daniel Yeisley
2023-01-03 18:24:25 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (ansible-collection-microsoft-sql bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2023:2411 |