Self Service User - Snapshot VM - Nope

[fufroma]

xo-* 5.2.1

Self service user, working VM, ACL admin on the VM.

Trying "snapshot" on the VM.

vm.snapshot
{
  "id": "119e0fbf-271b-b43c-15fb-e7a4c52836f2"
}
Unauthorized: not authenticated or not enough permissions
    at /source/api/vm.coffee:51:14
    at run (/usr/local/lib/node_modules/xo-server/node_modules/core-js/library/modules/es6.promise.js:87:22)
    at /usr/local/lib/node_modules/xo-server/node_modules/core-js/library/modules/es6.promise.js:100:28
    at flush (/usr/local/lib/node_modules/xo-server/node_modules/core-js/library/modules/_microtask.js:18:9) 

[olivierlambert]

Creating a snapshot will add a disk on the SR. So you need write permission on this SR.

[fufroma]

If I don't have write permission on this SR, how did I create the VM ;) ?

So, if I can create a VM, why can't I create a Snapshot ?

And even if you don't allow it, why displaying the Snapshot button ?

It's even a "server" bug, or a UI bug.

[julien-f]

It's a server bug (or missing feature), the snapshot command does not currently work with self services.

[olivierlambert]

@fufroma self service "hide" some ACLs: you can create VMs on a self without having write permission on the SR.

@julien-f yes I mixed with just "plain" ACLs, which is working when you add SR permissions to the user.

[olivierlambert]

Centralizing here: #1539

[fufroma]

I kinda like it as a "Missing feature", can it be a "long term" goal?

[olivierlambert]

Frankly, doing that will need to rewrite xo-server from scratch (something we'll do next year)

[fufroma]

If you tag it duplicate of #189 i will sulk 😉

[fufroma]

Nota in the futur: if you find a way to do it, it may give a way to have similar feature as #1521 as you can create a new VM from a snapshot.