- Description has changed:

Diff:

~~~~

--- old
+++ new
@@ -1,4 +1,4 @@
-ticket [#2145] looks to be causing this issue. 
+ticket #2145 looks to be causing this issue. 
 
 coredump printout is attached.
 

~~~~

- **Comment**:

The following is the analysis:
1. From the FIGURE 7 from SMF AIS spec, async-failure is supported in the 
following campaign state:
SA_SMF_CMPG_EXECUTING
SA_SMF_CMPG_SUSPENDING_EXECUTION
SA_SMF_CMPG_ROLLING_BACK

>From the campaign perspective mark the campaign as 
>SA_SMF_CMPG_SUSPENDED_BY_ERROR_DETECTED only when
the present campaign state is one of the above. This will avoid smfd 
segmentation fault.

2. But, the saAmfSUMaintenanceCampaign will be reset(cleared) at the time of 
committing the campaign, the same has been said in section 4.2.1.3 of SMF AIS.

"When an upgrade campaign is committed, the Software Management Framework
must reset all the maintenance status attributes that refer to the campaign 
being committed.
Beyond this point, it cannot determine whether a failed entity was upgraded
by the campaign or not."

when the component is failed, in the states other than above states(like 
SA_SMF_CMPG_EXECUTION_COMPLETED)
the amfnd will not restart, since saAmfSUMaintenanceCampaign is not yet reset. 
Ideally the failed component has to be reset
because the campaign will not be moved to error state.



---

** [tickets:#2413] smf: coredump, suspend is issued at completed state**

**Status:** unassigned
**Milestone:** 5.2.0
**Created:** Wed Apr 05, 2017 12:39 PM UTC by Rafael
**Last Updated:** Thu Apr 06, 2017 10:35 AM UTC
**Owner:** nobody
**Attachments:**

- 
[osafsmfd.9276.SC-2.core.txt](https://sourceforge.net/p/opensaf/tickets/2413/attachment/osafsmfd.9276.SC-2.core.txt)
 (15.4 kB; text/plain)


ticket #2145 looks to be causing this issue. 

coredump printout is attached.

Steps to reproduce: run a campaign and have AMF compenent fail at the campaign 
completed state. This triggers a event in SMF which tries to suspend a 
completed campaign.

Function handleAmfObjectStateChangeNotification will try to call asyncFailure() 
which is the same as suspend() because the campaign is completed and commited 
this is not a valid transition. The campaign state instance is most likely 
deleted therefore we get a coredump.

For reference refer to figures 5, 6, 7 in SMF AIS. Starting from section 5.1.3


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to