Hello,
I had the same problem not long ago. I added a new primary storage
(NFS) volume which did not have the proper write permissions (already
had multiple attached from the same storage and working fine) . When ACS
failed to create the KVMHA folder on it it rebooted all my hosts which
brought down the entire zone. Worst thing is the reboots are repeated
until you fix the underlying cause (or put the storage in maintenance mode).
I've updated the config's already as suggested here and will update our
procedures to manually do a mount and write permissions test before
adding a new storage volume.
I do feel this script is a bit trigger happy and an alert would be just
fine in these cases.
Regards,
On 9/17/25 13:58, rohityadavcloud (via GitHub) wrote:
GitHub user rohityadavcloud added a comment to the discussion: KVM hosts got
rebooted while adding NFS primary storage
I hit the same issue few weeks ago and can confirm the agent.properties
certainly helped.
GitHub link:
https://github.com/apache/cloudstack/discussions/11657#discussioncomment-14427474
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
--
David Sekne
Systems Administrator
--
DHH Infrastructure team
Webtasy, d.o.o., Slovenia
Plus Hosting Grupa d.o.o., Croatia
mCloud d.o.o., Serbia
