VMware

VMware vCenter Chargeback 1.6 Release Notes

vCenter Chargeback 1.6 | 02/10/2011 | Build 351155

Last Document Update: 02/10/2011

Check frequently for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New in this Release

vCenter Chargeback 1.6 provides the following new features:

  • Define pricing matrices for virtual machines based on vCPU count and memory bundles
    vCenter Chargeback 1.6 provides functionality to define a pricing matrix for virtual machines in your virtual datacenters (vDCs), such that a virtual machine is charged a fixed cost based on a vCPU count and memory bundle. This is applicable only to the virtual machines in the vDCs that have a Pay-As-You-Go resource management model in your VMware Cloud Director setup.

  • Internationalization Changes
    This release of vCenter Chargeback is I18N - Level 1 compliant. You can install and run the English version of vCenter Chargeback on any localized version of the supported operating systems. Also, the application accepts localized characters as input.

  • Changes to the vCenter Chargeback APIs
    In this release, the following two APIs have been made public:

    • Get Allocation Details of an Entity
    • Set Allocations for an Entity

    Also, the Exported Report resource schema is made public.
    However, the vCenter Chargeback API version is not changed for this release. The API version remains as 1.5.0.

vCenter Chargeback Documentation

For this release, only the following documents have been updated:

  • vCenter Chargeback User's Guide
  • vCenter Chargeback Online Help
  • vCenter Chargeback API Reference
The following documents released with vCenter Chargeback 1.5 are also applicable for 1.6. No changes have been effected in these documents.
  • vCenter Chargeback API Programming Guide
  • Using vCenter Chargeback with VMware Cloud Director

System Requirements

This section provides information about the supported operating systems, database management systems, and vCenter Server versions. The vCenter Chargeback User's Guide provides detailed information about the system requirements for installing and running the application.

Supported Operating Systems

  • Microsoft Windows Server 2003 with SP2 (32-bit and 64-bit)
  • Microsoft Windows Server 2003 R2 (32-bit and 64-bit)
  • Microsoft Windows Server 2008 (32-bit and 64-bit)
  • Microsoft Windows Server 2008 R2 (64-bit)

You can install and run vCenter Chargeback on any supported localized Windows operating system. However, all the labels and text messages in the installer and application user interface (including the plug-in in the vSphere Client) are displayed in English only. The application supports ASCII, extended ASCII, and non-ASCII characters. However, the characters are rendered correctly only if the client machine uses the appropriate fonts and the Web browser supports all the characters. The installer does not support all characters. Ensure that the information entered in the installer contains only the supported characters as specified in the install and upgrade instructions in this release notes and in the vCenter Chargeback User's Guide.

Supported Database Management Systems

  • Microsoft SQL Server 2005 (Standard and Enterprise)
  • Microsoft SQL Server 2008 (Standard and Enterprise)
  • Microsoft SQL Server 2005 Express
  • Oracle Database 10g (Standard and Enterprise)
  • Oracle Database 11g (Standard and Enterprise)

Supported vCenter Server Versions

  • VirtualCenter Server 2.5 Update 3
  • VirtualCenter Server 2.5 Update 4
  • VirtualCenter Server 2.5 Update 5
  • VirtualCenter Server 2.5 Update 6
  • vCenter Server 4.0
  • vCenter Server 4.0 Update 1
  • vCenter Server 4.0 Update 2
  • vCenter Server 4.1
  • vCenter Server 4.1 Update 1

Supported Web Browsers and Flash Player Plug-in

  • Microsoft Internet Explorer 7.x, and 8.x
  • Mozilla Firefox 3.5 and above
  • Adobe Flash Player for Windows Plug-in version 10.1
  • Adobe Flash Player for Linux version 10.1 (Plug-in for Mozilla Firefox running on Linux Platform)

Supported VMware Cloud Director Versions

  • VMware Cloud Director 1.0
  • VMware Cloud Director 1.0.1

Preinstallation Tasks

