I’m moving along on this implementation. I’ve successfully created Base Channels for CentOS5, CentOS6 for both the Base and Update Channels! I was also able to sync the errata using Steve’s script, but the erratas seem to be low (only 60 errata for CentOS6 32-bit, Just 6 for CentOS5 64-bit, 0 for CentOS5 32-bit and 318 for CentOS6 64-bit) does this sound correct?
The reason for this post has to do with my next objective… to register clients to the spacewalk server channels! I’ve created the activation keys per channel, but when I attempt to install the spacewalk client, per the instructions I found here: https://fedorahosted.org/spacewalk/wiki/RegisteringClients
I get the following problems.
On a CentOS5 32-bit client server, I installed the yum repository, but when I try to install the clients I get the following error messages:
[root nw-vp-001 CentOS5]# yum install rhn-client-tools rhn-check rhn-setup rhnsd m2crypto yum-rhn-plugin
(NOTE: fails the same with or without --enablerepo=spacewalk-client.repo)
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
http://repos.fedorapeople.org/repos/candlepin/subscription-manager/epel-6/i386/repodata/repomd.xml: [Errno 4] IOError: <urlopen error (111, 'Connection refused')>
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: subscription-manager. Please verify its path and try again
Here is the content of the repository:
[root nw-vp-001 CentOS5]# cat /etc/yum.repos.d/spacewalk-client.repo
name=Spacewalk Client Tools
proxy=http://nw-iwsva.corp.pcln.com:8080 ß I attempted to use our proxy setting, but it fails with or without this entry.
Any thoughts on what I’m doing wrong now?
From: spacewalk-list-bounces redhat com [mailto:spacewalk-list-bounces redhat com]
On Behalf Of Waldirio Manhães Pinheiro
Hello Marc, no problem
Sorry, I was talking about it with another Marc :-)
I'll for sure create a new post in my blog talking about how to configure erratas in SW. ASAP I'll post here.
On Fri, Nov 21, 2014 at 4:26 PM, Szabo, Marc <Marc Szabo priceline com> wrote:
I’ve only tried Steve’s script (errata-import.pl ) to this point… I feel that I’m very close to getting the desired results that I didn’t want to go into another direction until I’ve exhausted all attempts with this method.
My time has been temporarily redirected to another issue, but I plan to continue again as soon as I can. In the meantime, if you could provide more detailed instructions on how to use these methods, that would be greatly appreciated!
About the another errata script that you was trying a few days ago, no success !?
I'll write a post talking about how configure both scripts.
On Fri, Nov 21, 2014 at 1:08 PM, Matthew Madey <mattmadey gmail com> wrote:
You can export the variable on the commandline or in a script.
# export SPACEWALK_USER=your_username
# export SPACEWALK_PASS=your_password
On Fri, Nov 21, 2014 at 7:58 AM, Szabo, Marc <Marc Szabo priceline com> wrote:
I’m trying to use the CEFS script to pull down the CentOS6.5 errata into my spacewalk channel, and I’m still getting an error message that I’m not sure what it means:
I followed the instructions from Steve’s site:
· Download the latest errata XML file HERE (last updated: November 21, 2014)
· Download the errata-import.tar script HERE
· Extract the downloaded tarball in an empty directory (tar xf errata-import.tar)
· Make the main script executeable (chmod 755 errata-import.pl)
· Run the script and follow the instructions (./errata-import.pl)
[root nw-spcwlk-201 rh]# ls -tlrh
-rwxr-xr-x 1 root root 27K Oct 7 08:56 errata-import.pl
-rw-r--r-- 1 mszabo bin 5.9M Nov 21 03:29 errata.latest.xml
And this is what I get:
[root nw-spcwlk-201 rh]# ./errata-import.pl --server nw-spcwlk-201 --errata errata.latest.xml
INFO: Server is running API version 15
INFO: API version 15 is supported
ERROR: $SPACEWALK_USER not set
What and where do I set up a spacewalk user?
Ah so I thought you were having issues cloning exsiting errata in a channel. With a repo sync, there are some additional steps that need to be done since CentOS doesn’t publish errata in the repo (IIRC). There’s a few solutions for pulling and publishing errata to a CentOS channel such as CEFS, see here for a blog on how to use it http://blog.christian-stankowic.de/?p=5653&lang=en
Hope that proves helpful,
This is the command I issue from my Spacewalk Server:
[root nw-spcwlk-201 ~]# spacewalk-repo-sync --channel centos5-i386 --url http://mirror.centos.org/centos/5/os/i386/ --type yum
When the process completes, I only have the packages (2791) but 0 Erratas.
So are you saying that if I just include a “-z” option to the above command it would pull down the errata as well?
Errata should be cloned as part of the spacewalk-clone-by-date process based on the date provided by ‘-d’. The logic uses that to find the issue date of the errata, so if you are missing errata you may want to try the ‘-z’ option which expands the date criteria for finding relevant errata.
What issues are you having with errata sync?
This is great information… this is exactly what I’m trying to do. However, I’m having trouble sync’ing the Errata data. How are you sync’ing the errata, if you don’t mind me asking.
Thank you in advance for your help.
spacewalk-list-bounces redhat com
[mailto:spacewalk-list-bounces redhat com]
On Behalf Of Matthew Madey
This can easily be done, and I do something similar, but sync all Errata's on a monthly basis on patch tuesday.
Create your baseline channel that is fully up to date. Sync this baseline channel nightly, so it's always current, but don't keep any systems subscribed to it. Clone that channel, and use the clone channel for patching systems. If you want to add a single Errata to the cloned channel, you simply go to Channels-->Manage Software Channels-->Your cloned channel-->Errata then click Add. You'll see your baseline channel as the source, and can pick and choose whatever Errata or packages you'd like to add into your clone channel.
To refresh your clone channel on a monthly or quarterly basis, the easiest way to do this is setup a channel mapping configuration file, and use spacewalk-clone-by-date. Then you source your config file to that command like such:
spacewalk-clone-by-date --config=/etc/rhn/channel-maps/datacenter-channels-rhel6.conf -d 2014-10-14
The below document explains in detail how to setup this kind of configuration.
On Thu, Nov 20, 2014 at 9:15 AM, Nicolas Michel <be nicolas michel gmail com> wrote: