1) If we check wasp and portal logs, we would find them full with these error messages:
ERROR [PortalInitAction:111] (4) not found, Received status (4) on response (for sendRcv) for cmd = 'nametoip' name = '/infba01-S3948_domain/infba01-S3948_hub/infba01-S3948/discovery_server'
ERROR [PortalInitAction:111] at com.firehunter.usm.DataFactory.getDiscoveryStatus(DataFactory.java:7029)
- The above errors tell us that there is something wrong with the address that wasp has of our discovery_server probe.
- Then, if we open controller's (on the robot where discovery_server probe is running) probe utility (ctrl + p) and run the so-called "nametoip" callback, we will see it returns an error: "Command status: not found".
- To fix this, we have to access wasp's Raw Configure (ctrl + right-click) and then, within the "ump_common" section, modify our "discovery_server" entry to makes it look like this: discovery_server = discovery_server.
- After that, if we go back to UMP, we should find the discovery_wizard gear just as it was before:
2) If the problem was with some particular user(s) and there was no error message while hovering over the "Inventory" field, then, most likely, there is a problem with the user using an ACL that is linked to an account.
- The explanation on this:
- For users to be able to see discovery wizard, they need to have certain permissions in their ACL (Discovery, Discovery Management):
- On top of that, the user needs to be a Bus user:
- LDAP should be transparent here. So, if we have a Bus user, that has an ACL with the required permissions BUT it is linked to an account, that would be like having an Account Contact user, thus, the user would not be able to see discovery wizard.
- To fix this, we need to go to:
- Infrastructure Manager: "Security", "Manage Access Control List", select our ACL and click on "Set Account Link...". Then, we would need to chose "<none>" so the user is no longer an Account Contact user, but a Bus user (if it was originally created as a Bus user).