7.0
7.0
Docs menu
MENU

Virtuozzo OnApp 5.2 Update

This update is only relevant if your time zone uses uneven UTC offsets. If your time zone differs from UTC by a number of full hours, you can ignore this update.
Release NotesAffects Version/s
Fixed the issue with billing statistics calculation for the time zones that use uneven UTC offsets (i.e. zones that differ by 30, 45, etc. minutes from the usual one-hour time zone interval).5.2

Patch Installation

The instructions below are relevant if you already run Virtuozzo OnApp 5.2.0 version. If you are upgrading from Virtuozzo OnApp 5.1.x. version, run the full upgrade procedure. For more information refer to the 5.2 Get Started guide.

To apply the patch into Control Panel (running 5.2.0 version), run the following commands:

  1. Stop Monit and all related to Virtuozzo OnApp Control Panel services:

    1

    # for service in monit httpd onapp onapp-licensing; do service $service stop; done

  2. Update the required package(s):

    1

    # yum update rubygem-onapp-utils

  3. Start services, which were stopped on the first step:

    1

    # for service in monit httpd onapp onapp-licensing; do service $service start; done

Patch Installation for Clouds with High Availability Control Panel

If you are a High Availability Control Panel customer, it is recommended that you contact support for help with the procedure described below. Be aware, that if the configuration below is performed incorrectly it may cause damage to your cloud.

To apply the patch for clouds with the High Availability Control Panel run the following commands on all Control Panel servers:

  1. Disable managing resources on all nodes by running the following command once on any of the nodes:

    1

    # crm configure property maintenance-mode=true

  2. Stop all related to Virtuozzo OnApp Control Panel services:

    1

    # for service in httpd onapp onapp-licensing; do service $service stop; done

  3. Update the required package(s):

    1

    # yum update rubygem-onapp-utils

  4. Start services, which were stopped on the first step:

    1

    # for service in httpd onapp onapp-licensing; do service $service start; done

  5. Switch all nodes back online by running the following command once on any of the nodes:

    1

    # crm configure property maintenance-mode=false