CloudBolt Resources>Release Notes

SovLabs Plug-in 2018.3.x Release Notes


Important Notes

vRA 7.3 Notice

If using vRA 7.3.0, please upgrade to VMware’s vRA 7.3.1.

  • If on vRA 7.3.0, please login to the vRA Appliance and verify Appliance Version is Build. If not on the Build, please upgrade to vRA 7.3.1.  If on the Build, the VMware vRA Hotfix has been applied that is required for SovLabs.

VMware fixed an issue with form field validations that affects all of SovLabs’ provided XaaS forms.  VMware also fixed a vRA 7.3.0 vRO CAFE bug related to VMware vRA plug-in for vRO.

vRA 7.4 Notice

The minimum SovLabs plug-in version compatible for VMware’s vRA 7.4 is 2018.1.4.


vRA 7.5 Notice

The minimum SovLabs plug-in version compatible for VMware’s vRA 7.5 is 2018.2.6.


SovLabs Documentation

New Install

Prior to performing a new install, please complete all of the pre-requisites via: docs.sovlabs.comGetting Started


Please follow our Upgrade steps when performing an upgrade of our SovLabs Plug-in

New License Key provided?

Please perform the following:

1) Delete old SovLabs License Key

2) Add new SovLabs License Key


SovLabs 2018.3.x Plug-in Details

SovLabs Plug-in Version Details
2018.3.4 (latest)
Released January 8, 2019
What’s New?

  • F5 RESTipe versions now reflects the SovLabs Plug-in version after the SovLabs Configuration run
  • ServiceNow CMDB module has updated ServiceNow logos
  • ServiceNow Connector 2018.3.0.1 (see below in Resolved Issues) now supports ServiceNow London


Resolved Issues

Module Resolved Issue(s)
  • Fixed issue where incorrect F5 BIG-IP version was returned for instances that were upgraded to a newer version.
Microsoft DNS
  • Fixed issue where error log for missing license for Microsoft DNS was not being reported
  • Fixed issue when using VM Tools where invalid characters (e.g. backslash “”) would throw an exception and caused the raw error message to return the password in plain text.
Property Toolkit
  • Fixed issue where multiple vRO Scheduled Tasks were created for Property Toolkit.  During SovLabs Configuration, all extra SovLabs Property Toolkit vRO Scheduled Tasks that may have been created for Property Toolkit will be removed.
  • Fixed issue where inventory collection for Property Toolkit would not query vRA Blueprint Custom Properties that had “Overridable” set to “False”
  • Fixed issue where inventory collection for Property Toolkit would not query vRA Blueprint Components with IDs that only contained numbers (e.g. 2018)
SolarWinds IPAM/DNS
  • Fixed vRA Presentation issue for Update SolarWinds Endpoint that would not show/hide fields appropriately depending on SolarWinds version
ServiceNow Connector
  • Fixed issue for “Error MessageSyntax Error or Access Rule Violation detected by database”
Released December 20, 2018

  • Latest F5 RESTipe version is 2018.3.0

Resolved Issues

Module Resolved Issue(s)
Ansible Tower Ansible Tower module with Static Inventory now passes in VM Properties as part of Static Inventory to populate under variables/node
Property Toolkit Fixed issue where Property Toolkit Data Collection did not occur for vsphere.local tenants

Entity Property Assignment and Reporting vRA Catalog

  • Fixed minor typos on Reporting tab
  • Set to Property value for Properties to read-only to prevent changing of value once it is initially set to avoid wrong data being populated/represented on the form for Reporting


Released December 4, 2018
What’s New?

  • Added multi-license key support



  • Latest F5 RESTipe version is 2018.3.0
Released November 26, 2018
What’s New?

SovLabs OVF/OVA support for vRA 7.5

  • Native support for Naming, IPAM and DNS integrations for blueprints with OVF/OVA components via the SovLabs Property Toolkit module



  • Latest F5 RESTipe version is 2018.3.0


Module Feature/Enhancement
Ansible Tower Official support for Ansible Tower 3.3
BlueCat DNS/IPAM Official support for BlueCat 9.0 was in SovLabs Plug-in 2018.3.0, but only by selecting “8.3.2” from Version on a SovLabs BlueCat Endpoint

