Skip to content

Commit

Permalink
Correct condition message between Node not found and NHC time out sce…
Browse files Browse the repository at this point in the history
…narios

Condition message didn't match the variable name
  • Loading branch information
razo7 committed Aug 23, 2023
1 parent 3e0294e commit 09d07d2
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions api/v1alpha1/fenceagentsremediation_types.go
Original file line number Diff line number Diff line change
Expand Up @@ -31,8 +31,8 @@ const (
// FenceAgentActionSucceededType is the condition type used to signal whether the Fence Agent action was succeeded successfully or not
FenceAgentActionSucceededType = "FenceAgentActionSucceeded"
// condition messages
RemediationFinishedNodeNotFoundConditionMessage = "Node Healthcheck timeout annotation has been set"
RemediationInterruptedByNHCConditionMessage = "FAR CR name doesn't match a node name"
RemediationFinishedNodeNotFoundConditionMessage = "FAR CR name doesn't match a node name"
RemediationInterruptedByNHCConditionMessage = "Node Healthcheck timeout annotation has been set"
RemediationStartedConditionMessage = "FAR CR was found, its name matches one of the cluster nodes, and a finalizer was set to the CR"
FenceAgentSucceededConditionMessage = "FAR taint was added, fence agent command has been created and executed successfully"
RemediationFinishedSuccessfullyConditionMessage = "The unhealthy node was fully remediated (it was tainted, fenced using FA and all the node resources have been deleted)"
Expand Down

0 comments on commit 09d07d2

Please sign in to comment.