Bug 920292 - GPG keys are not rendered in kickstart profiles in spacewalk 1.9
Summary: GPG keys are not rendered in kickstart profiles in spacewalk 1.9
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Spacewalk
Classification: Community
Component: WebUI
Version: 1.9
Hardware: All
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Jan Pazdziora (Red Hat)
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
: 920467 (view as bug list)
Depends On:
Blocks: space27
TreeView+ depends on / blocked
 
Reported: 2013-03-11 17:44 UTC by Stéphane Gaubert
Modified: 2017-09-28 18:07 UTC (History)
3 users (show)

Fixed In Version: spacewalk-java-1.9.84-1
Clone Of:
Environment:
Last Closed: 2013-03-15 18:46:49 UTC
Embargoed:


Attachments (Terms of Use)

Description Stéphane Gaubert 2013-03-11 17:44:51 UTC
Description of problem:
The GPG keys added to a kickstart profile are not rendered in the RHN Post script. 

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


How reproducible:
Add at least one GPG key to a kickstart profile and view the generated kickstart file.

Steps to Reproduce:
1. Create a GPG key
2. Create a kickstart profile
3. Add the previously created key to the kickstart profile
4. View the generated kickstart file
  
Actual results:
The RHN post script generated doesn't import the GPG key.

Expected results:
The GPG key should be imported by the generated RHN post script


Additional info:
There is an issue in the GpgCryptoKey class from the com.redhat.rhn.domain.kickstart.crypto package : the isGPG method returns "false" instead of "true".

I hope that a fixed rpm will be published soon in the spacewalk 1.9 repository.

Comment 2 Michael Mráka 2013-03-12 07:46:29 UTC
*** Bug 920467 has been marked as a duplicate of this bug. ***

Comment 3 Jan Pazdziora (Red Hat) 2013-03-12 09:11:51 UTC
Fixed in Spacewalk master, ed30dc2f5e5f06afd5c056170b2ccab9643f69bc.

Comment 4 Stephen Herr 2013-03-15 18:46:49 UTC
Spacewalk 1.9 has been updated.

Comment 5 Eric Herget 2017-09-28 18:07:40 UTC
This BZ closed some time during 2.5, 2.6 or 2.7.  Adding to 2.7 tracking bug.


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