@David Thanks for the report! We're fixing it: https://github.com/vatesfr/xen-orchestra/pull/7031.

pdonias opened this pull request in vatesfr/xen-orchestra

closed fix(xo-server-auth-google): bad argument passed to registerUser2 #7031

@olivierlambert By default, it's 20 minutes. And it's already configurable through xo-server's config by adding:

[xapiOptions]
restartHostTimeout = '40 minutes'

@Tristis-Oris This should be fixed, now. If a pool is disabled or can't be found, you'll get an error message in the logs and the pool will simply be ignored. See https://xen-orchestra.com/blog/xen-orchestra-5-85/#️-netbox.

Hi @bnerickson, thanks for the detailed feedback!

XO Lite is still in its early development phase, which means that most of your suggestions are actually already planned, including VBD management, editing MAC addresses, creating/deleting VMs and snapshots, and more generally everything that can be done through XAPI calls.

Regarding your other suggestions, keep in mind that XO Lite is running without a server behind. This means that the persistency is only in the browser. For instance, I'm not sure how an LDAP login would work, since the credentials you're entering in XO Lite are your host's credentials, and XO Lite needs that to communicate with XAPI.

Regarding XOA's FQDN, you can already do that by configuring the field publicUrl in your XOA's config:

[http]
# Public URL to connect to this XO
#
# This optional entry is used to communicate to external entities (e.g. XO Lite)
# how to connect to this XO.
#
# It SHOULD be defined in case the IP address of the current machine is not
# good enough (e.g. a domain name must be used or there is a reverse proxy).
publicUrl = 'https://xoa.company.lan'

In any case, I took note of your feedback and we'll have to discuss some of your other interesting suggestions, both for XO Lite and XO 6, like showing more of the host's logs, failed services, etc.
Thanks!

@DustinB @olivierlambert I confirm it's not possible at the moment.

@vilhelm That's fixed: https://github.com/vatesfr/xen-orchestra/pull/6328. Thanks again for the report

pdonias opened this pull request in vatesfr/xen-orchestra

closed fix(xo-server/xapi-object-to-xo): handle guest metrics reporting empty IP field #6328

Hi @bnerickson, indeed, the configurations are correctly imported but plugins aren't automatically "configured" when you import a config. We'll improve that, thanks for the report

Hi @theaeon, this should already be fixed, could you check the full log for that error in Settings > Logs? It should give you more details.

Hi! We introduced a bug in commit 59e6868 causing "Page not found"s and fixed it in commit 6e52794.

Yes, we'll have to test the new version before bumping the max supported version.

In the meantime, if anyone wants to test it on a non-sensitive instance of XO, you can disable the version check in xo-server's config:

[netbox]
checkNetboxVersion = false

But I think I'm already seeing something that we'll have to handle:

The site foreign key field on virtualization.Cluster has been replaced by the scope generic foreign key.

@maverick This is for the URL https://fw-dea12.domain.tld/api/extras/custom-fields/1/, right? What about https://fw-dea12.domain.tld/api/extras/custom-fields/?

If that works too, could you run this from the machine that hosts your XO?
Replace <TOKEN> with the token that you put in the Netbox plugin configuration:

curl -skv -H "Content-Type: application/json" -H "Authorization: Token <TOKEN>" "https://fw-dea12.domain.tld/api/extras/custom-fields/"

@maverick What version of the Netbox plugin do you see in the UI? (/#/settings/plugins?s=netbox)

@techjeff Thanks for the report, it should be fixed on master

@jpasher-work Thanks, I'm adding that too!

@sb2014 I may have found the issue. If you want to test it, you can build the branch pierre-fix-addresses.

@sb2014 and @ThasianXi Thanks for the report and investigation
An empty IP shouldn't be an issue but the multiple IP addresses in the same field is probably what's causing the error. However, this should be handled by XO already, so I'm surprised we're still seeing this. What version of XCP-ng/XS are you running @sb2014?

Regarding the custom fields, that's most likely not the issue here because if you don't have the correct custom fields, it will fail at the very beginning with a clear error message. But indeed:

• with the new version of the plugin, you need to assign the uuid custom field to a third object type: Virtualization > interface
• the doc currently says Virtualization > vminterface but you're right, it should say Virtualization > interface instead. I'm fixing that

Thanks for the feedback @fred974 We're aware of this and we're going to add a way to deploy another XOA when one is already deployed and also a way to choose which XOA the button redirects to when there are multiple ones deployed.

Thanks for the feedback, we'll take care of that.

@mjtbrady Yes, there was an issue on our side but it's fixed, now. Thanks for the feedback and let us know if you have other issues

@propsoft All clear now, thanks! We'll discuss it and see what we can do, but I think this is indeed something that you need to configure in your browser. There should be an option to force the browser to ask where to save the file.

Thanks for the feedback @propsoft
XO Lite is indeed still a work in progress and there's a lot to come!

@propsoft said in EOL: XCP-ng Center has come to an end (New Maintainer!):

not being able to specify the target of an export (browser ran out of disk space, unsurprisingly)

I'm not sure to understand what you mean by "browser ran out of disk space". Do you mean your computer's disk?

Also, what do you mean by target? You'd like to be able to choose a destination folder on your computer?

Thanks!