- **status**: review --> fixed
- **Comment**:

changeset:   6589:d719ade2b028
tag:         tip
parent:      6586:86155b31d535
user:        Rafael Odzakow <[email protected]>
date:        Mon May 18 10:27:25 2015 +0200
summary:     smfd: get nodes for activation without warning if entity was a 
node [#960]

changeset:   6588:21730a950421
branch:      opensaf-4.6.x
parent:      6585:751c407456d0
user:        Rafael Odzakow <[email protected]>
date:        Mon May 18 10:27:25 2015 +0200
summary:     smfd: get nodes for activation without warning if entity was a 
node [#960]

changeset:   6587:071c4ca7a679
branch:      opensaf-4.5.x
parent:      6584:1c592917282b
user:        Rafael Odzakow <[email protected]>
date:        Mon May 18 10:27:25 2015 +0200
summary:     smfd: get nodes for activation without warning if entity was a 
node [#960]



---

** [tickets:#960] Activation/Deact units didnot allow amf node dn in single 
step upgrade.**

**Status:** fixed
**Milestone:** 4.7-Tentative
**Created:** Wed Jul 16, 2014 06:38 AM UTC by Hrishikesh
**Last Updated:** Wed May 20, 2015 01:39 PM UTC
**Owner:** Robert Apanowicz

Setup :SLES 64bit, changeset: 5270 of opensaf-4.3.x branch.

Problem description: 
===================
During singlestep upgrade, under activation/deact units is not handling AMF 
node DN.
if given it throws an error saying DN should be of type SU or COMP,log snippet
 given below 
=====
ER SmfUpgradeProcedure::getNodeForCompSu:The DN does not refere to a  SaAmfSUT 
or SaAmfComp class, DN=safAmfNode=PL-3,safAmfCluster=myAmfCluster
=====

If it is a constraint not allowing Amf Node, please capture it in some 
documentation.

Snippets of campaign xml and log
================================
<forAddRemove>
   <deactivationUnit>
     <actedOn>
       <byName objectDN="safAmfNode=PL-3,safAmfCluster=myAmfCluster"></byName>
       <byName 
objectDN="safSu=dummy_NWay_1Norm_1,safSg=SG_dummy_n,safApp=N"></byName>
=============

=================
Jul 15 15:21:24 SLES1 osafsmfd[11544]: NO PROC: Start upgrade procedure 
safSmfProc=amfClusterProc-1
Jul 15 15:21:24 SLES1 osafsmfd[11544]: NO PROC: Start procedure init actions
Jul 15 15:21:24 SLES1 osafsmfd[11544]: ER 
SmfUpgradeProcedure::getNodeForCompSu:The DN does not refere to a  SaAmfSUT or 
SaAmfComp class, DN=safAmfNode=PL-3,safAmfCluster=myAmfCluster
Jul 15 15:21:24 SLES1 osafsmfd[11544]: NO PROC: Procedure init actions completed
Jul 15 15:21:24 SLES1 osafsmfd[11544]: NO PROC: Start executing the steps
Jul 15 15:21:24 SLES1 osafsmfd[11544]: NO STEP: Executing AU lock step 
safSmfStep=1,safSmfProc=amfClusterProc-1,safSmfCampaign=campaign,safApp=safSmfService
Jul 15 15:21:24 SLES1 osafsmfd[11544]: NO STEP: Online installation of new 
software
==================


---

Sent from sourceforge.net because [email protected] is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to