[tickets] [opensaf:tickets] #1725 AMF: Recover transient SUSIs left over from headless
Please find the Configuration file and traces attached for TC #4. Configuration: SC-1 and 3 payloads PL-3, PL-4, PL-5 hosting SU1, SU2 and SU3 resp. 2N Red model. Steps: 1. Start all nodes, SU1 has Act and SU2 has Standby and SU3 is spare. 2. Lock SI and keep gdb in quisced callback of SU1 component and stop SC-1. After SC-1 is down i.e. headless situation, then kill component of SU1. SU failover happens. 3. Now, Start SC-1 and then unlock SI. --- ** [tickets:#1725] AMF: Recover transient SUSIs left over from headless** **Status:** fixed **Milestone:** 5.1.FC **Created:** Wed Apr 06, 2016 07:16 AM UTC by Minh Hon Chau **Last Updated:** Tue Oct 25, 2016 12:05 AM UTC **Owner:** nobody This ticket is more likely an enhancement that targets on how AMFD detect and recover the transients SUSI left over from headless. There are three major situations: (1) - Cluster goes headless, su/node failover on any payloads can happen, or any payloads can be hard rebooted/powered off by operator, then cluster recover (2) - issue admin op on any AMF entities, cluster goes headless. During headless, the middle HA assignments of whole admin op sequence between AMFND and components could be: (2.1) The assignment completes, component returns OK with csi callback, then cluster recover (2.2) The assignment is under going, then cluster recover. The assignment afterward could complete, or csi callback returns FAILED_OPERATION or error can also happen At the time cluster recover, amfd has collected all assignments from all amfnd(s). These assignments can be in assigned or assigning states whilst its HA states do not conform its SG redundancy. Any of (1) (2.1) (2.2) can happen in a combination, which means while issuing admin op (2), cluster go headless and any kinds of failover (1) can happen during headless. --- 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.-- The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1725 AMF: Recover transient SUSIs left over from headless
TC-4 Attachments: - [TC-4.rar](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/7b203666/a760/attachment/TC-4.rar) (353.9 kB; application/octet-stream) --- ** [tickets:#1725] AMF: Recover transient SUSIs left over from headless** **Status:** fixed **Milestone:** 5.1.FC **Created:** Wed Apr 06, 2016 07:16 AM UTC by Minh Hon Chau **Last Updated:** Mon Oct 31, 2016 09:10 AM UTC **Owner:** nobody This ticket is more likely an enhancement that targets on how AMFD detect and recover the transients SUSI left over from headless. There are three major situations: (1) - Cluster goes headless, su/node failover on any payloads can happen, or any payloads can be hard rebooted/powered off by operator, then cluster recover (2) - issue admin op on any AMF entities, cluster goes headless. During headless, the middle HA assignments of whole admin op sequence between AMFND and components could be: (2.1) The assignment completes, component returns OK with csi callback, then cluster recover (2.2) The assignment is under going, then cluster recover. The assignment afterward could complete, or csi callback returns FAILED_OPERATION or error can also happen At the time cluster recover, amfd has collected all assignments from all amfnd(s). These assignments can be in assigned or assigning states whilst its HA states do not conform its SG redundancy. Any of (1) (2.1) (2.2) can happen in a combination, which means while issuing admin op (2), cluster go headless and any kinds of failover (1) can happen during headless. --- 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.-- The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2151 osaf: system in not in correct state during Act controller comming up
--- ** [tickets:#2151] osaf: system in not in correct state during Act controller comming up** **Status:** unassigned **Milestone:** 5.2.FC **Created:** Mon Oct 31, 2016 10:54 AM UTC by Nagendra Kumar **Last Updated:** Mon Oct 31, 2016 10:54 AM UTC **Owner:** nobody Steps to reproduce: 1. Start two controllers(SC-1 Act, SC-2 Standby) and two paylods. Configure 50 components on SC-2 and unlock them. Keep 1 sec delay in each component stop script. 2. Stop SC-1 and after that, stop SC-2. 3. During SC-2 is going down, start SC-1. Observed behaviour: Since components are taking time in stopping all components during 'opensad stop' of SC-2, Amfnd hasn't exited. But, all middleware components assignments are stopped. Only Amfnd and Amfd is alive with few more components to stop. But SC-1 has come up till Amfd and since two Amfd is Act now, so SC-2 Amfd exits by saying "Duplicate ACTIVE detected, exiting". Till this time, services states including Amfd is in bad state as they couldn't differentiate whether it is headless state or cluster comming up. This is true also as the system is in half middle of headless and cluster coming up. Expected behaviour In my view: FMS should stop and shouldn't proceed if peer is going down. i.e. FMS should figure out on SC-1 that the peer system is going down. And should allow SC-1 only if all services are down i.e. it gets node down (may be cb->immd_down && cb->immnd_down && cb->amfnd_down && cb->amfd_down && cb->fm_down). --- 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.-- The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2151 osaf: system in not in correct state during Act controller comming up
- Description has changed: Diff: --- old +++ new @@ -6,7 +6,7 @@ Observed behaviour: Since components are taking time in stopping all components during 'opensad stop' of SC-2, Amfnd hasn't exited. But, all middleware components assignments are stopped. Only Amfnd and Amfd is alive with few more components to stop. But SC-1 has come up till Amfd and since two Amfd is Act now, so SC-2 Amfd exits by saying "Duplicate ACTIVE detected, exiting". -Till this time, services states including Amfd is in bad state as they couldn't differentiate whether it is headless state or cluster comming up. This is true also as the system is in half middle of headless and cluster coming up. +Till this time, services states including Amfd is in bad state as they couldn't differentiate whether it is headless state or failover. This is true also as the system is in half middle of headless and failover. Expected behaviour --- ** [tickets:#2151] osaf: system in not in correct state during Act controller comming up** **Status:** unassigned **Milestone:** 5.2.FC **Created:** Mon Oct 31, 2016 10:54 AM UTC by Nagendra Kumar **Last Updated:** Mon Oct 31, 2016 10:54 AM UTC **Owner:** nobody Steps to reproduce: 1. Start two controllers(SC-1 Act, SC-2 Standby) and two paylods. Configure 50 components on SC-2 and unlock them. Keep 1 sec delay in each component stop script. 2. Stop SC-1 and after that, stop SC-2. 3. During SC-2 is going down, start SC-1. Observed behaviour: Since components are taking time in stopping all components during 'opensad stop' of SC-2, Amfnd hasn't exited. But, all middleware components assignments are stopped. Only Amfnd and Amfd is alive with few more components to stop. But SC-1 has come up till Amfd and since two Amfd is Act now, so SC-2 Amfd exits by saying "Duplicate ACTIVE detected, exiting". Till this time, services states including Amfd is in bad state as they couldn't differentiate whether it is headless state or failover. This is true also as the system is in half middle of headless and failover. Expected behaviour In my view: FMS should stop and shouldn't proceed if peer is going down. i.e. FMS should figure out on SC-1 that the peer system is going down. And should allow SC-1 only if all services are down i.e. it gets node down (may be cb->immd_down && cb->immnd_down && cb->amfnd_down && cb->amfd_down && cb->fm_down). --- 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.-- The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2147 smf: balanced upgrade, modifications missing after reboot
- **status**: assigned --> review --- ** [tickets:#2147] smf: balanced upgrade, modifications missing after reboot** **Status:** review **Milestone:** 5.1.1 **Created:** Fri Oct 28, 2016 10:13 AM UTC by Rafael **Last Updated:** Fri Oct 28, 2016 10:13 AM UTC **Owner:** Rafael The issue happens duing balanced upgrade when doing an SI SWAP on the controllers just before starting the balanced procedures. In this case SMF normally would read the IMM data for any step modifications ticket [#906] changed that to not read any modifications when the procedures are in COMPLETE state. Solution is to keep the behaviour in a non balanced upgrade. When executing a balanced upgrade the modifications are read and a error check (forAddRemove and forModify) is skipped. --- 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.-- The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2152 smf: describe rollback limitation in balanced upgrade
--- ** [tickets:#2152] smf: describe rollback limitation in balanced upgrade** **Status:** unassigned **Milestone:** 5.1.1 **Created:** Mon Oct 31, 2016 12:06 PM UTC by Rafael **Last Updated:** Mon Oct 31, 2016 12:06 PM UTC **Owner:** Rafael Rollback is not tested or implemented to work in the balanced upgrade type of execution. Describe this in the SMF PR document. --- 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.-- The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2102 build: Make it possible to do a full installation of OpenSAF with RPMs
- **status**: review --> fixed - **Comment**: changeset: 8272:277d16bcdd50 user:Anders Widell date:Mon Oct 31 13:13:15 2016 +0100 summary: build: Make it possible to perform a full OpenSAF installation from RPMs [#2102] [staging:277d16] --- ** [tickets:#2102] build: Make it possible to do a full installation of OpenSAF with RPMs** **Status:** fixed **Milestone:** 5.2.FC **Created:** Fri Oct 07, 2016 02:08 PM UTC by Anders Widell **Last Updated:** Thu Oct 13, 2016 03:49 PM UTC **Owner:** Anders Widell When installing OpenSAF from RPMs, you have to select to install either the opensaf-controller or the opensaf-payload package. If you have installed the opensaf-controller package, it is not possible to configure the node as a payload node, and vice versa. The suggestion is to include everything needed to configure the node as either a controller or a payload in the opensaf-controller package, i.e. by selecting to install this package you will get a full installation of OpenSAF, in the same was as you do if you install from source using "make install". --- 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.-- The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2153 smf: Fails to create a node group, admin owner/handle is lost
--- ** [tickets:#2153] smf: Fails to create a node group, admin owner/handle is lost** **Status:** accepted **Milestone:** 5.1.1 **Created:** Mon Oct 31, 2016 02:54 PM UTC by elunlen **Last Updated:** Mon Oct 31, 2016 02:54 PM UTC **Owner:** elunlen Even though handles and admin owner needed to create a node group is created just before the node group shall be created the creation may still fail because of bad handle or missing admin owner. To increase robustness a mechanism for recreation of handles and admin owner similar to handling when deleting a node group should be implemented --- 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.-- The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2154 smf: non backward compatible name change for ExecCtrlCopy
--- ** [tickets:#2154] smf: non backward compatible name change for ExecCtrlCopy** **Status:** unassigned **Milestone:** 5.1.1 **Created:** Mon Oct 31, 2016 03:18 PM UTC by Rafael **Last Updated:** Mon Oct 31, 2016 03:18 PM UTC **Owner:** Rafael there was a name change introduced in patch for ticket #2114. This changed the name of the object openSafSmfExecControl_copy to openSafSmfExecControl=SmfHdlCopy. This causes the new upgrades between these two versions to fail. --- 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.-- The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2154 smf: non backward compatible name change for ExecCtrlCopy
- Description has changed: Diff: --- old +++ new @@ -1 +1 @@ -there was a name change introduced in patch for ticket #2114. This changed the name of the object openSafSmfExecControl_copy to openSafSmfExecControl=SmfHdlCopy. This causes the new upgrades between these two versions to fail. +there was a name change introduced in patch for ticket #2114. This changed the name of the object openSafSmfExecControl_copy to openSafSmfExecControl=SmfHdlCopy. This change causes the upgrades between these two versions to fail. --- ** [tickets:#2154] smf: non backward compatible name change for ExecCtrlCopy** **Status:** unassigned **Milestone:** 5.1.1 **Created:** Mon Oct 31, 2016 03:18 PM UTC by Rafael **Last Updated:** Mon Oct 31, 2016 03:18 PM UTC **Owner:** Rafael there was a name change introduced in patch for ticket #2114. This changed the name of the object openSafSmfExecControl_copy to openSafSmfExecControl=SmfHdlCopy. This change causes the upgrades between these two versions to fail. --- 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.-- The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2154 smf: non backward compatible name change for ExecCtrlCopy
- Description has changed: Diff: --- old +++ new @@ -1 +1 @@ -there was a name change introduced in patch for ticket #2114. This changed the name of the object openSafSmfExecControl_copy to openSafSmfExecControl=SmfHdlCopy. This change causes the upgrades between these two versions to fail. +there was a name change introduced in patch for ticket [#2114]. This changed the name of the object openSafSmfExecControl_copy to openSafSmfExecControl=SmfHdlCopy. This change causes the upgrades between these two versions to fail. - **status**: unassigned --> assigned --- ** [tickets:#2154] smf: non backward compatible name change for ExecCtrlCopy** **Status:** assigned **Milestone:** 5.1.1 **Created:** Mon Oct 31, 2016 03:18 PM UTC by Rafael **Last Updated:** Mon Oct 31, 2016 03:19 PM UTC **Owner:** Rafael there was a name change introduced in patch for ticket [#2114]. This changed the name of the object openSafSmfExecControl_copy to openSafSmfExecControl=SmfHdlCopy. This change causes the upgrades between these two versions to fail. --- 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.-- The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2144 AMF: support restrictions to auto-repair
- **status**: assigned --> review --- ** [tickets:#2144] AMF: support restrictions to auto-repair ** **Status:** review **Milestone:** 5.2.FC **Created:** Thu Oct 27, 2016 04:36 PM UTC by Alex Jones **Last Updated:** Thu Oct 27, 2016 04:36 PM UTC **Owner:** Alex Jones This ticket adds support for Section 3.11.1.4.2 of AMF B.4.1 spec: Restrictions to Auto-Repair. --- 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.-- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2145 SMF: add support for detection of asynchronous failures of AMF entities
- **status**: assigned --> review --- ** [tickets:#2145] SMF: add support for detection of asynchronous failures of AMF entities** **Status:** review **Milestone:** 5.2.FC **Created:** Thu Oct 27, 2016 04:42 PM UTC by Alex Jones **Last Updated:** Thu Oct 27, 2016 04:43 PM UTC **Owner:** Alex Jones This ticket adds support for Section 4.2.1.3 of SMF A.01.02 spec: Detection of Asynchronous Failures of AMF Entities. The ticket which does the AMF related work is 2144. --- 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.-- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
