Bug 1253111

Summary:	'push' XMLRPC method for updating inventory should not automatically create new arches
Product:	[Retired] Beaker	Reporter:	Dan Callaghan <dcallagh>
Component:	general	Assignee:	Dan Callaghan <dcallagh>
Status:	CLOSED CURRENTRELEASE	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	20	CC:	dcallagh, dowang, mjia, rjoost
Target Milestone:	21.1	Keywords:	Patch
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-10-21 03:25:07 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:

Description Dan Callaghan 2015-08-13 02:27:44 UTC

If a buggy version of beaker-system-scan starts reporting a wrong arch (for example, x86-64 instead of x86_64) the 'push' XMLRPC method will happily create the new architecture and then it will exist in Beaker forever, including being offered on the system page for system owners to pick for their system (and setting install options, etc).

This is quite painful to recover from, so it would be better if the 'push' method just rejected the unknown arch.

New arches come along very rarely, and we add them to beaker-init as needed. Admins can also create new arches in db directly if that is ever necessary. (We should probably have an admin interface for creating them but that is a separate issue.)

Comment 2 Dan Callaghan 2015-08-13 02:40:13 UTC

http://gerrit.beaker-project.org/4342

Comment 5 Dan Callaghan 2015-10-21 03:25:07 UTC

Beaker 21.1 has been released.