Re: libvirt.vif.driver ignored in ACS 4.16

Hi Felipe, Did you restart the agent after updating the `agent.properties` file? I've set this on my lab with the values you have shared, and it gets the correct Vif driver. Best regards, Slavka On Thu, Apr 28, 2022 at 1:28 AM Felipe Polanco wrote: > Hi, > > We are trying to setup Open

libvirt.vif.driver ignored in ACS 4.16

Hi, We are trying to setup Open Vswitch in ACS 4.16 and we have added the following lines to the agent config file and manually created the bridges in OVS: network.bridge.type=openvswitch libvirt.vif.driver=com.cloud.hypervisor.kvm.resource.OvsVifDriver # ovs-vsctl show

SV: Request Failed (530) - Cannot delete pool Primary as there are associated non-destroyed vols for this pool

Hi Pearl Spot on!!  There was two volumes for old deleted virtual routers hanging in there... I have successfully deleted Primary storage now. Thank you  Med vennlig hilsen David Larsen Senior systemkonsulent ADCOM MOLDE, IT Data AS Fabrikkvegen 13 | 6415 Molde

Re: Múltiple Usage Service

I am not dead sure as in I haven't seen the code but in my understanding... ACS will take care of job level data integrity. You can run multiple usage services. Moreover there are fields in the usage db's multiple event tables which mark events as processed making it idempotent. Regards Shiv On

Múltiple Usage Service

Hi, Is it possible to have as many usage services as Management servers running, or for consistency sake only one usage service is allowed? Regards, Ricardo Pertuz

Re: No longer able to see any "Snapshots"

Hi Antoine, The NPE error seems to be due to the primary storage with id '5', when checking for snapshot revertible or not during list snapshots cmd. Is that primary storage removed? Can you check with sql below. SELECT name, uuid, pool_type, scope, created, removed FROM cloud.storage_pool

Re: Request Failed (530) - Cannot delete pool Primary as there are associated non-destroyed vols for this pool

Hi David, The error message indicates that there are some volumes on the primary store that you are attempting to remove in the database. You can validate it by using: select * from volumes where pool_id = and removed is null; If you have validated that the volumes returned by the above query

Request Failed (530) - Cannot delete pool Primary as there are associated non-destroyed vols for this pool

Hi We are replacing our old datastore with a newer and faster storage. I have successfully created new volumes and successfully migrated every instance/volum, systemVM’s and Virtual routers to new volumes. We have five volumes on the old storage system and five on the new storage system (vmware