Bug 675505

Summary: Internal Server Error when trying to create a Kickstart profile
Product: [Community] Spacewalk Reporter: dburklan
Component: ServerAssignee: Michael Mráka <mmraka>
Status: CLOSED CURRENTRELEASE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.3CC: jpazdziora, mmraka, slukasik
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: spacewalk-java-1.4.1-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-26 09:10:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 674675    
Attachments:
Description Flags
Tomcat5 error log output none

Description dburklan 2011-02-06 03:37:19 UTC
Created attachment 477267 [details]
Tomcat5 error log output

Description of problem: I receive an "Internal Server Error" message when trying to create Kickstart profiles. 

Version-Release number of selected component (if applicable): 
Spacewalk v1.3 with the PostgreSQL backend (v8.4)

How reproducible: I am able to reproduce this error message every time I try to create a kickstart profile. 


Steps to Reproduce: I am able to go to the System->Kickstart->Profiles page along with either the "create new kickstart profile" page or "upload new kickstart file" page. The issue however is experienced after entering the required data and clicking either "finish" or "create" (depending on if I chose either "create new kickstart profile" or "upload new kickstart file") which results in an "Internal Server Error". 
  
Actual results: Internal Server Error


Expected results: The Kickstart profile should be created 


Additional info: I have attached the Tomcat5 error log output that is generated at the same time I receive the "Internal Server Error". If you would like me to obtain any other information that would help in diagnosing this bug let me know, thanks for all of your hard work!

Comment 1 dburklan 2011-02-07 05:29:41 UTC
I would like to note that I also experience when using the oracle backend (using Oracle 10G express on a completely separate installation). 

Regards,

Dan

Comment 2 Jan Pazdziora 2011-02-07 15:16:30 UTC
Taking.

Fixed in Spacewalk master, 25a58f15e8e692a8653df53ba633acecf8804437.

Comment 3 Michael Mráka 2011-02-07 15:55:49 UTC
Taking back.

Two more fixes are necessary because of struts upgrade from 1.2 to 1.3:

commit 88171f491f87659029f796910161f82238e6089a
    more fixes for javax.servlet.ServletException: javax.servlet.jsp.JspException: Cannot specify "styleId" when in XHTML mode as the HTML "id" attribute is already used to store the bean name
commit 85c5552dafc98948f5d837714ffb984cf45e7c29
    fixed javax.servlet.ServletException: javax.servlet.jsp.JspException: Cannot specify "styleId" when in XHTML mode as the HTML "id" attribute is already used to store the bean name

Fixed package: spacewalk-java-1.4.1-1

Comment 4 Miroslav Suchý 2011-04-11 07:45:12 UTC
Mass moving to ON_QA before release of Spacewalk 1.4

Comment 5 Miroslav Suchý 2011-04-26 09:10:39 UTC
Spacewalk 1.4 has been released