Shut down the secondary node

Description – shut down the secondary node where ERS is running.

Run node – secondary node where ERS is running.

Run steps

Log in to the Amazon Web Services Management Console and stop the ERS instance.

Expected result – the cluster will detect the failed ERS node and start ERS on the primary node (node 1).

hahost01:~ # crm status
Cluster Summary:
  * Stack: corosync
  * Current DC: hahost01 (version 2.0.xxxxxxxxxxxx) - partition with quorum
  * Last updated: 
  * Last change:  by root via crm_resource on hahost02
  * 2 nodes configured
  * 7 resource instances configured

Node List:
  * Online: [ hahost01 ]
  * OFFLINE: [ hahost02 ]

Full List of Resources:
  * res_AWS_STONITH     (stonith:external/ec2):  Started hahost01
  * Resource Group: grp_HA1_ASCS00:
    * rsc_IP_HA1_ASCS00 (ocf::suse:aws-vpc-move-ip):     Started hahost01
    * rsc_FS_HA1_ASCS00 (ocf::heartbeat:Filesystem):     Started hahost01
    * rsc_SAP_HA1_ASCS00        (ocf::heartbeat:SAPInstance):    Started hahost01
  * Resource Group: grp_HA1_ERS10:
    * rsc_IP_HA1_ERS10  (ocf::suse:aws-vpc-move-ip):     Started hahost01
    * rsc_FS_HA1_ERS10  (ocf::heartbeat:Filesystem):     Started hahost01
    * rsc_SAP_HA1_ERS10 (ocf::heartbeat:SAPInstance):    Started hahost01

Recovery procedure