For this release, “9.0” is available in the “Version” field for a SovLabs BlueCat Endpoint


Resolved Issues

Module Resolved Issue
Ansible Tower SovLabs Ansible Tower Profile vRA forms

  • For both Add/Update: Updated Ansible Tower Profile header “Prompt on Launch Overrides” to remove the word “(Optional)”.  The Inventory field is necessary for Static Inventory.
  • For Update Ansible Tower Profile: Added the same Notice message under the Inventory field declaring that the field is necessary for Static Inventory.


Resolved issue where a failure occurred when more than 1 Playbook is selected to run

F5 Resolved issue where inventory collection failed with an F5 Service Account with only “Manager” role access
Property Toolkit Resolved issue where Property Toolkit Data Collection would fail for a vsphere.local tenant
ServiceNow Connector Resolved Issue where failure occurred to execute a vRA Request from ServiceNow for a vsphere.local tenant


Released November 13, 2018
What’s New?

BlueCat Selective Deployment for BlueCat version 8.3.2 and above “to selectively deploy specific DNS resource records to managed DNS/DHCP Servers, enabling users to deploy records in real time based on a specific change via API” – DNS Integrity: The Need for Speed BlueCat Blog

  • See Features/Enhancements section below for more details

Ansible Tower Static Inventory enables a new way for storing vRA-provisioned machines (hosts) data in Ansible Tower without requiring any Ansible Tower server-side Python components

  • See Features/Enhancements section below for more details

ServiceNow Connector

  • See ServiceNow Connector Features/Enhancements and Resolved Issues section below


  • Latest F5 RESTipe version is 2018.3.0


Module Feature/Enhancement
Ansible Tower Ansible Tower Static Inventory enables a new way for storing vRA-provisioned machines (hosts) data in Ansible Tower.
Note: Static Inventory feature is currently available in Tower Module. Development for Tower CM Framework Plug-in is underway.

  • Provision a server using Ansible and remove the VM from Inventory
  • Synchronize Inventory on Ansible Tower to affect Hosts and Groups (vRA Resource Action)
  • VM Provisioning / De-provisioning immediately reflects in Ansible Tower
  • New “Inventory Type” field
  • Note: For Ansible Tower Profile, the Prompt on Launch Overrides > Inventory field is required
BlueCat DNS BlueCat Selective Deployment for BlueCat version 8.3.2 and above

  • If using BlueCat DNS or IPAM already, please Update the SovLabs BlueCat Endpoint(s)
  • New “Version” field – Select the BlueCat version for the SovLabs BlueCat Endpoint
  • New “Deployment Method” field – select the desired Deployment Method.
    • Quick Deploy option available for versions 8.1 and 8.2
    • Quick Deploy and Selective Deploy options available for version 8.3.2
  • Recommended to use Selective Deploy for BlueCat version 8.3.2 and above (better performance at scale, better fault isolation)

Resolved Issues

Module Resolved Issue(s)
Add License In rare event where Add License workflow fails during vRO action “updateIcons”, the workflow logic has been updated to continue.

The error, if any, in updateIcons is benign and should not have caused the overall Add License workflow to fail.

Ansible Tower Missing Icon fixed for Configure Ansible Tower Custom Inventory Day2 for a SovLabs Ansible Tower Inventory Profile
Infoblox Endpoint Removed the tab “Advanced” when adding a SovLabs Infoblox Endpoint to not cause confusion when setting up a SovLabs Infoblox Endpoint for the very first time.

The Advanced Settings tab is able to be manipulated during an “Update Infoblox Endpoint” in which all of the Advanced setting fields are populated with defaults.

F5 Fixed issue where a VM was not adding correctly to a Partition other than “Common”.
Resulted in RESTipe update, now at version 2018.3.0.

Fixed failure of F5 IPAM logic that causes failure of VIP deployment with Infoblox DNS Host Record reservation.

Property Toolkit All deployments trigger the SovLabs Property Toolkit vRA Event Broker Subscriptions.

When a deployment is executed without any SovLabs modules attached via SovLabs vRA Property Group(s), the Property Toolkit workflow fails to find the “SovLabs_Tenant” vRA Property and fails the deployment.

