🛰️ XO 6: dedicated thread for all your feedback!
-
@olivierlambert nice, better than megathreads !
added my first TAG demand on it -
Hi,
Just pulled the last commit and see that v6 become the "default" endpoint.
Unfortunatly, I have to rollback, any user can connect, SSO (oidc) is broken, I think it's not fully implemented yet ?
callback URL give a "Internal Server Error"; adding "/v5" make a loop with login screen...
There is any trick to diable v6 by default ? Or make OIDC works ?
Thank you and have a good day
-
@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
