Thank you Jorge. I'll give it a try.
Daryl
From: spacewalk-list-boun...@redhat.com on
behalf of Jorge Ernesto Guevara Cuenca
Sent: Tuesday, October 27, 2015 3:59 PM
To: spacewalk-list@redhat.com
Hi,
I have a question about osad and subject alternate names and can't find
an answer in satellite or spacewalk docs.
We have a spacewalk 2.4 install with multiple NICs
- the primary FQDN resolves to a public NIC and spacewalk is setup with
that name
- a second DNS name, spacewalk-mng resolves
Oh... Wait a minute!!!Am 28.10.2015 8:01 vorm. schrieb Robert Paschedag
:
>
> As long as the root CA did NOT change, your steps should work and no client
> need to update anything.
>
> You don't need to clear the jabber db.
>
> Regards
> RobertAm 28.10.2015 3:14 vorm.
As long as the root CA did NOT change, your steps should work and no client
need to update anything.
You don't need to clear the jabber db.
Regards
RobertAm 28.10.2015 3:14 vorm. schrieb Jun :
>
> Hoping someone can offer some advice on the following situation.
>
> Have an
I'd like to create a clone-by-date-channel once a quarter so we can have
all machines updated to the same level. I had previously done this in a
SUSE Manager server with another company fairly easy, but for CentOS I'm
running into some questions with each repo. My spacewalk server is running
on
The CentOS 7 Extras repository lists multiple versions of etcd:
http://mirror.centos.org/centos/7/extras/x86_64/Packages/
Spacewalk detects that etcd-2.1 is available in the repo but the client
machine detects nothing higher than etcd-2.0.13.
# yum info etcd
I am running Spacewalk2.3 Server and proxies and while trying to install
larger package then approximately 20MB getting an error 500. Any suggestion
for troubleshooting? Proxy boxes options?
Error while executing packages action: Error Downloading Packages:
clamav-db-0.98.7-1.el6.x86_64: failed