| 2019-01-14 15:44:05 |
Björn Tillenius |
bug |
|
|
added bug |
| 2019-01-14 15:44:13 |
Björn Tillenius |
tags |
|
rbac |
|
| 2019-01-14 15:44:17 |
Björn Tillenius |
maas: status |
New |
Triaged |
|
| 2019-01-14 15:44:20 |
Björn Tillenius |
maas: importance |
Undecided |
High |
|
| 2019-01-14 15:44:22 |
Björn Tillenius |
maas: milestone |
|
2.5.1 |
|
| 2019-01-14 16:57:57 |
Björn Tillenius |
description |
This is with MAAS 2.5.1-7489-g2f25a2cc0-0ubuntu1~18.04.1 and RBAC enabled.
If I'm authenticated as a user that has the Admin role on a resource pool,
the update command for a machine still can't be used:
lilium:~> maas user4 machine update 6q33ak hostname=my-name
This method is reserved for admin users. |
This is with MAAS 2.5.1-7489-g2f25a2cc0-0ubuntu1~18.04.1 and RBAC enabled.
If I'm authenticated as a user that has the Admin role on a resource pool,
the update command for a machine still can't be used:
lilium:~> maas user4 machine update 6q33ak hostname=my-name
This method is reserved for admin users.
In fact, it seems that a lot of the methods under machine is
only accessible to global admins, so we'll have to go through
each one of them and fix them. |
|
| 2019-01-15 11:34:42 |
Björn Tillenius |
tags |
rbac |
api rbac |
|
| 2019-01-15 14:27:55 |
Björn Tillenius |
description |
This is with MAAS 2.5.1-7489-g2f25a2cc0-0ubuntu1~18.04.1 and RBAC enabled.
If I'm authenticated as a user that has the Admin role on a resource pool,
the update command for a machine still can't be used:
lilium:~> maas user4 machine update 6q33ak hostname=my-name
This method is reserved for admin users.
In fact, it seems that a lot of the methods under machine is
only accessible to global admins, so we'll have to go through
each one of them and fix them. |
This is with MAAS 2.5.1-7489-g2f25a2cc0-0ubuntu1~18.04.1 and RBAC enabled.
If I'm authenticated as a user that has the Admin role on a resource pool,
the update command for a machine still can't be used:
lilium:~> maas user4 machine update 6q33ak hostname=my-name
This method is reserved for admin users.
In fact, it seems that a lot of the methods under machine is
only accessible to global admins, so we'll have to go through
each one of them and fix them.
The ones that are confirmed affected are:
machine update
machines set-zone |
|
| 2019-01-15 14:28:37 |
Björn Tillenius |
description |
This is with MAAS 2.5.1-7489-g2f25a2cc0-0ubuntu1~18.04.1 and RBAC enabled.
If I'm authenticated as a user that has the Admin role on a resource pool,
the update command for a machine still can't be used:
lilium:~> maas user4 machine update 6q33ak hostname=my-name
This method is reserved for admin users.
In fact, it seems that a lot of the methods under machine is
only accessible to global admins, so we'll have to go through
each one of them and fix them.
The ones that are confirmed affected are:
machine update
machines set-zone |
This is with MAAS 2.5.1-7489-g2f25a2cc0-0ubuntu1~18.04.1 and RBAC enabled.
If I'm authenticated as a user that has the Admin role on a resource pool,
the update command for a machine still can't be used:
lilium:~> maas user4 machine update 6q33ak hostname=my-name
This method is reserved for admin users.
In fact, it seems that a lot of the methods under machine is
only accessible to global admins, so we'll have to go through
each one of them and fix them.
The ones that are confirmed affected are:
machine update
machines set-zone
machines power-parameters |
|
| 2019-01-17 11:27:27 |
Björn Tillenius |
description |
This is with MAAS 2.5.1-7489-g2f25a2cc0-0ubuntu1~18.04.1 and RBAC enabled.
If I'm authenticated as a user that has the Admin role on a resource pool,
the update command for a machine still can't be used:
lilium:~> maas user4 machine update 6q33ak hostname=my-name
This method is reserved for admin users.
In fact, it seems that a lot of the methods under machine is
only accessible to global admins, so we'll have to go through
each one of them and fix them.
The ones that are confirmed affected are:
machine update
machines set-zone
machines power-parameters |
This is with MAAS 2.5.1-7489-g2f25a2cc0-0ubuntu1~18.04.1 and RBAC enabled.
If I'm authenticated as a user that has the Admin role on a resource pool,
the update command for a machine still can't be used:
lilium:~> maas user4 machine update 6q33ak hostname=my-name
This method is reserved for admin users.
In fact, it seems that a lot of the methods under machine is
only accessible to global admins, so we'll have to go through
each one of them and fix them.
The ones that are confirmed affected are:
machine update
machines set-zone
machines power-parameters
machines add-chassis |
|
| 2019-01-17 11:38:13 |
Björn Tillenius |
description |
This is with MAAS 2.5.1-7489-g2f25a2cc0-0ubuntu1~18.04.1 and RBAC enabled.
If I'm authenticated as a user that has the Admin role on a resource pool,
the update command for a machine still can't be used:
lilium:~> maas user4 machine update 6q33ak hostname=my-name
This method is reserved for admin users.
In fact, it seems that a lot of the methods under machine is
only accessible to global admins, so we'll have to go through
each one of them and fix them.
The ones that are confirmed affected are:
machine update
machines set-zone
machines power-parameters
machines add-chassis |
This is with MAAS 2.5.1-7489-g2f25a2cc0-0ubuntu1~18.04.1 and RBAC enabled.
If I'm authenticated as a user that has the Admin role on a resource pool,
the update command for a machine still can't be used:
lilium:~> maas user4 machine update 6q33ak hostname=my-name
This method is reserved for admin users.
In fact, it seems that a lot of the methods under machine is
only accessible to global admins, so we'll have to go through
each one of them and fix them.
The ones that are confirmed affected are:
machine update
machine power-parameters
machines set-zone
machines power-parameters
machines add-chassis |
|
| 2019-01-21 10:22:18 |
Björn Tillenius |
maas: status |
Triaged |
In Progress |
|
| 2019-01-21 10:22:21 |
Björn Tillenius |
maas: assignee |
|
Björn Tillenius (bjornt) |
|
| 2019-01-24 15:31:05 |
Björn Tillenius |
description |
This is with MAAS 2.5.1-7489-g2f25a2cc0-0ubuntu1~18.04.1 and RBAC enabled.
If I'm authenticated as a user that has the Admin role on a resource pool,
the update command for a machine still can't be used:
lilium:~> maas user4 machine update 6q33ak hostname=my-name
This method is reserved for admin users.
In fact, it seems that a lot of the methods under machine is
only accessible to global admins, so we'll have to go through
each one of them and fix them.
The ones that are confirmed affected are:
machine update
machine power-parameters
machines set-zone
machines power-parameters
machines add-chassis |
This is with MAAS 2.5.1-7489-g2f25a2cc0-0ubuntu1~18.04.1 and RBAC enabled.
If I'm authenticated as a user that has the Admin role on a resource pool,
the update command for a machine still can't be used:
lilium:~> maas user4 machine update 6q33ak hostname=my-name
This method is reserved for admin users.
In fact, it seems that a lot of the methods under machine is
only accessible to global admins, so we'll have to go through
each one of them and fix them.
The ones that are confirmed affected are:
machine update
machine power-parameters |
|
| 2019-01-24 15:32:03 |
Björn Tillenius |
description |
This is with MAAS 2.5.1-7489-g2f25a2cc0-0ubuntu1~18.04.1 and RBAC enabled.
If I'm authenticated as a user that has the Admin role on a resource pool,
the update command for a machine still can't be used:
lilium:~> maas user4 machine update 6q33ak hostname=my-name
This method is reserved for admin users.
In fact, it seems that a lot of the methods under machine is
only accessible to global admins, so we'll have to go through
each one of them and fix them.
The ones that are confirmed affected are:
machine update
machine power-parameters |
This is with MAAS 2.5.1-7489-g2f25a2cc0-0ubuntu1~18.04.1 and RBAC enabled.
If I'm authenticated as a user that has the Admin role on a resource pool,
the update command for a machine still can't be used:
lilium:~> maas user4 machine update 6q33ak hostname=my-name
This method is reserved for admin users.
In fact, it seems that a lot of the methods under machine is
only accessible to global admins, so we'll have to go through
each one of them and fix them.
The ones that are confirmed affected are:
machine update
machine power-parameters
There are also some methods under the 'machines' endpoint that have the
same problem. The bug to track that is bug 1813181. |
|
| 2019-01-24 15:36:31 |
Björn Tillenius |
merge proposal linked |
|
https://code.launchpad.net/~bjornt/maas/+git/maas/+merge/362197 |
|
| 2019-01-25 10:04:33 |
MAAS Lander |
maas: status |
In Progress |
Fix Committed |
|
| 2019-01-25 10:53:09 |
Björn Tillenius |
merge proposal linked |
|
https://code.launchpad.net/~bjornt/maas/+git/maas/+merge/362242 |
|
| 2019-02-08 15:26:34 |
Andres Rodriguez |
maas: status |
Fix Committed |
Fix Released |
|
