[tickets] [opensaf:tickets] #1456 imm: IMM object has different attribute value after reloading it from PBE

2015-10-01 Thread Anders Widell
- **Milestone**: 4.7.FC --> never --- ** [tickets:#1456] imm: IMM object has different attribute value after reloading it from PBE** **Status:** invalid **Milestone:** never **Created:** Fri Aug 21, 2015 01:05 PM UTC by Anders Widell **Last Updated:** Tue Aug 25, 2015 04:08 PM UTC **Owner:**

[tickets] [opensaf:tickets] #1456 imm: IMM object has different attribute value after reloading it from PBE

2015-08-24 Thread Anders Bjornerstedt
- **status**: unassigned -- invalid - **Milestone**: 4.5.2 -- 4.7-Tentative - **Comment**: This behavior is well documented in the immsv README (and should also be so in the IMMSV_PR) since OpenSAF4.3. It has worked this way since OpenSAF was created. My opinion is that the real problem is the

[tickets] [opensaf:tickets] #1456 imm: IMM object has different attribute value after reloading it from PBE

2015-08-21 Thread Anders Widell
--- ** [tickets:#1456] imm: IMM object has different attribute value after reloading it from PBE** **Status:** unassigned **Milestone:** 4.5.2 **Created:** Fri Aug 21, 2015 01:05 PM UTC by Anders Widell **Last Updated:** Fri Aug 21, 2015 01:05 PM UTC **Owner:** nobody There is a scenario