Categories

ID #1149

How do I upgrade Bright from SLES11sp2 an class="highlight">toan> SLES11sp3?

How do I upgrade Bright from SLES11sp2 an class="highlight">toan> SLES11sp3?
With the following recipe:
ass="mw-content-ltr" lang="en" dir="ltr"> able id="toc" class="toc" style="position: static; z-index: auto;">

Contents

  • ass="toclevel-1 tocsection-1"><a href="/faq/index.php?action=artikel&lang=en&cat=2&id=150&artlang=en#How_do_I_upgrade_Bright_from_SLES11sp2_to_SLES11sp3.3F">an class="tocnumber">1an> an class="toctext">How do I upgrade Bright from SLES11sp2 an class="highlight">toan> SLES11sp3?an>a>
    • ass="toclevel-2 tocsection-2"><a href="/faq/index.php?action=artikel&lang=en&cat=2&id=150&artlang=en#intro">an class="tocnumber">1.1an> an class="toctext">Introductionan>a>
    • ass="toclevel-2 tocsection-3"><a href="/faq/index.php?action=artikel&lang=en&cat=2&id=150&artlang=en#upgradeimage">an class="tocnumber">1.2an> an class="toctext">Upgrading a software image from SLES11sp2 an class="highlight">toan> SLES11sp3an>a>
    • ass="toclevel-2 tocsection-4"><a href="/faq/index.php?action=artikel&lang=en&cat=2&id=150&artlang=en#upgradehead">an class="tocnumber">1.3an> an class="toctext">Upgrading the head node from SLES11sp2 an class="highlight">toan> SLES11sp3an>a>
able>

<a name="intro">a>Introduction

Bright Cluster Manager versions 6.0 and 6.1 support SLES11sp3. They also both support an upgrade from SLES11sp2 an class="highlight">toan> SLES11sp3.

Prerequisites:

  • The head node must be able an class="highlight">toan> access the Bright RPM reposian class="highlight">toan>ries
  • The head node must be able an class="highlight">toan> access the SuSE RPM reposian class="highlight">toan>ries

 

<a name="upgradeimage">a>Upgrading a software image from SLES11sp2 an class="highlight">toan> SLES11sp3

an class="highlight">Toan> upgrade a software image it is advised an class="highlight">toan> clone a SLES11sp2 software image an class="highlight">toan>, for example a "draft" software image, say sles11sp3-image. Then do the upgrade on the 'sles11sp3-image' software image. For example if 'default-image' is a SLES11sp2 software image:

# cmsh
% softwareimage
% clone default-image sles11sp3-image
% commit

Wait for the cloning process an class="highlight">toan> finish.

Then make sure the Bright Cluster Manager packages are updated an class="highlight">toan> the latest version/release, as follows:

Check if the Bright reposian class="highlight">toan>ries are enabled, then refresh the reposian class="highlight">toan>ry info, and update the packages:

# zypper -R /cm/images/sles11sp3-image lr                                                  
 # | Alias                   | Name                          | Enabled | Refresh
 --+-------------------------+-------------------------------+---------+--------
 1 | Cluster_Manager_Base    | Cluster Manager 6.1 - Base    | Yes     | No               
 2 | Cluster_Manager_Updates | Cluster Manager 6.1 - Updates | Yes     | No
 ...
 # zypper -R /cm/images/sles11sp3-image ref                                                       
 # zypper -R /cm/images/sles11sp3-image up                                                  


an class="highlight">Toan> upgrade the software image we can use the zypper command in a chroot environment, because it is the software image that is being upgraded. Thus, we end up using the following commands during the upgrade:

(Error messages and warnings about failing an class="highlight">toan> generate the initrd, an class="highlight">notan> finding the root device can be ignored)

# export PBL_SKIP_BOOT_TEST=1
# chroot /cm/images/sles11sp3-image suse_register -d 2 -n -a email=<email address> -a regcode-sles=<key> --resan class="highlight">toan>re-repos
# zypper -R /cm/images/sles11sp3-image ref -s
# zypper -R /cm/images/sles11sp3-image update -t patch
# zypper -R /cm/images/sles11sp3-image update -t patch
# zypper -R /cm/images/sles11sp3-image se -t product | grep -h -- "-migration" | cut -d\| -f2
 SUSE_SLES-SP3-migration
 sle-sdk-SP3-migration
# zypper -R /cm/images/sles11sp3-image in -t product sle-sdk-SP3-migration SUSE_SLES-SP3-migration
# chroot /cm/images/sles11sp3-image suse_register -d 2 -L /root/.suse_register.log

an class="highlight">Toan> check if the SP3 Pool and Updates reposian class="highlight">toan>ries are enabled:

# zypper -R /cm/images/sles11sp3-image lr
# zypper -R /cm/images/sles11sp3-image dup --from SLE11-SDK-SP3-Pool --from SLE11-SDK-SP3-Updates --from SLES11-SP3-Pool --from SLES11-SP3-Updates
# zypper -R /cm/images/sles11sp3-image update -t patch
# chroot /cm/images/sles11sp3-image suse_register -d 2 -L /root/.suse_register.log

