mahdiadnan opened a new issue, #11604: URL: https://github.com/apache/cloudstack/issues/11604
### problem After upgrading the clustering to version 4.21 from version 4.20, following the document https://docs.cloudstack.apache.org/en/latest/upgrading/upgrade/upgrade-4.20.html cloudstack-agent failed to start with sig=kill Logs from agent.log 2025-09-10 14:21:01,960 INFO [cloud.agent.AgentShell] (main:[]) (logid:) Agent started 2025-09-10 14:21:01,963 INFO [cloud.agent.AgentShell] (main:[]) (logid:) Implementation Version is 4.21.0.0 2025-09-10 14:21:01,964 INFO [cloud.agent.AgentShell] (main:[]) (logid:) agent.properties found at /etc/cloudstack/agent/agent.properties 2025-09-10 14:21:01,994 INFO [cloud.agent.AgentShell] (main:[]) (logid:) Defaulting to using properties file for storage 2025-09-10 14:21:01,995 INFO [cloud.agent.AgentShell] (main:[]) (logid:) Defaulting to the constant time backoff algorithm 2025-09-10 14:21:02,021 INFO [cloud.agent.AgentShell] (main:[]) (logid:) Using default Java settings for IPv6 preference for agent connection 2025-09-10 14:21:02,088 INFO [cloud.agent.Agent] (main:[]) (logid:) Initialising agent [id: 34, uuid: b3e4fd47-bc22-4feb-9673-c35dc06727db, name: xxxx] 2025-09-10 14:21:02,094 ERROR [kvm.resource.LibvirtComputingResource] (main:[]) (logid:) uefi properties file not found due to: Unable to find file uefi.properties. 2025-09-10 14:21:02,270 INFO [kvm.resource.LibvirtComputingResource] (main:[]) (logid:) IO uring driver for Qemu: enabled 2025-09-10 14:21:02,349 INFO [kvm.storage.KVMStoragePoolManager] (main:[]) (logid:) Adding storage adaptor for com.cloud.hypervisor.kvm.storage.LinstorStorageAdaptor 2025-09-10 14:21:02,350 INFO [kvm.storage.KVMStoragePoolManager] (main:[]) (logid:) Adding storage adaptor for com.cloud.hypervisor.kvm.storage.StorPoolStorageAdaptor 2025-09-10 14:21:02,351 INFO [kvm.storage.KVMStoragePoolManager] (main:[]) (logid:) Adding storage adaptor for com.cloud.hypervisor.kvm.storage.ScaleIOStorageAdaptor 2025-09-10 14:21:02,352 INFO [kvm.storage.KVMStoragePoolManager] (main:[]) (logid:) Adding storage adaptor for com.cloud.hypervisor.kvm.storage.IscsiAdmStorageAdaptor 2025-09-10 14:21:02,352 INFO [kvm.storage.KVMStoragePoolManager] (main:[]) (logid:) Adding storage adaptor for com.cloud.hypervisor.kvm.storage.ManagedNfsStorageAdaptor 2025-09-10 14:21:02,359 INFO [kvm.storage.KVMStoragePoolManager] (main:[]) (logid:) Adding storage adaptor for com.cloud.hypervisor.kvm.storage.FiberChannelAdapter 2025-09-10 14:21:02,359 INFO [kvm.resource.LibvirtComputingResource] (main:[]) (logid:) No libvirt.vif.driver specified. Defaults to BridgeVifDriver. 2025-09-10 14:21:02,490 INFO [kvm.resource.LibvirtComputingResource] (main:[]) (logid:) iscsi session clean up is disabled 2025-09-10 14:21:02,493 INFO [kvm.resource.LibvirtComputingResource] (main:[]) (logid:) Skipping the memory balloon stats period setting, since there are no VMs (active Libvirt domains) on this host. 2025-09-10 14:21:02,493 INFO [kvm.resource.LibvirtComputingResource] (main:[]) (logid:) The [vm.memballoon.stats.period] property is set to '0', this prevents memory statistics from being displayed correctly. Adjust (increase) the value of this parameter to correct this. 2025-09-10 14:21:02,495 INFO [cloud.agent.Agent] (main:[]) (logid:) Agent [id = 34, uuid = b3e4fd47-bc22-4feb-9673-c35dc06727db, name = xxx, type = LibvirtComputingResource, zone = 2, pod = 2, workers = 5, port = 8250] with host = xxx, local id = 1 2025-09-10 14:21:02,836 INFO [kvm.resource.LibvirtComputingResource] (Agent-Handler-1:[]) (logid:) Host uses control group [cgroup2fs]. 2025-09-10 14:21:02,836 INFO [kvm.resource.LibvirtComputingResource] (Agent-Handler-1:[]) (logid:) Calculating the max shares of the host. 2025-09-10 14:21:02,837 INFO [kvm.resource.LibvirtComputingResource] (Agent-Handler-1:[]) (logid:) The max shares of the host is [200000]. 2025-09-10 14:21:04,134 INFO [cloud.agent.Agent] (Agent-Handler-2:[]) (logid:) Process agent startup answer, agent [id: 0, uuid: , name: ] connected to the server 2025-09-10 14:21:04,135 INFO [cloud.agent.Agent] (Agent-Handler-2:[]) (logid:) Startup Response Received: agent [id: 0, uuid: , name: ] 2025-09-10 14:21:04,526 INFO [cloud.agent.Agent] (AgentRequest-Handler-4:[]) (logid:5618826b) Processing agent ready command, agent id = 34, uuid = b3e4fd47-bc22-4feb-9673-c35dc06727db, name = xxx 2025-09-10 14:21:04,527 INFO [cloud.agent.Agent] (AgentRequest-Handler-4:[]) (logid:5618826b) Ready command is processed for agent [id: 34, uuid: b3e4fd47-bc22-4feb-9673-c35dc06727db, name: xxx] 2025-09-10 14:21:05,169 INFO [cloud.agent.Agent] (AgentShutdownThread:[]) (logid:) Stopping the agent: Reason = sig.kill ### versions From v 4.20.1 to 4.21 OS is Alma Linux 9.6 <kernel 5.14.0-570.37.1.el9_6.x86_64> virt-v2v version 1:2.7.1-10.el9_6 ### The steps to reproduce the bug 1. Update the cloudstack-agent using dnf 2. Restart the cloudstack-agent.service using systemctl 3. Agent logs showing the service was getting killed with sig=kill ... ### What to do about it? After removing virt-v2v package, the agent starts without issues. -- 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]