Before you install and use the VMware vCenter Chargeback application, you must perform the following tasks:

  • Create a vCenter Chargeback database and database user
    You must create a database for vCenter Chargeback to store the application-specific data. Ensure that this database is not configured to be case-sensitive. In addition, you must also create a database user having permissions to create and delete schema, as well as read from and write to the database.
  • Set a static IP address on the machine
    You must set a static IP address on the machine on which you plan to install vCenter Chargeback. You can obtain a static IP address from your network administrator. Preferably, obtain and set static IP addresses on all the servers and databases that the application will communicate with.
  • Ensure that MSI installation is enabled
    You must ensure that MSI installation is enabled on the machine. If it is not, you must manually install Microsoft Visual C++ 2005 Redistributable Package (x86) before running the vCenter Chargeback installer.
  • Check whether the required ports are free
    Ensure that the ports that you specify during the installation are free. While installing vCenter Chargeback, you must specify the port numbers for the HTTP port (default 8080), load-balancer port (default 8009), and HTTPS port (default 443).
  • Ensure that port exceptions are configured on Windows Firewall
    If Windows Firewall is enabled, you must set port exceptions for the HTTP, load-balancer, and HTTPS ports on the Windows Firewall. If these exceptions are not set, the application will not be usable.
  • Ensure that system time of all the servers and databases are in sync
    You must ensure that the system time of the machines on which you install vCenter Chargeback and vCenter Chargeback database are in sync. If you plan to install a separate data collector on a different machine, then the system time of this machine must be in sync with that of the other machines.
  • Ensure that the Windows user has the Log on as a service permission
    If you want to use the Windows Authentication option for the vCenter Chargeback database, you must ensure that the Windows user has the Log on as a service permission. If this permission is not set on the user, the installation fails. Also, the installer must be run in the context of this Windows user.
  • Ensure that the SQL Server Browser service is running if you are using a Microsoft SQL Server database and using the database instance name and a dynamic database instance port to connect to the vCenter Chargeback database.
  • Ensure that the vCenter Chargeback database is case-insensitive.

Quick Install

Download the vCenter-CB-1.6.0-351155.zip file, and extract the contents on to the machine on which you want to install vCenter Chargeback. Do not run the installer from a remote machine. To install vCenter Chargeback:

  1. Run the vCenter-CB.exe file.
    The installation wizard is displayed.
  2. Click Next on the Introduction screen.
  3. Accept the end-user license agreement, and click Next.
  4. Provide the path for the installation directory, and click Next.
    Ensure that the installation directory path has at least one directory (for example, C:\vCenterChargeback10\) and does not point to just a drive (for example, C:\). If the specified installation directory exists, ensure that it is empty. If the specified installation directory does not exist, the installer will create the directory. Also, the directory path must contain only ASCII characters.
  5. Configure the following vCenter Chargeback database-related information, and click Next:
    • Database Type: The type of database used to create the vCenter Chargeback database. This can be either SQL SERVER or ORACLE.
    • Database URL: The IP address of the system on which the vCenter Chargeback database is installed along with either the port at which the database listener service is running or the vCenter Chargeback database instance name. The database instance name must contain only ASCII characters.
      For Oracle Database, the database URL can be in any of the following formats:
      • <IP Address>
      • <Host Name>
      For SQL Server, the database URL can be in any of the following formats:
      • <IP Address>
      • <Host Name>
      • <IP Address>\<Database Instance Name>
      • <Host Name>\<Database Instance Name>
    • Database Port: (Optional) The port on which the database service is listening for requests. If the port number is not specified, the installer uses the default port. For an Oracle database, you must specify the TNS listener port if you are not using the default port 1521. For an SQL Server database, specify the database instance port if you are using a static port.
    • Database Name: Name of the database in which vCenter Chargeback stores the application-specific data. For Oracle Database, ensure that you provide the service name and not the SID.
    • SQL Authentication Mode: This option is applicable only for SQL Server database. For an SQL Server database, the authentication type can be either SQL Server Authentication or Windows Authentication.
    • Database Username: The name of the database user. The database user must have privileges to create and delete schema, as well as read from and write to the database. If you select Windows Authentication for SQL Authentication Mode, you must provide the Windows user account name. The user name must be of the form <Domain_Name>\<User_Name>. The user must have the Log on as a service permission.
    • Database Password: Password for the user name that you have provided. If you select Windows Authentication for SQL Authentication Mode, you must provide the password for the Windows user account. Ensure that the Windows user account password does not contain any special characters. The installer might fail if the password contains special characters.
    If the installer successfully connects to the database, the next screen is displayed.
  6. Provide the following information for the vCenter Chargeback application, and click Next:
    • IP Address: Static IP address of the machine on which you are installing vCenter Chargeback. Do not use localhost instead of the IP address.
    • HTTP Port: An unused HTTP port through which vCenter Chargeback communicates.
    • Load-Balancer Port: An unused port through which vCenter Chargeback can communicate with the load balancer (Apache Server).
    • Server Instance Name: A user-defined name for the vCenter Chargeback instance. This name is used by the load balancer to identify the instance. Ensure that the instance name contains only ASCII characters.
    If the specified ports are free, the next screen is displayed.
  7. Provide the following details for installing the load balancer, and click Next:
    • IP Address: Static IP address of the machine on which you are installing vCenter Chargeback. Do not use localhost instead of the IP address.
    • Admin Email Address: Email address of the server administrator. Ensure that the email address contains only ASCII characters.
    • HTTPS Port: An unused port through which the Apache Server communicates. The load balancer listens on this port for user requests.
    If the specified port is free, the next screen is displayed.
  8. Enter a user name and password for the administrative account that will be used to manage the vCenter Chargeback application, and click Next.
    The password must be less than or equal to 24 characters in length.
    Note: If you are using Oracle Database for your vCenter Chargeback database, ensure that the user name for the administrative account contains only ASCII and non-ASCII characters. Extended ASCII characters in the user name is not supported. This restriction is not applicable if you are using Microsoft SQL Server for you vCenter Chargeback database.
  9. Select the Install Data Collector option and click Next.
    You must have at least one instance of the data collector that is running and registered with the application for the database synchronization jobs to run.
  10. Review the information displayed on the Pre-Installation Summary screen, and click Install.
    The installer starts installing the various components and creating the database schema. If the installation is successful, the URL for accessing the vCenter Chargeback application is displayed.
  11. Note this URL, and click Done.
    The installer displays a dialog stating whether you want to generate your own SSL certificate.
  12. Click Skip now, I'll generate it later.

