We rebooted the passive node of a Windows Server 2008 R2 cluster hosting SQL 2008 for OS patching, and this triggered the restart of the SQL Services on the Active Node.
I first thought that the Active Node had been rebooted by mistake but the event log showed SQL was running on node 2 the whole time, and it was node 1 which was rebooted.
There is a error message about quorum being lost causing cluster service to shut down. We thought that the Current Host Server was node 1 so when it was rebooted Node 2 might have shut down SQL then brought it back after it took the quorum disk. But I tested this scenario on a non-production cluster (rebooted the current host server while SQL was running on other node) but SQL was not affected.
Has anyone else seen this?