The problem exists in 4.7.
The error printout in 4.7 does not exist anymore, since the implementation of
SmfUpgradeProcedure changed between 4.3 and 4.7.
Test results soo far in 4.7:
-"forModify": works
-"forAddRemove": seems to work when the deact/act are in the same procedure:
<upgradeScope>
<forAddRemove>
<deactivationUnit>
<actedOn>
<byName
objectDN="safAmfNode=SC-1,safAmfCluster=myAmfCluster"/>
<byName
objectDN="safAmfNode=SC-2,safAmfCluster=myAmfCluster"/>
</actedOn>
<swRemove bundleDN="safSmfBundle=7.7.7"
pathnamePrefix="/opt/amf_demo"/>
</deactivationUnit>
<activationUnit>
<actedOn>
<byName
objectDN="safAmfNode=SC-1,safAmfCluster=myAmfCluster"/>
<byName
objectDN="safAmfNode=SC-2,safAmfCluster=myAmfCluster"/>
</actedOn>
<swAdd bundleDN="safSmfBundle=9.9.9"
pathnamePrefix="/opt/amf_demo"/>
</activationUnit>
</forAddRemove>
</upgradeScope>
-"forAddRemove": when deact/act are in 2 separate procedures:
Apr 29 07:24:58 SC-1 osafsmfd[514]: NO SmfUpgradeProcedure::createImmStep: No
node given for bundle safSmfBundle=7.7.7
Apr 29 07:24:58 SC-1 osafsmfd[514]: NO SmfUpgradeProcedure::createImmSteps:
creation of SaSmfStep object structure fails, rc=SA_AIS_ERR_NOT_EXIST (12)
Apr 29 07:24:58 SC-1 osafsmfd[514]: NO
SmfProcStateInitial::executeInit:createImmSteps in IMM failes
Apr 29 07:24:58 SC-1 osafsmfd[514]: NO CAMP: Procedure
safSmfProc=SingleStepCompForAddRemoveByName_nodeUnlock returned FAILED
In "SmfUpgradeProcedure::calculateSingleStep" at activate case the "nodeList"
is not populated with nodes, because no node found.
(and later: no swNodes added to the created step object using "addSwNodes")
Node(s) found in deact case since it uses the method "getActDeactUnitsAndNodes"
to get the node.
Node(s) not found in act case since it uses the method "getNodeForCompSu" to
get the node, and in that case the input DN must be:
if ((i_objectDn == (*objit).second.suDN) || (i_objectDn ==
(*objit).second.compDN)) {
return (*objit).second.nodeDN;
}
which will never happen if dn object is an SaAmfNode instance.
Next step of the investigation could be to check if
the above campaign part is valid at all (both cases when deact/act are in same
or in separate procedures).
---
** [tickets:#960] Activation/Deact units didnot allow amf node dn in single
step upgrade.**
**Status:** assigned
**Milestone:** 4.7-Tentative
**Created:** Wed Jul 16, 2014 06:38 AM UTC by Hrishikesh
**Last Updated:** Wed Apr 15, 2015 11:35 AM 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