For detailed install instruction, refer to the vCenter Chargeback User's Guide.

Upgrade to vCenter Chargeback 1.6

This release of vCenter Chargeback does not provide any direct upgrade options. If you have an existing vCenter Chargeback 1.5.x setup, then you must first uninstall vCenter Chargeback but retain the database and then install vCenter Chargeback 1.6 and point it to the existing database during installation.

Upgrading from vCenter Chargeback 1.0 and 1.0.1

You cannot directly upgrade a vCenter Chargeback 1.0 or vCenter Chargeback 1.0.1 setup to vCenter Chargeback 1.6. You must first upgrade this setup to vCenter Chargeback 1.5. For detailed instructions about upgrading your setup to vCenter Chargeback 1.5, see the vCenter Chargeback User's Guide. Ensure that you perform the pre-upgrade tasks specified in the vCenter Chargeback User's Guide. Also, perform the tasks specified in KB 1026068 and KB 1026796 before you upgrade an existing vCenter Chargeback installation.

After you have upgraded to vCenter Chargeback 1.5, follow the instructions provided in the next section of the release notes to upgrade to vCenter Chargeback 1.6.

CAUTION: Do not try to upgrade your vCenter Chargeback 1.0 and vCenter Chargeback 1.0.1 setup to vCenter Chargeback 1.6 directly. The upgrade process might fail and could lead to data loss.

Upgrading from vCenter Chargeback 1.5.x to vCenter Chargeback 1.6

You cannot directly upgrade an existing vCenter Chargeback 1.5.x setup to vCenter Chargeback 1.6. To upgrade your existing setup to vCenter Chargeback 1.6, perform the followings tasks:

Task 1: Pre-Upgrade Steps

  1. Check whether the data collector has synchronized all the vCenter Server hierarchies.
    You can check the status and last-run time for the data collector synchronization jobs from the Data Collectors page of the Settings tab of the application. You can also browse the vCenter Server hierarchies and vCenter Chargeback hierarchies in the application to verify whether the hierarchies are synchronized.

  2. Stop all the vCenter Chargeback related services.

  3. Take a backup of the existing vCenter Chargeback database and configuration files as specified in KB 1026796.
    If the upgrade fails due to some unforeseen reason and you are not able to use the existing setup either, you can use the database backup to recover the data.

  4. Run the script to purge the duplicate samples from the performance stats table as specified in KB 1032952.

Task 2: Uninstall Existing vCenter Chargeback 1.5.x Setup but Retain Corresponding Database

Refer to the vCenter Chargeback User's Guide for the uninstall instructions. Ensure that you do not select the vCenter Chargeback database for uninstallation. You must retain the existing database. If you unistall the database, then all stored data will be lost.

