One more observation:

Though the clmna components are in uninstantiated state, csi assignments are 
showing as "Ready for assignment" for the saAmfCSICompHAReadinessState.
Please find the snippet below:

=================
safCSIComp=safComp=CLMNA\,safSu=SC-2\,safSg=NoRed\,safApp=OpenSAF,safCsi=CLMNA,safSi=NoRed1,safApp=OpenSAF
        saAmfCSICompHAState=ACTIVE(1)
        saAmfCSICompHAReadinessState=READY_FOR_ASSIGNMENT(1)
safCSIComp=safComp=CLMNA\,safSu=SC-1\,safSg=NoRed\,safApp=OpenSAF,safCsi=CLMNA,safSi=NoRed2,safApp=OpenSAF
        saAmfCSICompHAState=ACTIVE(1)
        saAmfCSICompHAReadinessState=READY_FOR_ASSIGNMENT(1)
safCSIComp=safComp=CLMNA\,safSu=PL-4\,safSg=NoRed\,safApp=OpenSAF,safCsi=CLMNA,safSi=NoRed3,safApp=OpenSAF
        saAmfCSICompHAState=ACTIVE(1)
        saAmfCSICompHAReadinessState=READY_FOR_ASSIGNMENT(1)
safCSIComp=safComp=CLMNA\,safSu=PL-3\,safSg=NoRed\,safApp=OpenSAF,safCsi=CLMNA,safSi=NoRed4,safApp=OpenSAF
        saAmfCSICompHAState=ACTIVE(1)
        saAmfCSICompHAReadinessState=READY_FOR_ASSIGNMENT(1)
=================

Logs could be referred from the files attached referred earlier.


---

** [tickets:#743] Newly added middleware component is not instantiated state 
after upgrade**

**Status:** review
**Created:** Thu Jan 23, 2014 12:14 PM UTC by Hrishikesh
**Last Updated:** Fri Jan 24, 2014 06:24 AM UTC
**Owner:** Nagendra Kumar

Configuration:
Opensaf 4.2 Changeset 3796 is running on 4 node SLES11 64bit cluster.

Opensaf 4.4 rpms are built with CS 4733 along with patches for ticket# 597 & 
ticket# 691.  For ticket #691, the changesets 4779 & 4783 are included.

The campaign.xml for the upgrade is attached.

In the campaign_complete_script.sh for the ProcWrapup Phase, included the logic 
for adding clmna comp & its csi's

Triggered the campaign to upgrade from Opensaf 4.2 to Opensaf 4.4.

Upgrade was successful, Opensaf 4.4 was installed &  running on all the nodes.
But clmna component states (Presence, Operation & Readiness states are as shown 
below:

======================
safComp=CLMNA,safSu=SC-1,safSg=NoRed,safApp=OpenSAF
        saAmfCompOperState=DISABLED(2)
        saAmfCompPresenceState=UNINSTANTIATED(1)
        saAmfCompReadinessState=OUT-OF-SERVICE(1)
safComp=CLMNA,safSu=SC-2,safSg=NoRed,safApp=OpenSAF
        saAmfCompOperState=DISABLED(2)
        saAmfCompPresenceState=UNINSTANTIATED(1)
        saAmfCompReadinessState=OUT-OF-SERVICE(1)
safComp=CLMNA,safSu=PL-3,safSg=NoRed,safApp=OpenSAF
        saAmfCompOperState=DISABLED(2)
        saAmfCompPresenceState=UNINSTANTIATED(1)
        saAmfCompReadinessState=OUT-OF-SERVICE(1)
safComp=CLMNA,safSu=PL-4,safSg=NoRed,safApp=OpenSAF
        saAmfCompOperState=DISABLED(2)
        saAmfCompPresenceState=UNINSTANTIATED(1)
        saAmfCompReadinessState=OUT-OF-SERVICE(1)
======================

Logs are attached.




---

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.
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to