date:20221010

[tickets] [opensaf:tickets] #3299 immnd: unexpected reboot node after merge network back

2022-10-10 Thread Thien Minh Huynh via Opensaf-tickets

- **status**: assigned --> not-reproducible



---

** [tickets:#3299] immnd: unexpected reboot node  after merge network back**

**Status:** not-reproducible
**Milestone:** 5.22.11
**Created:** Wed Dec 01, 2021 03:07 AM UTC by Huu The Truong
**Last Updated:** Tue Oct 11, 2022 05:37 AM UTC
**Owner:** Huu The Truong


Split network into two partitions. On each partition, create a dummy object.
During merge network back has happened twice the reboot node.

The first reboot node:
2021-09-07 12:20:06.926 SC-7 osafimmnd[376]: NO Used to be on another 
partition. Rebooting...
2021-09-07 12:20:06.935 SC-7 osafamfnd[431]: NO AVD NEW_ACTIVE, adest:1
2021-09-07 12:20:06.935 SC-7 osafimmnd[376]: Quick local node rebooting, 
Reason: Used to be on another partition. Rebooting...
2021-09-07 12:20:06.952 SC-7 opensaf_reboot: Do quick local node reboot

At the second, this reboot is unexpected:
2021-09-07 12:20:11.963 SC-7 osafimmnd[376]: NO Used to be on another 
partition. Rebooting...
2021-09-07 12:20:11.963 SC-7 osafimmnd[376]: Quick local node rebooting, 
Reason: Used to be on another partition. Rebooting...
2021-09-07 12:20:11.989 SC-7 osafclmna[333]: NO 
safNode=SC-7,safCluster=myClmCluster Joined cluster, nodeid=2070f
2021-09-07 12:20:11.992 SC-7 opensaf_reboot: Do quick local node reboot
2021-09-07 12:20:12.022 SC-7 opensafd[305]: ER Service RDE has unexpectedly 
crashed. Unable to continue, exiting


---

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] #3299 immnd: unexpected reboot node after merge network back

2022-10-10 Thread Thien Minh Huynh via Opensaf-tickets

Hi Mohan,

On behalf of Huu, I would like to share some information on the issue. 
The issue occurs when the network is split into partitions: 
partition1 = [SC-1, SC-2, SC-3, SC-4, SC-5]
partition2 = [SC-6, SC-7, SC-8, SC-9, SC-10]
I am not able to reproduce the issue. And the issue has not been seen again in 
a long time. I will close ticket as not reproduce.

Best Regards,
Thien


---

** [tickets:#3299] immnd: unexpected reboot node  after merge network back**

**Status:** assigned
**Milestone:** 5.22.11
**Created:** Wed Dec 01, 2021 03:07 AM UTC by Huu The Truong
**Last Updated:** Fri Oct 07, 2022 05:30 PM UTC
**Owner:** Huu The Truong


Split network into two partitions. On each partition, create a dummy object.
During merge network back has happened twice the reboot node.

The first reboot node:
2021-09-07 12:20:06.926 SC-7 osafimmnd[376]: NO Used to be on another 
partition. Rebooting...
2021-09-07 12:20:06.935 SC-7 osafamfnd[431]: NO AVD NEW_ACTIVE, adest:1
2021-09-07 12:20:06.935 SC-7 osafimmnd[376]: Quick local node rebooting, 
Reason: Used to be on another partition. Rebooting...
2021-09-07 12:20:06.952 SC-7 opensaf_reboot: Do quick local node reboot

At the second, this reboot is unexpected:
2021-09-07 12:20:11.963 SC-7 osafimmnd[376]: NO Used to be on another 
partition. Rebooting...
2021-09-07 12:20:11.963 SC-7 osafimmnd[376]: Quick local node rebooting, 
Reason: Used to be on another partition. Rebooting...
2021-09-07 12:20:11.989 SC-7 osafclmna[333]: NO 
safNode=SC-7,safCluster=myClmCluster Joined cluster, nodeid=2070f
2021-09-07 12:20:11.992 SC-7 opensaf_reboot: Do quick local node reboot
2021-09-07 12:20:12.022 SC-7 opensafd[305]: ER Service RDE has unexpectedly 
crashed. Unable to continue, exiting


---

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] #2468 amf: amfd asserts while decrementing opensaf NoRed SI assignment counter during fail-over.

2022-10-10 Thread Anand Sundararaj via Opensaf-tickets

- **status**: accepted --> needinfo
- **Comment**:

Hi Jianfeng,
Could you reproduce it on latest OpenSAF and share the logs?
Anand
High Availability Solutions



---

