[tickets] [opensaf:tickets] #2169 amf: su containing proxy comps is not working properly after a su restart recovery

2016-11-08 Thread Nagendra Kumar
- **status**: review --> fixed - **Comment**: searching for changes changeset: 8294:88be3d560de2 branch: opensaf-5.0.x parent: 8291:578552651e82 user:Nagendra Kumar date:Wed Nov 09 11:38:02 2016 +0530 summary: amfnd: clean proxy if proxy and

[tickets] [opensaf:tickets] #2134 AMF: Update RTA saAmfSISUHAState to IMM

2016-11-08 Thread Praveen
Hi Minh, What I get is : With part 2 of #1725, updation to IMM becomes consistent in the existing manner. If this is the case, I agree to close this ticket. In that case please update #1354 and #2133 with this ticket link so that discussion can be recolleted in future. Thanks, Praveen ---

[tickets] [opensaf:tickets] #2169 amf: su containing proxy comps is not working properly after a su restart recovery

2016-11-08 Thread Nagendra Kumar
Yes. If proxy and proxied are in the same SU, then proxy need to be cleaned in the last as cleanup command of proxied is first given to proxy. If proxy are killed first then there will not be any way to kill proxied components. I assume you have acked the patch and I am going to push it. ---

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

2016-11-08 Thread 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]

[tickets] [opensaf:tickets] Re: #2134 AMF: Update RTA saAmfSISUHAState to IMM

2016-11-08 Thread Minh Hon Chau
Hi Praveen, Agree that if the *Curr* related attributes consider fsm state in rt_attr_cb(), then it would be suitable for reflecting the current status of assignment, which is required by user of #1354 The part 2 of #1725 has been pushed, that contains a change to update saAmfSISUHaState to

[tickets] [opensaf:tickets] #2134 AMF: Update RTA saAmfSISUHAState to IMM

2016-11-08 Thread Minh Hon Chau
Hi Praveen, Agree that if the *Curr* related attributes consider fsm state in rt_attr_cb(), then it would be suitable for reflecting the current status of assignment, which is required by user of #1354 The part 2 of #1725 has been pushed, that contains a change to update saAmfSISUHaState to

[tickets] [opensaf:tickets] #2175 amfd: null SU during CCB modify apply on standby director

2016-11-08 Thread Gary Lee
- **summary**: amfd: null SU during CCB modify apply --> amfd: null SU during CCB modify apply on standby director - Description has changed: Diff: --- old +++ new @@ -1,4 +1,4 @@ -su is NULL and subsequently causes a segfault. +su is NULL and subsequently causes a segfault on standby

[tickets] [opensaf:tickets] #2171 amfd: invalid reads reported by valgrind

2016-11-08 Thread Gary Lee
- **status**: unassigned --> fixed - **Milestone**: 5.1.1 --> 5.0.2 - **Comment**: changeset: 8290:f2bccfcd6622 branch: opensaf-5.0.x tag: tip parent: 8269:7abe0ea2cd18 user:Gary Lee date:Wed Nov 09 10:19:44 2016 +1100 summary:

[tickets] [opensaf:tickets] #2151 osaf: system in not in correct state during Act controller comming up

2016-11-08 Thread Ramesh
Based on the current implementation (functional) scope holding by different services of OpenSAF, introducing such functional behaviour into FM module seems more appropriate to handle the scenario. FM is been already in MDS subscription with AMFD, AMFND etc. However, this proposal is

[tickets] [opensaf:tickets] #2151 osaf: system in not in correct state during Act controller comming up

