On Thu, 16 Jan 2020 13:51:08 +, Alan Pittman
wrote
>Hi,
> Is anyone successfully syncing SLES 15 and SLES 15 SP1 repos from
>updates.suse.com to Spacewalk 2.8 (or 2.9)? If you are, can I compare
notes >with you please? I have been successfully syncing SLES11 and SLES12
repos >for some time
I have a spacewalk 2.9 server with CentOS 7 clients. When I run a scheduled
remote command on 50 systems, usually about half of the systems will get
marked as "failed" with the error "Invalid function call attempted (code
6)".
They all have the same configuration, and every line put in the remote
Thanks for the reply and to others that replied earlier. It appears that
downloading to SMT first is the way to go with this. That is the option that my
co-worker suggested. I wanted feedback from the list in case there was
something I wasn't doing correctly.
Alan
From:
I have been syncing using SUSE's SMT, now RMT internally, then syncing from
those to spacewalk. It seemed like the least amount of headache and I have
plenty of disk space for another virtual server. Now a few of the SLES 15
update repos have an issue and SUSE has a fix for their SUSE Manager
Hi
I am stilly syncing the SLES 15 repos with Spacewalk 2.9. However, I am moving
to Uyuni as SLES integration is better.
For syncing SLES 15 in Spacewalk I installed a temporary SLES15 VM, registered
it directly to Suse and then just copied the URL showed by "zypper lr --uri"
They look
Hello,
Not directly. The method I use for SLES 12 and 15 is to sync the target repos
to a local SMT server using smt-mirror, then use a scripted cron job to push
these package updates to custom Spacewalk channels via rhnpush. It's not
elegant but it works as a staging process with granular
Hi,
Is anyone successfully syncing SLES 15 and SLES 15 SP1 repos from
updates.suse.com to Spacewalk 2.8 (or 2.9)? If you are, can I compare notes
with you please? I have been successfully syncing SLES11 and SLES12 repos for
some time now, but haven't been able to get a SLES 15 repo to sync.
