XenOrchestra not showing VM Disks on Pool (on single Server working) - XCP-ng Center is showing them

AlexD2006

Hi @all,

i noticed a strange behaviour in one environment with one pool (2 Hosts and NFS Storage) and 2 single node xcp-ng servers.
XenOrchestra from sources, connected directly to the pool and the 2 Servers.

When i open a VM in XenOrchestra, resident on an a single node, i see the VM Disks in xo and similar in XCP-ng Center.
When i open a VM in the same XenOrchestra resident on the pool (no matter if disks are on nfs shared storage or local storage of a Host), i dont see the disks in XenOrchestra (looks like no disks attached).
But in XCP-ng Center the disks are there and the VMs are running fine.

I did a full update today of XenOrchestra to actual commit and also upgraded the pool today (rebootet master first, then slave).
But the issue is still the same.

Is there anyone who has the same issue?

Screenshots of one of the VMs on the Pool:

in XenOrchestra

in XCP-ng Center

olivierlambert

Ping @anthoineb because it might be related to an XCP-ng bug

Pilow

@AlexD2006 could you check directly in the disks tab of the SR if all VDIs have a snapshot icon on them ?

AlexD2006

@Pilow
Indeed.
Thats exactly the Point.

All my VMs that ran into my nightly Backups, have this.
To test it i created a new VM that didnt get a snapshop yet.
In the new VM i see the Disks.

Pilow

@AlexD2006 this is a current bug, not solved yet

you could try that on one VM : snapshot it, revert to snapshot (VDIs will re appear in the disk tab of the VM), then delete snapshot.
rince & repeat for each VM...

problem of disappearing VDIs could come again.

There is no harm to the VMs, in XO6 you should see the VDIs are there (like in XCPNG Center).
xo-cli calls also work normal.

Pilow

@AlexD2006 see here, we're in the same boat
https://xcp-ng.org/forum/topic/11715/vdi-not-showing-in-xo-5-from-source.

AlexD2006

@Pilow

Thanks for your Reply.
Just one little correction.
Also in XO6, the Disks are missing in the VM-VDI Tab.
Its exactly the same in XO5 and XO6.
Only in XCP-ng Center i see the Disks.

I noticed an additional thing.
In the Health-Dashboard, i see one orphaned "base copy" for each Disk that is adressed by this behaviour.

Exactly the amount of Disks of all my VMs with this problem.
(in the screenshot only the two of the VM of the former screenshots)
I am shure there are no orphaned VDIs, its just the base-copies of all my active Disks.

I think this could be possibly extremely dangerous, if someone has the same problem and removes the orphanes at this point.

But maybe i am too paranoid here?

acebmxer

@AlexD2006

Yes while this can be a scarry situation there have been multiple post about his. @pilow has been dealing with it the longs I believe.

Some have tried @pilow suggestion and have been good since. I would see if you can create test vm or copy one of the existing ones to try with braking a production vm.

Pilow

@AlexD2006 you are right, this is dangerous.
I also have them old & dusty base copies from the seventies

do not shoot them.

Pilow

if you have other SRs, migrating VDIs/VMs is known to correct the "visual issue"

the bug just populates a metadata of the VDI making XOA Web UI believe it's a snapshot, and it is not...

a dev told us in another thread they are on it, but it will be a two phase remediation I believe, correcting the bug so that it doesn't reproduce and a way to script out this metadata on impacted VDIs

this is only guesses

AlexD2006

@Pilow
@acebmxer

Thanx for your replies.
And sorry, i havent seen your first reply between my last posts with the link to your existing Thread.

So, i think this is some kind of a bigger thing.
Will handle with care, but i have to leave for today.
Maybe i have time to test the snapshot and revert workarounds on the weekend.
But these are all production VMs.
Have to coordinate.
I have 2 NFS-SRs in the Pool.
Will try to migrate VMs from one to the other and see if this helps.

Kind Regards and thx again
Alex