@olivierlambert, yes, thank you. I will open that ticket.

@jkatz hello, thanks for your report. This topic is being studied on our side, we have scheduled a ticket on it in our roadmap. We will keep you informed. Have a good day!

@AtaxyaNetwork It will/it does

@olivierlambert Thanks!

haha we were all noobs when we started, it's fine

removed the failed server connection. Restarted xo-server service. Added new host again. Seems fine now. In hind sight, I could have very well recycled a DHCP ip here as well, if that is a known issue...

Sounds a like a bug to me, we can maybe check what's displayed in there and take a look at xe level to see what's the problem Ping @lsouai-vates

Indeed, you are right and it's about to be fixed very soon. Thanks!

Okay so you deployed XOA, the turnkey VM with XO already installed in it. Are you sure you do not have an IP conflict? Make sure XOA IP is different than the host.

I had the same problem, I had to run the XenClean script and do a fresh install of 9.4.1 which resolved the issue. https://github.com/xcp-ng/win-pv-drivers/releases

Hi, This is perfectly normal. Only the master is the contact point for the entire pool. I would advise to go for manual promotion if you consider your host dead. To do it, go on any slave you want to promote (just one) and type xe pool-emergency-transition-to-master. If you use HA, this will be done automatically, but HA can be tricky. The result will be the same, if the master is down, you'll lose the view in XO about what's going on the pool, until you get a master back.

@olivierlambert Interesting, thanks.

I had a similar issue and found that after changing the static IP directly by editing the network config file inside the XOA VM, things worked fine, but I had to double-check routing afterward. I also ran a quick ip stress test with multiple devices to make sure the new config didn’t cause conflicts or drops on the network. Everything stayed stable after that.

And that's the reason why we planned to keep displaying "out of sync objects" in XO 6

@bleader you have it right. I was checking before I started down the path of writing something myself. We are a public entity that operates very similar to an MSP so we have a ton of VLANs. We're migrating from vCenter/ESXi and have always used powerCLI with powershell to perform these functions.

No no, don't worry, it shouldn't be that frustrating. That's why I want to check what do we have in the pipes in the future to make it easier.

UPDATE, Its FIXED! I downloaded XCP-NG Center and it was able to connect to Xen-1 and I was then able to change xenbr3 to DHCP instead of the static IP that was the same as xenbr0. No idea how a power hit may have caused this but doing that allowed XO to immediately connect. Much appreciate the assistance, I think it would have taken much longer to figure out if I didn't have the support!

@olivierlambert Thanks for the quick fix - update worked fine when I tried again, right after I wrote my post

@DustinB I advise you not to decide for others what they should do. I'm tired.

@BSmithITGuy Thanks for your information. The temporary workaround now is put Xen Orchestra to the same XCP-ng management network. Update 1: Diving deeper, I discovered that the API was changed the host management address (where the VM is located) to the backup address: https://github.com/vatesfr/xen-orchestra/blob/92932dd54645838db58ecfdd872895c5ad461608/packages/xen-api/index.mjs#L1010 async _setHostAddressInUrl(url, host) { ... url.hostname = await this._getHostBackupAddress(host) }