SqlServerDsc: Integration tests fail to install instance

[johlju]

There are currently an issue with one of the integration tests, the test that installs a default instance. This is most likely related to a problem on the AppVeyor build worker.
Trying to narrowing down the problem by remove different parts of the integration tests to see if this is a problem with one of the other tests, or just a timing issue on the build worker.
Previously it failed when running dev-branch, and I have actually gotten it to pass when removing all the unit tests, but sometimes it works, so this error comes intermittent.

Posting this issue so that everyone is aware of this problem.

This is blocking all the PR's from merging and blocking release.

[johlju]

Updated the issue description. It seems this is an intermittent problem when running on the AppVeyor build worker, and probably due to all the previous installed (but stopped) instances on the build worker.

Since we can't control what is on the build worker, or takes to long to uninstall all the existing instances, I see only two options.

1. Try to restart the build worker (during install step) before running tests, if a reboot is missing and would help.
2. Remove all integration test related to the default instance, when running in AppVeyor, until we can have a safer method of running tests (maybe Azure Pipelines?).

[johlju]

So I did the alternative 1 above, and that made 4 of 4 test runs to pass. Sending in a PR with that change and hold my fingers that it's a solution. 🙂

[johlju]

Reopning this issue since the workaround that was merged only mitigated the issue, but did not solve it. Discussion around this SQL issue is being made in the issue appveyor/ci#2804. A thought is that this is due to are test suite is to memory intensive. One change is that the AppVeyor build worker since two days back has more memory allocated.

I suggest we revert the workaround, and if the issue still exist, then look into running test sequentially in several build workers (parallel testing, but for free account they are run sequentially).

[johlju]

It seems the service is in single user mode, and that is why it can't connect to the instance. I totally missed this error message. 😞

VERBOSE: Detailed results:
VERBOSE:   Feature:                       Database Engine Services
VERBOSE:   Status:                        Failed: see logs for details
VERBOSE:   Reason for failure:            An error occurred during the setup process of the feature.
VERBOSE:   Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
VERBOSE:   Component name:                SQL Server Database Engine Services Instance Features
VERBOSE:   Component error code:          0x84BB0001
VERBOSE:   Error description:             Login failed for user 'APPVYR-WIN\SqlInstall'. Reason: Server is in single user mode. Only one administrator can connect at this time.

That means it must be a timing issue when the resource try to connect to the SQL Server instance after successful install to verify availability/existence in the Get-TargetResource function. Correction, the problem is during the install - Setup exited with code '-2068119551', and it reports the component error code above.

[johlju]

Are there someone that knows a direct download URL for the ISO for SQL Server 2016 with SP2?

[johlju]

I hope the latest merge of PR #1268 will solve this. I will reopen if we see this issue again.