Issues Resolved in Prior 8.x Versions

This section lists the issues that have been resolved in versions 8.0.0 to 8.4.x.

To access complete release notes for previous releases, go to the Release Notes Archive.




The /webservices/services/rest/v2/security/sessions/count endpoint now returns the number of active sessions and the configured maximums as expected.


The destination control in the Commander administrator console incorrectly showed costs that included markup. The destination control now shows regular costs in Commander and marked up costs in the Service Portal, as expected.


The VM Billing Report now takes into consideration the digit-separating commas in 4-digit or higher numbers so that billing totals are correct.


For an Azure deployment, the variable #{} is now populated with the region of the target's placement destination.


To add a Kubernetes cluster as a managed system, the provided kubeconfig file must be properly encoded in UTF-8. If the file isn't properly encoded, an error is now displayed, and no managed system is added.


The CSV export of the Cloud Billing report no longer rounds cost and usage to 2 decimal places.


The cost associated with recommendations for VMs that have been powered on for long periods now update as expected.


The Azure region selection dialog is now populated with only the Azure regions that support Microsoft Compute to allow integration with Commander.


Resource group names for ARM templates are now generated based on uniqueness across a subscription.


The summary costs in the Cloud billing report are now right-aligned for easier reading.


The following changes were made to the REST v3 API virtual-machines/{id} properties:

  • "public_dns_name" and "private_dns_name" properties are now listed under "resources" instead of under "resources/network interfaces"
  • each network interface only displays its own IPs


Multi-cloud service requests now deploy to the proper destination when component resource settings are modified.


Using the REST v3 API to remove a child organization from a parent organization and then later re-adding it now works as expected.


In the Service Portal, you won't be able to clone published services that are corrupted (for example, the source template was deleted, the snapshot is missing, the credentials were deleted). A notification will let you know that you can't clone and will report the published service state.


When deploying VMs on a distributed port group that has an associated IP pool, in some cases IP addresses weren't assigned to VMs even though there were free IPs in the pool.

The deployed VMs are now assigned IP addresses as expected.


The descriptions for the RolePermission data type values in the REST v2 Reference Docs now align with the permissions described in the service portal documentation.


Making REST v2 API calls with the Commander PowerShell commandlets no longer requires you to configure Internet Explorer before using the commandlets.


The #{target.settings.dynamicList[‘*’]} variable is now available. You can use the variable to reference a specified dynamic list for the Deployed Name in a component form.


Change requests that assign ownership to an Active Directory user not directly managed in Commander will now function correctly.


Refactored internal representation of storage tier name identifier so storage tier name handling is now more robust.


When you add an AWS managed system account with the "Add Managed System" API call, Commander now prevents you from adding duplicate AWS managed system accounts. You can't add duplicate managed systems accounts for any managed system type.


Service Portal users are now able to upload files in the New Service Request form when requesting a service catalog item.


Command workflows configured to be visible to users in specific organizations are now consistently displayed in the Service Portal as expected.


For AWS, you can now use REST v3 to deploy a cloud formation template-based service that contains IAM resources such as Roles.


A VM search with a filter of "Version (Guest Tools)" returns the applicable tool information (for example, the VMware tools version) as expected. However, if the results are sent through scheduled email notification, the "Version (Guest Tools)" information could be listed as "Unknown".

VM search results received in an email notification now present applicable tool information as expected.


A REST v3 API call to get a list of workflows now consistently returns, as expected.


Resource group variable now gets populated with the appropriate resource group.


The DRS setting is now re-enabled as expected when a vCenter VM is deployed through a completion workflow.


The advanced system property embotics.workflow.customizeos.event.leadinperiod now accepts -1, to be able to look back an unlimited period for the "customization completed" event.


When using Global Text Replacement in names that are applied to deployed VMs, virtual services, and application stacks, variables will now correctly resolve names that contain underscore symbols.


For scheduled tasks, the View Last Report option is now only available for Reports (tasks with a type of Report or Saved Search).


List custom attributes can now be updated using REST v2.


In some cases, errors displayed for service requests with no set expiry date even though they successfully completed. Those errors are no longer displayed.


