Depending on timing, it's possible for node_info.member to be set
after this ccb callback. We should populate userData anyway, in case
the active validates this callback and then a SC failover to the
standby occurs.
---
src/amf/amfd/node.cc | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/amf/amfd/node.cc b/src/amf/amfd/node.cc
index e8f32bb..f95af3e 100644
--- a/src/amf/amfd/node.cc
+++ b/src/amf/amfd/node.cc
@@ -508,6 +508,7 @@ static SaAisErrorT node_ccb_completed_delete_hdlr(
if (node->node_info.member) {
report_ccb_validation_error(opdata, "Node '%s' is still cluster member",
osaf_extended_name_borrow(&opdata->objectName));
+ opdata->userData = node;
return SA_AIS_ERR_BAD_OPERATION;
}
--
2.7.4
_______________________________________________
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel
