Support Tip:Ovconfd aborts during start up on nodes where cluster software is not configured
Ovconfd aborts during the start up on nodes where cluster software is installed but not configured
If cluster s/w is installed on a system, when ‘ovconfd ‘ comes up,
by default the default value of MONITOR_MODE is set to TRUE .
The Cluster CLIs executed to get the status of the cluster would return non-zero / wrong values
on such systems which causes ‘ovconfd’ to abort .
Set MONITOR_MODE=FALSE in ‘conf.cluster’ namespace
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
If you liked it I would appreciate KUDOs.