search

SUSE / suse-best-practices

SUSE Best Practices documentation series
42 stars 74 forks source link

[doc] 4.5 Tagging the EC2 Instances #270

Open Thr3d opened 2 years ago

Thr3d commented 2 years ago

4.5 Tagging the EC2 Instances:

https://documentation.suse.com/sbp/all/html/SLES4SAP-hana-sr-guide-PerfOpt-15_AWS/index.html#id-tagging-the-ec2-instances

Using a capitalized value for the EC2 fence tag will cause the fence operation to fail even if the node's hostname is capitalized. A note should be added here mentioning the value needs to be lowercase.

Example: pacemaker tag value is SAP15SP2-NODE0 but EC2 stonith agent expects sap15sp2-node1. Updating the tag value to be lowercase resolved this.

Feb 25 21:38:56 SAP15SP2-NODE0 external/ec2(res_AWS_STONITH)[16017]: info: status check for sap15sp2-node1 is
Feb 25 21:38:58 SAP15SP2-NODE0 external/ec2(res_AWS_STONITH)[16031]: info: status check for sap15sp2-node1 is
Feb 25 21:38:59 SAP15SP2-NODE0 external/ec2(res_AWS_STONITH)[16045]: info: status check for sap15sp2-node1 is
Feb 25 21:39:00 SAP15SP2-NODE0 pacemaker-fenced[7641]:  warning: fence_legacy[11256] stderr: [ An error occurred (InvalidInstanceID.Malformed) when calling the DescribeInstances operation: Invalid id: "sap15sp2-node1" ]
Feb 25 21:39:00 SAP15SP2-NODE0 pacemaker-fenced[7641]:  error: Operation 'off' [11256] (call 10 from pacemaker-controld.7645) for host 'SAP15SP2-NODE1' with device 'res_AWS_STONITH' returned: -62 (Timer expired)
Feb 25 21:39:00 SAP15SP2-NODE0 pacemaker-fenced[7641]:  error: Operation 'off' targeting SAP15SP2-NODE1 on SAP15SP2-NODE0 for pacemaker-controld.7645@SAP15SP2-NODE0.e8b5638c: Timer expired
chabowski commented 2 years ago

@fmherschel @lpinne could you please have a look at this issue? Thanks very much :-).

lpinne commented 2 years ago

Hi Thr3d, hi Meike,

we need to discuss who should handle that cloud platform specific requests.

Regards, Lars

stephenmogg commented 2 years ago

Hi Meike, I just updated the doc and logged a bug for this.

chabowski commented 2 years ago

Hi Stephen, thank you very much! The changes will be online with the next repo build - this however will only happen somewhen next week. Hope this is okay.