Update SCS high availability documentation and refactor ASCS resource migration commands for improved clarity and consistency

Author: devanshjainms

docs/SCS_HIGH_AVAILABILITY.md

@@ -5,6 +5,5 @@
 | Test Case                    | Type          | Description                                                                                                                                                                   | More Info                                                                                                       |
 |------------------------------|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------|
 | HA Parameters Validation     | Configuration | The HA parameter validation test validates HA configuration including Corosync settings, Pacemaker resources, SBD device configuration, and SCS system replication setup.  | [ha-config.yml](../src/roles/ha_scs/tasks/ha-config.yml)                                                        |
-| Azure Load Balancer          | Configuration | The Azure LB configuration test validates Azure Load Balancer setup including health probe configuration, backend pool settings, load balancing rules, and frontend IP configuration. | [azure-lb.yml](../src/roles/ha_scs/tasks/azure-lb.yml)                                                          |
 | Resource Migration           | Failover      | The Resource Migration test validates planned failover scenarios by controlling resource movement between SCS nodes, ensuring proper role changes and data synchronization. | [ascs-migration.yml](../src/roles/ha_scs/tasks/ascs-migration.yml)                                        |
-| Block Network                | Network       | The Block Network test validates SCS behavior during network partition scenarios by blocking communication between primary and secondary nodes, confirming split-brain prevention. | [block-network.yml](../src/roles/ha_scs/tasks/block-network.yml)                                                  |
+| ASCS Node Crash                | Network       | The ASCS Node Crash test simulates cluster behavior when the ASCS node crashes. It simulates an ASCS node failure by forcefully terminating the process, then verifies automatic failover to the ERS node, monitors system replication status, and confirms service recovery without data loss. | [ascs-node-crash.yml](../src/roles/ha_scs/tasks/ascs-node-crash.yml)                                                  |

src/roles/ha_scs/tasks/ascs-migration.yml

@@ -34,7 +34,9 @@
       become:                           true
       block:
         - name:                         "Test Execution: Migrate ASCS resource"
-          ansible.builtin.command:      "crm resource move rsc_sap_{{ sap_sid }}_ASCS{{ scs_instance_number }} force"
+          ansible.builtin.command:      "{{ commands | selectattr(
+                                        'name', 'equalto', 'ascs_resource_migration_cmd') | map(
+                                        attribute=(ansible_os_family | upper)) | first }}"
           register:                     migration_result
 
         - name:                         "Test Execution: Validate SCS cluster status"
@@ -50,7 +52,9 @@
                                         and cluster_status_test_execution.ers_node == cluster_status_pre.ascs_node
 
         - name:                         "Test Execution: Remove location constraints"
-          ansible.builtin.command:      "crm resource clear rsc_sap_{{ sap_sid }}_ASCS{{ scs_instance_number }}"
+          ansible.builtin.command:      "{{ commands | selectattr(
+                                        'name', 'equalto', 'ascs_resource_unmigrate_cmd') | map(
+                                        attribute=(ansible_os_family | upper)) | first }}"
           register:                     unmigrate_result
 
         - name:                         "Test Execution: Cleanup resources"

src/vars/input-api.yaml

@@ -170,5 +170,13 @@ commands:
     SUSE:                           "crm_report -f '{{ test_group_start_time }}' /tmp/{{ test_group_invocation_id }}"
     REDHAT:                         "crm_report -f '{{ test_group_start_time }}' --dest /tmp/{{ test_group_invocation_id }} -yes"
 
+  - name:                           ascs_resource_migration_cmd
+    SUSE:                           "crm resource move rsc_sap_{{ sap_sid }}_ASCS{{ scs_instance_number }} force"
+    REDHAT:                         "pcs resource move rsc_sap_{{ sap_sid }}_ASCS{{ scs_instance_number }}"
+
+  - name:                           ascs_resource_unmigrate_cmd
+    SUSE:                           "crm resource clear rsc_sap_{{ sap_sid }}_ASCS{{ scs_instance_number }}"
+    REDHAT:                         "pcs resource clear rsc_sap_{{ sap_sid }}_ASCS{{ scs_instance_number }}"
+
 sap_sid:                            "HDB"
 db_sid:                             "HDB"