The Service Portal Dashboard has been updated to improve screen rendering.


With the Commander REST v2 API, you can now add existing users to multiple organizations as expected.


When an organization name is changed, using the Organization Name advanced filter for reports that use historical billing data (such as the VM Billing Report) now works as expected for the new organization name. Note that billing data created prior to upgrading to this release won't be included in reports when you filter on the new organization name.


You can now submit service requests as a Service Portal user as expected when using Connect-Client2 to communicate with the Commander REST API.


Update 3 for VMware vCenter 6.7 restores support for deploying linked clones from a template. As a result, linked clone deployments from a template are now also supported for vCenter managed systems in Commander.


If tag export is configured for a cloud account, custom attributes that have been edited are no longer removed from the remote cloud account.


Inventory synchronization for Azure cloud accounts no longer fails when an IPv6 address range is added to a subnet.


Azure systems no longer intermittently disconnect when tag synchronization is on.


Deleting a VM that had OS scan data associated with it now completes without errors.


The transaction log no longer runs out of space during upgrade.


Azure cloud accounts no longer disconnect if a SQL database uses a Subnet in a different subscription.


The exception that occurred when resolving stolen IP conflict on a VM with multiple network adapters has been resolved.


After a resource change request completes, the value for the organization quota is as expected even if the associated completion workflow fails.


You can now use V3 of the REST API to reset billing records for private clouds.


You can now validate the cloud account credentials used to configure console connections for VMs.


Applications in the Service Portal display as expected in the tree view.


When making a New Service Request or Change Request in the Service Portal, an appropriate error message now appears if an invalid value is entered in the Storage field.


The names of deleted VMs are now being purged properly, so a new VM can be deployed directly to a Datacenter or Cluster root using the same name as a previously deleted VM on VMware.


The Cloud Billing Report has been optimized to improve generation time, even with large datasets.


Improvements have been made to Commander to make it more tolerant of database deadlocks.


Billing records include timestamps as expected.


If a container (stack, auto scaling group, vApp, and resource group) was owned by a user’s organization, but wasn't owned by the user, and a VM within that container was owned by the user’s organization and was owned by the user, the user couldn't see the VM in the Service Portal Resources list.

This has now been fixed.


When a VM with IPs from the IP Pool is converted to a template, the IP addresses that were associated with that VM are now correctly released back to the IP pool.


Deleting a subnet that’s still associated to a RDS database instance no longer causes AWS to disconnect.


If a cloud account contains an invalid resource (such as a load balancer without a VPC on AWS), an error is now logged and the cloud account stays connected.


In some cases Azure accounts may disconnect. This no longer occurs.


A potential security vulnerability was identified with version 8.5.54 of Apache Tomcat. Tomcat is now upgraded to version 8.5.57.


The AWS cloud account will now remain connected when you enable the system property embotics.observation.caching and scan a remote inventory.


When performing a Change Request in the Service Portal, the Storage was set to Instance Store Volumes (xvdb) by default, which could potentially result in the loss of data. As recommended, the Storage is now set to EBS volumes by default.


Upgrades no longer fail when a custom attribute named "Folder" is in use.


The "Send Ctrl+Alt+Del" button now works as expected, so Service Portal users can now use Open Console to restart vCenter VMs.


A javascript error no longer occurs with Open Console for vCenter VMs via Commander.


Clicking rapidly around Commander Inventory no longer causes a refresh loop action.


Billing retrieval for VMware failed due to an incorrectly generated timestamp. The timestamp is now correctly generated for billing records and billing retrieval works as expected.


The Completion Workflow Module list now appears as expected in the Run Module workflow step.


In the Service Portal, all users that have "Show Performance" enabled can now view performance charts.


After upgrade to 8.2, an AWS Cloud Account can become disconnected if bare metal instances are used. Release 8.2.1 has resolved this issue.


AWS billing retrieval logic has been fixed to properly handle costs with usage start and end dates on different days.


AWS cloud accounts no longer disconnect if you delete an AMI and snapshot while synchronizing inventory.


Memory consumption has been optimized when retrieving AWS billing records.


