vRealize Business for Cloud 7.1 Release Notes

vRealize Business for Cloud | 23 August 2016 | Build 4269488

Last updated: 23 August 2016

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

  • Supports multiple versions of vRealize Automation. vRealize Business for Cloud 7.1 is compatible with the vRealize Automation 6.2.3, 6.2.4, 7.0, 7.0.1, and 7.1 releases.

  • Allows integration with external VMware Identity Manager. You can use standalone vRealize Business for Cloud 7.1, without deploying vRealize Automation.

  • Provides seemless integration with vRealize Operations Manager. vRealize Business for Cloud 7.1 provides seemless integration with vRealize Operations Manager by enabling additional configuration settings. For more information, see KB 2146836.

  • Includes UI changes. The Overview page is updated with new widgets to provide more information about cost and consumption.

  • Supports new versions of Transport Layer Security (TLS) encryption protocol. By default, vRealize Business for Cloud 7.1 has enabled TLS 1.1 and TLS 1.2 versions, and has disabled the 1.0 version. However, you can enable TLS 1.0 version, manually. For more information, see Enable or Disable TLS.

  • Provides a new version of reference database. A new version of the reference database is available with vRealize Business for Cloud 7.1.

  • Segregates the Azure EA account cost. vRealize Business for Cloud 7.1 groups the overall cost of the Azure account based on the individual billing account.

  • Supports Spanish locale. vRealize Business for Cloud 7.1 supports Spanish locale UI also. The following languages are supported:
    • English
    • French
    • German
    • Japanese
    • Korean
    • Spanish
    • Simplified Chinese
    • Traditional Chinese

Documentation

Resolved Issues

The following issues have been resolved in this release of vRealize Business for Cloud.

Upgrade Issues

  • vRealize Automation tab does not appear after vRealize Business for Cloud upgrade.
    After you upgrade to vRealize Business for Cloud 7.0.1 version, the vRealize Automation tab does not appear on the vRealize Business for Cloud web console.
  • SSH is disabled after vRealize Business for Cloud upgrade
    After vRealize Business for Cloud upgrade, when you reboot the virtual appliance, the SSH setting is disabled, by default.
  • After upgrade, the first vRealize Business for Cloud reboot fails
    After vRealize Business for Cloud upgrade, the first reboot of virtual appliance might fail and stops responding.
  • After upgrade, the vCloud Air Overview page does not display the accounts with special characters
    If you have added vCloud Air accounts with names that contain special characters (like colon (:), slash (/)), the account details are not displayed in the Service ID section of the vCloud Air Overview page after upgrade.
  • Unable to open the custom reports after upgrade
    After you upgrade, you cannot open the custom reports that you had created in an earlier version.
  • Attempts to upgrade might fail in a large environment that has around 10,000 virtual machines
    In a large environment with approximately 10,000 virtual machines, the upgrade process might stop responding without any notifications.
  • After vRealize Business for Cloud 7.0.1 upgrade, you cannot provision a blueprint in vRealize Automation
    After upgrade, an attempt to provision vRealize Automation by using a blueprint fails with the following error message:
    Request failed while fetching item metadata: Error communicating with Pricing service.

