- **status**: unassigned --> accepted
- **assigned_to**: Nagendra Kumar
---
** [tickets:#1116] AMF: SG unlock is allowed early but not lock**
**Status:** accepted
**Milestone:** 4.3.3
**Created:** Fri Sep 19, 2014 06:59 AM UTC by Hans Feldt
**Last Updated:** Fri Sep 19, 2014 06:59 AM UTC
**Owner:** Nagendra Kumar
A test case was allowed todo SG unlock early but the following lock failed with
BAD_OPERATION. This before the init_state goes to AVD_APP_STATE which it does
when the cluster startup timer expires. We should have consistency here. If
unlock is allowed, lock should be. Or unlock should return TRYAGAIN in the non
AVD_APP_STATE.
---
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.
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
