Bug 920467 - Provisioning: Missing GPG-Keys while Kickstarting
Summary: Provisioning: Missing GPG-Keys while Kickstarting
Keywords:
Status: CLOSED DUPLICATE of bug 920292
Alias: None
Product: Spacewalk
Classification: Community
Component: Server
Version: 1.9
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Michael Mráka
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space27
TreeView+ depends on / blocked
 
Reported: 2013-03-12 07:27 UTC by Rolf Linder
Modified: 2017-09-28 18:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-12 07:46:29 UTC
Embargoed:


Attachments (Terms of Use)

Description Rolf Linder 2013-03-12 07:27:02 UTC
Description of problem:
As of Spacewalk 1.9 (after update from 1.8) the generated kickstart file does not include any GPG keys anymore.


Version-Release number of selected component (if applicable):
Centos 6.3 (x86_64) witch Spacewalk 1.9 (postgres backend)

How reproducible:
Actiave / Generate Provisioning, build a tree for Centos 6.3 add GPG-Keys via Systems -> Kickstart -> GPG and SSL Keys 

*AND* 

within the generated Kickstart Profile by Systems -> Kickstart -> [profile name] -> System details -> GPG & SSL -> [activate / select your keys] -> update keys

Steps to Reproduce:
[see above]
  
Actual results:
only SSL-Keys are included within Kickstart-File, no GPG-Keys.

Expected results:
All selected Keys are included within Kickstart file, as state by the web-interface (e.g. "updated 5 keys").


Additional info:
caused by this bug, it is currently not possible to provisioning new system (means, you can kickstart systems but they're missing the relevant GPG-keys and will thus never update / install any rpm)

Comment 1 Michael Mráka 2013-03-12 07:46:29 UTC

*** This bug has been marked as a duplicate of bug 920292 ***

Comment 2 Eric Herget 2017-09-28 18:11:23 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.