Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 463976 - Internal server error when trying to save a cloned ks profile using the name of an existing profile
Summary: Internal server error when trying to save a cloned ks profile using the name ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Spacewalk
Classification: Community
Component: WebUI
Version: 0.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeff Ortel
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space04
TreeView+ depends on / blocked
 
Reported: 2008-09-25 18:52 UTC by Jeff Ortel
Modified: 2009-01-22 16:53 UTC (History)
1 user (show)

Fixed In Version: 0.2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-01-22 16:53:51 UTC


Attachments (Terms of Use)

Description Jeff Ortel 2008-09-25 18:52:26 UTC
Description of problem:

Satellite 5.0.1 reports a internal server error instead of a more descriptive error when someone choose the name of an existing kickstart profile in saving a cloned kickstart profile.

How reproducible:

always

Steps to Reproduce:

1  select an existing kickstart profile
2  create a new profile using "clone kickstart" button  
3  enter a profile name that already exists  
4  press clone kickstart  

Actual results:

we have an internal server error page

Expected results:

we should have a more descriptive error message displayed in the same page as it happens for other error conditions

Additional info:

Customer says that this happens in 4.x as well but I have not tested this. A workaround for this is to use the back button of the browser and choose an unused kickstart profile name.

Comment 1 Jeff Ortel 2008-09-25 18:53:20 UTC
Fixed.

Comment 2 Jesus M. Rodriguez 2009-01-22 16:53:51 UTC
ui now handles this case with an appropriate error message.


Note You need to log in before you can comment on or make changes to this bug.