Solution

1. Take a backup of mstr-md pod and save it to a secure location on Cluster Control Manager (CCM).
2. Log in to the Cluster Control Manager (CCM) console as the customer user.
3. To switch to the root user, type su and press Enter.
4. To get a list of all the Historical Reporting pods, run the following command:
   ADDITIONAL INFORMATION: kubectl get pods -n mstr

   Confirm the mstr-srv pod is in a running 1/1 state.
5. If the mstr-srv pod is in a running 0/1 state, use the following command to edit the mstr-srv configmap:
   ADDITIONAL INFORMATION: kubectl edit cm -n mstr srv-configmap
6. Update the property UPD_GROUPS to False using the following command:
   ADDITIONAL INFORMATION: UPD_GROUPS: "false"

   Use i to make the configmap editable.
7. To escape the edit mode, press the Esc button.
8. Type :wq! and press Enter to save the changes.
9. Restart the mstr-srv pod using the following command:
   ADDITIONAL INFORMATION: kubectl delete pods -n mstr mstr-srv-<pod-id>
10. Confirm that the mstr-srv pod gets to a running state which can take more than 10 minutes.
11. Log in to the Historical Reporting server administrator page https://cluster.fqdn/AvayaAnalytics/servlet/AnalyticsServerAdmin using the administrator user account credentials.
12. To display the list of user groups, click Server iconUser Manager.
    ADDITIONAL INFORMATION:

    Note:

    User groups are shown as a two-person icon. Users are shown as a single-person icon.
13. Confirm that the default Advanced, Basic, and Consumer groups are present.
14. Confirm if any additional groups have the customer’s LDAP group name.
15. To confirm if there are LDAP users and LDAP user groups, click Analytics GroupsLDAP Users.
16. To view/edit a user group properties, right-click the user group and select edit.
17. On the Project Access, Members, and Authentication tabs, confirm the following for each user group:
    ADDITIONAL INFORMATION:

    • Project Access: Security roles are selected.
    • Members: User group has local user members.
    • Authentication: LDAP login is the DN of the user group on the LDAP server.
18. Delete user groups that have no security roles selected and have the DN of an LDAP group in the Authentication tab.
19. To delete a user group, right-click the user group and select delete.
    ADDITIONAL INFORMATION:

    Confirm deletion of the group.

    Note:

    • On completion, there are five user groups under User Manager (Advanced, Basic, Consumer, Analytics Groups, and Everyone).
    • The LDAP Users under Analytics Groups should contain LDAP users and no LDAP groups.
20. Log out of the Historical Reporting server administrator page.
21. To edit the mstr-srv configmap, run the following command:
    ADDITIONAL INFORMATION: kubectl edit cm -n mstr srv-configmap
22. Update the property UPD_GROUPS to True using the following command:
    ADDITIONAL INFORMATION: UPD_GROUPS: "true"

    Use i to make the configmap editable.
23. To escape the edit mode, press the Esc button.
24. Type :wq! and press Enter to save the changes.
25. Restart the mstr-srv pod using the following command:
    ADDITIONAL INFORMATION: kubectl delete pods -n mstr mstr-srv-<pod-id>
26. Confirm that the mstr-srv pod gets to a running state which can take more than 10 minutes.
27. Confirm the login of the LDAP user.
28. In the Historical Reporting server administrator UI, confirm the LDAP login under the authentication tab of each user group.
29. Take a new backup of the mstr-md metadata and export it to a secure location.