Windows Discovery fails to create Windows clusters - Windows 2016 ClusterIssue When Windows Discovery runs, it is triggering a "Windows OS - Server" Pattern as expected and no errors were spotted, but the Windows Cluster is not being created on the "cmdb_ci_win_cluster" table.ReleaseLondon, MadridCauseTroubleshooting: If you follow through the "Windows OS - Servers" Pattern on debug mode, it is meant to create a cluster record on Step 15.21 "Insert clusters data to cmdb_ci_win_cluster" But the condition on that step was never met and as a result, the cluster record never got created. Two conditions to meet: * $isNode equal "true" * $shouldRunClusterOnOSType equal "true" 1. Checking on how $isNode Variable is set. * We create $isNode variable at step 2.20 "Create isNode Variable" and set it to "false" by default. * We then set the value to "true" at step 15.5 if it meets any of the conditions mentioned in that step. 2. Checking further on why "$shouldRunClusterOnOSType was not set to "true" * We create $shouldRunClusterOnOSType variable initially at step: 2.27 and set the value to "false" * We then tried to set the value to "True" if $isServer value is "true" at step 2.51. * But we could not find $isServer variable. * So we need to understand why $isServer was not set at some of the steps at the top. * Looking at step 2.26: We can see that we only set the $isServer to "true" if it meets any of the conditions below. * Since the conditions below don't include "2016" or "2019," this step never set the "isServer" variable to "true". * As a result, $shouldRunClusteronOSType value was never set to "true" ResolutionAs a workaround: We can manually add the condition at step 2.26 to include "2016" and "2019"Save and Publish the Pattern. Or We can import the "Windows - General Pattern Variables" Pattern from New York Instance as these conditions are included in the New York Release.Once the Pattern has been imported, make sure to re-sync the Pattern by right-clicking on the pattern name and selecting "Synchronize with MID Servers" Or Restart all MID servers.