[tickets] [opensaf:tickets] #2160 fm: Add support for differentiating a hung node versus a stopped node

2016-11-04 Thread Hans Nordebäck
the implementation dosen't modify the opensafd script to lock and unlock the 
clm node, instead fm checks via IMM the saClmNodeIsMember attribute, if member 
is true, fencing will be performed. Changing clm admin state requires modifying 
start and stop functions in opensafd script, but e.g. immfind, immadm et.al 
commands may not yet be installed when opensafd start runs. 



---

** [tickets:#2160] fm: Add support for differentiating a hung node versus a 
stopped node **

**Status:** review
**Milestone:** 5.2.FC
**Created:** Wed Nov 02, 2016 11:37 AM UTC by Hans Nordebäck
**Last Updated:** Fri Nov 04, 2016 01:06 PM UTC
**Owner:** Hans Nordebäck


At opensafd stop, OpenSAF don't differentiate between a hung node and a stopped 
node.
This ticket will implement the suggestion by AndersW from ticket [#2094], to:
1). modify the opensafd script to lock the node using CLM. The CLM lock admin 
operation will remove the node from cluster membership.
2).fm_main will then be able to differentiate between a hung node and a stopped 
node by checking the node for CLM cluster membership.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


[tickets] [opensaf:tickets] #2160 fm: Add support for differentiating a hung node versus a stopped node

2016-11-04 Thread Hans Nordebäck
- **status**: assigned --> review



---

** [tickets:#2160] fm: Add support for differentiating a hung node versus a 
stopped node **

**Status:** review
**Milestone:** 5.2.FC
**Created:** Wed Nov 02, 2016 11:37 AM UTC by Hans Nordebäck
**Last Updated:** Wed Nov 02, 2016 11:37 AM UTC
**Owner:** Hans Nordebäck


At opensafd stop, OpenSAF don't differentiate between a hung node and a stopped 
node.
This ticket will implement the suggestion by AndersW from ticket [#2094], to:
1). modify the opensafd script to lock the node using CLM. The CLM lock admin 
operation will remove the node from cluster membership.
2).fm_main will then be able to differentiate between a hung node and a stopped 
node by checking the node for CLM cluster membership.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


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

2016-11-04 Thread Mathi Naickan
This scenario is related to cluster startup. It is quite possible that a node 
(old) that went down is still in the progress of going down(due to big 
application termination timeouts) and such a node could well be a controller 
node.

I think what has to be done is that RDE should lookout for the presence of such 
slow (stranded?) node and should fail the opensafd startup by returning failure 
to NID.
One way to detect such slow nodes is to make RDE subscribe for AMFD and during 
node startup if RDE determines to become ACTIVE but receives an AMFD MDS UP 
event from a node where no peer RDE is running, then RDE can return failure to 
NID.



---