Task 3: Install vCenter Chargeback 1.6 with Existing vCenter Chargeback Database

  1. Run the vCenter-CB.exe file.
    The installation wizard is displayed.
  2. Click Next on the Introduction screen.
  3. Accept the end-user license agreement, and click Next.
  4. Provide the path for the installation directory, and click Next.
    Ensure that the installation directory path has at least one directory (for example, C:\vCenterChargeback10\) and does not point to just a drive (for example, C:\). If the specified installation directory exists, ensure that it is empty. If the specified installation directory does not exist, the installer will create the directory. Also, the directory path must contain only ASCII characters.
  5. Configure the following vCenter Chargeback database-related information, and click Next:
    • Database Type: The type of database used to create the existing vCenter Chargeback database. This can be either SQL SERVER or ORACLE.
    • Database URL: The IP address or host name of the system on which the existing vCenter Chargeback database is installed. For an SQL Server database, you can also provide the vCenter Chargeback database instance name. The database instance name must contain only ASCII characters.
      For Oracle Database, the database URL can be in any of the following formats:
      • <IP Address>
      • <Host Name>
      For SQL Server, the database URL can be in any of the following formats:
      • <IP Address>
      • <Host Name>
      • <IP Address>\<Database Instance Name>
      • <Host Name>\<Database Instance Name>
    • Database Port: (Optional) The port on which the database service is listening for requests. If the port number is not specified, the installer uses the default port. For an Oracle database, you must specify the TNS listener port if you are not using the default port 1521. For an SQL Server database, specify the database instance port if you are using a static port.
    • Database Name: The name of the existing vCenter Chargeback database. For Oracle Database, ensure that you provide the service name and not the SID.
    • SQL Authentication Mode: This option is applicable only for SQL Server databases. For an SQL Server database, the authentication type can be either SQL Server Authentication or Windows Authentication.
    • Database Username: The name of the database user. The database user must have privileges to create and delete schema, as well as read from and write to the database. If you select Windows Authentication for SQL Authentication Mode, you must provide the Windows user account name. The user name must be of the form <Domain_Name>\<User_Name>. The user must have the Log on as a service permission.
    • Database Password: Password for the user name that you have provided. If you select Windows Authentication for SQL Authentication Mode, you must provide the password for the Windows user account. Ensure that the Windows user account password does not contain any special characters. The installer might fail if the password contains special characters.
    If the installer successfully connects to the database and detects a vCenter Chargeback schema, a dialog box is displayed.
  6. Click Use it.
    The vCenter Chargeback instance will use this existing vCenter Chargeback database.
    If you click Create new schema, the existing schema is overwritten and you lose the existing data.
  7. Enter the IP address and port details for the vCenter Chargeback application, and click Next.
    • IP Address: The static IP address of the machine on which you are installing vCenter Chargeback. Do not use localhost instead of the IP address.
    • HTTP Port: An unused HTTP port through which vCenter Chargeback communicates.
    • Load-Balancer Port: An unused port through which vCenter Chargeback can communicate with the load balancer (Apache Server).
    • Server Instance Name: A user-defined name for the vCenter Chargeback instance. This name is used by the load balancer to identify the instance. Ensure that the instance name contains only ASCII characters.
    If the specified ports are free, the next screen is displayed.
  8. Enter the load-balancer-related information, and click Next:
    • IP Address: The static IP address of the machine on which you are installing vCenter Chargeback. Do not use localhost instead of the IP address.
    • Admin Email Address: The email address of the server administrator. Ensure that the email address contains only ASCII characters.
    • HTTPS Port: An unused port through which the Apache Server communicates. The load balancer listens on this port for user requests.
    If the specified port is free, the next screen is displayed.
  9. Select only the Install Data Collector option and click Next.
    You must have at least one instance of the data collector that is running and registered with the application for the database synchronization jobs to run.
    You can optionally choose to install the VMware Cloud Director Data Collector and vShield Manager Data Collector. All the data collectors can be installed even after a vCenter Chargeback instance is installed. If you are installing the vShield Manager Data Collector, choose to install the VMware Cloud Director Data Collector too or ensure that at least one instance of VMware Cloud Director Data Collector is running.
  10. Review the information displayed on the Pre-Installation Summary screen, and click Install.
    The installer starts installing the various components and creating the database schema. If the installation is successful, the URL for accessing the vCenter Chargeback application is displayed.
  11. Note this URL, and click Done.
    The installer displays a dialog box confirming whether you want to generate your own SSL certificate.
  12. Click Skip now, I'll generate it later.

Note: If the earlier instance vCenter Chargeback had a VMware Cloud Director Data Collector installed, ensure that you provide the same VMware Cloud Director database details for the vCenter Chargeback instance post upgrade.

Resolved Issues

This section lists the issues that have been fixed in this release.

Internationalization Issues

  • Non-ASCII characters are not displayed correctly in the exported report and the report sent by email
    If a report includes non-ASCII characters, they are not displayed correctly if the report is exported to the PDF or CSV format. vCenter Chargeback, however, displays these characters correctly. This issue also occurs when the report is sent through an email. If the report name has non-ASCII characters, the generated report name and emailed report name might differ. Starting with vCenter Chargeback 1.6, this issue is fixed. You must, however, ensure that you are using the correct fonts and these fonts files are configured in your vCenter Chargeback setup. For more information, refer to the vCenter Chargeback User's Guide.

Other Issues

  • User sessions overlap when multiple users are logged in from the same machine
    Prior to this release, if multiple vCenter Chargeback users are accessing a vCenter Chargeback instance from the same machine using different instances of the same Web browser, then the user sessions could get overlapped. Starting with this release, if a user session is active on a machine and you try to start another user session from a different instance of the same Web browser on the machine, vCenter Chargeback redirects you to the active user session without prompting for the login credentials. Therefore, you can have only one active user session from a Web browser on a machine.

