OC upgrade Verify Robot step shows Disk Free (MB) 0 | Error retrieving disk free from CDM probe | java.lang.NullPointerException

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

While upgrading operator console to 23.4.4 (CU4) we are getting below error. We have enough space in disk in all the OC server.

 

The selected robot does not meet the minimum requirements for Operator Console. Review the system requirements in the release notes. If you believe the selected robot's configuration is sufficient to run Operator Console, you can proceed with the installation.

 

 

Installation log located at: 

tmp/ia/oc.log

shows: 

Querying /<domain>/<hub>/<oc_robot>/cdm for disk_status...
NIM_ROOT on UMP robot discovered as: C:\Program Files (x86)\Nimsoft

 data (PDS)

  0 (PDS)
    DiskUsedPct=0
    CheckTime=1751986571
    DiskAvail=204625
    Label=New Volume
    TypeDesc=Local
    DiskFree=204625
    DiskActive=1
    InodeAvail=0
Error retrieving disk free from CDM probe at /<domain>/<hub>/<oc_robot>/: java.lang.NullPointerException
  - Localization lookup: [Key=VerifyRobot.DiskFreeMB.JTextField.DecimalFormat]    [Value=#,##0]
  - Localization lookup: [Key=VerifyRobot.TotalMemoryMB.JTextField.DecimalFormat]    [Value=#,##0]
java.lang.InterruptedException: sleep interrupted
  - Localization lookup: [Key=VerifyRobot.Error.InsufficientSpecs]    [Value=The selected robot does not meet the minimum requirements for $PRODUCT_NAME$. Review the system requirements in the release notes. If you believe the selected robot's configuration is sufficient to run $PRODUCT_NAME$, you can proceed with the installation.]
InstallCDM ended
ProcessingDialog ended

 

Environment

DX UIM 23.4.* 

Cause

The verify robot step is intended to ensure the minimum requirements for the installations are met before we proceed. The install wizard will collect system specifications from the robot you selected in the previous panel. The CDM probe is used to gather this information and will be deployed to the robot if necessary.

If there is any issue with the CDM probe, this issue may happen. 

Resolution

To resolve this issue: 

 

• Since the robot verify is an informational step and does not actually prevent the installation to proceed, if you know you are meeting the requirements you can ignore the step and proceed assuming the CDM is not providing the correct information. 
• Check the CDM probe state. Redeploy the CDM probe and or upgrade to the latest version and retry to run the same step. Some patch version of CDM 8.*+Patch have shown this issue.