GitHub user weizhouapache added a comment to the discussion: KVMHAMonitor getting initialized without host ha enabled
> > > > > @DaanHoogland now I am confused! Why is KVMHAMonitor rebooting hosts > > > > > when the host is unable to write a heartbeat file to any storage when > > > > > any HA setting is disabled in the UI? Do you know the reason for that? > > > > > > > > > > > > @sbrueseke You can add a setting in `/etc/cloudstack/agent.properties` > > > > and restart cloudstack-agent > > > > ``` > > > > reboot.host.and.alert.management.on.heartbeat.timeout=false > > > > ``` > > > > > > > > > I know this workaround. My question is if this setting should be added by > > > the management server instead of manually. Is there any legit reason > > > KVMHAMonitor should reboot a host when all HA settings are disabled in > > > the UI? > > > > > > @sbrueseke as I understand, the Host HA means the HA solutions by OOBM/IPMI > > Can you explain the root cause why KVMHAMonitor needs to reboot the host when > a storage is read only? @sbrueseke it is the old behaviour introduced more than 10 years ago. I am not clear why. there were lots of discussion in the past https://github.com/apache/cloudstack/pull/2722 https://github.com/apache/cloudstack/issues/2890 https://github.com/apache/cloudstack/pull/2984 https://github.com/apache/cloudstack/pull/4586 and #4708 since storage issue rarely happens, it may be ok for users to change the setting in agent.properties GitHub link: https://github.com/apache/cloudstack/discussions/8953#discussioncomment-9174427 ---- This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
