@borzel said in [WARNING] XCP-ng Center shows wrong CITRIX updates for XCP-ng Servers - DO NOT APPLY - Fix released:
XCP-ng Center
Pretty please do not abandon XCP-ng Center! There are BASIC things XCP-ng Center does that XOA free does not. For example, cloning a VM cannot be done with free XOA.
I will also repeat, THANK YOU to you and your team for your work. It pains me to read posts questioning your reasons to charge A,B,C for X,Y,Z, and I am on your camp. You need to make it viable... Hence my apprehension to use XO from sources.
I am learning so much... thank you.
The issue probably here, the flags:
uuid ( RO) : 13a6127c-59ab-1da2-1f2c-50fae29b5775
name-label ( RW): Snap with Center
name-description ( RW):
user-version ( RW): 1
is-a-template ( RW): true
is-default-template ( RW): false
is-a-snapshot ( RO): true
uuid ( RO) : 05847d68-ae1f-c06b-c05f-aeff2ca5c6fe
name-label ( RW): Snap with XOA
name-description ( RW): Had to change to HVM and remove "console=hvc0" from kernel line
user-version ( RW): 1
is-a-template ( RW): false
is-default-template ( RW): false
is-a-snapshot ( RO): true
I understand they will have to pull the plug on xcp-ng Center at some point and I will have build XO from sources. I do hope XO's views improve and work better, because they can be quite frustrating now. Its the nature of a web interface, and I understand there are challenges there, but if there is no choice but to use XO then the challenge is even greater.
However, I say XO(A) is a fantastic product and I have tried to make the math work for us and pay for it. I still can't swing it, partly because you need Enterprise Edition to make a simple clone.
I am exceedingly grateful any of this exists at all, and I thank everyone who have made it possible!!!
I appreciate you trying to educate me. However, we're going in circles... Its ok, I get it. The end result is:
No, I get that... and thats the silly part. All XO needs to do is set the flag, and it has been clear from the moment you had me print the objects.
It is super clear to me... the XO Snapshot is different than the Center Snapshot, only because of a single flag that XO is not setting to be true.
That difference, is enough to make them behave differently. They are not the same, no matter how tiny that difference may be.
I am using XCP-ng because I believe in your vision as opposed to your competitors. There are other options, and yet I like what you've done with XO/A and XCP-ng. And that's why I am writing here, whereas I have never participated in a feature/bug discussion with Citrix.
If earn a Euro in France, I expect that Euro to behave the same anywhere else that Euro's are accepted. I didn't earn a French Euro, only valid in places that accept French Euros.
The snapshot I created in XO, is my earned Euro. Except that I didn't realize it was an XO Snapshot, different from a Center snapshot. Why that is I leave to you, but it is undeniable that they are not created equal, be it a dumb concept or not.
Still, there is no need to continue this, as the facts are already in the thread, from both perspectives. I was just trying to help, and I am learning more than I ever expected.
It is doing that because upstream does that.
A true snapshot allows me to create a VM from it. It has done so in XenCenter for as long as I can remember, and XCP-ng Center has continued that.
And yes, this makes me very weary of using XO, and that I will not have a choice in the future but XO.
But, I will leave now and you can decide how much it is ok to diverge from upstream.
Because they are not true snapshots, as they have been defined in Center. They do not behave the same, then they are not the same. Yet they are both snapshots... What else is called the same in XO and Center but are actually not the same?
I understand your point, but my point is just as valid: I have just learned, for example, I cannot trust XO snapshots. And what problems might I encounter with VMs created in XO today, when I try to manage them in Center, months from now?
Your response worries me. How many other features in Center, replicated in XO, are actually not the same feature? As a user, I trust that a snapshot in *Center or XO behave identically across both. They are both supposed to be using the same API. Why are they different? Over time, it would lead to distrust of XO.
I have just learned, for example, I cannot trust XO snapshots. And what problems might I encounter with VMs created in XO today, when I try to manage them in Center, months from now?
Said another way, if XO's snapshots are generated identically to Center's snapshots, then the flag is the only difference. The flag would be the only fix needed.
I would surmise, that since Center is behaving as it has for as long as I can remember, the fix should be applied to XO.
XO should set the template flag on a snapshot, so XenCenter and XCP-ng Center both behave as expected. The two flags I imagine are used by XenCenter and XCP-ng to build lists in the relevant dialogs that require ONLY templates, or templates and snapshots of a given VM. In this case, the dialog looks to show is-a-template (true) and is-a-snap-shot (true) and is it for the selected VM.
That said, I don't know enough about the implications. It may just be a flag, or there is something much deeper going on.
Said another way, if XO's snapshots are generated identically to Center's snapshots, then the flag is the only difference. The flag would be the only fix needed.
Also worth noting is that Center isn't adding the name-description string, whereas XOA is.
No... XOA is defaulting to the name-description (as expected.) and Center is asking for one, and I left it blank... No issue here.