Description of problem: There is currently no automated method to clone an activation key. An option similar to clone kickstart would help users in creating new keys based off of old ones. This would help assure the user that the new key was exactly the same as the old key with the exception of any changes made afterwards by the user.
Right, there's no option to clone an activation key. However a set of API calls from the activationkey namespace can substitute the clone process very well by creating a new activation key and setting it's parameters according the original activation key. Check https://<spacewalk/rhn/apidoc/handlers/ActivationKeyHandler.jsp for more details.
Fixed in SW: e8d7c7caf1ae8d79894a5af49707abd20387b285
Accepting patch from pull request https://github.com/spacewalkproject/spacewalk/pull/128 to fix cloning keys that have config channels attached (if the name and label on the config channel are not the same. Committing to Spacewalk master: 982e636032ded124fde55808b1c38a3c2dc58d80
Refreshing after cloning an activation key should not cause another copy to get cloned. Committing to Spacewalk master: 846f990e8596df239e2d48d2a97f16cdf74e7c79
Moving bugs to ON_QA as we move to release Spacewalk 2.3
Spacewalk 2.3 has been released. See https://fedorahosted.org/spacewalk/wiki/ReleaseNotes23