A REST GET service request now returns a service catalog custom component's name and form metadata.


Quota approval email workflow steps failed to complete if no quota was assigned to an organization. This has been fixed and quota approval email workflow steps now complete as expected.


Viewing all IP addresses now works as expected in cases where there are two or more IP addresses configured for a VM's network interface.


The Cloud Billing report can now include negative costs, such as refunds or adjustments.


VMware web service connections now properly handle SOAP messages created by vSphere plugins that aren't supported by the standard VMware WDSL.


A GET /rest/v3/virtual-machines/ call will now always apply the correct visibility filtering.


REST v3 JSON web tokens sometimes expire before the set renewal time had elapses. This has been corrected.


AWS Reserved Instance Fee costs were inaccurate. This has now been corrected, except as noted in the Known Issues. To correct historical data, you can use the REST API billing reset.


Viewing service request details on resources with a null storage tier was causing an error. This has now been resolved.


The previous day costs in the Daily Cost Breakdown table will now be accurately represented for billing records when the billing tags changed on the previous day.


Users that belong to an AD group can now run API V3 calls as expected. They no longer have to be explicitly added to Commander.


Command workflow approval email links now direct the user to the approve/reject page, as expected.


BlueCat™ IPAM integration with Commander has been fixed.


Users are now prevented from editing service catalog entries to which they don't have access.

15220, 15217

Users couldn't sign in to the Service Portal or Commander using the SAML single sign-on (SSO) integration with the REST API. The SAML SSO integration now works as expected.


In the VM Billing Report, 0 costs are no longer shown as -1.00.


You can now search for an email address in the Service Portal after a wrong email address was entered in the form for a new service request.


Service Portal users can now submit change requests using REST v2.


Performance optimizations have been made for the retrieval of VM performance data for AWS cloud accounts with large numbers of AMIs.


Performance optimizations have been made for the retrieval of billing records.


Billing retrieval took much longer than expected, and now completes in the expected amount of time.


You can run a command workflow from the Service Portal to modify a VM's network as expected.


Inventory synchronization could fail for Azure storage accounts of type FileStorage. Inventory synchronization now works as expected.


GCP billing retrieval no longer fails in cases when there are multiple credits associated with a service.


You can now use bullets in workflow emails.


If the Billing Record generation task is unable to get data from all of the requested cloud accounts, it now registers as a failed task and produces an error event instead of just issuing a warning.


The system now waits for the deletion confirmation before completing a delete task. The maximum wait time can be set using the system property embotics.task.delete.image.timeout and has a default value of 20 minutes. If the defined value is 0 (zero), the task won't wait for the confirmation.


Under some circumstances, tasks may fail and become suspended without issuing a failure notification. This no longer occurs.


You can now skip a workflow step that has an in-progress task. When the step is skipped, the workflow will continue with the next step.


Optimized memory usage during nightly billing record retrieval.


If billing retrieval fails, an event is generated for the parent account and also for each linked child account.


Billing data for GCP was not displayed if it contained high usage values. The size of numeric fields used to store billing records has been increased to accommodate high usage values. As such, billing data for GCP is now displayed as expected.


The default field size for the CIDR Block field has been increased, so GCP data for this variable won't be truncated.


Nightly billing retrieval didn't finish successfully for all cloud accounts when a retrieval for one cloud account encountered an unexpected error. The result was that billing data wasn't updated for all cloud accounts. This has now been fixed.


For some environments with a large number of cloud accounts, the nightly scheduled task to retrieve billing records could show a decreasing percentage done. Now, as billing records are retrieved, the displayed percentage done will increase, as expected.


Service Portal users were not able to enter any text if the Message of the Day was enabled. Service Portal users can now enter text as expected while the Message of the Day is enabled.


The same AWS account can't be added twice, even if different credentials are used.


When upgrading Commander, the default number of scheduled tasks that can run was reduced from 5 to 1. The default number of scheduled tasks that can run will remain at 5, as expected.


When doing a manual billing retrieval of a cloud account with linked accounts, the linked accounts are now synced as expected.