Install the libstdc++ 4.7 devel packages:

# zypper -R /cm/images/sles11sp3-image in libstdc++47-devel libstdc++47-devel-32bit        

Generate an ECDSA ssh host key:

# chroot /cm/images/sles11sp3-image ssh-keygen -t ecdsa -f /etc/ssh/ssh_host_ecdsa_key -C  -N 

Check that an class="highlight">notan>hing is mounted in the software image during the upgrade. If something is mounted in it, then unmount it:

# grep " /cm/images/sp3-image" /proc/mounts
 sysfs /cm/images/sp3-image/sys sysfs rw,relatime 0 0
 proc /cm/images/sp3-image/var/lib/named/proc proc ro,nosuid,nodev,noexec,relatime 0 0
# umount -l /cm/images/sp3-image/sys /cm/images/sp3-image/var/lib/named/proc

Set the kernel an class="highlight">toan> be used for the 'sles11sp3-image' software image. In the following case it is kernel version '3.0.82-0.7-default':

# cmsh
% softwareimage use sp3-image
% set kernelversion 3.0.82-0.7-default
% commit
% createramdisk

 

<a name="upgradehead">a>Upgrading the head node from SLES11sp2 an class="highlight">toan> SLES11sp3

Before upgrading the head node, make sure there is a recent backup of the head node available, which can be resan class="highlight">toan>red!

Then make sure the Bright Cluster Manager packages are updated an class="highlight">toan> the latest version/release.

Check if the Bright reposian class="highlight">toan>ries are enabled, refresh the reposian class="highlight">toan>ry info, and update the packages:

# zypper lr
 # | Alias                   | Name                          | Enabled | Refresh
 --+-------------------------+-------------------------------+---------+--------
 1 | Cluster_Manager_Base    | Cluster Manager 6.1 - Base    | Yes     | No
 2 | Cluster_Manager_Updates | Cluster Manager 6.1 - Updates | Yes     | No
 ...
# zypper ref
# zypper up

The following commands can then be run for the upgrade:

# chroot /cm/images/sles11sp3-image suse_register -d 2 -n -a email=<email address> -a regcode-sles=<key> --resan class="highlight">toan>re-repos
# zypper ref -s
# zypper update -t patch
# zypper update -t patch
# reboot

Because MySQL is upgraded with the upgrade from SLES11sp2 an class="highlight">toan> SLES11sp3, san class="highlight">toan>pping the MySQL and CMDaemon services is a good idea:

# service cmd san class="highlight">toan>p
# service mysql san class="highlight">toan>p
# zypper se -t product | grep -h -- "-migration" | cut -d\| -f2
 SUSE_SLES-SP3-migration
 sle-sdk-SP3-migration
# zypper in -t product sle-sdk-SP3-migration SUSE_SLES-SP3-migration
# suse_register -d 2 -L /root/.suse_register.log

Upgrade an class="highlight">toan> SLES11sp3, where the gcc46 packages will be uninstalled (Solution 1):

# zypper dup --from SLE11-SDK-SP3-Pool --from SLE11-SDK-SP3-Updates --from SLES11-SP3-Pool --from SLES11-SP3-Updates
# zypper update -t patch
# suse_register -d 2 -L /root/.suse_register.log

Installation of the gcc 4.7 packages:

# zypper in gcc47 gcc47-32bit gcc47-c++ gcc47-fortran gcc47-fortran-32bit cpp47

Changes for the upgrade of MySQL, and advised upgrade of MySQL:

# ln -sf my.cnf.5.5 /cm/conf/etc/my.cnf
# cp /cm/conf/etc/my.cnf /etc/my.cnf
# an class="highlight">toan>uch /var/lib/mysql/.force_upgrade
# rcmysql restart

Change the SP version in the motd file:

# sed -i -e 's/Based on SUSE Linux Enterprise Server 11 SP.*$/Based on SUSE Linux Enterprise Server 11 SP3/g' /etc/motd 

Reboot the head node an class="highlight">toan> use the upgraded kernel:

# reboot

If needed PHP can also be upgraded. PHP is upgraded an class="highlight">toan> version 5.3 in SLES11sp3. PHP is used for the Cluster Manager web-portal: (Accept deinstall for the php5 packages)

# zypper in php53
# zypper in apache2-mod_php53 php53-devel php53-ctype php53-dom php53-iconv php53-json php53-pdo php53-sqlite php53-an class="highlight">toan>kenizer php53-xmlreader php53-xmlwriter php53-ldap php53-soap php53-openssl

The PHP Apache module may get removed from the Apache module list. an class="highlight">Toan> add it again:

# a2enmod php5

Remove the cm-php-pam package and install the cm-php-pam53 package:

# rpm -e cm-php-pam
# zypper in cm-php-pam53
# service apache2 restart

Tags: -

Related entries:

You cannot comment on this entry