Hello Antoine, I saw that this time my yum update upgraded me to 8.2.1 You were in 8.2.1 too ?
I tried this fix in ACS : #add hypervsisor xcp 8.2.1 to acs 4.16 INSERT IGNORE INTO `cloud`.`hypervisor_capabilities`(uuid, hypervisor_type, hypervisor_version, max_guests_limit, max_data_volumes_limit, max_hosts_per_cluster, storage_motion_supported) values (UUID(), 'XenServer', '8.2.1', 1000, 253, 64, 1); +-- Copy XenServer 8.2.0 hypervisor guest OS mappings to XenServer 8.2.1 +INSERT IGNORE INTO `cloud`.`guest_os_hypervisor` (uuid,hypervisor_type, hypervisor_version, guest_os_name, guest_os_id, created, is_user_defined) SELECT UUID(),'Xenserver', '8.2.1', guest_os_name, guest_os_id, utc_timestamp(), 0 FROM `cloud`.`guest_os_hypervisor` WHERE hypervisor_type='Xenserver' AND hypervisor_version='8.2.0'; Theses are the fix used to add xcp-ng 8.2.0 to ACS 4.15 Here i adapted the fix to copy guest os mapping from xcp-ng 8.2.0 capabilities I tried to reboot and this is not working on another Cloudstack mgmt instance with xcp-ng 8.2 freshly patched to 8.2.1 with yum update Regards, Benoit Le lun. 2 mai 2022 à 19:46, Antoine Boucher <[email protected]> a écrit : > Bonjour Benoit, > > I had similar issues after I did a yum update and I was only able to fitx > the issue by rebooting my hosts. > > -Antoine > > > On May 2, 2022, at 12:04 PM, benoit lair <[email protected]> wrote: > > > > Hello all, > > > > This is surely due to my yum update which updated to xcp 8.2.1 > > > > Do anybody know how to fix this ? xcp 8.2.1 is compatible ? would it be > > possible to add hypervisor capabilities without doing it in beta mode ? > > > > Le lun. 2 mai 2022 à 16:15, benoit lair <[email protected]> a écrit > : > > > >> Hello folks, > >> > >> I have a several issue > >> I try to live migrate my storage vm disks on a xcp-ng 8.2 cluster and i > >> cant live migrate > >> When clicking on the "Migrate volume" button, i have the following > message > >> : > >> > >> No primary storage pools available for migration > >> > >> and it generates this in logs : "the hypervisor doesn't support storage > >> motion." > >> > >> 2022-05-02 15:52:33,120 DEBUG [c.c.a.ApiServlet] > >> (qtp1850777594-186961:ctx-2ee90dcf) (logid:1b094155) ===START=== > >> 192.168.4.30 -- GET > >> > id=b8d15b4c-93e9-4931-81ab-26a47ada32d5&command=findStoragePoolsForMigration&response=json > >> 2022-05-02 15:52:33,136 DEBUG [c.c.a.ApiServer] > >> (qtp1850777594-186961:ctx-2ee90dcf ctx-d6c062ae) (logid:1b094155) CIDRs > >> from which account 'Acct[a6441eae-68b8-11ec-acb6-96264736f9a1-admin] -- > >> Account {"id": 2, "name": "admin", "uuid": > >> "a6441eae-68b8-11ec-acb6-96264736f9a1"}' is allowed to perform API > calls: > >> 0.0.0.0/0,::/0 > >> 2022-05-02 15:52:33,151 INFO [c.c.s.ManagementServerImpl] > >> (qtp1850777594-186961:ctx-2ee90dcf ctx-d6c062ae) (logid:1b094155) Volume > >> Vol[320|vm=191|DATADISK] is attached to any running vm. Looking for > storage > >> pools in the cluster to which this volumes can be migrated. > >> 2022-05-02 15:52:33,157 ERROR [c.c.s.ManagementServerImpl] > >> (qtp1850777594-186961:ctx-2ee90dcf ctx-d6c062ae) (logid:1b094155) > >> Capabilities for host Host {"id": "2", "name": "xcp-cluster1-node2", > >> "uuid": "ae51578b-928c-4d25-9164-3bd7ca0afed4", "type"="Routing"} > couldn't > >> be retrieved. > >> 2022-05-02 15:52:33,157 INFO [c.c.s.ManagementServerImpl] > >> (qtp1850777594-186961:ctx-2ee90dcf ctx-d6c062ae) (logid:1b094155) Volume > >> Vol[320|vm=191|DATADISK] is attached to a running vm and the hypervisor > >> doesn't support storage motion. > >> 2022-05-02 15:52:33,164 DEBUG [c.c.a.ApiServlet] > >> (qtp1850777594-186961:ctx-2ee90dcf ctx-d6c062ae) (logid:1b094155) > ===END=== > >> 192.168.4.30 -- GET > >> > id=b8d15b4c-93e9-4931-81ab-26a47ada32d5&command=findStoragePoolsForMigration&response=json > >> > >
