Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Due to a known issue in the vSAN data processing, vSAN usage may be reported incorrectly. There are two issues affecting vSAN metering: In some situations, vCloud Usage Meter does not meter vSAN at all.for vSAN versions 6.6 and 6.6.1, if the vSAN Deduplication feature is turned on, you will see a difference between the Total Use Capacity in vCloud Usage Meter reports and the vSAN used - Total values in your vCenter Server cluster.
This issue occurs due to the following:Issue #1vCloud Usage Meter 3.6 detects vSAN features that are consumed and determines the billing rate for vSAN usage automatically. vCloud Usage Meter collects information for the enabled features from the associated vCenter Server and stores this information in the vCloud Usage Meter. In certain occasions Usage Meter fails to read the used vSAN features. As a result, vCloud Usage Meter does not meter vSAN usage and vCloud Usage Meter reports do not contain vSAN usage information. There is no workaround. The issue is fixed in vCloud Usage Meter 3.6.1.Issue #2If the vSAN Deduplication feature is turned on, you will see a difference between the Total Used Capacity in the vCloud Usage Meter reports and the vSAN Used – Total values in your vCenter Server Cluster.This issue only affects vSAN versions 6.6 and 6.6.1, if the vSAN deduplication feature is turned on. For vSAN versions 6.2 and 6.5, metering is accurate even if the deduplication feature is turned on.If the deduplication feature is turned off, metering of all supported vSAN versions is accurate. There is no workaround. The issue is fixed in vCloud Usage Meter 3.6.1.
Accurate reporting of vSAN consumption.
This issue is resolved in vCloud Usage Meter 3.6.1, available at VMware Downloads.Notes: vCloud Usage Meter 3.6.1 is GA and replaces versions 3.6 and 3.6.0.1.vCloud Usage Meter versions 3.6 and 3.6.0.1 are removed from the Download site.For partners using vSAN, VMware recommends to migrate to vCloud Usage Meter 3.6.1. Correct ReportingIf you are affected by any of the above issues, correct the vSAN reporting manually. For more information about manual reporting, see the VMware Cloud Provider Program Product Usage Guide in Partner Central. (login required).
Exposure Issue #1The probability of partners being affected by the issue is low. The issue is very hard to reproduce.Issue #2This issue only affects vCloud Usage Meter versions 3.6 and 3.6.0.1 that are metering vSAN versions 6.6 and 6.6.1, and only if vSAN Deduplication feature is in use. If the vSAN Deduplication feature is turned off, metering of all supported vSAN versions is accurate. Metering vSAN versions 6.2 and 6.5 with vCloud Usage Meter versions 3.6 and 3.6.0.1 is accurate even if the vSAN Deduplication feature is enabled. Release Notes Issue#1 “Known issue” entry in the vCloud Usage Meter 3.6 Release Notes."Resolved issue” entry in the vCloud Usage Meter 3.6.1 Release Notes. Issue#2 “Known issue” entry in the vCloud Usage Meter 3.6 Release Notes. “Resolved issue” entry in the vCloud Usage Meter 3.6.1 Release Notes.