[2.4,2.5] Regular users unable to partition storage
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Blake Rouse | ||
Bug Description
When logging in as a regular non-admin MAAS user the user does not have permissions to create partitions. Using the web interface, after acquiring a machine a user has the capability to unmount and remove filesystems, but they can not remount or recreate those same filesystems. Removing the partition in the UI seems to be a glitch in the UI as if you navigate away and come back the filesystem is still there. This is true for standard partitions and LVM logical volumes. Once the machine is released by the user the original partition layout is restored.
Using the CLI as a regular user I am able to unmount and remount partitions as well as change things like the fstype. I am not able to delete the partitions.
In both cases, once the machine is released the original/default set of filesystems are restored.
As a regular non-admin user I should be able to delete/create partitions on the storage, then when the system is released it should return to the default configuration.
I have confirmed this on 2.4 but it may affect other versions as well.
Related branches
- Andres Rodriguez (community): Approve
-
Diff: 245 lines (+121/-10)6 files modifiedsrc/maasserver/forms/filesystem.py (+2/-1)
src/maasserver/forms/tests/test_filesystem.py (+8/-3)
src/maasserver/static/js/angular/controllers/node_details_storage.js (+22/-3)
src/maasserver/static/js/angular/controllers/tests/test_node_details_storage.js (+86/-0)
src/maasserver/static/partials/nodedetails/storage/disks-partitions.html (+1/-1)
src/maasserver/static/partials/nodedetails/storage/filesystems.html (+2/-2)
| Changed in maas: | |
| assignee: | nobody → Blake Rouse (blake-rouse) |
| Nick Niehoff (nniehoff) wrote | #1 |
| summary: |
- [2.4] Regular users unable to partition storage + [2.4,2.5] Regular users unable to partition storage |
| Changed in maas: | |
| milestone: | none → 2.6.0beta2 |
| Changed in maas: | |
| milestone: | 2.6.0beta2 → 2.6.0rc1 |
| Changed in maas: | |
| status: | New → In Progress |
| importance: | Undecided → High |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| milestone: | 2.6.0rc1 → 2.6.0beta4 |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
I have confirmed the same behavior in 2.5.