Operator can't mark machines as broken without acquiring the machine
Bug #1811234 reported by
Björn Tillenius
This bug report is a duplicate of:
Bug #1997000: `Mark Broken` and `Mark Fixed` permissions are too restrictive and inconsistent.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Triaged
|
High
|
Unassigned |
Bug Description
This is testing with MAAS 2.5.1-7489-
Logged in as a user that has the Operator role in RBAC, I can't mark
a machine in the Ready state as Broken.
I can however mark the machine as broken if I acquire the machine first,
but I see no reason why that should be necessary.
In fact, even a normal user can mark a machine as broken if it's acquired
first, in which case he looses access to the machine and it becomes unusable
for him, with no way of fixing it.
An Operator can mark a Broken machine as fixed.
This bug affects both the UI and the API.
tags: | added: rbac |
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 2.5.1 |
summary: |
- [2.5, RBAC] Operator can't mark machines as broken + [2.5, RBAC] Operator can't mark machines as broken without acquiring the + machine |
description: | updated |
Changed in maas: | |
milestone: | 2.5.1 → 2.5.2 |
Changed in maas: | |
milestone: | 2.5.2 → 2.5.3 |
Changed in maas: | |
milestone: | 2.5.3 → 2.5.4 |
Changed in maas: | |
milestone: | 2.5.4 → none |
summary: |
- [2.5, RBAC] Operator can't mark machines as broken without acquiring the - machine + Operator can't mark machines as broken without acquiring the machine |
To post a comment you must log in.