vRealize Business for Cloud 7.3.1 Release Notes

|

vRealize Business for Cloud | 24 August 2017 | Build 6400451

Last updated: 05 October 2017

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

What-If Analysis: VMware Cloud on AWS Assessment

You can assess the cost of running your applications and VMs on VMware Cloud on AWSvRealize Business for Cloud calculates and displays the cost of running your applications and virtual machines on VMware Cloud on AWS with similar configurations in your private cloud. You can see the comparative cost based on the utilization for both your private cloud and VMware Cloud on AWS.

User Interface: Menu changes

vRealize Business for Cloud 7.3.1 is updated with menu changes to provide enhanced and consistent user experience.

Note: The vRealize Business documentation is not updated with the user interface menu changes for the 7.3.1 release.

  • Private Cloud menus. The Operational Analysis section is merged with Expenses to provide a holistic view of private cloud computation at a single location.
    • Overview – Provides a summary of total monthly cost and constituent cost drivers.
    • Cost Drivers – Provides detailed information about cost drivers and the flexibility to enter custom values.
    • Cluster Base Rate – Provides information about how cluster level base rates are derived from total infrastructure cost.
    • VM Costs – Provides information about how VM costs are derived from cluster base rates.

    The UI menu changes between the previous release and this release are compared in the following table.

    Before Now
    Business Management > Expenses > Private Cloud Business Management > Expenses > Private Cloud > Overview
    Business Management > Expenses > Private Cloud > Edit Expenses Business Management > Expenses > Private Cloud > Cost Drivers
    Business Management > Operational Analysis > Private Cloud > Edit Utilization Business Management > Expenses > Private Cloud > Cluster Base Rate
    Business Management > Operational Analysis > Private Cloud Business Management > Expenses > Private Cloud > VM Costs

  • Consumption menus. Business Units, Applications (Business Services), and Budgets are listed under Consumption. The shortcuts to these functionalities are available as they were, such as from Charges and Business Unit Consumption.
  • The UI menu changes between the previous release and this release are compared in the following table.

    Before Now
    Business Management > Consumption > Business Units List > Edit > Edit Business Hierarchy > Business Units Business Management > Consumption > Business Units
    Business Management > Consumption > Business Units List > Edit > Edit Business Hierarchy > Business Services Business Management > Consumption > Applications
    Business Management > Consumption > Business Units List > Edit > Edit Budget Business Management > Consumption > Budgets
    Business Management > Consumption > Pricing and Charges > Pricing Business Management > Consumption > Pricing
    Business Management > Consumption > Pricing and Charges > Charges Business Management > Consumption > Charges
    Business Management > Consumption > Pricing and Charges > Business Units List Business Management > Consumption > Business Unit Consumption
    Business Management > Consumption > Pricing and Charges > Business Units Map Business Management > Consumption > Business Units Map

Important Information

Before upgrading to vRealize Business for Cloud 7.3.1, you must read the KB article 2151835.

Documentation

Resolved Issues

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

Deployment Issues

  • After deploying the vRealize Business appliance VMware tools do not run on vRealize Business appliance.
    After deploying and powering on the vRealize Business appliance, VMware Tools do not run, preventing a graceful shutdown or restart. The appliance need to be reset to keep the VMware Tools running.

Configuring and Provisioning Issues

  • The vCenter Server VMs provisioned by vRealize Automation show the storage charges value as 0.
    For VMs provisioned by vRealize Automation, the storage pricing is not being calculated based on the defined policy in vRealize Business.
  • vCenter Server slows down or stops responding when it is added as an endpoint in vRealize Business.
    vCenter Server slows down gradually when it is added to vRealize Business as an endpoint.

Cost Calculation Issues

  • Daily cost calculation stops running after a period of time.
    In vRealize Business 6.x versions, an issue with the Quartz Scheduler component causes the scheduled runs of cost calculation to fail after a period of time. Because the cost calculation does not run for a period of time, the following issues might occur:
    • Costs appear zero or lesser than the actual value.
    • vRealize Business is not up to date with the change in the vCenter Server inventory and the number of VMs does not match with the number of VMs in the vCenter Server.
    • Business units are not created according to the actual inventory.
  • Cost calculation wrongly appears as succeeded.
    In vRealize Business 6.x versions, unscheduled cost calculations appear to be successful because of an issue in the system status. This lets you believe that the cost calculations are successful when the cost calculations are actually not running.

Known Issues

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