** [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:** Tue Nov 01, 2016 10:49 AM UTC
**Owner:** nobody


Steps to reproduce:
1. Start two controllers(SC-1 Act, SC-2 Standby) and two paylods. Configure 50 
components on SC-2 and unlock them. Keep 1 sec delay in each component stop 
script.
2. Stop SC-1 and after that, stop SC-2.
3. During SC-2 is going down, start SC-1.

Observed behaviour:
Since components are taking time in stopping all components during 'opensad 
stop' of SC-2, Amfnd hasn't exited. But, all middleware components assignments 
are stopped. Only Amfnd and Amfd is alive with few more components to stop.
But SC-1 has come up till Amfd and since two Amfd is Act now, so SC-2 Amfd 
exits by saying "Duplicate ACTIVE detected, exiting".
Till this time, services states including Amfd is in bad state as they couldn't 
differentiate whether it is headless state or failover. This is true also as 
the system is in half middle of headless and failover.


Expected behaviour
In my view:
FMS should stop and shouldn't proceed if peer is going down. i.e. FMS should 
figure out on SC-1 that the peer system is going down. And should allow SC-1 
only if all services are down i.e. it gets node down (may be cb->immd_down && 
cb->immnd_down && cb->amfnd_down && cb->amfd_down && cb->fm_down).





---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


[tickets] [opensaf:tickets] #2153 smf: Fails to create a node group, admin owner/handle is lost

2016-11-04 Thread elunlen
- Description has changed:

Diff:



--- old
+++ new
@@ -1,2 +1 @@
 Even though handles and admin owner needed to create a node group is created 
just before the node group shall be created the creation may still fail because 
of bad handle or missing admin owner. To increase robustness a mechanism for 
recreation of handles and admin owner similar to handling when deleting a node 
group should be implemented.
-Also, the admin owner name must be unique per instance of the 
SmfAdminOperation class in order to be thread safe. Becoming admin owner may 
fail because already exist






---

** [tickets:#2153] smf: Fails to create a node group, admin owner/handle is 
lost**

**Status:** accepted
**Milestone:** 5.1.1
**Created:** Mon Oct 31, 2016 02:54 PM UTC by elunlen
**Last Updated:** Thu Nov 03, 2016 01:15 PM UTC
**Owner:** elunlen


Even though handles and admin owner needed to create a node group is created 
just before the node group shall be created the creation may still fail because 
of bad handle or missing admin owner. To increase robustness a mechanism for 
recreation of handles and admin owner similar to handling when deleting a node 
group should be implemented.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


[tickets] [opensaf:tickets] #248 "amf: Incorrect return code from saAmfComponentErrorReport_4 () and saAmfComponentErrorClear_4()".

2016-11-04 Thread Nagendra Kumar
- **status**: unassigned --> accepted
- **assigned_to**: Nagendra Kumar
- **Part**: - --> lib
- **Milestone**: future --> 5.2.FC



---

** [tickets:#248] "amf: Incorrect return code from saAmfComponentErrorReport_4 
() and saAmfComponentErrorClear_4()". **

**Status:** accepted
**Milestone:** 5.2.FC
**Created:** Thu May 16, 2013 06:41 AM UTC by Praveen
**Last Updated:** Thu Aug 06, 2015 11:07 AM UTC
**Owner:** Nagendra Kumar


Migrated from http://devel.opensaf.org/ticket/2817.

Changeset:3728
 When saAmfComponentErrorReport_4() and saAmfComponentErrorReport_4() are 
called after finalizing the amfHandle(calling saAmfFinalize()), both of them 
returns SA_AIS_ERR_VERSION instead of SA_AIS_ERR_BAD_HANDLE.



---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


[tickets] [opensaf:tickets] #251 amf: saAmResponse_4() does not return ERR_NOT_EXIST when called with invalid invocation parameter.

2016-11-04 Thread Nagendra Kumar
- **status**: accepted --> review



---

** [tickets:#251] amf: saAmResponse_4() does not return ERR_NOT_EXIST when 
called with invalid invocation parameter.**

**Status:** review
**Milestone:** 5.2.FC
**Created:** Thu May 16, 2013 06:46 AM UTC by Praveen
**Last Updated:** Fri Nov 04, 2016 10:04 AM UTC
**Owner:** Nagendra Kumar


Migrated from http://devel.opensaf.org/ticket/2815.

Changeset:3728
 When saAmfResponse_4() is called with invalid value of SaInvocationT (say 19), 
it returns SA_AIS_ERR_INVALID_PARAM. According to AMF spec (B.04.01, section 
7.13.1, page 335), return code should be SA_AIS_ERR_NOT_EXIST.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


[tickets] [opensaf:tickets] #251 amf: saAmResponse_4() does not return ERR_NOT_EXIST when called with invalid invocation parameter.

2016-11-04 Thread Nagendra Kumar
- **status**: unassigned --> accepted
- **assigned_to**: Nagendra Kumar
- **Part**: - --> lib
- **Milestone**: future --> 5.2.FC



---

** [tickets:#251] amf: saAmResponse_4() does not return ERR_NOT_EXIST when 
called with invalid invocation parameter.**

**Status:** accepted
**Milestone:** 5.2.FC
**Created:** Thu May 16, 2013 06:46 AM UTC by Praveen
**Last Updated:** Thu Aug 06, 2015 11:06 AM UTC
**Owner:** Nagendra Kumar


Migrated from http://devel.opensaf.org/ticket/2815.

Changeset:3728
 When saAmfResponse_4() is called with invalid value of SaInvocationT (say 19), 
it returns SA_AIS_ERR_INVALID_PARAM. According to AMF spec (B.04.01, section 
7.13.1, page 335), return code should be SA_AIS_ERR_NOT_EXIST.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


[tickets] [opensaf:tickets] #252 amf: saAmfPmStart_3() returns SA_AIS_ERR_ACCESS when called with invalid recovery.

2016-11-04 Thread Nagendra Kumar
- **status**: accepted --> review



---

** [tickets:#252] amf: saAmfPmStart_3() returns SA_AIS_ERR_ACCESS when called 
with invalid recovery.**

**Status:** review
**Milestone:** 5.2.FC
**Created:** Thu May 16, 2013 06:49 AM UTC by Praveen
**Last Updated:** Fri Nov 04, 2016 09:52 AM UTC
**Owner:** Nagendra Kumar


Migrated from http://devel.opensaf.org/ticket/2813.
Changeset:3728
 When saAmfPmStart_3() is called with invalid value of 
SaAmfRecommendedRecoveryT (say 19), it returns SA_AIS_ERR_ACCESS instead of 
SA_AIS_ERR_INVALID_PARAM. SA_AIS_ERR_ACCESS should be returned when AMF rejects 
recommended recovery from functionality perspective and should not returned as 
validation check.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


[tickets] [opensaf:tickets] #252 amf: saAmfPmStart_3() returns SA_AIS_ERR_ACCESS when called with invalid recovery.

2016-11-04 Thread Nagendra Kumar
- **status**: unassigned --> accepted
- **assigned_to**: Nagendra Kumar
- **Part**: - --> lib
- **Milestone**: future --> 5.2.FC
- **Comment**:

As per SAI-AIS-CPROG-B.05.01.pdf:
SA_AIS_ERR_ACCESS - Access is denied due to a reason other than a security 
violation.
SA_AIS_ERR_INVALID_PARAM - A parameter is not set correctly.

SA_AIS_ERR_ACCESS was added after Amf Specs B 3.1 onwards and is not available 
in B1.1.
Some explanation is there in B3.1:
The Availability Management Framework validates the recommended recovery action
in an implementation-dependent way. This could be done, for example, by putting 
in
place security measures like access control and authentication schemes. If the 
validation
succeeds, the Availability Management Framework will not implement a
weaker recovery action than the recommended one; however, the Availability 
Management
Framework may decide to implement a stronger recovery action based on
its recovery escalation policy. If the validation fails, the Availability 
Management
Framework rejects the error report with the return code SA_AIS_ERR_ACCESS
unless the recommended recovery action is SA_AMF_NO_RECOMMENDATION.

So, Amf can return ERR_ACCESS if the recommended recovery is not valid.
But again it is how we implement it.

So, my suggestion is to close this ticket by marking invalid. Please throw your 
suggestion within 5 days.




---

** [tickets:#252] amf: saAmfPmStart_3() returns SA_AIS_ERR_ACCESS when called 
with invalid recovery.**

**Status:** accepted
**Milestone:** 5.2.FC
**Created:** Thu May 16, 2013 06:49 AM UTC by Praveen
**Last Updated:** Thu Aug 06, 2015 11:06 AM UTC
**Owner:** Nagendra Kumar


Migrated from http://devel.opensaf.org/ticket/2813.
Changeset:3728
 When saAmfPmStart_3() is called with invalid value of 
SaAmfRecommendedRecoveryT (say 19), it returns SA_AIS_ERR_ACCESS instead of 
SA_AIS_ERR_INVALID_PARAM. SA_AIS_ERR_ACCESS should be returned when AMF rejects 
recommended recovery from functionality perspective and should not returned as 
validation check.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


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

2016-11-04 Thread Long HB Nguyen



---

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

**Status:** unassigned
**Milestone:** 5.0.2
**Created:** Fri Nov 04, 2016 09:45 AM UTC by Long HB Nguyen
**Last Updated:** Fri Nov 04, 2016 09:45 AM UTC
**Owner:** nobody
**Attachments:**

- 
[osaftestLog-2016-11-04_14-55-08.tgz](https://sourceforge.net/p/opensaf/tickets/2169/attachment/osaftestLog-2016-11-04_14-55-08.tgz)
 (1.2 MB; application/x-gzip-compressed)


- Description:
When a proxy component restart is escalated to a su restart, then the SU is not 
working properly after that (e.g. lock failed).

- Reproduction:
1) Use the proxy demo in amf samples.
2) Unlock-in/unlock proxy SU, proxied SU.
3) Kill the proxy process some times to take the recovery escalation from comp 
restart to su restart.
4) Lock the proxy SU => timeout.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


[tickets] [opensaf:tickets] #340 amf: AMF API error logging is non existent

2016-11-04 Thread Nagendra Kumar
- **status**: unassigned --> review
- **assigned_to**: Mathi Naickan --> Nagendra Kumar
- **Part**: - --> nd
- **Milestone**: future --> 5.2.FC



---

** [tickets:#340] amf: AMF API error logging is non existent**

**Status:** review
**Milestone:** 5.2.FC
**Created:** Mon May 27, 2013 05:54 AM UTC by Praveen
**Last Updated:** Wed Jan 13, 2016 06:02 AM UTC
**Owner:** Nagendra Kumar


Migrated from http://devel.opensaf.org/ticket/2461.

For example when an application does saAmfHealthcheckStart() with an invalid 
parameter, amfnd does not log (or trace for that matter!) anything.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


[tickets] [opensaf:tickets] #2163 smf: monitor changes of IMM config object

2016-11-04 Thread elunlen
- **status**: unassigned --> duplicate
- **Comment**:

See ticket [#2139]



---

** [tickets:#2163] smf: monitor changes of IMM config object**

**Status:** duplicate
**Milestone:** 5.2.FC
**Created:** Thu Nov 03, 2016 12:26 PM UTC by elunlen
**Last Updated:** Thu Nov 03, 2016 12:26 PM UTC
**Owner:** nobody


SMF needs to know if long dn is enabled. This setting is owned by IMM
Implement an IMM applier in order to know when changes of long dn setting is 
done instead of reading the setting in many places. Remove the cb global 
variable where this setting is saved internally in SMF


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


[tickets] [opensaf:tickets] #2168 log: test case logtest 5 3 failed

2016-11-04 Thread Canh Truong
- **summary**: log:  --> log: test case logtest 5 3 failed
- Description has changed:

Diff:



--- old
+++ new
@@ -1,3 +1,3 @@
 In branches 5.0.x and 5.1.x, test case logtest 5 3 failed
 
-Before verifing if the directory and subdirectly are created successfully, we 
sleep in 100ms to make sure the cbb appcallback makes new directory. This time 
is too small and cause the test case failed.
+Before verifing if the directory and subdirectly are created successfully, we 
sleep in 100ms to make sure the cbb appcallback makes new directory. This time 
is too small and may cause the test case failed.






---

** [tickets:#2168] log: test case logtest 5 3 failed**

**Status:** unassigned
**Milestone:** 5.0.2
**Created:** Fri Nov 04, 2016 07:52 AM UTC by Canh Truong
**Last Updated:** Fri Nov 04, 2016 07:52 AM UTC
**Owner:** nobody


In branches 5.0.x and 5.1.x, test case logtest 5 3 failed

Before verifing if the directory and subdirectly are created successfully, we 
sleep in 100ms to make sure the cbb appcallback makes new directory. This time 
is too small and may cause the test case failed.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


[tickets] [opensaf:tickets] #2168 log:

2016-11-04 Thread Canh Truong



---

** [tickets:#2168] log: **

**Status:** unassigned
**Milestone:** 5.0.2
**Created:** Fri Nov 04, 2016 07:52 AM UTC by Canh Truong
**Last Updated:** Fri Nov 04, 2016 07:52 AM UTC
**Owner:** nobody


In branches 5.0.x and 5.1.x, test case logtest 5 3 failed

Before verifing if the directory and subdirectly are created successfully, we 
sleep in 100ms to make sure the cbb appcallback makes new directory. This time 
is too small and cause the test case failed.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets