[4.22.1.0-shapeblue1] KVM HA fixes #13373 and #13377

[harikrishna-patnala]

Description

This PR is a duplicate of upstream PRs apache#13373 and apache#13377 to address the same in the ShapeBlue custom patch 4.22.1.0-shapeblue1

cc @sureshanaparti

Types of changes

• Breaking change (fix or feature that would cause existing functionality to change)
• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Enhancement (improves an existing feature and functionality)
• Cleanup (Code refactoring and cleanup, that may add test cases)
• Build/CI
• Test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

• Major
• Minor

Bug Severity

• BLOCKER
• Critical
• Major
• Minor
• Trivial

Screenshots (if appropriate):

How Has This Been Tested?

How did you try to break this feature and the system with this change?

[harikrishna-patnala]

@blueorangutan package

[kiranchavala]

@weizhouapache @NuxRo @rajujith @sureshanaparti @harikrishna-patnala @andrijapanicsb

what should be the expected behaviour of vm ha in case of soft power off the kvm host

Steps to reproduce the issue

1. Create a HA enabled offering
2. Deploy a vm with HA enabled offering on a kvm host 1
3. Login to the kvm host 1
4. Issue shutdown command
5. VM HA doesn't get triggered
6. Global setting value : commands.timeout = CheckHealthCommand=5,CheckOnHostCommand=5

[root@ref-trl-11991-k-Mol8-kiran-chavala-kvm1 ~]# virsh list
 Id   Name       State
--------------------------
 1    i-2-6-VM   running

[root@ref-trl-11991-k-Mol8-kiran-chavala-kvm1 ~]# shutdown now
Connection to 10.0.32.193 closed by remote host.
Connection to 10.0.32.193 closed.

7. Host goes into disconnected state
8. No entry created in ( select * from op_ha_work) table
9. grep "status reported from itself" /var/log/cloudstack/management/management-server.log

---

VM HA gets triggered only if hard power-off a KVM host

[weizhouapache]

if Host goes into disconnected state, VM HA will NOT be triggered.
It is a known issue, we will address in a customer FR.