Cannot create or edit users

Important: IBM Cloud Pak® for Data Version 4.6 will reach end of support (EOS) on 31 July, 2025. For more information, see the Discontinuance of service announcement for IBM Cloud Pak for Data Version 4.X.

Upgrade to IBM Software Hub Version 5.1 before IBM Cloud Pak for Data Version 4.6 reaches end of support. For more information, see Upgrading IBM Software Hub in the IBM Software Hub Version 5.1 documentation.

You get an error when you attempt to create a new users or edit or delete an existing user from the Manage users page.

Symptoms

When you try to create a user, you see the following message:
The user couldn't be created. Try to create the user again.
When you try to edit a user, you see the following message:
The changes to the user couldn’t be saved. Try to edit the user again.
When you try to delete a user, you see the following message:
The user couldn’t be deleted. Try to delete the user again.

Causes

This error can occur for one of the following reasons:
  • There is a network issue that causes the operation to take a long time.
  • You have an invalid session token.
  • One or more IBM Cloud Pak for Data services are not running.

Resolving the problem

User response: Take the following steps to try to resolve the problem:
  • Ignore the error and wait approximately 30 seconds. Reload the page to see if the operation completed successfully. (This indicates a network issue.)
  • If the operation did not complete successfully, sign out of the web client and then sign back in. Try to create, edit, or delete the user again. (If the operation completes successfully, this indicates that you had an invalid session token.)
  • If you still cannot create, edit, or delete the user, a cluster administrator must check whether the required services are running.

Administrator response:

To complete the following steps, you must have ssh access to the cluster and cluster administrator permission.

  1. SSH into the load balancer node of your cluster.
  2. Login with cluster administrator credentials:
    oc login -u ocadmin_username -p ocadmin_password
    Note: By default, all Cloud Pak for Data related pods will be in the zen project namespace within the Red Hat® OpenShift®container platform, unless configured differently during install.
  3. Check the status of the usermgmt pod(s):
    oc get pods | grep usermgmt

    If the usermgmt pod(s) are not running, delete them:

    oc delete pod usermgmt_pod
  4. Check the status of the couchdb pod:
    oc get pods | grep couchdb

    Look for the pod that has the couchdb prefix. There could be several other couchdb pods that are instantiated by other services that you can ignore.

    If the couchdb pod is not running, delete it:
    oc delete pod couchdb_pod
  5. Check the status of the redis pod:
    oc get pods | grep redis

    Look for the pod that has the redis-hash_value prefix. There could be other redis-ha pods that are instantiated by other services that you can ignore.

    If the redis pod is not running, delete it:
    oc delete pod redis_pod
  6. Check the status of the iis-services pod:
    oc get pods | grep iis-services
    If the iis-services pod is not running, delete it:
    oc delete pod iis-services_pod
  7. Wait several minutes while the pods are recreated before you try to add, edit, or delete users.
  8. If you deleted the iis-services pod, the Cloud Pak for Data administrator must sign out of the web client and then sign back in before attempting to create, edit, or delete users.