Hello again,
still having problems,
I noticed that the errata-cache gets triggerd when a client refreshes its
repos or searches for updates. So I manually fired a "zypper ref -s" or a
"apt-get update" on every client connected to this spacewalk server. This
seems to have fixed "something". Sud
I am still having an issue understanding how to properly get patches from a
test/dev environment to a prod environment.
I currently have an environment called Test/Dev with an activation key. I
then created a base channel and the underlying child channels. I have set
it to sync to repositories the
Have you tried the spacewalk-manage-channel-lifecycle utility?
RPM which provides the utility: spacewalk-utils
/usr/bin/spacewalk-manage-channel-lifecycle --help
Examples:
List the base channels and child channels
/usr/bin/spacewalk-manage-channel-lifecycle -u $conf{org1user} -p
$conf{
There is a more direct way to do this. Please see my post from 3 weeks ago
under the subject “Spacewalk and RHEL Client Support”
From: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Morten Middelthon
Sent: Tuesday, January 12, 2016 1:35 AM
To: spacewa
Since I've seen no negative comments back on this thread, I'm going to post
here the outline of the process as it has worked for me. There may be other
ways to get the required keys by way of the Red Hat Portal. The ways that
previously worked for me seem to no longer work the same, so I'm no
