GutoVeronezi opened a new pull request #4586: URL: https://github.com/apache/cloudstack/pull/4586
### Description On KVMHAMonitor, when there is an inconsistency on the heartbeat's file or heartbeat timeout is extrapolated several times, the host is restarted. The host restarting amid several operations might bring inconsistency problems; therefore, it is interesting to let operators choose if they want the host restart or not on the hearbeat's timeout or storage errors. This PR intends to externalize the heartbeat reboot configuration on KVMHAMonitor. The default value is `true`; therefore, the current behavior is maintained. This PR depends on [PR#4585](https://github.com/apache/cloudstack/pull/4585). ### 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) - [x] Enhancement (improves an existing feature and functioanlity) - [ ] Cleanup (Code refactoring and cleanup, that may add test cases) ### Feature/Enhancement Scale or Bug Severity #### Feature/Enhancement Scale - [x] Major - [ ] Minor ### How Has This Been Tested? It has been tested locally on a test lab. 1. On agent, I changed my log4j to debug mode. 2. I added `hearbeat.update.timeout=10` setting to `agent.properties` to force a timeout on hearbeat. 3. I added `reboot.host.and.alert.management.on.hearbeat.timeout` setting to `agent.properties` and changed it some times; 4. I restarted agent and watched the log. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