Known Issues

The known issues in this release are listed in this section. Workarounds, if any, are provided in the issue description.

Hierarchy Management Issues

  • Connection times out when browsing hierarchy
    If you are browsing a large vCenter Server or vCenter Chargeback hierarchy in the vCenter Chargeback plug-in, the connection to vCenter Chargeback might time out.

  • vCenter Chargeback does not show the status of the virtual machines
    This release of vCenter Chargeback does not show the status of the virtual machines in the chargeback hierarchy and vCenter Server hierarchy. All the virtual machines in the hierarchies have the same icon and do not indicate whether they are powered on, suspended, or powered off. Also, the vCenter Server hierarchy displays all the virtual machines, including the ones that are suspended or powered off. This, however, does not affect the usage and cost calculation. The usage statistics that are used by vCenter Chargeback to calculate the costs are tracked by vCenter Server and stored in the vCenter Server database.

  • Changes to a chargeback hierarchy are not reflected in the concurrent user sessions
    Hierarchy creation, deletion, and renaming operations performed by a user are not automatically reflected in concurrent user sessions. The concurrent users must log out and then log in again to see these changes. Any other change to the chargeback hierarchy, such as adding or deleting an entity, might not reflect immediately in the concurrent user sessions. After a change is made to the chargeback hierarchy, the hierarchy must be manually refreshed in the concurrent user sessions. Users can refresh the chargeback hierarchy by clicking the refresh button next to the chargeback hierarchy or by loading another chargeback hierarchy and then reloading the chargeback hierarchy. The refresh button appears only if vCenter Chargeback detects changes to the chargeback hierarchy.

  • Re-added virtual machine does not have the cost information configured on it
    If you delete an ESX host from a vCenter Server, all the virtual machines belonging to the ESX host are deleted from the chargeback hierarchy. After re-adding the ESX host to the vCenter Server, you can add the virtual machines on this ESX host back to the respective chargeback hierarchies in vCenter Chargeback. However, any entity-specific cost configuration set on the virtual machines prior to deleting the ESX host from the vCenter Server is lost. You must, therefore, migrate all the virtual machines on an ESX host before removing the ESX host from the vCenter Server.

  • Changes to the chargeback hierarchy are not reflected immediately
    If the changes made to a chargeback hierarchy are not displayed immediately in the Web browser, you must refresh the chargeback hierarchy to view the changes. You can refresh the chargeback hierarchy by selecting another hierarchy and then selecting the required chargeback hierarchy.

