[tickets] [opensaf:tickets] #1934 amf: amfd fail-overs su to failed node during node-switchover recovery.

[Praveen]

- **status**: review --> fixed
- **Comment**:

changeset:   8291:578552651e82
branch:  opensaf-5.0.x
user:Praveen Malviya 
date:Wed Nov 09 12:04:56 2016 +0530
summary: amfd: mark all SUs OOS on failed node before nodeswitchover 
recovery[#1934]

changeset:   8292:a029795d9845
branch:  opensaf-5.1.x
parent:  8289:e174c5b17b91
user:Praveen Malviya 
date:Wed Nov 09 12:05:13 2016 +0530
summary: amfd: mark all SUs OOS on failed node before nodeswitchover 
recovery[#1934]

changeset:   8293:135eb53abf6f
tag: tip
parent:  8288:af327247583f
user:Praveen Malviya 
date:Wed Nov 09 12:05:25 2016 +0530
summary: amfd: mark all SUs OOS on failed node before nodeswitchover 
recovery[#1934]

[staging:578552]
[staging:a02979]
[staging:135eb5]




---

** [tickets:#1934] amf: amfd fail-overs su to failed node during 
node-switchover recovery. **

**Status:** fixed
**Milestone:** 5.0.2
**Created:** Thu Aug 04, 2016 11:46 AM UTC by Praveen
**Last Updated:** Tue Sep 20, 2016 06:00 PM UTC
**Owner:** Praveen
**Attachments:**

- 
[nodeswitch.xml](https://sourceforge.net/p/opensaf/tickets/1934/attachment/nodeswitch.xml)
 (11.1 kB; text/xml)


Conf: 
Two SUs hosted on standby controller with 2N model. Recovery is 
node-switchover with su-failover flag enabled for SU1.

Steps to reproduce:
1)Bring attached configuration up. 
2) kill comp in SU1(active SU).

When AMFD gets recovery request for standby SC, it failovers SU1 and gives 
active to SU2 as a part of SU1 recovery. For SU2 recovery, it then sends 
quiesced assignment. This is a wrong sequence. Since SU2 is hosted on failed 
node, AMFD should not failover SU1 to SU2,

>From code perpective: AMFD marks all SUs of failed node OOS only in INIT_DONE 
>state. In APP_STATE this needs to be done by respective reocovery funtion. In 
>case of node-failvoer recovery avd_node_down_appl_susi_failover() is marking 
>SUs OOS before performing failover. But perform_nodeswitchover_recovery() is 
>not marking all the SUs OOS before performing failover/switchover of any SU.



---

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

[tickets] [opensaf:tickets] #1934 amf: amfd fail-overs su to failed node during node-switchover recovery.

[Anders Widell]

- **Milestone**: 4.7.2 --> 5.0.2



---

** [tickets:#1934] amf: amfd fail-overs su to failed node during 
node-switchover recovery. **

**Status:** review
**Milestone:** 5.0.2
**Created:** Thu Aug 04, 2016 11:46 AM UTC by Praveen
**Last Updated:** Fri Aug 26, 2016 12:54 PM UTC
**Owner:** Praveen
**Attachments:**

- 
[nodeswitch.xml](https://sourceforge.net/p/opensaf/tickets/1934/attachment/nodeswitch.xml)
 (11.1 kB; text/xml)


Conf: 
Two SUs hosted on standby controller with 2N model. Recovery is 
node-switchover with su-failover flag enabled for SU1.

Steps to reproduce:
1)Bring attached configuration up. 
2) kill comp in SU1(active SU).

When AMFD gets recovery request for standby SC, it failovers SU1 and gives 
active to SU2 as a part of SU1 recovery. For SU2 recovery, it then sends 
quiesced assignment. This is a wrong sequence. Since SU2 is hosted on failed 
node, AMFD should not failover SU1 to SU2,

>From code perpective: AMFD marks all SUs of failed node OOS only in INIT_DONE 
>state. In APP_STATE this needs to be done by respective reocovery funtion. In 
>case of node-failvoer recovery avd_node_down_appl_susi_failover() is marking 
>SUs OOS before performing failover. But perform_nodeswitchover_recovery() is 
>not marking all the SUs OOS before performing failover/switchover of any SU.



---

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.--
___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1934 amf: amfd fail-overs su to failed node during node-switchover recovery.

[Praveen]

- **status**: accepted --> review



---

** [tickets:#1934] amf: amfd fail-overs su to failed node during 
node-switchover recovery. **

**Status:** review
**Milestone:** 4.7.2
**Created:** Thu Aug 04, 2016 11:46 AM UTC by Praveen
**Last Updated:** Thu Aug 04, 2016 11:54 AM UTC
**Owner:** Praveen
**Attachments:**

- 
[nodeswitch.xml](https://sourceforge.net/p/opensaf/tickets/1934/attachment/nodeswitch.xml)
 (11.1 kB; text/xml)


Conf: 
Two SUs hosted on standby controller with 2N model. Recovery is 
node-switchover with su-failover flag enabled for SU1.

Steps to reproduce:
1)Bring attached configuration up. 
2) kill comp in SU1(active SU).

When AMFD gets recovery request for standby SC, it failovers SU1 and gives 
active to SU2 as a part of SU1 recovery. For SU2 recovery, it then sends 
quiesced assignment. This is a wrong sequence. Since SU2 is hosted on failed 
node, AMFD should not failover SU1 to SU2,

>From code perpective: AMFD marks all SUs of failed node OOS only in INIT_DONE 
>state. In APP_STATE this needs to be done by respective reocovery funtion. In 
>case of node-failvoer recovery avd_node_down_appl_susi_failover() is marking 
>SUs OOS before performing failover. But perform_nodeswitchover_recovery() is 
>not marking all the SUs OOS before performing failover/switchover of any SU.



---

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.--
___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1934 amf: amfd fail-overs su to failed node during node-switchover recovery.

[Praveen]

Active AMFD trace and messages from standby controller.


Attachments:

- 
[messages](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/926ad9ce/fa78/attachment/messages)
 (10.9 kB; application/octet-stream)
- 
[osafamfd](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/926ad9ce/fa78/attachment/osafamfd)
 (1.6 MB; application/octet-stream)


---

** [tickets:#1934] amf: amfd fail-overs su to failed node during 
node-switchover recovery. **

**Status:** accepted
**Milestone:** 4.7.2
**Created:** Thu Aug 04, 2016 11:46 AM UTC by Praveen
**Last Updated:** Thu Aug 04, 2016 11:47 AM UTC
**Owner:** Praveen
**Attachments:**

- 
[nodeswitch.xml](https://sourceforge.net/p/opensaf/tickets/1934/attachment/nodeswitch.xml)
 (11.1 kB; text/xml)


Conf: 
Two SUs hosted on standby controller with 2N model. Recovery is 
node-switchover with su-failover flag enabled for SU1.

Steps to reproduce:
1)Bring attached configuration up. 
2) kill comp in SU1(active SU).

When AMFD gets recovery request for standby SC, it failovers SU1 and gives 
active to SU2 as a part of SU1 recovery. For SU2 recovery, it then sends 
quiesced assignment. This is a wrong sequence. Since SU2 is hosted on failed 
node, AMFD should not failover SU1 to SU2,

>From code perpective: AMFD marks all SUs of failed node OOS only in INIT_DONE 
>state. In APP_STATE this needs to be done by respective reocovery funtion. In 
>case of node-failvoer recovery avd_node_down_appl_susi_failover() is marking 
>SUs OOS before performing failover. But perform_nodeswitchover_recovery() is 
>not marking all the SUs OOS before performing failover/switchover of any SU.



---

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.--
___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1934 amf: amfd fail-overs su to failed node during node-switchover recovery.

[Praveen]

- **status**: unassigned --> accepted
- **assigned_to**: Praveen



---

** [tickets:#1934] amf: amfd fail-overs su to failed node during 
node-switchover recovery. **

**Status:** accepted
**Milestone:** 4.7.2
**Created:** Thu Aug 04, 2016 11:46 AM UTC by Praveen
**Last Updated:** Thu Aug 04, 2016 11:46 AM UTC
**Owner:** Praveen
**Attachments:**

- 
[nodeswitch.xml](https://sourceforge.net/p/opensaf/tickets/1934/attachment/nodeswitch.xml)
 (11.1 kB; text/xml)


Conf: 
Two SUs hosted on standby controller with 2N model. Recovery is 
node-switchover with su-failover flag enabled for SU1.

Steps to reproduce:
1)Bring attached configuration up. 
2) kill comp in SU1(active SU).

When AMFD gets recovery request for standby SC, it failovers SU1 and gives 
active to SU2 as a part of SU1 recovery. For SU2 recovery, it then sends 
quiesced assignment. This is a wrong sequence. Since SU2 is hosted on failed 
node, AMFD should not failover SU1 to SU2,

>From code perpective: AMFD marks all SUs of failed node OOS only in INIT_DONE 
>state. In APP_STATE this needs to be done by respective reocovery funtion. In 
>case of node-failvoer recovery avd_node_down_appl_susi_failover() is marking 
>SUs OOS before performing failover. But perform_nodeswitchover_recovery() is 
>not marking all the SUs OOS before performing failover/switchover of any SU.



---

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.--
___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1934 amf: amfd fail-overs su to failed node during node-switchover recovery.

[Praveen]

---

** [tickets:#1934] amf: amfd fail-overs su to failed node during 
node-switchover recovery. **

**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Thu Aug 04, 2016 11:46 AM UTC by Praveen
**Last Updated:** Thu Aug 04, 2016 11:46 AM UTC
**Owner:** nobody
**Attachments:**

- 
[nodeswitch.xml](https://sourceforge.net/p/opensaf/tickets/1934/attachment/nodeswitch.xml)
 (11.1 kB; text/xml)


Conf: 
Two SUs hosted on standby controller with 2N model. Recovery is 
node-switchover with su-failover flag enabled for SU1.

Steps to reproduce:
1)Bring attached configuration up. 
2) kill comp in SU1(active SU).

When AMFD gets recovery request for standby SC, it failovers SU1 and gives 
active to SU2 as a part of SU1 recovery. For SU2 recovery, it then sends 
quiesced assignment. This is a wrong sequence. Since SU2 is hosted on failed 
node, AMFD should not failover SU1 to SU2,

>From code perpective: AMFD marks all SUs of failed node OOS only in INIT_DONE 
>state. In APP_STATE this needs to be done by respective reocovery funtion. In 
>case of node-failvoer recovery avd_node_down_appl_susi_failover() is marking 
>SUs OOS before performing failover. But perform_nodeswitchover_recovery() is 
>not marking all the SUs OOS before performing failover/switchover of any SU.



---

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.--
___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets