SelfService issues creating new VM
-
Hello all!
I've just installed XO from source (xo-server 5.50.1 - xo-web 5.50.2) on a CentOS 7 (last updates up to now) in my test environment, with XCP-NG 8 (latest) and I don't know if my installation has some problems or I'm doing something wrong.
Summing up, create a self-service resource to a group, gave the permissions to use some templates, SR, ISO SR, Networks, max cpu, max ram, max disk, etc.
When logged with a user in that group, he can see the resources set to him, existent VMs and all, but when this user tries to create a new VM, he can see the template but can't select it, on the drop down when click on the template to use it does not select it and it can't go to the next part of creation.
Also, no networks are shown even if the network device is selected on the self-service settings.
Tried to set ACLs to SR, as viewer and operator and no go. The only way it worked was to set ACL to the pool, but in that case he can see all pool resources, hosts and all VM instead of only seeing his VM.
Am I doing something wrong? Followed all tutorials and videos that I’ve found, done exactly the same thing but my result are different from the rest.
Best regards,
Anderson Alipio
-
Can you test on XOA to see if you can reproduce the issue?
It might be relate to https://github.com/vatesfr/xen-orchestra/issues/4565
-
I was just installing XOA to see this. About to finish and I'll post here.
-
In XOA, there's 2 release channel:
- stable
- latest
By default, you are on stable. So test with stable first. Then try latest, and keep us posted
Note: if you need our assistance to get your trial, just let me know your registered email in private chat
-
Worked well on XOA stable (xo-server 5.42.1 xo-web 5.48.1)
-
After testing with XOA and seeing that a update has been issued, updated my XO from source with
$ git checkout .
$ git pull --ff-only
$ yarn
$ yarn buildand then restarting xenorchestra, working fine now.
Thanks a lot!
-
Indeed, this was an issue only hitting
master(and XOAlatestbranch). This is now solved (see https://github.com/vatesfr/xen-orchestra/issues/4565 ).Note those are kind of features are usually utilized in corporate environment. What's your use case out of curiosity?
