Description of problem:
There was experienced an issue when s390x-server-5 channels were synchronized, system was registered and a provisioning tried to be applied on that system to make it kickstarted to server-rhel-5-u4 (all these: without rhn-satellite restart)
Satellite UI complained that there is no suitable ks profile made (while actually there were made 2). cliff argued it as a hibernate caching issue - restart of satellite helped to resolve the issue - ks profiles were recognized then.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. see above in description.
2.
3.
  
Actual results:
impossible to make s390x kickstarting until satellite is restarted.

Expected results:
clients should not experience such an issue - provisioning should be possible.

Additional info: