[tickets] [opensaf:tickets] #624 IMM: Many immomtest cases fail incorrectly if 2PBE is enabled.

2014-01-27 Thread Zoran Milinkovic
- **status**: review -- fixed



---

** [tickets:#624] IMM: Many immomtest cases fail incorrectly if 2PBE is 
enabled.**

**Status:** fixed
**Created:** Tue Nov 12, 2013 01:48 PM UTC by Anders Bjornerstedt
**Last Updated:** Tue Jan 21, 2014 12:18 PM UTC
**Owner:** Zoran Milinkovic

Most testcases for immomtest fail executed on a system with 2PBE enabled.
The reason is that immomtest heavily depends on the OpenSAF IMM service object:

opensafImm=opensafImm,safApp=safImmService

2PBE sets admin-owner for this object to 'safImmService', which seems to 
conflict with some tests that attempt to set the admin-woner to a test value.
In addition, 2PBE creates two runtime objects as children to this object.
This seems to trip up tests that use a scope of SA_IMM_SUBTREE for some operatin
and expects to hit just one object. 

The second problem could possibly be fixed by changing scope to SA_IMM_ONE,
but more fundamentally it is wrong that these tests rely on and operate on
official imm service objects. The tests should only operate on test objects
set up by these tests. This to insulate them from changes in the implementation
of the imm service. 


---

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.--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments  Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


[tickets] [opensaf:tickets] #624 IMM: Many immomtest cases fail incorrectly if 2PBE is enabled.

2014-01-27 Thread Zoran Milinkovic
opensaf-4.4.x:

changeset:   4848:5baf042cd19a
branch:  opensaf-4.4.x
parent:  4846:59acee1edebc
user:Zoran Milinkovic zoran.milinko...@ericsson.com
date:Tue Jan 21 13:09:20 2014 +0100
summary: IMMTEST: fix IMM tests if 2PBE is enabled [#624]

-

default(4.5):

changeset:   4849:20e0dd43e2e1
tag: tip
parent:  4847:cbd072502096
user:Zoran Milinkovic zoran.milinko...@ericsson.com
date:Tue Jan 21 13:09:20 2014 +0100
summary: IMMTEST: fix IMM tests if 2PBE is enabled [#624]



---

** [tickets:#624] IMM: Many immomtest cases fail incorrectly if 2PBE is 
enabled.**

**Status:** fixed
**Created:** Tue Nov 12, 2013 01:48 PM UTC by Anders Bjornerstedt
**Last Updated:** Tue Jan 21, 2014 12:18 PM UTC
**Owner:** Zoran Milinkovic

Most testcases for immomtest fail executed on a system with 2PBE enabled.
The reason is that immomtest heavily depends on the OpenSAF IMM service object:

opensafImm=opensafImm,safApp=safImmService

2PBE sets admin-owner for this object to 'safImmService', which seems to 
conflict with some tests that attempt to set the admin-woner to a test value.
In addition, 2PBE creates two runtime objects as children to this object.
This seems to trip up tests that use a scope of SA_IMM_SUBTREE for some operatin
and expects to hit just one object. 

The second problem could possibly be fixed by changing scope to SA_IMM_ONE,
but more fundamentally it is wrong that these tests rely on and operate on
official imm service objects. The tests should only operate on test objects
set up by these tests. This to insulate them from changes in the implementation
of the imm service. 


---

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.--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments  Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


[tickets] [opensaf:tickets] #624 IMM: Many immomtest cases fail incorrectly if 2PBE is enabled.

2014-01-21 Thread Zoran Milinkovic
https://sourceforge.net/p/opensaf/mailman/message/31869147/


---

** [tickets:#624] IMM: Many immomtest cases fail incorrectly if 2PBE is 
enabled.**

**Status:** review
**Created:** Tue Nov 12, 2013 01:48 PM UTC by Anders Bjornerstedt
**Last Updated:** Thu Jan 16, 2014 11:15 AM UTC
**Owner:** Zoran Milinkovic

Most testcases for immomtest fail executed on a system with 2PBE enabled.
The reason is that immomtest heavily depends on the OpenSAF IMM service object:

opensafImm=opensafImm,safApp=safImmService

2PBE sets admin-owner for this object to 'safImmService', which seems to 
conflict with some tests that attempt to set the admin-woner to a test value.
In addition, 2PBE creates two runtime objects as children to this object.
This seems to trip up tests that use a scope of SA_IMM_SUBTREE for some operatin
and expects to hit just one object. 

The second problem could possibly be fixed by changing scope to SA_IMM_ONE,
but more fundamentally it is wrong that these tests rely on and operate on
official imm service objects. The tests should only operate on test objects
set up by these tests. This to insulate them from changes in the implementation
of the imm service. 


---

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.--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments  Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


[tickets] [opensaf:tickets] #624 IMM: Many immomtest cases fail incorrectly if 2PBE is enabled.

2014-01-08 Thread Anders Bjornerstedt
- **status**: accepted -- assigned
- **assigned_to**: Anders Bjornerstedt -- Zoran Milinkovic



---

** [tickets:#624] IMM: Many immomtest cases fail incorrectly if 2PBE is 
enabled.**

**Status:** assigned
**Created:** Tue Nov 12, 2013 01:48 PM UTC by Anders Bjornerstedt
**Last Updated:** Tue Dec 17, 2013 12:34 PM UTC
**Owner:** Zoran Milinkovic

Most testcases for immomtest fail executed on a system with 2PBE enabled.
The reason is that immomtest heavily depends on the OpenSAF IMM service object:

opensafImm=opensafImm,safApp=safImmService

2PBE sets admin-owner for this object to 'safImmService', which seems to 
conflict with some tests that attempt to set the admin-woner to a test value.
In addition, 2PBE creates two runtime objects as children to this object.
This seems to trip up tests that use a scope of SA_IMM_SUBTREE for some operatin
and expects to hit just one object. 

The second problem could possibly be fixed by changing scope to SA_IMM_ONE,
but more fundamentally it is wrong that these tests rely on and operate on
official imm service objects. The tests should only operate on test objects
set up by these tests. This to insulate them from changes in the implementation
of the imm service. 


---

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.--
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET,  PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


[tickets] [opensaf:tickets] #624 IMM: Many immomtest cases fail incorrectly if 2PBE is enabled.

2013-12-17 Thread Anders Bjornerstedt
Will also fix the problem that 'immomtest 1' fails due to API version
shift to A.2.13.


---

** [tickets:#624] IMM: Many immomtest cases fail incorrectly if 2PBE is 
enabled.**

**Status:** accepted
**Created:** Tue Nov 12, 2013 01:48 PM UTC by Anders Bjornerstedt
**Last Updated:** Tue Dec 03, 2013 09:41 AM UTC
**Owner:** Anders Bjornerstedt

Most testcases for immomtest fail executed on a system with 2PBE enabled.
The reason is that immomtest heavily depends on the OpenSAF IMM service object:

opensafImm=opensafImm,safApp=safImmService

2PBE sets admin-owner for this object to 'safImmService', which seems to 
conflict with some tests that attempt to set the admin-woner to a test value.
In addition, 2PBE creates two runtime objects as children to this object.
This seems to trip up tests that use a scope of SA_IMM_SUBTREE for some operatin
and expects to hit just one object. 

The second problem could possibly be fixed by changing scope to SA_IMM_ONE,
but more fundamentally it is wrong that these tests rely on and operate on
official imm service objects. The tests should only operate on test objects
set up by these tests. This to insulate them from changes in the implementation
of the imm service. 


---

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.--
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET,  PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


[tickets] [opensaf:tickets] #624 IMM: Many immomtest cases fail incorrectly if 2PBE is enabled.

2013-12-17 Thread Anders Bjornerstedt
- **status**: assigned -- accepted



---

** [tickets:#624] IMM: Many immomtest cases fail incorrectly if 2PBE is 
enabled.**

**Status:** accepted
**Created:** Tue Nov 12, 2013 01:48 PM UTC by Anders Bjornerstedt
**Last Updated:** Tue Dec 03, 2013 09:41 AM UTC
**Owner:** Anders Bjornerstedt

Most testcases for immomtest fail executed on a system with 2PBE enabled.
The reason is that immomtest heavily depends on the OpenSAF IMM service object:

opensafImm=opensafImm,safApp=safImmService

2PBE sets admin-owner for this object to 'safImmService', which seems to 
conflict with some tests that attempt to set the admin-woner to a test value.
In addition, 2PBE creates two runtime objects as children to this object.
This seems to trip up tests that use a scope of SA_IMM_SUBTREE for some operatin
and expects to hit just one object. 

The second problem could possibly be fixed by changing scope to SA_IMM_ONE,
but more fundamentally it is wrong that these tests rely on and operate on
official imm service objects. The tests should only operate on test objects
set up by these tests. This to insulate them from changes in the implementation
of the imm service. 


---

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.--
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET,  PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


[tickets] [opensaf:tickets] #624 IMM: Many immomtest cases fail incorrectly if 2PBE is enabled.

2013-12-03 Thread Anders Bjornerstedt
- **assigned_to**: Zoran Milinkovic -- Anders Bjornerstedt



---

** [tickets:#624] IMM: Many immomtest cases fail incorrectly if 2PBE is 
enabled.**

**Status:** assigned
**Created:** Tue Nov 12, 2013 01:48 PM UTC by Anders Bjornerstedt
**Last Updated:** Tue Nov 12, 2013 01:48 PM UTC
**Owner:** Anders Bjornerstedt

Most testcases for immomtest fail executed on a system with 2PBE enabled.
The reason is that immomtest heavily depends on the OpenSAF IMM service object:

opensafImm=opensafImm,safApp=safImmService

2PBE sets admin-owner for this object to 'safImmService', which seems to 
conflict with some tests that attempt to set the admin-woner to a test value.
In addition, 2PBE creates two runtime objects as children to this object.
This seems to trip up tests that use a scope of SA_IMM_SUBTREE for some operatin
and expects to hit just one object. 

The second problem could possibly be fixed by changing scope to SA_IMM_ONE,
but more fundamentally it is wrong that these tests rely on and operate on
official imm service objects. The tests should only operate on test objects
set up by these tests. This to insulate them from changes in the implementation
of the imm service. 


---

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.--
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET,  PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351iu=/4140/ostg.clktrk___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


[tickets] [opensaf:tickets] #624 IMM: Many immomtest cases fail incorrectly if 2PBE is enabled.

2013-11-12 Thread Anders Bjornerstedt



---

** [tickets:#624] IMM: Many immomtest cases fail incorrectly if 2PBE is 
enabled.**

**Status:** assigned
**Created:** Tue Nov 12, 2013 01:48 PM UTC by Anders Bjornerstedt
**Last Updated:** Tue Nov 12, 2013 01:48 PM UTC
**Owner:** Zoran Milinkovic

Most testcases for immomtest fail executed on a system with 2PBE enabled.
The reason is that immomtest heavily depends on the OpenSAF IMM service object:

opensafImm=opensafImm,safApp=safImmService

2PBE sets admin-owner for this object to 'safImmService', which seems to 
conflict with some tests that attempt to set the admin-woner to a test value.
In addition, 2PBE creates two runtime objects as children to this object.
This seems to trip up tests that use a scope of SA_IMM_SUBTREE for some operatin
and expects to hit just one object. 

The second problem could possibly be fixed by changing scope to SA_IMM_ONE,
but more fundamentally it is wrong that these tests rely on and operate on
official imm service objects. The tests should only operate on test objects
set up by these tests. This to insulate them from changes in the implementation
of the imm service. 


---

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.--
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most 
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231iu=/4140/ostg.clktrk___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets