Raised to critical because this ticket means there could be systems out there
that have a corrupt imm database due to this problem.
Besides fixing the bug that this ticket reports we also needs some form
of audit that users could use to check for infection by the problem and
some means to correct it.
An audit is preferable to implement in immdump/pbe for several reasons.
It can be run off-line and it catches problems caused by either imm-ram
or imm-pbe. There exists an enhancement ticket for this #19.
Enhancement of course means it will be available as such in the next release.
But again by encapsulating it in the immdump/pbe tool such a tool could be
applied on files generated from older releases.
---
** [tickets:#1377] imm: IMM deletes object with NO_DANGLING reference**
**Status:** review
**Milestone:** 4.5.2
**Created:** Fri May 29, 2015 08:45 AM UTC by Zoran Milinkovic
**Last Updated:** Tue Jun 02, 2015 12:53 PM UTC
**Owner:** Hung Nguyen
In a certain case with bidirectional references between objects, IMM is able to
delete object with NO_DANGLING reference from another object.
- Case 1: IMM worked as expected and rejected the deletion
<pre>
SC-1:~ # immcfg -c TestClass testClassId=1
SC-1:~ # immcfg
> immcfg -c TestClass -a reference="testClassId=1" testClassId=2
> immcfg -a reference="testClassId=2" testClassId=1
>(Ctrl+D)
{Note that the above object-create and object-modify have to occur in the same
CCB.
This is to simulate the actions when creating objects with bidirectional
associations}
SC-1:~ # immcfg -d testClassId=2
error - saImmOmCcbApply FAILED: SA_AIS_ERR_FAILED_OPERATION (21)
SC-1:~ # immcfg -d testClassId=1
error - saImmOmCcbApply FAILED: SA_AIS_ERR_FAILED_OPERATION (21)
SC-1:~ #
</pre>
*syslog messages*
..........
May 27 04:01:48 SC-1 osafimmnd[4671]: ER ERR_FAILED_OPERATION: Delete of object
testClassId=2 would violate NO_DANGLING reference from object testClassId=1,
not scheduled for delete by this Ccb:58
May 27 04:01:48 SC-1 osafimmnd[4671]: NO Ccb 58 ABORTED (immcfg_SC-1_13712)
May 27 04:01:51 SC-1 osafimmnd[4671]: ER ERR_FAILED_OPERATION: Delete of object
testClassId=1 would violate NO_DANGLING reference from object testClassId=2,
not scheduled for delete by this Ccb:59
May 27 04:01:51 SC-1 osafimmnd[4671]: NO Ccb 59 ABORTED (immcfg_SC-1_13715)
..........
- Case 2: IMM worked unexpectedly and approved the deletion
<pre>
SC-1:~ # immcfg -c TestClass testClassId=2
SC-1:~ # immcfg
> immcfg -c TestClass -a reference="testClassId=2" testClassId=1
> immcfg -a reference="testClassId=1" testClassId=2
> (Ctrl+D)
{Note that the above object-create and object-modify have to occur in the same
CCB.
This is to simulate the actions when creating objects with bidirectional
associations}
SC-1:~ # immcfg -d testClassId=1
SC-1:~ # immfind | grep testClass
testClassId=2
SC-1:~ #
</pre>
*syslog messages*
..........
May 27 04:20:58 SC-1 osafimmnd[4671]: NO Ccb 73 COMMITTED (immcfg_SC-1_14511)
..........
---
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.------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
