[tickets] [opensaf:tickets] #2485 amfnd: missing susi response if component is restarted

2017-06-06 Thread Gary Lee via Opensaf-tickets 



---

** [tickets:#2485] amfnd: missing susi response if component is restarted**

**Status:** unassigned
**Milestone:** 5.17.06
**Created:** Wed Jun 07, 2017 12:57 AM UTC by Gary Lee
**Last Updated:** Wed Jun 07, 2017 12:57 AM UTC
**Owner:** nobody


An SI contains multiple CSIs. If a restart component admin operation arrives at 
amfnd before all CSIs are assigned,
the SUSI response is not sent to AMFD.

This code in avnd_comp_csi_assign_done() appears to be the problem area.

  /* while restarting, we wont use assign all, so csi will not be null */
  if (csi && m_AVND_COMP_CSI_CURR_ASSIGN_STATE_IS_RESTARTING(csi)) {
m_AVND_COMP_CSI_CURR_ASSIGN_STATE_SET(csi,
  AVND_COMP_CSI_ASSIGN_STATE_ASSIGNED);
goto done;
  }

Perhaps we should not initiate a restart in avnd_evt_comp_admin_op_req(), if
a component is still in AVND_COMP_CSI_ASSIGN_STATE_ASSIGNING state.


---

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.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2484 imm: Testsuit 7 of immoitest fails with ERR_TRY_AGAIN

2017-06-06 Thread Hung Nguyen via Opensaf-tickets 
- **status**: accepted --> review



---

** [tickets:#2484] imm: Testsuit 7 of immoitest fails with ERR_TRY_AGAIN**

**Status:** review
**Milestone:** 5.17.06
**Created:** Tue Jun 06, 2017 04:25 AM UTC by Hung Nguyen
**Last Updated:** Tue Jun 06, 2017 04:25 AM UTC
**Owner:** Hung Nguyen


~~~
# immoitest --longDn 7

Suite 7: Long DN
1  PASSED   SA_AIS_OK - Object create callback;
2  PASSED   SA_AIS_OK - Object modify callback;
3  PASSED   SA_AIS_OK - Object delete callback;
4  PASSED   SA_AIS_OK - Rt Object create and delete;
error: in src/imm/apitest/implementer/test_saImmOiLongDn.c at 500: 
SA_AIS_ERR_TRY_AGAIN (6), expected SA_AIS_OK (1) - exiting
~~~

The testcases of testsuite 7 use the same implementer name.
At the end of each testcase, the implementer name is not explicitly cleared 
with saImmOiImplementerClear().
Instead, saImmOiFinalize() is called.
The difference between OiImplementerClear() and OiFinalize() is:
\- OiImplementerClear() returns after the implementer is fully discarded on all 
nodes
\- saImmOiFinalize() returns after the implementer is locally discarded on the 
originating node (no guarantee of being fully discarded)

So if you set the same implementer name after saImmOiFinalize(), chances are 
you will get ERR_TRY_AGAIN.


---

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.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2478 clmtest: failed test cases

2017-06-06 Thread Hung Nguyen via Opensaf-tickets 
- **status**: review --> fixed
- **Milestone**: 5.17.08 --> 5.17.06
- **Comment**:

5.17.08 (develop) [code:664e46]

~~~
commit 664e46e54ef3c4b2e11b84e5efc73916ba6f6fc2
Author: Hoang Vo 
Date:   Tue Jun 6 17:39:02 2017 +0700

clmtest: Correct test case following AIS [#2478]

Correct test case following AIS.
~~~

5.17.06 (release) [code:360bb7]
~~~
commit 360bb7dee0b8d85ae7e25d70ba1c7d7eab034b8a
Author: Hoang Vo 
Date:   Tue Jun 6 17:39:02 2017 +0700

clmtest: Correct test case following AIS [#2478]

Correct test case following AIS.
~~~



---

** [tickets:#2478] clmtest: failed test cases**

**Status:** fixed
**Milestone:** 5.17.06
**Created:** Fri Jun 02, 2017 06:20 AM UTC by Vo Minh Hoang
**Last Updated:** Fri Jun 02, 2017 07:32 AM UTC
**Owner:** Vo Minh Hoang


Test cases failed due to inconsistence with specification:
Suite 2 - saClmSelectionObjectGet NULL handle
Suite 5 - saClmClusterNodeGet & saClmClusterNodeGet_4 with NULL timeout
Suite 5 - saClmClusterNodeGet & saClmClusterNodeGet_4 with nodeId of non member 
node
Suite 7 - saClmClusterTrack_4 with null handle or invalid handle
Suite 7 - saClmClusterTrack_4 with null flags


---

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.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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.

2017-06-06 Thread Praveen via Opensaf-tickets 
Hi,
In the later releases assert has been replaced with warning. 
Without amfd traces, it is not possbile to know why the counter was decremented 
before the assert.
I will try to reproduce based on code analysis and will update further.

Thanks
Praveen



---

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

**Status:** unassigned
**Milestone:** 5.17.06
**Created:** Thu May 25, 2017 08:46 AM UTC by Praveen
**Last Updated:** Thu Jun 01, 2017 02:41 PM UTC
**Owner:** nobody


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.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets