Symptoms
Due to a known issue in vRA 8.1 which relates to replacement of the vIDM certificate with a new one, the issue occurs when the below command is executed on the appliance:
vracli vidm set {vidm_url} {vidm_admin_user} {vra_org_owner_user} {vidm_admin_pass_file} -r {vidm_root_cert_file}The error that can be seen when executing the command is: YYYY-MM-DD HH:MM:SS,507 [ERROR] Exception while setting vidm. Traceback (most recent call last): File "/opt/python-modules/vracli/commands/vidm.py", line 90, in set_handler self.__restart_identity_pods() File "/opt/python-modules/vracli/commands/vidm.py", line 154, in __restart_identity_pods kubernetes.client.V1DeleteOptions()) TypeError: delete_namespaced_pod() takes 3 positional arguments but 4 were given
Cause
The cause is a newer python library (i.e. kubernetes) version, used in vRA 8.1, which has changed its contract of the "delete_namespaced_pod()" method which is used in the "/opt/python-modules/vracli/commands/vidm.py" script.
Resolution
The issue is resolved in the later releases of vRealize Automation.
Workaround
Note: The below workaround is to be used for affected versions vRA.8.1 GA and vRA 8.1 P1 GA only.To workaround the issue:
Please replace the following file on every vRA node in the cluster:
/opt/python-modules/vracli/commands/vidm.py with the file attached in this KB.
The /opt/python-modules/vracli/commands/vidm.py file should have at least the following permissions: "-rw-r--r--".
Once the file has been replaced, retrigger the task from LCM and it should complete successfully.
