[tickets] [opensaf:tickets] #152 LOG: remove dependency to shared file system

2013-12-13 Thread elunlen
- **status**: accepted -- review --- ** [tickets:#152] LOG: remove dependency to shared file system** **Status:** review **Created:** Mon May 13, 2013 11:51 AM UTC by elunlen **Last Updated:** Tue Oct 29, 2013 07:52 AM UTC **Owner:** elunlen Purpose: Make OpenSAF not depended on shared

[tickets] [opensaf:tickets] #650 build: Enable extra GCC error checking options

2013-12-13 Thread Anders Widell
- **status**: review -- fixed --- ** [tickets:#650] build: Enable extra GCC error checking options** **Status:** fixed **Created:** Fri Dec 06, 2013 03:41 PM UTC by Anders Widell **Last Updated:** Mon Dec 09, 2013 11:46 AM UTC **Owner:** Anders Widell For security reasons, as well as to

[tickets] [opensaf:tickets] #650 build: Enable extra GCC error checking options

2013-12-13 Thread Anders Widell
changeset: 4727:0b66b72951ae tag: tip user:Anders Widell anders.wid...@ericsson.com date:Fri Dec 13 12:50:00 2013 +0100 summary: build: Add extra GCC hardening compilation flags [#650] ID 0b66b72951ae866d48b23c4887565b1fc580b682 [staging:0b66b7] --- **

[tickets] [opensaf:tickets] #657 SMF component got faulted during middleware rollback from CS-4667 to CS-3796

2013-12-13 Thread Hrishikesh
--- ** [tickets:#657] SMF component got faulted during middleware rollback from CS-4667 to CS-3796** **Status:** unassigned **Created:** Fri Dec 13, 2013 11:59 AM UTC by Hrishikesh **Last Updated:** Fri Dec 13, 2013 11:59 AM UTC **Owner:** nobody Changeset of Opensaf 4.2 CS-3796,

[tickets] [opensaf:tickets] #658 logtrace syslogs when write fails

2013-12-13 Thread Hans Feldt
--- ** [tickets:#658] logtrace syslogs when write fails** **Status:** unassigned **Created:** Fri Dec 13, 2013 12:39 PM UTC by Hans Feldt **Last Updated:** Fri Dec 13, 2013 12:39 PM UTC **Owner:** nobody If out of disk this just adds to the problem: Nov 26 04:28:43 err osafamfnd[5160]:

[tickets] [opensaf:tickets] #658 logtrace syslogs when write fails

2013-12-13 Thread Hans Feldt
- **status**: unassigned -- review - **assigned_to**: Hans Feldt --- ** [tickets:#658] logtrace syslogs when write fails** **Status:** review **Created:** Fri Dec 13, 2013 12:39 PM UTC by Hans Feldt **Last Updated:** Fri Dec 13, 2013 12:39 PM UTC **Owner:** Hans Feldt If out of disk this

Re: [tickets] [opensaf:tickets] #657 SMF component got faulted during middleware rollback from CS-4667 to CS-3796

2013-12-13 Thread Bertil Engelholm
The problem seem to start here: Dec 13 12:19:56 SLES2-2 osafsmfd[2331]: ER amf_quiesced_state_handler oi deactivate FAILED SMF tries to clear the class implementors and something fails (no logging exactly what fails). And SMF is not reporting the failure to AMF so AMF tries to activate the other

[tickets] [opensaf:tickets] Re: #657 SMF component got faulted during middleware rollback from CS-4667 to CS-3796

2013-12-13 Thread Bertil Engelholm
The problem seem to start here: Dec 13 12:19:56 SLES2-2 osafsmfd[2331]: ER amf_quiesced_state_handler oi deactivate FAILED SMF tries to clear the class implementors and something fails (no logging exactly what fails). And SMF is not reporting the failure to AMF so AMF tries to activate the other

[tickets] [opensaf:tickets] #656 SMF: Call configured smfBundleCheckCmd as part of prerequisites test

2013-12-13 Thread Ingvar Bergström
- **status**: assigned -- review --- ** [tickets:#656] SMF: Call configured smfBundleCheckCmd as part of prerequisites test** **Status:** review **Created:** Fri Dec 13, 2013 07:47 AM UTC by Ingvar Bergström **Last Updated:** Fri Dec 13, 2013 07:47 AM UTC **Owner:** Ingvar Bergström SMF

Re: [tickets] [opensaf:tickets] #657 SMF component got faulted during middleware rollback from CS-4667 to CS-3796

2013-12-13 Thread Anders Björnerstedt
The most likely error code on an implementer-clear would be try-again. A brutal way to release implementers, which can not fail is to just finalize the OI-handle. Of course that typically means you also need to initialize a new OI handle if the process is to continue as some other

[tickets] [opensaf:tickets] Re: #657 SMF component got faulted during middleware rollback from CS-4667 to CS-3796

2013-12-13 Thread Anders Bjornerstedt
The most likely error code on an implementer-clear would be try-again. A brutal way to release implementers, which can not fail is to just finalize the OI-handle. Of course that typically means you also need to initialize a new OI handle if the process is to continue as some other

Re: [tickets] [opensaf:tickets] #657 SMF component got faulted during middleware rollback from CS-4667 to CS-3796

2013-12-13 Thread Anders Björnerstedt
Are you using ClassImplementerRelease ?!?!? That function should only be used in situations like schema-changes or major reorganizations/upgrades of software, where the long-term component ownership of an implementer-name shifts from one component-type to another. So the short answer is YES

[tickets] [opensaf:tickets] Re: #657 SMF component got faulted during middleware rollback from CS-4667 to CS-3796

2013-12-13 Thread Anders Bjornerstedt
Are you using ClassImplementerRelease ?!?!? That function should only be used in situations like schema-changes or major reorganizations/upgrades of software, where the long-term component ownership of an implementer-name shifts from one component-type to another. So the short answer is YES

Re: [tickets] [opensaf:tickets] #657 SMF component got faulted during middleware rollback from CS-4667 to CS-3796

2013-12-13 Thread Anders Björnerstedt
And yes saImmOiClassImplementerSet is idempotent. /AndersBj From: Anders Björnerstedt [mailto:anders.bjornerst...@ericsson.com] Sent: den 13 december 2013 15:04 To: Bertil Engelholm; Ticket 657; opensaf-tickets@lists.sourceforge.net Subject: Re: [tickets]

[tickets] [opensaf:tickets] Re: #657 SMF component got faulted during middleware rollback from CS-4667 to CS-3796

2013-12-13 Thread Anders Bjornerstedt
And yes saImmOiClassImplementerSet is idempotent. /AndersBj From: Anders Björnerstedt [mailto:anders.bjornerst...@ericsson.com] Sent: den 13 december 2013 15:04 To: Bertil Engelholm; Ticket 657; opensaf-tickets@lists.sourceforge.net Subject: Re: [tickets]

[tickets] [opensaf:tickets] #657 SMF component got faulted during middleware rollback from CS-4667 to CS-3796

2013-12-13 Thread Anders Bjornerstedt
In OpenSAF 4.3 and later. /AndersBj From: Anders Björnerstedt Sent: den 13 december 2013 15:06 To: Anders Björnerstedt; Bertil Engelholm; Ticket 657; opensaf-tickets@lists.sourceforge.net Subject: RE: [tickets] [opensaf:tickets] #657 SMF component got faulted

[tickets] [opensaf:tickets] #220 CLM should use CLMNA service DOWN event as additional evidence for node eviction

2013-12-13 Thread Mathi Naickan
changeset: 4728:ab2b366a8c21 user:Mathivanan N.P.mathi.naic...@oracle.com date:Fri Dec 13 22:57:23 2013 +0530 summary: clm: add clmna to the information model and update config, scripts [#220] changeset: 4729:394a781ed865 user:Mathivanan

[tickets] [opensaf:tickets] #220 CLM should use CLMNA service DOWN event as additional evidence for node eviction

2013-12-13 Thread Mathi Naickan
- **status**: review -- fixed - **assigned_to**: Mathi Naickan -- nobody --- ** [tickets:#220] CLM should use CLMNA service DOWN event as additional evidence for node eviction** **Status:** fixed **Labels:** componentize clmna '/etc/init.d/opensafd stop without OS reboot' **Created:** Wed