vRealize Business for Cloud 7.0.1 Release Notes

vRealize Business for Cloud | 15 March 2016 | Build 3631900

Last updated: 25 April 2016

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes covers the following topics:

What's New

  • Branding Change. vRealize Business Standard is rebranded to vRealize Business for Cloud. The user interface and the documentation use the new product name.
    • vRealize Business for Cloud refers to both Standard and Advanced editions.
    • vRealize Business for Cloud Standard refers to the Standard edition, which is accessible by vCloud Suite Standard and vRealize Suite Standard licenses.
    • vRealize Business for Cloud Advanced refers to the Advanced edition, which is accessible by the vRealize Business for Cloud, vRealize Business Enterprise, vCloud Air Advanced and Enterprise, and vRealize Suite Advanced and Enterprise licenses.

  • Supports additional licenses. In addition to vRealize Business for Cloud, vRealize Business Enterprise, and vCloud Suite licenses, you can access vRealize Business for Cloud by using the vRealize Suite license. However, the vRealize Business for Cloud user interface options vary based on the license key edition. You can see all the available options by using the vRealize Suite Advanced and Enterprise licenses. Certain options might not be available as part of vRealize Suite Standard license.

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

  • Supports the Customer Experience Improvement Program (CEIP). vRealize Business for Cloud participates in VMware’s CEIP. It allows VMware to collect technical details about vRealize Business for Cloud usage anonymously. This helps VMware to improve the product and features you use most often and to help solve problems.

  • Displays public cloud historical data. You can view the public cloud account details and cost for the past months, similar to vCenter Server virtual machine historical reports.

  • Supports new currencies. vRealize Business for Cloud supports several additional currencies for cost calculation, which you can set during vRealize Business Standard deployment. The new currencies supported are Thai Baht (THB), Danish Krone (DKK), Brazilian Real (BRL) and Mexican Peso (MXN).

  • Change in cost projection calculation. The projected expense for public cloud and vCloud Air is sum of total cost till date and the cost of previous day multiplied by the remaining number of days for the current month.

  • Assign Business Management Controller roles. You must explicitly assign the Business Management Controller role to the vRealize Automation users to allow access to vRealize Business for Cloud. In earlier releases, all the Business Management administrators were automatically assigned the Business Management Controller privileges.

  • Enhanced debug and supportability. You can enable debug logging to collect the debug level information in the log files, which helps during support and debugging the issues.

  • Download support files for remote data collection. You can download the support file to get support for the remote data collection problems.

  • Export vRealize Business for Cloud log files. You can configure the vRealize Business for Cloud log files to export your setup details to the system log servers such as vRealize Log Insight for analyzing the operations and provide faster troubleshooting procedures.

  • Updated glibc library. The glibc library has been updated to address cve-2015-7547.

  • Localization support. vRealize Business for Cloud 7.0.1 is available in following languages:
    • English
    • French
    • German
    • Japanese
    • Korean
    • Spanish
    • Simplified Chinese
    • Traditional Chinese
    • Note: Spanish locale is supported in documentation only, not on the UI.

Documentation

Resolved Issues

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

Migration Issues

  • After you deploy vRealize Business Standard 7.0, DNS server is not auto-detected
    If you are deploying vRealize Business Standard 7.0 on vCloud Director, the DNS settings are not updated automatically.
    This issue is resolved in this release.
  • After vRealize Business Standard 7.0 migration, some AWS reports do not display data
    After migrating to the vRealize Business Standard 7.0 version, AWS resources are not migrated. As a result, the AWS charges page and the AWS Resources report do not display data. However, you can see data in the AWS Overview page and the AWS Instances reports.
    This issue is resolved in this release.
  • After migrating your vRealize Business Standard 6.0 to 7.0, the vCloud Air virtual machine data is not migrated
    After you migrate vRealize Business Standard 6.0 to the 7.0 version, the vCloud Air virtual machines report does not display any data.
    This issue is resolved in this release.
  • After migrating to vRealize Business Standard 7.0, the customized utilization values defined for CPU and memory in an earlier version are not migrated to the new version
    After you migrate to vRealize Business Standard 7.0, the expected CPU and memory utilization values set on an earlier vRealize Business Standard version are not migrated to vRealize Business Standard 7.0.
    This issue is resolved in this release.
  • After vRealize Business Standard 7.0 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 migrated setup. The vCenter Server policies defined by resource pools are not migrated.
    This issue is resolved in this release.

