[tickets] [opensaf:tickets] #1756 AMF : amfd on controller asserted ( for CSI removal timeout during application si lock )

2016-05-05 Thread Nagendra Kumar 
- **status**: review --> fixed
- **Comment**:

changeset:   7609:6e1158554404
branch:  opensaf-4.7.x
parent:  7604:72cc6d1ea330
user:Nagendra Kumar
date:Thu May 05 14:34:52 2016 +0530
summary: amfd: mark su fsm state as assigned [#1756]

changeset:   7610:cf43b685a1ec
branch:  opensaf-5.0.x
parent:  7606:94676cfe3582
user:Nagendra Kumar
date:Thu May 05 14:35:19 2016 +0530
summary: amfd: mark su fsm state as assigned [#1756]

changeset:   7611:5c4c0121de10
tag: tip
parent:  7608:f2fe3e3db1f0
user:Nagendra Kumar
date:Thu May 05 14:35:28 2016 +0530
summary: amfd: mark su fsm state as assigned [#1756]

[staging:6e1158]
[staging:cf43b6]
[staging:5c4c01]




---

** [tickets:#1756] AMF : amfd on controller asserted ( for CSI removal timeout 
during application si lock )**

**Status:** fixed
**Milestone:** 4.7.2
**Created:** Wed Apr 13, 2016 11:00 AM UTC by Srikanth R
**Last Updated:** Wed May 04, 2016 06:56 PM UTC
**Owner:** Nagendra Kumar
**Attachments:**

- 
[1755.tgz](https://sourceforge.net/p/opensaf/tickets/1756/attachment/1755.tgz) 
(681.2 kB; application/x-compressed-tar)


Changeset : 7436
Version : 5.0 FC
Setup :  Controller with 2 payloads. 
 2n red model with 2 SUs, 4 SIs and no si-si deps.
 
   
Steps performed :

-> Initially the application is brought up and all the SIs are fully assigned.

-> LPerformed shutdown operation on one of the SI .i.e SI4.

-> Ensured that application with active assignment shall time out in CSI 
removal callback. 

The shutdown operation timed out and the amfd on active controller asserted. 

Invoking admin operation SHUTDOWN on safSi=TestApp_SI4,safApp=TestApp_TwoN 
OP RETURN VALUE and AIS OP RETURN VAL =  5 -65536


Apr 13 16:17:40 CONTROLLER-2 osafamfd[2689]: sg_2n_fsm.cc:125: 
avd_su_fsm_state_determine: Assertion '0' failed.
Apr 13 16:17:40 CONTROLLER-2 osafamfnd[2699]: WA AMF director unexpectedly 
crashed
Apr 13 16:17:40 CONTROLLER-2 osafamfnd[2699]: Rebooting OpenSAF NodeId = 131599 
EE Name = , Reason: local AVD down(Adest) or both AVD down(Vdest) received, 
OwnNodeId = 131599, SupervisionTime = 6




---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1809 msg: APIs returning SA_AIS_OK even when cluster node has left cluster membership

2016-05-05 Thread Chani Srivastava 
- **Part**: - --> lib
- **Priority**: major --> minor



---

** [tickets:#1809] msg: APIs returning SA_AIS_OK even when cluster node has 
left cluster membership**

**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Thu May 05, 2016 09:52 AM UTC by Chani Srivastava
**Last Updated:** Thu May 05, 2016 09:52 AM UTC
**Owner:** nobody
**Attachments:**

- 
[mqsv_demo_app.c](https://sourceforge.net/p/opensaf/tickets/1809/attachment/mqsv_demo_app.c)
 (4.0 kB; text/x-c)


Setup:
Changeset- 7436
Version - opensaf 5.0
The issue is observed with last two releases also.

Issue: When a node is locked by clm service, saMsgQueueOpen() return SA_AIS_OK 
when it is should have returned SA_AIS_ERR_UNAVAILABLE according to the spec as 
mentioned blow:

If the cluster node has left the cluster membership or is being administratively
evicted from the cluster membership, the Message Service behaves as follows
towards processes residing on that node and using or attempting to use the 
service:
⇒ Calls to saMsgInitialize() will fail with SA_AIS_ERR_UNAVAILABLE.
⇒ All Message Service APIs that are invoked by the process and that operate on
handles already acquired by the process will fail with
SA_AIS_ERR_UNAVAILABLE with the following exceptions, assuming that the
handle msgHandle has already been acquired:

Step to Reproduce:
1. Compile and build the attached test code.
2. After Initialization, test sleep for 10 sec
3. During this sleep, lock the CLM node from another node in cluster
4. saMsgQueueOpen returns successfully.

Expected: saMsgQueueOpen should fail with rc = 31 


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1772 AMF: amfnd false assert when unlock 2N Active SU

2016-05-05 Thread Praveen 
- **status**: unassigned --> assigned
- **assigned_to**: Praveen



---

** [tickets:#1772] AMF: amfnd false assert when unlock 2N Active SU**

**Status:** assigned
**Milestone:** 4.7.2
**Created:** Wed Apr 20, 2016 02:39 AM UTC by Minh Hon Chau
**Last Updated:** Wed May 04, 2016 06:55 PM UTC
**Owner:** Praveen
**Attachments:**

- 
[amfnd_assert.tgz](https://sourceforge.net/p/opensaf/tickets/1772/attachment/amfnd_assert.tgz)
 (290.1 kB; application/x-compressed)


- Configuration: as attached file
   . Set up 2N amf_demo with active SU4 on PL4, standby SU5, SU5B on PL5.
   . 3 components for each SU
   . 3 SIs, with dependency: SI3 -> SI2 -> S1 (highest sponsored SI)
- Steps:
   . Bring up 2 SU
   . Lock Active SU4, delay csi remove callback 
   . Meanwhile, reboot PL5
   . Release delay of csi remove callback in SU4 -> assignments are removed 
successfully
   . PL5 restarts, SU5B get Active, SU5 get Standb assignments
   . Lock SU5, SU5B
   . Unlock SU4
   -> amfnd on PL4 asserts

2016-04-20 12:36:14 PL-4 osafamfnd[423]: di.cc:835: avnd_di_susi_resp_send: 
Assertion 'si' failed.
2016-04-20 12:36:14 PL-4 osafamfwd[465]: Rebooting OpenSAF NodeId = 0 EE Name = 
No EE Mapped, Reason: AMF unexpectedly crashed, OwnNodeId = 132111, 
SupervisionTime = 60
2016-04-20 12:36:14 PL-4 amf_demo[660]: AL AMF Node Director is down, terminate 
this process



---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1757 Standby controller failed to join the cluster

2016-05-05 Thread Srikanth R 
- **summary**: Standby controller failed to join the cluster probably because 
of setup issues --> Standby controller failed to join the cluster
- **status**: unassigned --> duplicate
- **Milestone**: 4.7.2 --> never
- **Comment**:

Closing this ticket as duplicate of #1701. In both the tickets, the CLM client 
(.i.e.. osafamfnd ) received SA_AIS_ERR_NO_MEMORY during initialization. 



---

** [tickets:#1757] Standby controller failed to join the cluster**

**Status:** duplicate
**Milestone:** never
**Created:** Wed Apr 13, 2016 11:12 AM UTC by Ritu Raj
**Last Updated:** Wed May 04, 2016 06:56 PM UTC
**Owner:** nobody


*Setup:
Changeset- 7436
Version - opensaf 5.0FC
OS: SUSE 11SP2 x86_64

*Issue observed :
Standby controller failed to join the cluster with error message "ER Failed to 
Initialize with CLM"

*Steps To Reproduce:
> OpenSAF is already up and running on controller1(SC-1)
> when OpenSAF started on controller2(SC-2), it failed with following mesage: 

SCALE_SLOT-2:~ # /etc/init.d/opensafd start
Apr 26 20:11:28 SCALE_SLOT-2 opensafd: Starting OpenSAF Services(5.0.FC - ) 
(Using TIPC)
Starting OpenSAF Services (Using TIPC):Apr 26 20:11:28 SCALE_SLOT-2 kernel: 
[1930938.251473] TIPC: Activated (version 2.0.0)
...
Apr 26 20:11:29 SCALE_SLOT-2 osafamfnd[29911]: Started
**Apr 26 20:11:29 SCALE_SLOT-2 osafamfnd[29911]: ER Failed to Initialize with 
CLM: 8
Apr 26 20:11:29 SCALE_SLOT-2 osafamfnd[29911]: ER avnd_create failed**
Apr 26 20:11:29 SCALE_SLOT-2 osafamfnd[29911]: NO exiting

> The crossponding syslog of active controller(SC-1) at that time
Apr 26 20:08:51 SCALE_SLOT-1 osafclmd[31692]: WA FAILED:** 
ncs_patricia_tree_add, client_id** 53
Apr 26 20:08:51 SCALE_SLOT-1 osafamfd[31702]: NO Node 'SC-2' left the cluster


>> It is also observed that, on active controller(SC-1) there in no log record 
>> of osafclmd during which controller2(SC-2) failed, while other service have 
>> log record at that time stamp

Below is the output of osafclmd (SC-1), during time stamp "Apr 26 
20:08:51.237701" to "Apr 26 20:12:06.272871" osafclmd not logged anything.
Apr 26 20:08:51.237695 osafclmd [31692:clms_evt.c:1601] << process_api_evt
**Apr 26 20:08:51.237701 osafclmd [31692:clms_evt.c:1667] << clms_process_mbx
Apr 26 20:12:06.272871 osafclmd [31692:ava_mds.c:0179] >> ava_mds_cbk**
Apr 26 20:12:06.272923 osafclmd [31692:ava_mds.c:0530] >> ava_mds_flat_dec


Note: 
1. This is random issue
2. The time gap between controller1(SC-1) and controller2(SC-2) is 3 min. 


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1809 msg: APIs returning SA_AIS_OK even when cluster node has left cluster membership

2016-05-05 Thread Chani Srivastava 



---

** [tickets:#1809] msg: APIs returning SA_AIS_OK even when cluster node has 
left cluster membership**

**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Thu May 05, 2016 09:52 AM UTC by Chani Srivastava
**Last Updated:** Thu May 05, 2016 09:52 AM UTC
**Owner:** nobody
**Attachments:**

- 
[mqsv_demo_app.c](https://sourceforge.net/p/opensaf/tickets/1809/attachment/mqsv_demo_app.c)
 (4.0 kB; text/x-c)


Setup:
Changeset- 7436
Version - opensaf 5.0
The issue is observed with last two releases also.

Issue: When a node is locked by clm service, saMsgQueueOpen() return SA_AIS_OK 
when it is should have returned SA_AIS_ERR_UNAVAILABLE according to the spec as 
mentioned blow:

If the cluster node has left the cluster membership or is being administratively
evicted from the cluster membership, the Message Service behaves as follows
towards processes residing on that node and using or attempting to use the 
service:
⇒ Calls to saMsgInitialize() will fail with SA_AIS_ERR_UNAVAILABLE.
⇒ All Message Service APIs that are invoked by the process and that operate on
handles already acquired by the process will fail with
SA_AIS_ERR_UNAVAILABLE with the following exceptions, assuming that the
handle msgHandle has already been acquired:

Step to Reproduce:
1. Compile and build the attached test code.
2. After Initialization, test sleep for 10 sec
3. During this sleep, lock the CLM node from another node in cluster
4. saMsgQueueOpen returns successfully.

Expected: saMsgQueueOpen should fail with rc = 31 


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1808 pyosaf:saImmOiAugmentCcbInitialize() call in saImmOi.py is failing

2016-05-05 Thread Neelakanta Reddy 



---

** [tickets:#1808] pyosaf:saImmOiAugmentCcbInitialize() call in saImmOi.py is 
failing**

**Status:** accepted
**Milestone:** 4.7.2
**Created:** Thu May 05, 2016 09:43 AM UTC by Neelakanta Reddy
**Last Updated:** Thu May 05, 2016 09:43 AM UTC
**Owner:** Neelakanta Reddy


 saImmOiAugmentCcbInitialize() call in saImmOi.py will fail due to unknown 
symbol.
 
 TR ERR_LIBRARY: Error in library linkage. libSaImmOm.so is not linked


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1772 AMF: amfnd false assert when unlock 2N Active SU

2016-05-05 Thread Praveen 
Attached is simple configuration to reproduce the problem without Si deps 
(amf-demo + su3). Also attached are the traces from active amfnd and amfnd. 
Steps to reproduce are same.


Attachments:

- 
[1772.xml](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/3ff377bf/494c/attachment/1772.xml)
 (11.9 kB; text/xml)
- 
[messages](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/3ff377bf/494c/attachment/messages)
 (135.8 kB; application/octet-stream)
- 
[osafamfd](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/3ff377bf/494c/attachment/osafamfd)
 (5.8 MB; application/octet-stream)
- 
[osafamfnd](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/3ff377bf/494c/attachment/osafamfnd)
 (1.5 MB; application/octet-stream)


---

** [tickets:#1772] AMF: amfnd false assert when unlock 2N Active SU**

**Status:** assigned
**Milestone:** 4.7.2
**Created:** Wed Apr 20, 2016 02:39 AM UTC by Minh Hon Chau
**Last Updated:** Thu May 05, 2016 08:29 AM UTC
**Owner:** Praveen
**Attachments:**

- 
[amfnd_assert.tgz](https://sourceforge.net/p/opensaf/tickets/1772/attachment/amfnd_assert.tgz)
 (290.1 kB; application/x-compressed)


- Configuration: as attached file
   . Set up 2N amf_demo with active SU4 on PL4, standby SU5, SU5B on PL5.
   . 3 components for each SU
   . 3 SIs, with dependency: SI3 -> SI2 -> S1 (highest sponsored SI)
- Steps:
   . Bring up 2 SU
   . Lock Active SU4, delay csi remove callback 
   . Meanwhile, reboot PL5
   . Release delay of csi remove callback in SU4 -> assignments are removed 
successfully
   . PL5 restarts, SU5B get Active, SU5 get Standb assignments
   . Lock SU5, SU5B
   . Unlock SU4
   -> amfnd on PL4 asserts

2016-04-20 12:36:14 PL-4 osafamfnd[423]: di.cc:835: avnd_di_susi_resp_send: 
Assertion 'si' failed.
2016-04-20 12:36:14 PL-4 osafamfwd[465]: Rebooting OpenSAF NodeId = 0 EE Name = 
No EE Mapped, Reason: AMF unexpectedly crashed, OwnNodeId = 132111, 
SupervisionTime = 60
2016-04-20 12:36:14 PL-4 amf_demo[660]: AL AMF Node Director is down, terminate 
this process



---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1810 smf: choose highest AU in merged procedure

2016-05-05 Thread Mathi Naickan 



---

** [tickets:#1810] smf: choose highest AU in merged procedure**

**Status:** assigned
**Milestone:** 4.7.2
**Created:** Thu May 05, 2016 11:47 AM UTC by Mathi Naickan
**Last Updated:** Thu May 05, 2016 11:47 AM UTC
**Owner:** Mathi Naickan


In the procedure of campaign, there must be consistent between Activation Unit 
Specification ( tag) of procedure and the 
saSmfBundleInstallOfflineScope of the added bundle (), that means if the 
saSmfBundleInstallOfflineScope of the added bundle equal to 4 – 
executionEnviroment, the Activation Unit Specification must be a scope of node.

This(choosing highest scope) is debatable though, but will try to provide a 
patch for review.


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1811 smf: Execution time of getNodeDestination() is not included in smfRebootTimeout in waitForNodeDestination

2016-05-05 Thread Mathi Naickan 



---

** [tickets:#1811] smf: Execution time of getNodeDestination() is not included 
in smfRebootTimeout in waitForNodeDestination**

**Status:** assigned
**Milestone:** 4.7.2
**Created:** Thu May 05, 2016 11:50 AM UTC by Mathi Naickan
**Last Updated:** Thu May 05, 2016 11:50 AM UTC
**Owner:** Mathi Naickan


This getNodeDestination() function is being used in another retry loop in 
waitForNodeDestination(). By default, if getNodeDestination() returns FALSE, 
the waitForNodeDestination() function will sleep for 2 seconds before 
re-invoking the getNodeDestination().

In such case that the reason getNodeDestination() returns FALSE was caused by 
timeout, the waitForNodeDestination() function will take 22 seconds to complete 
a loop instead of 2 seconds as expected. Then, in the worst scenario, the 
waitForNodeDestination() function has to wait 11*smfRebootTimeout to return 
FALSE (TIMEOUT case).


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1725 AMF: Recover transient SUSIs left over from headless

2016-05-05 Thread Minh Hon Chau 
thanks, I will check


---

** [tickets:#1725] AMF: Recover transient SUSIs left over from headless**

**Status:** accepted
**Milestone:** 5.1.FC
**Created:** Wed Apr 06, 2016 07:16 AM UTC by Minh Hon Chau
**Last Updated:** Thu May 05, 2016 05:28 AM UTC
**Owner:** Minh Hon Chau


This ticket is more likely an enhancement that targets on how AMFD detect and 
recover the transients SUSI left over from headless. There are three major 
situations:
(1) - Cluster goes headless, su/node failover on any payloads can happen, then 
cluster recover
(2) - issue admin op on any AMF entities, cluster goes headless. During 
headless, the middle HA assignments of whole admin op sequence between AMFND 
and components could be:
(2.1) The assignment completes, component returns OK with csi callback, 
then cluster recover
(2.2) The assignment is under going, then cluster recover. The assignment 
afterward could complete, or csi callback returns FAILED_OPERATION or error can 
also happen

At the time cluster recover, amfd has collected all assignments from all 
amfnd(s). These assignments can be in assigned or assigning states whilst its 
HA states do not conform its SG redundancy. Any of (1) (2.1) (2.2) can happen 
in a combination, which means while issuing admin op (2), cluster go headless 
and any kinds of failover (1) can happen during headless.  



---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1812 amfd: saClmDispatch FAILED on newly promoted SC

2016-05-05 Thread Gary Lee 
- Attachments has changed:

Diff:



--- old
+++ new
@@ -0,0 +1 @@
+amfd_coredump_bt.txt (8.0 kB; text/plain)



- **Comment**:

backtrace



---

** [tickets:#1812] amfd: saClmDispatch FAILED on newly promoted SC**

**Status:** accepted
**Milestone:** 5.0.1
**Created:** Fri May 06, 2016 05:56 AM UTC by Gary Lee
**Last Updated:** Fri May 06, 2016 05:56 AM UTC
**Owner:** Gary Lee
**Attachments:**

- 
[amfd_coredump_bt.txt](https://sourceforge.net/p/opensaf/tickets/1812/attachment/amfd_coredump_bt.txt)
 (8.0 kB; text/plain)


Enable headless and roaming features. Then:

Stop active SC (SC-1) and then standby SC (SC-2)

On the newly promoted SC, saClmDispatch FAILED 9 can be seen followed by a 
coredump.

2016-05-04 05:33:48 SC-5 osafamfd[474]: ER main: saClmDispatch FAILED 9




---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1812 amfd: saClmDispatch FAILED on newly promoted SC

2016-05-05 Thread Gary Lee 



---

** [tickets:#1812] amfd: saClmDispatch FAILED on newly promoted SC**

**Status:** accepted
**Milestone:** 5.0.1
**Created:** Fri May 06, 2016 05:56 AM UTC by Gary Lee
**Last Updated:** Fri May 06, 2016 05:56 AM UTC
**Owner:** Gary Lee


Enable headless and roaming features. Then:

Stop active SC (SC-1) and then standby SC (SC-2)

On the newly promoted SC, saClmDispatch FAILED 9 can be seen followed by a 
coredump.

2016-05-04 05:33:48 SC-5 osafamfd[474]: ER main: saClmDispatch FAILED 9




---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets