Have you imported your keys to Spacewalk (found under Systems ->
Kickstart -> GPG and SSL Keys)?
Have you associated those keys to your kickstart profile? (System ->
Kickstart -> Profiles -> <SL6 profile> -> System Details -> GPG and SSL ?
You should be able to read the kickstart file and see your keys being
imported after this line:
# --Begin Spacewalk command section
Jonathan
On 08/10/2011 10:47 AM, Brandon Young wrote:
Hi all. I am in the process of setting up a Spacewalk 1.5 server and
am attempting to create a kickstart. My channel setup looks something
like:
Scientific Linux 6
EPEL 6
SL6 Fastbugs
SL6 OS
SL6 Updates
SL6 With Tools
Spacewalk Client
Where Scientific Linux 6 is the base channel, and everything else is a
child channel.
I noticed that the Spacewalk server reports that the kickstart fails,
quite consistently. Upon closer inspection, I see that the reason it
is failing is because it is not importing some/all of the GPG keys
associated with the locally mirrored repos. For example, looking at
the History tab of the kickstart event for a system, it tells me:
Summary: Package Install scheduled by (none)
Details: This action will be executed after 08/10/11 9:30:45 AM CDT.
This action's status is: Failed.
The client picked up this action on 08/10/11 9:30:48 AM CDT.
The client completed this action on 08/10/11 9:32:12 AM CDT.
Client execution returned "Error while executing packages action:
Refusing to automatically import keys when running unattended. [[6]]"
(code -1)
Packages Scheduled:
* rhncfg-client
* rhn-virtualization-host
* rhncfg
* rhncfg-actions
Time: 08/10/11 9:30:45 AM CDT
I've also noticed this behavior when trying to schedule a package
install after kickstart. Google doesn't come up with anything useful
on this error. Poking around in the mailing list archives, I don't
see anything similar either, which leads me to believe I'm doing
something silly. I am aware that I can edit
/etc/yum/pluginconf.d/rhnplugin.conf to 'gpgcheck=0' and this problem
stops, but that strikes me as the wrong way to resolve this issue.
Can anyone give me pointers on a better way to resolve this problem?
Am I possibly forgetting a step somewhere? Is there a config setting
that affects this behavior?
I am happy to provide whatever command output or config settings
necessary in discovering the solution, I'm just not sure what info
would be relevant in getting started.
Thanks in advance.
--
Brandon
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
--
Jonathan DeHaan
Linux Systems Engineer
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
