- **summary**: AMF: Rollback admin shutdown SI operation if node failover -->
AMF: Rollback admin shutdown/lock SI operation if node failover
- **Type**: discussion --> defect
- **Milestone**: 5.2.FC --> future
---
** [tickets:#2133] AMF: Rollback admin shutdown/lock SI operation if node
failover**
**Status:** unassigned
**Milestone:** future
**Created:** Thu Oct 20, 2016 06:49 PM UTC by Minh Hon Chau
**Last Updated:** Thu Nov 10, 2016 06:36 AM UTC
**Owner:** nobody
In scenario of shut down SI, delay QUIESCING csi callback, then reboot the node
that hosting SU having pending this csi callback. The result of this operation
looks differently between SGs
- For 2N: the SI Admin state is rollbacked to UNLOCK
- For Nway: the SI Admin state moves to LOCKED
- In NpM: Haven't tested just browsing SG_NPM::node_fail_si_oper, looks SI
Admin states rollbacks to UNLOCK
My question is whether the result of these scenario should be consistent? And
what's the expected outcome?
Also, the handling of node_fail_si_oper for admin lock is not consistent. For
2N, Admin state remains LOCKED, NpM rollbacks to UNLOCK
---
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.
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
