2025-10-18 14:39:49 - Patch directory ready: CSP-102092-Appliance-3.3.72025-10-18 14:39:49 - Running patch script: CSP-102092-applyPatch.sh2025-10-18 14:39:49 - Tail the log file /opt/vmware/var/log/update/vidm-CSP-102092-update.log for live logs..2025-10-18 14:39:49 - Running pre patch validations...2025-10-18 14:39:49 - Sufficient disk space in /db/vidm_upgrade/CSP-102092-Appliance-3.3.7-Patch/CSP-102092-Appliance-3.3.7: 50GB2025-10-18 14:39:49 - Pre-checks passed successfully.Traceback (most recent call last): File "/opt/vmware/bin/vamicli", line 34, in <module> import pywbem File "/opt/vmware/lib/python/site-packages/pywbem/__init__.py", line 40, in <module> from cim_types import *ModuleNotFoundError: No module named 'cim_types'
Attempting to run the following command on the vIDM appliance also fails
vamicli version --appliance
Traceback (most recent call last): File "/opt/vmware/bin/vamicli", line 34, in <module> import pywbem File "/opt/vmware/lib/python/site-packages/pywbem/{}init{}.py", line 40, in <module> from cim_types import *ModuleNotFoundError: No module named 'cim_types'
vIDM 3.3.7
This issue occurs due to python being changed on the system to python 3
To resolve this issue confirm that python has been altered on the system
1. Run the following command on the vIDM appliance
head -1 /opt/vmware/bin/vamicli
Incorrect Output
#!/usr/bin/env python
Correct Output
#!/usr/bin/env python2
2. If you receive an incorrect output from the command above then edit the first line in the /opt/vmware/bin/vamicli file to look like below
#!/usr/bin/env python2
3. Restart the vami-sfcb service
systemctl restart vami-sfcb
4. Attempt to patch vIDM once again following the instructions outlined here