Icinga / Icinga/icinga-powershell-cluster
Adding Check for Clusterhealthcheck if this is really a ClusterNode
Open
@LordHepipud is already working on this.
Since Jul 14, 2026.
needs-feedback
- Dominant language
- PowerShell
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Installing the component on a non valid Cluster node and trying to execute the check ends in abrupt break and there seems to be no real error message.
Suggestion adding the following
function Invoke-IcingaCheckClusterHealth()
{
param (
[array]$Include = @(),
[array]$Exclude = @(),
[ValidateSet('Unknown', 'Up', 'Down', 'Paused', 'Joining')]
[array]$WarningState = @(),
[ValidateSet('Unknown', 'Up', 'Down', 'Paused', 'Joining')]
[array]$CriticalState = @(),
[switch]$SkipClusterRessource = $FALSE,
[switch]$NoPerfData = $FALSE,
[ValidateSet(0, 1, 2, 3)]
$Verbosity = 0
);
if((Get-WindowsFeature -Name Failover-Clustering).InstallState -eq "Available") {
Write-IcingaEventMessage -EventId xxxx -Namespace 'Cluster';
echo "This is not a vaild Failover cluster node this component shouldn't be installed here"
break;
}
else {
continue;
}
# Create a main CheckPackage under which all other checks will be placed
$CheckPackage = New-IcingaCheckPackage -Name 'Cluster Services' -OperatorAnd -Verbose $Verbosity -AddSummaryHeader;
$ClusterServiceInfo = Get-IcingaClusterInfo;
...
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.