Cool Solutions

Patching and Upgrading OES 2 SP1 to OES 2 SP2



By:

November 17, 2009 4:47 pm

Reads: 15982

Comments:5

Score:0

This article describes upgrading OES 2 SP1 to OES 2 SP2 using several different methods.

For this document, I have used nu.novell.com as the patch channel. The same methods with required modifications should work with internal patch servers as well.

Table of Contents:

1. Media Upgrade
     1.1 Media Upgrade on Physical OES Server
     1.2 Media Upgrade on DSFW Server
     1.3 Media Upgrade on XEN
2. Channel Upgrade
     2.1 RUG cli Method
     2.2 RUG GUI Method
     2.3 YaST Method
3. Silent and Interactive Upgrade
4. TroubleShooting

 

1. Media Upgrade

Supported Scenarios:

  • OES 1 -> OES 2 SP2
  • OES 2 -> OES 2 SP2
  • OES 2 SP1 -> OES 2 SP2
Note: DSFW Upgrade is supported only from OES 2 SP1 to OES 2 SP2.

1.1 Media Upgrade on Physical OES Server

  1. Insert the SLES10SP3 Boot disk on the OES 2 SP1 server and proceed with the Installation.
  2. During Installation Mode choose the option “Update” and click “Include add-on products”.
  3. Click “Next” and enter the OES 2 SP2 build path.

  4. Click “Accept” and start the Upgrade process.

  5. After the Installation is done, during the OES configuration, click “Upgrade” to upgrade eDirectory.

  6. Enter the admin credentials for the upgrade to proceed.

1.2 Media Upgrade on DSFW Server

The DSFW Media is same as a normal Linux Upgrade except that the DSFW administrator password has to be provided during the eDirectory Upgrade.