** [tickets:#2468] amf: amfd asserts while decrementing opensaf NoRed SI 
assignment counter during fail-over.**

**Status:** needinfo
**Milestone:** future
**Created:** Thu May 25, 2017 08:46 AM UTC by Praveen
**Last Updated:** Mon Oct 10, 2022 12:34 PM UTC
**Owner:** Anand Sundararaj


Ticket is based on a issue reported via user list mail dated: 22-May-17, 
subject  "[users] osafamfd coredump issue.


Here is syslog when the issue occurred:

2017-05-01T07:52:57.714906-04:00 scm2 kernel: tipc: Resetting link 
<1.1.16:eth2-1.1.5:bond0>, peer not responding

2017-05-01T07:52:57.714935-04:00 scm2 kernel: tipc: Lost link 
<1.1.16:eth2-1.1.5:bond0> on network plane A

2017-05-01T07:52:57.714939-04:00 scm2 kernel: tipc: Lost contact with <1.1.5>

2017-05-01T07:52:57.716788-04:00 scm2 osafimmd[3009]: NO MDS event from svc_id 
25 (change:4, dest:287038266327043)

2017-05-01T07:52:57.717304-04:00 scm2 osafclmd[4259]: NO Node 66831 went down. 
Not sending track callback for agents on that node

2017-05-01T07:52:57.719178-04:00 scm2 osafimmnd[3020]: NO Global discard node 
received for nodeId:1050f pid:15395

2017-05-01T07:52:57.719233-04:00 scm2 osafimmnd[3020]: NO Implementer 
disconnected 104 <0, 1050f(down)> (MsgQueueService66831)

2017-05-01T07:52:57.721345-04:00 scm2 osafamfd[4277]: NO Node 'PLD0105' left 
the cluster

2017-05-01T07:52:57.722778-04:00 scm2 log_demo[6160]: [0.I.Proc]: FYI state 
change notification from NTF, entity PLD0105 now has new state DISABLED (Oper 
state safAmfNode=PLD0105,safAmfCluster=myAmfCluster changed)

2017-05-01T07:52:57.732796-04:00 scm2 osafamfd[4277]: su.cc:2006: 
dec_curr_act_si: Assertion 'saAmfSUNumCurrActiveSIs > 0' failed.

2017-05-01T07:52:57.778777-04:00 scm2 kernel: tipc: Resetting link 
<1.1.16:eth2-1.1.6:bond0>, peer not responding

2017-05-01T07:52:57.778827-04:00 scm2 kernel: tipc: Lost link 
<1.1.16:eth2-1.1.6:bond0> on network plane A

2017-05-01T07:52:57.778833-04:00 scm2 kernel: tipc: Lost contact with <1.1.6>

2017-05-01T07:52:57.777979-04:00 scm2 osafimmd[3009]: NO MDS event from svc_id 
25 (change:4, dest:288139774320643)

2017-05-01T07:52:57.717343-04:00 scm2 osafclmd[4259]: NO Node 66831 went down. 
Not sending track callback for agents on that node

2017-05-01T07:52:57.779373-04:00 scm2 osafclmd[4259]: NO Node 67087 went down. 
Not sending track callback for agents on that node

2017-05-01T07:52:57.780552-04:00 scm2 osafimmnd[3020]: NO Global discard node 
received for nodeId:1060f pid:17439

2017-05-01T07:52:57.780607-04:00 scm2 osafimmnd[3020]: NO Implementer 
disconnected 106 <0, 1060f(down)> (MsgQueueService67087)

2017-05-01T07:52:57.810785-04:00 scm2 osafamfnd[5281]: WA AMF director 
unexpectedly crashed

2017-05-01T07:52:57.810839-04:00 scm2 osafamfnd[5281]: Rebooting OpenSAF NodeId 
= 69647 EE Name = , Reason: local AVD down(Adest) or both AVD down(Vdest) 
received, OwnNodeId = 69647, SupervisionTime = 0

2017-05-01T07:52:57.810978-04:00 scm2 osafimmnd[3020]: NO Implementer locally 
disconnected. Marking it as doomed 105 <29, 1100f> (safAmfService)

2017-05-01T07:52:57.812582-04:00 scm2 osafimmnd[3020]: NO Implementer 
disconnected 105 <29, 1100f> (safAmfService)

2017-05-01T07:52:57.950567-04:00 scm2 opensaf_reboot: Rebooting local node; 
timeout=0

2017-05-01T07:52:58.084968-04:00 scm2 atwdog[28335]: rebooting (-f) local node



---

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] #2468 amf: amfd asserts while decrementing opensaf NoRed SI assignment counter during fail-over.

2022-10-10 Thread Anand Sundararaj via Opensaf-tickets

- **status**: assigned --> accepted



---

** [tickets:#2468] amf: amfd asserts while decrementing opensaf NoRed SI 
assignment counter during fail-over.**

**Status:** accepted
**Milestone:** future
**Created:** Thu May 25, 2017 08:46 AM UTC by Praveen
**Last Updated:** Mon Oct 10, 2022 12:33 PM UTC
**Owner:** Anand Sundararaj


Ticket is based on a issue reported via user list mail dated: 22-May-17, 
subject  "[users] osafamfd coredump issue.


Here is syslog when the issue occurred:

2017-05-01T07:52:57.714906-04:00 scm2 kernel: tipc: Resetting link 
<1.1.16:eth2-1.1.5:bond0>, peer not responding

2017-05-01T07:52:57.714935-04:00 scm2 kernel: tipc: Lost link 
<1.1.16:eth2-1.1.5:bond0> on network plane A

2017-05-01T07:52:57.714939-04:00 scm2 kernel: tipc: Lost contact with <1.1.5>

2017-05-01T07:52:57.716788-04:00 scm2 osafimmd[3009]: NO MDS event from svc_id 
25 (change:4, dest:287038266327043)

2017-05-01T07:52:57.717304-04:00 scm2 osafclmd[4259]: NO Node 66831 went down. 
Not sending track callback for agents on that node

2017-05-01T07:52:57.719178-04:00 scm2 osafimmnd[3020]: NO Global discard node 
received for nodeId:1050f pid:15395

2017-05-01T07:52:57.719233-04:00 scm2 osafimmnd[3020]: NO Implementer 
disconnected 104 <0, 1050f(down)> (MsgQueueService66831)

2017-05-01T07:52:57.721345-04:00 scm2 osafamfd[4277]: NO Node 'PLD0105' left 
the cluster

2017-05-01T07:52:57.722778-04:00 scm2 log_demo[6160]: [0.I.Proc]: FYI state 
change notification from NTF, entity PLD0105 now has new state DISABLED (Oper 
state safAmfNode=PLD0105,safAmfCluster=myAmfCluster changed)

2017-05-01T07:52:57.732796-04:00 scm2 osafamfd[4277]: su.cc:2006: 
dec_curr_act_si: Assertion 'saAmfSUNumCurrActiveSIs > 0' failed.

2017-05-01T07:52:57.778777-04:00 scm2 kernel: tipc: Resetting link 
<1.1.16:eth2-1.1.6:bond0>, peer not responding

2017-05-01T07:52:57.778827-04:00 scm2 kernel: tipc: Lost link 
<1.1.16:eth2-1.1.6:bond0> on network plane A

2017-05-01T07:52:57.778833-04:00 scm2 kernel: tipc: Lost contact with <1.1.6>

2017-05-01T07:52:57.777979-04:00 scm2 osafimmd[3009]: NO MDS event from svc_id 
25 (change:4, dest:288139774320643)

2017-05-01T07:52:57.717343-04:00 scm2 osafclmd[4259]: NO Node 66831 went down. 
Not sending track callback for agents on that node

2017-05-01T07:52:57.779373-04:00 scm2 osafclmd[4259]: NO Node 67087 went down. 
Not sending track callback for agents on that node

2017-05-01T07:52:57.780552-04:00 scm2 osafimmnd[3020]: NO Global discard node 
received for nodeId:1060f pid:17439

2017-05-01T07:52:57.780607-04:00 scm2 osafimmnd[3020]: NO Implementer 
disconnected 106 <0, 1060f(down)> (MsgQueueService67087)

2017-05-01T07:52:57.810785-04:00 scm2 osafamfnd[5281]: WA AMF director 
unexpectedly crashed

2017-05-01T07:52:57.810839-04:00 scm2 osafamfnd[5281]: Rebooting OpenSAF NodeId 
= 69647 EE Name = , Reason: local AVD down(Adest) or both AVD down(Vdest) 
received, OwnNodeId = 69647, SupervisionTime = 0

2017-05-01T07:52:57.810978-04:00 scm2 osafimmnd[3020]: NO Implementer locally 
disconnected. Marking it as doomed 105 <29, 1100f> (safAmfService)

2017-05-01T07:52:57.812582-04:00 scm2 osafimmnd[3020]: NO Implementer 
disconnected 105 <29, 1100f> (safAmfService)

2017-05-01T07:52:57.950567-04:00 scm2 opensaf_reboot: Rebooting local node; 
timeout=0

2017-05-01T07:52:58.084968-04:00 scm2 atwdog[28335]: rebooting (-f) local node



---

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] #2468 amf: amfd asserts while decrementing opensaf NoRed SI assignment counter during fail-over.

