[MODULES-6168] SQLServer fact doesn't detect 2017 - Puppet Tickets

XML

Word

Printable

Details

Type: New Feature
Status: Resolved
Priority: Normal
Resolution: Fixed
Affects Version/s: None
Fix Version/s: SQL Server 2.1.0
Component/s: sqlserver
Labels:
None

Acceptance Criteria:

Hide

Running the module should correctly detect that there
is no SQL 2017 instance installed on the host.

Running the module should correctly install SQL 2017 on the host.

Running the module should only install an instance once.

Confirm other installation conforms to previous behavior.

Show
Running the module should correctly detect that there is no SQL 2017 instance installed on the host. Running the module should correctly install SQL 2017 on the host. Running the module should only install an instance once. Confirm other installation conforms to previous behavior.
Epic Link:
SQL 2.1.0
Team:
Windows
Sprint:
Windows Kanban

QA Risk Assessment:
Needs Assessment

Description

From user e-mail:

Just to highlight, we don’t need the new features at this point, we just need that the facter recognize the SQL 2017 installed, as in our current tests, current module install SQL 2017 sucessfully, however every agent run it tries to install again because the facter doesn’t recognize there’s a SQL 2017 installed.

Attachments

Issue Links

relates to

MODULES-8438 SQLServer fact doesn't detect 2019

Resolved

MODULES-5774 SQLserver : Add support for SQL Server 2017

Resolved

Activity

People

Assignee:: William Hurt

Reporter:: Paul Anderson

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 2017/11/29 7:43 AM

Updated:: 2019/01/07 7:23 AM

Resolved:: 2017/12/07 7:05 PM