So here's a question... I kickstarted a new system using a similar list of packages (to that listed by Jeffrey below) in my ks profile. They all installed but osad failed to start until I installed jabberpy (which is in the EPEL repo). Is there any way around that? Since I didn't have a previous notion of that client it wasn't subscribed to any software channels.
Along those lines, when I ks a new system there are a number of things I want to do on all the systems in a particular configuration channel. E.g... - add the "monitoring" entitlement (management and provisioning are already added) - add location info blah etc. - subscribe to the CentOS_x86_64 software channel all 4 of its child channels - run "/etc/init.d/osad start" - subscribe system to a default configuration channel - join a default system group - deploy managed config files (e.g. /etc/ntp.conf) - configure scout monitoring for load, mem, and disk checks Obviously there are ways to script this with RHN commands, although I am not familiar enough to do that yet. But does the spacewalk UI provide some other means that I am not seeing for doing some of these things. Basically I am going to use this to roll-out/kickstart new Linux VMs and want to automate as much as possible with Spacewalk. Thanks. --Ryan From: [email protected] [mailto:[email protected]] On Behalf Of Jeffrey Watts Sent: Wednesday, February 03, 2010 12:18 PM To: [email protected] Subject: Re: [Spacewalk-list] rhn_check I think rhn-profile-sync will do that. By the way, here are the additional packages that my activation key installs when I register an existing system into Satellite: rhnmd rhn-custom-info rhncfg-management rhncfg-client rhncfg-actions rhncfg osad I'm not sure if there are more (or less) with the current Spacewalk, but you ought to make sure you have these installed (though rhnmd is only necessary if you're doing monitoring). Jeffrey. On Wed, Feb 3, 2010 at 2:08 PM, Kennedy, Ryan <[email protected]<mailto:[email protected]>> wrote: Is there any way to force an update of a system's IP address (e.g. I changed the IP address and want it to update in Spacewalk) w/o manually intervening? What worked was scheduling a hardware list refresh for the system and then running rhn_check from that host (or wait for it to do it automatically). It didn't auto-fire with osad, so I am assuming osa-dispatcher must be using the old IP (as Spacewalk has no notion of the new one at this point). Once I ran rhn_check from the system it updated the IP in Spacewalk and all is well. Is this the correct/best process for changing a managed system's IP address in Spacewalk? DISCLAIMER: Information contained in this message may be privileged and confidential. If the reader of this message is not the intended recipient, be notified that any dissemination, distribution or copying of this communication is strictly prohibited. If this communication is received in error, please notify the sender immediately by replying to the message and deleting from your computer. Thank you
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
