@olivierlambert

Oh, you are absolutely right. I forgot to do that, and in the latest version, it is fixed. So the problem is gone!

Thank you very much!

@olivierlambert Well, sadly, I cannot replicate it then, because my system is behind strict firewalls that do not allow contact to registration servers, and sadly, I cannot change that.

Nothing works on the XOA subpage because of that.

@olivierlambert I must admit that I am not entirely sure of how each component of XCP is named, and what differentiates Xen from XOA and so on.

The .git/config tells me it was pulled from https://github.com/vatesfr/xen-orchestra (in a VM on my XCP cluster).

What steps may I do to check what you requested me to check? I'd be glad to help, and sorry for the inconvience of me not knowing all the details of this great product.

Hi,
I have a selfcompiled version of XCP. I just upgraded it to b100a (latest git master, just did "git pull"), but this error still is there.

The situation is the following. I have a user that has self-service rights, and I have three hosts and several storage systems.

When the user goes to the storage window, the user sees this:

This is the developers console. It seems like the action requires admin rights, which the normal user obviously doesn't have. It would be great to show something there anyways, if somehow possible, or to hide the storage tab if it's not possible, so the user never gets error messages.

This is what shows in the logs after calling the page as testuser:

This is the log content (they all are the same, only one as an example):

proxy.getAll
{}
{
  "code": 2,
  "data": {
    "permission": "admin",
    "object": {}
  },
  "message": "not enough permissions",
  "name": "XoError",
  "stack": "XoError: not enough permissions
    at Module.unauthorized (/root/xen-orchestra-2/packages/xo-common/api-errors.js:26:11)
    at Xo.call (file:///root/xen-orchestra-2/packages/xo-server/src/xo-mixins/api.mjs:88:18)
    at Api.#callApiMethod (file:///root/xen-orchestra-2/packages/xo-server/src/xo-mixins/api.mjs:368:29)"
}

Is there anything I can do to fix this? Or is it considered a bug?

@olivierlambert

Oh, you are absolutely right. I forgot to do that, and in the latest version, it is fixed. So the problem is gone!

Thank you very much!

I have a normal user on my XCPng installation, which is admin for one VM. On each (newly created or old) VM I assign him to, he gets "an error has occurred" on the disks tab.

In the firefox command line, this error message pops up.

"Uncaught TypeError: (destructured parameter).pool is undefined"

I have 3 pool servers defined, and they work, and the VM work on them, too, but on the "pools" tab for the user, none are shown.

The system logs (settings -> logs) gives me:

"not enough permissions"

And the details are:

xoa.check
{}
{
  "code": 2,
  "data": {
    "permission": "admin",
    "object": {}
  },
  "message": "not enough permissions",
  "name": "XoError",
  "stack": "XoError: not enough permissions
    at Module.unauthorized (/usr/local/lib/node_modules/xo-server/node_modules/xo-common/src/api-errors.js:21:32)
    at Object.call (file:///usr/local/lib/node_modules/xo-server/src/xo-mixins/api.mjs:95:18)
    at Api.callApiMethod (file:///usr/local/lib/node_modules/xo-server/src/xo-mixins/api.mjs:278:29)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)"
}

I have xo-server 5.80.0.

Also, here the overview page showing 0 (of 3) pools:

Also, on dashboard/health, there's an error regarding the pool.