<HTML> <HEAD> <TITLE>FW: [Spacewalk-list] Spacewalk setup questions</TITLE> </HEAD> <BODY> Please ignore my post below. I had overlooked the key step of deploying my Spacewalk GPG key to clients. Everything appears to be humming along nicely now. Along with Michael’s response to my Cobbler question, I think I’m all set! Thanks! Craig ------ Forwarded Message From: Craig Pendleton <<a href="craig.pendleton@healthlanguage.com">craig.pendleton@healthlanguage.com</a>> Reply-To: <<a href="spacewalk-list@redhat.com">spacewalk-list@redhat.com</a>> Date: Wed, 27 May 2009 13:32:41 -0600 To: <<a href="spacewalk-list@redhat.com">spacewalk-list@redhat.com</a>> Subject: [Spacewalk-list] Spacewalk setup questions I am a new user of Spacewalk, currently working through initial setup for RHEL and CentOS base and “client tools” child channels. I’ve run into a host of problems, and I’m hoping some kind soul can help me sort these out. Please excuse the long post. I’ve read through most of the Spacewalk Wiki and Redhat Satellite/RHN documentation, and I can’t seem to track these issues down. What I’m looking to accomplish is: <OL><LI>Kickstart RHEL and CentOS clients that install all required Spacewalk client components and self-register to OS and config file channels with my Spacewalk server <LI>Automatically deploy errata, updates, and config files to these systems based on their channel membership, through Spacewalk. Remote commands as well. <LI>Security is not very important in my environment, as these are throw-away test systems on an isolated segment </OL> I have done the following: <OL><LI>Build spacewalk server, according to the following instructions: <a href="https://fedorahosted.org/spacewalk/wiki/HowToInstall">https://fedorahosted.org/spacewalk/wiki/HowToInstall</a> <LI>I’ve followed these instructions for channel/kickstart setup for both RHEL and CentOS: <a href="https://fedorahosted.org/spacewalk/wiki/HowToKickstartCobbler">https://fedorahosted.org/spacewalk/wiki/HowToKickstartCobbler</a> <LI>Run “cobbler buildiso” for a bootstrap install disk, as I can’t use cobbler’s integrated DHCP/PXE in my environment </OL> What is working: <OL><LI>Clients kickstart fine, using the buildiso created with cobbler. <LI>Clients apparently self-register to the correct base and child OS channels, via a rhnreg_ks command in my ks.cfg <LI>Clients show entitlements management, virtualization, provisioning, monitoring following kickstart </OL> What I can’t get working properly: 1. Install all required client tools during kickstart. All the client RPMs are in the “client tools” child channel that the client is kickstarting from, but none of these packages get installed. Installing these from Spacewalk also fails. 2. Since client tools weren’t being installed during kickstart, I’ve even tried a bunch of “wget <a href="http://mirror.whatever.com/package.rpm">http://mirror.whatever.com/package.rpm</a> && yum localinstall package.rpm” installs in my ks.cfg. For some reason kickstart always hangs on jabberpy and koan installs. 3. Push any packages or config files to clients. I can schedule them in Spacewalk, but they sit in a pending state until they fail. Remote commands do the same. 4. “OSA Status” is showing offline on the system page in Spacewalk 5. Since I cannot use DHCP/PXE for this in my environment, I would like to pass a hostname parameter to kickstart when booting from the cobbler buildiso. Is that possible? Thank you in advance for any assistance. I’ll be happy to provide any information you might need to help me, but I’m not sure where to start looking at this point. Regards, Craig <HR ALIGN=CENTER SIZE="3" WIDTH="100%">NOTICE BY HEALTH LANGUAGE, INC. This message, as well as any attached document, contains information from Health Language, Inc. that is confidential. The information is intended only for the use of the addressee named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on the contents of this message or its attachments is strictly prohibited, and may be unlawful. If you have received this message in error, please delete all electronic copies of this message and its attachments, if any, destroy any hard copies you may have created, without disclosing the contents, and notify the sender immediately. Unless expressly stated otherwise, nothing contained in this message should be construed as a digital or electronic signature, nor is it intended to reflect an intention to make an agreement by electronic means. <HR ALIGN=CENTER SIZE="3" WIDTH="95%">_______________________________________________ Spacewalk-list mailing list <a href="Spacewalk-list@redhat.com">Spacewalk-list@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/spacewalk-list">https://www.redhat.com/mailman/listinfo/spacewalk-list</a> ------ End of Forwarded Message <hr> NOTICE BY HEALTH LANGUAGE, INC. This message, as well as any attached document, contains information from Health Language, Inc. that is confidential. The information is intended only for the use of the addressee named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on the contents of this message or its attachments is strictly prohibited, and may be unlawful. If you have received this message in error, please delete all electronic copies of this message and its attachments, if any, destroy any hard copies you may have created, without disclosing the contents, and notify the sender immediately. Unless expressly stated otherwise, nothing contained in this message should be construed as a digital or electronic signature, nor is it intended to reflect an intention to make an agreement by electronic means. </BODY> </HTML>