OnApp 5.4.0-76 Update

Release NotesAffects Version/s
Fixed the issue when a created through SAML OnApp user who belongs to a vCD user group could not log into OnApp using SAML authentication.5.4
Fixed the issue when the federated VS creation wizard could not proceed to the Recipes step if the 'Show IP address selection for new VS' option was enabled at Settings > Configuration.5.4
Fixed the issue when a user who had a configured default template that was not in a template group could not create a federated VS by selecting a template in the creation wizard.5.4
Fixed a malicious code detector Scooby vulnerability.5.3, 5.4
Fixed the issue when network mask '30' could not be applied to IP addresses.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 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