Bug 2039990

Summary:	[Improvement] SQL Server role should be able to use TLS cert/key files that are already on managed nodes
Product:	Red Hat Enterprise Linux 8	Reporter:	Brian Smith <briasmit>
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:	medium
Version:	8.7	CC:	gfialova, lmanasko, pkettman, spetrosi
Target Milestone:	rc	Keywords:	Improvement, Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ansible-collection-microsoft-sql-1.2.0-2.el8	Doc Type:	Enhancement
Doc Text:	The RN description for this BZ is covered as part of BZ#2066338. link: https://bugzilla.redhat.com/show_bug.cgi?id=2066338	Story Points:	---
Clone Of:
Clones:	2098212 (view as bug list)		Environment:
Last Closed:	2022-11-08 09:47:20 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:
Bug Blocks:	2098212

Description Brian Smith 2022-01-12 21:40:39 UTC

Description of problem:
Currently the SQL Server role, when setting up TLS certificate/keys, requires that the cert/key files are on the control node host, and the cert/key files are then copied to the managed nodes.  

With some work flows, the key/cert file are present on the managed nodes rather than the control node.  For example, when using the certificate role with IPA to generate certificates, the certificates need to be generated on each managed node.  

In addition to the current functionality of copying the cert/keys from the control node to the managed node, the role should have an option to use cert/key files already on the managed node.  

Version-Release number of selected component (if applicable):
ansible-collection-microsoft-sql-1.1.0-1.el8.noarch

Comment 10 errata-xmlrpc 2022-11-08 09:47:20 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/RHBA-2022:7597