2022-10-10 Thread Anand Sundararaj via Opensaf-tickets

- **status**: unassigned --> assigned
- **assigned_to**: Anand Sundararaj



---

** [tickets:#2468] amf: amfd asserts while decrementing opensaf NoRed SI 
assignment counter during fail-over.**

**Status:** assigned
**Milestone:** future
**Created:** Thu May 25, 2017 08:46 AM UTC by Praveen
**Last Updated:** Wed Jan 09, 2019 09:52 PM UTC
**Owner:** Anand Sundararaj


Ticket is based on a issue reported via user list mail dated: 22-May-17, 
subject  "[users] osafamfd coredump issue.


Here is syslog when the issue occurred:

2017-05-01T07:52:57.714906-04:00 scm2 kernel: tipc: Resetting link 
<1.1.16:eth2-1.1.5:bond0>, peer not responding

2017-05-01T07:52:57.714935-04:00 scm2 kernel: tipc: Lost link 
<1.1.16:eth2-1.1.5:bond0> on network plane A

2017-05-01T07:52:57.714939-04:00 scm2 kernel: tipc: Lost contact with <1.1.5>

2017-05-01T07:52:57.716788-04:00 scm2 osafimmd[3009]: NO MDS event from svc_id 
25 (change:4, dest:287038266327043)

2017-05-01T07:52:57.717304-04:00 scm2 osafclmd[4259]: NO Node 66831 went down. 
Not sending track callback for agents on that node

2017-05-01T07:52:57.719178-04:00 scm2 osafimmnd[3020]: NO Global discard node 
received for nodeId:1050f pid:15395

2017-05-01T07:52:57.719233-04:00 scm2 osafimmnd[3020]: NO Implementer 
disconnected 104 <0, 1050f(down)> (MsgQueueService66831)

2017-05-01T07:52:57.721345-04:00 scm2 osafamfd[4277]: NO Node 'PLD0105' left 
the cluster

2017-05-01T07:52:57.722778-04:00 scm2 log_demo[6160]: [0.I.Proc]: FYI state 
change notification from NTF, entity PLD0105 now has new state DISABLED (Oper 
state safAmfNode=PLD0105,safAmfCluster=myAmfCluster changed)

2017-05-01T07:52:57.732796-04:00 scm2 osafamfd[4277]: su.cc:2006: 
dec_curr_act_si: Assertion 'saAmfSUNumCurrActiveSIs > 0' failed.

2017-05-01T07:52:57.778777-04:00 scm2 kernel: tipc: Resetting link 
<1.1.16:eth2-1.1.6:bond0>, peer not responding

2017-05-01T07:52:57.778827-04:00 scm2 kernel: tipc: Lost link 
<1.1.16:eth2-1.1.6:bond0> on network plane A

2017-05-01T07:52:57.778833-04:00 scm2 kernel: tipc: Lost contact with <1.1.6>

2017-05-01T07:52:57.777979-04:00 scm2 osafimmd[3009]: NO MDS event from svc_id 
25 (change:4, dest:288139774320643)

2017-05-01T07:52:57.717343-04:00 scm2 osafclmd[4259]: NO Node 66831 went down. 
Not sending track callback for agents on that node

2017-05-01T07:52:57.779373-04:00 scm2 osafclmd[4259]: NO Node 67087 went down. 
Not sending track callback for agents on that node

2017-05-01T07:52:57.780552-04:00 scm2 osafimmnd[3020]: NO Global discard node 
received for nodeId:1060f pid:17439

2017-05-01T07:52:57.780607-04:00 scm2 osafimmnd[3020]: NO Implementer 
disconnected 106 <0, 1060f(down)> (MsgQueueService67087)

2017-05-01T07:52:57.810785-04:00 scm2 osafamfnd[5281]: WA AMF director 
unexpectedly crashed

2017-05-01T07:52:57.810839-04:00 scm2 osafamfnd[5281]: Rebooting OpenSAF NodeId 
= 69647 EE Name = , Reason: local AVD down(Adest) or both AVD down(Vdest) 
received, OwnNodeId = 69647, SupervisionTime = 0

2017-05-01T07:52:57.810978-04:00 scm2 osafimmnd[3020]: NO Implementer locally 
disconnected. Marking it as doomed 105 <29, 1100f> (safAmfService)

2017-05-01T07:52:57.812582-04:00 scm2 osafimmnd[3020]: NO Implementer 
disconnected 105 <29, 1100f> (safAmfService)

2017-05-01T07:52:57.950567-04:00 scm2 opensaf_reboot: Rebooting local node; 
timeout=0

2017-05-01T07:52:58.084968-04:00 scm2 atwdog[28335]: rebooting (-f) local node



---

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] #2526 amfd: Command unlock nodegroup timeout if su failover is escalated (>= 2SIs)

2022-10-10 Thread Nagendra Kumar via Opensaf-tickets