Migration Issues

  • The budget defined in vRealize Business Standard 6.2.3 is not migrated to the 7.0.1 setup
    If you migrate your vRealize Business Standard 6.2.3 setup to 7.0.1, the budget values are not migrated to the 7.0.1 setup.
  • After you migrate vRealize Automation and vRealize Business Standard from the 6.2.3 version, duplicate entries of a blueprint appear
    If you migrate vRealize Automation from 6.2.3 to 7.0.1 and then migrate vRealize Business Standard from 6.2.3 to 7.0.1, the Additional Services window in the Edit Pricing section displays duplicate entries of blueprint names.
  • After vRealize Business for Cloud 7.0.1 migration, vRealize Automation and vCloud Director policies are not migrated
    When you migrate vRealize Business Standard 6.2.3 to vRealize Business for Cloud 7.0.1, vRealize Automation and vCloud Director pricing policies are not migrated.
  • Virtual machine up-time data is not migrated after vRealize Business for Cloud 7.0.1 migration
    After you migrate to vRealize Business for Cloud 7.0.1, the information about the total duration of the powered on virtual machines is not migrated.
  • After vRealize Business for Cloud 7.0.1 migration, only some vCenter Server polices types are migrated
    Though you have vCenter Server policies defined by hosts, clusters, and resource pools in vRealize Business Standard 6.2.3, the pricing policies defined only by clusters and hosts are migrated to the vRealize Business for Cloud 7.0.1 setup. The vCenter Server policies defined by resource pools are not migrated.
  • After migration, the AWS virtual machine count on the AWS Overview page is different from the count shown on the Pricing and Edit Hierarchy page
    After you migrate to vRealize Business for Cloud 7.0.1, the AWS Overview page includes the deleted virtual machines count for the current month. However, the Pricing and Edit Hierarchy pages do not include the deleted virtual machines, and display a different count as a result.
  • After migrating, the cost calculation might appear as failed
    After you migrate from 6.2.3, you might see that cost calculation status as failed.
    Workaround: Trigger the cost calculation process manually.
  • After migrating, the purchase and lease batch information are not migrated
    When you migrate vRealize Business Standard to vRealize Business for Cloud 7.0.1, the purchase and lease batch information added under each server hardware are not migrated.
  • Any changes to the DRL file are lost after upgrading to vRealize Business for Cloud 7.0.1
    After you upgrade 7.0 to vRealize Business for Cloud 7.0.1, the DRL files of your earlier vRealize Business Standard version are deleted, and your changes are lost.
    Workaround: Reconfigure the DRL file manually and upload the file into vRealize Business for Cloud 7.0.1. For more information, see the Update the DRL file for Cloud Comparison section in the installation guide.
  • After you migrate to vRealize Business for Cloud 7.0.1, the expenses defined on data centers are lost
    When you migrate your vRealize Business Standard 6.2.3 setup to vRealize Business for Cloud 7.0.1, expense data defined on data centers is not migrated.
  • After 7.0.1 migration, vRealize Business for Cloud prompts for license key
    Even though you had applied license for vRealize Business Standard 6.2.3, after migrating to 7.0.1, vRealize Business for Cloud prompts to reenter the license key.
    Note: The license prompt does not appear if you use vCloud Suite license in the earlier version.

Integration Issues

  • You cannot provision a new blueprint in vRealize Automation
    When you attempt to provision vRealize Automation by using the new blueprint, the provisioning process fails with an error message.
    Cannot calculate cost. Contact your system administrator to review the vRA appliance logs.
  • Cost calculation fails in vRealize Business for Cloud 7.0.1 with a missing ID error message
    During cost calculation, you see the following error, which results in cost calculation failure:
    Can't find 'Blueprint' with id
  • An out-of-memory error might occur when multiple instances are connected to vRealize Business for Cloud
    When multiple types of accounts such as vCenter Server, vCloud Director, SRM, AWS, Azure, and vCloud Air are added to vRealize Business for Cloud, you might see an out-of-memory error. This error occurs because the configured value for JAVA PermGen is insufficient.
  • vRealize Automation data collection fails in vRealize Business for Cloud
    When invalid entities (such as disks, VMs)  are reported from vRealize Automation, the data collection fails in vRealize Business for Cloud, and the following error is written to the facts-repo.log file.
    Failed to persist SnapshotRequest com.google.common.util.concurrent.UncheckedExecutionException: java.lang.NullPointerException
  • vCenter Server data collection fails
    During data collection, the storage synchronization might fail with the following error due to failed API response from vCenter Server for a particular storage policy.
    javax.xml.ws.WebServiceException: java.lang.IllegalArgumentException: prefix vim25 is not bound to a namespace
  • When you attempt to save a vCloud Air account information in vRealize Business for Cloud, you see an unexpected error message
    After you enter the required vCloud Air account information to add or edit in vRealize Business for Cloud through proxy, you see the following error message:
    Unexpected error occurred
  • You cannot retrieve the data from vCenter Server configured in vRealize Operations Manager
    If you are using vRealize Operations Manager 6.0.x, 6.1.x, or 6.2.x, when the data collection occurs after you add a vCenter Server in vRealize Business for Cloud, the following error appears:
    Unable to retrieve data from vROps