2016-11-08 Thread Ramesh
- **Type**: discussion --> enhancement --- ** [tickets:#2151] osaf: system in not in correct state during Act controller comming up** **Status:** unassigned **Milestone:** 5.2.FC **Created:** Mon Oct 31, 2016 10:54 AM UTC by Nagendra Kumar **Last Updated:** Fri Nov 04, 2016 12:33 PM UTC

[tickets] [opensaf:tickets] #2173 base: Add support classes for pthread mutexes and condition variables

2016-11-08 Thread Anders Widell
- **status**: accepted --> review --- ** [tickets:#2173] base: Add support classes for pthread mutexes and condition variables** **Status:** review **Milestone:** 5.2.FC **Created:** Mon Nov 07, 2016 11:59 AM UTC by Anders Widell **Last Updated:** Mon Nov 07, 2016 11:59 AM UTC **Owner:**

[tickets] [opensaf:tickets] #2179 AMF: Update PR/README for headless feature limitation

2016-11-08 Thread Minh Hon Chau
--- ** [tickets:#2179] AMF: Update PR/README for headless feature limitation** **Status:** assigned **Milestone:** 5.2.FC **Created:** Tue Nov 08, 2016 02:23 PM UTC by Minh Hon Chau **Last Updated:** Tue Nov 08, 2016 02:23 PM UTC **Owner:** Minh Hon Chau Update documents suggested by

[tickets] [opensaf:tickets] Re: #2094 Standby controller goes for reboot on stopping openSaf with STONITH enabled cluster

2016-11-08 Thread Srikanth R
For the scenario-2, -> Management software e.g. SWN other than opensafd issued reboot on standby controller. From opensaf perspecitve , the standby controller might be healthy member of a cluster. But from the SWN perspecitve, node needs to be repaired and reboot is invoked. -> When reboot

[tickets] [opensaf:tickets] #2094 Standby controller goes for reboot on stopping openSaf with STONITH enabled cluster

2016-11-08 Thread Hans Nordebäck
in a) doing /etc/init.d/opensafd stop doesn't reboot the node, but stops opensaf on that node and saClmNodeIsMember is set to false. The active controller will then not perform remote fencing of that node. in b) "graceful" reboot after opensafd stop, should work fine without any involvemnet of

[tickets] [opensaf:tickets] #1082 imm: add more display information to verbose output for ResourceDisplay

2016-11-08 Thread Neelakanta Reddy
- **status**: accepted --> assigned --- ** [tickets:#1082] imm: add more display information to verbose output for ResourceDisplay ** **Status:** assigned **Milestone:** future **Created:** Mon Sep 15, 2014 12:20 PM UTC by Neelakanta Reddy **Last Updated:** Tue Mar 08, 2016 05:04 AM UTC

[tickets] [opensaf:tickets] #1552 smf: read IMM_long_DN_config at the start of SmfCampaignInit function

2016-11-08 Thread Neelakanta Reddy
- **status**: unassigned --> duplicate - **Comment**: The problem is similar to #2087 AND #2119. --- ** [tickets:#1552] smf: read IMM_long_DN_config at the start of SmfCampaignInit function** **Status:** duplicate **Milestone:** 5.0.2 **Created:** Wed Oct 21, 2015 07:10 AM UTC by Neelakanta

[tickets] [opensaf:tickets] #2169 amf: su containing proxy comps is not working properly after a su restart recovery

2016-11-08 Thread Long HB Nguyen
Hi Nagu, I have tested the patch. It is working fine and the proxy component gets CLEANUP. In your patch, you have fixed for the case that Proxy and Proxied comp are not in the same SU. In the case, they are in the same SU, the behavior is different (i.e. still return immediately). Could you

[tickets] [opensaf:tickets] #1900 imm: Mention in docs that 2PBE cannot be used on systems with more than 2 SCs

2016-11-08 Thread Neelakanta Reddy
- **status**: unassigned --> duplicate - **Comment**: The IMM docs has been updated as part of #1925 +2PBE with spares(#79 & #1925) + +From OpenSAF 5.0 the mds_register for IMMD is delayed until amfd comes up and gives role. +Because of this the standby role is

[tickets] [opensaf:tickets] #2169 amf: su containing proxy comps is not working properly after a su restart recovery

2016-11-08 Thread Nagendra Kumar
- **status**: assigned --> review --- ** [tickets:#2169] amf: su containing proxy comps is not working properly after a su restart recovery** **Status:** review **Milestone:** 5.0.2 **Created:** Fri Nov 04, 2016 09:45 AM UTC by Long HB Nguyen **Last Updated:** Tue Nov 08, 2016 06:12 AM UTC

[tickets] [opensaf:tickets] #69 AMF support for saAmfSUMaintenanceCampaign

2016-11-08 Thread Praveen
- **status**: unassigned --> duplicate - **Milestone**: future --> never - **Comment**: Duplicate of newly raised ticket #2144. --- ** [tickets:#69] AMF support for saAmfSUMaintenanceCampaign** **Status:** duplicate **Milestone:** never **Created:** Mon May 13, 2013 04:11 AM UTC by Nagendra

[tickets] [opensaf:tickets] #1868 Headless: IMM: Cluster reset happened due to 'avaDown' while killing immd

2016-11-08 Thread Neelakanta Reddy
When the 2N middleware component si killed the following message will appear in syslog. Jun 8 15:44:07 SCALE_SLOT-81 osafamfnd[1863]: Rebooting OpenSAF NodeId = 131343 EE Name = , Reason: Component faulted: recovery is node failfast, OwnNodeId = 131343, SupervisionTime = 60 For SC1, SC2. SC3

[tickets] [opensaf:tickets] #2175 amfd: null SU during CCB modify apply

2016-11-08 Thread Gary Lee
- **status**: unassigned --> review - **assigned_to**: Gary Lee - **Component**: unknown --> amf - **Part**: - --> d --- ** [tickets:#2175] amfd: null SU during CCB modify apply** **Status:** review **Milestone:** 5.1.1 **Created:** Tue Nov 08, 2016 06:37 AM UTC by Gary Lee **Last Updated:**