Good morning.
It’s been a few years since I registered servers that were not originally built
within Spacewalk (or Satellite.) I’d suspect that the rpm yum commands you
list in #1 are at least a good start.
For the bootstrap script, see Admin/Spacewalk Configuration/Bootstrap Script in
the
Hi I am trying to get to the bottom of this issue but I have hit a wall.
Any hints would be greatly appreciated. The action gets scheduled but never
gets picked up. From last week the jobs are still Queued and have not
been picked up yet. I have a task to do this same patching to a larger pool
of
Just to complement
About RHEL you can download and use the SW to manager in your servers,
pay attention in your quantity, if you have 10 subscriptions, you may
support only 10 servers.
Have a great day!
__
Atenciosamente
Waldirio
msn: waldi...@gmail.com
Skype: waldirio
Site:
Hello Jason,
About your first question, I'm not sure about SLES, btw if you have 10
subscriptions or licenses (i don't know if SLES subscribe as license)
and download the packages to update only 10 servers, you are in
compliance, if you download from site or use another automated system
to do it,
Hello Jason
My recommendation is you configure epel as a repository / child
channel and leave the SW sync automatically for you, btw about your
question, check if you have the file in this path and / or the file
name.
Take Care
__
Atenciosamente
Waldirio
msn: waldi...@gmail.com
Hi Waldirio,
Actually my question is not about Licensing, it's really about Vendor
Support. For Licensing we do not have any issues.
I am more concerned about using 3rd party packages here. I'd like to know
if anyone who gets support from RedHat, Novell, Canonical, etc, if they use
spacewalk to
sorry for the delayed response
the reason i mentioned a kickstart script is if you create one that
includes the spacewalk client and EPEL repos you will see in the beginning
of the kickstart script the lines where the URL's for those channels that
anaconda is using, and they are essentially yum
Hi Paul, Jeff
Appreciate your help. I was able to get run the bootstrap scripts on my
centOS 6.6 server with the follow configuration.
ACTIVATION_KEYS=1-centos-server-66
ORG_GPG_KEY=
# can be edited, but probably correct:
CLIENT_OVERRIDES=client-config-overrides.txt
Ok
I'll talk from Red Hat, you will be in compliance using SW to
distribute your packages (attention only in the subscription
quantity).
About packages, you can distribute for example in your SW softwares
from vmware, zabbix, epel, etc, so the Red Hat company will not
support you in 3d packages
Oh its an error in the activation key
in the activation key you can specify channels to join make sure you tell
it to subscribe to the spacewalk client and EPEL channels in the key.
On Mon, Jun 15, 2015 at 3:44 PM, Jason Calafiore jason.calafi...@gmail.com
wrote:
Hi Paul, Jeff
Appreciate
Hi All,
I have recently done a spacewalk upgrade in RHEL7 from 2.3 to 2.4.
Everything looked to be fine except now when I login I get this error.
* When I login to spacewalk now I get this error
Internal Server Error
The server experienced a problem which prevented your request from
11 matches
Mail list logo
