Broadcom Product team has been notified and is working to address this issue in a timely manner. Please subscribe to this article to receive updates when they are available.
Workaround:
Before following the steps below, make sure to take a snapshot of the virtual appliance(s)
Note that if there are multiple directories in vIDM there will be a directory for each <WORKER_ID> in the <TENANT_NAME> directory. In this case it is necessary to check the config- state.json in every <WORKER_ID> directory and restore the latest stable version for any affected directory.
-
SSH to VMware Identity Manager Appliance(s) using root credentials. Change the directory to the location of the config-state.json file by running the command:
cd /usr/local/horizon/conf/states/<TENANT_NAME>/<WORKER_ID>
For example cd /usr/local/horizon/conf/states/VSPHERE.LOCAL/3001
-
Stop the service before doing anything.
service horizon-workspace stop
-
Back up the current configuration file by running the command:
mv config-state.json config-state.json.1
-
Copy application backup of the configuration file by running the command:
cp -p config-state.json.backup_<latest-stable-version> config-state.json
-
Change the owner of the config-state.json to horizon user by running the command:
chown horizon:www /usr/local/horizon/conf/states/<TENANT_NAME>/<WORKER_ID>/config-state.json
-
Change the permission of the config-state.json file by running the command:
chmod 640 /usr/local/horizon/conf/states/<TENANT_NAME>/<WORKER_ID>/config-state.json
-
Start vIDM/Workspace service by running the command:
service horizon-workspace start
- Go to Directory Setting and for each tab do the save operation by navigating to Identity & Access Management > YOUR DIRECTORY > Sync Settings

- Navigate each of the tabs and click on Save.
- If the "Groups" page refuses to save due to an error about the Bind DN: come back to the directory settings, enter the Bind DN password, validate & save.
Then come back to save the remaining tabs in Sync Settings.






- To avoid the issue for re-occurring please apply vIDM root partition is full on one node of the cluster