You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
UEFI VMs on KVM throwing error "No enum constant com.cloud.hypervisor.kvm.resource.LibvirtVMDef.WatchDogDef.WatchDogModel.ITCO" #9038
Bug Report
UEFI VMs on KVM throwing error "No enum constant com.cloud.hypervisor.kvm.resource.LibvirtVMDef.WatchDogDef.WatchDogModel.ITCO"
Due to this the VMs are running but unable to open console or manage instance i.e start/stop instances
COMPONENT NAME
UI
CLOUDSTACK VERSION
4.19.0.1
CONFIGURATION
OS / ENVIRONMENT
Used to ISO to boot VM , happens with all instance
SUMMARY
Cloudstack is managing and running VMs with BIOS boot perfectly , but when selected UEFI with Legacy or Secure below error is throw :
WARN [cloud.agent.Agent] (agentRequest-Handler-1:null) (logid:fb71c7dd) Caught:
java.lang.IllegalArgumentException: No enum constant com.cloud.hypervisor.kvm.resource.LibvirtVMDef.WatchDogDef.WatchDogModel.ITCO
at java.base/java.lang.Enum.valueOf(Enum.java:240)
at com.cloud.hypervisor.kvm.resource.LibvirtVMDef$WatchDogDef$WatchDogModel.valueOf(LibvirtVMDef.java:2202)
at com.cloud.hypervisor.kvm.resource.LibvirtDomainXMLParser.parseDomainXML(LibvirtDomainXMLParser.java:384)
at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.getInterfaces(LibvirtComputingResource.java:4258)
at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.getVmStat(LibvirtComputingResource.java:4452)
at com.cloud.hypervisor.kvm.resource.wrapper.LibvirtGetVmStatsCommandWrapper.execute(LibvirtGetVmStatsCommandWrapper.java:53)
at com.cloud.hypervisor.kvm.resource.wrapper.LibvirtGetVmStatsCommandWrapper.execute(LibvirtGetVmStatsCommandWrapper.java:37)
at com.cloud.hypervisor.kvm.resource.wrapper.LibvirtRequestWrapper.execute(LibvirtRequestWrapper.java:78)
at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1903)
at com.cloud.agent.Agent.processRequest(Agent.java:683)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:1106)
at com.cloud.utils.nio.Task.call(Task.java:83)
at com.cloud.utils.nio.Task.call(Task.java:29)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
I have checked out #8282 but that does not help much here as even with ITCO watchdog issue is coming up, i can see two watchdogs are being added on VM - 'i6300esb' and 'itco'
Activity
boring-cyborg commentedon May 3, 2024
Thanks for opening your first issue here! Be sure to follow the issue template!
weizhouapache commentedon May 3, 2024
@sghazra21
4.19.0.1 does not have the fix.
sghazra21 commentedon May 3, 2024
Is the fix planned for this version or should i test by downgrading it ?
Also if i downgrade will existing instances be impacted ?
weizhouapache commentedon May 3, 2024
@sghazra21
the fix is including in 4.18.2.0 release and upcoming 4.19.1.0 release (planned in June)
you can build packages for 4.19.0.1 and the fix