1.3 Media Upgrade on XEN

  1. Install OES 2 SP1 as VM Guest on the Host Machine
  2. Create a directory on the VM Host server to copy the RAM disk and configuration files of SLES10SP3 (/upgrade)
  3. Check the kernel type on VM guest using the command uname -r, the kernel ends either with xen or xenpae. Based on this kernel type the file has to be copied into the upgrade directory of the VM Host server
  4. Shutdown the VM Guest
  5. Copy the vmlinuz-xen and initrd-xen or vmlinuz-xenpae and initrd-xenpae(based on kernel type) from the Installation source of SLES10SP3 to the upgrade directory of the VM Host server
  6. Copy the VM Guest configuration file into a file to modify for Upgrade process

    Run this command on the VM host

    xm list -l <Name of VM Guest> > /<path ofupgrade dir>/modify_config_file.sxp
    
    

    eg:

    xm list -l oes2sp1 > /upgrade/modify_config_file.sxp
    
    
  7. Make a copy of this modified_config_file before modifying and name it as unmodified_config_file and create the two files under the same path /upgrade
  8. Delete the VM Guest configuration from the XEN database using xm delete <VM Guest name>
  9. Open the Modified_config_file.sxp and modify the following parameters
    1. Remove the line that begins with (bootloader_args ….
    2. Change the line from

      (on_reboot restart) to (on_reboot destroy)
    3. Remove the line that contains

      (bootloader /usr/lib/xen/boot/domUloader.py)
    4. Modify the kernel line so that it reads:

      (kernel /upgrade/vmlinuz-xen or /upgrade/vmlinuz-xenpae)
    5. Insert a ramdisk line below the kernel line

      (ramdisk /upgrade/initrd-xen or /upgrade/initrd-xenpae)
    6. In the args line between the quotes insert the SLES10SP3 Installation path

      (args ‘install=http://<ip addr>/sles10sp3/<arch>’)

      unmodified_config_file.sxp:

      modified_config_file.sxp:

  10. Start the Upgrade by entering this command on VM host server:
    xm create -F /<path of upgrade dir>/modify_config_file.sxp
    	

    eg:

    xm create -F /upgrade/modify_config_file.sxp
    	

    Now the VM Guest will appear on the virt-manager as running, open the VM Guest and the enter the details for Upgrade

  11. After the first stage of the Upgrade i.e Perform Update, the VM Guest will disappear from the virt-manager.

    Create the VM Guest again to continue the second stage of the Upgrade process by entering the following command on VM Host server:

    xm new -F /<path of upgrade dir>/unmodify_config_file.sxp
    

    eg:

    xm new -F /upgrade/unmodify_config_file.sxp
    

    Now continue with the second stage of Upgrade process.

2. Channel Upgrade

2.1 Upgrading the Server using command line (RUG cli)

  1. Register the server in the Novell Customer Center using YaST -> Software -> Customer Center Configuration or through command:
    suse_register -a email=<email-address> -a regcode-sles=code  -a regcode-oes=code
    
    
  2. Verify the Service types using:
       rug sl
    
       # | Status  | Type | Name                                | URI
       --+---------+------+-------------------------------------+--------------
       1 | Active  | ZYPP | Novell Open Enterprise Server 2 SP1 | http://164.99.147....
       2 | Active  | ZYPP | SUSE Linux Enterprise Server 10 SP2 | http://164.99.147....
       3 | Active  | NU   | https://nu.novell.com               | https://nu.novell.com
       
       
  3. Install the move-to-oes2-sp2 patch on the server using the rug command
    rug in -t patch move-to-oes2-sp2 && rug ping -a
    	
    	

    (Using GUI Method, click Software Updater Icon and select move-to-oes2-sp2 patch and click Update)

  4. Check SLES10-SP3-Updates and OES2-SP2-Updates using rug pch
  5. Install the recommended patches in the channel:
    rug up -t patch -g recommended && rug ping -a 
    	
    	
  6. To finish the upgrade, reboot the server.
    Note: For Silent Upgrade, create an answer file and reboot the server
  7. After reboot, the upgrade proceeds with the OES configurations.

2.2 Upgrading the server using GUI (Rug GUI Method)

  1. Click the novell Updater icon on the desktop (orange color icon near the clock on taskbar).
  2. Select the patches you wish to install and click update.

  3. After the Update is successful, it pops up with a Reboot option to proceed with the Update process.
  4. When all the patches are applied, the Novell Updater icon changes to a globe.

  5. Reboot the server and the upgrade proceeds with the YaST Configurations of OES.
Note: For Silent Upgrade, create an answer file and reboot the server.

2.3 YaST method of Upgrade

  1. Click YaST -> Software -> Online Update and select all the Security and Recommended patches, click Accept and install all these patches.

    Then select the optional patch which is move-to-oes2-sp2 and Install the patch to go to the next level.

  2. After the Patches are applied, reboot the server for the upgrade to finish.

    Note: Channel Upgrade on XEN is the same as upgrading the Linux Physical Server.

3. Silent Upgrade and Interactive Upgrade

Channel Upgrade can be done using two ways. One is Silent or scripted upgrade and other one is Interactive upgrade.

Silent Upgrade:

The password file will get generated where the admin password will be saved into the file and during upgrade process the admin credentials will be picked up from the password file. No user intervention is required during Upgrade process.

After applying the patches, do not reboot the server. Create the answer file for a Silent Upgrade and reboot the server

Command to create answer file:

yast2 create-answer-file <admin password>

The create-answer-file script will be located under /usr/share/YAST2/clients.

It will create an answer file under the same location(/usr/share/YAST2/clients)

Copy the answer file to /opt/novell/oes-install directory. The upgrade code will search the answer file in /opt/novell/oes-install.

 :/usr/share/YAST2/clients # cp answer /opt/novell/oes-install

Command to create answer file for DSFW silent upgrade

yast2 create-answer-file <admin password> <dsfw administrator password>

Interactive Upgrade:

User intervention is required to provide the admin password during upgrade.

DSFW Interactive Channel Upgrade:

4. TroubleShooting

Archive Versioning:

If Archive Versioning is not running by default after Upgrade, check the permissions of arkmanager directory located under /opt/novell.

If the User and Group has been changed to root user after the upgrade, change the permissions to admin and admin group and start the service.

iPrint on NSS:

If the iPrint Client RPM breaks the iPrint NSS Symbolic Links.

Prerequisites:

  1. Bring up the shared volume used for storing the iPrint configuration.
  2. Backup the existing /var/opt/novell/iprint/htdocs on your shared volume.
    Note: At minimum, backup the existing /var/opt/novell/iprint/htdocs/iprint.ini and restore it post step 2.
  3. Copy /var/opt/novell/iprint_client/htdocs to /var/opt/novell/iprint/htdocs (which will be a symbolic link to the shared folder) using following:
    cp /var/opt/novell/iprint_client/htdocs/* /var/opt/novell/iprint/htdocs/* -rf 
    
    Note: Do not remove the /var/opt/novell/iprint/htdocs on the shared volume, only overwrite the contents in this folder from /var/opt/novell/iprint_client/htdocs/. This is because the /var/opt/novell/iprint/htdocs/ folder contains some additional files which are not part of the client rpm and hence not available in /var/opt/novell/iprint_client/htdocs/ folder.
  4. Copy the iprint.ini from the backup folder in to the /var/opt/novell/iprint/htdocs.
VN:F [1.9.22_1171]
Rating: 0.0/5 (0 votes cast)

Tags:
Categories: Uncategorized

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

5 Comments

  1. By:skipthompson81

    thanks!
    when doing
    rug up -t patch.
    i had to accept the license repeatedly……
    first time, i didn’t realize that was what was happening.

    finally, i hit y 20+ times, it went. a little better process may be in order?

    VN:F [1.9.22_1171]
    Rating: 0.0/5 (0 votes cast)
  2. By:gldavis

    There are switches you can use to bypass the license and other prompts, however some of these messages are really meant to be read (may have certain warnings the admin should know about).

    If taking the entire channel for the first time with hundreds of patches, you will see many prompts.

    To bypass license agreements –agree-to third-party-licences # ( with two c’s)

    Switch to bypass warnings/messages -y

    So if you really want to skip all agreements and warnings, it can be done with the following command (but do it at your own risk).

    rug up -t patch -y –agree-to-third-party-licences

    VN:F [1.9.22_1171]
    Rating: 0.0/5 (0 votes cast)
  3. By:kiefabeb

    You should _NOT_ use the “move-to-sles10-sp3″ patch from what I am reading:


    http://www.novell.com/documentation/oes2/inst_oes_lx/?page=/documentation/oes2/inst_oes_lx/data/front.html

    In the ‘Before You Start the Upgrade’ section it states:

    The SLES move-to-sles10-sp3 patch cannot be used to migrate OES 2 SP2.


    http://forums.novell.com/novell-product-support-forums/open-enterprise-server/oes-linux/oes-l-install/392496-oes2-sp2-has-been-released.html

    In this forum thread, it is stated:

    “…As a note if you use the patch channel to upgrade choose ONLY the
    ‘Move-to-OES2sp2′ patch and NOT the ‘Move-to-SLES10sp3′ patch (at the same time or separately). One patch to rule them all…”

    VN:F [1.9.22_1171]
    Rating: 0.0/5 (0 votes cast)
  4. By:skapanen

    Online update from OES2SP1 to SP2 fails when nic bonding is used ;-(
    It doesn’t load network after the reboot phase and cannot continue. Removing the bond and changing to single nic fixes the problem.

    VN:F [1.9.22_1171]
    Rating: 0.0/5 (0 votes cast)
  5. By:schoerch

    Online update to OES2SP2 fails when guest nic configured as vmnet3. VMware tools not match to new kernel after reboot .
    Add a second nic as E1000 and give a separate ip address. After uprade remove the nic.

    VN:F [1.9.22_1171]
    Rating: 0.0/5 (0 votes cast)

Comment

RSS