[tickets] [opensaf:tickets] #1389 AMF: Node state is not correct after unlock-in nodegroup
I guess, version is 'reported version' on which tests were performed and bug was found. --- ** [tickets:#1389] AMF: Node state is not correct after unlock-in nodegroup** **Status:** fixed **Milestone:** 4.6.1 **Created:** Tue Jun 16, 2015 09:24 AM UTC by Quyen Dao **Last Updated:** Wed Jul 15, 2015 10:53 AM UTC **Owner:** Praveen Steps to reproduce -- * Start UML cluster * Create a node group containing PL-3 and PL-4 with admin state as LOCKED-INSTANTIATION * Admin lock then lock-in PL-4 - admin state of PL4 is LOCKED-INSTANTIATION, PL3 is UNLOCKED * Admin unlock-in node group Observed behaviour -- - Admin states of PL-3 and PL-4 are LOCKED Expected behaviour -- - Admin state of PL-4 is LOCKED and PL-3 remains UNLOCKED. --- 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.-- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1389 AMF: Node state is not correct after unlock-in nodegroup
- **Comment**: The version setting does not make sense for this defect ticket. Version must be set to the oldest version where it is known that the defect exists. This defect was fixed on 4.6 branch and default, which suggests that the defect was introduced on the 4.6 branch. Is this correct ? If the defect was introduced earlier, or has always been present, then it should be fixed also on the 4.5 branch. --- ** [tickets:#1389] AMF: Node state is not correct after unlock-in nodegroup** **Status:** fixed **Milestone:** 4.6.1 **Created:** Tue Jun 16, 2015 09:24 AM UTC by Quyen Dao **Last Updated:** Tue Jul 14, 2015 01:52 PM UTC **Owner:** Praveen Steps to reproduce -- * Start UML cluster * Create a node group containing PL-3 and PL-4 with admin state as LOCKED-INSTANTIATION * Admin lock then lock-in PL-4 - admin state of PL4 is LOCKED-INSTANTIATION, PL3 is UNLOCKED * Admin unlock-in node group Observed behaviour -- - Admin states of PL-3 and PL-4 are LOCKED Expected behaviour -- - Admin state of PL-4 is LOCKED and PL-3 remains UNLOCKED. --- 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.-- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1389 AMF: Node state is not correct after unlock-in nodegroup
- **Version**: 4.7-Tentative -- 4.6 --- ** [tickets:#1389] AMF: Node state is not correct after unlock-in nodegroup** **Status:** fixed **Milestone:** 4.6.1 **Created:** Tue Jun 16, 2015 09:24 AM UTC by Quyen Dao **Last Updated:** Wed Jul 15, 2015 11:01 AM UTC **Owner:** Praveen Steps to reproduce -- * Start UML cluster * Create a node group containing PL-3 and PL-4 with admin state as LOCKED-INSTANTIATION * Admin lock then lock-in PL-4 - admin state of PL4 is LOCKED-INSTANTIATION, PL3 is UNLOCKED * Admin unlock-in node group Observed behaviour -- - Admin states of PL-3 and PL-4 are LOCKED Expected behaviour -- - Admin state of PL-4 is LOCKED and PL-3 remains UNLOCKED. --- 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.-- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1389 AMF: Node state is not correct after unlock-in nodegroup
- **status**: review -- fixed - **Comment**: changeset: 6670:0b11c5a96a94 branch: opensaf-4.6.x parent: 6668:3950242b02b0 user:praveen.malv...@oracle.com date:Tue Jul 14 19:17:53 2015 +0530 summary: amfd: ignore unlocked node during unlock-in op on ng [#1389] changeset: 6671:682b61512159 parent: 6669:08f308d682ca user:praveen.malv...@oracle.com date:Tue Jul 14 19:18:44 2015 +0530 summary: amfd: ignore unlocked node during unlock-in op on ng [#1389] changeset: 6672:67e6c858561e branch: opensaf-4.6.x parent: 6670:0b11c5a96a94 user:Gary Lee gary@dektech.com.au date:Tue Jul 14 19:19:29 2015 +0530 summary: amfd: ignore invalid operations on nodegroup [#1389] changeset: 6673:9682ea6b4dd9 tag: tip parent: 6671:682b61512159 user:Gary Lee gary@dektech.com.au date:Tue Jul 14 19:19:39 2015 +0530 summary: amfd: ignore invalid operations on nodegroup [#1389] --- ** [tickets:#1389] AMF: Node state is not correct after unlock-in nodegroup** **Status:** fixed **Milestone:** 4.6.1 **Created:** Tue Jun 16, 2015 09:24 AM UTC by Quyen Dao **Last Updated:** Wed Jun 24, 2015 05:24 AM UTC **Owner:** Praveen Steps to reproduce -- * Start UML cluster * Create a node group containing PL-3 and PL-4 with admin state as LOCKED-INSTANTIATION * Admin lock then lock-in PL-4 - admin state of PL4 is LOCKED-INSTANTIATION, PL3 is UNLOCKED * Admin unlock-in node group Observed behaviour -- - Admin states of PL-3 and PL-4 are LOCKED Expected behaviour -- - Admin state of PL-4 is LOCKED and PL-3 remains UNLOCKED. --- 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.-- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1389 AMF: Node state is not correct after unlock-in nodegroup
- **status**: accepted -- review --- ** [tickets:#1389] AMF: Node state is not correct after unlock-in nodegroup** **Status:** review **Milestone:** 4.6.1 **Created:** Tue Jun 16, 2015 09:24 AM UTC by Quyen Dao **Last Updated:** Wed Jun 17, 2015 04:39 AM UTC **Owner:** Praveen Steps to reproduce -- * Start UML cluster * Create a node group containing PL-3 and PL-4 with admin state as LOCKED-INSTANTIATION * Admin lock then lock-in PL-4 - admin state of PL4 is LOCKED-INSTANTIATION, PL3 is UNLOCKED * Admin unlock-in node group Observed behaviour -- - Admin states of PL-3 and PL-4 are LOCKED Expected behaviour -- - Admin state of PL-4 is LOCKED and PL-3 remains UNLOCKED. --- 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.-- Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical virtual servers, alerts via email sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1389 AMF: Node state is not correct after unlock-in nodegroup
- **status**: unassigned -- accepted - **assigned_to**: Praveen - **Milestone**: future -- 4.6.1 --- ** [tickets:#1389] AMF: Node state is not correct after unlock-in nodegroup** **Status:** accepted **Milestone:** 4.6.1 **Created:** Tue Jun 16, 2015 09:24 AM UTC by Quyen Dao **Last Updated:** Tue Jun 16, 2015 09:24 AM UTC **Owner:** Praveen Steps to reproduce -- * Start UML cluster * Create a node group containing PL-3 and PL-4 with admin state as LOCKED-INSTANTIATION * Admin lock then lock-in PL-4 - admin state of PL4 is LOCKED-INSTANTIATION, PL3 is UNLOCKED * Admin unlock-in node group Observed behaviour -- - Admin states of PL-3 and PL-4 are LOCKED Expected behaviour -- - Admin state of PL-4 is LOCKED and PL-3 remains UNLOCKED. --- 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] #1389 AMF: Node state is not correct after unlock-in nodegroup
--- ** [tickets:#1389] AMF: Node state is not correct after unlock-in nodegroup** **Status:** unassigned **Milestone:** future **Created:** Tue Jun 16, 2015 09:24 AM UTC by Quyen Dao **Last Updated:** Tue Jun 16, 2015 09:24 AM UTC **Owner:** nobody Steps to reproduce -- * Start UML cluster * Create a node group containing PL-3 and PL-4 with admin state as LOCKED-INSTANTIATION * Admin lock then lock-in PL-4 - admin state of PL4 is LOCKED-INSTANTIATION, PL3 is UNLOCKED * Admin unlock-in node group Observed behaviour -- - Admin states of PL-3 and PL-4 are LOCKED Expected behaviour -- - Admin state of PL-4 is LOCKED and PL-3 remains UNLOCKED. --- 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
