Hi

Our cluster is running Oscar 5.0 on Redhat Enterprise WS 4. Today I did a
kernel update on the head node and all client nodes. The steps I went
through:

1) Updated the head node using up2date.
2) Copied the new kernel rpms to /tftpboot/distro/redhat-el-ws-4-x86_64.
3) Regenerated the repository metadata cache:
yume --prepare --repo /tftpboot/distro/redhat-el-ws-4-x86_64
4) Updated a single node:
cexec :1  yume -y update
5) On reboot the node was still running the old kernel. So I tried updating
the compute image:
yume --installroot /var/lib/systemimager/images/compute
and attempted to PXE boot, but it still had the wrong kernel
6) Followed the instructions for a maunal setup of UYOK on p25 of the
install guide. Still not finding the new kernel.
7) Opted to hand edit the /boot/grub/grub.conf file. This worked so I copied
the file out to all the client nodes and rebooted them.

Questions:
a) Was my approach to this correct? Did I miss something out, or was I
always going to need to hand edit /boot/grub/grub.conf (which was originally
created by System Configurator)?

b) I had considered updating other packages on the head node and client, but
chose not to in case I hit other configuration issues. Do you recommend
updating all packages across the cluster? Are there any packages which might
cause me complications?

Thanks
Pen 
-- 
Penny Richardson                        
Research Computing Services
Kilburn Building                        
University of Manchester
Oxford Road
Manchester M13 9PL

email: [EMAIL PROTECTED]
tel: +44 161 275 6408


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Oscar-users mailing list
Oscar-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oscar-users

Reply via email to