Cloudbolt Support will be closed on Thurs Nov 26 in observance of Thanksgiving

Downgrade SovLabs plugin

Overview

This is the process required to move backward in versions when using the SovLabs plugin.  This should only be undertaken if reverting to VM snapshots is not possible to recover to a previous known-good state.

WARNING: It is highly recommended that you contact SovLabs Support before attempting this procedure.  Failure to complete each step in exact sequence can result in data loss and a non-functional vRA instance.  Proceed with extreme caution!

Before you Begin

Considerations

The process may require reboots of the vRealize infrastructure servers to restore functionality so plan accordingly for downtime.


You will lose token/log history on all previous SovLabs workflow runs in VRO.

Procedure

Removing the plugin from vRO Control Center

  1. Open Control Center - remove the plugin by clicking the trash can.

    1. [FQDN]:8283/vco-controlcenter/config/#/

  2. Restart Orchestrator Service by SSH to the Orchestrator Appliance

    1. Service vco-server restart <or> allow configurator to do the automatic restart of the vco service.

  3. Validate restart completed using "Validate Configuration" in VMware vRealize Orchestrator Control center

  4. Validate plugin is removed from Control Center (Navigate to "Manage Plug-Ins" and look at the inventory).


Remove SovLabs Content from Orchestrator

  1. In the Orchestrator Client - Navigate to the Package Tab.
    1. Select "com.sovLabs.vra"

    2. Right-click "Delete element with content" and on the confirmation box choose "DELETE ALL" (This will take several minutes)


      VERY IMPORTANT Wait 10 minutes after removing the package and DO NOT restart after doing so.

      The wait is especially important if vRO is clustered, to make sure that all nodes are in sync. (DO NOT RESTART right after removing the package). 
       
      To make sure all the deletions have completed, tail /var/log/vco/app-server/server.log on all vRO nodes and make sure messages like these have stopped:

      Log
      2020-04-16 18:31:15.693+0000 [https-jsse-nio-0.0.0.0-8281-exec-8] INFO {} [WorkflowManagementServiceImpl] Workflow 'Update Foreman Master Configuration/4e70482f-d81d-435b-bfad-e2b36b066f7d' deleted.
    3. Re-check the cluster status in vRO Control Center.  https://{vro_fqdn}:8283/vco-controlcenter/config/#/control-app/ha

Install Stable version of SovLabs plugin

  1. In Control center - upload the stable version of plugin

    1. Navigate to "Manage Plug-Ins" and upload the vmoapp file provided.

  2. Restart Orchestrator Service by SSH to the Orchestrator Appliance

    1. Service vco-server restart
  3. Validate restart completed using "Validate Configuration" in Control center and making sure all marks are green.

  4. Validate Plugin Version in Control Center and in the vRO Inventory.

  5. Verify that the com.sovlabs.vra package is back in the Packages tab in vRO client
  6. After vRO is completely up, wait 10 minutes to allow the new license type to propagate to vRA.  If you run the Configuration workflow before that happens, you'll get a type-sovlabs:license not found errror.
  7. In the Orchestrator Client - Navigate to the Workflow Tab.  A

    1. Run SovLabs Configuration workflow with these options:

      1. Tab 2a - Service and Content

        1. make sure you choose the correct Tenant and Business group (check the last successful token run if you're not sure)

        2. Create Sovlabs vRA Catalog Service - No

        3. Publish License Content - No

      2. Tab 2b

        1. Upgrade existing SovLabs vRA content - No

      3. Tab 3a

        1. Install or Update SovLabs workflow subscriptions - Yes

    2. Run SovLabs Configuration workflow a 2nd time with these Options:
      1. Tab 2a - Service and Content

        1. make sure you choose the same Tenant and Business group as the first run

        2. Create Sovlabs vRA Catalog Service - No

        3. Publish License Content - Yes

      2. Tab 2b

        1. Upgrade existing SovLabs vRA content - Yes

      3. Tab 3a

        1. Install or Update SovLabs workflow subscriptions - Yes

NOTE

The order above must be followed or Configuration may error.  If you still see an error "Failed to import SovLabs License…" - Restart the vRA appliance(s). 
If in cluster mode, restart replicas first, failover primary to one of the replicas and then restart the final vRA node after failover completes.

Validation of SovLabs plugin Operations

  1. The previous License + Old SovLabs configurations should still be stored as vRO resources and remain un-impacted by the downgrade process.

    1. Validate old SovLabs Deployments still load in vRA. Click on a SovLabs Configuration in the Deployment Tab and attempt to "update". Make sure configuration data is loaded.

    2. Request a test build from a known working blueprint and confirm Completion.


Additional information

Process is similar to information found on New Install: http://docs.sovlabs.com/latest/vmware-vra7x-plugin/getting-started/sovlabs-plugin/new-install/

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.