Since the CentOS distro does not include the needed registration client, It makes it hard to have a centOs machine registered after kickstarting. Currently we update certain packages in the %post, so for a centOS kickstart we could simply update/install all the needed packages in the %post section as well. Should be fairly simple.
Hmmm, would having such a client be useful in an extras repository? My limited understanding of why the client was not there was because it was not needed (eg you have yum and RHN was not OS. ) Would having a generic set of tools repository to register a client would be useful. And what src.rpm's would that need to be work with a spacewalk versus a RHN in particular?
BobFW1 trying to kickstart CentOs 5: BobFW1 jsherrill_laptop: I've tried to install the files manually [11:26] BobFW1 there are four files missing from the list [11:27] BobFW1 rhn-setup and its deps (rhnsd, rhn-check and rhn-client-tools) [11:28] BobFW1 rhnreg_ks works after installing those [11:28] jsherrill_laptop BobFW1, so wget isn't pull those down ? [11:29] BobFW1 no [11:30] BobFW1 wget pulls: rhnlib pyOpenSSL and libxml2-python [11:36] BobFW1 jsherrill_laptop: can the ks templates be edited manually? [11:36] BobFW1 to fix the problem So it looks like if we just have it install rhn-setup and its deps (rhnsd, rhn-check and rhn-client-tools), that might be all it needs to do...
After some more attempts: to get package installation working, the packages yum-rhn-plugin and spacewalk-client-tools are also required.
spacewalk-client-tools shouldn't be required, but rhn-client-tools should (Spacewalk client tools is just a rpm with repo data and GPG keys for http://stahnma.fedorapeople.org/spacewalk-tools/). But i will add yum-rhn-plugin. Thanks Bob!
Thanks. What I've seen now is that sometimes between the download of the kickstart and the download of the files (i mean rhnlib, pyOpenSSL and libxml2-python) the links have expired. The system will then download files, but instead of getting the files it gets the 'link expired or 404' page which it will try to install. As a workaround: maybe it is an option to put the required files in the '/pub/' folder next to the RHN-SSL cert to make sure they are always available?
Have fixed this and centos will be auto registered by spacewalk commit f5376cb97e47c0a917b2234636013a5d96f99cfb tree 7bd3654fa269c9a8cee19d07df4d495e05fa23d1 tree | snapshot parent 10133e8951eb8ff61bdbac8b1d0ecb31cf08752a commit | diff Note, when upgrading from spacewalk 0.4 to 0.5 (when released) you need to delete the file located in /var/lib/rhn/kickstarts that corresponds to your kickstart for it to be 'regenerated'. Alternatively you can simply update the kickstart in the WebUi and it will be regenerated.
Left out details of the fix. In the post section we now do this: wget -P /tmp/rhn_rpms http://columbia.devel.redhat.com:80/download/package/11ae129e7929ae4a2aaea997fe7c8bb9531844b4/1237594252226/1/22105/rhn-setup-0.4.17-8.el5.noarch.rpm http://columbia.devel.redhat.com:80/download/package/16b897afdb8c1142409436dc4b2ca1561948a04b/1237594252356/1/22104/rhn-client-tools-0.4.17-8.el5.noarch.rpm http://columbia.devel.redhat.com:80/download/package/910a03b9e1387579e3e8e6da9356c05564f43184/1237594252416/1/22100/rhn-check-0.4.17-8.el5.noarch.rpm http://columbia.devel.redhat.com:80/download/package/ebeace1dfa8749dde7a531c28bd7293aed1b8488/1237594252302/1/22115/yum-rhn-plugin-0.5.3-6.el5.6.noarch.rpm http://columbia.devel.redhat.com:80/download/package/3d61fada1bb53cdfd081cb01ea0092319e06c3cf/1237594252331/1/22129/rhnsd-4.6.1-1.el5.i386.rpm http://columbia.devel.redhat.com:80/download/package/22899d7024ca1f97860e777bee3c4b6d4c47f113/1237594252391/1/22103/rhnlib-2.2.5-1.el5.noarch.rpm rpm -Uvh --replacepkgs --replacefiles /tmp/rhn_rpms/optional/pyOpenSSL* /tmp/rhn_rpms/optional/rhnlib* /tmp/rhn_rpms/optional/libxml2-python* rpm -Uvh /tmp/rhn_rpms/*rpm for anything that isn't RHEL 2, 3, or 4. those files are pulled from the channel tree, so they can either be pushed to the base channel or a child channel.
Spacewalk 0.6 released