Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 920489

Summary: Can't update kickstart SSL and GPG keys with Spacewalk 1.9
Product: [Community] Spacewalk Reporter: Stéphane Gaubert <s.gaubert>
Component: WebUIAssignee: Jan Pazdziora (Red Hat) <jpazdziora>
Status: CLOSED CURRENTRELEASE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.9CC: jpazdziora
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: spacewalk-java-1.9.84-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-15 18:45:35 UTC Type: Bug
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: 1484117    

Description Stéphane Gaubert 2013-03-12 09:06:05 UTC 
Description of problem:
When I try to update kickstart SSL or GPG keys with the Web UI, I get this error lmessage : "**type** is required"

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


How reproducible:
Always

Steps to Reproduce:
1. Create an SSL or GPG key under "systems"/"Kickstart"/"GPG and SSL Keys"
2. Update this key by selecting a file to upload then clicking the "Update Key" Button.
3. 
  
Actual results:
The update fails with the message "**type** is required".

Expected results:
The update should succeed or at else only fail if the uploaded key is malformed but not because the type is not given as the update key form obviously doesn't ask for the type of the key.

Additional info:
This bug may be related to bug id 920292.
Comment 1 Jan Pazdziora (Red Hat) 2013-03-12 13:39:17 UTC 
Fixed in Spacewalk master, 0b928b2e0f55c69b96e5f4f9f38835a22f4bdbfe.
Comment 2 Stephen Herr 2013-03-15 18:45:35 UTC 
Spacewalk 1.9 has been updated.
Comment 3 Eric Herget 2017-09-28 18:09:48 UTC 
This BZ closed some time during 2.5, 2.6 or 2.7.  Adding to 2.7 tracking bug.