Upgrade Issues

  • If you are using the VMware Identity Manager integrated vRealize Business for Cloud setup, after 7.3.1 upgrade, the administrator user has read-only permissions, instead of all permissions.
    After you upgrade VMware Identity Manager integrated vRealize Business for Cloud setup to 7.3.1, though you log in as an administrator user, you cannot perform administrator tasks.
    Workaround: vRealize Business for Cloud 7.3.1 creates a new user group by the name vRBC_Administrator. You must add the administrator user to this new group to perform all administrator tasks.
  • After vRealize Business for Cloud 7.3.1 upgrade, vCloud Director pricing policies are not retained.
    When you upgrade vRealize Business for Cloud 7.3.1, vCloud Director pricing policy values that you had defined are not available.
    Workaround: You must redefine the pricing values.
  • After vRealize Business for Cloud 7.3.1 upgrade, the addition of NSX Manager does not trigger the cost calculation automatically.
    After you upgrade vRealize Business for Cloud 7.3.1, when you add a NSX Manager, the data collection completes and shows green indication. However, cost calculation does not trigger automatically and you do not see the cost changes on the UI.
    Workaround: Trigger the cost calculation for NSX manually or wait until the next default cost calculation completes.
  • After upgrade, you do not see Azure endpoints that were added in the earlier version of vRealize Business for Cloud.
    After you upgrade vRealize Business for Cloud, you do not see the Azure endpoints on the upgraded setup.
    This issue happens when you have an Azure endpoint without completing the data collection process. All Azure endpoints must have completed the data collection process at least once (irrespective of successful or unsuccessful process). You must add all the Azure endpoints in the upgraded vRealize Business for Cloud setup.

Migration Issues

  • After migration, the public cloud costs for the sample group virtual machines are reduced.
    After you migrate from 6.2.3, you see the reduced costs for the public cloud sample groups under the Planning section. Also, though you had set the service offerings as Dedicated Cloud or Virtual Private Cloud, the service offering is changed to On Demand after migration.
    Workaround: To get the correct cost, you must manually change the service offering according to the previous setting after migration.
  • After migration, the pricing policy names are not visible in the vRealize Automation virtual machines report.
    Since the 6.2.3 version did not support pricing policies, after you migrate 6.2.3 to the later releases, the Pricing Policy Name column displays an empty field value.
    Note: The empty policy name appears only for the month when you completed the migration or when or the pricing policy has changed. However, you see the policy names in the later months.

Deployment Issues

  • When powering on the vRealize Business appliance, the vSphere Web Client issues the following question: "Cannot connect the virtual device IDE0:0 because no corresponding device is available on the host. Do you want to try to connect this virtual device every time you power on the virtual machine?"
    By default, the vRealize Business appliance's virtual CD/DVD drive is set to connect at power on. When the appliance fails to find media at bootup, the question described in the symptom is issued.
    Workaround:See VMware knowledge base article 2151287.

Integration Issues

  • The monit command shows incorrect status about data collectors.
    Though the data collectors are running, the monit summary command might show incorrect status stating that the service is not running.
    The issue occurs when the PID file for data collectors is missing in the /usr/local/tcserver/vfabric-tc-server-standard/itbm-data-collector/logs directory.
    Workaround:To fix the issue, restart the vRealize Business for Cloud virtual appliance.

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.
  • Incorrect count of network service policy is displayed after deletion of a policy.
    After you delete a network policy from the Edit Pricing page, the count is not reduced under the Pricing > Other Private Cloud Services section.
  • Incorrect count of VMs is displayed after deletion of VMs or organization.
    After you delete a VM or an organization, the VM count does not reduce under the Consumption > Pricing > Edit Pricing section.

User Interface Issues

  • You see an internal error message on the user interface intermittently.
    During the vRealize Business for Cloud processes such as cost calculation, policy creation, or cloud comparison, though the process is running correctly, you might see the following error on the user interface:
    System unable to process your request at this time due to some internal error. Please reload the page and try gain later.
    Workaround: Ignore the error and wait until the completion of the respective process.
  • You do not see the VMware Cloud on AWS logo on Internet Explorer.
    If you are using Internet Explorer, when you attempt to add VMware Cloud on AWS for cost comparison on the Manage Cloud Providers screen, you do not see an icon.
    Workaround: Use a different browser such as Mozilla Firefox, Google Chrome, and Microsft Edge.

Report Issues

  • You see blank entries in the Daily Price report.
    When you generate the Daily Price report, you see the price for the virtual machines till the previous day only. The price of the virtual machines for current day is blank.

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.

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.