OnApp 5.4.0-66 Update

Release NotesAffects Version/s
Fixed the issue when a disk could not be edited for a VS which is inside a vApp.5.4
Fixed the issue when a disk could not be added to a VS which is inside a vApp.5.3, 5.4
Fixed the issue when a custom SSL certificate could not be set up for the cloud.5.4

Patch Installation

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

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

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

    # for service in monit httpd onapp onapp-licensing; do service $service stop; done
  2. Update the required package(s):

    # yum update rubygem-onapp-infrastructure onapp-cp
  3. Start services, which were stopped on the first step:

    # 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:

    # crm configure property maintenance-mode=true


  2. Stop  all related to OnApp Control Panel services:

     # for service in httpd onapp onapp-licensing; do service $service stop; done
  3. Update the required package(s):

     # yum update rubygem-onapp-infrastructure onapp-cp
  4. Start services, which were stopped on the first step:

     # 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:

     # crm configure property maintenance-mode=false