TadiosAbebe commented on issue #11141:
URL: https://github.com/apache/cloudstack/issues/11141#issuecomment-3568368239

   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.


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to