[tickets] [opensaf:tickets] #1526 imm: exit the 1PBE when pbeBeginTrans sees db as locked

Question: How can this case happen for the 1PBE case when there is only one user thread using the sqlite instance ? Another relevant question is why/when do you observe this now ? The test case or test setup must be special somehow. With only one thread this case should be impossible. It

[tickets] [opensaf:tickets] #1526 imm: exit the 1PBE when pbeBeginTrans sees db as locked

I looked at the code and the error message is correct but the "lock" is the PBE "spin lock" created for handling 2PBE. The fact that it finds it locked in 1PBE means there is a logical bug somewhere in 1PBE. Most likely some error case where there is a bailout from commit processing without

[tickets] [opensaf:tickets] #1526 imm: exit the 1PBE when pbeBeginTrans sees db as locked

- **summary**: imm: abort the 1PBE when pbeBeginTrans sees db as locked --> imm: exit the 1PBE when pbeBeginTrans sees db as locked - **status**: accepted --> review --- ** [tickets:#1526] imm: exit the 1PBE when pbeBeginTrans sees db as locked** **Status:** review **Milestone:** 4.5.2

[tickets] [opensaf:tickets] #1529 Opensaf cluster went for reset wihle invoking failover

- **Milestone**: 4.7.RC1 --> future --- ** [tickets:#1529] Opensaf cluster went for reset wihle invoking failover** **Status:** unassigned **Milestone:** future **Created:** Thu Oct 08, 2015 07:53 AM UTC by Chani Srivastava **Last Updated:** Thu Oct 08, 2015 07:53 AM UTC **Owner:** nobody

[tickets] [opensaf:tickets] #1526 imm: exit the 1PBE when pbeBeginTrans sees db as locked

I guess it could be that the pbe level message "Sqlite db locked by other thread" is plain wrong, i.e. missleading. --- ** [tickets:#1526] imm: exit the 1PBE when pbeBeginTrans sees db as locked** **Status:** review **Milestone:** 4.5.2 **Created:** Wed Oct 07, 2015 09:43 AM UTC by

[tickets] [opensaf:tickets] #1529 Opensaf cluster went for reset wihle invoking failover

--- ** [tickets:#1529] Opensaf cluster went for reset wihle invoking failover** **Status:** unassigned **Milestone:** 4.7.RC1 **Created:** Thu Oct 08, 2015 07:53 AM UTC by Chani Srivastava **Last Updated:** Thu Oct 08, 2015 07:53 AM UTC **Owner:** nobody **Attachments:** -

[tickets] [opensaf:tickets] #1526 imm: 1PBE can see db as locked

- **summary**: imm: exit the 1PBE when pbeBeginTrans sees db as locked --> imm: 1PBE can see db as locked - **Comment**: Changed ticket slogan to describe the problem. --- ** [tickets:#1526] imm: 1PBE can see db as locked** **Status:** review **Milestone:** 4.5.2 **Created:** Wed Oct 07,

[tickets] [opensaf:tickets] #1519 log: The log notice message should be informative

- **Comment**: Also, it is better to use PRIx64 while printing MDS addresses. The output will be more readable, i guess. --- ** [tickets:#1519] log: The log notice message should be informative** **Status:** unassigned **Milestone:** 5.0 **Created:** Tue Oct 06, 2015 09:18 AM UTC by

[tickets] [opensaf:tickets] #1518 AMF: SU presence state transition is not correct during admin op restart

- **Milestone**: 4.5.2 --> 4.7.RC1 --- ** [tickets:#1518] AMF: SU presence state transition is not correct during admin op restart** **Status:** unassigned **Milestone:** 4.7.RC1 **Created:** Tue Oct 06, 2015 07:41 AM UTC by Quyen Dao **Last Updated:** Thu Oct 08, 2015 10:16 AM UTC

[tickets] [opensaf:tickets] #1517 AMF : si-si deps not followed during SU restart

- **Milestone**: 4.5.2 --> 4.7.RC1 --- ** [tickets:#1517] AMF : si-si deps not followed during SU restart** **Status:** unassigned **Milestone:** 4.7.RC1 **Created:** Tue Oct 06, 2015 06:55 AM UTC by Srikanth R **Last Updated:** Tue Oct 06, 2015 07:12 AM UTC **Owner:** nobody Changeset :

[tickets] [opensaf:tickets] #1531 LOG: Improve handling of OI implementer create and restore

--- ** [tickets:#1531] LOG: Improve handling of OI implementer create and restore** **Status:** assigned **Milestone:** 5.0 **Created:** Thu Oct 08, 2015 11:14 AM UTC by elunlen **Last Updated:** Thu Oct 08, 2015 11:14 AM UTC **Owner:** elunlen Setting up IMM Object Implementer (OI) is not

[tickets] [opensaf:tickets] #1518 AMF: SU presence state transition is not correct during admin op restart

On page 74 for Prescence state of Component spec says, when a restartable component is instantiated, it will move from restarting to Instantiated state. Thus for a restartable SU, when last comp is started terminating, SU will move to RESTARTING state. At this point of time all the component

[tickets] [opensaf:tickets] #1530 AMF : TwoN, SU struck in terminating during sponsor si lock ( csi quiescd timeout)

Configuration to create AMF application is attached Attachments: - [1530_twon.sh](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/022eb6bb/24a1/attachment/1530_twon.sh) (9.7 kB; application/x-shellscript) --- ** [tickets:#1530] AMF : TwoN, SU struck in terminating during sponsor

[tickets] [opensaf:tickets] #1530 AMF : TwoN, SU struck in terminating during sponsor si lock ( csi quiescd timeout)

--- ** [tickets:#1530] AMF : TwoN, SU struck in terminating during sponsor si lock ( csi quiescd timeout)** **Status:** unassigned **Milestone:** 4.5.2 **Created:** Thu Oct 08, 2015 09:52 AM UTC by Srikanth R **Last Updated:** Thu Oct 08, 2015 09:52 AM UTC **Owner:** nobody Changeset :

[tickets] [opensaf:tickets] #1519 log: The log notice message should be informative

It also looks like there is a superfluous "x" character printed after the MDS destination. The "x" character after PRIu64 should be removed: LOG_NO("Send of WRITE ack to %"PRIu64"x FAILED: %u", mds_dest, rc); --- ** [tickets:#1519] log: The log notice message should be

[tickets] [opensaf:tickets] #1531 LOG: Improve handling of OI implementer create and restore

Will fix [#585] --- ** [tickets:#1531] LOG: Improve handling of OI implementer create and restore** **Status:** assigned **Milestone:** 5.0 **Created:** Thu Oct 08, 2015 11:14 AM UTC by elunlen **Last Updated:** Thu Oct 08, 2015 11:14 AM UTC **Owner:** elunlen Setting up IMM Object

[tickets] [opensaf:tickets] #1516 AMF : si-swap operation in nway should honor saAmfSGMaxStandbySIsperSU

- **Milestone**: 4.5.2 --> 4.7.RC1 --- ** [tickets:#1516] AMF : si-swap operation in nway should honor saAmfSGMaxStandbySIsperSU ** **Status:** unassigned **Milestone:** 4.7.RC1 **Created:** Mon Oct 05, 2015 12:59 PM UTC by Srikanth R **Last Updated:** Wed Oct 07, 2015 04:29 AM UTC

[tickets] [opensaf:tickets] #1532 AMF : SI is in assigned state, after shutdown operation of SI ( quiescing reject scenario)

--- ** [tickets:#1532] AMF : SI is in assigned state, after shutdown operation of SI ( quiescing reject scenario)** **Status:** unassigned **Milestone:** 4.5.2 **Created:** Thu Oct 08, 2015 11:20 AM UTC by Srikanth R **Last Updated:** Thu Oct 08, 2015 11:20 AM UTC **Owner:** nobody

[tickets] [opensaf:tickets] #1420 log: crashed when performing admin op on configurable obj class

- **Type**: enhancement --> defect --- ** [tickets:#1420] log: crashed when performing admin op on configurable obj class** **Status:** review **Milestone:** 4.5.2 **Created:** Thu Jul 16, 2015 09:28 AM UTC by Vu Minh Nguyen **Last Updated:** Tue Sep 29, 2015 07:56 AM UTC **Owner:** Vu Minh

[tickets] [opensaf:tickets] #1420 log: crashed when performing admin op on configurable obj class

- **status**: review --> fixed - **assigned_to**: Vu Minh Nguyen --> nobody - **Comment**: changeset: 6985:f9f8e549f071 tag: tip parent: 6980:f133f1195bc2 user:Vu Minh Nguyen date:Thu Oct 08 15:46:12 2015 +0200 summary: log:

[tickets] [opensaf:tickets] #509 reource leak when cpnd restarts and the application finalizes the checkpoint handles

The problem doesn't happen on the latest changeset. According to the log, the problem happened because the ckpt_lcl_ref_cnt was still 1 after the application on PL4 finalized Jul 17 17:18:07.958259 osafckptnd [13885:cpnd_evt.c:0540] T1 cpnd client ckpt close success