Performance charts fail after Daylight Savings changes are applied

November 5th, 2010 by jason Leave a reply »

Daylight savings changes this weekend allow many folks to get an extra hour of sleep.  However, a VMware vSphere 4.1 bug has surfaced which may spoil the fun. 

VMware has published KB 1030305 (Performance charts fail after Daylight Savings changes are applied) which serves as a reminder that the pitfalls and treachery of mixing daylight savings changes and million dollar datacenters are not behind us yet.  Those who are on vSphere 4.1 and observe the weekend time change will run into problems come Sunday morning:

After Daylight Savings settings are applied:

  • Performance charts do not display data
  • Past week, month, and year performance overview charts are not displayed
  • Datastore performance/space data charts are not displayed
  • You receive the error: The chart could not be loaded
  • This occurs when clocks are set back 1 hour from Daylight Savings Time to Standard Time

VMware offers the following workaround:

Use Advanced Chart Options:

  1. Click Performance
  2. Click Advanced
  3. Click Chart Options and then choose the chart you want to review

Use a custom time range when viewing performance charts after clocks are set back:

  1. Click Performance
  2. Click the Time Range dropdown
  3. Choose Custom
  4. Specify From and To options that exclude the hours for when the time change occurred

For example:

If Standard Time settings were applied on November 7, at 01:00 AM, you could use these ranges:
Before the time change:
From 1/11/2010 12:00 AM To 7/11/2010 12:00 AM
After the time change:
From 7/11/2010 03:00 AM To 8/11/2010 15:00 PM

Have a great weekend!

Advertisement

3 comments

  1. Justin Paul says:

    So after a week or so will this problem correct itself? or are the graphs forever broken?

    Thanks for the heads up!

  2. mlweaver says:

    SERIOUSLY?! there is no fix for this? this seems like a simple math error to me. I understand the word-around published above, but come on! There needs to be a SOLUTION, not a work-around.

  3. jason says:

    Are you impacted by the bug? I’ve created several reports and for the most part, I’m not seeing the issue myself although I’m seeing the error messages described in the vCenter logs.

Leave a Reply