OnApp 5.3.0-41 Update

Release NotesAffects Version/s
Updated the maximum RAM values that can be set when creating a server per virtualization type. 
Fixed an error which occurred during autoscaling rules creation.5.3
Fixed the issue with routed org network deletion from OnApp.5.2
Fixed the issue when the Control Panel was sending incorrectly formatted data to the Dashboard.5.3
Fixed the issue with Cloud Score Scroll Bar.5.3
Fixed the issue with running recipes on Control Panel under CentOS 7.5.3
Fixed the issue when "Activate DRaaS" was not available after upgrade to 5.3.5.3
Fixed the issue with boot-freebsd-onapp-3.5.iso availability for CloudBoot compute resource.5.3
Fixed the issue when provider vDC and vDC instant statistics were not cleaned according to the "Time of instant statistics storage (days)".5.3
Removed validation of price format which caused incorrect work of setting prices in plans.5.2, 5.3
Fixed the issue when the delimiter could not be set as a dot.5.2, 5.3

Patch Installation

The instructions below are relevant if you already run OnApp 5.3.0 version. If you are upgrading from OnApp 5.2.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.3.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.

Upgrade Control Panel Servers for Advanced HA Deployment


To apply the patch for clouds with the Advanced configuration of the High Availability Control Panel:

  1. Switch the cloud to maintenance mode at Control Panel > Sysadmin > Control Panel Maintenance

    Run the following commands on all  Control Panel servers:

  2. Issue the following command:

    # rpm -Uvh http://rpm.repo.onapp.com/repo/onapp-repo-5.3.noarch.rpm
  3. Unmanage RabbitMQ service:

    # crm resource unmanage onapp-mq-cluster
  4. Stop rabbitmq-server on each node:

     # service rabbitmq-server stop


  5. Upgrade the OnApp installer package on CP nodes:

     # yum -y update onapp-cp-install


  6. Upgrade the RabbitMQ packages on remote nodes:

     # yum -y update rabbitmq-server rabbitmq-admin erlang


  7. Start rabbitmq service on remote nodes:

     # service rabbitmq-server start


  8. Ensure that RabbitMQ cluster is working:

     # rabbitmqctl cluster_status


  9. Delete old queues from the RabbitMQ cluster. This command should be run on any remote node without CP

    # rabbitmqctl list_queues | grep 0 | awk '{print $1}' | xargs -I qn python /usr/local/bin/rabbitmqadmin -u <user> -p <password> delete queue name=qn

    You can find the <user> and <password> parameters on the remote RabbitMQ nodes by using this command:

    # cat /onapp/onapp-rabbitmq/.rabbitmq.mgr
  10. Run the Control Panel installer:

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


After you have successfully run the previous commands on all Control Panel servers, issue the following commands on one of the CP servers:

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

    # crm configure property maintenance-mode=false
  2. Enable monitoring onapp-mq-cluster:

     # crm resource manage onapp-mq-cluster
  3. Enable file synchronization on all nodes by running the following command once on any of the nodes:

     # crm resource start lsyncd-cluster

    Ensure that the lsyncd service is not started during the whole CP upgrade procedure.

Upgrade Control Panel Servers for Regular HA Deployment


To apply the patch for clouds with the Regular configuration of the High Availability Control Panel:
  1. Switch the cloud to maintenance mode at Control Panel > Sysadmin Tools > Control Panel Maintenance

  2. Run the Control Panel installer on all three Control Panel servers:

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

After you have successfully run the previous commands on all Control Panel servers, issue the following two commands on one of the CP servers:

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

    # crm configure property maintenance-mode=false
  2. Enable file synchronization on all nodes by running the following command once on any of the nodes:

    # crm resource start lsyncd-cluster