Faulty XCP-ng host after update (but only on XO)

olivierlambert

Have you refreshed your UI?

Affonso

@olivierlambert

I cleared the browser cache and when it didn't solve I tried using a private tab.
The error persists.

Or is refresh the UI another thing entirely?

olivierlambert

That's weird indeed. Are you sure you are upgrading/restarting the right XO? Have you tried with XOA?

Affonso

@olivierlambert

I am sure yes. Quite easy even when I reboot the XO vm I lose access to Xen Orchestra on the browser until the reboot is complete, so no questions there.

I launched a XOA VM and it shows correctly there so I assume its not from the hosts but the XO itself. What can I do to clear this?

olivierlambert

It's hard to tell. Maybe remove/re-install your XO from the sources?

Affonso

@olivierlambert but could you tell if there is some caching or what could be doing this? If I could just remove temp files and clear local application cache and check again would rather than removing the whole XO and rebuilding, just for a faster solution. rebuilding is also doable.

olivierlambert

Frankly, I never saw this behavior, so I can't tell. Objects aren't stored in a cache, it's all in memory, so it's really weird. What is your NodeJS version used?

Affonso

@olivierlambert

# node --version
v18.18.2

olivierlambert

I suppose you disconnected/reconnected the server in settings/servers?

Affonso

@olivierlambert well the XO instance is connected to the Master, it's not the master node showing this problem.
As when I rebooted the XO already assumed it was "disconnecting" and "connecting", but I am going to do it manually.

I have:

Rebooted the XO VM
Rebooted the XCP node
Rebooted the XCP master

none produced any different result.

Affonso

Now I just did as you suggested went to Settings > Severs
Disabled the master, counted to 10, enabled the master.

Problem persists. (for a moment I thought it was gone but then I realised I was looking to XOA not XO).

olivierlambert

You only need to connect to the master, there's no direct connection to other hosts needed. You should only have the master server listed in there, is it the case, right?

Affonso

@olivierlambert Yes only one server listed

Affonso

Well since there is no issue when looking at XOA but only on XO, I am going to disregard this issue and wait to see if it resolves by itself until the weekend and if not I'll try and remove this XO build and make a new one.

Thank you for your suggestions, I'll try and let know how it went.

Andrew

@olivierlambert It happens to me too now on XO Source (commit 039d5)... seems to be showing memory usage of ALL VMs in the graph, including guests NOT running. ONLY when you have a single host/pool. The actual memory calculation below the graph looks correct.

Danp

@Andrew Same here.

Andrew

@olivierlambert @Danp @julien-f
Problem cause by XO commit 1718649e0c6e18fd01b6cb3fb3c6f740214decc4

julien-f

Thank you everyone, I'm investigating.

olivierlambert

Probably because we used $container in this view before, and it was only the host when the VM was running. Since we changed the logic, it broke that view.

julien-f

It should be fixed, let me know if there are any other issues

https://github.com/vatesfr/xen-orchestra/commit/9e5541703b25f6533cd94bdd786a716b6f739615

0

julien-f committed to vatesfr/xen-orchestra

fix(xo-web/host): only count memory of running VMs

Introduced by 1718649e0

FIxes https://xcp-ng.org/forum/post/71886