Bug 1254385 - add an option for bkr remove-account to specify who the new owner should be
Summary: add an option for bkr remove-account to specify who the new owner should be
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: general
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 21.1
Assignee: Roman Joost
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks: 1254387
TreeView+ depends on / blocked
 
Reported: 2015-08-17 23:12 UTC by Dan Callaghan
Modified: 2015-10-21 03:25 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-21 03:25:10 UTC
Embargoed:

Attachments (Terms of Use)

Description Dan Callaghan 2015-08-17 23:12:42 UTC 
Currently when bkr remove-account is run, if the closed account owned any systems, the user who ran the remove-account command will become the new owner of the systems.

However since the person running bkr remove-account may just be a support team member they would usually want the systems to be owned by the manager of the closed account, or by "admin" or similar.

bkr remove-account should accept an option to control which account will become the new owner of the systems.
Comment 1 Roman Joost 2015-09-11 05:59:19 UTC 
Patch available on gerrit:

https://gerrit.beaker-project.org/#/c/4392/
Comment 4 Dan Callaghan 2015-10-21 03:25:10 UTC 
Beaker 21.1 has been released.
Note You need to log in before you can comment on or make changes to this bug.