The above has now been resolved in 2018.3.0

ServiceNow Connector Features/Enhancements and Resolved Issues

What’s New?

  • User Mapping page
    • Ability to map a ServiceNow user to their vRA user email address in the event that they are different
  • 2 new SovLabs ServiceNow Workflows
    • Added ability to mark the request in a failed state (e.g. Closed Incomplete)
    • NOTE: If “Closed Incomplete” is not an acceptable “Failed” state, please duplicate and update the ServiceNow Workflows with the desired state for use.
  • ServiceNow Catalog Request
    • New vRA Request Number, vRA Request ID and vRA Request link fields on the ServiceNow Catalog Request
    • When an error has occurred (“Closed Incomplete”), a new field with vRA Request error log snippet is shown
  • Ability to import initial vRA settings of a vRA Catalog Item if it is one of the following:
    • Field is mandatory, during Import, the ServiceNow Catalog will also have a corresponding variable that is set as Mandatory
    • Field has a min/max constraint, during Import, the ServiceNow Catalog’s variable will have the min/max constraints initially set, if it was chosen to be imported.
    • Field has a default value, during Import, the ServiceNow Catalog’s variable’s default value is set, if it is chosen to be Imported.
    • Field is a masked secure string, the ServiceNow Catalog’s variable is set to Mask, if it was chosen to be imported
    • Field has Array/String values from a vRA Property Dictionary that has static values defined, during Import, the ServiceNow Catalog will also have the variable’s choice selection pre-populated, if it was chosen to be imported.

Import Catalog Item / Modify Catalog Item Mapping Page Enhancements

  • Ability to designate ServiceNow Category during Import/Modify Catalog Item Mapping
  • Ability to Preview the ServiceNow Catalog via Modify Catalog Item Mapping
  • Ability to Modify the ServiceNow Catalog via link in Modify Catalog Item Mapping and reload the Modify Catalog Item Mapping page to pull in changes
  • Ability to filter vRA Catalog Items by vRA Business Group


  • Speed/Performance improvements
  • User validations on Import/Modify Catalog Item Mapping
  • vRA Blueprint Components displayed with containers that are collapsable/expandable
    • Main vRA Deployment fields are displayed at the top
  • vRO Setup page
    • Ability to provide a label/name for a vRO Endpoint
    • Improved validation checks when saving a vRO Endpoint
    • Specify the Service Account within a vRO Endpoint that will be used to request/see vRA Catalog Items

Resolved Issues

  • Fixed vRA Catalog Item not passing in vRA tenant upon request from ServiceNow
  • Fixed Request Task being in state “OPEN” even when the overall ServiceNow Request was marked as “Complete”
  • Enhanced handling of 401 error from vRO when requesting a ServiceNow Catalog via SovLabs ServiceNow Connector
  • Fixed issue to get an Active/Up MID server in the event multiple MID servers exist and 1 or more happen to be Inactive/Down.


Known Issues

  • Currently, unable to run more than 1 Ansible Playbook for Static Inventory (resolved in 2018.3.1)


Hotfix Releases

Release Date Released From Release Version Purpose
January 16, 2019 2018.3.4 2018.3.5 Ansible Tower

  • Fixed issue with Ansible Tower machineProvisioned vRO workflow timing out
  • Fixed issue with Ansible Tower with Static Inventory not honoring the vRA Property Translation field
January 18, 2019 2018.3.0 2018.3.6 BlueCat DNS

  • Allowed for enabling an Advanced Setting on the BlueCat Endpoint to disable logout when concurrent calls are made to BlueCat’s API that would cause deployments to fail
    • Advanced Settings, new entry: “DisableLogout” set to “true“, without quotes

IPAM machineBuilding

  • Enable locking for SovLabs IPAM machineBuilding workflows by setting a vRA Property: SovLabs_IPAMEnableLocking set to true


Known Issues

Type Known Issue + Workaround
Single node vRO Failed to get latest version of the resource element {{ name }}

Workaround: None.  This Please re-submit the request of interest.  SovLabs is pursuing this issue at the highest priority.

