BUG metadata restore list infinite loading ? (edit : perhaps not a bug, just a glitch)

[Pilow]

as this job was done with a XOA proxy, i tested it WITHOUT the proxy... and the restore points are back...

but when i put again the proxy in the job configuration, they stay there, as usual... all is OK now...

I don't know what happened...
to note : I manually launched the backup to test with & without proxies, I don't know if there is a different behavior than the usual : executed by sequence.

[Pilow]

i'll let tomorrow sequence execute, and report back if the metadata restore points are unaivailable again.

[acebmxer]

@Pilow While i havent had that issue that i am aware of. I have noticed that the backup restore points for the proxy specifically are slow to load. Even when deleting large quantities of backups to the point it stops reporting to XOA until some time of processing.

[Pilow]

@acebmxer yeah I know... sometimes I have to REFRESH BACKUP LIST for normal backups of VMs, but this button doesn't even exists for metadata

[Pilow]

@acebmxer do you have AUDIT LOGS activated ?

if so, could you check on your XOA if you have the same from-earth-to-moon audit log on metadata backup list ?

why do I have quite a full log of all my infrastructure information in this log ?
this one is a bug I guess

perhaps is it linked to the infinite refresh I had ?

EDIT : saved the log on the desktop in notepad ... 1.528 Mo !

[acebmxer]

@Pilow Yes i do have Audit logs enabled but i do not have any metadatabackup.list.... Maybe a setting in backup job?

While my production XOA environment did not my home lab does...

[Pilow]

@acebmxer you need to go in backup/restore/metadata

it will try to list your metadata backups by an api call

then go back to audit you will see the audit log

mine is gigantic.

[acebmxer]

@Pilow
Yeah still dont know why i dont see it in my production envorioment but yes the most recent file from home lab is 5k lines saved as txt file only 756KB in size. Yes i see alot off information in that file.

Production has no backup job for pool metadata / config. I assumed that backup to vates would be the same? But since they are not stored locally that would be why?

[Pilow]

@acebmxer xoconfig goes to vates but not pool metadata
doesn't cost anything to put a job on it I guess

so we wait for Vates team to tell us why this vebose audit log on metadata

or perhaps it IS the metadata that would explain the fuss

[olivierlambert]

Adding @florent and/or @Bastien-Nollet in the loop