[tickets] [opensaf:tickets] #20 IMMTOOLS: immcfg support for mixed changes in a transaction (CCB)
- **status**: assigned -- review --- ** [tickets:#20] IMMTOOLS: immcfg support for mixed changes in a transaction (CCB)** **Status:** review **Created:** Tue May 07, 2013 08:47 AM UTC by Zoran Milinkovic **Last Updated:** Tue May 07, 2013 08:47 AM UTC **Owner:** Zoran Milinkovic Today immcfg only support one type of change at a time (create, delete, modify). This makes more complicated changes fragile since they are not protected by an IMM CCB. A rather easy fix would be to have the immcfg read from stdin and add each line to the same CCB, and at end of file commit the CCB. Is is suggested that each line of input is of exactly the same syntax as the current command line. The change will be backwards compatible and just extend immcfg. Any comments on this idea? Migrated from: http://devel.opensaf.org/ticket/2437 --- 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.-- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #549 IMM: saImmOmAccessorGet_2 does not free object name
--- ** [tickets:#549] IMM: saImmOmAccessorGet_2 does not free object name** **Status:** unassigned **Created:** Wed Aug 21, 2013 11:51 AM UTC by Zoran Milinkovic **Last Updated:** Wed Aug 21, 2013 11:51 AM UTC **Owner:** Zoran Milinkovic saImmOmAccessorGet_2 does not free a memory allocated for an object name which causes a memory leak. --- 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.-- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #549 IMM: saImmOmAccessorGet_2 does not free object name
- **status**: unassigned -- review --- ** [tickets:#549] IMM: saImmOmAccessorGet_2 does not free object name** **Status:** review **Created:** Wed Aug 21, 2013 11:51 AM UTC by Zoran Milinkovic **Last Updated:** Wed Aug 21, 2013 11:51 AM UTC **Owner:** Zoran Milinkovic saImmOmAccessorGet_2 does not free a memory allocated for an object name which causes a memory leak. --- 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.-- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #552 IMMTEST: Clean up of imm test code
http://www.mail-archive.com/opensaf-devel@lists.sourceforge.net/msg00400.html --- ** [tickets:#552] IMMTEST: Clean up of imm test code** **Status:** review **Created:** Mon Aug 26, 2013 01:37 PM UTC by Zoran Milinkovic **Last Updated:** Mon Aug 26, 2013 01:37 PM UTC **Owner:** Zoran Milinkovic Today, running immomtest and immoitest using valgrind report many memory problems. The clean up of imm test code will fix the test code and will remove all valgrind reports. --- 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.-- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #549 IMM: memory leak in saImmOmAccessorGet_2
- **summary**: IMM: saImmOmAccessorGet_2 does not free object name -- IMM: memory leak in saImmOmAccessorGet_2 - Description has changed: Diff: --- old +++ new @@ -1 +1,2 @@ -saImmOmAccessorGet_2 does not free a memory allocated for an object name which causes a memory leak. +If saImmOmFinalize is called before saImmOmAccessorFinalize, it's possible to have a memory leak. +saImmOmAccessorGet_2 does not free a memory allocated for an object name which causes a memory leak (only in 4.4). - **status**: fixed -- accepted - **Version**: 4.4 -- 4.2.4 - **Milestone**: 4.4.FC -- 4.2.5 --- ** [tickets:#549] IMM: memory leak in saImmOmAccessorGet_2** **Status:** accepted **Created:** Wed Aug 21, 2013 11:51 AM UTC by Zoran Milinkovic **Last Updated:** Fri Aug 30, 2013 08:25 AM UTC **Owner:** Zoran Milinkovic If saImmOmFinalize is called before saImmOmAccessorFinalize, it's possible to have a memory leak. saImmOmAccessorGet_2 does not free a memory allocated for an object name which causes a memory leak (only in 4.4). --- 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.-- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #20 IMMTOOLS: immcfg support for mixed changes in a transaction (CCB)
default(4.4): changeset: 4469:452ebf8a4919 tag: tip user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Thu Sep 05 14:33:08 2013 +0200 summary: IMMTOOLS: add explicit commit mode to immcfg [#20] --- ** [tickets:#20] IMMTOOLS: immcfg support for mixed changes in a transaction (CCB)** **Status:** fixed **Created:** Tue May 07, 2013 08:47 AM UTC by Zoran Milinkovic **Last Updated:** Thu Jul 18, 2013 01:49 PM UTC **Owner:** Zoran Milinkovic Today immcfg only support one type of change at a time (create, delete, modify). This makes more complicated changes fragile since they are not protected by an IMM CCB. A rather easy fix would be to have the immcfg read from stdin and add each line to the same CCB, and at end of file commit the CCB. Is is suggested that each line of input is of exactly the same syntax as the current command line. The change will be backwards compatible and just extend immcfg. Any comments on this idea? Migrated from: http://devel.opensaf.org/ticket/2437 --- 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.-- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #20 IMMTOOLS: immcfg support for mixed changes in a transaction (CCB)
- **status**: review -- fixed --- ** [tickets:#20] IMMTOOLS: immcfg support for mixed changes in a transaction (CCB)** **Status:** fixed **Created:** Tue May 07, 2013 08:47 AM UTC by Zoran Milinkovic **Last Updated:** Thu Jul 18, 2013 01:49 PM UTC **Owner:** Zoran Milinkovic Today immcfg only support one type of change at a time (create, delete, modify). This makes more complicated changes fragile since they are not protected by an IMM CCB. A rather easy fix would be to have the immcfg read from stdin and add each line to the same CCB, and at end of file commit the CCB. Is is suggested that each line of input is of exactly the same syntax as the current command line. The change will be backwards compatible and just extend immcfg. Any comments on this idea? Migrated from: http://devel.opensaf.org/ticket/2437 --- 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.-- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #20 IMMTOOLS: immcfg support for mixed changes in a transaction (CCB)
The ticket is reopened. Hans pointed out that the patch fails to build on Ubuntu 13.04 because of missing libdl library in Makefile.am. http://www.mail-archive.com/opensaf-devel@lists.sourceforge.net/msg00461.html --- ** [tickets:#20] IMMTOOLS: immcfg support for mixed changes in a transaction (CCB)** **Status:** review **Created:** Tue May 07, 2013 08:47 AM UTC by Zoran Milinkovic **Last Updated:** Thu Sep 05, 2013 12:55 PM UTC **Owner:** Zoran Milinkovic Today immcfg only support one type of change at a time (create, delete, modify). This makes more complicated changes fragile since they are not protected by an IMM CCB. A rather easy fix would be to have the immcfg read from stdin and add each line to the same CCB, and at end of file commit the CCB. Is is suggested that each line of input is of exactly the same syntax as the current command line. The change will be backwards compatible and just extend immcfg. Any comments on this idea? Migrated from: http://devel.opensaf.org/ticket/2437 --- 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.-- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #20 IMMTOOLS: immcfg support for mixed changes in a transaction (CCB)
- **status**: fixed -- review --- ** [tickets:#20] IMMTOOLS: immcfg support for mixed changes in a transaction (CCB)** **Status:** review **Created:** Tue May 07, 2013 08:47 AM UTC by Zoran Milinkovic **Last Updated:** Thu Sep 05, 2013 12:55 PM UTC **Owner:** Zoran Milinkovic Today immcfg only support one type of change at a time (create, delete, modify). This makes more complicated changes fragile since they are not protected by an IMM CCB. A rather easy fix would be to have the immcfg read from stdin and add each line to the same CCB, and at end of file commit the CCB. Is is suggested that each line of input is of exactly the same syntax as the current command line. The change will be backwards compatible and just extend immcfg. Any comments on this idea? Migrated from: http://devel.opensaf.org/ticket/2437 --- 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.-- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #549 IMM: memory leak in saImmOmFinalize for non finalized accessors
OpenSAF 4.2 and 4.3: http://www.mail-archive.com/opensaf-devel@lists.sourceforge.net/msg00476.html --- ** [tickets:#549] IMM: memory leak in saImmOmFinalize for non finalized accessors** **Status:** review **Created:** Wed Aug 21, 2013 11:51 AM UTC by Zoran Milinkovic **Last Updated:** Tue Sep 03, 2013 09:39 AM UTC **Owner:** Zoran Milinkovic If saImmOmFinalize is called before saImmOmAccessorFinalize, it's possible to have a memory leak. saImmOmAccessorGet_2 does not free a memory allocated for an object name which causes a memory leak (only in 4.4). --- 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.-- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #20 IMMTOOLS: immcfg support for mixed changes in a transaction (CCB)
- **status**: review -- fixed --- ** [tickets:#20] IMMTOOLS: immcfg support for mixed changes in a transaction (CCB)** **Status:** fixed **Created:** Tue May 07, 2013 08:47 AM UTC by Zoran Milinkovic **Last Updated:** Fri Sep 06, 2013 03:29 PM UTC **Owner:** Zoran Milinkovic Today immcfg only support one type of change at a time (create, delete, modify). This makes more complicated changes fragile since they are not protected by an IMM CCB. A rather easy fix would be to have the immcfg read from stdin and add each line to the same CCB, and at end of file commit the CCB. Is is suggested that each line of input is of exactly the same syntax as the current command line. The change will be backwards compatible and just extend immcfg. Any comments on this idea? Migrated from: http://devel.opensaf.org/ticket/2437 --- 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.-- How ServiceNow helps IT people transform IT departments: 1. Consolidate legacy IT systems to a single system of record for IT 2. Standardize and globalize service processes across IT 3. Implement zero-touch automation to replace manual, redundant tasks http://pubads.g.doubleclick.net/gampad/clk?id=5127iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #549 IMM: memory leak in saImmOmFinalize for non finalized accessors
- **status**: review -- fixed --- ** [tickets:#549] IMM: memory leak in saImmOmFinalize for non finalized accessors** **Status:** fixed **Created:** Wed Aug 21, 2013 11:51 AM UTC by Zoran Milinkovic **Last Updated:** Mon Sep 09, 2013 02:03 PM UTC **Owner:** Zoran Milinkovic If saImmOmFinalize is called before saImmOmAccessorFinalize, it's possible to have a memory leak. saImmOmAccessorGet_2 does not free a memory allocated for an object name which causes a memory leak (only in 4.4). --- 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.-- How ServiceNow helps IT people transform IT departments: 1. Consolidate legacy IT systems to a single system of record for IT 2. Standardize and globalize service processes across IT 3. Implement zero-touch automation to replace manual, redundant tasks http://pubads.g.doubleclick.net/gampad/clk?id=5127iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #552 IMMTEST: Clean up of imm test code
The ticket is reopened. Add IMM tests cleanup code for OpenSAF 4.2 and 4.3 --- ** [tickets:#552] IMMTEST: Clean up of imm test code** **Status:** review **Created:** Mon Aug 26, 2013 01:37 PM UTC by Zoran Milinkovic **Last Updated:** Fri Aug 30, 2013 09:11 AM UTC **Owner:** Zoran Milinkovic Today, running immomtest and immoitest using valgrind report many memory problems. The clean up of imm test code will fix the test code and will remove all valgrind reports. --- 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.-- How ServiceNow helps IT people transform IT departments: 1. Consolidate legacy IT systems to a single system of record for IT 2. Standardize and globalize service processes across IT 3. Implement zero-touch automation to replace manual, redundant tasks http://pubads.g.doubleclick.net/gampad/clk?id=5127iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #552 IMMTEST: Clean up of imm test code
- **status**: review -- fixed --- ** [tickets:#552] IMMTEST: Clean up of imm test code** **Status:** fixed **Created:** Mon Aug 26, 2013 01:37 PM UTC by Zoran Milinkovic **Last Updated:** Thu Sep 12, 2013 09:19 AM UTC **Owner:** Zoran Milinkovic Today, running immomtest and immoitest using valgrind report many memory problems. The clean up of imm test code will fix the test code and will remove all valgrind reports. --- 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.-- LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #572 immcfg segfaults
http://www.mail-archive.com/opensaf-devel@lists.sourceforge.net/msg00559.html --- ** [tickets:#572] immcfg segfaults** **Status:** review **Created:** Fri Sep 20, 2013 07:07 AM UTC by Hans Feldt **Last Updated:** Mon Sep 23, 2013 01:11 PM UTC **Owner:** Zoran Milinkovic $ immcfg -f AppConfig-2N.xml Failed to call saImmOmAdminOwnerSet on parent: 'safAmfNode=SC-2,safAmfCluster=myAmfCluster' , rc = 12 Segmentation fault (core dumped) (gdb) bt #0 __strlen_sse2_pminub () at ../sysdeps/x86_64/multiarch/strlen-sse2-pminub.S:38 #1 0x004098b7 in createImmObject (state=state@entry=0x7fffd470) at imm_import.cc:666 #2 0x0040a635 in endElementHandler (userData=0x7fffd470, name=optimized out) at imm_import.cc:1508 #3 0x77abc81d in ?? () from /usr/lib/x86_64-linux-gnu/libxml2.so.2 #4 0x77ac3f69 in ?? () from /usr/lib/x86_64-linux-gnu/libxml2.so.2 #5 0x77ac4f86 in xmlParseChunk () from /usr/lib/x86_64-linux-gnu/libxml2.so.2 #6 0x0040864f in loadImmXML (xmlfile=xmlfile@entry=0x7fffe35b AppConfig-2N.xml) at imm_import.cc:2432 #7 0x004088b4 in importImmXML (xmlfileC=xmlfileC@entry=0x7fffe35b AppConfig-2N.xml, adminOwnerName=optimized out, verbose=optimized out, ccb_safe=optimized out, immHandle=immHandle@entry=0x619aa8 immHandle, ownerHandle=ownerHandle@entry=0x619a98 ownerHandle, ccbHandle=ccbHandle@entry=0x6197e0 ccbHandle, mode=0) at imm_import.cc:2519 #8 0x00410846 in imm_operation (argc=3, argv=0x7fffe048) at imm_cfg.c:1270 #9 0x768d9ea5 in __libc_start_main (main=0x4034e0 main, argc=3, ubp_av=0x7fffe048, init=optimized out, fini=optimized out, rtld_fini=optimized out, stack_end=0x7fffe038) at libc-start.c:260 #10 0x00403511 in _start () always reproducible (only tested default branch) --- 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.-- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60133471iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #572 immcfg segfaults
- **status**: review -- fixed --- ** [tickets:#572] immcfg segfaults** **Status:** fixed **Created:** Fri Sep 20, 2013 07:07 AM UTC by Hans Feldt **Last Updated:** Tue Sep 24, 2013 02:15 PM UTC **Owner:** Zoran Milinkovic $ immcfg -f AppConfig-2N.xml Failed to call saImmOmAdminOwnerSet on parent: 'safAmfNode=SC-2,safAmfCluster=myAmfCluster' , rc = 12 Segmentation fault (core dumped) (gdb) bt #0 __strlen_sse2_pminub () at ../sysdeps/x86_64/multiarch/strlen-sse2-pminub.S:38 #1 0x004098b7 in createImmObject (state=state@entry=0x7fffd470) at imm_import.cc:666 #2 0x0040a635 in endElementHandler (userData=0x7fffd470, name=optimized out) at imm_import.cc:1508 #3 0x77abc81d in ?? () from /usr/lib/x86_64-linux-gnu/libxml2.so.2 #4 0x77ac3f69 in ?? () from /usr/lib/x86_64-linux-gnu/libxml2.so.2 #5 0x77ac4f86 in xmlParseChunk () from /usr/lib/x86_64-linux-gnu/libxml2.so.2 #6 0x0040864f in loadImmXML (xmlfile=xmlfile@entry=0x7fffe35b AppConfig-2N.xml) at imm_import.cc:2432 #7 0x004088b4 in importImmXML (xmlfileC=xmlfileC@entry=0x7fffe35b AppConfig-2N.xml, adminOwnerName=optimized out, verbose=optimized out, ccb_safe=optimized out, immHandle=immHandle@entry=0x619aa8 immHandle, ownerHandle=ownerHandle@entry=0x619a98 ownerHandle, ccbHandle=ccbHandle@entry=0x6197e0 ccbHandle, mode=0) at imm_import.cc:2519 #8 0x00410846 in imm_operation (argc=3, argv=0x7fffe048) at imm_cfg.c:1270 #9 0x768d9ea5 in __libc_start_main (main=0x4034e0 main, argc=3, ubp_av=0x7fffe048, init=optimized out, fini=optimized out, rtld_fini=optimized out, stack_end=0x7fffe038) at libc-start.c:260 #10 0x00403511 in _start () always reproducible (only tested default branch) --- 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.-- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60133471iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #595 IMM: saImmOmAccessorGet_2 locks IMM handle if SA_IMM_SEARCH_GET_CONFIG_ATTR is used for IMM version less than A.02.11
--- ** [tickets:#595] IMM: saImmOmAccessorGet_2 locks IMM handle if SA_IMM_SEARCH_GET_CONFIG_ATTR is used for IMM version less than A.02.11** **Status:** accepted **Created:** Mon Oct 14, 2013 01:58 PM UTC by Zoran Milinkovic **Last Updated:** Mon Oct 14, 2013 01:58 PM UTC **Owner:** Zoran Milinkovic If attribute names contain SA_IMM_SEARCH_GET_CONFIG_ATTR for IMM version lower than A.02.11, all synchronous calls of IMM handle will fail with error code SA_AIS_ERR_LIBRARY. --- 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.-- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60134071iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #612 IMM: imm client crashes when using saImmOmSearchNext_2
--- ** [tickets:#612] IMM: imm client crashes when using saImmOmSearchNext_2** **Status:** unassigned **Created:** Thu Oct 31, 2013 09:51 AM UTC by Zoran Milinkovic **Last Updated:** Thu Oct 31, 2013 09:51 AM UTC **Owner:** nobody saImmOmSearchNext_2 code does not handle out_evt-info.imma.type well, and can crash IMM client trying to free a random memory. saImmOmsearchNext_2 assumes that out_evt-info.imma.type is always a type of IMMA_EVT_ND2A_SEARCHNEXT_RSP, and according to the type, IMMSV_OM_RSP_SEARCH_NEXT struct is freed. If out_evt-info.imma.type is a type of IMMA_EVT_ND2A_IMM_ERROR, an IMM client crashes. The bug is seen in OpenSAF 4.2, and OpenSAF 4.3 --- 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.-- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #612 IMM: imm client crashes when using saImmOmSearchNext_2
- **status**: assigned -- review --- ** [tickets:#612] IMM: imm client crashes when using saImmOmSearchNext_2** **Status:** review **Created:** Thu Oct 31, 2013 09:51 AM UTC by Zoran Milinkovic **Last Updated:** Fri Nov 01, 2013 07:47 AM UTC **Owner:** Zoran Milinkovic saImmOmSearchNext_2 code does not handle out_evt-info.imma.type well, and can crash IMM client trying to free a random memory. saImmOmsearchNext_2 assumes that out_evt-info.imma.type is always a type of IMMA_EVT_ND2A_SEARCHNEXT_RSP, and according to the type, IMMSV_OM_RSP_SEARCH_NEXT struct is freed. If out_evt-info.imma.type is a type of IMMA_EVT_ND2A_IMM_ERROR, an IMM client crashes. The bug is seen in OpenSAF 4.2, and OpenSAF 4.3 --- 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.-- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #612 IMM: imm client crashes when using saImmOmSearchNext_2
http://www.mail-archive.com/opensaf-devel@lists.sourceforge.net/msg00852.html --- ** [tickets:#612] IMM: imm client crashes when using saImmOmSearchNext_2** **Status:** review **Created:** Thu Oct 31, 2013 09:51 AM UTC by Zoran Milinkovic **Last Updated:** Fri Nov 01, 2013 07:47 AM UTC **Owner:** Zoran Milinkovic saImmOmSearchNext_2 code does not handle out_evt-info.imma.type well, and can crash IMM client trying to free a random memory. saImmOmsearchNext_2 assumes that out_evt-info.imma.type is always a type of IMMA_EVT_ND2A_SEARCHNEXT_RSP, and according to the type, IMMSV_OM_RSP_SEARCH_NEXT struct is freed. If out_evt-info.imma.type is a type of IMMA_EVT_ND2A_IMM_ERROR, an IMM client crashes. The bug is seen in OpenSAF 4.2, and OpenSAF 4.3 --- 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.-- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #612 IMM: imm client crashes when using saImmOmSearchNext_2
- **status**: review -- fixed --- ** [tickets:#612] IMM: imm client crashes when using saImmOmSearchNext_2** **Status:** fixed **Created:** Thu Oct 31, 2013 09:51 AM UTC by Zoran Milinkovic **Last Updated:** Fri Nov 01, 2013 09:53 AM UTC **Owner:** Zoran Milinkovic saImmOmSearchNext_2 code does not handle out_evt-info.imma.type well, and can crash IMM client trying to free a random memory. saImmOmsearchNext_2 assumes that out_evt-info.imma.type is always a type of IMMA_EVT_ND2A_SEARCHNEXT_RSP, and according to the type, IMMSV_OM_RSP_SEARCH_NEXT struct is freed. If out_evt-info.imma.type is a type of IMMA_EVT_ND2A_IMM_ERROR, an IMM client crashes. The bug is seen in OpenSAF 4.2, and OpenSAF 4.3 --- 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
[tickets] [opensaf:tickets] #612 IMM: imm client crashes when using saImmOmSearchNext_2
opensaf-4.2.x: changeset: 4586:996320b5482e branch: opensaf-4.2.x tag: tip parent: 4583:bbaf89a8415b user:dung.v.cao dung.v@dektech.com.au date:Fri Nov 01 07:20:28 2013 +0100 summary: IMM: fix memory problem in saImmOmSearchNext_2 [#612] - opensaf-4.3.x: changeset: 4587:30203fc1d89c branch: opensaf-4.3.x tag: tip parent: 4584:d78e3ea0efed user:dung.v.cao dung.v@dektech.com.au date:Fri Nov 01 07:20:28 2013 +0100 summary: IMM: fix memory problem in saImmOmSearchNext_2 [#612] --- ** [tickets:#612] IMM: imm client crashes when using saImmOmSearchNext_2** **Status:** fixed **Created:** Thu Oct 31, 2013 09:51 AM UTC by Zoran Milinkovic **Last Updated:** Fri Nov 01, 2013 09:53 AM UTC **Owner:** Zoran Milinkovic saImmOmSearchNext_2 code does not handle out_evt-info.imma.type well, and can crash IMM client trying to free a random memory. saImmOmsearchNext_2 assumes that out_evt-info.imma.type is always a type of IMMA_EVT_ND2A_SEARCHNEXT_RSP, and according to the type, IMMSV_OM_RSP_SEARCH_NEXT struct is freed. If out_evt-info.imma.type is a type of IMMA_EVT_ND2A_IMM_ERROR, an IMM client crashes. The bug is seen in OpenSAF 4.2, and OpenSAF 4.3 --- 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
[tickets] [opensaf:tickets] #49 IMM: Support reference integrity checking
- **status**: accepted -- review --- ** [tickets:#49] IMM: Support reference integrity checking** **Status:** review **Created:** Wed May 08, 2013 07:52 AM UTC by Anders Bjornerstedt **Last Updated:** Wed Oct 23, 2013 03:08 PM UTC **Owner:** Zoran Milinkovic Migrated from: http://devel.opensaf.org/ticket/3122 Add a new flag for object attributes, defined as follows: #define SA_IMM_ATTR_NO_DANGLING 0x0400 The SA_IMM_ATTR_NO_DANGLING attribute is only meaningful for configuration attributes of type SA_IMM_ATTR_SANAMET. Setting it for runtime attributes or configuration attributes of other types is not allowed and generates an error. The IMM service will guarantee that the value(s) of an attribute with the SA_IMM_ATTR_NO_DANGLING flag, when set, contains the distinguished name of an existing IMM object. IMM will reject attempts to set it to anything that is not the distinguished name of an existing object, and it will reject attempts to delete objects that are referenced by such an attribute. This validation is performed when the CCB is applied, which means that it will take into account all changes performed within the CCB. Optionally, it is also possible to restrict the type of objects that an attribute with the flag SA_IMM_ATTR_NO_DANGLING is allowed to reference. If the attribute name contains the colon character (ASCII value 58), then the part of the attribute name following the colon specifies the class name that referenced object must be an instance of. The IMM service will reject attempts to set the attribute to the distinguished name of an object that is not an instance of this class. - In addition, besides checking that the attribute value to be assigned is the DN of an existing object, the imm service will check that the object is persistent, i.e. either the DN of a config object or the DN of a persistent runtime object. References to non persistent runtime objects can not be allowed since a cluster restart would automatically cause such references to become dangling. (Peristent runtime objects should of course never be used, but since they *are* used heavily by services such as smfsv, it would be strange not to support referential integrity covering references to such objects. References from one PRTO to another PRTO would not be allowed according to the above rules, so this addition concerns only references from config objects to runtime objects. --- 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.-- Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #49 IMM: Support reference integrity checking
https://sourceforge.net/p/opensaf/mailman/message/31668846/ --- ** [tickets:#49] IMM: Support reference integrity checking** **Status:** review **Created:** Wed May 08, 2013 07:52 AM UTC by Anders Bjornerstedt **Last Updated:** Fri Nov 22, 2013 12:57 PM UTC **Owner:** Zoran Milinkovic Migrated from: http://devel.opensaf.org/ticket/3122 Add a new flag for object attributes, defined as follows: #define SA_IMM_ATTR_NO_DANGLING 0x0400 The SA_IMM_ATTR_NO_DANGLING attribute is only meaningful for configuration attributes of type SA_IMM_ATTR_SANAMET. Setting it for runtime attributes or configuration attributes of other types is not allowed and generates an error. The IMM service will guarantee that the value(s) of an attribute with the SA_IMM_ATTR_NO_DANGLING flag, when set, contains the distinguished name of an existing IMM object. IMM will reject attempts to set it to anything that is not the distinguished name of an existing object, and it will reject attempts to delete objects that are referenced by such an attribute. This validation is performed when the CCB is applied, which means that it will take into account all changes performed within the CCB. Optionally, it is also possible to restrict the type of objects that an attribute with the flag SA_IMM_ATTR_NO_DANGLING is allowed to reference. If the attribute name contains the colon character (ASCII value 58), then the part of the attribute name following the colon specifies the class name that referenced object must be an instance of. The IMM service will reject attempts to set the attribute to the distinguished name of an object that is not an instance of this class. - In addition, besides checking that the attribute value to be assigned is the DN of an existing object, the imm service will check that the object is persistent, i.e. either the DN of a config object or the DN of a persistent runtime object. References to non persistent runtime objects can not be allowed since a cluster restart would automatically cause such references to become dangling. (Peristent runtime objects should of course never be used, but since they *are* used heavily by services such as smfsv, it would be strange not to support referential integrity covering references to such objects. References from one PRTO to another PRTO would not be allowed according to the above rules, so this addition concerns only references from config objects to runtime objects. --- 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.-- Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #659 CLM: OpenSAF fails to compile
--- ** [tickets:#659] CLM: OpenSAF fails to compile** **Status:** unassigned **Created:** Sun Dec 15, 2013 01:12 PM UTC by Zoran Milinkovic **Last Updated:** Sun Dec 15, 2013 01:12 PM UTC **Owner:** Mathi Naickan OpenSAF fails to compile due to the latest CLM change. The problem is seen on Debian (gcc 4.7.2) and Ubuntu (gcc 4.6.3). make[7]: Entering directory `/local/scratch/emilzor/sf/opensaf-default-clmtest/osaf/services/saf/clmsv/nodeagent' CC osafclmna-main.o main.c: In function ‘clmna_mds_svc_evt’: main.c:161:11: error: variable ‘rc’ set but not used [-Werror=unused-but-set-variable] cc1: all warnings being treated as errors --- 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] #49 IMM: Support reference integrity checking
https://sourceforge.net/p/opensaf/mailman/message/31753231/ --- ** [tickets:#49] IMM: Support reference integrity checking** **Status:** review **Created:** Wed May 08, 2013 07:52 AM UTC by Anders Bjornerstedt **Last Updated:** Thu Dec 12, 2013 10:58 AM UTC **Owner:** Zoran Milinkovic Migrated from: http://devel.opensaf.org/ticket/3122 Add a new flag for object attributes, defined as follows: #define SA_IMM_ATTR_NO_DANGLING 0x0400 The SA_IMM_ATTR_NO_DANGLING attribute is only meaningful for configuration attributes of type SA_IMM_ATTR_SANAMET. Setting it for runtime attributes or configuration attributes of other types is not allowed and generates an error. The IMM service will guarantee that the value(s) of an attribute with the SA_IMM_ATTR_NO_DANGLING flag, when set, contains the distinguished name of an existing IMM object. IMM will reject attempts to set it to anything that is not the distinguished name of an existing object, and it will reject attempts to delete objects that are referenced by such an attribute. This validation is performed when the CCB is applied, which means that it will take into account all changes performed within the CCB. Optionally, it is also possible to restrict the type of objects that an attribute with the flag SA_IMM_ATTR_NO_DANGLING is allowed to reference. If the attribute name contains the colon character (ASCII value 58), then the part of the attribute name following the colon specifies the class name that referenced object must be an instance of. The IMM service will reject attempts to set the attribute to the distinguished name of an object that is not an instance of this class. - In addition, besides checking that the attribute value to be assigned is the DN of an existing object, the imm service will check that the object is persistent, i.e. either the DN of a config object or the DN of a persistent runtime object. References to non persistent runtime objects can not be allowed since a cluster restart would automatically cause such references to become dangling. (Peristent runtime objects should of course never be used, but since they *are* used heavily by services such as smfsv, it would be strange not to support referential integrity covering references to such objects. References from one PRTO to another PRTO would not be allowed according to the above rules, so this addition concerns only references from config objects to runtime objects. --- 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] #49 IMM: Support reference integrity checking
- **status**: review -- fixed --- ** [tickets:#49] IMM: Support reference integrity checking** **Status:** fixed **Created:** Wed May 08, 2013 07:52 AM UTC by Anders Bjornerstedt **Last Updated:** Sun Dec 15, 2013 03:59 PM UTC **Owner:** Zoran Milinkovic Migrated from: http://devel.opensaf.org/ticket/3122 Add a new flag for object attributes, defined as follows: #define SA_IMM_ATTR_NO_DANGLING 0x0400 The SA_IMM_ATTR_NO_DANGLING attribute is only meaningful for configuration attributes of type SA_IMM_ATTR_SANAMET. Setting it for runtime attributes or configuration attributes of other types is not allowed and generates an error. The IMM service will guarantee that the value(s) of an attribute with the SA_IMM_ATTR_NO_DANGLING flag, when set, contains the distinguished name of an existing IMM object. IMM will reject attempts to set it to anything that is not the distinguished name of an existing object, and it will reject attempts to delete objects that are referenced by such an attribute. This validation is performed when the CCB is applied, which means that it will take into account all changes performed within the CCB. Optionally, it is also possible to restrict the type of objects that an attribute with the flag SA_IMM_ATTR_NO_DANGLING is allowed to reference. If the attribute name contains the colon character (ASCII value 58), then the part of the attribute name following the colon specifies the class name that referenced object must be an instance of. The IMM service will reject attempts to set the attribute to the distinguished name of an object that is not an instance of this class. - In addition, besides checking that the attribute value to be assigned is the DN of an existing object, the imm service will check that the object is persistent, i.e. either the DN of a config object or the DN of a persistent runtime object. References to non persistent runtime objects can not be allowed since a cluster restart would automatically cause such references to become dangling. (Peristent runtime objects should of course never be used, but since they *are* used heavily by services such as smfsv, it would be strange not to support referential integrity covering references to such objects. References from one PRTO to another PRTO would not be allowed according to the above rules, so this addition concerns only references from config objects to runtime objects. --- 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] #49 IMM: Support reference integrity checking
default(4.4): changeset: 4734:bbb2c89c1361 user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Sun Dec 15 16:42:12 2013 +0100 summary: IMM: Add support for NO_DANGLING flag to API [#49] changeset: 4735:e0399aa51366 user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Sun Dec 15 16:42:41 2013 +0100 summary: IMM: Add support for NO_DANGLING flag to the service [#49] changeset: 4736:bb56f3cb6b11 tag: tip user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Sun Dec 15 16:43:09 2013 +0100 summary: IMMTOOLS: Add support for NO_DANGLING flag to tools [#49] --- ** [tickets:#49] IMM: Support reference integrity checking** **Status:** fixed **Created:** Wed May 08, 2013 07:52 AM UTC by Anders Bjornerstedt **Last Updated:** Sun Dec 15, 2013 03:59 PM UTC **Owner:** Zoran Milinkovic Migrated from: http://devel.opensaf.org/ticket/3122 Add a new flag for object attributes, defined as follows: #define SA_IMM_ATTR_NO_DANGLING 0x0400 The SA_IMM_ATTR_NO_DANGLING attribute is only meaningful for configuration attributes of type SA_IMM_ATTR_SANAMET. Setting it for runtime attributes or configuration attributes of other types is not allowed and generates an error. The IMM service will guarantee that the value(s) of an attribute with the SA_IMM_ATTR_NO_DANGLING flag, when set, contains the distinguished name of an existing IMM object. IMM will reject attempts to set it to anything that is not the distinguished name of an existing object, and it will reject attempts to delete objects that are referenced by such an attribute. This validation is performed when the CCB is applied, which means that it will take into account all changes performed within the CCB. Optionally, it is also possible to restrict the type of objects that an attribute with the flag SA_IMM_ATTR_NO_DANGLING is allowed to reference. If the attribute name contains the colon character (ASCII value 58), then the part of the attribute name following the colon specifies the class name that referenced object must be an instance of. The IMM service will reject attempts to set the attribute to the distinguished name of an object that is not an instance of this class. - In addition, besides checking that the attribute value to be assigned is the DN of an existing object, the imm service will check that the object is persistent, i.e. either the DN of a config object or the DN of a persistent runtime object. References to non persistent runtime objects can not be allowed since a cluster restart would automatically cause such references to become dangling. (Peristent runtime objects should of course never be used, but since they *are* used heavily by services such as smfsv, it would be strange not to support referential integrity covering references to such objects. References from one PRTO to another PRTO would not be allowed according to the above rules, so this addition concerns only references from config objects to runtime objects. --- 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] #702 IMMTOOLS: creating an object using immcfg crashes when RDN value has a DN of an associated object
--- ** [tickets:#702] IMMTOOLS: creating an object using immcfg crashes when RDN value has a DN of an associated object** **Status:** assigned **Created:** Thu Jan 02, 2014 10:05 AM UTC by Zoran Milinkovic **Last Updated:** Thu Jan 02, 2014 10:05 AM UTC **Owner:** Zoran Milinkovic When trying to create a new object, which does not have a parent DN, and its RDN value has a DN of an associated object, immcfg crashes. Example: $ immcfg -c TestClass 'id=testid=1\,testid=5' Segmentation fault (core dumped) --- 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] #702 IMMTOOLS: creating an object using immcfg crashes when RDN value has a DN of an associated object
- **status**: assigned -- review --- ** [tickets:#702] IMMTOOLS: creating an object using immcfg crashes when RDN value has a DN of an associated object** **Status:** review **Created:** Thu Jan 02, 2014 10:05 AM UTC by Zoran Milinkovic **Last Updated:** Thu Jan 02, 2014 10:05 AM UTC **Owner:** Zoran Milinkovic When trying to create a new object, which does not have a parent DN, and its RDN value has a DN of an associated object, immcfg crashes. Example: $ immcfg -c TestClass 'id=testid=1\,testid=5' Segmentation fault (core dumped) --- 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] #702 IMMTOOLS: creating an object using immcfg crashes when RDN value has a DN of an associated object
https://sourceforge.net/p/opensaf/mailman/message/31801584/ --- ** [tickets:#702] IMMTOOLS: creating an object using immcfg crashes when RDN value has a DN of an associated object** **Status:** review **Created:** Thu Jan 02, 2014 10:05 AM UTC by Zoran Milinkovic **Last Updated:** Thu Jan 02, 2014 10:05 AM UTC **Owner:** Zoran Milinkovic When trying to create a new object, which does not have a parent DN, and its RDN value has a DN of an associated object, immcfg crashes. Example: $ immcfg -c TestClass 'id=testid=1\,testid=5' Segmentation fault (core dumped) --- 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] #702 IMMTOOLS: creating an object using immcfg crashes when RDN value has a DN of an associated object
- **status**: review -- fixed --- ** [tickets:#702] IMMTOOLS: creating an object using immcfg crashes when RDN value has a DN of an associated object** **Status:** fixed **Created:** Thu Jan 02, 2014 10:05 AM UTC by Zoran Milinkovic **Last Updated:** Thu Jan 02, 2014 12:27 PM UTC **Owner:** Zoran Milinkovic When trying to create a new object, which does not have a parent DN, and its RDN value has a DN of an associated object, immcfg crashes. Example: $ immcfg -c TestClass 'id=testid=1\,testid=5' Segmentation fault (core dumped) --- 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] #702 IMMTOOLS: creating an object using immcfg crashes when RDN value has a DN of an associated object
opensaf-4.2.x: changeset: 4786:e33d3933f335 branch: opensaf-4.2.x parent: 4751:3277c773f609 user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Thu Jan 02 13:15:55 2014 +0100 summary: IMMTOOLS: fix RDN value with a DN of an associated object in immcfg [#702] - opensaf-4.3.x: changeset: 4787:446574bdd7db branch: opensaf-4.3.x parent: 4752:bb00faa2f8bd user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Thu Jan 02 13:15:55 2014 +0100 summary: IMMTOOLS: fix RDN value with a DN of an associated object in immcfg [#702] - default(4.4): changeset: 4788:f7289aea6f8b tag: tip parent: 4785:d88779d80ff4 user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Thu Jan 02 13:15:55 2014 +0100 summary: IMMTOOLS: fix RDN value with a DN of an associated object in immcfg [#702] --- ** [tickets:#702] IMMTOOLS: creating an object using immcfg crashes when RDN value has a DN of an associated object** **Status:** fixed **Created:** Thu Jan 02, 2014 10:05 AM UTC by Zoran Milinkovic **Last Updated:** Thu Jan 02, 2014 12:27 PM UTC **Owner:** Zoran Milinkovic When trying to create a new object, which does not have a parent DN, and its RDN value has a DN of an associated object, immcfg crashes. Example: $ immcfg -c TestClass 'id=testid=1\,testid=5' Segmentation fault (core dumped) --- 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] #636 IMM: Missing immomtest cases for NO_DANGLING
- **status**: assigned -- review - **Part**: - -- tests --- ** [tickets:#636] IMM: Missing immomtest cases for NO_DANGLING ** **Status:** review **Created:** Fri Nov 22, 2013 09:50 AM UTC by Anders Bjornerstedt **Last Updated:** Wed Jan 08, 2014 12:19 PM UTC **Owner:** Zoran Milinkovic This is related to ticket (#49) 'IMM: Support reference integrity checking. Enhancement #49 extends the IMM OM API. This means that some level of api-function tests should be added to immomtest, to test NO_DANGLING. --- 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] #636 IMM: Missing immomtest cases for NO_DANGLING
https://sourceforge.net/p/opensaf/mailman/message/31852734/ --- ** [tickets:#636] IMM: Missing immomtest cases for NO_DANGLING ** **Status:** review **Created:** Fri Nov 22, 2013 09:50 AM UTC by Anders Bjornerstedt **Last Updated:** Wed Jan 08, 2014 12:19 PM UTC **Owner:** Zoran Milinkovic This is related to ticket (#49) 'IMM: Support reference integrity checking. Enhancement #49 extends the IMM OM API. This means that some level of api-function tests should be added to immomtest, to test NO_DANGLING. --- 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] #726 IMM: wrong error codes in README.NO_DANGLING
--- ** [tickets:#726] IMM: wrong error codes in README.NO_DANGLING** **Status:** accepted **Created:** Thu Jan 16, 2014 12:14 PM UTC by Zoran Milinkovic **Last Updated:** Thu Jan 16, 2014 12:14 PM UTC **Owner:** Zoran Milinkovic In two places in README.NO_DANGLING, a wrong error code is stated. BAD_OPERATION needs to be replaced with INVALID_PARAM o If the created object has a NO_DANGLING reference to a non-persistent runtime object, return bBAD_OPERATION/b. o If an updated attribute value has a NO_DANGLING reference to a non-persistent runtime object, return bBAD_OPERATION/b. --- 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] #636 IMM: Missing immomtest cases for NO_DANGLING
opensaf-4.4.x: changeset: 4815:c8cb0beaa27e branch: opensaf-4.4.x parent: 4807:bb5a37c82405 user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Thu Jan 16 12:48:29 2014 +0100 summary: IMMTEST: add new test cases for NO_DANGLING flag [#636] - default(4.5): changeset: 4816:2712ca2144d2 parent: 4814:833bb198e9fc user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Thu Jan 16 12:48:29 2014 +0100 summary: IMMTEST: add new test cases for NO_DANGLING flag [#636] --- ** [tickets:#636] IMM: Missing immomtest cases for NO_DANGLING ** **Status:** fixed **Created:** Fri Nov 22, 2013 09:50 AM UTC by Anders Bjornerstedt **Last Updated:** Thu Jan 16, 2014 11:58 AM UTC **Owner:** Zoran Milinkovic This is related to ticket (#49) 'IMM: Support reference integrity checking. Enhancement #49 extends the IMM OM API. This means that some level of api-function tests should be added to immomtest, to test NO_DANGLING. --- 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] #636 IMM: Missing immomtest cases for NO_DANGLING
- **status**: review -- fixed --- ** [tickets:#636] IMM: Missing immomtest cases for NO_DANGLING ** **Status:** fixed **Created:** Fri Nov 22, 2013 09:50 AM UTC by Anders Bjornerstedt **Last Updated:** Thu Jan 16, 2014 11:58 AM UTC **Owner:** Zoran Milinkovic This is related to ticket (#49) 'IMM: Support reference integrity checking. Enhancement #49 extends the IMM OM API. This means that some level of api-function tests should be added to immomtest, to test NO_DANGLING. --- 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] #726 IMM: wrong error codes in README.NO_DANGLING
- **status**: review -- fixed --- ** [tickets:#726] IMM: wrong error codes in README.NO_DANGLING** **Status:** fixed **Created:** Thu Jan 16, 2014 12:14 PM UTC by Zoran Milinkovic **Last Updated:** Thu Jan 16, 2014 12:27 PM UTC **Owner:** Zoran Milinkovic In two places in README.NO_DANGLING, a wrong error code is stated. BAD_OPERATION needs to be replaced with INVALID_PARAM o If the created object has a NO_DANGLING reference to a non-persistent runtime object, return bBAD_OPERATION/b. o If an updated attribute value has a NO_DANGLING reference to a non-persistent runtime object, return bBAD_OPERATION/b. --- 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.
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] #749 IMMTOOLS: immcfg crashes when default value type is different then attribute type in a class definition
--- ** [tickets:#749] IMMTOOLS: immcfg crashes when default value type is different then attribute type in a class definition** **Status:** accepted **Created:** Mon Jan 27, 2014 09:46 AM UTC by Zoran Milinkovic **Last Updated:** Mon Jan 27, 2014 09:46 AM UTC **Owner:** Zoran Milinkovic immcfg crashes during the import of XML file when different type is used in the default value element, then the attribute type is stated in the class. In the case we found the bug, in the class definition, an SA_INT32_T attribute has a string default value. It's not easy to reproduce the bug, and it depends on the operating system. On LOTC it's easy to reproduce, while on Debian immcfg works fine. --- 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] #749 IMMTOOLS: immcfg crashes when default value type is different then attribute type in a class definition
- **status**: accepted -- review --- ** [tickets:#749] IMMTOOLS: immcfg crashes when default value type is different then attribute type in a class definition** **Status:** review **Created:** Mon Jan 27, 2014 09:46 AM UTC by Zoran Milinkovic **Last Updated:** Mon Jan 27, 2014 09:46 AM UTC **Owner:** Zoran Milinkovic immcfg crashes during the import of XML file when different type is used in the default value element, then the attribute type is stated in the class. In the case we found the bug, in the class definition, an SA_INT32_T attribute has a string default value. It's not easy to reproduce the bug, and it depends on the operating system. On LOTC it's easy to reproduce, while on Debian immcfg works fine. --- 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] #749 IMMTOOLS: immcfg crashes when default value type is different then attribute type in a class definition
https://sourceforge.net/p/opensaf/mailman/message/31890041/ --- ** [tickets:#749] IMMTOOLS: immcfg crashes when default value type is different then attribute type in a class definition** **Status:** review **Created:** Mon Jan 27, 2014 09:46 AM UTC by Zoran Milinkovic **Last Updated:** Mon Jan 27, 2014 09:46 AM UTC **Owner:** Zoran Milinkovic immcfg crashes during the import of XML file when different type is used in the default value element, then the attribute type is stated in the class. In the case we found the bug, in the class definition, an SA_INT32_T attribute has a string default value. It's not easy to reproduce the bug, and it depends on the operating system. On LOTC it's easy to reproduce, while on Debian immcfg works fine. --- 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.
- **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.
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] #758 opensaf 4.4.x latest staging does not compile for 32bit
https://sourceforge.net/p/opensaf/mailman/message/31924488/ --- ** [tickets:#758] opensaf 4.4.x latest staging does not compile for 32bit** **Status:** review **Created:** Fri Jan 31, 2014 06:50 AM UTC by Sirisha Alla **Last Updated:** Mon Feb 03, 2014 11:59 AM UTC **Owner:** Zoran Milinkovic This issue is seen on cs 4871 make rpm fails with below error: libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../../.. -DIMMA_OM -I../../../../../osaf/libs/saf/include -I../../../../../osaf/libs/core/include -I../../../../../osaf/libs/core/leap/include -I../../../../../osaf/libs/core/mds/include -I../../../../../osaf/libs/core/common/include -I../../../../../osaf/libs/common/immsv/include -g -Wall -fno-strict-aliasing -Werror -fPIC -D_FORTIFY_SOURCE=2 -fstack-protector -DINTERNAL_VERSION_ID=\\ -O2 -g -m32 -march=i586 -mtune=i686 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -MT libimmaOm_la-imma_om_api.lo -MD -MP -MF .deps/libimmaOm_la-imma_om_api.Tpo -c imma_om_api.c -fPIC -DPIC -o .libs/libimmaOm_la-imma_om_api.o cc1: warnings being treated as errors imma_om_api.c: In function ‘saImmOmSearchInitialize_2’: imma_om_api.c:6030: error: integer constant is too large for ‘long’ type make[7]: *** [libimmaOm_la-imma_om_api.lo] Error 1 make[7]: Leaving directory `/home/incrementaldropstaging/rpms/BUILD/opensaf-4.4.FC/osaf/libs/agents/saf/imma' make[6]: *** [all-recursive] Error 1 make[6]: Leaving directory `/home/incrementaldropstaging/rpms/BUILD/opensaf-4.4.FC/osaf/libs/agents/saf' make[5]: *** [all-recursive] Error 1 make[5]: Leaving directory `/home/incrementaldropstaging/rpms/BUILD/opensaf-4.4.FC/osaf/libs/agents' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/home/incrementaldropstaging/rpms/BUILD/opensaf-4.4.FC/osaf/libs' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/incrementaldropstaging/rpms/BUILD/opensaf-4.4.FC/osaf' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/incrementaldropstaging/rpms/BUILD/opensaf-4.4.FC' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/incrementaldropstaging/rpms/BUILD/opensaf-4.4.FC' error: Bad exit status from /home/incrementaldropstaging/rpms/tmp/rpm-tmp.89674 (%build) RPM build errors: Bad exit status from /home/incrementaldropstaging/rpms/tmp/rpm-tmp.89674 (%build) gcc -v Using built-in specs. Target: i586-suse-linux Configured with: ../configure --prefix=/usr --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib --libexecdir=/usr/lib --enable-languages=c,c++,objc,fortran,obj-c++,java,ada --enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.3 --enable-ssp --disable-libssp --with-bugurl=http://bugs.opensuse.org/ --with-pkgversion='SUSE Linux' --disable-libgcj --disable-libmudflap --with-slibdir=/lib --with-system-zlib --enable-__cxa_atexit --enable-libstdcxx-allocator=new --disable-libstdcxx-pch --enable-version-specific-runtime-libs --program-suffix=-4.3 --enable-linux-futex --without-system-libunwind --with-cpu=generic --build=i586-suse-linux Thread model: posix gcc version 4.3.4 [gcc-4_3-branch revision 152973] (SUSE Linux) - CC ntftest-tet_saNtfNotificationSubscribe.o cc1: warnings being treated as errors tet_saNtfNotificationSubscribe.c: In function ‘saNtfNotificationSubscribe_03’: tet_saNtfNotificationSubscribe.c:94: error: cast from pointer to integer of different size tet_saNtfNotificationSubscribe.c:95: error: cast from pointer to integer of different size tet_saNtfNotificationSubscribe.c:96: error: cast from pointer to integer of different size tet_saNtfNotificationSubscribe.c:97: error: cast from pointer to integer of different size tet_saNtfNotificationSubscribe.c:98: error: cast from pointer to integer of different size make[2]: *** [ntftest-tet_saNtfNotificationSubscribe.o] Error 1 make[2]: Leaving directory `/home/emilzor/development/opensaf-4.4-i386/tests/ntfsv' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/emilzor/development/opensaf-4.4-i386' make: *** [all] Error 2 - CC clmtest-tet_saClmClusterNodeGet.o cc1: warnings being treated as errors ../../tests/clmsv/src/tet_saClmClusterNodeGet.c:23: error: integer constant is too large for ‘long’ type make[2]: *** [clmtest-tet_saClmClusterNodeGet.o] Error 1 make[2]: Leaving directory `/home/emilzor/development/opensaf-4.4-i386/tests/clmsv' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/emilzor/development/opensaf-4.4-i386' make: *** [all] Error 2 --- 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
[tickets] [opensaf:tickets] #758 opensaf 4.4.x latest staging does not compile for 32bit
- **status**: accepted -- review --- ** [tickets:#758] opensaf 4.4.x latest staging does not compile for 32bit** **Status:** review **Created:** Fri Jan 31, 2014 06:50 AM UTC by Sirisha Alla **Last Updated:** Mon Feb 03, 2014 11:59 AM UTC **Owner:** Zoran Milinkovic This issue is seen on cs 4871 make rpm fails with below error: libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../../.. -DIMMA_OM -I../../../../../osaf/libs/saf/include -I../../../../../osaf/libs/core/include -I../../../../../osaf/libs/core/leap/include -I../../../../../osaf/libs/core/mds/include -I../../../../../osaf/libs/core/common/include -I../../../../../osaf/libs/common/immsv/include -g -Wall -fno-strict-aliasing -Werror -fPIC -D_FORTIFY_SOURCE=2 -fstack-protector -DINTERNAL_VERSION_ID=\\ -O2 -g -m32 -march=i586 -mtune=i686 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -MT libimmaOm_la-imma_om_api.lo -MD -MP -MF .deps/libimmaOm_la-imma_om_api.Tpo -c imma_om_api.c -fPIC -DPIC -o .libs/libimmaOm_la-imma_om_api.o cc1: warnings being treated as errors imma_om_api.c: In function ‘saImmOmSearchInitialize_2’: imma_om_api.c:6030: error: integer constant is too large for ‘long’ type make[7]: *** [libimmaOm_la-imma_om_api.lo] Error 1 make[7]: Leaving directory `/home/incrementaldropstaging/rpms/BUILD/opensaf-4.4.FC/osaf/libs/agents/saf/imma' make[6]: *** [all-recursive] Error 1 make[6]: Leaving directory `/home/incrementaldropstaging/rpms/BUILD/opensaf-4.4.FC/osaf/libs/agents/saf' make[5]: *** [all-recursive] Error 1 make[5]: Leaving directory `/home/incrementaldropstaging/rpms/BUILD/opensaf-4.4.FC/osaf/libs/agents' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/home/incrementaldropstaging/rpms/BUILD/opensaf-4.4.FC/osaf/libs' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/incrementaldropstaging/rpms/BUILD/opensaf-4.4.FC/osaf' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/incrementaldropstaging/rpms/BUILD/opensaf-4.4.FC' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/incrementaldropstaging/rpms/BUILD/opensaf-4.4.FC' error: Bad exit status from /home/incrementaldropstaging/rpms/tmp/rpm-tmp.89674 (%build) RPM build errors: Bad exit status from /home/incrementaldropstaging/rpms/tmp/rpm-tmp.89674 (%build) gcc -v Using built-in specs. Target: i586-suse-linux Configured with: ../configure --prefix=/usr --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib --libexecdir=/usr/lib --enable-languages=c,c++,objc,fortran,obj-c++,java,ada --enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.3 --enable-ssp --disable-libssp --with-bugurl=http://bugs.opensuse.org/ --with-pkgversion='SUSE Linux' --disable-libgcj --disable-libmudflap --with-slibdir=/lib --with-system-zlib --enable-__cxa_atexit --enable-libstdcxx-allocator=new --disable-libstdcxx-pch --enable-version-specific-runtime-libs --program-suffix=-4.3 --enable-linux-futex --without-system-libunwind --with-cpu=generic --build=i586-suse-linux Thread model: posix gcc version 4.3.4 [gcc-4_3-branch revision 152973] (SUSE Linux) - CC ntftest-tet_saNtfNotificationSubscribe.o cc1: warnings being treated as errors tet_saNtfNotificationSubscribe.c: In function ‘saNtfNotificationSubscribe_03’: tet_saNtfNotificationSubscribe.c:94: error: cast from pointer to integer of different size tet_saNtfNotificationSubscribe.c:95: error: cast from pointer to integer of different size tet_saNtfNotificationSubscribe.c:96: error: cast from pointer to integer of different size tet_saNtfNotificationSubscribe.c:97: error: cast from pointer to integer of different size tet_saNtfNotificationSubscribe.c:98: error: cast from pointer to integer of different size make[2]: *** [ntftest-tet_saNtfNotificationSubscribe.o] Error 1 make[2]: Leaving directory `/home/emilzor/development/opensaf-4.4-i386/tests/ntfsv' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/emilzor/development/opensaf-4.4-i386' make: *** [all] Error 2 - CC clmtest-tet_saClmClusterNodeGet.o cc1: warnings being treated as errors ../../tests/clmsv/src/tet_saClmClusterNodeGet.c:23: error: integer constant is too large for ‘long’ type make[2]: *** [clmtest-tet_saClmClusterNodeGet.o] Error 1 make[2]: Leaving directory `/home/emilzor/development/opensaf-4.4-i386/tests/clmsv' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/emilzor/development/opensaf-4.4-i386' make: *** [all] Error 2 --- 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
[tickets] [opensaf:tickets] #217 imm tools crashes if run on a system where opensaf is not started
Change History Changed 10 months ago by hafe description modified (diff) summary changed from immfind crashes if run on a system where opensaf is not started to imm tools crashes if run on a system where opensaf is not started Changed 10 months ago by zmilinkovic Cannot reproduce the problem. OpenSAF 4.4: emilzor@SC-1:/etc/opensaf$ immfind error - saImmOmInitialize FAILED: SA_AIS_ERR_LIBRARY (2) emilzor@SC-1:/etc/opensaf$ immlist test error - saImmOmInitialize FAILED: SA_AIS_ERR_LIBRARY (2) OpenSAF 4.2.3: emilzor@SC-2:~/development/opensaf-4.2.x$ immfind error - immfind command timed out (alarm) emilzor@SC-2:~/development/opensaf-4.2.x$ immlist test error - immlist command timed out (alarm) Can you attach core dump and binary files ? Changed 10 months ago by hafe (gdb) bt #0 0x77161425 in GI_raise (sig=optimized out) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #1 0x77164b8b in GI_abort () at abort.c:91 #2 0x7798c95a in mds_init_transport () at mds_main.c:432 #3 0x7798d242 in mds_lib_req (req=0x7fffd5f0) at mds_main.c:278 #4 0x77963545 in ncs_mds_startup () at ncs_main_pub.c:288 #5 0x779647d5 in ncs_core_agents_startup () at ncs_main_pub.c:343 #6 0x77964879 in ncs_agents_startup () at ncs_main_pub.c:180 #7 0x7772e6d5 in imma_startup (sv_id=NCSMDS_SVC_ID_IMMA_OM) at imma_init.c:272 #8 0x7771b564 in initialize_common (immHandle=0x7fffdcd0, cl_node=0x60a010, version=0x7fffdb70) at imma_om_api.c:195 #9 0x7771dab3 in saImmOmInitialize (immHandle=0x7fffdcd0, immCallbacks=0x0, inout_version=optimized out) at imma_om_api.c:177 #10 0x0040452e in immutil_saImmOmInitialize (immHandle=0x7fffdcd0, immCallbacks=0x0, version=0x609340) at ../../../../osaf/tools/safimm/src/immutil.c:1117 #11 0x00402216 in main (argc=1, argv=0x7fffe138) at imm_find.c:164 it does not seems to be an imm/tools problem, seems like its mds and it might already be fixed with the later changes in this area. Changed 10 months ago by zmilinkovic Can confirm the problem with latest changesets ? Changed 9 months ago by anders owner set to zmilinkovic status changed from new to assigned component changed from opensaf to tools/safimm Changed 9 months ago by zmilinkovic component changed from tools/safimm to core/mds Changed 9 months ago by zmilinkovic status changed from assigned to closed resolution set to migrated Migrated to: http://sourceforge.net/p/opensaf/tickets/217/ --- ** [tickets:#217] imm tools crashes if run on a system where opensaf is not started** **Status:** unassigned **Created:** Wed May 15, 2013 07:47 AM UTC by Zoran Milinkovic **Last Updated:** Wed May 15, 2013 07:47 AM UTC **Owner:** nobody $ immfind Aborted (core dumped) same with immlist: $ immlist test Aborted (core dumped) not so nice... - Migrated from: http://devel.opensaf.org/ticket/3131 --- 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.-- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #217 imm tools crashes if run on a system where opensaf is not started
- **status**: unassigned -- not-reproducible - **assigned_to**: Zoran Milinkovic --- ** [tickets:#217] imm tools crashes if run on a system where opensaf is not started** **Status:** not-reproducible **Created:** Wed May 15, 2013 07:47 AM UTC by Zoran Milinkovic **Last Updated:** Wed Feb 12, 2014 02:18 PM UTC **Owner:** Zoran Milinkovic $ immfind Aborted (core dumped) same with immlist: $ immlist test Aborted (core dumped) not so nice... - Migrated from: http://devel.opensaf.org/ticket/3131 --- 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.-- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #116 IMMTOOLS: IMM is not forwards compatible with changes in the XML dump format
- **status**: accepted -- review --- ** [tickets:#116] IMMTOOLS: IMM is not forwards compatible with changes in the XML dump format** **Status:** review **Created:** Mon May 13, 2013 07:57 AM UTC by Zoran Milinkovic **Last Updated:** Mon Jan 13, 2014 03:13 PM UTC **Owner:** Zoran Milinkovic In order to provide compatibility with future changes in the IMM XML format, the IMM tools should ignore things like unknown attribute flags when loading an XML file. It would also be a good idea to check if the XML file uses a known version of the XML schema, and log a warning message (but still try to load it) if the version is unknown. Migrated from: http://devel.opensaf.org/ticket/3121 --- 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.-- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #116 IMMTOOLS: IMM is not forwards compatible with changes in the XML dump format
opensaf-4.2.x: http://sourceforge.net/p/opensaf/mailman/message/32009447/ opensaf-4.3.x: https://sourceforge.net/p/opensaf/mailman/message/32009450/ opensaf-4.4.x, default(4.5): https://sourceforge.net/p/opensaf/mailman/message/32009463/ --- ** [tickets:#116] IMMTOOLS: IMM is not forwards compatible with changes in the XML dump format** **Status:** review **Created:** Mon May 13, 2013 07:57 AM UTC by Zoran Milinkovic **Last Updated:** Mon Jan 13, 2014 03:13 PM UTC **Owner:** Zoran Milinkovic In order to provide compatibility with future changes in the IMM XML format, the IMM tools should ignore things like unknown attribute flags when loading an XML file. It would also be a good idea to check if the XML file uses a known version of the XML schema, and log a warning message (but still try to load it) if the version is unknown. Migrated from: http://devel.opensaf.org/ticket/3121 --- 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.-- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #794 IMM: imcfg --delete-class generates incorrect error message
- **status**: unassigned -- review - **assigned_to**: Zoran Milinkovic --- ** [tickets:#794] IMM: imcfg --delete-class generates incorrect error message** **Status:** review **Created:** Fri Feb 21, 2014 02:06 PM UTC by Anders Bjornerstedt **Last Updated:** Fri Feb 21, 2014 02:20 PM UTC **Owner:** Zoran Milinkovic While testing a fix for catching interference between concurrent attempts to create or delete a class (ticket #757). When testing to delete a class that is currently being created I get the expected error code but: # immcfg --delete-class OpensafImmTest error - saImmOmAdminOwnerSet FAILED: SA_AIS_ERR_BUSY (10) This has nothing to do with saImmOmAdminOwnerSet. Typical copy paste error. Error strings can only be picked up from admin-operations and ccb-operations, i.e. where there is an OI involved. So it is not possible for saImmOmClassCreate or saImmOmClassDelete. --- 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.-- Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #116 IMMTOOLS: IMM is not forwards compatible with changes in the XML dump format
opensaf-4.2.x: changeset: 5025:ec41bb7903b0 branch: opensaf-4.2.x parent: 5018:6be00445ee20 user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Wed Feb 26 11:11:55 2014 +0100 summary: IMM: add support for forwards compatibility of attribute flags [#116] changeset: 5026:2be1331136aa branch: opensaf-4.2.x user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Wed Feb 26 11:13:15 2014 +0100 summary: IMMTOOLS: add support for forwards compatibility of attribute flags [#116] - opensaf-4.3.x: changeset: 5027:17dfb53d8f6d branch: opensaf-4.3.x parent: 5020:5a86ab771256 user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Wed Feb 26 13:03:41 2014 +0100 summary: IMM: add support for forwards compatibility of attribute flags [#116] changeset: 5028:2071c6b320b0 branch: opensaf-4.3.x user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Wed Feb 26 13:04:16 2014 +0100 summary: IMMTOOLS: add support for forwards compatibility of attribute flags [#116] - opensaf-4.4.x: changeset: 5029:1fc514ed8859 branch: opensaf-4.4.x parent: 5024:a34a6d33ffe8 user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Wed Feb 26 16:36:44 2014 +0100 summary: IMM: add support for forwards compatibility of attribute flags [#116] changeset: 5030:ee95f259400b branch: opensaf-4.4.x user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Wed Feb 26 16:37:33 2014 +0100 summary: IMMTOOLS: add support for forwards compatibility of attribute flags [#116] - default(4.5): changeset: 5031:8fe8ae6eb6ca parent: 5022:ae54df41e16c user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Wed Feb 26 16:48:25 2014 +0100 summary: IMM: add support for forwards compatibility of attribute flags [#116] changeset: 5032:9557b2c1819f tag: tip user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Wed Feb 26 16:48:52 2014 +0100 summary: IMMTOOLS: add support for forwards compatibility of attribute flags [#116] --- ** [tickets:#116] IMMTOOLS: IMM is not forwards compatible with changes in the XML dump format** **Status:** fixed **Created:** Mon May 13, 2013 07:57 AM UTC by Zoran Milinkovic **Last Updated:** Fri Feb 21, 2014 04:47 PM UTC **Owner:** Zoran Milinkovic In order to provide compatibility with future changes in the IMM XML format, the IMM tools should ignore things like unknown attribute flags when loading an XML file. It would also be a good idea to check if the XML file uses a known version of the XML schema, and log a warning message (but still try to load it) if the version is unknown. Migrated from: http://devel.opensaf.org/ticket/3121 --- 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.-- Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #116 IMMTOOLS: IMM is not forwards compatible with changes in the XML dump format
- **status**: review -- fixed --- ** [tickets:#116] IMMTOOLS: IMM is not forwards compatible with changes in the XML dump format** **Status:** fixed **Created:** Mon May 13, 2013 07:57 AM UTC by Zoran Milinkovic **Last Updated:** Fri Feb 21, 2014 04:47 PM UTC **Owner:** Zoran Milinkovic In order to provide compatibility with future changes in the IMM XML format, the IMM tools should ignore things like unknown attribute flags when loading an XML file. It would also be a good idea to check if the XML file uses a known version of the XML schema, and log a warning message (but still try to load it) if the version is unknown. Migrated from: http://devel.opensaf.org/ticket/3121 --- 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.-- Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #794 IMM: imcfg --delete-class generates incorrect error message
opensaf-4.3.x: changeset: 5049:bf61c60558da branch: opensaf-4.3.x parent: 5046:56d8b6c5ede4 user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Tue Feb 25 09:58:18 2014 +0100 summary: IMMTOOLS: fix incorrect error message for deleting class in immcfg [#794] - opensaf-4.4.x: changeset: 5050:1873752b0343 branch: opensaf-4.4.x parent: 5047:10a21fb6be16 user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Tue Feb 25 09:58:18 2014 +0100 summary: IMMTOOLS: fix incorrect error message for deleting class in immcfg [#794] - default(4.5): changeset: 5051:4f313a050649 tag: tip parent: 5048:fdc98c16ebb5 user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Tue Feb 25 09:58:18 2014 +0100 summary: IMMTOOLS: fix incorrect error message for deleting class in immcfg [#794] --- ** [tickets:#794] IMM: imcfg --delete-class generates incorrect error message** **Status:** fixed **Milestone:** 4.3.3 **Created:** Fri Feb 21, 2014 02:06 PM UTC by Anders Bjornerstedt **Last Updated:** Tue Feb 25, 2014 09:15 AM UTC **Owner:** Zoran Milinkovic While testing a fix for catching interference between concurrent attempts to create or delete a class (ticket #757). When testing to delete a class that is currently being created I get the expected error code but: # immcfg --delete-class OpensafImmTest error - saImmOmAdminOwnerSet FAILED: SA_AIS_ERR_BUSY (10) This has nothing to do with saImmOmAdminOwnerSet. Typical copy paste error. Error strings can only be picked up from admin-operations and ccb-operations, i.e. where there is an OI involved. So it is not possible for saImmOmClassCreate or saImmOmClassDelete. --- 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.-- Subversion Kills Productivity. Get off Subversion Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #796 IMM: imm-xml tools must generate file-header that refers to latest relevant XSD
- **status**: assigned -- review --- ** [tickets:#796] IMM: imm-xml tools must generate file-header that refers to latest relevant XSD** **Status:** review **Milestone:** 4.3.3 **Created:** Tue Feb 25, 2014 12:32 PM UTC by Anders Bjornerstedt **Last Updated:** Tue Mar 04, 2014 01:09 PM UTC **Owner:** Zoran Milinkovic OpenSAF release 4.3 introduced SA_IMM_ATTR_NOTIFY and SA_IMM_ATTR_NO_DUPLICATES. OpenSAF release 4.4 introduced SA_IMM_ATTR_NO_DANGLING. The attribute tags impact not just the IMM API but also the xml export format and thus the xml schema (the XSD file). The imm-xml tools used to generate the initial imm.xml deployment file can in principle include any features defined for that release. Thus any xml file generated by the imm-xml tools should in the header of that file have a reference to the latest schema version file know by that release. The imm-xml tools are regarded as part of the imm service, but these tools also include a lot of knowledge (templates) that derive from the AMF information model. So this ticket does not have to be accepted and fixed by an imm service developer. (That is my way of asking for a little assistance from any opensaf developer interested and fluent in python coding) --- 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.-- Subversion Kills Productivity. Get off Subversion Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #796 IMM: imm-xml tools must generate file-header that refers to latest relevant XSD
opensaf-4.3.x: https://sourceforge.net/p/opensaf/mailman/message/32068887/ opensaf-4.4.x, default(4.5): https://sourceforge.net/p/opensaf/mailman/message/32068909/ --- ** [tickets:#796] IMM: imm-xml tools must generate file-header that refers to latest relevant XSD** **Status:** review **Milestone:** 4.3.3 **Created:** Tue Feb 25, 2014 12:32 PM UTC by Anders Bjornerstedt **Last Updated:** Tue Mar 04, 2014 01:09 PM UTC **Owner:** Zoran Milinkovic OpenSAF release 4.3 introduced SA_IMM_ATTR_NOTIFY and SA_IMM_ATTR_NO_DUPLICATES. OpenSAF release 4.4 introduced SA_IMM_ATTR_NO_DANGLING. The attribute tags impact not just the IMM API but also the xml export format and thus the xml schema (the XSD file). The imm-xml tools used to generate the initial imm.xml deployment file can in principle include any features defined for that release. Thus any xml file generated by the imm-xml tools should in the header of that file have a reference to the latest schema version file know by that release. The imm-xml tools are regarded as part of the imm service, but these tools also include a lot of knowledge (templates) that derive from the AMF information model. So this ticket does not have to be accepted and fixed by an imm service developer. (That is my way of asking for a little assistance from any opensaf developer interested and fluent in python coding) --- 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.-- Subversion Kills Productivity. Get off Subversion Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #796 IMM: imm-xml tools must generate file-header that refers to latest relevant XSD
- **status**: review -- fixed - **Comment**: opensaf-4.3.x: changeset: 5061:b752a65316a1 branch: opensaf-4.3.x tag: tip parent: 5058:f0d10e84063a user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Thu Mar 06 14:40:15 2014 +0100 summary: IMMTOOLS: fix the schema name for immxml tools to comply with the latest schema known by the release [#796] - opensaf-4.4.x: changeset: 5062:192cff0881ee branch: opensaf-4.4.x tag: tip parent: 5059:9e9e782a4f9c user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Thu Mar 06 14:39:12 2014 +0100 summary: IMMTOOLS: fix the schema name for immxml tools to comply with the latest schema known by the release [#796] - default(4.5): changeset: 5063:cb4523967b48 tag: tip parent: 5060:048ccfa8343d user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Thu Mar 06 14:39:12 2014 +0100 summary: IMMTOOLS: fix the schema name for immxml tools to comply with the latest schema known by the release [#796] --- ** [tickets:#796] IMM: imm-xml tools must generate file-header that refers to latest relevant XSD** **Status:** fixed **Milestone:** 4.3.3 **Created:** Tue Feb 25, 2014 12:32 PM UTC by Anders Bjornerstedt **Last Updated:** Thu Mar 06, 2014 01:51 PM UTC **Owner:** Zoran Milinkovic OpenSAF release 4.3 introduced SA_IMM_ATTR_NOTIFY and SA_IMM_ATTR_NO_DUPLICATES. OpenSAF release 4.4 introduced SA_IMM_ATTR_NO_DANGLING. The attribute tags impact not just the IMM API but also the xml export format and thus the xml schema (the XSD file). The imm-xml tools used to generate the initial imm.xml deployment file can in principle include any features defined for that release. Thus any xml file generated by the imm-xml tools should in the header of that file have a reference to the latest schema version file know by that release. The imm-xml tools are regarded as part of the imm service, but these tools also include a lot of knowledge (templates) that derive from the AMF information model. So this ticket does not have to be accepted and fixed by an imm service developer. (That is my way of asking for a little assistance from any opensaf developer interested and fluent in python coding) --- 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.-- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #824 OSAF: little endian vs. big endian systems
--- ** [tickets:#824] OSAF: little endian vs. big endian systems** **Status:** unassigned **Milestone:** future **Created:** Wed Mar 26, 2014 04:27 PM UTC by Zoran Milinkovic **Last Updated:** Wed Mar 26, 2014 04:27 PM UTC **Owner:** Zoran Milinkovic Has anyone tried to run OpenSAF in mixed endian cluster, with both little endian and big endian nodes ? According to the code, it seems that OpenSAF has been written for little endian systems, and having both a node with a little endian system and a node with a big endian system is not possible. Code of ncs_encode_* and ncs_decode_* functions had been written for little endian systems, and it works correctly. Integers are converted into network byte order (big endian), while looking from big endian system perspective, it's incorrect. Integers are converted in the opposite way. Also, macros m_NCS_OS_HTONLL_P() and m_NCS_OS_NTOHLL_P that should replace non-existing htonll and ntohll functions had been written for little endian systems. they don't work correctly in big endian systems. --- 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.-- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #47 IMM: Auto relase of lingering search handles
- **status**: assigned -- accepted --- ** [tickets:#47] IMM: Auto relase of lingering search handles** **Status:** accepted **Milestone:** future **Created:** Wed May 08, 2013 07:43 AM UTC by Anders Bjornerstedt **Last Updated:** Mon Nov 04, 2013 01:10 PM UTC **Owner:** Zoran Milinkovic Migrated from: http://devel.opensaf.org/ticket/3107 Tickets #3036 #2977 introduced a sanity limit on the number of coexisting search hadnles per om-handle. The main reason behind that enhancement was to catch application resource leaks (of search handles); provide a clear error indication instead of unpredictable system degradation; and forcing the application to deal with the problem instead of having immsv maintainers perpetually involved in locating application resource leaks. There is however a problem. It turns out that there are applications that legitimately need to allocate thousands of coexisting searches handles under one om-handle and the introduced limit is not backwards compatible for such applications. Although such applications could in principle set the IMMA_MAX_OPEN_SEARCHES_PER_HANDLE environment variable to a correspondingly high value, that would have to be done in an upgrade step associated with the application, before upgrading to OpensAF 4.3. This assumes that the application maintainers are communicating with the people doing the upgrade, which can not be guaranteed. So in our deployment, the limit mechanism of #2977 and #3036 will be disabled. An alternative mechanism, is for the server to unilaterally de-allocate lingering search handles, if the number of handles exceed the configurable limit AND some handles have been inactive beyond some time limit. The time limit would be on the order of 10 minutes. The time limit should not need to be configurable since the application that has a problem can raise the number of allowed handles. The application trying to use a search handle that has been de-allocated in the server would get BAD_HANDLE. This is of course also not strictly backwards compatible in terms of resource behavior, but it should be much lower in risk of interfering with legitimate use, or incorrect use that would be problematic to expose during an upgrade. --- 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.-- ___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #47 IMM: Auto relase of lingering search handles
- **status**: accepted -- review - **Milestone**: future -- 4.5.FC - **Comment**: https://sourceforge.net/p/opensaf/mailman/message/32158231/ --- ** [tickets:#47] IMM: Auto relase of lingering search handles** **Status:** review **Milestone:** 4.5.FC **Created:** Wed May 08, 2013 07:43 AM UTC by Anders Bjornerstedt **Last Updated:** Thu Mar 27, 2014 09:23 AM UTC **Owner:** Zoran Milinkovic Migrated from: http://devel.opensaf.org/ticket/3107 Tickets #3036 #2977 introduced a sanity limit on the number of coexisting search hadnles per om-handle. The main reason behind that enhancement was to catch application resource leaks (of search handles); provide a clear error indication instead of unpredictable system degradation; and forcing the application to deal with the problem instead of having immsv maintainers perpetually involved in locating application resource leaks. There is however a problem. It turns out that there are applications that legitimately need to allocate thousands of coexisting searches handles under one om-handle and the introduced limit is not backwards compatible for such applications. Although such applications could in principle set the IMMA_MAX_OPEN_SEARCHES_PER_HANDLE environment variable to a correspondingly high value, that would have to be done in an upgrade step associated with the application, before upgrading to OpensAF 4.3. This assumes that the application maintainers are communicating with the people doing the upgrade, which can not be guaranteed. So in our deployment, the limit mechanism of #2977 and #3036 will be disabled. An alternative mechanism, is for the server to unilaterally de-allocate lingering search handles, if the number of handles exceed the configurable limit AND some handles have been inactive beyond some time limit. The time limit would be on the order of 10 minutes. The time limit should not need to be configurable since the application that has a problem can raise the number of allowed handles. The application trying to use a search handle that has been de-allocated in the server would get BAD_HANDLE. This is of course also not strictly backwards compatible in terms of resource behavior, but it should be much lower in risk of interfering with legitimate use, or incorrect use that would be problematic to expose during an upgrade. --- 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.-- ___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #459 Imm: Dynamic deletion of application stream returns SA_AIS_ERR_NOT_EXIST during failover
- **status**: unassigned -- accepted - **assigned_to**: Zoran Milinkovic --- ** [tickets:#459] Imm: Dynamic deletion of application stream returns SA_AIS_ERR_NOT_EXIST during failover** **Status:** accepted **Milestone:** 4.5.FC **Created:** Mon Jun 17, 2013 02:17 PM UTC by Madhurika Koppula **Last Updated:** Mon Nov 11, 2013 03:37 PM UTC **Owner:** Zoran Milinkovic Migrated from http://devel.opensaf.org/ticket/2943 The immsv should add an error string to the reply for this case. --- 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.-- ___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #459 Imm: Dynamic deletion of application stream returns SA_AIS_ERR_NOT_EXIST during failover
- Description has changed: Diff: --- old +++ new @@ -2,3 +2,4 @@ The immsv should add an error string to the reply for this case. +Error string should be added for same cases in object create and object delete. - **status**: accepted -- review - **Comment**: https://sourceforge.net/p/opensaf/mailman/message/32177493/ --- ** [tickets:#459] Imm: Dynamic deletion of application stream returns SA_AIS_ERR_NOT_EXIST during failover** **Status:** review **Milestone:** 4.5.FC **Created:** Mon Jun 17, 2013 02:17 PM UTC by Madhurika Koppula **Last Updated:** Tue Apr 01, 2014 09:06 AM UTC **Owner:** Zoran Milinkovic Migrated from http://devel.opensaf.org/ticket/2943 The immsv should add an error string to the reply for this case. Error string should be added for same cases in object create and object delete. --- 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.-- ___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #834 IMM: Potential memory leak in immnd_evt_proc_ccb_compl_rsp()
- **status**: assigned -- review - **assigned_to**: Zoran Milinkovic - **Comment**: https://sourceforge.net/p/opensaf/mailman/message/32181188/ --- ** [tickets:#834] IMM: Potential memory leak in immnd_evt_proc_ccb_compl_rsp()** **Status:** review **Milestone:** 4.3.3 **Created:** Thu Apr 03, 2014 08:30 AM UTC by Anders Bjornerstedt **Last Updated:** Thu Apr 03, 2014 08:30 AM UTC **Owner:** Zoran Milinkovic There is a potential memory leak in immnd_evt_proc_ccb_compl_rsp() in immnd_evt.c where immModel_ccbGrabErrStrings() is done generically but the corresponding release (using immsv_evt_free_attrNames) is done only if the client to respond to is local. The memory leak would happen if one or more OIs reject a ccb in validation and add error strings. --- 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.-- ___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #834 IMM: Potential memory leak in immnd_evt_proc_ccb_compl_rsp()
- **status**: review -- fixed - **Comment**: opensaf-4.3.x: changeset: 5130:4419501105e0 branch: opensaf-4.3.x parent: 5125:bdd14796ea9e user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Wed Apr 09 10:56:33 2014 +0200 summary: IMM: fix memory leak in IMM [#834] - opensaf-4.4.x: changeset: 5131:6a2171548ea4 branch: opensaf-4.4.x parent: 5128:1c50b771e916 user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Wed Apr 09 10:55:35 2014 +0200 summary: IMM: fix memory leak in IMM [#834] - default(4.5): changeset: 5132:17e7a62a61a5 tag: tip parent: 5129:554cb2cd493f user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Thu Apr 03 11:13:35 2014 +0200 summary: IMM: fix memory leak in IMM [#834] --- ** [tickets:#834] IMM: Potential memory leak in immnd_evt_proc_ccb_compl_rsp()** **Status:** fixed **Milestone:** 4.3.3 **Created:** Thu Apr 03, 2014 08:30 AM UTC by Anders Bjornerstedt **Last Updated:** Thu Apr 03, 2014 09:37 AM UTC **Owner:** Zoran Milinkovic There is a potential memory leak in immnd_evt_proc_ccb_compl_rsp() in immnd_evt.c where immModel_ccbGrabErrStrings() is done generically but the corresponding release (using immsv_evt_free_attrNames) is done only if the client to respond to is local. The memory leak would happen if one or more OIs reject a ccb in validation and add error strings. --- 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.-- Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #459 Imm: Dynamic deletion of application stream returns SA_AIS_ERR_NOT_EXIST during failover
- **Comment**: http://sourceforge.net/p/opensaf/mailman/message/32223660/ --- ** [tickets:#459] Imm: Dynamic deletion of application stream returns SA_AIS_ERR_NOT_EXIST during failover** **Status:** review **Milestone:** 4.5.FC **Created:** Mon Jun 17, 2013 02:17 PM UTC by Madhurika Koppula **Last Updated:** Wed Apr 02, 2014 01:52 PM UTC **Owner:** Zoran Milinkovic Migrated from http://devel.opensaf.org/ticket/2943 The immsv should add an error string to the reply for this case. Error string should be added for same cases in object create and object delete. --- 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.-- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/NeoTech___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #47 IMM: Auto relase of lingering search handles
- **status**: review -- fixed - **Comment**: Long description is added in the pushed code. changeset: 5149:e3aaf51b69f4 tag: tip user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Tue Apr 15 11:12:31 2014 +0200 summary: IMM: release inactive search handles [#47] --- ** [tickets:#47] IMM: Auto relase of lingering search handles** **Status:** fixed **Milestone:** 4.5.FC **Created:** Wed May 08, 2013 07:43 AM UTC by Anders Bjornerstedt **Last Updated:** Tue Apr 01, 2014 08:58 AM UTC **Owner:** Zoran Milinkovic Migrated from: http://devel.opensaf.org/ticket/3107 Tickets #3036 #2977 introduced a sanity limit on the number of coexisting search hadnles per om-handle. The main reason behind that enhancement was to catch application resource leaks (of search handles); provide a clear error indication instead of unpredictable system degradation; and forcing the application to deal with the problem instead of having immsv maintainers perpetually involved in locating application resource leaks. There is however a problem. It turns out that there are applications that legitimately need to allocate thousands of coexisting searches handles under one om-handle and the introduced limit is not backwards compatible for such applications. Although such applications could in principle set the IMMA_MAX_OPEN_SEARCHES_PER_HANDLE environment variable to a correspondingly high value, that would have to be done in an upgrade step associated with the application, before upgrading to OpensAF 4.3. This assumes that the application maintainers are communicating with the people doing the upgrade, which can not be guaranteed. So in our deployment, the limit mechanism of #2977 and #3036 will be disabled. An alternative mechanism, is for the server to unilaterally de-allocate lingering search handles, if the number of handles exceed the configurable limit AND some handles have been inactive beyond some time limit. The time limit would be on the order of 10 minutes. The time limit should not need to be configurable since the application that has a problem can raise the number of allowed handles. The application trying to use a search handle that has been de-allocated in the server would get BAD_HANDLE. This is of course also not strictly backwards compatible in terms of resource behavior, but it should be much lower in risk of interfering with legitimate use, or incorrect use that would be problematic to expose during an upgrade. --- 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.-- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/NeoTech___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #53 IMM: SaDoubleT and SaFloatT attributes not handled correctly
https://sourceforge.net/p/opensaf/mailman/message/32229003/ --- ** [tickets:#53] IMM: SaDoubleT and SaFloatT attributes not handled correctly** **Status:** review **Milestone:** 4.5.FC **Created:** Wed May 08, 2013 08:15 AM UTC by Anders Bjornerstedt **Last Updated:** Tue Mar 25, 2014 03:31 PM UTC **Owner:** Zoran Milinkovic Migrated from: http://devel.opensaf.org/ticket/1554 Attribute values defined on either of the two floating point types, SaFloatT or SaDoubleT, are not handled correctly by the immsv. The problem occurs when transforming to external representation, both for transport (MDS) and storage (dump to xml or PBE). There is no htonl/ntohl for floats and when formating to ascii for xml/PBE the precision is insufficient. The solution should be to transform to ascii for *both* transport and storage and to use maximum precision in the formating and scaning. The priority for this should perhaps be major. I have set it to minor only because there are very few real immsv applications that use SaFloatT or SaDoubleT. In fact I know of none. If there where any I think this problem would have been noted earlier. --- Changing this ticket to an enhancement. I think the only problem with the current support for float and double in immsv is that precision may be lost in the conversion between host and network byte order and the casting too and from long int and long long int. --- 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.-- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/NeoTech___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #861 IMMTOOLS: parsing default values in immcfg is not backward compatible
--- ** [tickets:#861] IMMTOOLS: parsing default values in immcfg is not backward compatible** **Status:** accepted **Milestone:** 4.4.1 **Created:** Thu Apr 17, 2014 08:39 AM UTC by Zoran Milinkovic **Last Updated:** Thu Apr 17, 2014 08:39 AM UTC **Owner:** Zoran Milinkovic In ticket #20, improved parsing of values was added to immcfg, which detects an error in wrong written values and immcfg fails. It results in non-backward compatibility, and some earlier imported xml files cannot be imported now. The ticket will revert the old way of working with additional printing of warnings to stderr if the wrong defined value exists in xml file. In this case, immcfg will not fail. Also, a new flag --strict will be introduced, which means that immcfg will fail if it finds a wrong defined value in xml file. It is actually how immcfg works today. The flag will be applicable to -f and -L flags. --- 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.-- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/NeoTech___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #53 IMM: SaDoubleT and SaFloatT attributes not handled correctly
- **status**: review -- fixed - **Comment**: default(4.5): changeset: 5164:2579607cb3af user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Tue Apr 15 16:10:24 2014 +0200 summary: IMMTOOLS: fix printing and dumping for float and double values [#53] changeset: 5165:f9047da95476 tag: tip user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Tue Apr 15 16:20:03 2014 +0200 summary: IMM: fix loading double values from PBE in immload [#53] --- ** [tickets:#53] IMM: SaDoubleT and SaFloatT attributes not handled correctly** **Status:** fixed **Milestone:** 4.5.FC **Created:** Wed May 08, 2013 08:15 AM UTC by Anders Bjornerstedt **Last Updated:** Tue Apr 15, 2014 02:42 PM UTC **Owner:** Zoran Milinkovic Migrated from: http://devel.opensaf.org/ticket/1554 Attribute values defined on either of the two floating point types, SaFloatT or SaDoubleT, are not handled correctly by the immsv. The problem occurs when transforming to external representation, both for transport (MDS) and storage (dump to xml or PBE). There is no htonl/ntohl for floats and when formating to ascii for xml/PBE the precision is insufficient. The solution should be to transform to ascii for *both* transport and storage and to use maximum precision in the formating and scaning. The priority for this should perhaps be major. I have set it to minor only because there are very few real immsv applications that use SaFloatT or SaDoubleT. In fact I know of none. If there where any I think this problem would have been noted earlier. --- Changing this ticket to an enhancement. I think the only problem with the current support for float and double in immsv is that precision may be lost in the conversion between host and network byte order and the casting too and from long int and long long int. --- 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.-- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/NeoTech___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #861 IMMTOOLS: parsing default values in immcfg is not backward compatible
- **status**: accepted -- review - **Comment**: http://sourceforge.net/p/opensaf/mailman/message/32255523/ --- ** [tickets:#861] IMMTOOLS: parsing default values in immcfg is not backward compatible** **Status:** review **Milestone:** 4.4.1 **Created:** Thu Apr 17, 2014 08:39 AM UTC by Zoran Milinkovic **Last Updated:** Thu Apr 17, 2014 08:39 AM UTC **Owner:** Zoran Milinkovic In ticket #20, improved parsing of values was added to immcfg, which detects an error in wrong written values and immcfg fails. It results in non-backward compatibility, and some earlier imported xml files cannot be imported now. The ticket will revert the old way of working with additional printing of warnings to stderr if the wrong defined value exists in xml file. In this case, immcfg will not fail. Also, a new flag --strict will be introduced, which means that immcfg will fail if it finds a wrong defined value in xml file. It is actually how immcfg works today. The flag will be applicable to -f and -L flags. --- 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.-- Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eXo Platform Software Java Based Open Source Intranet - Social, Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A Collaboration Platform http://p.sf.net/sfu/ExoPlatform___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #459 Imm: Dynamic deletion of application stream returns SA_AIS_ERR_NOT_EXIST during failover
- **status**: review -- fixed - **Comment**: default(4.5): changeset: 5170:ed192ef2fa68 user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Mon Apr 14 13:56:55 2014 +0200 summary: IMM: add error strings for CCB operations for ERR_NOT_EXIST error [#459] changeset: 5171:cfb838fa1c61 tag: tip user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Mon Apr 14 13:59:21 2014 +0200 summary: IMMTOOLS: write error strings for ERR_NOT_EXIST error code in immcfg [#459] --- ** [tickets:#459] Imm: Dynamic deletion of application stream returns SA_AIS_ERR_NOT_EXIST during failover** **Status:** fixed **Milestone:** 4.5.FC **Created:** Mon Jun 17, 2013 02:17 PM UTC by Madhurika Koppula **Last Updated:** Mon Apr 14, 2014 12:16 PM UTC **Owner:** Zoran Milinkovic Migrated from http://devel.opensaf.org/ticket/2943 The immsv should add an error string to the reply for this case. Error string should be added for same cases in object create and object delete. --- 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.-- Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eXo Platform Software Java Based Open Source Intranet - Social, Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A Collaboration Platform http://p.sf.net/sfu/ExoPlatform___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #838 OSAF: OpenSAF failes to compile with 32-bit compilers
- **status**: review -- fixed - **Comment**: opensaf-4.3.x: changeset: 5176:ddd90bf704fb branch: opensaf-4.3.x tag: tip user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Wed Apr 23 16:41:47 2014 +0200 summary: OSAF: fix errors compiled with 32-bit compiler [#838] - opensaf-4.4.x: changeset: 5177:132833c3a636 branch: opensaf-4.4.x tag: tip parent: 5173:877b21e0ab2c user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Wed Apr 23 16:50:39 2014 +0200 summary: IMMTOOLS: fix errors compiled with 32-bit compiler [#838] - default(4.5): changeset: 5178:a29955c4fd43 tag: tip parent: 5174:91e49ceba5d0 user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Wed Apr 23 16:50:39 2014 +0200 summary: IMMTOOLS: fix errors compiled with 32-bit compiler [#838] --- ** [tickets:#838] OSAF: OpenSAF failes to compile with 32-bit compilers** **Status:** fixed **Milestone:** 4.3.3 **Created:** Mon Apr 07, 2014 02:43 PM UTC by Zoran Milinkovic **Last Updated:** Tue Apr 08, 2014 09:07 AM UTC **Owner:** Zoran Milinkovic Using 32-bit gcc, OpenSAF fails to compile. For OpenSAF 4.3, it fails for NTF and LOG. For OpenSAF 4.4, and default(4.5), it fails for immcfg. --- 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.-- Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eXo Platform Software Java Based Open Source Intranet - Social, Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A Collaboration Platform http://p.sf.net/sfu/ExoPlatform___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #861 IMMTOOLS: parsing default values in immcfg is not backward compatible
- **status**: review -- fixed - **Comment**: opensaf-4.4.x: changeset: 5188:87e81f29ed22 branch: opensaf-4.4.x parent: 5186:df71c692fec6 user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Fri Apr 25 15:56:08 2014 +0200 summary: immtools: revert old way of parsing default values and add a flag for more strict parsing values in immcfg [#861] - default(4.5): changeset: 5189:2211a1cd00d0 tag: tip parent: 5187:7a195e2c63c9 user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Fri Apr 25 15:56:08 2014 +0200 summary: immtools: revert old way of parsing default values and add a flag for more strict parsing values in immcfg [#861] --- ** [tickets:#861] IMMTOOLS: parsing default values in immcfg is not backward compatible** **Status:** fixed **Milestone:** 4.4.1 **Created:** Thu Apr 17, 2014 08:39 AM UTC by Zoran Milinkovic **Last Updated:** Tue Apr 22, 2014 03:02 PM UTC **Owner:** Zoran Milinkovic In ticket #20, improved parsing of values was added to immcfg, which detects an error in wrong written values and immcfg fails. It results in non-backward compatibility, and some earlier imported xml files cannot be imported now. The ticket will revert the old way of working with additional printing of warnings to stderr if the wrong defined value exists in xml file. In this case, immcfg will not fail. Also, a new flag --strict will be introduced, which means that immcfg will fail if it finds a wrong defined value in xml file. It is actually how immcfg works today. The flag will be applicable to -f and -L flags. --- 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.-- Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eXo Platform Software Java Based Open Source Intranet - Social, Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A Collaboration Platform http://p.sf.net/sfu/ExoPlatform___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #907 imm: memory leak in closing search handles
--- ** [tickets:#907] imm: memory leak in closing search handles** **Status:** accepted **Milestone:** 4.4.1 **Created:** Tue May 13, 2014 08:07 AM UTC by Zoran Milinkovic **Last Updated:** Tue May 13, 2014 08:07 AM UTC **Owner:** Zoran Milinkovic When a search is initialized for many objects in the result, and when the search handle is closed (either by saImmOmSearchFinalize or by saImmOmFinalize) before saImmOmSearchNext reach the last object in the result, IMM library makes a memory leak. --- 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.-- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #907 imm: memory leak in closing search handles
- **status**: review -- fixed - **Comment**: opensaf-4.4.x: changeset: 5249:77da9cb8a72f branch: opensaf-4.4.x parent: 5246:5c7c9b1db66e user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Tue May 13 10:20:48 2014 +0200 summary: imm: fix memory leak in IMM library when search handle is closed [#907] - default(4.5): changeset: 5251:68e08eb2c489 tag: tip user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Tue May 13 10:20:48 2014 +0200 summary: imm: fix memory leak in IMM library when search handle is closed [#907] --- ** [tickets:#907] imm: memory leak in closing search handles** **Status:** fixed **Milestone:** 4.4.1 **Created:** Tue May 13, 2014 08:07 AM UTC by Zoran Milinkovic **Last Updated:** Tue May 13, 2014 08:33 AM UTC **Owner:** Zoran Milinkovic When a search is initialized for many objects in the result, and when the search handle is closed (either by saImmOmSearchFinalize or by saImmOmFinalize) before saImmOmSearchNext reach the last object in the result, IMM library makes a memory leak. --- 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.-- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #53 IMM: SaDoubleT and SaFloatT attributes not handled correctly
- **status**: fixed -- accepted - **Comment**: The ticket is reopened for fixing the loading of the first value of double attribute from PBE. --- ** [tickets:#53] IMM: SaDoubleT and SaFloatT attributes not handled correctly** **Status:** accepted **Milestone:** 4.5.FC **Created:** Wed May 08, 2013 08:15 AM UTC by Anders Bjornerstedt **Last Updated:** Thu Apr 17, 2014 01:27 PM UTC **Owner:** Zoran Milinkovic Migrated from: http://devel.opensaf.org/ticket/1554 Attribute values defined on either of the two floating point types, SaFloatT or SaDoubleT, are not handled correctly by the immsv. The problem occurs when transforming to external representation, both for transport (MDS) and storage (dump to xml or PBE). There is no htonl/ntohl for floats and when formating to ascii for xml/PBE the precision is insufficient. The solution should be to transform to ascii for *both* transport and storage and to use maximum precision in the formating and scaning. The priority for this should perhaps be major. I have set it to minor only because there are very few real immsv applications that use SaFloatT or SaDoubleT. In fact I know of none. If there where any I think this problem would have been noted earlier. --- Changing this ticket to an enhancement. I think the only problem with the current support for float and double in immsv is that precision may be lost in the conversion between host and network byte order and the casting too and from long int and long long int. --- 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.-- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #53 IMM: SaDoubleT and SaFloatT attributes not handled correctly
- **status**: accepted -- review - **Comment**: https://sourceforge.net/p/opensaf/mailman/message/32360574/ --- ** [tickets:#53] IMM: SaDoubleT and SaFloatT attributes not handled correctly** **Status:** review **Milestone:** 4.5.FC **Created:** Wed May 08, 2013 08:15 AM UTC by Anders Bjornerstedt **Last Updated:** Tue May 20, 2014 02:29 PM UTC **Owner:** Zoran Milinkovic Migrated from: http://devel.opensaf.org/ticket/1554 Attribute values defined on either of the two floating point types, SaFloatT or SaDoubleT, are not handled correctly by the immsv. The problem occurs when transforming to external representation, both for transport (MDS) and storage (dump to xml or PBE). There is no htonl/ntohl for floats and when formating to ascii for xml/PBE the precision is insufficient. The solution should be to transform to ascii for *both* transport and storage and to use maximum precision in the formating and scaning. The priority for this should perhaps be major. I have set it to minor only because there are very few real immsv applications that use SaFloatT or SaDoubleT. In fact I know of none. If there where any I think this problem would have been noted earlier. --- Changing this ticket to an enhancement. I think the only problem with the current support for float and double in immsv is that precision may be lost in the conversion between host and network byte order and the casting too and from long int and long long int. --- 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.-- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #16 IMM: Configigurable OI callback server-side timeout per OI-handle.
https://sourceforge.net/p/opensaf/mailman/message/32315376/ --- ** [tickets:#16] IMM: Configigurable OI callback server-side timeout per OI-handle.** **Status:** review **Milestone:** 4.5.FC **Created:** Tue May 07, 2013 08:28 AM UTC by Anders Bjornerstedt **Last Updated:** Thu May 08, 2014 12:09 PM UTC **Owner:** Zoran Milinkovic There is a need for configurable timeout for IMMND OI callbacks, i.e. the timeout for how long the imm-service will wait for a reply on an OI callback. Currently there is a hardwired timer of 6 seconds. Version A.03.01 of the SAF IMM standard does in fact define such an attribute 'saImmOiTimeout', which is one reason that A.03.01 is actually not backwards compatible with A.02.01 (Schema upgrades are not supported in the official A.03.01 standard. Schema upgrades are however supported by the OpenSAF IMM). The 'saImmOiTimeout' is already present in the definition of the SaImmMngt class since OpenSAF 4.1. This despite that the OpenSAF IMM does not support the A.03.01 version. The imm service ignores this attribute currently. But the concept of having *one* config attribute controlling the timeout for *all* OIs in the system, has severe problems. See comments below. Because of this, we alter the proposed solution to the problem. Instead of using this single config attribute, we will use an environment variable recognized by the IMMA library. This will follow the same pattern as the existing IMMA_SYNCR_TIMEOUT that configures the timeout for blocking downcalls (in both the OM and OI libraries). A new environment variable IMMA_OI_CALLBACK_TIMEOUT will be recognized by the OI library. Just as for the existing IMMA_SYNCR_TIMEOUT, this environment variable is sampled by the SaImmOiInitialize function for initializing an oi-handle. The handle will have that timeout associated with it for the rest of its lifetime. Different OI handles can have different timeouts by changing the value of IMMA_OI_CALLBACK_TIMEOUT prior to each saImmOiIntitialize. The library will send the handles callback timeout-value down to the server as an added part to the message used by saImmOiImplementerSet Migrated from: http://devel.opensaf.org/ticket/2021 --- 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.-- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://www.hpccsystems.com___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #16 IMM: Configigurable OI callback server-side timeout per OI-handle.
- **status**: accepted -- review - **Comment**: https://sourceforge.net/p/opensaf/mailman/message/32618117/ --- ** [tickets:#16] IMM: Configigurable OI callback server-side timeout per OI-handle.** **Status:** review **Milestone:** 4.5.FC **Created:** Tue May 07, 2013 08:28 AM UTC by Anders Bjornerstedt **Last Updated:** Wed Jul 16, 2014 10:02 AM UTC **Owner:** Zoran Milinkovic There is a need for configurable timeout for IMMND OI callbacks, i.e. the timeout for how long the imm-service will wait for a reply on an OI callback. Currently there is a hardwired timer of 6 seconds. Version A.03.01 of the SAF IMM standard does in fact define such an attribute 'saImmOiTimeout', which is one reason that A.03.01 is actually not backwards compatible with A.02.01 (Schema upgrades are not supported in the official A.03.01 standard. Schema upgrades are however supported by the OpenSAF IMM). The 'saImmOiTimeout' is already present in the definition of the SaImmMngt class since OpenSAF 4.1. This despite that the OpenSAF IMM does not support the A.03.01 version. The imm service ignores this attribute currently. But the concept of having *one* config attribute controlling the timeout for *all* OIs in the system, has severe problems. See comments below. Because of this, we alter the proposed solution to the problem. Instead of using this single config attribute, we will use an environment variable recognized by the IMMA library. This will follow the same pattern as the existing IMMA_SYNCR_TIMEOUT that configures the timeout for blocking downcalls (in both the OM and OI libraries). A new environment variable IMMA_OI_CALLBACK_TIMEOUT will be recognized by the OI library. Just as for the existing IMMA_SYNCR_TIMEOUT, this environment variable is sampled by the SaImmOiInitialize function for initializing an oi-handle. The handle will have that timeout associated with it for the rest of its lifetime. Different OI handles can have different timeouts by changing the value of IMMA_OI_CALLBACK_TIMEOUT prior to each saImmOiIntitialize. The library will send the handles callback timeout-value down to the server as an added part to the message used by saImmOiImplementerSet Migrated from: http://devel.opensaf.org/ticket/2021 --- 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.-- Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #886 IMM: Add support for long DNs in existing IMM APIs.
- **status**: review -- fixed - **Comment**: default(4.5): changeset: 5483:dc3fbdbd96d5 user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Fri Jul 25 13:56:15 2014 +0200 summary: imm: add support for long DN to IMM service [#886] changeset: 5484:e2b0532473da user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Fri Jul 25 13:57:15 2014 +0200 summary: imm: add support for long DN to IMM library [#886] changeset: 5485:243d58ea9d48 user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Fri Jul 25 13:58:09 2014 +0200 summary: immtools: add support for long DN to IMM tools [#886] changeset: 5486:9a46e323a13f tag: tip user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Fri Jul 25 13:59:52 2014 +0200 summary: immtest: add test cases for long DN [#886] --- ** [tickets:#886] IMM: Add support for long DNs in existing IMM APIs.** **Status:** fixed **Milestone:** 4.5.FC **Created:** Tue May 06, 2014 08:14 AM UTC by Anders Bjornerstedt **Last Updated:** Mon Jul 14, 2014 03:01 PM UTC **Owner:** Zoran Milinkovic Enhancement ticket [#191] introduces support for tunneling long DNs through the existing SaNameT type. This allows existing APIs to be enhanced to support handling of long DNs. This enhancement ticket tracks the introduction of such support for long DNs in the existing IMM APIs. By default, support for long DNs will be disabled in the old SaNameT based APIs. Support for long DNs is enabled per IMMA client by setting the environment variable SA_ENABLE_EXTENDED_NAMES to the value 1, see README.00.conf. Enhancement ticket [#643] is related to this. It introduces a new IMM API where all use of SaNameT has been removed and replaced with SaStringT or SaConstStringT. That API will be available only to clients initializing with IMM API version A.2.14. The new SaStringT based API will by default allow long DNs. To disallow long DNs while using the new IMM API will be possible by setting the environment variable SA_ENABLE_EXTENDED_NAMES to the value 0. --- 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.-- Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #16 IMM: Configigurable OI callback server-side timeout per OI-handle.
- **status**: review -- fixed - **Comment**: default(4.5): changeset: 5487:b6dfd46ec94e user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Fri Jul 25 15:00:42 2014 +0200 summary: imm: add support for configurable OI callback timeout [#16] changeset: 5488:b00e638de216 user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Fri Jul 25 15:01:27 2014 +0200 summary: imm: use IMMA_OI_CALLBACK_TIMEOUT for setting OI callback timeout [#16] changeset: 5489:52dbf65847a0 user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Fri Jul 25 15:02:16 2014 +0200 summary: immtests: add test cases for OI callback timeout [#16] changeset: 5490:e6ab06fa6808 tag: tip user:Anders Bjornerstedt anders.bjornerst...@ericsson.com date:Thu May 08 18:10:17 2014 +0200 summary: imm: update immsv/README for IMMA_OI_CALLBACK_TIMEOUT [#16] --- ** [tickets:#16] IMM: Configigurable OI callback server-side timeout per OI-handle.** **Status:** fixed **Milestone:** 4.5.FC **Created:** Tue May 07, 2013 08:28 AM UTC by Anders Bjornerstedt **Last Updated:** Thu Jul 17, 2014 03:08 PM UTC **Owner:** Zoran Milinkovic There is a need for configurable timeout for IMMND OI callbacks, i.e. the timeout for how long the imm-service will wait for a reply on an OI callback. Currently there is a hardwired timer of 6 seconds. Version A.03.01 of the SAF IMM standard does in fact define such an attribute 'saImmOiTimeout', which is one reason that A.03.01 is actually not backwards compatible with A.02.01 (Schema upgrades are not supported in the official A.03.01 standard. Schema upgrades are however supported by the OpenSAF IMM). The 'saImmOiTimeout' is already present in the definition of the SaImmMngt class since OpenSAF 4.1. This despite that the OpenSAF IMM does not support the A.03.01 version. The imm service ignores this attribute currently. But the concept of having *one* config attribute controlling the timeout for *all* OIs in the system, has severe problems. See comments below. Because of this, we alter the proposed solution to the problem. Instead of using this single config attribute, we will use an environment variable recognized by the IMMA library. This will follow the same pattern as the existing IMMA_SYNCR_TIMEOUT that configures the timeout for blocking downcalls (in both the OM and OI libraries). A new environment variable IMMA_OI_CALLBACK_TIMEOUT will be recognized by the OI library. Just as for the existing IMMA_SYNCR_TIMEOUT, this environment variable is sampled by the SaImmOiInitialize function for initializing an oi-handle. The handle will have that timeout associated with it for the rest of its lifetime. Different OI handles can have different timeouts by changing the value of IMMA_OI_CALLBACK_TIMEOUT prior to each saImmOiIntitialize. The library will send the handles callback timeout-value down to the server as an added part to the message used by saImmOiImplementerSet Migrated from: http://devel.opensaf.org/ticket/2021 --- 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.-- Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1001 IMM: PBE fails in sqlite on commit of CCB object create
- **status**: review -- fixed
- **Comment**:
opensaf-4.5.x:
changeset: 5639:6f91a7303ffa
branch: opensaf-4.5.x
parent: 5637:35734330f2ec
user:Zoran Milinkovic zoran.milinko...@ericsson.com
date:Thu Aug 21 16:14:28 2014 +0200
summary: immtools: fix memory release of object names when CCB data is
deleted [#1001]
-
default(4.6):
changeset: 5640:519dded451af
tag: tip
parent: 5638:5542e0886de4
user:Zoran Milinkovic zoran.milinko...@ericsson.com
date:Thu Aug 21 16:14:28 2014 +0200
summary: immtools: fix memory release of object names when CCB data is
deleted [#1001]
---
** [tickets:#1001] IMM: PBE fails in sqlite on commit of CCB object create**
**Status:** fixed
**Milestone:** 4.5.0
**Created:** Thu Aug 21, 2014 05:38 AM UTC by Sirisha Alla
**Last Updated:** Thu Aug 21, 2014 02:43 PM UTC
**Owner:** Zoran Milinkovic
This issue is seen on SLES 64bit 4 node VMs. The changeset of OpenSAF used is
5608 along with patches for #938,#994 and #997.
IMM applications are in progress when the issue is observed. During one of the
CCB commit operations following is observed on the active controller:
Aug 21 10:15:44 SLES-64BIT-SLOT1 osafimmpbed: ER SQL statement('INSERT INTO
objects (obj_id, class_id, dn, last_ccb) VALUES (?, ?, ?, ?)') failed with
error code: 19
Aug 21 10:15:44 SLES-64BIT-SLOT1 osafimmnd[3645]: NO Invalid error reported
implementer 'OpenSafImmPBE', Ccb 46 will be aborted
Aug 21 10:15:44 SLES-64BIT-SLOT1 osafimmnd[3645]: NO Ccb 46 ABORTED (exowner)
Aug 21 10:15:44 SLES-64BIT-SLOT1 osafimmpbed: WA Failed to find CCB object for
2e/46
Once this error is seen further CCB commits(ccbApply()) fail with
FAILED_OPERATION. Cluster becomes unusable for CCB commit operations.
Aug 21 10:15:50 SLES-64BIT-SLOT1 osafimmpbed: ER Failed to bind obj_id with
error code: 21
Aug 21 10:15:50 SLES-64BIT-SLOT1 osafimmnd[3645]: NO Invalid error reported
implementer 'OpenSafImmPBE', Ccb 47 will be aborted
Aug 21 10:15:50 SLES-64BIT-SLOT1 osafimmnd[3645]: NO Ccb 47 ABORTED (adminOwner)
Aug 21 10:15:50 SLES-64BIT-SLOT1 osafimmpbed: WA Failed to find CCB object for
2f/47
Aug 21 10:15:52 SLES-64BIT-SLOT1 osafimmpbed: IN Create of class
noDanglingPreconfigurationClass committing with ccbId:10089
Aug 21 10:15:53 SLES-64BIT-SLOT1 osafimmnd[3645]: NO Create of class
noDanglingPreconfigurationClass is PERSISTENT.
Aug 21 10:15:53 SLES-64BIT-SLOT1 osafimmpbed: ER Failed to bind obj_id with
error code: 21
Aug 21 10:15:53 SLES-64BIT-SLOT1 osafimmnd[3645]: NO Invalid error reported
implementer 'OpenSafImmPBE', Ccb 92 will be aborted
Aug 21 10:15:53 SLES-64BIT-SLOT1 osafimmnd[3645]: NO Ccb 92 ABORTED
(noDanglingPreconfigurationClass)
Aug 21 10:15:53 SLES-64BIT-SLOT1 osafimmpbed: WA Failed to find CCB object for
5c/92
Aug 21 10:15:53 SLES-64BIT-SLOT1 osafimmpbed: IN Delete of class
noDanglingPreconfigurationClass committing with ccbId:1008a
Aug 21 10:15:53 SLES-64BIT-SLOT1 osafimmnd[3645]: NO Delete of class
noDanglingPreconfigurationClass is PERSISTENT.
Aug 21 10:15:53 SLES-64BIT-SLOT1 osafimmpbed: IN Create of class
immsv_N0_Dangling_test01 committing with ccbId:1008b
Aug 21 10:15:53 SLES-64BIT-SLOT1 osafimmnd[3645]: NO Create of class
immsv_N0_Dangling_test01 is PERSISTENT.
Aug 21 10:15:53 SLES-64BIT-SLOT1 osafimmpbed: ER Failed to bind obj_id with
error code: 21
Aug 21 10:15:53 SLES-64BIT-SLOT1 osafimmnd[3645]: NO Invalid error reported
implementer 'OpenSafImmPBE', Ccb 98 will be aborted
Aug 21 10:15:53 SLES-64BIT-SLOT1 osafimmnd[3645]: NO Ccb 98 ABORTED
(immsv_N0_Dangling_test01)
Aug 21 10:15:53 SLES-64BIT-SLOT1 osafimmpbed: WA Failed to find CCB object for
62/98
This issue is reproducible. Traces are attached. IMMD traces are available and
will be able to share them on request. I am not sure whether this is
consequence after #1000 is observed. I will try to see if this can be
reproduced independantly.
---
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.--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #980 IMM: immcfg coredump when creating long dn object
- **status**: unassigned -- accepted - **assigned_to**: Zoran Milinkovic --- ** [tickets:#980] IMM: immcfg coredump when creating long dn object** **Status:** accepted **Milestone:** 4.5.0 **Created:** Fri Aug 08, 2014 07:38 PM UTC by Minh Hon Chau **Last Updated:** Fri Aug 15, 2014 03:09 PM UTC **Owner:** Zoran Milinkovic Coredump on immcfg by following test: root@uvb:~/ grep EXTENDED /etc/opensaf/immnd.conf export SA_ENABLE_EXTENDED_NAMES=1 root@uvb:~/ immcfg -m -a longDnsAllowed=1 opensafImm=opensafImm,safApp=safImmService root@uvb:~/ immcfg -f longdn_class.xml root@uvb:~/ immcfg -c OsafNtfCmTestCFG stringRdnCfg=abcd root@uvb:~/ immcfg -a testNameCfg=123 stringRdnCfg=abcd root@uvb:~/ immlist stringRdnCfg=abcd Name Type Value(s) testNameCfgSA_NAME_T123 (3) stringRdnCfg SA_STRING_T stringRdnCfg=abcd SaImmAttrImplementerName SA_STRING_T Empty SaImmAttrClassName SA_STRING_T OsafNtfCmTestCFG SaImmAttrAdminOwnerNameSA_STRING_T Empty root@uvb:~/ immcfg -a testNameCfg= stringRdnCfg=abcd Aborted (core dumped) --- The longdn_class.xml as below: imm:IMM-contents xsi:noNamespaceSchemaLocation=SAI-AIS-IMM-XSD-A.01.01.xsd class name=OsafNtfCmTestCFG categorySA_CONFIG/category rdn namestringRdnCfg/name typeSA_STRING_T/type categorySA_CONFIG/category flagSA_INITIALIZED/flag flagSA_NOTIFY/flag /rdn attr nametestNameCfg/name typeSA_NAME_T/type categorySA_CONFIG/category flagSA_MULTI_VALUE/flag flagSA_NOTIFY/flag flagSA_WRITABLE/flag /attr /class /imm:IMM-contents the backtrace as below: Core was generated by `immcfg -a testNameCfg=1'. Program terminated with signal SIGABRT, Aborted. \#0 0x415d5f79 in raise () from /lib64/libc.so.6 (gdb) bt \#0 0x415d5f79 in raise () from /lib64/libc.so.6 \#1 0x415d9388 in abort () from /lib64/libc.so.6 \#2 0x409c5cbe in __osafassert_fail (__file=__file@entry=0x409f9cd1 osaf_extended_name.c, __line=__line@entry=130, __func=__func@entry=0x409f9d60 __FUNCTION__.3257 osaf_extended_name_length, __assertion=__assertion@entry=0x409f9d10 osaf_extended_names_enabled length = SA_MAX_UNEXTENDED_NAME_LENGTH) at sysf_def.c:281 \#3 0x409c3936 in osaf_extended_name_length (name=name@entry=0x62dc60) at osaf_extended_name.c:129 \#4 0x40c322fd in imma_copyAttrValue (p=0x62d870, attrValueType=SA_IMM_ATTR_SANAMET, attrValue=0x62dc60) at imma_init.c:421 \#5 0x40c24e77 in saImmOmCcbObjectModify_2 (ccbHandle=ccbHandle@entry=1406852104797087000, objectName=objectName@entry=0x61b240, attrMods=attrMods@entry=0x62dc40) at imma_om_api.c:2349 \#6 0x00412ddc in immutil_saImmOmCcbObjectModify_2 (immCcbHandle=1406852104797087000, objectName=0x61b240, attrMods=attrMods@entry=0x62dc40) at immutil.c:1540 \#7 0x0040d2ee in object_modify (objectNames=objectNames@entry=0x61b220, optargs=optargs@entry=0x61b010, optargs_len=optargs_len@entry=1) at imm_cfg.c:589 \#8 0x0040e894 in imm_operation (argc=4, argv=optimised out) at imm_cfg.c:1439 \#9 0x415c0ec5 in __libc_start_main () from /lib64/libc.so.6 \#10 0x0040378e in _start () (gdb) f 2 \#2 0x409c5cbe in __osafassert_fail (__file=__file@entry=0x409f9cd1 osaf_extended_name.c, __line=__line@entry=130, __func=__func@entry=0x409f9d60 __FUNCTION__.3257 osaf_extended_name_length, __assertion=__assertion@entry=0x409f9d10 osaf_extended_names_enabled length = SA_MAX_UNEXTENDED_NAME_LENGTH) at sysf_def.c:281 281 abort(); (gdb) p osaf_extended_names_enabled $1 = false (gdb) --- 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
[tickets] [opensaf:tickets] #980 IMM: immcfg coredump when creating long dn object
- **status**: accepted -- review - **Part**: nd -- tools - **Comment**: https://sourceforge.net/p/opensaf/mailman/message/32757659/ --- ** [tickets:#980] IMM: immcfg coredump when creating long dn object** **Status:** review **Milestone:** 4.5.0 **Created:** Fri Aug 08, 2014 07:38 PM UTC by Minh Hon Chau **Last Updated:** Fri Aug 22, 2014 10:46 AM UTC **Owner:** Zoran Milinkovic Coredump on immcfg by following test: root@uvb:~/ grep EXTENDED /etc/opensaf/immnd.conf export SA_ENABLE_EXTENDED_NAMES=1 root@uvb:~/ immcfg -m -a longDnsAllowed=1 opensafImm=opensafImm,safApp=safImmService root@uvb:~/ immcfg -f longdn_class.xml root@uvb:~/ immcfg -c OsafNtfCmTestCFG stringRdnCfg=abcd root@uvb:~/ immcfg -a testNameCfg=123 stringRdnCfg=abcd root@uvb:~/ immlist stringRdnCfg=abcd Name Type Value(s) testNameCfgSA_NAME_T123 (3) stringRdnCfg SA_STRING_T stringRdnCfg=abcd SaImmAttrImplementerName SA_STRING_T Empty SaImmAttrClassName SA_STRING_T OsafNtfCmTestCFG SaImmAttrAdminOwnerNameSA_STRING_T Empty root@uvb:~/ immcfg -a testNameCfg= stringRdnCfg=abcd Aborted (core dumped) --- The longdn_class.xml as below: imm:IMM-contents xsi:noNamespaceSchemaLocation=SAI-AIS-IMM-XSD-A.01.01.xsd class name=OsafNtfCmTestCFG categorySA_CONFIG/category rdn namestringRdnCfg/name typeSA_STRING_T/type categorySA_CONFIG/category flagSA_INITIALIZED/flag flagSA_NOTIFY/flag /rdn attr nametestNameCfg/name typeSA_NAME_T/type categorySA_CONFIG/category flagSA_MULTI_VALUE/flag flagSA_NOTIFY/flag flagSA_WRITABLE/flag /attr /class /imm:IMM-contents the backtrace as below: Core was generated by `immcfg -a testNameCfg=1'. Program terminated with signal SIGABRT, Aborted. \#0 0x415d5f79 in raise () from /lib64/libc.so.6 (gdb) bt \#0 0x415d5f79 in raise () from /lib64/libc.so.6 \#1 0x415d9388 in abort () from /lib64/libc.so.6 \#2 0x409c5cbe in __osafassert_fail (__file=__file@entry=0x409f9cd1 osaf_extended_name.c, __line=__line@entry=130, __func=__func@entry=0x409f9d60 __FUNCTION__.3257 osaf_extended_name_length, __assertion=__assertion@entry=0x409f9d10 osaf_extended_names_enabled length = SA_MAX_UNEXTENDED_NAME_LENGTH) at sysf_def.c:281 \#3 0x409c3936 in osaf_extended_name_length (name=name@entry=0x62dc60) at osaf_extended_name.c:129 \#4 0x40c322fd in imma_copyAttrValue (p=0x62d870, attrValueType=SA_IMM_ATTR_SANAMET, attrValue=0x62dc60) at imma_init.c:421 \#5 0x40c24e77 in saImmOmCcbObjectModify_2 (ccbHandle=ccbHandle@entry=1406852104797087000, objectName=objectName@entry=0x61b240, attrMods=attrMods@entry=0x62dc40) at imma_om_api.c:2349 \#6 0x00412ddc in immutil_saImmOmCcbObjectModify_2 (immCcbHandle=1406852104797087000, objectName=0x61b240, attrMods=attrMods@entry=0x62dc40) at immutil.c:1540 \#7 0x0040d2ee in object_modify (objectNames=objectNames@entry=0x61b220, optargs=optargs@entry=0x61b010, optargs_len=optargs_len@entry=1) at imm_cfg.c:589 \#8 0x0040e894 in imm_operation (argc=4, argv=optimised out) at imm_cfg.c:1439 \#9 0x415c0ec5 in __libc_start_main () from /lib64/libc.so.6 \#10 0x0040378e in _start () (gdb) f 2 \#2 0x409c5cbe in __osafassert_fail (__file=__file@entry=0x409f9cd1 osaf_extended_name.c, __line=__line@entry=130, __func=__func@entry=0x409f9d60 __FUNCTION__.3257 osaf_extended_name_length, __assertion=__assertion@entry=0x409f9d10 osaf_extended_names_enabled length = SA_MAX_UNEXTENDED_NAME_LENGTH) at sysf_def.c:281 281 abort(); (gdb) p osaf_extended_names_enabled $1 = false (gdb) --- 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] [opensaf:tickets] #974 IMM: Loading of xml or PBE will fail with objects having longdns
- **status**: unassigned -- review - **assigned_to**: Zoran Milinkovic - **Comment**: https://sourceforge.net/p/opensaf/mailman/message/32762280/ --- ** [tickets:#974] IMM: Loading of xml or PBE will fail with objects having longdns** **Status:** review **Milestone:** 4.5.0 **Created:** Fri Aug 01, 2014 11:33 AM UTC by Neelakanta Reddy **Last Updated:** Mon Aug 25, 2014 12:28 PM UTC **Owner:** Zoran Milinkovic Description: 1. Create the longdn objects with dn Lexicographic ahead of dn opensafImm=opensafImm,safApp=safImmService 2. take the dump with immdump or load from PBE. 3. restart the cluster and try to load with the xml generated by immdump or imm.db 4. loading fails with following error: syslog: Aug 1 16:51:43 Slot-3 osafimmloadd: NO Load starting Aug 1 16:51:43 Slot-3 osafimmloadd: NO IMMSV_PBE_FILE is defined (imm.db) check it for existence and SaImmRepositoryInitModeT Aug 1 16:51:43 Slot-3 osafimmloadd: IN File '/etc/opensaf/imm.db' is not accessible for read/write, cause:No such file or directory Aug 1 16:51:43 Slot-3 osafimmloadd: WA Could not open repository:imm.db Aug 1 16:51:43 Slot-3 osafimmloadd: NO * Loading from XML file imm.xml at /etc/opensaf * Aug 1 16:51:43 Slot-3 osafimmloadd: ER Failed to create object err: 13, class: testClass6, dn: 'tEstAttr=0'. Check for duplicate attributes, or trace osafimmloadd Aug 1 16:51:43 Slot-3 osafimmloadd: NO Failed to create object - exiting Aug 1 16:51:43 Slot-3 osafimmnd[5640]: WA Hard close of admin owner IMMLOADER id(1)= Loading must have failed Aug 1 16:51:43 Slot-3 osafimmnd[5640]: ER LOADING APPARENTLY FAILED status:1 Aug 1 16:51:43 Slot-3 osafimmd[5625]: ER LOADING FAILED. File(s) possibly missing, inaccessible or corrupt .. ? * Aug 1 16:51:43 Slot-3 opensafd[5564]: ER Failed DESC:IMMND IMMND traces: Aug 1 16:51:43.313401 osafimmnd [5640:immnd_evt.c:5605] immnd_evt_proc_object_create Aug 1 16:51:43.313409 osafimmnd [5640:ImmModel.cc:6423] ccbObjectCreate Aug 1 16:51:43.313415 osafimmnd [5640:ImmModel.cc:6436] T2 parentName: Aug 1 16:51:43.313423 osafimmnd [5640:ImmModel.cc:2563] getLongDnsAllowed Aug 1 16:51:43.313428 osafimmnd [5640:ImmModel.cc:2574] getLongDnsAllowed Aug 1 16:51:43.313453 osafimmnd [5640:ImmModel.cc:6758] T7 ERR_NAME_TOO_LONG: DN is too long, size:786, max size is:2048 Aug 1 16:51:43.313461 osafimmnd [5640:ImmModel.cc:7376] ccbObjectCreate Aug 1 16:51:43.313467 osafimmnd [5640:immnd_evt.c:5774] T2 send immediate reply to client/agent The loading failed because longDnsPermitted is false(getLongDnsAllowed () will return false). The possible solution may be delay the loading of objects until IMM object opensafImm=opensafImm,safApp=safImmService is created or if longdns are present delay the longdn objects until opensafImm=opensafImm,safApp=safImmService is created. --- 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.-- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1008 IMM: Changes to access control attribute should be local validated
- **status**: unassigned -- accepted - **assigned_to**: Zoran Milinkovic --- ** [tickets:#1008] IMM: Changes to access control attribute should be local validated** **Status:** accepted **Milestone:** 4.5.0 **Created:** Fri Aug 22, 2014 01:52 PM UTC by Anders Bjornerstedt **Last Updated:** Fri Aug 22, 2014 01:52 PM UTC **Owner:** Zoran Milinkovic Validation logic should be added to ImmModel::ccbObjectmodify checking that updates to the 'ccessControlMode' attribute in the OpensAF service object are in the value range of the enum defined for it. Local validation can be done here because there is no inter-object relation from this attribute with anything else (currently) in the imm model. --- 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.-- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #980 IMM: immcfg coredump when creating long dn object
- **status**: review -- invalid - **Comment**: SA_ENABLE_EXTENDED_NAMES should have been set to 1 before immcfg --- ** [tickets:#980] IMM: immcfg coredump when creating long dn object** **Status:** invalid **Milestone:** 4.5.0 **Created:** Fri Aug 08, 2014 07:38 PM UTC by Minh Hon Chau **Last Updated:** Wed Aug 27, 2014 10:23 AM UTC **Owner:** Zoran Milinkovic Coredump on immcfg by following test: root@uvb:~/ grep EXTENDED /etc/opensaf/immnd.conf export SA_ENABLE_EXTENDED_NAMES=1 root@uvb:~/ immcfg -m -a longDnsAllowed=1 opensafImm=opensafImm,safApp=safImmService root@uvb:~/ immcfg -f longdn_class.xml root@uvb:~/ immcfg -c OsafNtfCmTestCFG stringRdnCfg=abcd root@uvb:~/ immcfg -a testNameCfg=123 stringRdnCfg=abcd root@uvb:~/ immlist stringRdnCfg=abcd Name Type Value(s) testNameCfgSA_NAME_T123 (3) stringRdnCfg SA_STRING_T stringRdnCfg=abcd SaImmAttrImplementerName SA_STRING_T Empty SaImmAttrClassName SA_STRING_T OsafNtfCmTestCFG SaImmAttrAdminOwnerNameSA_STRING_T Empty root@uvb:~/ immcfg -a testNameCfg= stringRdnCfg=abcd Aborted (core dumped) --- The longdn_class.xml as below: imm:IMM-contents xsi:noNamespaceSchemaLocation=SAI-AIS-IMM-XSD-A.01.01.xsd class name=OsafNtfCmTestCFG categorySA_CONFIG/category rdn namestringRdnCfg/name typeSA_STRING_T/type categorySA_CONFIG/category flagSA_INITIALIZED/flag flagSA_NOTIFY/flag /rdn attr nametestNameCfg/name typeSA_NAME_T/type categorySA_CONFIG/category flagSA_MULTI_VALUE/flag flagSA_NOTIFY/flag flagSA_WRITABLE/flag /attr /class /imm:IMM-contents the backtrace as below: Core was generated by `immcfg -a testNameCfg=1'. Program terminated with signal SIGABRT, Aborted. \#0 0x415d5f79 in raise () from /lib64/libc.so.6 (gdb) bt \#0 0x415d5f79 in raise () from /lib64/libc.so.6 \#1 0x415d9388 in abort () from /lib64/libc.so.6 \#2 0x409c5cbe in __osafassert_fail (__file=__file@entry=0x409f9cd1 osaf_extended_name.c, __line=__line@entry=130, __func=__func@entry=0x409f9d60 __FUNCTION__.3257 osaf_extended_name_length, __assertion=__assertion@entry=0x409f9d10 osaf_extended_names_enabled length = SA_MAX_UNEXTENDED_NAME_LENGTH) at sysf_def.c:281 \#3 0x409c3936 in osaf_extended_name_length (name=name@entry=0x62dc60) at osaf_extended_name.c:129 \#4 0x40c322fd in imma_copyAttrValue (p=0x62d870, attrValueType=SA_IMM_ATTR_SANAMET, attrValue=0x62dc60) at imma_init.c:421 \#5 0x40c24e77 in saImmOmCcbObjectModify_2 (ccbHandle=ccbHandle@entry=1406852104797087000, objectName=objectName@entry=0x61b240, attrMods=attrMods@entry=0x62dc40) at imma_om_api.c:2349 \#6 0x00412ddc in immutil_saImmOmCcbObjectModify_2 (immCcbHandle=1406852104797087000, objectName=0x61b240, attrMods=attrMods@entry=0x62dc40) at immutil.c:1540 \#7 0x0040d2ee in object_modify (objectNames=objectNames@entry=0x61b220, optargs=optargs@entry=0x61b010, optargs_len=optargs_len@entry=1) at imm_cfg.c:589 \#8 0x0040e894 in imm_operation (argc=4, argv=optimised out) at imm_cfg.c:1439 \#9 0x415c0ec5 in __libc_start_main () from /lib64/libc.so.6 \#10 0x0040378e in _start () (gdb) f 2 \#2 0x409c5cbe in __osafassert_fail (__file=__file@entry=0x409f9cd1 osaf_extended_name.c, __line=__line@entry=130, __func=__func@entry=0x409f9d60 __FUNCTION__.3257 osaf_extended_name_length, __assertion=__assertion@entry=0x409f9d10 osaf_extended_names_enabled length = SA_MAX_UNEXTENDED_NAME_LENGTH) at sysf_def.c:281 281 abort(); (gdb) p osaf_extended_names_enabled $1 = false (gdb) --- 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
[tickets] [opensaf:tickets] #1038 immtools: imm tools should support long DN by default
--- ** [tickets:#1038] immtools: imm tools should support long DN by default** **Status:** accepted **Milestone:** 4.5.0 **Created:** Wed Sep 03, 2014 08:40 AM UTC by Zoran Milinkovic **Last Updated:** Wed Sep 03, 2014 08:40 AM UTC **Owner:** Zoran Milinkovic All imm tools should support long DN by default. --- 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.-- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1038 immtools: imm tools should support long DN
- **summary**: immtools: imm tools should support long DN by default -- immtools: imm tools should support long DN - Description has changed: Diff: --- old +++ new @@ -1 +1,2 @@ -All imm tools should support long DN by default. +All imm tools should support long DN. +Disabling long DN support will not be possible. - **status**: accepted -- review - **Comment**: https://sourceforge.net/p/opensaf/mailman/message/32791835/ --- ** [tickets:#1038] immtools: imm tools should support long DN** **Status:** review **Milestone:** 4.5.0 **Created:** Wed Sep 03, 2014 08:40 AM UTC by Zoran Milinkovic **Last Updated:** Wed Sep 03, 2014 08:40 AM UTC **Owner:** Zoran Milinkovic All imm tools should support long DN. Disabling long DN support will not be possible. --- 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.-- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #974 IMM: Loading of xml or PBE will fail with objects having longdns
- **status**: review -- fixed - **Comment**: opensaf-4.5.x: changeset: 5711:abd2e0576ccc branch: opensaf-4.5.x parent: 5709:ea15bcddfabd user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Wed Sep 03 16:13:55 2014 +0200 summary: imm: fix loading long DNs from imm.xml and PBE [#974] - default(4.6): changeset: 5712:5a6ab7a375aa tag: tip parent: 5710:487531132423 user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Wed Sep 03 16:13:55 2014 +0200 summary: imm: fix loading long DNs from imm.xml and PBE [#974] --- ** [tickets:#974] IMM: Loading of xml or PBE will fail with objects having longdns** **Status:** fixed **Milestone:** 4.5.0 **Created:** Fri Aug 01, 2014 11:33 AM UTC by Neelakanta Reddy **Last Updated:** Tue Aug 26, 2014 02:16 PM UTC **Owner:** Zoran Milinkovic Description: 1. Create the longdn objects with dn Lexicographic ahead of dn opensafImm=opensafImm,safApp=safImmService 2. take the dump with immdump or load from PBE. 3. restart the cluster and try to load with the xml generated by immdump or imm.db 4. loading fails with following error: syslog: Aug 1 16:51:43 Slot-3 osafimmloadd: NO Load starting Aug 1 16:51:43 Slot-3 osafimmloadd: NO IMMSV_PBE_FILE is defined (imm.db) check it for existence and SaImmRepositoryInitModeT Aug 1 16:51:43 Slot-3 osafimmloadd: IN File '/etc/opensaf/imm.db' is not accessible for read/write, cause:No such file or directory Aug 1 16:51:43 Slot-3 osafimmloadd: WA Could not open repository:imm.db Aug 1 16:51:43 Slot-3 osafimmloadd: NO * Loading from XML file imm.xml at /etc/opensaf * Aug 1 16:51:43 Slot-3 osafimmloadd: ER Failed to create object err: 13, class: testClass6, dn: 'tEstAttr=0'. Check for duplicate attributes, or trace osafimmloadd Aug 1 16:51:43 Slot-3 osafimmloadd: NO Failed to create object - exiting Aug 1 16:51:43 Slot-3 osafimmnd[5640]: WA Hard close of admin owner IMMLOADER id(1)= Loading must have failed Aug 1 16:51:43 Slot-3 osafimmnd[5640]: ER LOADING APPARENTLY FAILED status:1 Aug 1 16:51:43 Slot-3 osafimmd[5625]: ER LOADING FAILED. File(s) possibly missing, inaccessible or corrupt .. ? * Aug 1 16:51:43 Slot-3 opensafd[5564]: ER Failed DESC:IMMND IMMND traces: Aug 1 16:51:43.313401 osafimmnd [5640:immnd_evt.c:5605] immnd_evt_proc_object_create Aug 1 16:51:43.313409 osafimmnd [5640:ImmModel.cc:6423] ccbObjectCreate Aug 1 16:51:43.313415 osafimmnd [5640:ImmModel.cc:6436] T2 parentName: Aug 1 16:51:43.313423 osafimmnd [5640:ImmModel.cc:2563] getLongDnsAllowed Aug 1 16:51:43.313428 osafimmnd [5640:ImmModel.cc:2574] getLongDnsAllowed Aug 1 16:51:43.313453 osafimmnd [5640:ImmModel.cc:6758] T7 ERR_NAME_TOO_LONG: DN is too long, size:786, max size is:2048 Aug 1 16:51:43.313461 osafimmnd [5640:ImmModel.cc:7376] ccbObjectCreate Aug 1 16:51:43.313467 osafimmnd [5640:immnd_evt.c:5774] T2 send immediate reply to client/agent The loading failed because longDnsPermitted is false(getLongDnsAllowed () will return false). The possible solution may be delay the loading of objects until IMM object opensafImm=opensafImm,safApp=safImmService is created or if longdns are present delay the longdn objects until opensafImm=opensafImm,safApp=safImmService is created. --- 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.-- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1008 IMM: Changes to access control attribute should be local validated
- **status**: accepted -- review - **Comment**: https://sourceforge.net/p/opensaf/mailman/message/32811953/ --- ** [tickets:#1008] IMM: Changes to access control attribute should be local validated** **Status:** review **Milestone:** 4.5.0 **Created:** Fri Aug 22, 2014 01:52 PM UTC by Anders Bjornerstedt **Last Updated:** Fri Sep 05, 2014 07:43 AM UTC **Owner:** Zoran Milinkovic Validation logic should be added to ImmModel::ccbObjectmodify checking that updates to the 'accessControlMode' attribute in the OpensAF service object are in the value range of the enum defined for it. Local validation (meaning local to the modify operation) can be done here because there is no inter-object relation from this attribute with any other imm object (currently) in the imm model. Create operations are not an issue because the immsv already rejects creates of instances of either class 'OpensafImm' or 'SaImmMngt'. --- 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.-- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce. Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1038 immtools: imm tools should support long DN
- **status**: review -- fixed - **Comment**: opensaf-4.5.x: changeset: 5754:9ca969e74de9 branch: opensaf-4.5.x parent: 5751:e76a6a91e564 user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Wed Sep 03 15:21:21 2014 +0200 summary: immtools: support long DN in imm tools [#1038] - default(4.6): changeset: 5755:a1fbfb8ca093 tag: tip parent: 5753:a070c5206574 user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Wed Sep 03 15:21:21 2014 +0200 summary: immtools: support long DN in imm tools [#1038] --- ** [tickets:#1038] immtools: imm tools should support long DN** **Status:** fixed **Milestone:** 4.5.0 **Created:** Wed Sep 03, 2014 08:40 AM UTC by Zoran Milinkovic **Last Updated:** Wed Sep 03, 2014 01:34 PM UTC **Owner:** Zoran Milinkovic All imm tools should support long DN. Disabling long DN support will not be possible. --- 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.-- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce. Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #643 IMM: API that replaces SaNameT with SaStringT and SA_IMM_ATTR_DN
- **status**: assigned -- accepted --- ** [tickets:#643] IMM: API that replaces SaNameT with SaStringT and SA_IMM_ATTR_DN** **Status:** accepted **Milestone:** 4.6.FC **Created:** Thu Nov 28, 2013 05:00 PM UTC by Anders Bjornerstedt **Last Updated:** Mon Sep 01, 2014 10:44 AM UTC **Owner:** Zoran Milinkovic The IMM service should provide an updated API where all use of the troublesome SaNameT type is replaced by the SaStringT type or the SaConstStringT type #625. Also needed is a new flag value for attribute definitions: SA_IMM_ATTR_DN. Defining an attribute in an IMM class definition on the SaStringT type and also setting the flag SA_IMM_ATTR_DN, will mean that the attribute is intended to hold a value that should be a DN. Other flags that make sense to also set on such an attribute definition where applicable are: SA_IMM_ATTR_RDN if this is the RDN attribute. Just as having SaNameT the type of an RDN attribute indicates that the class is an association class, having SaStringT and SA_IMM_ATTR_DN combined with SA_IMM_ATTR_RDN would also indicate that this is an association class. SA_IMM_ATTR_NO_DANGLING. Currently (OpenSAF 4.4) will only be allowed on attributes of type SaNameT, but will of course be allowed also on attributes of type SaStringT if the SA_IMM_ATTR_DN flag is also set. All the other flags may also be used in combination with SA_IMM_ATTR_DN, with the normal meaning. --- 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.-- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce. Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1061 imm: memory leak in dumping resources in PBE
--- ** [tickets:#1061] imm: memory leak in dumping resources in PBE** **Status:** unassigned **Milestone:** 4.5.0 **Created:** Wed Sep 10, 2014 12:35 PM UTC by Zoran Milinkovic **Last Updated:** Wed Sep 10, 2014 12:35 PM UTC **Owner:** Zoran Milinkovic In dumping resources (in PBE), data are collected, sent as a result, but allocated memory (rparams) is not freed. p SaImmAdminOperationParamsT_2 ** rparams;br/ rparams = (SaImmAdminOperationParamsT_2 **) realloc(NULL, sizeof(SaImmAdminOperationParamsT_2 *)); /p --- 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.-- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1062 imm: immnd may crash in resourceDisplay
--- ** [tickets:#1062] imm: immnd may crash in resourceDisplay** **Status:** unassigned **Milestone:** 4.5.0 **Created:** Wed Sep 10, 2014 02:10 PM UTC by Zoran Milinkovic **Last Updated:** Wed Sep 10, 2014 02:10 PM UTC **Owner:** Zoran Milinkovic immnd may crash in immModel_resourceDisplay and ImmModel::resourceDisplay if operation name is not provided. In this case, opName is NULL, and strcmp() functions may crash. --- 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.-- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1068 longdn : immnd crashed on all nodes leading to cluster reset
- **status**: unassigned -- accepted - **assigned_to**: Zoran Milinkovic --- ** [tickets:#1068] longdn : immnd crashed on all nodes leading to cluster reset** **Status:** accepted **Milestone:** 4.3.3 **Created:** Fri Sep 12, 2014 11:49 AM UTC by surender khetavath **Last Updated:** Fri Sep 12, 2014 12:25 PM UTC **Owner:** Zoran Milinkovic changeset : 5697 Test: OmInit() AdminOwnerInit() AdminOwnerSet on opensafImm=opensafImm,safApp=safImmService subtree level Create a Class Create 2 objects Obj1,Obj2 under the above object FinalizeOmHandles OiInit(),OiImplSet,ClassImplSet for above class In a thread wait for Dispatch events Initialize om handles Now creation of 3rd object is rejected by OI While aborting the CCB immnd crashed on all nodes #0 0x0a424ac2 in ?? () (gdb) bt #0 0x0a424ac2 in ?? () #1 0x0013 in ?? () #2 0x006c3580 in ?? () #3 0x006c3580 in ?? () #4 0x00407cc8 in immnd_evt_proc_ccb_finalize.isra.28 () at immnd_evt.c:7189 #5 0x004150ec in immnd_evt_proc_fevs_dispatch () at immnd_evt.c:7756 #6 0x0041853d in immnd_process_evt () at immnd_evt.c:8549 #7 0x0040b83b in main () at immnd_main.c:343 (gdb) dir /home/staging/osaf/services/saf/immsv/immnd/ Source directories searched: /home/staging/osaf/services/saf/immsv/immnd:$cdir:$cwd (gdb) fr 4 #4 0x00407cc8 in immnd_evt_proc_ccb_finalize.isra.28 () at immnd_evt.c:7189 7189err = immModel_ccbFinalize(cb, evt-info.ccbId); (gdb) Traces from osafimmnd Sep 12 16:32:43.113291 osafimmnd [15525:immnd_evt.c:3543] immnd_evt_proc_ccb_obj_create_rsp Sep 12 16:32:43.113304 osafimmnd [15525:ImmModel.cc:9461] ccbObjCreateContinuation Sep 12 16:32:43.113341 osafimmnd [15525:ImmModel.cc:9517] NO ImmModel::ccbObjCreateContinuation: implementer returned error, Ccb aborted with error: 20 Sep 12 16:32:43.113355 osafimmnd [15525:ImmModel.cc:9538] ccbObjCreateContinuation --- 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.-- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1008 IMM: Changes to access control attribute should be local validated
- **status**: review -- fixed - **Comment**: opensaf-4.5.x : changeset: 5782:8b7f5de7bd3a branch: opensaf-4.5.x parent: 5780:9ac53ee22ac2 user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Tue Sep 09 13:30:56 2014 +0200 summary: imm: add a validation for accessControlMode [#1008] -- default(4.6) : changeset: 5783:6799e094d3b2 tag: tip parent: 5779:6c62a01ef630 user:Zoran Milinkovic zoran.milinko...@ericsson.com date:Tue Sep 09 13:30:56 2014 +0200 summary: imm: add a validation for accessControlMode [#1008] --- ** [tickets:#1008] IMM: Changes to access control attribute should be local validated** **Status:** fixed **Milestone:** 4.5.0 **Created:** Fri Aug 22, 2014 01:52 PM UTC by Anders Bjornerstedt **Last Updated:** Tue Sep 09, 2014 01:50 PM UTC **Owner:** Zoran Milinkovic Validation logic should be added to ImmModel::ccbObjectmodify checking that updates to the 'accessControlMode' attribute in the OpensAF service object are in the value range of the enum defined for it. Local validation (meaning local to the modify operation) can be done here because there is no inter-object relation from this attribute with any other imm object (currently) in the imm model. Create operations are not an issue because the immsv already rejects creates of instances of either class 'OpensafImm' or 'SaImmMngt'. --- 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.-- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1083 imm: runtime attributes are trimmed away for PBE
---
** [tickets:#1083] imm: runtime attributes are trimmed away for PBE**
**Status:** unassigned
**Milestone:** 4.3.3
**Created:** Mon Sep 15, 2014 01:29 PM UTC by Zoran Milinkovic
**Last Updated:** Mon Sep 15, 2014 01:29 PM UTC
**Owner:** nobody
Runtime attributes are trimmed away for PBE.
The problem is in the calculation in IF statement, which is always true if
attr-flags contains SA_IMM_ATTR_RUNTIME flag.
if((attr-mFlags SA_IMM_ATTR_RUNTIME)
~(attr-mFlags SA_IMM_ATTR_PERSISTENT)
~(attr-mFlags SA_IMM_ATTR_NOTIFY)) {
Sign ~ should be replaced with !.
---
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.--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1084 imm: wrong trace log in setImplementer
--- ** [tickets:#1084] imm: wrong trace log in setImplementer** **Status:** unassigned **Milestone:** 4.3.3 **Created:** Mon Sep 15, 2014 01:41 PM UTC by Zoran Milinkovic **Last Updated:** Mon Sep 15, 2014 01:41 PM UTC **Owner:** nobody In ImmModel::setImplementer for regular OI, a wrong trace is logged if class implementer has already been set to the object. TRACE_7(ERR_EXIST: Object '%s' already has class implementer %s conflicts with setting object implementer, objectName.c_str(), obj-mImplementer-mImplementerName.c_str()); This code may crash immnd if obj-mImplementer is NULL. --- 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.-- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