Integration Issues

  • An internal server error appears when you select a vCloud Director identification or tag for adding a cross-infrastructure policy
    Though vCloud Director is not connected to vRealize Business Standard, when you are adding additional services to the pricing policy the vCloud Director identifications and tags appear for selection. This results in an internal server error.
    This issue is resolved in this release.
  • Issue with edit pricing functionality on Mozilla Firefox
    If you register vRealize Business Standard 7.0 with vRealize Automation 6.2.3, the edit pricing page does not open in the Firefox browser.
    This issue is resolved in this release.

Configuring and Provisioning Issues

  • Exporting the virtual machine report might fail
    Attempts to export virtual machine report that contains more than 10,000 records might fail.
    This issue is resolved in this release.
  • An incorrect charge value is displayed on the Business Unit Details page
    When you click a business unit on the Business Unit List page, the CPU charge includes both CPU and RAM charges in the Charge Distribution widget and its tooltip. Instead, the CPU value must include only CPU charges.
    This issue is resolved in this release.
  • When you click the search icon, the search operation does not work
    After you enter a string in the search text box, when you click the search icon, vRealize Business Standard does not search for the matching records.
    This issue is resolved in this release.
  • Unable to open the custom reports saved with HTML tag names
    While saving a report, if you have used the HTML tag names, for example scripts, HTML tags, SQL injection, you cannot open the report from the Custom Reports page.
    This issue is resolved in this release.
  • While importing a virtual machine for cloud comparison, you cannot search for the virtual machine
    The Search VMs option for importing the virtual machine under Cloud Comparison does not work.
    This issue is resolved in this release.
  • The AWS virtual machine count on the AWS Overview page is different from the count shown on the Pricing and Edit Hierarchy page
    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, which results in a different count.
    This issue is resolved in this release.
  • The vRealize Automation data collection fails if vRealize Automation has multi machine blueprints
    vRealize Business Standard ignores machines that do not collect blueprints or whose external reference ID is null.
    This issue is resolved in this release.
  • If you upgrade vRealize Automation and then upgrade vRealize Business for Cloud, the upgrade completes with the system synchronization error
    After upgrading vRealize Business Automation and vRealize Business for Cloud, you see a Can't find 'Blueprint' error in the itfm-server.log file. For more information, see KB 2141411.
    This issue is resolved in this release.

Known Issues

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

Upgrade Issues

You might see the following issues when you upgrade from vRealize Business Standard 7.0 version to 7.0.1.

  • SSH is disabled after upgrade
    After a successful upgrade, when you reboot the virtual appliance, the SSH setting is disabled, by default.
    Workaround: Enable the SSH settings manually. For more information, see the Enable or Disable SSH Settings section in the vRealize Business for Cloud Install Guide.
  • After upgrade, the first vRealize Business for Cloud reboot fails
    After upgrade from 7.0 to vRealize Business for Cloud 7.0.1, only the first reboot of VA might get stuck and hence the virtual appliance might stop responding.
    Workaround: To fix the issue, power off and power on the vRealize Business for Cloud virtual appliance.
  • Unable to open the custom reports after upgrade
    After you upgrade from 7.0 to 7.0.1, you cannot open the custom reports that you had created on the 7.0 setup.
    Workaround: Re-create the custom reports on the 7.0.1 setup.

Migration Issues

You might see the following issues when you migrate from vRealize Business Standard 6.2.3 version to 7.0.1.

  • After you migrate vRealize Automation and vRealize Business Standard from 6.2.3 to 7.0.1, 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 policy section displays duplicate entries of blueprint names.
  • After migrating to the 7.0.1 version, 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 vRealize Business for Cloud 7.0.1 migration, the 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, the vRealize Automation and vCloud Director pricing policies 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, which results in a different count.

