Ack (reviewed only) /HansF > -----Original Message----- > From: [email protected] [mailto:[email protected]] > Sent: den 11 september 2014 13:34 > To: Hans Feldt; Hans Nordebäck; [email protected] > Cc: [email protected] > Subject: [PATCH 1 of 1] amfd: update su oper state to imm during su addition > [#1054] > > osaf/services/saf/amf/amfd/su.cc | 3 +++ > 1 files changed, 3 insertions(+), 0 deletions(-) > > > Amfd sets oper state as disable when it create su in its data base. > When Amfd goes to update imm in set_oper_state to mark it disable, then > because of if(saAmfSUOperState == oper_state), it fails to update as > current oper state is same as to be updated. So, oper state is not > updated in imm for su hosted on absent node. > > Amfd should explicitely update oper state to imm along with other > run time params like SUPreInstantiable, saAmfSUHostedByNode, etc > > diff --git a/osaf/services/saf/amf/amfd/su.cc > b/osaf/services/saf/amf/amfd/su.cc > --- a/osaf/services/saf/amf/amfd/su.cc > +++ b/osaf/services/saf/amf/amfd/su.cc > @@ -649,6 +649,9 @@ static void su_add_to_model(AVD_SU *su) > } > > done: > + avd_saImmOiRtObjectUpdate(&su->name, "saAmfSUOperState", > + SA_IMM_ATTR_SAUINT32T, &su->saAmfSUOperState); > + > avd_saImmOiRtObjectUpdate(&su->name, "saAmfSUPreInstantiable", > SA_IMM_ATTR_SAUINT32T, &su->saAmfSUPreInstantiable); >
------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ Opensaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-devel