Configuring and Provisioning Issues

  • Datastores and services do not appear in the list for vCenter Server and AWS
    On the Pricing panel, when you open Private Cloud(vSphere) > vCenter Cluster or Public cloud (AWS) > AWS Services, the datastores list or the services list does not appear.
  • Unable to access the vRealize Business for Cloud server when the server is overloaded
    If the vRealize Business for Cloud server is overloaded, you see an internal server error.
  • vRealize Business Standard does not save the manually updated percentage value for the Total cost surcharge option on the Pricing page
    When you modify the percentage value in the Total cost surcharge option on the Pricing page, the updated value appears on the UI. However, the value is not saved in the server.
  • After you move a host to a new data center, the expense values are not displayed for the cost drivers of the new data center
    After you create a data center, when you move a host from an existing data center to a new data center, the expense data does not appear. The issue occurs because the data calculation or synchronization does not happen.
  • AWS cost values always appear in the USD currency
    Even after you configure vRealize Business for Cloud currency to a format other than USD, the AWS values appear in the USD format.
  • Microsoft Azure Enterprise Account data collection fails
    vRealize Business for Cloud 7.0.1 cannot collect Azure data for enterprise accounts, and displays the following error message:
    Error : An unexpected error has occurred during Microsoft Azure data collection
  • vRealize Business for Cloud 7.0.1 displays an incorrect date on the Overview page
    The Overview page in vRealize Business for Cloud 7.0.1 displays the name of the previous month, instead of the current month. However, the cost displayed is for the current month.
  • The NIC count is incorrect under Expenses
    When you deploy vRealize Business for Cloud 7.0.1, the NIC count displays incorrect values after data collection. Also, the count increases for every vCenter Server data collection.
  • During pricing recalculation, the virtual machine price values are updated incorrectly
    During pricing recalculation, the virtual machine price values are updated from the date of recalculation, instead of updating from the start date of virtual machine.
  • Cost Calculation fails on certain virtual SAN setups
    Cost calculation fails with the NullPointerException when virtual SAN reports null values for the host disk fields.
  • The tags with the same name from different vCenter Server appear as two individual entries
    If you have two tags with the same name in two vCenter Servers, the tag names appear twice in the Edit Business Hierarchy. Instead, the tag name must appear once, irrespective of the vCenter Server.
  • Cost calculation does not complete
    Although vCenter Server and vRealize Automation data collection completes and shows the system status with the green icon, the cost calculation does not complete, and a spinning icon is displayed even after you restart the service.
  • While editing a vCenter Server storage pricing policy, the datastore clusters are not populated
    When you click the Storage tab under vCenter Server Edit Pricing Policy, the list of datastore clusters and the total number of datastores does not appear.
  • The vRealize Business for Cloud proxy configuration does not decode the encoded proxy password
    When the proxy password contains the special characters, vRealize Business for Cloud virtual appliance does not decode the password.
  • The inventory synchronization fails during vCenter Server data collection
    During vCenter Server data collection, if there is an issue with the tag, the synchronization process fails with one of the following errors:
    • com.vmware.vim.binding.vmodl.fault.SecurityError
    • The object has already been deleted or has not been completely created

User Interface Issues

  • The vCenter Server Storage grouping strategy label displays Datastore Name, instead of VMs.
    While adding or editing pricing policies, the storage grouping strategy displays the list of VMs, but the label name is Datastore Name, instead of VMs.
  • You cannot see more than ten vCenter Servers on the Administration tab.
    On the Administration tab, if you have added more than ten vCenter Servers, you cannot scroll the list to see all the vCenter Servers.

Localization Issues

  • When you attempt to add a vCenter Server with a localized name to the additional services, HTTP 401 error appears
    Under Edit Pricing > Additional Services, when you select a vCenter Server with the localized alias name, you see an HTTP Status 401 error message.

Reports Issues

  • The GroupBy option in the Reports section does not work on columns with a period (.) in the names
    If a period (.) exists in the column name, the GroupBy option for the column in the Reports section does not work.
  • When you export the reports individually, you cannot see all the report columns
    When you export reports individually, some columns are not visible or not exported. However, you can see and export these missing columns, when you export all reports together.

Known Issues

The following issues are known to occur in vRealize Business for Cloud 7.1, and are grouped as follows:

Upgrade Issues

  • After upgrade, the earlier month costs of an Azure EA account do not appear
    After you upgrade vRealize Business for Cloud 7.0.1 to 7.1, the cost of an Azure EA account for the months prior to the current month do not appear.
    Workaround: Remove the Azure EA account and add it again into vRealize Business for Cloud 7.1.

Migration Issues

  • After migration, the cost calculation does not run automatically
    After you migrate from 6.2.3 to vRealize Business for Cloud 7.1, the cost calculation process does not run automatically and displays inconsistent data on the UI.
    Workaround: To fix the issue, after migration from 6.2.3 to 7.1, you must run the cost calculation process manually for the first time.