Integration Issues

  • You cannot provision vRealize Automation with a new blueprint
    When you attempt to provision vRealize Automation by using the new blueprint, the provisioning fails with an error message.
    Cannot calculate cost. Contact your system administrator to review the vRA appliance logs.
    Workaround: Perform the following steps:
    1. Trigger the vRealize Automation data collection.
    2. Trigger cost calculation on vRealize Business for Cloud.
    3. Provision the machine.
  • After vRealize Business for Cloud 7.0.1 upgrade, you cannot provision vRealize Automation with a blueprint
    After upgrade, attempt to provision vRealize Automation by using a blueprint fails with an error message.
    Request failed while fetching item metadata: Error communicating with Pricing service.
    Workaround: Perform the following steps:
    1. Unregister vRealize Business for Cloud with vRealize Automation.
    2. Generate the self-generated certificate for vRealize Business for Cloud.
    3. Re-register vRealize Business for Cloud with vRealize Automation.
    4. Wait for 10 minutes for all services start.
    5. Start provisioning vRealize Automation.
  • 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

  • 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 do not appear.
  • 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 new 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.
    Workaround: Manually modify the AWS currency to match the currency configured in vRealize Business for Cloud.

User Interface Issues

  • A part of add or edit dialog boxes are truncated
    When you open the add or edit dialog boxes on vRealize Business for Cloud, you might not see the complete page.
    Workaround: To view the complete vRealize Business for Cloud user interface, zoom out the page and refresh the browser.

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.
    Workaround: Rename the vCenter Server alias name in the English locale.

Known Issues from Earlier Release

In addition to these new issues found in this release, some known issues in vRealize Business Standard 7.0.0 release are also applicable. Click here.

Upgrade Issues from Earlier Release

Following are the upgrade known issues carried from earlier release, which are applicable in this release also.
  • 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 so 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.
  • The budget defined in vRealize Business Standard 6.2.x is not migrated to 7.0.1
    If you migrate your vRealize Business Standard 6.2.x virtual appliance that is categorized based on vCloud Director, the budget values are not migrated to the 7.0.1 setup.
    Workaround: Import the budget values manually into the 7.0.1 setup.
    1. Upgrade to vRealize Business for Cloud 7.0.1.
    2. Open the Edit Budget page on the vRealize Business Standard 6.2.x setup and export the budget details to the XLS format.
    3. Open the Edit Budget page on the 7.0.1 setup and create a template.
    4. Copy the budget lines from the XLS file and replace them in the template file.
    5. Import the updated template file into the 7.0.1 setup.
  • The advanced pricing policies defined are not migrated during vRealize Business for Cloud 7.0.1 migration
    When you migrate to vRealize Business Standard 7.0.1, the advanced pricing policies based on vRealize Automation or vCloud Director categorization are not migrated.
  • The 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 migrating to vRealize Business for Cloud 7.0.1, the server hardware batch information is not migrated
    When you migrate vRealize Business Standard from 6.0 to vRealize Business for Cloud 7.0.1, the server hardware batch information 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 vRealize Business for Cloud 7.0.1 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, the account details are not displayed in the Service ID section of the vCloud Air Overview page.
    Workaround:
    1. Rollback the upgrade.
    2. Before your upgrade, perform the following steps:
      1. Rename or modify the vCloud Air account names by deleting the special characters in the vRealize Business Standard 6.x setup.
      2. Run the vCloud Air data collection process to refresh the name changes.
  • After upgrade, the data is not synchronized
    After you upgrade vRealize Business Standard to 7.0.1 and register the instance with vRealize Automation, the data collection is not seen on the UI. Additionally, you cannot trigger the process manually.
    Workaround: You must wait for at least twelve hours after registering with vRealize Automation or wait for the data collection process to complete.
    For AWS data collection, you must trigger the process manually.
  • 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.

Integration Issues from Earlier Release

Following are the integration known issues carried from earlier release, which are applicable in this release also.
  • 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.
    Workaround: To avoid the issue, increase the PermGen parameter size to 512 MB. The value of the parameter is 256 MB, by default.
    1. Log in to the vRealize Business for Cloud virtual appliance.
    2. Open the setenv.sh file in /usr/local/tcserver/vfabric-tc-server-standard/itbm-data-collector/bin/.
    3. Change the value of MaxPermSize from 256m to 512m.
      -Xms512m -Xmx1024m -XX:MaxPermSize=512m -XX:+HeapDumpOnOutOfMemoryError
    4. Save the changes.
    5. Restart the data collection process by running the monit restart itbm-data-collector command.
  • 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.
  • 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 with a non-Latin 1 character, 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.
  • 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.
  • 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.
    Workaround: Access vRealize Business for Cloud after some time.