🛰️ XO 6: dedicated thread for all your feedback!
-
@Kptainflintt Please provide us the XO-server log that concerns the connection error, authentication is supposed to work as before.
-
Hi,
That's the wired thing, no error in logs...
But I found why : I have "profile" scope in my OIDC configuration for a while, it seems to broke SSO in last version. Without it, it works.
Thank you
-
Subject: XO 6 is unusable without Migration tools
I just updated and was presented with the XO 6 interface. I am shocked to find that the "Migrate" functionality is missing from the UI.
Moving a VM is the most fundamental feature of a hypervisor management tool. Making an interface the default—or even presenting it as a viable preview—without this feature is a major workflow breaker. I shouldn't have to revert to the CLI or hunt for a "legacy view" toggle just to perform basic maintenance.
Please prioritize porting the migration/lifecycle actions before pushing users toward this interface. It makes the product feel broken.
-
Have you read the release announcement? You can upvote your most important features at https://feedback.vates.tech
-
@olivierlambert i voted. thanks
-
Just did my RPU and checked on the new v6 interface.
The old one has task details that are missing on the new one (or I didn't find them:
I like to see the evacuation tasks happening (in the past I could identify hangs etc)
Here instead of the ID of the VM host the real names should be shown:
-
As shown above the evacuation tasks are not shown.
The last steps migrating thre VM's to the original place are shown:
-
Also here the task progression can't be followed (stays at 0% until completed):
instead of
-
I can't seem to find User settings to change admin name/password or configure filters. and they are not in the obvious place - account settings in top right corner.
-
Trying not to be negative, but I hate having to jump back to v5 to get things done.
-
@Greg_E This is only until we get more features directly into XO 6. Our goal was th get feedback ASAP without waiting again for months and something entirely finished (to finally realize it's not the right way and lose another year).
If you don't want to test XO 6 and report what's missing first for you, you can configure your instance to be on XO 5 by default and switch later
-
The odd part is that I'm happy with XO Lite, so not sure why 6 is causing me problems other than needing g to jump back to 5. I only have one XO new enough to be updated, I guess I need to update my lab since I'm in it a lot lately and come up with more productive comments for the team. The switch just immediately shocked me in a way that it shouldn't have done being that I've been using Lite to try and get ready.
-
That's also because XO Lite is replacing basically "nothing before", while XO 5 is 10y full of features that we can't all re-implement at once in XO 6
