@gduperrey said in XCP-ng 8.3 updates announcements and testing:
Since it doesn't indicate that an updated 8.2 is actually 8.2.1, only the major version is displayed.
Not a very good example actually (but what's true is that for 8.2 we didn't add a "LTS" mention next to the version number in the system either).
[image: 1750243409436-37210535-b72a-49e3-aeb0-ad59cbbdd82e-image.png]
But yes, we decided not to increment the version number for XCP-ng 8.3.0. That breaks compatibility with some third party software because they wouldn't recognize a "8.3.1".
However we're working on a secondary version identifier that would allow you to know your precise patch level.
Hmm, interesting observation about potentially this being a failed migration issue.
I can confirm that none of my users in the lab are migrating any VMs or this particular one, for that matter. However, I do have the Load Balancer plugin running and it could be the source of a migration that could've failed. How can I confirm this in the logs? I mean, what should I be looking for?
