René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Autoscale Load Balancing Rule looses VMs during a node failure.","articleBody":"\u003c!--\r\nVerify first that your issue/request is not already reported on GitHub.\r\nAlso test if the latest release and main branch are affected too.\r\nAlways add information AFTER of these HTML comments, but no need to delete the comments.\r\n--\u003e\r\n\r\n##### ISSUE TYPE\r\n\u003c!-- Pick one below and delete the rest --\u003e\r\n * Bug Report\r\n\r\n##### COMPONENT NAME\r\n\u003c!--\r\nCategorize the issue, e.g. API, VR, VPN, UI, etc.\r\n--\u003e\r\n~~~\r\nAutoscaling, Load Balancer\r\n~~~\r\n\r\n##### CLOUDSTACK VERSION\r\n\u003c!--\r\nNew line separated list of affected versions, commit ID for issues on main branch.\r\n--\u003e\r\n\r\n~~~\r\n4.19.0\r\n~~~\r\n\r\n##### CONFIGURATION\r\n\u003c!--\r\nInformation about the configuration if relevant, e.g. basic network, advanced networking, etc.  N/A otherwise\r\n--\u003e\r\n\r\n\r\n##### OS / ENVIRONMENT\r\n\u003c!--\r\nInformation about the environment if relevant, N/A otherwise\r\n--\u003e\r\n\r\n\r\n##### SUMMARY\r\n\u003c!-- Explain the problem/feature briefly --\u003e\r\n\r\nWe have a few Autoscale Rules running in production. For simplicity, lets say we have 1 Autoscale Rule, with 4 VMs currently under the Rule. \r\n\r\n2 of the VMs are located in a server that has experienced a node failure.\r\n\r\nDuring the node failure, the VMs are restarted in a new node.  The 2 VMs started up again in the new server. When you go to the Autoscale Load Balancing Rule, you will notice that these 2 VMs are not under the Autoscale Rule anymore. They are now orphans. \r\n\r\nBut, the autoscale rule will still state it has a total of 4 scaled up VMs\r\n\r\nIn summary, \r\n- Total No. Of VMs resulting from Autoscale : 4 VMs\r\n- No. of VMs under LB Rule: 2 VMs\r\n- No. Of VMs as Orphans : 2VMs\r\n\r\n##### STEPS TO REPRODUCE\r\n\u003c!--\r\nFor bugs, show exactly how to reproduce the problem, using a minimal test-case. Use Screenshots if accurate.\r\n\r\nFor new features, show how the feature would be used.\r\n--\u003e\r\n\r\n\u003c!-- Paste example playbooks or commands between quotes below --\u003e\r\n~~~\r\n- Create Autoscale Rule with Multiple VMs\r\n- Live Migrate VMs to another host\r\n- Force Power Off the Host to simulate node failure\r\n- Wait for VMs to restart in new Node\r\n- Go to Autoscale Load Balancer, and display the list of VMs under the load balancing rule\r\n- If cannot replicate the issue, retry it again until it happens. It may be intermittent.\r\n~~~\r\n\r\n\u003c!-- You can also paste gist.github.com links for larger files --\u003e\r\n\r\n##### EXPECTED RESULTS\r\n\u003c!-- What did you expect to happen when running the steps above? --\u003e\r\n\r\n~~~\r\nA logic should be implemented to:\r\n- Scale up the VMs when it has detected the node is down (to fufill the scale up requirement)\r\n- Do not restart the VMs from the host failure to prevent confusion.\r\n~~~\r\n\r\n##### ACTUAL RESULTS\r\n\u003c!-- What actually happened? --\u003e\r\n\r\n\u003c!-- Paste verbatim command output between quotes below --\u003e\r\n~~~\r\nVMs are missing from the load balancing rule\r\n~~~\r\n","author":{"url":"https://github.com/btzq","@type":"Person","name":"btzq"},"datePublished":"2024-05-29T14:24:53.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":9},"url":"https://github.com/9145/cloudstack/issues/9145"}