Trying to reproduce it on latest OpenSAF.
Thanks
-Nagendra
High Availability Solutions(www.GetHighAvailability.com)


---

** [tickets:#2526] amfd: Command unlock nodegroup timeout if su failover is 
escalated (>= 2SIs)**

**Status:** accepted
**Milestone:** future
**Labels:** nodegroup timeout 
**Created:** Wed Jul 12, 2017 04:23 AM UTC by Minh Hon Chau
**Last Updated:** Mon Oct 10, 2022 12:20 PM UTC
**Owner:** Nagendra Kumar
**Attachments:**

- 
[app3_twon3su3si.xml](https://sourceforge.net/p/opensaf/tickets/2526/attachment/app3_twon3su3si.xml)
 (14.6 kB; text/xml)


- Configuration: 2N app, 3SI (model is attached), SU4/SU5 are hosted on PL4/PL5 
respectively
- Steps:
. Create nodegroup consists of PL4/PL5
. Unlock ng
. SU4 is assigned ACTIVE
. While component of SU5 is being assigned STANDBY, kill a component of SU4 to 
escalate to a SuFailover
. SU4 is now getting STANDBY assignment, SU5 is getting ACTIVE assignment
. But the command unlock ng is being hold until TIMEOUT

Note: Repeat the same test with only **1 SI**, the command unlock ng returns OK


---

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] #2526 amfd: Command unlock nodegroup timeout if su failover is escalated (>= 2SIs)

2022-10-10 Thread Nagendra Kumar via Opensaf-tickets

- **status**: assigned --> accepted



---

** [tickets:#2526] amfd: Command unlock nodegroup timeout if su failover is 
escalated (>= 2SIs)**

**Status:** accepted
**Milestone:** future
**Labels:** nodegroup timeout 
**Created:** Wed Jul 12, 2017 04:23 AM UTC by Minh Hon Chau
**Last Updated:** Mon Oct 10, 2022 12:19 PM UTC
**Owner:** Nagendra Kumar
**Attachments:**

- 
[app3_twon3su3si.xml](https://sourceforge.net/p/opensaf/tickets/2526/attachment/app3_twon3su3si.xml)
 (14.6 kB; text/xml)


- Configuration: 2N app, 3SI (model is attached), SU4/SU5 are hosted on PL4/PL5 
respectively
- Steps:
. Create nodegroup consists of PL4/PL5
. Unlock ng
. SU4 is assigned ACTIVE
. While component of SU5 is being assigned STANDBY, kill a component of SU4 to 
escalate to a SuFailover
. SU4 is now getting STANDBY assignment, SU5 is getting ACTIVE assignment
. But the command unlock ng is being hold until TIMEOUT

Note: Repeat the same test with only **1 SI**, the command unlock ng returns OK


---

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] #2526 amfd: Command unlock nodegroup timeout if su failover is escalated (>= 2SIs)

2022-10-10 Thread Nagendra Kumar via Opensaf-tickets

- **status**: unassigned --> assigned
- **assigned_to**: Nagendra Kumar



---

** [tickets:#2526] amfd: Command unlock nodegroup timeout if su failover is 
escalated (>= 2SIs)**

**Status:** assigned
**Milestone:** future
**Labels:** nodegroup timeout 
**Created:** Wed Jul 12, 2017 04:23 AM UTC by Minh Hon Chau
**Last Updated:** Wed Jan 09, 2019 09:43 PM UTC
**Owner:** Nagendra Kumar
**Attachments:**

- 
[app3_twon3su3si.xml](https://sourceforge.net/p/opensaf/tickets/2526/attachment/app3_twon3su3si.xml)
 (14.6 kB; text/xml)


- Configuration: 2N app, 3SI (model is attached), SU4/SU5 are hosted on PL4/PL5 
respectively
- Steps:
. Create nodegroup consists of PL4/PL5
. Unlock ng
. SU4 is assigned ACTIVE
. While component of SU5 is being assigned STANDBY, kill a component of SU4 to 
escalate to a SuFailover
. SU4 is now getting STANDBY assignment, SU5 is getting ACTIVE assignment
. But the command unlock ng is being hold until TIMEOUT

Note: Repeat the same test with only **1 SI**, the command unlock ng returns OK


---

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] #2074 amfd asserted on rebooted controllers continuoulsy after split brain scenario (headless)

2022-10-10 Thread Mohan Kanakam via Opensaf-tickets

I will try to reproduce it and will let you know if it is reproducible on the 
latest.
Though I have tested such scenarios before and I didn't get into such situation.
Thanks
Mohan
High Availability Solutions(www.GetHighAvailability.com)


---

** [tickets:#2074] amfd asserted on rebooted controllers continuoulsy after 
split brain scenario (headless)**

**Status:** accepted
**Milestone:** future
**Created:** Tue Sep 27, 2016 12:14 PM UTC by Srikanth R
**Last Updated:** Mon Oct 10, 2022 12:04 PM UTC
**Owner:** Mohan  Kanakam


Setup : 
SLES 11 Physical machine
Changeset :7997 5.1 FC
2 controllers and 2 payloads with headless feature enabled.
2N application with 3 SUs. (AmfDemo).

Issue :

amfd asserted on controllers  continuoulsy for every reboot after  initial 
split brain scenario is observed


Steps performed :

-> Initially brought up four nodes and all the nodes joined the cluster.

-> Brought up the 2N application, with SUs hosted on SC-1 ,SC-2 and PL-3 
successfully.

-> Performed some operations on the AMF objects and the cluster is left in idle 
state later.

-> After a gap of 2 weeks, MDS down event is generated on both the controllers 
for which spilt brain scenario is generated. Because of momentary cable(s) 
unplugging, MDS down event is generated.


Sep 24 21:36:40 SLES-SLOT1 osafimmd[2729]: NO MDS event from svc_id 25 
(change:3, dest:565214187380752)
Sep 24 21:36:40 SLES-SLOT1 kernel: [1297950.833811] TIPC: Established link 
<1.1.1:em1-1.1.2:em1> on network plane A
Sep 24 21:36:40 SLES-SLOT1 osafrded[2710]: Rebooting OpenSAF NodeId = 0 EE Name 
= No EE Mapped, Reason: Split-brain detected, OwnNodeId = 131343, 
SupervisionTime = 60


Sep 26 00:00:01 SLES-SLOT2 osafrded[2715]: NO Got peer info request from node 
0x2010f with role ACTIVE
Sep 26 00:00:01 SLES-SLOT2 osafrded[2715]: Rebooting OpenSAF NodeId = 0 EE Name 
= No EE Mapped, Reason: Split-brain detected, OwnNodeId = 131599, 
SupervisionTime = 60


-> As headless feature is enabled, payloads did not go for reboot.

-> Once controllers joined the payloads, amfd asserted on the rebooted 
controller and controllers went for reboot.
Sep 24 21:39:27 SLES-SLOT1 osafamfd[2772]: NO Received node_up from 2010f: 
msg_id 1
Sep 24 21:39:27 SLES-SLOT1 osafamfd[2772]: siass.cc:953: avd_susi_recreate: 
Assertion 'su' failed.
Sep 24 21:39:27 SLES-SLOT1 osafamfnd[2782]: WA AMF director unexpectedly crashed
Sep 24 21:39:27 SLES-SLOT1 osafamfnd[2782]: WA AMF director unexpectedly crashed
Sep 24 21:39:27 SLES-SLOT1 osafamfnd[2782]: Rebooting OpenSAF NodeId = 131343 
EE Name = , Reason: local AVD down(Adest) or both AVD down(Vdest) received, 
OwnNodeId = 131343, SupervisionTime = 60


Below is the backtrace :

#0  0x7f1d28510b55 in raise () from /lib64/libc.so.6
No symbol table info available.
#1  0x7f1d28512131 in abort () from /lib64/libc.so.6
No symbol table info available.
#2  0x7f1d2a397197 in __osafassert_fail (__file=0x517c15 "siass.cc", 
__line=953, __func=0x518250 
 
"avd_susi_recreate", 
__assertion=0x517d01 "su") at sysf_def.c:281
No locals.
#3  0x004c56a5 in avd_susi_recreate (info=0x7f1d20008ec8) at 
siass.cc:953
su = 0x0
__FUNCTION__ = "avd_susi_recreate"
susi = 0x0
node = 0x7bfdf0
susi_state = 0x0
su_state = 0x7f1d200055a0
__PRETTY_FUNCTION__ = "SaAisErrorT 
avd_susi_recreate(AVSV_N2D_ND_SISU_STATE_MSG_INFO*)"
#4  0x00459943 in avd_process_state_info_queue (cb=0x75cba0 
<_control_block>) at ndfsm.cc:78
n2d_msg = 0x7f1d20008ec0
i = 0
queue_size = 4
queue_evt = 0x7a9b60
act_amfnd_node_up_count = 1
found_state_info = true
__FUNCTION__ = "avd_process_state_info_queue"
#5  0x0045a50f in avd_node_up_evh (cb=0x75cba0 <_control_block>, 
evt=0x7f1d20008880) at ndfsm.cc:363
avnd = 0x7bf380
n2d_msg = 0x7f1d20004b30
rc = 1
sync_nd_size = 4
act_nd = true
__FUNCTION__ = "avd_node_up_evh"
#6  0x00453d78 in process_event (cb_now=0x75cba0 <_control_block>, 
evt=0x7f1d20008880) at main.cc:768
__FUNCTION__ = "process_event"
#7  0x00453a9b in main_loop () at main.cc:689
pollretval = 1
cb = 0x75cba0 <_control_block>
evt = 0x7f1d20008880
mbx_fd = {raise_obj = 11, rmv_obj = 12}
error = SA_AIS_OK
polltmo = -1
term_fd = 17
__FUNCTION__ = "main_loop"
#8  0x00454017 in main (argc=2, argv=0x7fff50cd9958) at main.cc:841


