[Spacewalk-list] question about patches pushed slow

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Is it possible that when we schedule to upgrade the packages on 24 machines that Spacewalk try one by one to patch the servers? We started a upgrade package roll out at 11:00 AM and now at 12:35 PM (Local time in Amsterdam) there are only 7

Re: [Spacewalk-list] question about patches pushed slow

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, why not disabling monitoring in the admin/Spacewalk Configuration ? Be sure to restart the spacewalk services via admin/Spacewalk Configuration/restart. Franz Michiel van Es schrieb: Hi, Is it possible that when we schedule to upgrade the

[Spacewalk-list] Nightly/git version question !

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, i have installed the lastest version for testing purposes. THe nighty build don't work as expected so i tested the git version and rebuild all packages. But the problem still extists. Neither rhnpush nor spacewalk-repo-sync is working. The

Re: [Spacewalk-list] GPG key URL

A little more explanation on this In spacewalk channel properties, if I put a file:// url in the GPG key URL field, yum on the client automatically imports the key. However if I have an http://; url in the field, yum does not automatically import. Anyone else having this problem or know