[tickets] [opensaf:tickets] #2331 CLM: : saClmNodeCurrAddress and saClmNodeCurrAddressFamily are not exposed to IMM even that TPC mode is using
- **status**: unassigned --> accepted - **assigned_to**: Praveen - **Milestone**: future --> 5.17.08 --- ** [tickets:#2331] CLM: : saClmNodeCurrAddress and saClmNodeCurrAddressFamily are not exposed to IMM even that TPC mode is using** **Status:** accepted **Milestone:** 5.17.08 **Created:** Thu Mar 02, 2017 10:10 AM UTC by Tai Dinh **Last Updated:** Thu Mar 23, 2017 07:11 AM UTC **Owner:** Praveen saClmNodeCurrAddress and saClmNodeCurrAddressFamily of cluster node is not exposed to IMM even that TCP mode is configured. This kind of information is sometimes needed by application. --- 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.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2421 amfd: is_swbdl_delete_ok_for_node should also check for SG and Node admin state
- **status**: unassigned --> assigned - **assigned_to**: Praveen - **Milestone**: 5.17.08 --> 5.17.06 --- ** [tickets:#2421] amfd: is_swbdl_delete_ok_for_node should also check for SG and Node admin state** **Status:** assigned **Milestone:** 5.17.06 **Created:** Tue Apr 11, 2017 09:33 AM UTC by Tai Dinh **Last Updated:** Tue Apr 11, 2017 09:33 AM UTC **Owner:** Praveen During deleting of NodeSwBundle object, AMF only check if the SUs admin state is at LOCKED_INSTANTIATION or not. Which means that the deletion of that object is not allowed even in the case where the SG or Node is at LOCKED_INSTANTIATION state, which implicitetly means that the SU is UNINSTANTIATED. This currently blocks the SMF campagin to be rolled back in some situation. The SU's node admin state and SU's SG admin state should also be checked and the deletetion should be allowed if one of above state is LOCKED_INSTANTIATION. /Tai --- 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.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2434 log: lgs doesn't checkpoint dest_names in open stream request
--- ** [tickets:#2434] log: lgs doesn't checkpoint dest_names in open stream request** **Status:** unassigned **Milestone:** 5.17.08 **Created:** Wed Apr 19, 2017 01:25 PM UTC by Canh Truong **Last Updated:** Wed Apr 19, 2017 01:25 PM UTC **Owner:** nobody In case failover when one node is rebooted then back again, stb_dest_names has not been checkpointed to standby (this node) if the log agent send request open the stream again before cold sync is completed. --- 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.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2149 log: refactor handling IMM in log service
- **status**: accepted --> review --- ** [tickets:#2149] log: refactor handling IMM in log service ** **Status:** review **Milestone:** 5.17.08 **Created:** Fri Oct 28, 2016 12:25 PM UTC by elunlen **Last Updated:** Thu Apr 13, 2017 06:55 AM UTC **Owner:** Vu Minh Nguyen This ticket intends to do refactor stuffs related to IMM handling in log service. More details will come later. With first look, we see many places using IMM APIs, and refering to IMM OI handler. It would be very good if we could move this into one or several files that are purely dedicated to IMM handling, with a well-defined API. --- 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.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2432 dtm: Node reboot because transportd reads invalid pid of dtmd
- Description has changed: Diff: --- old +++ new @@ -1,4 +1,4 @@ -There's an expected node reboot during Opensaf node startup +There's an unexpected node reboot during Opensaf node startup 2017-01-24 18:19:53 SC-1 opensafd: Starting OpenSAF Services(5.2.M0 - 8532:b6df9e2a2b8b:default) (Using TCP) 2017-01-24 18:19:53 SC-1 osaftransportd[398]: Started --- ** [tickets:#2432] dtm: Node reboot because transportd reads invalid pid of dtmd** **Status:** accepted **Milestone:** 5.17.06 **Created:** Wed Apr 19, 2017 12:02 AM UTC by Minh Hon Chau **Last Updated:** Wed Apr 19, 2017 12:08 AM UTC **Owner:** Minh Hon Chau There's an unexpected node reboot during Opensaf node startup 2017-01-24 18:19:53 SC-1 opensafd: Starting OpenSAF Services(5.2.M0 - 8532:b6df9e2a2b8b:default) (Using TCP) 2017-01-24 18:19:53 SC-1 osaftransportd[398]: Started 2017-01-24 18:19:53 SC-1 osafdtmd[393]: mkfifo already exists: /var/lib/opensaf/osafdtmd.fifo File exists 2017-01-24 18:19:53 SC-1 osaftransportd[398]: Rebooting OpenSAF NodeId = 0 EE Name = No EE Mapped, Reason: osafdtmd failed to start, OwnNodeId = 0, SupervisionTime = 60 2017-01-24 18:19:53 SC-1 osafdtmd[393]: Started Another attempt to reproduce this problem by adding more debug log: 2017-04-18 18:01:14 SC-1 opensafd: Starting OpenSAF Services(5.2.0 - 0:) (Using TCP) 2017-04-18 18:01:14 SC-1 osaftransportd[380]: fifo_file /var/lib/opensaf/osaftransportd.fifo 2017-04-18 18:01:14 SC-1 osaftransportd[380]: mkfifo already exists: /var/lib/opensaf/osaftransportd.fifo File exists 2017-04-18 18:01:14 SC-1 osafdtmd[386]: fifo_file /var/lib/opensaf/osafdtmd.fifo 2017-04-18 18:01:14 SC-1 osafdtmd[386]: mkfifo already exists: /var/lib/opensaf/osafdtmd.fifo File exists 2017-04-18 18:01:15 SC-1 osaftransportd[380]: __pidfile /var/run/opensaf/osaftransportd.pid 2017-04-18 18:01:15 SC-1 osaftransportd[380]: Started 2017-04-18 18:01:15 SC-1 osaftransportd[380]: WA file_path_:/var/run/opensaf, file_name_:osafdtmd.pid 2017-04-18 18:01:15 SC-1 osafdtmd[386]: __pidfile /var/run/opensaf/osafdtmd.pid 2017-04-18 18:01:15 SC-1 osaftransportd[380]: WA file name: osafdtmd.pid created 2017-04-18 18:01:15 SC-1 osaftransportd[380]: WA rdstate 6, pid: 4294967295 2017-04-18 18:01:15 SC-1 osaftransportd[380]: Rebooting OpenSAF NodeId = 0 EE Name = No EE Mapped, Reason: osafdtmd failed to start, OwnNodeId = 0, SupervisionTime = 60 2017-04-18 18:01:15 SC-1 osafdtmd[386]: Started It could be because osaftransportd fails to read pid in osafdmtd.pid --- 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.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2433 imm: Add more details to no dangling CcbErrorString
--- ** [tickets:#2433] imm: Add more details to no dangling CcbErrorString** **Status:** accepted **Milestone:** 5.17.08 **Created:** Wed Apr 19, 2017 06:29 AM UTC by Hung Nguyen **Last Updated:** Wed Apr 19, 2017 06:29 AM UTC **Owner:** Hung Nguyen ~~~ root@SC-1:~# immcfg -d test=1 error - saImmOmCcbApply FAILED: SA_AIS_ERR_FAILED_OPERATION (21) OI reports: IMM: Validation abort: No dangling validation failed ~~~ Add more details about the object name to CcbErrorString to provide more information for users. --- 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.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
