changeset: 8590:0355138c830d
branch: opensaf-5.0.x
parent: 8580:66ec2284f5d4
user: Gary Lee <[email protected]>
date: Fri Feb 17 17:33:44 2017 +1100
summary: amfd: do not assert on saAmfSUMaintenanceCampaign modification
[#2305]
changeset: 8589:f407d2c67c2f
branch: opensaf-5.1.x
parent: 8581:e0b4efdf79af
user: Gary Lee <[email protected]>
date: Fri Feb 17 16:58:16 2017 +1100
summary: amfd: do not assert on saAmfSUMaintenanceCampaign modification
[#2305]
changeset: 8588:19fffa5c9aa5
user: Gary Lee <[email protected]>
date: Fri Feb 17 16:45:52 2017 +1100
summary: amfd: do not assert on saAmfSUMaintenanceCampaign modification
[#2305]
---
** [tickets:#2305] amfd: saAmfSUMaintenanceCampaign assertion **
**Status:** review
**Milestone:** 5.0.2
**Created:** Tue Feb 14, 2017 06:04 AM UTC by Gary Lee
**Last Updated:** Wed Feb 15, 2017 02:22 AM UTC
**Owner:** Gary Lee
Feb 10 03:58:50 SC-1 osafamfd[4874]:
../../../../../../../opensaf/osaf/services/saf/amf/amfd/su.cc:1872:
su_ccb_apply_modify_hdlr: Assertion 'su->saAmfSUMaintenanceCampaign.empty() ==
true' failed.
Someone could do this and cause a 'crash':
immcfg
immcfg -a saAmfSUMaintenanceCampaign=Foo1 safSu=SU1,safSg=SG1,safApp=App1
immcfg -a saAmfSUMaintenanceCampaign=Foo2 safSu=SU1,safSg=SG1,safApp=App1
control-d
AMF director should probably just log a WARNING instead of asserting.
---
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.
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