vRA/vRO Clustering for vRA 7.3 and vRA 7.4 vRA does not consistently persist XaaS items to inventory (independent of SovLabs) even though the vRO workflow related to item creation completes successfully.

Workaround: None.  SovLabs is pursuing this issue with VMware GSS at the highest priority.
SovLabs KB Article 6000197373

Custom Naming Unable to rename deployments in vRA 7.x due to vRA Platform limitation.

The deployment name defaults to the blueprint name appended by a dash and an auto-generated 8-digit number (e.g. blueprintName-12345678)

Workaround: The deployment name can be influenced by adding a vRA Custom Property at the composite blueprint level (versus at the machine component in the blueprint) with:

  • Name: _deploymentName
  • Value: Unique value utilizing the SovLabs Template Engine

*Note: Using the same property value will result in deployments with the same name

Manage Credentials for Puppet Open Source with Foreman Unable to update a credential that is tied to Puppet Open Source with Foreman

Workaround: Update the Foreman Master or Foreman Agent and create a new credential directly inline and submit.

F5 Issue: A nested vRA blueprint with the F5 virtual component in the child vRA blueprint that defines the value for Pool Health Monitors field fails with a: Status Code 400 ‘The value for the ‘poolHealthMonitors’ field should be among the permitted value’ for vRA 7.2.  This issue does not occur for vRA 7.3 nor for a single (non-nested) blueprint.

Workaround: Do not define (pin) the value for Pool Health Monitors (or any field that is Array/String) on the F5 Virtual component in the child blueprint for a nested blueprint.

vRA 7.4, 2018.1.4
During provisioning for vRA 7.4, vRO server.log will log errors when the SovLabs RESTipe executes a vRO workflow.  The error logs are benign and can be ignored.  vRO workflows are executed successfully via SovLabs RESTipes.

Issue: When defining multiple F5 virtual components and different VIPs are tied to use the same Pool Name (often when manually defining the Pool Name), the VIPs and the Pool is not removed from F5 when destroying the deployment even though the Pool is empty.

Workaround: Please try to keep a 1:1 relationship between a VIP and Pool.  A circular dependency exists when trying to remove the VIPs tied to the same Pool and proper disposal cannot take place.

vSphere Snapshot Management If using vSphere Snapshot Management with any of the Backup as a Service modules (Cohesity, Rubrik, Veeam) may result in an email notification of a Backup as a Service snapshot.

If the Backup as a Service snapshot lives beyond deletion time set in Snapshot Configuration, will get deleted.

Property Toolkit Day2 on vRA VM “Manage Properties (SovLabs Property Toolkit) does not have a correct reflection of the fields: Hidden, Encrypted, Show in Request for a Property when the Action field is Update Existing Property.

Workaround: Please check the checkbox during an Update of a Property on a VM for any of the applicable fields: Hidden, Encrypted, Show in Request and then Submit.

Property Toolkit vRA Catalog Item: Entity Property Assignment and Reporting has an issue when creating a new vRA Blueprint Custom Property and setting it to “Overridable = false” will create the vRA Blueprint Custom Property as “Overridable = true”
Workaround: Please manually set “Overridable = false” on the vRA Blueprint

SovLabs vCenter Endpoint Version “6.7x” does not show in the dropdown list.

Workaround: Please select “6.5x” from the Version dropdown list. We have certified vCenter 6.7 in 2018.1.5.

Resolved in 2019.6.0

Puppet Open Source with Foreman (starting from release 2018.2.4) The Host Parameters field is optional.  When no Host Parameters are defined, an error stack trace for null pointer exception is in the vRO logs.

Workaround: None, the error stack trace is benign.  The provisioning succeeds and the machine is added correctly into Foreman.

Related Blogs

SovLabs Plugin 2019.24.0 Release Notes

Today, we have released the SovLabs Plugin version 2019.24.0 for vRA7.x to General Availability. Below is a bullet point summary…

SovLabs Plugin 2019.22.0 Release Notes

Late last week, we released the SovLabs Plugin version 2019.22.0 for vRA7.x to General Availability. Below is a bullet point…

SovLabs Plug-in 2019.16.0 Release Notes

Yesterday, we released SovLabs Plugin 2019.16.0. Here’s a quick summary, with all the details below, of what’s new in this…