Re: [I] Agent 4.21.0.0 secondarystoragevm [cloudstack]
weizhouapache commented on issue #11552: URL: https://github.com/apache/cloudstack/issues/11552#issuecomment-3261918659 fixed by #11557 -- 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]
Re: [I] Agent 4.21.0.0 secondarystoragevm [cloudstack]
weizhouapache closed issue #11552: Agent 4.21.0.0 secondarystoragevm URL: https://github.com/apache/cloudstack/issues/11552 -- 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]
Re: [I] Agent 4.21.0.0 secondarystoragevm [cloudstack]
jonathaanbastin commented on issue #11552: URL: https://github.com/apache/cloudstack/issues/11552#issuecomment-3252495779 > > [@jonathaanbastin](https://github.com/jonathaanbastin) [@amitmvyas](https://github.com/amitmvyas) [@daviftorres](https://github.com/daviftorres) > > just to confirm, you have a separated physical network for Storage traffic, right ? > > Yes. I have the following Traffic Types: > > Management on `cloudbr0` Guest and Public on `cloudbr1` Storage on `strgbr0` Yes storage and guest network are seperate. -- 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]
Re: [I] Agent 4.21.0.0 secondarystoragevm [cloudstack]
amitmvyas commented on issue #11552: URL: https://github.com/apache/cloudstack/issues/11552#issuecomment-3250522839 In my case, yes it's a different physical nic -- 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]
Re: [I] Agent 4.21.0.0 secondarystoragevm [cloudstack]
daviftorres commented on issue #11552: URL: https://github.com/apache/cloudstack/issues/11552#issuecomment-3250706617 @sjanssen15, feel free to ping me whenever you need tests. l will do my best to fuzz them. -- 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]
Re: [I] Agent 4.21.0.0 secondarystoragevm [cloudstack]
shwstppr commented on issue #11552: URL: https://github.com/apache/cloudstack/issues/11552#issuecomment-3250671946 @sjanssen15 I think 4.21 would work fine if you don't have a separate physical network defined for storage traffic type or if the separate physical network for storage uses VLAN I wish more people had tested one of the 5 RCs -- 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]
Re: [I] Agent 4.21.0.0 secondarystoragevm [cloudstack]
sjanssen15 commented on issue #11552: URL: https://github.com/apache/cloudstack/issues/11552#issuecomment-3250586504 What does this imply right now? That 4.21 is not usable as of right now (clean install) or only in certain scenarios? -- 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]
Re: [I] Agent 4.21.0.0 secondarystoragevm [cloudstack]
sjanssen15 commented on issue #11552: URL: https://github.com/apache/cloudstack/issues/11552#issuecomment-3250678690 > @sjanssen15 I think 4.21 would work fine if you don't have a separate physical network defined for storage traffic type or if the separate physical network for storage uses VLAN > > I wish more people had tested one of the 5 RCs Well, our new environment will have both. Will see if I can test this soon (single nic and separate nics install) -- 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]
Re: [I] Agent 4.21.0.0 secondarystoragevm [cloudstack]
weizhouapache commented on issue #11552: URL: https://github.com/apache/cloudstack/issues/11552#issuecomment-3250550757 > I got this same error after upgrading 3 different non-prod environments. I even nuked a couple and installed 421 from scratch (no upgrade) and the issue remains. > Thanks @amitmvyas @daviftorres I think #11557 addresses the issue. Thanks @shwstppr raising the PR. -- 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]
Re: [I] Agent 4.21.0.0 secondarystoragevm [cloudstack]
daviftorres commented on issue #11552: URL: https://github.com/apache/cloudstack/issues/11552#issuecomment-3250534982 > [@jonathaanbastin](https://github.com/jonathaanbastin) [@amitmvyas](https://github.com/amitmvyas) [@daviftorres](https://github.com/daviftorres) > > just to confirm, you have a separated physical network for Storage traffic, right ? Yes. I have the following Traffic Types: Management on `cloudbr0` Guest and Public on `cloudbr1` Storage on `strgbr0` -- 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]
Re: [I] Agent 4.21.0.0 secondarystoragevm [cloudstack]
amitmvyas commented on issue #11552: URL: https://github.com/apache/cloudstack/issues/11552#issuecomment-3250530149 > > Hi, > > > > I have done the fresh installation of Management Server 4.21.0 version on Ubuntu 24.04, CS agent is also 4.21.0 on Ubuntu 24.04. SSVM doesn't comes up. If I downgrade the CS agent version to 4.20.0.1 then SSVM comes up, however GPU shows in Error state instead of free. Once I upgrade the CS agent on host to 4.21.0 then GPU shows as free. But CSProxy and SSVM is still showing 4.20.0.1 version. > > @amitmvyas > you need to stop/start or destroy or patch the system vms I will give a try for this method but, I am pretty much sure that something is wrong with agent version 4.21.0 for SSVM which is causing the issue. -- 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]
Re: [I] Agent 4.21.0.0 secondarystoragevm [cloudstack]
weizhouapache commented on issue #11552: URL: https://github.com/apache/cloudstack/issues/11552#issuecomment-3250518171 @jonathaanbastin @amitmvyas @daviftorres just to confirm, you have a separated physical network for Storage traffic, right ? -- 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]
Re: [I] Agent 4.21.0.0 secondarystoragevm [cloudstack]
daviftorres commented on issue #11552:
URL: https://github.com/apache/cloudstack/issues/11552#issuecomment-3250303707
I got this same error after upgrading 3 different non-prod environments. I
even nuked a couple and installed 421 from scratch (no upgrade) and the issue
remains.
```
2025-09-03 14:24:37,591 DEBUG [cloud.agent.Agent]
(AgentRequest-Handler-5:[]) (logid:9b1fb285) Processing command:
com.cloud.agent.api.StartCommand
2025-09-03 14:24:37,591 DEBUG [kvm.resource.LibvirtComputingResource]
(AgentRequest-Handler-5:[]) (logid:9b1fb285) Creating VM from specifications
[VM {id: "3", name: "s-3-VM", uuid: "aef0e83b-f8a6-46b5-a77d-85e36c17f2f7",
type: "SecondaryStorageVm"}]
2025-09-03 14:24:37,591 DEBUG [kvm.resource.LibvirtComputingResource]
(AgentRequest-Handler-5:[]) (logid:9b1fb285) Configuring VM with UUID
[aef0e83b-f8a6-46b5-a77d-85e36c17f2f7].
2025-09-03 14:24:37,592 DEBUG [agent.properties.AgentPropertiesFileHandler]
(AgentRequest-Handler-5:[]) (logid:9b1fb285) Property
[vm.memballoon.stats.period] was altered. Now using the value [5].
2025-09-03 14:24:37,592 WARN [kvm.resource.LibvirtComputingResource]
(AgentRequest-Handler-5:[]) (logid:9b1fb285) Setting System VM's [VM {id: "3",
name: "s-3-VM", uuid: "aef0e83b-f8a6-46b5-a77d-85e36c17f2f7", type:
"SecondaryStorageVm"}] current memory as max memory [524288].
2025-09-03 14:24:37,592 DEBUG [kvm.resource.LibvirtComputingResource]
(AgentRequest-Handler-5:[]) (logid:9b1fb285) This host utilizes cgroupv2 (as
the max shares value is [104000]), thus, the VM requested shares of [500] will
be converted to consider the host limits; the new CPU shares value is [49].
2025-09-03 14:24:37,592 DEBUG [agent.properties.AgentPropertiesFileHandler]
(AgentRequest-Handler-5:[]) (logid:9b1fb285) Property [hypervisor.uri] has
empty or null value. Using default value [null].
2025-09-03 14:24:37,592 DEBUG [kvm.resource.LibvirtConnection]
(AgentRequest-Handler-5:[]) (logid:9b1fb285) Looking for libvirtd connection
at: qemu:///system
2025-09-03 14:24:37,593 INFO [kvm.storage.LibvirtStorageAdaptor]
(AgentRequest-Handler-5:[]) (logid:9b1fb285) Trying to fetch storage pool
3c8a09fe-56cb-3263-bf8e-0abcbbd5cf85 from libvirt
2025-09-03 14:24:37,593 DEBUG [kvm.resource.LibvirtConnection]
(AgentRequest-Handler-5:[]) (logid:9b1fb285) Looking for libvirtd connection
at: qemu:///system
2025-09-03 14:24:37,598 DEBUG [kvm.storage.LibvirtStorageAdaptor]
(AgentRequest-Handler-5:[]) (logid:9b1fb285) Successfully refreshed pool
3c8a09fe-56cb-3263-bf8e-0abcbbd5cf85 Capacity: (1.4292 TB) 1571370827776 Used:
(431.42 GB) 463237808128 Available: (1.0078 TB) 1108133019648
2025-09-03 14:24:37,602 DEBUG [kvm.resource.LibvirtConnection]
(AgentRequest-Handler-5:[]) (logid:9b1fb285) Looking for libvirtd connection
at: qemu:///system
2025-09-03 14:24:37,603 DEBUG [utils.script.Script]
(AgentRequest-Handler-5:[]) (logid:9b1fb285) Executing command [qemu-img info
-U
/mnt/3c8a09fe-56cb-3263-bf8e-0abcbbd5cf85/84ee5be8-5b28-4f99-b453-afb3fc4f7ae3
].
2025-09-03 14:24:37,611 DEBUG [utils.script.Script]
(AgentRequest-Handler-5:[]) (logid:9b1fb285) Successfully executed process
[13862] for command [qemu-img info -U
/mnt/3c8a09fe-56cb-3263-bf8e-0abcbbd5cf85/84ee5be8-5b28-4f99-b453-afb3fc4f7ae3
].
2025-09-03 14:24:37,611 DEBUG [kvm.resource.LibvirtComputingResource]
(AgentRequest-Handler-5:[]) (logid:9b1fb285) Disk IO driver policy [null]. The
host supports the io_uring policy [true]
2025-09-03 14:24:37,612 INFO [kvm.storage.LibvirtStorageAdaptor]
(AgentRequest-Handler-5:[]) (logid:9b1fb285) Trying to fetch storage pool
3c8a09fe-56cb-3263-bf8e-0abcbbd5cf85 from libvirt
2025-09-03 14:24:37,612 DEBUG [kvm.resource.LibvirtConnection]
(AgentRequest-Handler-5:[]) (logid:9b1fb285) Looking for libvirtd connection
at: qemu:///system
2025-09-03 14:24:37,616 DEBUG [kvm.storage.LibvirtStorageAdaptor]
(AgentRequest-Handler-5:[]) (logid:9b1fb285) Successfully refreshed pool
3c8a09fe-56cb-3263-bf8e-0abcbbd5cf85 Capacity: (1.4292 TB) 1571370827776 Used:
(431.42 GB) 463237808128 Available: (1.0078 TB) 1108133019648
2025-09-03 14:24:37,616 DEBUG [kvm.resource.BridgeVifDriver]
(AgentRequest-Handler-5:[]) (logid:9b1fb285)
nic=[Nic:Control-169.254.27.218-null]
2025-09-03 14:24:37,616 DEBUG [utils.script.Script]
(AgentRequest-Handler-5:[]) (logid:9b1fb285) Executing command [/bin/bash -c ip
route | grep 169.254.0.0/16 ].
2025-09-03 14:24:37,623 DEBUG [utils.script.Script]
(AgentRequest-Handler-5:[]) (logid:9b1fb285) Successfully executed process
[13865] for command [/bin/bash -c ip route | grep 169.254.0.0/16 ].
2025-09-03 14:24:37,623 DEBUG [kvm.resource.BridgeVifDriver]
(AgentRequest-Handler-5:[]) (logid:9b1fb285)
nic=[Nic:Management-10.120.0.218-null]
2025-09-03 14:24:37,623 DEBUG [kvm.resource.BridgeVifDriver]
(AgentRequest-Handler-5:[]) (logid:9b1fb285)
nic=[Nic:Public-10.120.1.222-vlan://
Re: [I] Agent 4.21.0.0 secondarystoragevm [cloudstack]
weizhouapache commented on issue #11552: URL: https://github.com/apache/cloudstack/issues/11552#issuecomment-3248436373 > Hi, > > I have done the fresh installation of Management Server 4.21.0 version on Ubuntu 24.04, CS agent is also 4.21.0 on Ubuntu 24.04. SSVM doesn't comes up. If I downgrade the CS agent version to 4.20.0.1 then SSVM comes up, however GPU shows in Error state instead of free. Once I upgrade the CS agent on host to 4.21.0 then GPU shows as free. But CSProxy and SSVM is still showing 4.20.0.1 version. @amitmvyas you need to stop/start or destroy or patch the system vms -- 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]
Re: [I] Agent 4.21.0.0 secondarystoragevm [cloudstack]
boring-cyborg[bot] commented on issue #11552: URL: https://github.com/apache/cloudstack/issues/11552#issuecomment-3242849666 Thanks for opening your first issue here! Be sure to follow the issue template! -- 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]
Re: [I] Agent 4.21.0.0 secondarystoragevm [cloudstack]
amitmvyas commented on issue #11552: URL: https://github.com/apache/cloudstack/issues/11552#issuecomment-3247447589 Hi, I have done the fresh installation of Management Server 4.21.0 version on Ubuntu 24.04, CS agent is also 4.21.0 on Ubuntu 24.04. SSVM doesn't comes up. If I downgrade the CS agent version to 4.20.0.1 then SSVM comes up, however GPU shows in Error state instead of free. Once I upgrade the CS agent on host to 4.21.0 then GPU shows as free. But CSProxy and SSVM is still showing 4.20.0.1 version. -- 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]
Re: [I] Agent 4.21.0.0 secondarystoragevm [cloudstack]
jonathaanbastin commented on issue #11552: URL: https://github.com/apache/cloudstack/issues/11552#issuecomment-3242871352 I believe this causes an issue with importing from external unmanaged VMware sources as well but still testing to confirm. -- 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]
Re: [I] Agent 4.21.0.0 secondarystoragevm [cloudstack]
jonathaanbastin closed issue #11552: Agent 4.21.0.0 secondarystoragevm URL: https://github.com/apache/cloudstack/issues/11552 -- 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]
