OnApp 5.4.0-82 Update

Release NotesAffects Version/s
Fixed the issue when vApp deployment failed because template disk used LSI Logic SAS controller.5.4
Fixed the issue when 'RebuildNetwork' transaction failed for not accelerated VSs if accelerator existed without IP address.5.4
Fixed the issue when autoscale parameter 'for_minutes' was not stored in database.5.3, 5.4
Fixed the issue when disabled permissions became enabled after upgrade to OnApp 5.4 version.5.4
Fixed the issue when template store child folders were not shown during VS creation.5.4
Fixed the issue when in case user had federation and not-federation templates, some templates were not shown at Templates step of VS creation wizard.5.4
Fixed an error, which occurred during resize of vCenter virtual server.5.4
Fixed an error, which occurred during deployment of a new vApp.5.4
Fixed the issue when an autoscaling load balancer was created with one IP address instead of two.5.4
Fixed the issue when an autoscaling load balancer did not pick up nodes added automatically by autoscaling.5.0, 5.1

  

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 Control panel installer:

# /onapp/onapp-cp-install/onapp-cp-install.sh


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. Run the Control panel installer:

    # /onapp/onapp-cp-install/onapp-cp-install.sh
  3. Switch all nodes back online by running the following command once on any of the nodes:

     # crm configure property maintenance-mode=false

    Ensure that the lsyncd service is not started during the whole CP upgrade procedure. In separate consoles, connect to all three CP servers and run the following command:

    watch /etc/init.d/lsyncd stop