OnApp 4.2.0-130 Update

Release NotesAffects Version/s
Improved OnApp daemon and transaction runner.4.2
Fixed the issue when several "save_vm_billing_stats" transactions were stuck.4.2
Fixed the billing statistics calculation for federated resources.4.0, 4.1, 4.2

Patch Installation

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

To apply the patch into Control Panel (running 4.2.0 version):

  1. Upgrade OnApp Control Panel installer package:

    # 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

If you are a High Availability 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 enabled:
  1. Switch the cloud to maintenance mode at Control Panel > Sysadmin Tools > Control Panel Maintenance
  2. Stop syncing on all nodes by issuing the following command on any node:

    crm resource stop lsyncd
  3. Switch all nodes to maintenance by sequentially issuing the following command on each node:

    crm node maintenance
  4. Upgrade OnApp Control Panel installer package:

    yum update onapp-cp-install
  5. Update your server OS components (if required):

    bash# /onapp/onapp-cp-install/onapp-cp-install.sh -y
  6. Run the Control Panel installer:

    /onapp/onapp-cp-install/onapp-cp-install.sh
  7. Update the High Availability package:

    yum update onapp-cp-ha
    /onapp/onapp-ha/onapp-cp-ha.sh


  8. Switch all nodes back online one by one by running the following command:

    crm node ready