Worth asking @Team-OS-Platform-Release

@tsukraw Your best option is to open a support ticket so that we can assist you on updating the XOA registration.

Nice find! Is there's any plan for Debian to backport that patch?

@florent increasing the timeout value was the solution. Thank you.

@florent said in Problems import vm Vmware to Xcp-ng from import Vmware and OVA: @olivluca skip ssl check in the import form I already did that. In fact it connects and I can get a list of VMs to import.

Does it work as you wanted now? If yes, probably something we can put in our official doc! Ping @thomas-dkmt

Indeed, it's hosted in Lyon, so an issue could happen in many places in the middle ^^

@florent I think you meant it was locking the xoa via .tar.gz but not via .zip which seemed to be the case Yeah I just decompressed the restored .zip and checked number of files and size via ncdu, result: "Total disk usage: 194,5 MiB Apparent size: 193,1 MiB Items: 613" In case I can provide more information for investigating this issue, please let me know. Thanks and best regards

@mpiton thanks for sharing docs, the crucial part was openssl rand -hex 32 my password was too simple and that's why i got :"Query authentication does not match server setting" error after setting 32 characters password i got my metrics, in both http://localhost:9004/metrics and http://<xo-ip>/openmetrics/metrics

I don't think stop will remove it, probably better to yum remove it. For Openmetrics, check: https://docs.xen-orchestra.com/advanced#openmetrics--prometheus-integration I switched our own production to that, so far it looks promising.

@florent I'll send you a link in DM, hope it helps with something. If not, it wasn't too much of an effort, thanks for your time so far

@anthoineb have we found a possible explanation?

I recreate my ZFS pool. But next time or for other stuck with this kind of issue, I think you should start to rename your ZFS POOL. I think the old ZPOOL name stay in XO configuration shadow settings. To rename a ZFS pool, export it with zpool export [poolname] and then import it with the new name using zpool import [poolname] [newpoolname] And then recreate (sr-create) your STORAGE in XO

@ronan-a Thanks

Hi @jacob.becker, We identified the issue last weekend, and we're currently working on a solution. We plan to include a fix in the next XO release.

@olivierlambert Because Andriy did quite a bit of work before this merge, xcp-ng depends on xenserver releasing the package to the clients before we can integrate it into xcp-ng. I'd say we can release the package February at the earliest

@myles3 Hello Myles3. This post is over 20 days old. The issue was since been resolved by support. I dont remember the exact solution off the top of my head with out looking it up.

@Bastien-Nollet many thanks