Hi @acebmxer the bug related to the ISO will be fixed soon (probably tomorrow on the master branch).
@gheppy Same for the CPU provisioning bug.

@ElFritto Can you try this branch xo6/update-site-dashboard and check if that solve your issue?

Perfect, thanks.
We will fix the infinite loader for backups info soon

I don't understand what's happening.
Could you try installing directly from the xen-orchestra GitHub repository? This would help us determine if the problem is with the ronivay installation script.
Could you also show us your xo server config?

Do you confirm that you are using an admin user?

Hi @elfritto

Personally, I have no issues with XS pools.
Can you provide more information?

• Do you have any error logs on xo server?
• Are there any errors in your browser console?
• Is your're XO up to date?

Hi @Kptainflintt,

I don't think this is related to XO6, but probably to this PR: https://github.com/vatesfr/xen-orchestra/pull/9231
VDIs with snapshot_of: <something> are now recognized as snapshots

spacotte-vates opened this pull request in vatesfr/xen-orchestra

closed fix(xo-server): improve handling of xapi snapshots #9231

ping @melissa-fr

@Pilow Hi.
I've managed to reproduce the issue. I'm currently investigating it

@wmazren Hi.
Weird,i am unable to reproduce the issue..

Can you show us the output from the following command?
xe vbd-param-list uuid=c6f4c7fa-4f6f-7999-d13c-3a29d887d828

@fluxtor Hi.

Could you try disabling the redirectToHttps option in your configuration?
This should resolve the issue. You can re-enable the option once the patch release 6.0.2 is available.
Alternatively, if you absolutely need this option, you can open a support tunnel so I can apply the fix directly to your XOA instance.

@fcgo Hi.
The OTP field is in the preferences property

E.g.

  {
    "email": "foo",
    "permission": "none",
    "pw_hash": "***obfuscated***",
    "preferences": {
      "otp": "<value>"
    },
    "groups": [],
    "id": "694e8856-04c9-448b-90ef-2beb96d119cb",
    "name": "foo",
    "href": "/rest/v0/users/694e8856-04c9-448b-90ef-2beb96d119cb"
  }

@MajorP93 can you try this branch? mra-fix-redirect-https It should fix your issue with redirectToHttps=true

@MajorP93 I think I am finally able to reproduce the bug. I will try to fix it

@acebmxer
Perfect.
Thank you all as well! Early testing and feedback are very precious to us.

@acebmxer I want logs from the journalctl.
sudo systemctl restart xo-server
sudo journalctl -fu xo-server

@MajorP93 various fixes have been performed on master.

Your config file should look like this

[http.mounts]
# Uncomment to setup a default version.
# Otherwise, XO5 will be the default for stable channel and XO6 for latest and source
# '/' = '../xo-web/dist/'

'/v5' = '../xo-web/dist/'
'/v6' = '../../@xen-orchestra/web/dist/'

[http.proxies]
# [port] is used to reuse the same port declared in [http.listen.0]
'/v5/api' = '[protocol]//localhost:[port]/api'
'/v5/api/updater' = 'ws://localhost:9001'
'/v5/rest' = 'http://localhost:[port]/rest'

If you are using a different configuration file that overrides the default configuration, please verify that the paths to xo-5 and xo-6 are correct. You can use absolute paths if necessary.

@acebmxer Can you provide me with the logs from xo-server at its launch?

@acebmxer
Just update your config as bellow

[http.mounts]
164 # Uncomment to setup a default version.
165 # Otherwise, XO5 will be the default for stable channel and XO6 for latest and source
166 # '/' = '../xo-web/dist/'
167 
168 '/v5' = '../xo-web/dist/'  
169 '/' = '../../@xen-orchestra/web/dist/'
170 
171 [http.proxies]
172 # [port] is used to reuse the same port declared in [http.listen.0]
173 '/v5/api' = '[protocol]//localhost:[port]/api'
174 '/v5/api/updater' = 'ws://localhost:9001'
175 '/v5/rest' = 'http://localhost:[port]/rest'

@acebmxer
The first configuration file you show exposes XO5 by default and exposes XO6 on the v6 endpoint
The second configuration file doesn't work because you expose XO5 on the v6 endpoint, but your proxies still point to v5 (changing your proxies to /v6/api, /v6/api/updater and /v6/rest should work, but it seems weird to expose XO5 on a v6 endpoint)
The original config exposes XO5 on v5, XO6 on v6 and /