Report Management Issues

  • Error displayed when fetching archived reports
    When you try to fetch a report that was generated and archived by a user whose user ID is deleted from vCenter Chargeback, the application fails to retrieve the report and displays an error stating that the object cannot be retrieved. This issue also occurs for scheduled reports that are archived where the reporting schedule was created by a user that no longer exists in the application.
    A workaround for this issue is to run the following query against the vCenter Chargeback database:
    update cb_task_queue set created_by = 1 where created_by not in (select user_id from cb_user);
    commit;

  • Scheduled reports are not generated if the user is deleted
    If a user is deleted from vCenter Chargeback, then the report schedules created by this user fail to generate reports as per the defined schedule. vCenter Chargeback displays an error and logs an exception corresponding to the report generation failure.

  • Unable to access an archived report generated by a report schedule
    If a user is given some privileges on a report schedule, he can access the report schedule but not the reports generated and archived by the schedule. vCenter Chargeback does not implicitly assign the user any privileges for the reports generated by the schedule. This issue exists only for users who are not creator of the report schedule but have been assigned some privileges on the report schedule.

  • Report generation schedule fails with an invalid XML error
    When generating a reporting schedule, if the recurrence range is shorter in duration than the recurrence pattern, then vCenter Chargeback fails to create the schedule and throws an error similar to the following:
    Incoming XML is invalid.
    That is, if you create a weekly schedule and the recurrence range has the start date as the current date and end date as five days from the current date, then the schedule creation fails. In this case, the recurrence range is five days, which is less than the recurrence pattern, which is seven days.

  • Report generation fails with entity not found error
    If you backdate a hierarchy after adding a newly created vCenter Server entity to a hierarchy, which contains vCenter Server entities that were synchronized during the first run of the data collector synchronization jobs, then the newly created vCenter Server entity is also backdated by three months. Therefore, when you generate a report on this entity, vCenter Chargeback throws an entity not found error. Also, if you generate a report on any of the parent entities of this entity, the report excludes this entity from the report. vCenter Chargeback does not display or log any message stating the entity was excluded from the report. To ensure that the entity is included in the reports, you must delete the entity from the hierarchy and add it again if you have already backdated the hierarchy.

  • Information messages stating lack of data for a specific time period is not displayed in the report
    If data is unavailable for a part of the reporting period, then vCenter Chargeback considers zero usage for this time period. However, no information message stating the same is included in the report.

  • Report includes the usage and cost information for secondary virtual machines
    If you enable fault tolerance on a virtual machine after the data collector has synchronized the vCenter Chargeback inventory for the first time after installation, the report might include usage and cost information for the secondary virtual machines corresponding to the fault tolerance-enabled virtual machine. However, this cost and usage data included is for a very negligible time frame.

  • Report created time is modified to upgrade time
    After upgrading to vCenter Chargeback 1.5, the create time for the archived reports in vCenter Chargeback is changed to the upgrade time. Although the report content is not changed, a search based on the report create time might provide incorrect results.

  • Reports for a vCenter Server user might not contain the correct entities
    A report scheduled for a vCenter Server user might contain the usage and cost details for entities on which the user does not have permissions. The report might also exclude some entities on which the user has permissions. There is currently no workaround for this issue. However, reports might be generated correctly for the vCenter Server user whose credentials are used to add the vCenter Server to vCenter Chargeback.

  • Report generation schedule is automatically changed
    If vCenter Chargeback stops running and is restarted, all the reports generation schedules that were set to run during the period that the application was not running are immediately started. Also, these report generation schedules are automatically updated to run at this new time. For example, suppose you have created a report generation schedule that generates a daily report at 6:00 PM. If the application stops running at 4:30 PM, and you restart vCenter Chargeback at 9:00 AM the next day, the report that had to be generated at 6:00 PM the previous day is generated at 9:00 AM instead. Also, the corresponding schedule is updated automatically to run at 9:00 AM everyday.

  • Report generation fails with an error on a vCenter Server entity in a chargeback hierarchy that is not back-dated
    In a chargeback hierarchy that is not back-dated, when you try to generate a report on a vCenter Server entity for a time period before the entity was added to the hierarchy, vCenter Chargeback reports the following error:
    Error in response format

  • Report search based on page count returns incorrect results
    When you search for reports based on page count by using the Advanced Search option, vCenter Chargeback might not return all the reports that have page count in the specified range. The search results might be incorrect.

  • The last run time for rescheduled report defaults to N/A
    After you reschedule a report, vCenter Chargeback shows the last run time for this scheduled report as N/A instead of the date and time when the report was last generated as per the original schedule.

  • Additional plug-ins required message displayed when trying to preview Report View
    On Mozilla Firefox 3.6.x, an additional plug-ins required message appears when you click Preview on the Report View page of the Settings tab. You can safely close the message. The report preview is displayed on the right pane of the page.

  • Dashboard report does not check the user's privilege for cost elements
    vCenter Chargeback filters the chargeback hierarchical entities included in the dashboard report based on the user's vCenter Chargeback resource authorization details. However, the application does not check for the authorization details on the cost elements for the logged-in user.

  • Information from the Report View is not included in the exported or emailed report
    The information configured in the Report View might not appear in the exported or emailed report after you upgrade to vCenter Chargeback 1.5. Also, the configured data might not be shown when you click Preview on the Report View page of the Settings tab. A workaround for this issue is that, if you have included images in any of the sections of the Report View, then you upload all the images again and save the report view after the upgrade. If you have only text in the Report View sections, just click Save on the Report View page of the Settings tab.

  • Report does not include cost and usage data for all the child entities
    If you delete a virtual machine from a chargeback hierarchy and then upgrade to vCenter Chargeback 1.5, then vCenter Chargeback does not include the entity details in the report, even if the report is generated for time period when the virtual machine existed in the hierarchy.

  • Inconsistent usage and cost data reported
    If you generate a report that considers the actual resource usage for a billing period including the past 24 to 36 hours from the report generation time, the usage data and cost included in the report might be inconsistent. This inconsistency might occur if vCenter Server has not completed the statistics roll-up or the data collector has not synchronized the rolled-up statistics in the vCenter Chargeback database.

  • Report does not include usage and cost information related to raw devices
    If a virtual machine contains a hard disk that uses raw device mapping, then the report does not include the usage and cost information for the raw device. vCenter Chargeback currently does not account for raw device mapping.

User Management Issues

  • Post-upgrade user is incorrectly assigned Super User role
    When you upgrade your existing vCenter Chargeback instance to vCenter Chargeback 1.5, any user having discrete privileges, that is, privileges which are not part of a role, is assigned the Super User role after upgrade. The only workaround is to delete such users after the upgrade, recreate them in vCenter Chargeback, and assign the appropriate roles and privileges on the required entities.

  • Unable to modify or delete a hierarchy
    Although a user has the necessary privileges to update or delete a hierarchy, he is unable to update or delete it. To enable a user to update or delete a hierarchy, the user must be assigned a role with the update and delete privileges for the hierarchy resource type on the hierarchy and the update and delete privileges for the chargeback hierarchical entity resource type on the root node of the hierarchy, which is same as the hierarchy name.

