This section contains the cumulative release notes for Cloud Cruiser Express version 3.3.x. This includes the new and updated features, bug fixes since v3.2.1, and the system requirements. The current release is Cloud Cruiser Express 3.3.0. The full documentation for this release is available at Cloud Cruiser Express v3 for Windows Azure Pack.
This release contains all of the enhancements and bug fixes in Cloud Cruiser 3.3.0. The following table lists the fixes that affect Cloud Cruiser Express users. The remaining enhancements and fixes in this release are instantly unlocked when you purchase an upgrade to Cloud Cruiser.
Running the sample collection job with the argument
|Data was lost because usage occurred under a subscription or plan that an Azure Pack administrator had attempted to delete.||3507|
The usage amount and charges for the following resources were too high by a factor of 1,024:
This is because resource values were incorrectly converted from bytes to megabytes rather than to gigabytes.
|The Service Revenue chart on the Home page displayed values that were three times the correct values.||3525|
|When you chose Last 7 Days as the date range for a chart on the Home page, only six days of data were shown.||3513|
The Customer Revenue and Service Revenue charts on the Home page had a fixed scale, always dividing charted values by 1,000 and showing numbers along the Y axis in thousands. When these charts displayed small values the numbers along the Y axis all read
The following issues affected the Home page when using a locale other than US English (en_us):
In addition to these fixes, the Customer Revenue and Service Revenue charts have been retitled Customer Amount (<code>) and Service Amount (<code>), where
|3005, 3571, 3579|
|With a browser set to an Icelandic or Greek locale, labels in reports contained a locale-specific prefix.||3470|
|Some database operations performed slowly.||3584|
If you are upgrading from Cloud Cruiser Express 3.0.1 and were receiving some
Subscription not found warnings when running the
azure_pack_daily_load job, see Restoring dropped subscriptions for a procedure introduced with version 3.1.1 that corrects this problem.