Suggested recovery :

 During a split brain scenario, payloads  should be ordered for reboot even in 
headless feature. 


---

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

[tickets] [opensaf:tickets] #2074 amfd asserted on rebooted controllers continuoulsy after split brain scenario (headless)

2022-10-10 Thread Mohan Kanakam via Opensaf-tickets

- **status**: unassigned --> accepted



---

** [tickets:#2074] amfd asserted on rebooted controllers continuoulsy after 
split brain scenario (headless)**

**Status:** accepted
**Milestone:** future
**Created:** Tue Sep 27, 2016 12:14 PM UTC by Srikanth R
**Last Updated:** Mon Oct 10, 2022 12:04 PM UTC
**Owner:** Mohan  Kanakam


Setup : 
SLES 11 Physical machine
Changeset :7997 5.1 FC
2 controllers and 2 payloads with headless feature enabled.
2N application with 3 SUs. (AmfDemo).

Issue :

amfd asserted on controllers  continuoulsy for every reboot after  initial 
split brain scenario is observed


Steps performed :

-> Initially brought up four nodes and all the nodes joined the cluster.

-> Brought up the 2N application, with SUs hosted on SC-1 ,SC-2 and PL-3 
successfully.

-> Performed some operations on the AMF objects and the cluster is left in idle 
state later.

-> After a gap of 2 weeks, MDS down event is generated on both the controllers 
for which spilt brain scenario is generated. Because of momentary cable(s) 
unplugging, MDS down event is generated.


Sep 24 21:36:40 SLES-SLOT1 osafimmd[2729]: NO MDS event from svc_id 25 
(change:3, dest:565214187380752)
Sep 24 21:36:40 SLES-SLOT1 kernel: [1297950.833811] TIPC: Established link 
<1.1.1:em1-1.1.2:em1> on network plane A
Sep 24 21:36:40 SLES-SLOT1 osafrded[2710]: Rebooting OpenSAF NodeId = 0 EE Name 
= No EE Mapped, Reason: Split-brain detected, OwnNodeId = 131343, 
SupervisionTime = 60


Sep 26 00:00:01 SLES-SLOT2 osafrded[2715]: NO Got peer info request from node 
0x2010f with role ACTIVE
Sep 26 00:00:01 SLES-SLOT2 osafrded[2715]: Rebooting OpenSAF NodeId = 0 EE Name 
= No EE Mapped, Reason: Split-brain detected, OwnNodeId = 131599, 
SupervisionTime = 60


-> As headless feature is enabled, payloads did not go for reboot.

-> Once controllers joined the payloads, amfd asserted on the rebooted 
controller and controllers went for reboot.
Sep 24 21:39:27 SLES-SLOT1 osafamfd[2772]: NO Received node_up from 2010f: 
msg_id 1
Sep 24 21:39:27 SLES-SLOT1 osafamfd[2772]: siass.cc:953: avd_susi_recreate: 
Assertion 'su' failed.
Sep 24 21:39:27 SLES-SLOT1 osafamfnd[2782]: WA AMF director unexpectedly crashed
Sep 24 21:39:27 SLES-SLOT1 osafamfnd[2782]: WA AMF director unexpectedly crashed
Sep 24 21:39:27 SLES-SLOT1 osafamfnd[2782]: Rebooting OpenSAF NodeId = 131343 
EE Name = , Reason: local AVD down(Adest) or both AVD down(Vdest) received, 
OwnNodeId = 131343, SupervisionTime = 60


Below is the backtrace :

#0  0x7f1d28510b55 in raise () from /lib64/libc.so.6
No symbol table info available.
#1  0x7f1d28512131 in abort () from /lib64/libc.so.6
No symbol table info available.
#2  0x7f1d2a397197 in __osafassert_fail (__file=0x517c15 "siass.cc", 
__line=953, __func=0x518250 
 
"avd_susi_recreate", 
__assertion=0x517d01 "su") at sysf_def.c:281
No locals.
#3  0x004c56a5 in avd_susi_recreate (info=0x7f1d20008ec8) at 
siass.cc:953
su = 0x0
__FUNCTION__ = "avd_susi_recreate"
susi = 0x0
node = 0x7bfdf0
susi_state = 0x0
su_state = 0x7f1d200055a0
__PRETTY_FUNCTION__ = "SaAisErrorT 
avd_susi_recreate(AVSV_N2D_ND_SISU_STATE_MSG_INFO*)"
#4  0x00459943 in avd_process_state_info_queue (cb=0x75cba0 
<_control_block>) at ndfsm.cc:78
n2d_msg = 0x7f1d20008ec0
i = 0
queue_size = 4
queue_evt = 0x7a9b60
act_amfnd_node_up_count = 1
found_state_info = true
__FUNCTION__ = "avd_process_state_info_queue"
#5  0x0045a50f in avd_node_up_evh (cb=0x75cba0 <_control_block>, 
evt=0x7f1d20008880) at ndfsm.cc:363
avnd = 0x7bf380
n2d_msg = 0x7f1d20004b30
rc = 1
sync_nd_size = 4
act_nd = true
__FUNCTION__ = "avd_node_up_evh"
#6  0x00453d78 in process_event (cb_now=0x75cba0 <_control_block>, 
evt=0x7f1d20008880) at main.cc:768
__FUNCTION__ = "process_event"
#7  0x00453a9b in main_loop () at main.cc:689
pollretval = 1
cb = 0x75cba0 <_control_block>
evt = 0x7f1d20008880
mbx_fd = {raise_obj = 11, rmv_obj = 12}
error = SA_AIS_OK
polltmo = -1
term_fd = 17
__FUNCTION__ = "main_loop"
#8  0x00454017 in main (argc=2, argv=0x7fff50cd9958) at main.cc:841


