OnApp 5.0.0-83 Update

Release NotesAffects Version/s
Added support for Windows 2016 and Windows 10 by OnApp Control Panel. 
Fixed the issue when erlang could not be updated to version 19.1.5 during OnApp 4.3 to 5.0LTS upgrade. 
Fixed the issue when the set "." delimiter caused incorrect calculation in billing plans.5.0, 5.1, 5.2, 5.3
Fixed the issue when it was possible to delete a network zone which contained a network attached to a VS.5.0, 5.1, 5.2, 5.3


Patch Installation

The instructions below are relevant if you already run OnApp 5.0.0 version. If you are upgrading from OnApp 4.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.0.0 version), run the following commands:

  1. Update the Control Panel installer:

    # yum update onapp-cp-install
  2. 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 High Availability Control Panel enabled:
  1. Switch the cloud to maintenance mode at Control Panel > Sysadmin Tools > Control Panel Maintenance


    Run the following commands on all three Control Panel servers:

  2. Unmanage RabbitMQ service:

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

    # service rabbitmq-server stop
  4. Upgrade the OnApp installer package:

    # yum -y update onapp-cp-install rabbitmq-server rabbitmq-admin erlang
  5. Start rabbitmq service on all nodes:

    # service rabbitmq-server start 

    Start the RabbitMQ service on the node on which the RabbitMQ service was stopped last of all. Then start RabbitMQ on other nodes.

  6. Ensure that RabbitMQ cluster is working:

    # rabbitmqctl cluster_status
  7. 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 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. Enabling 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.