Internationalization Issues

  • Errors displayed while accessing vCenter Chargeback from a localized version of Windows Server 2003
    In this release of vCenter Chargeback, some errors might occur when you access the application from a Web browser on a localized version of Windows Server 2003 operating system. You should access vCenter Chargeback from a Web browser on any operating system other than Windows Server 2003. There are currently no workarounds for this issue.

  • Date format in the exported or emailed report is different from that in the application
    If you are running vCenter Chargeback on a localized operating system, the date format in the application might differ from that in the exported or emailed reports. The change in the date format is due to the change in the locale. Currently, there are no workarounds for this issue.

Virtual Appliance Issues

  • vCenter Chargeback virtual appliance is unavailable
    This release of vCenter Chargeback does not contain the vCenter Chargeback virtual appliance.

API-Related Issues

  • Apply Cost Template API fails if the rate factors are not set on the cost template
    If the Apply Cost Template API is called for a cost template that does not have any rate factor set, an exception with response XML similar to the following is raised:
    <Error majorErrorCode="400" minorErrorCode="3004" message="At least one computing resource must be selected." />
    The only workaround is to set the rate factors. This issue, however, does not occur if a cost template without any rate factors is applied from the application user interface.

Other Issues

  • Some of the database management scripts do not work
    In this release, the following database management scripts do not work:
    • spaceHierarchyData_oracle: The workaround for this is to remove the schema reference sys. from the table names in the script.
    • purgeReportData_mssql and purgeReportData_oracle: No workaround for these two scripts.
    • purgeTables_mssql and purgeTables_oracle: The workaround is to comment the delete command for the cb_report table in these scripts.
  • Correct reservation values are not reflected for expandable vApps and resource pools
    For expandable vApps and resource pools, the memory and CPU reservation values reflected in vCenter Chargeback might differ from the actual reservation values as shown in vSphere Client. vCenter Chargeback shows the last explicitly set reservation value for expandable vApps and resource pools. To ensure that the correct values are reflected in vCenter Chargeback, you must edit the settings for the vApp or resource pool in vSphere Client and save the current reservation values.

  • vCenter Chargeback displays the disconnected hosts and orphaned virtual machines
    vCenter Chargeback does not distinguish between connected and disconnected ESX hosts. Therefore, vCenter Chargeback displays the disconnected hosts and orphaned virtual machines and accounts for the same in generated reports. Also, vCenter Chargeback does not display the state of these ESX hosts and virtual machines. If a ESX host is disconnected from a vCenter Server and added to another vCenter Server, and both the vCenter Server instances are added to vCenter Chargeback, then vCenter Chargeback will display a duplicate entry for the ESX host. That is, vCenter Chargeback will display an ESX host entry corresponding to the disconnected host and another corresponding to the host connected to the second vCenter Server. As a result, vCenter Chargeback accounts for the disconnected host CPUs and orphaned virtual machines in vCenter Chargeback licensing.

  • vCenter Chargeback throws a resource already exists message
    If you create a resource with a name that contains the % or _ characters, then vCenter Chargeback might throw an error if it detects another resource with a similar naming pattern. For example, you create a cost model with the name FirstModel. Now, when you try to create a another cost model with the name F%Model, vCenter Chargeback might throw an error stating cost model with the given name already exists. Similarly, let us say you create a hierarchy with the name My1Hierarchy. Now, if you try to create another hierarchy with the name My_Hierarchy, vCenter Chargeback might throw an error.

  • vCenter Chargeback throws an error when deleting vCenter Server
    When you delete a vCenter Server whose entities are added to a hierarchy, vCenter Chargeback shows a dialog box asking whether you want to retain the entities or delete them from vCenter Chargeback. If you choose to delete the entities, then an error message similar to the following is displayed:
    vCenter Server 'vcId' or it's 'Hosts & Clusters and VMs & Templates Synchronization' job is not found.
    However, the delete operation is successful. This error message is displayed only if the vCenter Server hierarchy is displayed in the Manage Hierarchy tab when the vCenter Server is deleted. You must close all the relevant error dialog boxes displayed to continue normal functioning of vCenter Chargeback.

  • vCenter Chargeback throws an error when you add a license
    When you add a license to vCenter Chargeback, an error is thrown. However, vCenter Chargeback functions correctly without any issue. In Firefox, the error is logged in the error console. In Internet Explorer, the error is shown in the status bar if the Disable script debugging check box is selected under Tools > Internet Options > Advanced. If the check box is not selected, an error dialog is displayed.

  • Unable to download and install the vCenter Chargeback plug-in from the Plug-ins Manager window of the vSphere Client
    This is a vSphere Client issue. Restart the vSphere Client and accept the vCenter Chargeback SSL certificate. This might rectify the issue if the vSphere Client is able to communicate with vCenter Chargeback. If the vSphere Client and vCenter Chargeback are on different network domains, this issue might persist.

  • VI Client does not render the hierarchy completely or displays error while rendering
    If you are using VI Client 2.5 with Internet Explorer 6 on a Windows Server 2003 machine, the VI Client might display some errors, such as Insufficient Memory, when rendering a very large hierarchy (with more than 1000 entities). Also, the hierarchy rendering is very slow. A probable workaround is to access vCenter Chargeback directly from a Web browser instead of using the vCenter Chargeback plug-in on the VI Client.

  • vCenter Chargeback instance is not recognized as a part of the cluster
    If you have a two-instance cluster and the first vCenter Chargeback instance fails due to some reason, all the requests currently being served by the first instance are moved to the second instance. After the first instance is restarted, if the second instance fails, the requests handled by the second instance are not moved to the first instance. That is, the failover does not happen because the second instance does not recognize the first instance as a part of the cluster. A workaround for this issue is to restart all the vCenter Chargeback instances in the cluster. This issue also occurs for clusters with more than two instances. If any of the vCenter Chargeback instances fails and is restarted, that instance starts serving user requests but is not recognized by the cluster until other instances are restarted.

  • Imported vCenter Server attributes are not deleted when the vCenter Server entity is deleted
    While adding a vCenter Server entity to a chargeback hierarchy, you can import the attributes defined on the entity. However, these attributes are not deleted from the vCenter Chargeback application when the corresponding vCenter Server entity is deleted. You can manually delete these attributes from the application if the attributes are no longer required and are not assigned to any other entities across the chargeback hierarchies defined in the application.

  • Logged-in users do not see newly added computing resources
    If you are logged in to vCenter Chargeback and any new computing resource is added to it through an API call, you can see the newly added computing resource only if you log in again to vCenter Chargeback.

  • vCenter Chargeback ignore the base DN value provided when configuring the LDAP server
    In this release, vCenter Chargeback ignores the value entered for base DN when configuring the LDAP server. vCenter Chargeback automatically fetches the root base DN and uses this value to configure the LDAP server.

  • After upgrade, the samples folder contains old files
    When you upgrade from vCenter Chargeback 1.0.1 to vCenter Chargeback 1.5, the installer does not remove or update the samples folder under the installation directory. vCenter Chargeback 1.5 installation does not include any sample files.

  • The version of the vCenter Chargeback plug-in in vSphere Client is not updated after upgrading to vCenter Chargeback 1.5
    After upgrading to vCenter Chargeback 1.5 from vCenter Chargeback 1.0.1, vSphere Client reports the plug-in version as 1.0.1 when you check the version from Plug-ins > Manage Plug-ins. Although the plug-in is upgraded, the plug-in version is reported incorrectly. However, the plug-in version is reported correctly when checked from Tools > About in the plug-in.

