GitHub user TadiosAbebe added a comment to the discussion: Degraded cloudstack agent
I am beginning to doubt whether this issue is related to the CloudStack agent. Over the past few weeks, I’ve been looking more closely at the problem. As I mentioned earlier, I encounter it fairly frequently, and it affects basic VM operations such as creating, starting, stopping, and accessing the console. It turns out my earlier assumption was incorrect and force reconnecting the compute host does not consistently resolve the issue. This time, instead of reconnecting the host or restarting the cloudstack-agent service, I tried restarting the libvirtd service whenever i encounter the issue. I tested this several times, and in every case, simply restarting libvirtd (without restarting CloudStack agent) resolved the issue. I haven't seen any noticeable differences in the libvirtd logs compared to a working host, so it’s difficult to pinpoint the root cause. Since this doesn’t appear to be a widely reported problem, I suspect it may be environmental. All my compute hosts are running Ubuntu Server 24.04, and the environment uses a hyperconverged Ceph setup. GitHub link: https://github.com/apache/cloudstack/discussions/12450#discussioncomment-15515823 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