Suggested recovery :

 During a split brain scenario, payloads  should be ordered for reboot even in 
headless feature. 


---

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] #2074 amfd asserted on rebooted controllers continuoulsy after split brain scenario (headless)

2022-10-10 Thread Mohan Kanakam via Opensaf-tickets

- **assigned_to**: Mohan  Kanakam
- **Blocker**:  --> False



---

** [tickets:#2074] amfd asserted on rebooted controllers continuoulsy after 
split brain scenario (headless)**

**Status:** unassigned
**Milestone:** future
**Created:** Tue Sep 27, 2016 12:14 PM UTC by Srikanth R
**Last Updated:** Tue Sep 27, 2016 12:14 PM UTC
**Owner:** Mohan  Kanakam


Setup : 
SLES 11 Physical machine
Changeset :7997 5.1 FC
2 controllers and 2 payloads with headless feature enabled.
2N application with 3 SUs. (AmfDemo).

Issue :

amfd asserted on controllers  continuoulsy for every reboot after  initial 
split brain scenario is observed


Steps performed :

-> Initially brought up four nodes and all the nodes joined the cluster.

-> Brought up the 2N application, with SUs hosted on SC-1 ,SC-2 and PL-3 
successfully.

-> Performed some operations on the AMF objects and the cluster is left in idle 
state later.

-> After a gap of 2 weeks, MDS down event is generated on both the controllers 
for which spilt brain scenario is generated. Because of momentary cable(s) 
unplugging, MDS down event is generated.


Sep 24 21:36:40 SLES-SLOT1 osafimmd[2729]: NO MDS event from svc_id 25 
(change:3, dest:565214187380752)
Sep 24 21:36:40 SLES-SLOT1 kernel: [1297950.833811] TIPC: Established link 
<1.1.1:em1-1.1.2:em1> on network plane A
Sep 24 21:36:40 SLES-SLOT1 osafrded[2710]: Rebooting OpenSAF NodeId = 0 EE Name 
= No EE Mapped, Reason: Split-brain detected, OwnNodeId = 131343, 
SupervisionTime = 60


Sep 26 00:00:01 SLES-SLOT2 osafrded[2715]: NO Got peer info request from node 
0x2010f with role ACTIVE
Sep 26 00:00:01 SLES-SLOT2 osafrded[2715]: Rebooting OpenSAF NodeId = 0 EE Name 
= No EE Mapped, Reason: Split-brain detected, OwnNodeId = 131599, 
SupervisionTime = 60


-> As headless feature is enabled, payloads did not go for reboot.

-> Once controllers joined the payloads, amfd asserted on the rebooted 
controller and controllers went for reboot.
Sep 24 21:39:27 SLES-SLOT1 osafamfd[2772]: NO Received node_up from 2010f: 
msg_id 1
Sep 24 21:39:27 SLES-SLOT1 osafamfd[2772]: siass.cc:953: avd_susi_recreate: 
Assertion 'su' failed.
Sep 24 21:39:27 SLES-SLOT1 osafamfnd[2782]: WA AMF director unexpectedly crashed
Sep 24 21:39:27 SLES-SLOT1 osafamfnd[2782]: WA AMF director unexpectedly crashed
Sep 24 21:39:27 SLES-SLOT1 osafamfnd[2782]: Rebooting OpenSAF NodeId = 131343 
EE Name = , Reason: local AVD down(Adest) or both AVD down(Vdest) received, 
OwnNodeId = 131343, SupervisionTime = 60


Below is the backtrace :

#0  0x7f1d28510b55 in raise () from /lib64/libc.so.6
No symbol table info available.
#1  0x7f1d28512131 in abort () from /lib64/libc.so.6
No symbol table info available.
#2  0x7f1d2a397197 in __osafassert_fail (__file=0x517c15 "siass.cc", 
__line=953, __func=0x518250 
 
"avd_susi_recreate", 
__assertion=0x517d01 "su") at sysf_def.c:281
No locals.
#3  0x004c56a5 in avd_susi_recreate (info=0x7f1d20008ec8) at 
siass.cc:953
su = 0x0
__FUNCTION__ = "avd_susi_recreate"
susi = 0x0
node = 0x7bfdf0
susi_state = 0x0
su_state = 0x7f1d200055a0
__PRETTY_FUNCTION__ = "SaAisErrorT 
avd_susi_recreate(AVSV_N2D_ND_SISU_STATE_MSG_INFO*)"
#4  0x00459943 in avd_process_state_info_queue (cb=0x75cba0 
<_control_block>) at ndfsm.cc:78
n2d_msg = 0x7f1d20008ec0
i = 0
queue_size = 4
queue_evt = 0x7a9b60
act_amfnd_node_up_count = 1
found_state_info = true
__FUNCTION__ = "avd_process_state_info_queue"
#5  0x0045a50f in avd_node_up_evh (cb=0x75cba0 <_control_block>, 
evt=0x7f1d20008880) at ndfsm.cc:363
avnd = 0x7bf380
n2d_msg = 0x7f1d20004b30
rc = 1
sync_nd_size = 4
act_nd = true
__FUNCTION__ = "avd_node_up_evh"
#6  0x00453d78 in process_event (cb_now=0x75cba0 <_control_block>, 
evt=0x7f1d20008880) at main.cc:768
__FUNCTION__ = "process_event"
#7  0x00453a9b in main_loop () at main.cc:689
pollretval = 1
cb = 0x75cba0 <_control_block>
evt = 0x7f1d20008880
mbx_fd = {raise_obj = 11, rmv_obj = 12}
error = SA_AIS_OK
polltmo = -1
term_fd = 17
__FUNCTION__ = "main_loop"
#8  0x00454017 in main (argc=2, argv=0x7fff50cd9958) at main.cc:841


