When creating new storage domain a new disk profile was added without the relevant permissions.
Users couldn't use this profile until a DiskProfileUser role was manually added.
When creating the new disk profile add the DiskProfileUser role to Everyone group.
Users are able to use the disk profile immediately after its creation.
Description of problem:
assign DiskProfileUser role to Everyone group to newly added storagedomain
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Add new storage domain.
2. Check it's permissions.
Group Everyone don't have DiskProfileUser role on sd's disk profile.
Group Everyone have DiskProfileUser role on sd's disk profile.
On creation of a new domain we should make sure that a domain has a profile with everyone perms on it so a creation of a disk should be available with no further work (otherwise this was a regression)
This was fixed in bug 1160846 in 3.5.1. Please verify.
note that the role given by default is UserProfileEditor
To be able to see(and use) the disk profile you need to have role 'DiskProfileUser' on diskprofile of newly added storage domain, so it don't work.
(In reply to Ondra Machacek from comment #4)
> To be able to see(and use) the disk profile you need to have role
> 'DiskProfileUser' on diskprofile of newly added storage domain, so it don't
Ondra you are correct, we don't add that permission on the creation of the storage domain.
Why is the bug on NEW when there's a patch being worked on? Is it going to make it to 3.6.6? Otherwise, please move it TODAY to whatever release it's going to be.
Moving to 3.6.7, for the time being.
(In reply to Yaniv Kaul from comment #6)
> Why is the bug on NEW when there's a patch being worked on? Is it going to
> make it to 3.6.6? Otherwise, please move it TODAY to whatever release it's
> going to be.
I expected automation to do so. Anyway noticed and took care of