Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1254385

Summary:	add an option for bkr remove-account to specify who the new owner should be
Product:	[Retired] Beaker	Reporter:	Dan Callaghan <dcallagh>
Component:	general	Assignee:	Roman Joost <rjoost>
Status:	CLOSED CURRENTRELEASE	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	20	CC:	dcallagh, dowang, mjia, mtyson, rjoost
Target Milestone:	21.1	Keywords:	FutureFeature, NeedsTestCase, Patch
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-10-21 03:25:10 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1254387

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.