XO Team group | XCP-ng and XO forum

julienXOvates

@acomav We will actually propose to change the date and time format in XO6 settings, so you would be able to choose between :

YYYY-MM-DD
MM/DD/YYYY
DD/MM/YYYY
and 12h or 24h time format.
Hopefully in one of the next 3 months !
I hope that will answer your need, otherwise let me know !

mpiton

@tmk Confirmed bug on our side; thanks for the report.

The plugin declared its secret with a random default in the config schema. That expression runs when the module is imported, so every xo-server process computes a different one, and xo-server never writes back the values ajv fills in from schema defaults. So if you copied the secret out of the plugin form without saving the configuration, scraping worked until the next restart, and Prometheus started getting 401s.

Fix is here: https://github.com/vatesfr/xen-orchestra/pull/10290. The random default is gone. The secret is generated once on the first load and saved through the plugin configuration, so it survives a restart. If you already have one saved, it's left alone.

Once it's merged it'll be on master for people building from sources, and it'll reach XOA in the next release.

pierrebrunet

@pedro_udifar Hi,
Do you still have errors 500 when you are talking about general errors?

pierrebrunet

@JB @majorp93 We made a smaller PR to be merged just after the release (because it is linked to almost all XAPI calls), the new branch is this one if you want to test: fix_undici_timeout
Same fix, just a little smaller

pierrebrunet

@gsszuber Hi,
Yes indeed, you need to preserve the root of the bucket from Lifecycle. We just had a customer with a similar issue.
Can you help us by giving a small screenshot of the field to filter out the root (or filter in the three folders) please?

pierrebrunet

@bogikornel are you talking about another issue? We are on an issue specifically on "pool metadata backups". It seems you are talking about VM backups. If yes, can you send the backup log please?

pierrebrunet

@acebmxer ok, too bad... I thought we had it...
@majorp93 this can be a lead. I will ask xapi team if they changed something in pool metadata export.

pierrebrunet

@MajorP93 Hi,
Thank you, thank you! I think you found it! It seems to be SMB, @acebmxer can you confirm that you also use smb please?
If this is the case, the bad news is I think we will need to update our docs to not advise SMB at all: it was already said for delta but maybe we will have to extend this to all kind of BR

florent

@JB this really looks like a network issue

are the host/xoa remotes ?

julienXOvates

@oliv77 said:

Hi,

XOA version:
xo-server 5.193.1
xo-web-premium 5.191.0

We've noticed on our production XOA server that when we put an XCPNG host in a pool into maintenance mode, we reboot it and then it reconnects to its pool but is no longer in maintenance mode.
Is it possible to configure the XCPNG hosts so that they automatically return to maintenance mode after a reboot?

Regards,

Oliv77

Hi @oliv77, XO 6.7 - latest - adds this option in REST API and next month we should have the available action (Disable host and evacuate VM) in XO6 !

XO Team

Posts

Member List