Performance Charts on ESXi 6.7 fail to update correctly.

Products

• VMware vSphere ESXi

Issue/Introduction

• Performance Charts on ESXi 6.7 fail to update correctly.
• Restricted to 6.7 version only

Hostd log 
2018-11-15T21:53:41.990Z info hostd[2099388] [Originator@6876 sub=Libs opID=a29ef48a user=root] NetstackInstanceImpl: congestion control algorithm: newreno
2018-11-15T21:53:41.990Z info hostd[2099983] [Originator@6876 sub=Libs opID=a29ef489 user=root] NetstackInstanceImpl: congestion control algorithm: newreno
2018-11-15T21:53:41.991Z info hostd[2099390] [Originator@6876 sub=Libs opID=a29ef488 user=root] NetstackInstanceImpl: congestion control algorithm: newreno

Upon enabling trivia for hostd you may see similar entry as 

2019-01-22T12:13:19.999Z trivia hostd[2763740] [Originator@6876 sub=Statssvc] Collection Time 1548159199
2019-01-22T12:13:20.002Z trivia hostd[2763740] [Originator@6876 sub=Statssvc] CollectVmVdiskStats: For VM(MoID:'21',WID:2716566) and VMDK 'scsi0:0': Read OIO=0, ioSize=0. . .
2019-01-22T12:13:20.028Z trivia hostd[2763740] [Originator@6876 sub=Statssvc] Collection Flushing stat after 2730 samples
2019-01-22T12:13:20.078Z trivia hostd[2763740] [Originator@6876 sub=Statssvc] CollectVmVMFSDsStats: Failed to get VMFS stats for VM(MoID:'28',WID:4012267): N6VmkCtl3Lib16SysinfoExceptionE(Unable to complete Sysinfo operation. Please see the VMkernel log file for more details.: Sysinfo error: Not foundSee VMkernel log for details.)
2019-01-22T12:13:20.078Z verbose hostd[2763740] [Originator@6876 sub=Statssvc] VMKStatsCollector: HostCtl exception in stats collection. Turn on 'trivia' log for details
2019-01-22T12:13:20.093Z trivia hostd[2763740] [Originator@6876 sub=Statssvc] Time taken for stats collection : 93883 (microsec)
2019-01-22T12:13:20.093Z trivia hostd[2763740] [Originator@6876 sub=Statssvc] Process time : 56364 Usage : 60.036427
2019-01-22T12:13:20.093Z trivia hostd[2763740] [Originator@6876 sub=Statssvc] Cumulative Usage : 0.000028

From the above log-snip collection cycle is going normally, but the time-stamp is taken at 2019-01-22T12:14:19.999Z due to some internal reason this is going to be rounded down to the nearest 20seconds, which is 2019-01-22T12:13:00, this will overwrite the column to 13:00 and will make the StatsDepot the time is moved backward. Which is going to reset the entries stats file and starting the collection with the new entries.

Environment

VMware vSphere ESXi 6.7

Resolution

This issue is resolved in VMware ESXi 6.7 Update 3.