Red Hat Bugzilla – Bug 979402
Traceback ERROR com.redhat.rhn.manager.kickstart.cobbler.CobblerSystemCreateComman during provisioning wizard
Last modified: 2013-10-01 17:59:41 EDT
Description of problem:
I created kickstart profile for provision real system - Virtualization Type is "None". And when I clicked on button "Schedule Kickstart and Finish" on page rhn/systems/details/kickstart/ScheduleWizard.do, I found error in log catelina.out. Problem is only traceback in log - I didn't find any other problem of functionality.
If I set Virtualization Type to other value ( except "None"), then it's without traceback.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create kickstart profile with none Virtualization Type
2. provision system - click on button "Schedule Kickstart and Finish"
3. got error in catalina.out
traceback is in log
>> tail /var/log/tomcat6/catalina.out
2013-06-29 01:07:46,191 [TP-Processor15] ERROR com.redhat.rhn.manager.kickstart.cobbler.CobblerSystemCreateCommand - This cobbler profile does not have a redhat_management_key set
at org.apache.jsp.WEB_002dINF.pages.kickstart.wizard.schedule.fifth_jsp._jspx_meth_decorator_005fgetProperty_005f0(Unknown Source)
at org.apache.jsp.WEB_002dINF.pages.kickstart.wizard.schedule.fifth_jsp._jspx_meth_c_005fif_005f2(Unknown Source)
at org.apache.jsp.WEB_002dINF.pages.kickstart.wizard.schedule.fifth_jsp._jspService(Unknown Source)
Fixed in spacewalk master: e5372e275dd1e8f0ffded62f54e4e99f42073d43
By the way, a real (functional) side effect of this traceback was that if you tried to use the "delete system" or "add to / remove from ssm" links you would have gotten an internal service error (because the system id was not being included in the url).
Satellite 5.6 has been released. This bug was tracked under the release.
This bug was either VERIFIED or RELEASE_PENDING (re-verified prior shortly
Moving to CLOSED CURRENT_RELEASE.
Text from Upgrade Erratum follows:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.