Integration Issues

  • You cannot upload the latest reference database file
    When you attempt to upload the latest available reference database file into vRealize Business for Cloud by clicking Administration > Update Reference Database > manual update process > Browse, you see the following error message:
    Unable to load the reference file. See the log files for more details.
    Workaround: To fix the issue, perform the following steps:
    1. Log in to vRealize Automation.
    2. Navigate to the container.js file at /var/lib/vcac/server/webapps/vcac/WEB-INF/classes/containers/default/.
    3. Update the gadgets.jsonProxyUrl.maxPostSize parameter with a value greater than the size of the reference database ZIP file.
    4. Restart the vRealize Automation virtual machine.

Configuring and Provisioning Issues

  • Incorrect endpoint name is displayed for vCloud Director provisioned virtual machines in the vRealize Automation Virtual Machine report
    vRealize Automation Virtual Machine report displays vCloud Air as the endpoint for the virtual machines provisioned in vCloud Director through vRealize Automation 6.2.5.

User Interface Issues

  • The UI text is truncated on the add and edit pages of the public cloud accounts
    You might not see the complete text on the add or edit page for the public cloud accounts in the Administrator section. For example,
    • Add or Edit AWS account page
    • Add or Edit Azure account page
    • Add or Edit Cloud Providers for Comparison
    Workaround: To resolve the issue, zoom out the browser or increase the screen resolution to 1440*900.

Report Issues

  • You cannot export the filtered reports
    When you click Search on a report and enter a string to filter a report, you can see the matching records on the UI. However, when you export the filtered report, all the records appear in the XLS file, instead of only the matching records.

Known Issues From Earlier Releases

In addition to these new issues found in this release, some known issues from the earlier releases are also applicable. Click here.

Integration Issues From Earlier Releases

  • The Running price values might not match in vRealize Business for Cloud and vRealize Automation
    The Running price that is shown in the Consumption Analysis in vRealize Business for Cloud might be different from the running price values displayed in vRealize Automation.
    This is because, vRealize Business for Cloud calculates the running price on daily basis based on power state of virtual machines. However, vRealize Automation displays the running price based on the upfront cost which is multiplied with the lease days.
  • Two AWS services with the same name can have two different policies in vRealize Business for Cloud
    When two different AWS accounts have the same service names (for example, Amazon Kinesis) in Edit Pricing -> Public Cloud (AWS), they can have two different policies set corresponding to these services.
    Note: Currently you cannot identify the account to which the service is associated with.
    In case of multi-machine blueprint, it is classified both under Private and Hybrid Cloud (vCloud Air). To set the prices for multi-machine blueprint, you must define the prices for the blueprints that are classified under the Private category.

  • The vRealize Automation user session does not timeout
    When you have registered vRealize Business for Cloud with vRealize Automation, vRealize Automation ignores its default timeout interval and keeps the user session active indefinitely even without user actions.

Configuring and Provisioning Issues From Earlier Releases

  • An error might appear when you click a business unit on the Business Units List page
    On the Business Unit List page, when you click on a business unit name that has a non-Latin 1 character or a slash ("/"), an HTTP Status 404 error appears.
    Workaround: Use the ISO-8859-1 character set for defining the business unit names. vRealize Business Standard supports only the Latin-1 format, and not the UTF-8 format. And, do not use a slash ("/") in the business unit names.
  • The secure channel is unable to use HTTP proxy environment variables, which results in failure of user creation and token
    Due to the operating system upgrade from SUSE Linux Enterprise Server (SLES) 11 to SLES12, the bifrost service is unable to use environment variables such as http_proxy. When vRealize Automation is integrated with IaaS, the proxy configuration might block certain calls related to IaaS because of the configuration through the system properties.
    Workaround: To resolve the issue, perform the following steps:
    1. Set the proxy in VAMI.
    2. Enable SSH for the vRealize Business for Cloud. For more information, see the Enable or Disable SSH Settings section in the vRealize Business for Cloud Install Guide.
    3. Run ps -ef|grep bifrost.
    4. Run kill -9 , where pid is the process that is running the WAR file.
    5. Run nohup /usr/java/jre-vmware/bin/java $JAVA_OPTS -Daccess.token.file=/usr/local/bifrost-client/access.token -jar /usr/local/bifrost-client/bifrost-client-1.0.0.war --server.port=9876 > /dev/null 2>&1 &.
    6. To verify the fix, run the following commands:
      1. ps -ef|grep bifrost.
      2. cat /proc//environ
    7. Find the http_proxy variable in the output.