Suggested recovery :

 During a split brain scenario, payloads  should be ordered for reboot even in 
headless feature. 


---

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

[tickets] [opensaf:tickets] #2172 mbc: trace logs of OpenSAF services are flooded after si-swap

2022-10-10 Thread Mohan Kanakam via Opensaf-tickets

- **Blocker**:  --> False
- **Comment**:

Hi  Vu Minh Nguyen,
What is the expectation from this ticket. Do we want to reduce traces or fix a 
logic?
I will try to reproduce it and will let you know if it gets reproduced on 
latest OpenSAF.
Thanks
Mohan
High Availability Solutions (www.GetHighAvailability.com)



---

** [tickets:#2172] mbc: trace logs of OpenSAF services are flooded after 
si-swap**

**Status:** unassigned
**Milestone:** future
**Created:** Mon Nov 07, 2016 07:19 AM UTC by Vu Minh Nguyen
**Last Updated:** Mon Nov 07, 2016 07:20 AM UTC
**Owner:** nobody


After performing si-swap, OpenSAF service TRACE are flooded by MBCSV TRACE log. 
Following TRACE are dumped at every second, and seems non-stop:

> Nov  7 10:48:42.136763 osaflogd [453:mbcsv_api.c:0406] >> 
> mbcsv_process_dispatch_request: Dispatch MBCSV event
> Nov  7 10:48:42.137051 osaflogd [453:mbcsv_pr_evts.c:0269] >> 
> mbcsv_hdl_dispatch_all
> Nov  7 10:48:42.137301 osaflogd [453:mbcsv_pr_evts.c:0068] >> 
> mbcsv_process_events: mbcsv hdl: 4293918753
> Nov  7 10:48:42.137504 osaflogd [453:mbcsv_pr_evts.c:0129] TR Timer event
> Nov  7 10:48:42.137590 osaflogd [453:mbcsv_pr_evts.c:0140] T1 myrole: 1, 
> svc_id: 36, pwe_hdl: 65547, peer_anchor: 565214255040142, peer_state: 3, 
> event type:MBCSV_TMR_TRANSMIT
> Nov  7 10:48:42.137670 osaflogd [453:mbcsv_tmr.c:0481] TR Transmit timer. 
> sending call-again-event for pwe_hdl:65547. revisit!
> Nov  7 10:48:42.137750 osaflogd [453:mbcsv_util.c:0929] >> mbcsv_send_msg: 
> event type: 6
> Nov  7 10:48:42.137826 osaflogd [453:mbcsv_util.c:0811] >> 
> ncs_mbcsv_encode_message
> Nov  7 10:48:42.138089 osaflogd [453:mbcsv_util.c:0832] TR set 
> call_again_action for coldsync_resp or warmsync_resp or data_resp
> Nov  7 10:48:42.138192 osaflogd [453:mbcsv_util.c:0862] TR set-next 
> call_again_action for coldsync_resp or warmsync_resp or data_resp
> Nov  7 10:48:42.138363 osaflogd [453:mbcsv_util.c:0905] << 
> ncs_mbcsv_encode_message
> Nov  7 10:48:42.138453 osaflogd [453:mbcsv_mds.c:0185] >> mbcsv_mds_send_msg: 
> sending to vdest:b
> Nov  7 10:48:42.138593 osaflogd [453:mbcsv_mds.c:0201] TR send type 
> MDS_SENDTYPE_RED
> Nov  7 10:48:42.139412 osaflogd [453:mbcsv_mds.c:0244] << mbcsv_mds_send_msg: 
> success
> Nov  7 10:48:42.139614 osaflogd [453:mbcsv_util.c:0978] T1 event is 
> multi-part response(i.e.coldsync resp, warmsync resp or dataresp), call-again
> Nov  7 10:48:42.139704 osaflogd [453:mbcsv_util.c:0982] T1 start the transmit 
> timer
> Nov  7 10:48:42.139782 osaflogd [453:mbcsv_tmr.c:0094] >> 
> ncs_mbcsv_start_timer
> Nov  7 10:48:42.140069 osaflogd [453:mbcsv_tmr.c:0120] TR starting timer. my 
> role:1, svc_id:36, pwe_hdl:65547, peer_anchor: 565214255040142, tmr 
> type:NCS_MBCSV_TMR_TRANSMIT
> Nov  7 10:48:42.140568 osaflogd [453:mbcsv_tmr.c:0127] << 
> ncs_mbcsv_start_timer
> Nov  7 10:48:42.140665 osaflogd [453:mbcsv_util.c:0999] << mbcsv_send_msg
> Nov  7 10:48:42.140746 osaflogd [453:mbcsv_pr_evts.c:0222] << 
> mbcsv_process_events
> Nov  7 10:48:42.141440 osaflogd [453:mbcsv_pr_evts.c:0278] << 
> mbcsv_hdl_dispatch_all
> Nov  7 10:48:42.141648 osaflogd [453:mbcsv_api.c:0435] << 
> mbcsv_process_dispatch_request: retval: 1


---

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] #2914 clm : add missing testcases in Clm apitest

