ViPR Controller: VPLEX metering task fails with a NumberFormatException


   Article Number:     536816                                   Article Version: 2     Article Type:    Break Fix 




ViPR Controller,ViPR Controller Controller 3.6 SP2,ViPR Controller Controller 3.6 SP1,ViPR Controller Controller 3.6,ViPR Controller Controller 3.5





ViPR Controller automatically runs a VPLEX metering task once an hour by default.   
    The ViPR Controller controllersvc-discovery logs report the following error:   

      vipr3 controllersvc-discovery 2019-08-02 12:02:42,365 [138|vplex|Metering|<IP>|c955f9f6-2380-4eb4-9edc-ee96dd367dfe]  INFO (line 96) Metering task Started using Provider <IP> using Namespace Metering-vplex       
        vipr3 controllersvc-discovery 2019-08-02 12:02:46,764 [138|vplex|Metering|<IP>|c955f9f6-2380-4eb4-9edc-ee96dd367dfe]  INFO (line 487) director-1-1-A [cpu] (VPLEX+<Serial Number>): <Director stats>       
        vipr3 controllersvc-discovery 2019-08-02 12:02:46,766 [138|vplex|Metering|<IP>|c955f9f6-2380-4eb4-9edc-ee96dd367dfe] ERROR (line 104) Metering job failed for urn:storageos:StorageSystem:b600410c-b3bf-4040-aadc-9e1968faa040:vdc1--->        
        java.lang.NumberFormatException: For input string: "no data"






In the above example, ViPR Controller parses the VPLEX PERPETUAL log,    
    ViPR Controller expects this file to contain numerical values only but encounters a string "no data" instead.       
        This results in a Java NumberFormatException and the metering task fails.







      This should not be a persistent issue as the VPLEX performance log file should be updated by the VPLEX system.     
      As a result the VPLEX metering task should not fail each time.     
      ViPR Engineering is currently addressing this problem, but has not provided a fix in a released patch.     
      This solution will be updated with the patch when it has been released.