VR HA is not getting triggered by Cloudstack

[kiranchavala]

ISSUE TYPE

BUG

Component Name

HA, Management server

CLOUDSTACK VERSION

Cloudstack version 4.19

SUMMARY

VR HA is not getting triggered by Cloudstack

Steps to reproduce the issue

1. Create a cloudstack env with 2 kvm hosts

2. Create a new system offering for virtual router with Ha enabled option or use the default (System Offering For Software Router).

Make sure offerha parameter is set when list serviceofferings issystem=true

{
      "cpunumber": 1,
      "cpuspeed": 500,
      "created": "2024-02-20T10:52:30+0000",
      "defaultuse": true,
      "diskofferingstrictness": false,
      "dynamicscalingenabled": true,
      "encryptroot": false,
      "hasannotations": false,
      "id": "13dd43a0-3ddf-4cb4-b81b-a191cffdf7a0",
      "iscustomized": false,
      "issystem": true,
      "isvolatile": false,
      "limitcpuuse": false,
      "memory": 256,
      "name": "System Offering For Software Router",
      "offerha": true,
      "provisioningtype": "thin",
      "rootdisksize": 0,
      "storagetype": "shared",
      "systemvmtype": "domainrouter"
 },

   {
      "cacheMode": "none",
      "cpunumber": 1,
      "cpuspeed": 500,
      "created": "2024-03-19T03:58:21+0000",
      "defaultuse": false,
      "diskofferingstrictness": false,
      "displaytext": "harouter",
      "dynamicscalingenabled": true,
      "encryptroot": false,
      "hasannotations": false,
      "id": "3212cee3-3ac0-46cb-9a85-10781ecdefb8",
      "iscustomized": false,
      "iscustomizediops": false,
      "issystem": true,
      "isvolatile": false,
      "limitcpuuse": false,
      "maxiops": 0,
      "memory": 256,
      "miniops": 0,
      "name": "harouter",
      "offerha": true,
      "provisioningtype": "thin",
      "rootdisksize": 0,
      "storagetype": "shared",
      "systemvmtype": "domainrouter"
    } 

3. Set the global setting value for "router.service.offering" to the UUID vaule of the service offering or leave it NULL

4. Create a Network and deploy the vm in the network

5. Make sure router is running host 1 and the vm is running on host 2

6. Login to the kvm host 1 and execute the following command

echo c > /proc/sysrq-trigger

7. After 10 min the host 1 will be marked as down and the vr will be in stopped state

This issue is not occuring for ssvm and console proxy

Actual Behaviour

VR is in stopped state

Expected Behaviour

VR should migrate to HOST 2

[kiranchavala]

This issue is not observed in the latest build of 4.19.1