If an OpenSAF component requires reload after an upgrade,
then AMF should also be upgraded, requiring a node
reboot. Thus there is no need to refresh component
config.

The patch fixes a problem where OpenSAF has been upgraded
and is about to be rebooted. Before the reboot occurs,
IMMND aborts due to message loss, and AMFND is trying to
reload IMMND's configuration. Since IMMND is down, AMFND
is stuck in saImmOmInitialize(), before eventually being killed
by the AMF watchdog.
---
 src/amf/amfnd/compdb.cc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/amf/amfnd/compdb.cc b/src/amf/amfnd/compdb.cc
index 1aa3863ec..1ecd1a1c9 100644
--- a/src/amf/amfnd/compdb.cc
+++ b/src/amf/amfnd/compdb.cc
@@ -1687,7 +1687,7 @@ int avnd_comp_config_reinit(AVND_COMP *comp) {
   ** At first time instantiation of OpenSAF components we cannot go
   ** to IMM since we would deadloack.
   */
-  if (comp->config_is_valid) {
+  if (comp->config_is_valid || comp->su->is_ncs == true) {
     res = 0;
     goto done1;
   }
-- 
2.11.0


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel

Reply via email to