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.)