[2.5, UI, RBAC] Normal users can unmount the root file system, but not remount it

Bug #1811109 reported by Björn Tillenius
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Unassigned
maas-ui
Fix Released
Unknown

Bug Description

This is with 2.5.1-7489-g2f25a2cc0-0ubuntu1~18.04.1.

If I log in as a user that has the User role on a resource pool, I can't seem to modify the storage for the machines.

After allocating a node (that has / on the first disk and two unused disks), there are no actions available for the unused disks. For the / partition there is Unmount and Remove. Remove doesn't seem to do anything, except giving the illusion of removing the disk (after reloading the page it's there again).

I can however Umnount the filesystem, but now I have a machine with no /, and no possibility of adding a filesystem.

Further more, the "Add special filesystem" functionality is also somewhat
broken. I can click on it, and it doesn't give any errors when adding
a tmpfs, for example. But there's no sign of it on the page, not even
after reloading it. But if I try to add the same filesystem again,
it complains that one already exists.

After releasing the machine, the tmpfs filesystem is there, though. In
fact, somehow there are 4 tmpfs at the same mount point, and I can't
acquired the machine any more, since it complains that there already
is a filesystem at /mytmpfs (which is the mount point for all four)

This is UI only. In the API it works as expected.

Tags: ui
Changed in maas:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.5.1
tags: added: rbac
Revision history for this message
Nick Niehoff (nniehoff) wrote :
Revision history for this message
Björn Tillenius (bjornt) wrote : Re: [2.5, RBAC] Normal users can unmount the root file system, but not remount it

I've change the summary to make it clear that this is about the user is able to turn the machine unusable, and the only way of fixing it is to release and reacquire the machine. So it's not a duplicate of 1809470.

I've also confirmed that the behavior is the same without using RBAC as well.

summary: - [2.5, RBAC] Can't modify storage as a normal user on allocated machines
+ [2.5, RBAC] Normal users can unmount the root file system, but not
+ remount it
summary: - [2.5, RBAC] Normal users can unmount the root file system, but not
- remount it
+ [2.5] Normal users can unmount the root file system, but not remount it
Changed in maas:
importance: High → Medium
tags: removed: rbac
description: updated
description: updated
Revision history for this message
Björn Tillenius (bjornt) wrote : Re: [2.5] Normal users can unmount the root file system, but not remount it

FWIW, a non-admin can't mount any filesystem, it can only unmount them. This is a UI issue only, it works using the API.

summary: - [2.5] Normal users can unmount the root file system, but not remount it
+ [2.5, UI] Normal users can unmount the root file system, but not remount
+ it
Changed in maas:
importance: Medium → High
tags: added: ui
description: updated
Changed in maas:
milestone: 2.5.1 → 2.5.2
Changed in maas:
milestone: 2.5.2 → 2.5.3
summary: - [2.5, UI] Normal users can unmount the root file system, but not remount
- it
+ [2.5, UI, RBAC] Normal users can unmount the root file system, but not
+ remount it
Changed in maas:
milestone: 2.5.3 → 2.6.0beta2
Changed in maas:
milestone: 2.6.0beta2 → 2.6.0rc1
Changed in maas:
milestone: 2.6.0rc1 → 2.6.0rc2
Changed in maas:
milestone: 2.6.0rc2 → 2.7.0alpha1
Changed in maas:
milestone: 2.7.0b1 → 2.7.0b2
Changed in maas:
milestone: 2.7.0b2 → none
Changed in maas-ui:
importance: Undecided → Unknown
Changed in maas-ui:
status: New → Fix Released
Changed in maas:
status: Triaged → Fix Committed
Changed in maas:
milestone: none → 3.3.0
Changed in maas:
milestone: 3.3.0 → 3.3.0-beta1
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.