<div dir="ltr"><div class="gmail_extra"> Hi Paul, I checked and found that the activation key seems to be set right. I found the Centos 6 Base channel and child channels including Spacewalk and Epel all configured. If I go to the Activated systems tab I also see my server listed there. Any further ideas? ThanksJason <a name="_MailOriginal">From:</a> <a href="mailto:spacewalk-list-bounces@redhat.com">spacewalk-list-bounces@redhat.com</a> [mailto:<a href="mailto:spacewalk-list-bounces@redhat.com">spacewalk-list-bounces@redhat.com</a>] On Behalf Of Paul Robert Marino Sent: Monday, June 15, 2015 6:13 PM To: <a href="mailto:spacewalk-list@redhat.com">spacewalk-list@redhat.com</a> Subject: [External] Re: [Spacewalk-list] Registering Offline servers to Spacewalk 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 <<a href="mailto:jason.calafiore@gmail.com" target="_blank">jason.calafiore@gmail.com</a>> wrote: 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 HOSTNAME=<a href="http://spacewalk-server.com" target="_blank">spacewalk-server.com</a> ORG_CA_CERT=RHN-ORG-TRUSTED-SSL-CERT ORG_CA_CERT_IS_RPM_YN=0 USING_SSL=1 USING_GPG=1 REGISTER_THIS_BOX=1 ALLOW_CONFIG_ACTIONS=1 ALLOW_REMOTE_COMMANDS=1 FULLY_UPDATE_THIS_BOX=1 After running the script locally on the CentOS server. I received the following error about setting permissions for config management. Is there something that I missed in the configuration? REGISTRATION ------------ * registering *** this system should now be registered, please verify *** * setting permissions to allow configuration management NOTE: use an activation key to subscribe to the tools channel and yum upgrade rhncfg-actions Error setting permissions for configuration management. Please ensure that the activation key subscribes the system to the tools channel and yum updates rhncfg-actions. Thanks Jason From: <a href="mailto:spacewalk-list-bounces@redhat.com" target="_blank">spacewalk-list-bounces@redhat.com</a> [mailto:<a href="mailto:spacewalk-list-bounces@redhat.com" target="_blank">spacewalk-list-bounces@redhat.com</a>] On Behalf Of Paul Robert Marino Sent: Monday, June 15, 2015 1:20 PM To: <a href="mailto:spacewalk-list@redhat.com" target="_blank">spacewalk-list@redhat.com</a> Subject: [External] Re: [Spacewalk-list] Registering Offline servers to Spacewalk 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 repos. you can use those URLs with the yum command to install the spacewalk client I usually create a set of disabled repos for them under /etc/yum.repos.d with no gpg check and enable them via the yum command during the install. On Mon, Jun 15, 2015 at 11:58 AM, Kalchik, Jeffery <<a href="mailto:JDKalchik@landolakes.com" target="_blank">JDKalchik@landolakes.com</a>> wrote: 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 web console. It’ll end up named bootstrap.sh or some such. client_config_update.py is part of the bootstrap tools. Jeff Kalchik Systems Engineering Land O’Lakes On Fri, Jun 12, 2015 at 11:33 AM, Jason Calafiore <<a href="mailto:jason.calafiore@gmail.com" target="_blank">jason.calafiore@gmail.com</a>> wrote: Hi Jeff, Thanks for the help. I just wanted to clarify a few things 1. When you say install "Spacewalk client tools & Libraries first", does that mean the following steps? rpm -Uvh <a href="http://yum.spacewalkproject.org/2.3-client/RHEL/7/x86_64/spacewalk-client-repo-2.3-2.el7.noarch.rpm" target="_blank">http://yum.spacewalkproject.org/2.3-client/RHEL/7/x86_64/spacewalk-client-repo-2.3-2.el7.noarch.rpm</a> rpm -Uvh <a href="http://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm" target="_blank">http://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm</a> yum install rhn-client-tools rhn-check rhn-setup rhnsd m2crypto yum-rhn-plugin 2. I did find the bootstrap script /var/www/html/pub/bootstrap/client_config_update.py is this it? If so this is run after the steps above? 3. This method still seems to involve creating a local yum repo on the spacewalk server to serve out the packages for offline servers. As a result I'll need to still login to a machine and create a .repo file on the remote server that needs to be registered. Isn't there any way to automate registration of servers with a script? It surprising spacewalk doesn't have an easier way to handle this. 4. Once I register the remote servers, will i be able to update the spacewalk client packages provided they are subscribed to the spacewalk channel? Thank you, Jason ________________________________________________________________________________________________________ Good morning, Jason, et al. To register an existing server, you’ll need to install the Spacewalk client tools & libraries first. That’ll extend the capabilities of yum (or the appropriate update manager,) to communicate with a Spacewalk service. Once that’s done, you’ll need to run /usr/sbin/rhn_register, /usr/sbin/rhnreg_ks or the bootstrap script (bootstrap runs rhnreg_ks internally.) The registration script normally gets generated into /var/www/html/pub/bootstrap. The bootstrap script does perform some other activities, such as a full system update (through yum, zypper, etc.,) downloading SSL certs, and so forth. You might want to run it, you also might want to manually register your clients, depending on your local requirements. Jeff Kalchik Systems Engineering Land O’Lakes From: <a href="mailto:spacewalk-list-bounces@redhat.com" target="_blank">spacewalk-list-bounces@redhat.com</a> [<a href="mailto:spacewalk-list-bounces@redhat.com" target="_blank">mailto:spacewalk-list-bounces@redhat.com</a>] On Behalf Of Jason Calafiore Sent: Thursday, June 11, 2015 7:55 AM To: <a href="mailto:spacewalk-list@redhat.com" target="_blank">spacewalk-list@redhat.com</a> Subject: Re: [Spacewalk-list] Registering Offline servers to Spacewalk Hi Marino, I have add the spacewalk repo as a child for my base channels, but I am dealing with the initial implementation of spacewalk in my existing environment, so I don't understand how kickstart would be applicable. Can you explain a little more about the registration script? Where is it exactly and how could i modify it as you are suggesting to register existing servers? Thank you, Jason _______________________________________________________________ I always include the spacewalk clients in a child repo of my base channels then include it in my kickstarts. Then I can view the kickstart and pick out the URI‎ yum has an option to install using an adhock yumrepo. Also you may not be aware of this but spacewalk generates a boilerplate registration script for you in the public directory for apache you can use as a template to modify into your own custom registration script. Additionally yum and the rpm command can install packages over a network by specifying the URI as the package name. <table class="" border="0" cellpadding="0" width="100%" style="width:100%;border-spacing:0px;background-image:initial;background-repeat:initial"> <tbody><tr> <td style="padding:0.75pt;font-size:initial;text-align:initial"> From: Jason Calafiore Sent: Wednesday, June 10, 2015 17:51 To: <a href="mailto:spacewalk-list@redhat.com" target="_blank">spacewalk-list@redhat.com</a> Reply To: <a href="mailto:spacewalk-list@redhat.com" target="_blank">spacewalk-list@redhat.com</a> Subject: [Spacewalk-list] Registering Offline servers to Spacewalk </td> </tr> </tbody></table> Hi All, I am trying to figure out a an easy to register servers that are already created and offline without have to reach out to the internet to get the necessary packages. The only way I could do this was to do the following below by creating a yum repo with the necessary packages and then on a client server configure a .repo file that get the necessary packages. Is there any easier way to do this? I would think spacewalk would have an easy way to register clients especially offline servers. I had asked this before and someone suggested a scripts on github, but couldn't figure it out. Thanks, Jason Create Local Repo on the spacewalk Server mkdir /var/www/html/pub/spacewalk-client cd /var/www/html/pub/spacewalk-client repotrack -a x86_64 -p /var/www/html/pub/spacewalk-client rhn-client-tools rhn-check rhn-setup rhnsd m2crypto yum-rhn-plugin rm *i686* -f wget <a href="http://yum.spacewalkproject.org/2.3-client/RHEL/7/x86_64/spacewalk-client-repo-2.3-2.el7.noarch.rpm" target="_blank">http://yum.spacewalkproject.org/2.3-client/RHEL/7/x86_64/spacewalk-client-repo-2.3-2.el7.noarch.rpm</a> wget <a href="http://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm" target="_blank">http://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm</a> creapterepo /var/www/html/pub/spacewalk-client Register Server to Spacewalk vi/etc/yum.repos.d/spacewalk-local.repo [spacewalk-local-install-repo] name=Spacewalk Client Install baseurl=<a href="http://spacewalk-server.com/pub/spacewalk-client" target="_blank">http://spacewalk-server.com/pub/spacewalk-client</a> gpgcheck=0 gpgkey= enabled=1 Disable other repos in /yum.repos.d yum install rhn-client-tools rhn-check rhn-setup rhnsd m2crypto yum-rhn-plugin # rpm -Uvh <a href="http://ghslspacewalk.ds.src.bah.com/pub/rhn-org-trusted-ssl-cert-1.0-1.noarch.rpm" target="_blank">http://spacewalk-server.com/pub/rhn-org-trusted-ssl-cert-1.0-1.noarch.rpm</a> rhnreg_ks --serverUrl=<a href="https://spacewalk-server.com/XMLRPC--sslCACert=/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT--activationkey=1-centos-server-7" target="_blank">https://spacewalk-server.com/XMLRPC --sslCACert=/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT --activationkey=1-centos-server-7</a> This message may contain confidential material from Land O'Lakes, Inc. (or its subsidiary) for the sole use of the intended recipient(s) and may not be reviewed, disclosed, copied, distributed or used by anyone other than the intended recipient(s). If you are not the intended recipient, please contact the sender by reply email and delete all copies of this message. _______________________________________________ Spacewalk-list mailing list <a href="mailto:Spacewalk-list@redhat.com">Spacewalk-list@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a> </div></div>