Troubleshooting Missing Tabs in DataHub UI on Amazon EKS

ui
1

Original Slack Thread

<@U06TM7M40RK> I have deployed data hub on Amazon EKS. Now when I am logging into datahub UI using default ‘datahub’ user, I am not seeing Analytics and ingesting tab.
Do we need to add certain permissions to default ‘datahub’ user?

2

It seems likely that the issue you’re experiencing with missing Analytics and Ingestion tabs in the DataHub UI could be related to permissions or roles assigned to the default ‘datahub’ user. According to the <https://datahubproject.io/docs/0.14.0/authorization/roles#platform-privileges|Platform Privileges documentation>, certain privileges are required to manage metadata ingestion and view analytics. The default ‘datahub’ user should typically have these privileges, but if they are missing, you might need to adjust the permissions.

Here are some steps you might consider:

  1. Check User Roles and Permissions: Ensure that the ‘datahub’ user has the necessary roles and permissions. You can do this by accessing the admin panel and reviewing the roles/permissions section. If the ‘datahub’ user does not have admin rights, you may need to assign them.

  2. Manage Metadata Ingestion Privilege: The ‘Manage Metadata Ingestion’ privilege is required to create, remove, and update metadata ingestion sources. If this privilege is not assigned, the Ingestion tab might not be visible.

  3. View Analytics Privilege: To view the analytics dashboard, the ‘View Analytics’ privilege is necessary. Ensure that this privilege is granted to the ‘datahub’ user.

  4. Configuration Files: If you have modified configuration files such as user.props or policies.json, ensure that they reflect the correct user roles and permissions. According to the <https://datahubproject.io/docs/0.14.0/troubleshooting/quickstart#ive-modified-the-default-userprops-file-to-include-a-custom-username-and-password-but-i-dont-see-the-new-users-inside-the-users--groups-tab-why-not|troubleshooting guide>, changes in these files might not automatically reflect in the UI.

  5. Restart Services: After making changes to permissions or configuration files, it might be necessary to restart the DataHub services to apply the changes.

Would you like more detailed steps or further assistance with this issue?

Sources:

3

Hi <@U08PBD4M9RR>, how did my answer work out for you? Need any more assistance? You can also tag <@U07FV3UHE4D> to let your fellow community members know you’re still looking for guidance.

4

<@U06TM7M40RK> It didn’t work.
<@U07FV3UHE4D> can you pls help here. This looks like a bug in new datahub release

5

If the steps provided earlier did not resolve the issue, and you suspect it might be a bug in the new DataHub release, here are a few additional steps you can take:

  1. Check for Known Issues: Review the <https://github.com/datahub-project/datahub/issues|GitHub issues page for DataHub> to see if there are any known issues related to the missing tabs in the UI for the version you are using.

  2. Review Release Notes: Check the release notes for the version you are using to see if there are any changes or known issues that might affect the UI. Sometimes, features might be moved or require additional configuration in newer releases.

  3. Verify Role Assignments: Double-check the role assignments for the ‘datahub’ user. According to the <https://github.com/datahub-project/datahub/blob/master/docs/authorization/roles.md|Roles documentation>, the ‘Admin’ role should have full access to all features, including Analytics and Ingestion.

  4. Inspect Logs: Look at the logs for the DataHub frontend and backend services to see if there are any error messages or warnings that might indicate what is going wrong. You can use kubectl logs <pod-name> -n <namespace> to view logs for specific pods.

  5. Community Support: Consider reaching out to the DataHub community on https://datahubspace.slack.com|Slack for real-time support. There might be other users who have encountered similar issues and can offer solutions.

  6. Reinstall or Rollback: If the issue persists and you suspect it’s a bug, you might consider rolling back to a previous version of DataHub that was working correctly for you.

Would you like more detailed steps on any of these troubleshooting points or further assistance on a specific part of the process?

Sources: