During headless state, escalataion are reduced to "Restart or Reboot". I think
titile of this ticket should be more generic like "support all escalation
policies during headless state" because it would require considerable changes
at AMFD to handle assignments specially in recovery policies like
comp-failover, node-switchover etc where transient quiesced state will be
involved after fault occurs.
Another interesting case is when recovery policy like node-failover and
node-switchover is configuered but node auto repair is disabled
(saAmfNodeAutoRepar=false). Node cannot be rebooted, In such a case what will
be the fate of such a failed node after headless state. After headless, AMFD
will have to failover all the assignments from this failed node. But for this
AMFND should not delete SUSIs after cleaning up the components.
---
** [tickets:#1902] AMF: Remove node reboot if su/comp failover during headless**
**Status:** unassigned
**Milestone:** 5.1.FC
**Created:** Wed Jun 29, 2016 12:02 PM UTC by Minh Hon Chau
**Last Updated:** Wed Jun 29, 2016 12:02 PM UTC
**Owner:** nobody
If a comp/su failover occurs during headless, amfnd will escalate to reboot.
This will unexpectedly impact on other comp/su which are up and running if
there's no node failover escalation configured on this faulty comp/su
2016-06-29 21:30:07 PL-4 osafamfnd[429]: NO
'safComp=AmfDemo2,safSu=SU4,safSg=AmfDemoTwon,safApp=AmfDemoTwon' faulted due
to 'avaDown' : Recovery is 'suFailover'
2016-06-29 21:30:07 PL-4 osafamfnd[429]: NO Terminating components of
'safSu=SU4,safSg=AmfDemoTwon,safApp=AmfDemoTwon'(abruptly & unordered)
2016-06-29 21:30:07 PL-4 osafamfnd[429]: NO
'safSu=SU4,safSg=AmfDemoTwon,safApp=AmfDemoTwon' Presence State INSTANTIATED =>
TERMINATING
2016-06-29 21:30:07 PL-4 osafamfnd[429]: NO
'safSu=SU4,safSg=AmfDemoTwon,safApp=AmfDemoTwon' Presence State TERMINATING =>
TERMINATING
2016-06-29 21:30:07 PL-4 osafamfnd[429]: NO
'safSu=SU4,safSg=AmfDemoTwon,safApp=AmfDemoTwon' Presence State TERMINATING =>
TERMINATING
2016-06-29 21:30:07 PL-4 osafamfnd[429]: Rebooting OpenSAF NodeId = 132111 EE
Name = , Reason: Can't perform recovery while controllers are down. Recovery is
node failfast., OwnNodeId = 132111, SupervisionTime = 60
2016-06-29 21:30:07 PL-4 opensaf_reboot: Rebooting local node; timeout=60
This ticket will remove unexpected reboot due to failover during headless which
is mentioned as limitation in AMF opensaf documentation.
---
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.
------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
