3.5.2.2 Upgrading Oracle VM Server 3.2.9 to Oracle VM Server 3.3.3

Note:

If you are running Oracle VM Server 3.0.3 (Base Image 2.0.1.1) or a version prior to Oracle VM Server 3.2.9, go to "Upgrading Oracle VM Server 3.0.3 (Base Image 2.0.1.1) or later version to Oracle VM Server 3.2.9".

To upgrade Oracle VM Server 3.2.9 to Oracle VM Server 3.3.3, complete the following procedures:

Prerequisites:

  1. Upgraded to Oracle VM Server 3.2.9.

  2. Before you upgrade Oracle VM Server, ensure that you have upgraded Oracle VM Manager.

  3. If there are any RAID devices configured in OVS 3.2.9, complete the following steps to restore the RAID device after upgrade:

    1. Ensure that the RAID is configured:

      1. To check the configured devices, run the following command:

        # mdadm --detail --scan

      2. To verify the contents of the mdamd.conf file, run the following command:

        # cat /etc/mdadm.conf

        The output looks similar to the following:

        ARRAY /dev/md2 level=raid1 num-devices=2 metadata=0.90 UUID=ce2fa269:741add38:3862df88:521ea08a 
minimum_kernel_version=2.6.39-400.215.9.el6uek

      3. Add the missing entries in the mdamd.conf file, if any.

    2. To backup the mdamd.conf file, run the following command:

      # cp /etc/mdadm.conf /etc/mdadm.conf_bfr_bkup

      This ensures that the mdadm.conf entry is available after the upgrade.

  4. Before upgrading to OVS 3.3.3, increase the “/” partition that includes the /boot partition as well, with the instructions provided in https://docs.oracle.com/cd/E64076_01/E64078/html/vmiug-server-upgrading-ovs-partitions.html

    This ensures that enough disk space is available.

To upgrade Oracle VM Server 3.2.9 to Oracle VM Server 3.3.3:

  1. Navigate to My Oracle Support and download the OVM Server 3.3.3 iso file: Patch number 22546910. The patch contains the Exalytics_2.2.0.0.0_X5-4_OVS3.3.3_01082016.iso file.

  2. Mount the iso file to a temporary directory, by running the following commands:

    # mkdir /tmp/ovs-mount

    # mount –o loop Exalytics_2.2.0.0.0_X5-4_OVS3.3.3_01082016.iso /tmp/ovs-mount

  3. Copy the mounted files to a location under the /var/www directory, by running the following commands:

    # mkdir /var/www/repos

    # cp –rp /tmp/ovs-mount/* /var/www/repos/

  4. Run the following commands:

    # cd /var/www/repos/Server

    #createrepo .

  5. Are there any non-native packages?

    No: Go to the step 6.

    Yes: Complete the steps in the following section.

    If you have non-native packages:

    If there are non-native packages detected then the upgrade script displays an error message. The error message looks similar to the following:

    Wed Feb 24 05:30:29 2016 INFO: Checking servers for non-native packages (those installed after initial server installation)
Wed Feb 24 05:30:30 2016 INFO: Non-native package status://
Wed Feb 24 05:30:30 2016 INFO: Non-native package Status in 3.3_ovs_repoWed Feb 24 05:30:30 2016 INFO: ----------------------------- ----------------------
Wed Feb 24 05:30:30 2016 INFO: Lib_Utils ERROR: Missing package!
Wed Feb 24 05:30:30 2016 INFO: MegaCli ERROR: Missing package!
Wed Feb 24 05:30:30 2016 INFO: QConvergeConsoleCLI ERROR: Missing package!
Wed Feb 24 05:30:30 2016 INFO: autofs ERROR: Missing package!
Wed Feb 24 05:30:30 2016 INFO: exalogic.tools ERROR: Missing package!
Wed Feb 24 05:30:30 2016 INFO: exalytics-flash ERROR: Missing package!
Wed Feb 24 05:30:30 2016 INFO: hesiod ERROR: Missing package!
Wed Feb 24 05:30:30 2016 INFO: infiniband-diags ERROR: Missing package!
Wed Feb 24 05:30:30 2016 INFO: ipmiflash ERROR: Missing package!
Wed Feb 24 05:30:30 2016 INFO: ipmitool ERROR: Missing package!
Wed Feb 24 05:30:30 2016 INFO: libibmad ERROR: Missing package!
Wed Feb 24 05:30:30 2016 INFO: libibumad ERROR: Missing package!

    1. Run the following commands to remove the additional packages:

      # rpm -e ovsvf-config-1.0-10 exalogic.tools sas_snmp openib hesiod Lib_Utils MegaCli QConvergeConsoleCLI autofs

      # rpm -e --nodeps hesiod

    2. To run the update script, run the following command:

      # /u101/app/oracle/ovm-manager-3/ovm_tools/bin/UpgradeServers.py -v <server>

      Where, <server> is the server that you want to update.

    3. The script displays a confirmation message. Type Yes to continue with the upgrade script.

    4. Apply the patch (file: p20431965_20001_Linux-x86-64.zip) that is downloaded with the OVM Server 3.3.3 iso file: Patch number 22546910. For information about how to apply the patch, see the readme file that is provided in the OVM Server 3.3.3 iso file.

  6. To go the repos directory, run the following command:

    # cd /var/www

  7. To start the http server, run the following command:

    # python –m SimpleHTTPServer 80

  8. Perform the following steps to configure the Yum repositories in OVM:

    1. Connect to Oracle VM Manager.

    2. Select Tools and Resource > Click Server Update Groups.

    3. In the left pane, click GlobalX86ServerUpdate Configuration and select the + icon to add the transitional repository.

    4. Enter the following information for the server:

      - Name: 3.3_trans_repo.

      - Repository Name: 3.3_trans_repo.

      - URL: http://example.com/repos/Transition.

      - Enabled: select the check box.

      - Package Signature Key: From the drop-down list, select None.

    5. Click OK.

      The transitional repository is created.

    6. In the left pane, select the + icon to add the update repository.

    7. Enter the following information for the server:

      - Name: 3.3_ovs_repo.

      - Repository Name: 3.3_ovs_repo.

      - URL: http://example.com/repos/Server.

      - Enabled: select the check box.

      - Package Signature Key: From the drop-down list, select None.

    8. Click OK.

      The update repository is created.

  9. Start the OVM server update:

    # /u01/app/oracle/ovm-manager-3/ovm_tools/bin/UpgradeServers.py -v <server>

    Where, <server> is the server that you want to update.

  10. When prompted to enter the OVM username, enter admin.

  11. When prompted to enter the OVM password, enter password.

Post installation: If there were any RAID devices configured before the upgrade, complete the following steps to restore the RAID devices:

  1. Go to the mdamd.conf file and delete the following entry:

    DEVICE /no/device

  2. To copy the contents of the previous setup to the current mdadm.conf file, run the following command:

    # cat /etc/mdadm.conf_bfr_bkup >> /etc/mdadm.conf

  3. Restart the server and ensure that the RAID devices are available with the previous partitions and data.

Parent topic: Upgrading Oracle VM Server 3.0.3 (Base Image 2.0.1.1) or Later Version to Oracle VM Server 3.4.3