VMware Cloud Director Data Collector and vShield Manager Data Collector Issues

Some of the following listed issues are common for both the VMware Cloud Director Data Collector and the vShield Manager Data Collector.

  • If the VMware Cloud Director database has a large history of chargeback events, the processing of the events might take a long time to complete.

  • If VMware Cloud Director, vShield Manager instances, vCenter Chargeback instances, and the corresponding databases and data collectors are not in the same timezone, then the data collectors might fail to process the events.

  • You cannot change the logging level for the data collectors at runtime. Also, the logging levels cannot be changed from the vCenter Chargeback GUI.

  • vCenter Chargeback accounts for the virtual machines only from the time they are added to the hierarchy in vCenter Chargeback and till they are deleted from vCenter Chargeback by the data collector.

  • A virtual machine added to the VMware Cloud Director setup is reflected in the corresponding vCenter Chargeback hierarchy only if the lifetime of the virtual machine is greater than the frequency of the event processor job of VMware Cloud Director Data Collector.

  • vShield Manager reports incorrect external broadband statistics values if the vShield Manager instances are not in the same timezone as VMware Cloud Director, vCenter Chargeback, and the corresponding databases and data collectors.

  • If chargeback events are not processed because of a failed VMware Cloud Director instance, then the entities in the hierarchy might not be charged correctly and consistently.

  • vCenter Chargeback charges for the network services and network count even if the deployment of a network fails during service configuration in vShield Manager.

  • Virtual machines might be incorrectly charged if vApp creation with resolved virtual machines partially fails.

  • Changes to the vApp name in VMware Cloud Director might not be reflected in vCenter Chargeback.