An admin is allowed to create raids for an Allocated node in the UI, but not the API
Bug #1812377 reported by
Björn Tillenius
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Unassigned | ||
| maas-ui |
Fix Released
|
Unknown
|
|||
Bug Description
This is with MAAS 2.5.1-7489-
I have a user that is an admin in MAAS and a machine that is allocated.
If I try to create a raid device for that machine in the API, it says that
I'm not allowed, since the machine is not in a Ready state.
The UI allows me to create a raid array without any problems, though.
We either need to relax the API, or make the UI stricter.
Note that with RBAC enabled and a user that has the Admin role
on the resource pool, he gets presented the UI for creating
a raid, but after clicking "Create RAID", the form is simply
closed. No raid was created, and no error message was given.
| tags: | added: api rbac ui |
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| milestone: | none → 2.5.1 |
| Changed in maas: | |
| milestone: | 2.5.1 → 2.5.2 |
| Changed in maas: | |
| milestone: | 2.5.2 → 2.5.3 |
| summary: |
- [2.5, UI] An admin is allowed to create raids for an Allocated node in - the UI, but not the API + [2.5, UI, RBAC] An admin is allowed to create raids for an Allocated + node in the UI, but not the API |
| 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 |
| summary: |
- [2.5, UI, RBAC] An admin is allowed to create raids for an Allocated - node in the UI, but not the API + An admin is allowed to create raids for an Allocated node in the UI, but + not the API |
| Changed in maas: | |
| status: | Fix Committed → Triaged |
| Changed in maas: | |
| status: | Triaged → Fix Committed |
| tags: | removed: ui |
| tags: | removed: rbac |
| Changed in maas: | |
| milestone: | none → 3.3.0 |
| status: | Fix Committed → Triaged |
Revision history for this message
| Jerzy Husakowski (jhusakowski) wrote | #1 |
| tags: |
added: ui removed: api bug-council |
| Changed in maas: | |
| milestone: | 3.3.0 → 3.4.0 |
| Changed in maas: | |
| status: | Triaged → Fix Committed |
| Changed in maas: | |
| milestone: | 3.4.0 → 3.3.0 |
| status: | Fix Committed → Triaged |
| milestone: | 3.3.0 → 3.4.0 |
| Changed in maas: | |
| status: | Triaged → Fix Committed |
| Changed in maas: | |
| milestone: | 3.4.0 → 3.4.0-beta1 |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Let's check if there's still an inconsistency after migration of the UI to React.