2022-10-10 Thread Mohan Kanakam via Opensaf-tickets

Hi ,
I was reviewing the tickets on my name.  I see this ticket is in review since 
long. Can we push the published patch? If you are not good, then we can discard 
it and close this ticket.
Thanks
Mohan K
High Availability Solutions(www.GetHighAvailability.com)


---

** [tickets:#2914] clm : add missing testcases  in Clm apitest**

**Status:** review
**Milestone:** future
**Created:** Mon Aug 20, 2018 01:34 PM UTC by Richa 
**Last Updated:** Sun Jan 23, 2022 10:07 PM UTC
**Owner:** Mohan  Kanakam


Adding missing test cases in clm apitest.


---

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] #2932 ckpt: converting the checkpoint service from c to c++

2022-10-10 Thread Mohan Kanakam via Opensaf-tickets

Hi folks,
I was reviewing the tickets on my name.  I see this ticket is in review since 
long. Can we push the published patch? If you are not good, then we can discard 
it and close this ticket.
Thanks
Mohan K
High Availability Solutions(www.GetHighAvailability.com)


---

** [tickets:#2932] ckpt: converting the checkpoint service from  c to c++  **

**Status:** review
**Milestone:** future
**Created:** Mon Oct 01, 2018 01:25 PM UTC by Mohan  Kanakam
**Last Updated:** Sun Jan 23, 2022 10:07 PM UTC
**Owner:** Mohan  Kanakam


Converting the checkpoint service  from c to  c++. 


---

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] #2966 lck: add missing test case of lck apitest

2022-10-10 Thread Mohan Kanakam via Opensaf-tickets

Hi folks,
I was reviewing the tickets on my name.  I see this ticket is in review since 
long. Can we push the published patch? If you are not good, then we can discard 
it and close this ticket.
Thanks
Mohan K
High Availability Solutions(www.GetHighAvailability.com)


---

** [tickets:#2966] lck: add missing test case of lck apitest**

**Status:** review
**Milestone:** future
**Created:** Mon Nov 19, 2018 05:30 AM UTC by Mohan  Kanakam
**Last Updated:** Sun Jan 23, 2022 10:07 PM UTC
**Owner:** Mohan  Kanakam





---

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] #2967 msg: add missing test case of msg apitest

2022-10-10 Thread Mohan Kanakam via Opensaf-tickets

Hi folks,
Can we push the published patch? If you are not good, then we can discard it 
and close this ticket.
Thanks
Mohan K
High Availability Solutions(www.GetHighAvailability.com)

 


---

** [tickets:#2967] msg: add missing test case of msg apitest**

**Status:** review
**Milestone:** future
**Created:** Tue Nov 20, 2018 05:33 AM UTC by Mohan  Kanakam
**Last Updated:** Sun Jan 23, 2022 10:06 PM UTC
**Owner:** Mohan  Kanakam





---

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] #3299 immnd: unexpected reboot node after merge network back

[tickets] [opensaf:tickets] #3299 immnd: unexpected reboot node after merge network back

[tickets] [opensaf:tickets] #2468 amf: amfd asserts while decrementing opensaf NoRed SI assignment counter during fail-over.

[tickets] [opensaf:tickets] #2468 amf: amfd asserts while decrementing opensaf NoRed SI assignment counter during fail-over.

[tickets] [opensaf:tickets] #2468 amf: amfd asserts while decrementing opensaf NoRed SI assignment counter during fail-over.

[tickets] [opensaf:tickets] #2526 amfd: Command unlock nodegroup timeout if su failover is escalated (>= 2SIs)

[tickets] [opensaf:tickets] #2526 amfd: Command unlock nodegroup timeout if su failover is escalated (>= 2SIs)

[tickets] [opensaf:tickets] #2526 amfd: Command unlock nodegroup timeout if su failover is escalated (>= 2SIs)

[tickets] [opensaf:tickets] #2074 amfd asserted on rebooted controllers continuoulsy after split brain scenario (headless)

[tickets] [opensaf:tickets] #2074 amfd asserted on rebooted controllers continuoulsy after split brain scenario (headless)

[tickets] [opensaf:tickets] #2074 amfd asserted on rebooted controllers continuoulsy after split brain scenario (headless)

[tickets] [opensaf:tickets] #2172 mbc: trace logs of OpenSAF services are flooded after si-swap

[tickets] [opensaf:tickets] #2914 clm : add missing testcases in Clm apitest

[tickets] [opensaf:tickets] #2932 ckpt: converting the checkpoint service from c to c++

[tickets] [opensaf:tickets] #2966 lck: add missing test case of lck apitest

[tickets] [opensaf:tickets] #2967 msg: add missing test case of msg apitest

16 matches

Site Navigation

Mail list logo

Footer information