The Cloud Billing report now correctly shows cost entries that were previously missing in the Details table when the “Group By” feature is used.


Usage and costs in the Cloud Billing Report now display as expected when using the Group By filter.


The Send Email step of the Completion Workflow now executes fully when resources are allocated in any order.


vSphere remains connected when datastores are orphaned from their hosts.


In some cases, if Commander failed to retrieve billing data for a cloud account, it wouldn't attempt to retrieve billing data for other subsequent cloud accounts. Now if Commander fails to retrieve billing data, it will log the failure, then continue to retrieve billing data for other cloud accounts.


The Service Portal Cost Dashboard could show totals that include recommendations for resources not owned by an organization. The Service Portal Cost Dashboard now only shows totals that include recommendations for resources owned by an organization.


You can now reassign ownership of policies when you delete a user account.


Total costs in the Cloud Billing Report now display as expected.


If you deleted a subnet in AWS for an Auto Scaling Group with no VMs, Commander could fail to sync with that AWS account and lose the connection to it. Now, for such a scenario, Commander will synchronize with the AWS account and maintain the connection, as expected.


Search terms that contain special characters or non-English characters will no longer return 500 errors.


Service Portal report scheduling is no longer affected by Commander time zone settings.


Refunds for AWS cloud accounts are now categorized as cost adjustments.


You can now assign descriptive names of up to 300 characters to parent organizations. This matches the length allowed for organization names.


The Choose button for the Upload Files field now displays as expected when using a custom theme.


Scheduled reports that include advanced filters with enumerations now generate as expected.


For some Azure deployments, rightsizing recommendations were created that crossed instance families creating inconsistent behavior. Recommendations now correctly suggest instance types within the same family.


When creating or editing an Azure blueprint, a validation error occurred if you only specified a variable for the deployed name instead of using the default naming convention. The validation now passes as expected.


In Azure, using REST v2, you can now create ownership policies on resource groups so that ownership is set properly when resources are deployed into resource groups.


You can no longer add duplicate AWS cloud accounts through the Commander admin console.


The properties returned from a REST v3 API call of GET /rest/v3/organizations/<name> now includes the current cost quota usage of an organization.


With REST v3, you can now filter resource groups by organization.


REST v3 requests were intermittently failing and resulting in incorrect error messages due to issues with concurrent use. This has been fixed, so multiple requests are now handled appropriately.


The user directory locking mechanism now allows for users to authenticate even when a user directory synchronization is happening.


The REST v3 API documentation now includes Bearer Authorization.


Some region codes used in billing records could cause cost analytics discrepancies because they vary from codes recognized by the Azure API. Support for some additional region codes, such as "all regions" and "krcentral", have been added.


The vSphere server no longer disconnects when one of its hosts is remediated.


When used in completion workflow steps, the Jenkins workflow plugin could cause server connections to fail when using HTTPS. The Jenkins workflow plugin now allows server connections using both HTTP and HTTPS.


Invalid XML in log4j2.xml will no longer cause upgrades to fail.


The VM Capacity Remaining values in the Cluster Capacity report now match as expected.


When using REST v2 to create an Azure deployment destination, validation now occurs as expected to ensure that the resource group is valid for the cloud account.


Administrators and Service Portal users can now power off suspended VMs with the "Stop VM" and "Power Off" options, respectively.


If a URL path used by an Execute REST workflow step included spaces, the spaces would be considered illegal characters, and the step would fail. The workflow step now appropriately handles spaces in a URL path.


Multiple Azure Enterprise Agreement accounts now show separate data for each account.


A REST v3 API /internal/system-health endpoint is now available. This endpoint provides metrics on the health of Commander.


If the advanced system property embotics.execute.command.task.succeed.unknown.exitcode is set to true, when a workflow step returns an unknown exit code, the system now behaves as expected: a warning will be recorded in the comment log, and the step will complete. If false, Commander continues to query for the result until the timeout is reached.


The maximum allowed lengths for list-based custom attribute values and organization names have been increased.


For Service Portal users that are permitted to modify VM networks, you can now limit the networks available to those users according to their organization membership and the VM placement destination.