Feature Request: maas-cli change ownership of machine

[Eduardo Damato]

Feature request:

A system that is allocated to a user in MAAS can not be transferred to another user. If a user leaves the group etc, the machine will have to be destroyed and reinstalled, therefore I request that MAAS implements a way via maas-cli at least to transfer the ownership of the system to another user.

Something along the lines of:

$ maas-cli root nodes owner=<newowner>

[Eduardo Damato (edamato)]

For the record in this case the node was allocated to MAAS without juju.

In this case it was installed by doing:

$ maas-cli username nodes acquire name=<FQDN>

and not via juju.

Thanks,
Eduardo.

[Raphaël Badin (rvb)]

I think this has to be a separate method (because it's sort of an override). Something along the lines of:
$ maas-cli root nodes change_owner owner=<newowner>

[Andres Rodriguez (andreserl)]

Hi!

**This is an automated message**

We believe this is may no longer be an issue in the latest MAAS release. Due to the report date of this, we are currently marking it as Invalid. If you believe this bug report still valid against the latest release of MAAS, or if you are still interested in this, please re-open this bug report.

Thanks

[Jim Conner (snafuxnj)]

Would it be possible to re-open this bug? This is affecting us with practically the same conditions. We don't use juju and much of what we do is done through either maas-cli, maas UI, or gomaasAPI. A user, who was an admin, recently left our team/company. He has one asset he owns (switch) which is the main switch on the network maas runs. I fear that deleting the switch would require tearing the entire environment down, which is simply not an option. However, allowing this user's login to maas to remain is a security nono. It would be amazing if a change-owner ability existed.

[Jim Conner (snafuxnj)]

re-opened. See last statement for argument to re-open this ticket for consideration.

[Maruthi S. Inukonda (maruthisi)]

 +1 . I agree with Jim. We have BMaaS only deployment without overcloud.

[Björn Tillenius (bjornt)]

So far, the stated use case has been that a user leaves the company. For that MAAS already has a solution, which is to run this:

  maas $profile user delete $old_user transfer_resources_to=$new_user

This will delete the user and transfer everything that he owns to someone else.

Is that enough, or do you have another use case in mind as well?

[Laurent Dumont (baconpackets)]

We had similar case when using the rescue mode. The node that is being rescued will be transfered under the user that requested the rescue.

In our env, we have a specific user that "owns" all the deployed machines for a site. We usually don't want to have to log into that account just to enter rescue.

I think there are two possible designs:
- Rescue should not change the owner of a machine.
- There should be a GUI or CLI way to change the owner of a node.

[Launchpad Janitor (janitor)]

[Expired for MAAS because there has been no activity for 60 days.]

[Heather Lemon (hypothetical-lemon)]

I'd like to have this kept open as we are having multiple people wanting this option.

[Heather Lemon (hypothetical-lemon)]

You can set the machine to rescue mode and change the ownership then and the user becomes the new owner of the machine

[Collin LeGault (clegault)]

I have a different use case. I am automating the setup of services as user Admin, once they come up I'd like to be able to transfer the ownership to the requestor. I would have to store everyone's password or a token for their account and they would need to be Administrator accounts in order to do the rescue mode thing. It makes much more sense that an Admin would be able to set the owner tag rather than take the system out of production (enter/exit rescue mode reboots twice) in order to make a descriptive change to a field in the MaaS DB.

[Heitor (heitorpbittencourt)]

Can we reopen this issue? I have another use case:

We are on-boarding another person to take over some of the infrastructure responsibility that I have. I don't want to delete my user, but I want to transfer the ownership of some resources to this new user.

Something like would be perfect:

    $ maas <profile> <resource> transfer-ownership <target_user>

In this case, <resource> would be anything that can have an owner.

[Redbom (redbom)]

I also need to change the owner of the machine.
Is this possibility still not provided?