Description of problem:

reference bz# 496318 : 

So, here are two issues that I am seeing. 

#1. I register a system and create reactivation key using api client.system.obtainReactivationKey(key, sysemid). It shows up created key in webUI for first time but not after that. 

[root@rlx-3-20 ~]# rhnreg_ks --activationkey="1-aa3b47975110ee23d6ac98cb6c72229d" --force
[root@rlx-3-20 ~]# 

The system is registered without error and with usage-limit set to 1. So when you generate reactivation key multiple times, call seems to succeed however key cannot be seen in webui after first couple of times. 

Steps: 
1. Register a system to satellite.
2. client.system.obtainReactivationKey(key, sysid)
4. Go to https://sat-url/network/systems/details/activation.pxt?sid=1000010302
(You can see the created reactivation key )
3. rhnreg_ks --activationkey=key --force  (This will succeed)
4. Follow sequence 2 to 4  3-4 times and check whether activation key is shown each time in webui 

Observed: 
Reactivation key is not see on webui after initial try which shouldn't happen.


#2. If I invoke api multiple times without actually using reactivation key, old key doesnt seem to have replaced by new key. I can still register systems using old key. (unlike the behavior when we create reactivation key using webui.)

Steps: 
1. Register a system to satellite.
2. client.system.obtainReactivationKey(key, sysid)  (lets say generated key value is key1)
3. client.system.obtainReactivationKey(key, sysid)  (lets say generated key value is key2)
3. rhnreg_ks --activationkey=key1 --force  (This will succeed)
   So basically when we generated key2, key1 was not removed or replaced by key2. It still exists.     


If we follow above 2 sequences just using generate reactivation key in webui, we can see the key every time and also the new key is replaced by old key. So, if we try to register using old key it gives invalid key which makes sense.