I've updated spacewalk and restarted it with spacewalk-service stop
followed by spacewalk-service start, but I'm still hitting this bug.
# rpm -q spacewalk-java
spacewalk-java-1.9.84-1.el5
Am I missing a step?
On Mar 18, 2013, at 4:15 AM, Jan Pazdziora wrote:
On Wed, Mar 13, 2013 at 08:09:44AM +0100, Jan Pazdziora wrote:
On Tue, Mar 12, 2013 at 04:03:32PM -0400, John Pittman wrote:
After upgrading my Spacewalk 1.8 system to 1.9 (and Centos 6.4), my
kickstarts no longer push the gpg keys assigned to each profile.
After a
kickstart finishes, I receive NOKEY errors on any package installs
from the
assigned channels (such as EPEL, spacewalk-client for osad, vmware-
tools,
etc)
I do not see anything in the current kickstart file that pushes
the keys
down, but all of this worked fine on 1.8. The keys are imported in
the "GPG
and SSL" list and assigned to the kickstart profile as
appropriate. After
manually importing the keys all is well.
Thoughts on where to start troubleshooting?
I believe you are hitting bug
https://bugzilla.redhat.com/show_bug.cgi?id=920292
which was fixed in Spacewalk nightly and we plan to release updated
1.9 packages as soon as people confirm that the issue is indeed
resolved in nightly.
Packages in Spacewalk 1.9 yum repos were updated.
--
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
