- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Cloudera Atlas 2.0; error when acess any item, " Unknown Entity-Type"
Created ā12-08-2020 09:43 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi folks,
After install Cloudera CDP 7.1.4 we access Altas and searched items .
When click any item we receive this error "Unknown Entity-Type"
But, looking the searching options we canĀ“t find any ENTITY-TYPE:
Someone have any idea why not show any ENTITY TYPE?
Thanks
Eduardo
Created ā01-06-2021 12:45 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- This happens because the "Read Type" permission is absent in the Ranger-Atlas plugin repository for the Atlas service.
- During the upgrade, a step to upgrade the ranger DB with the patches is skipped. Which is causing this permission to be not present after the CDP upgrade.
- The update handler needs to call the right script to install the DB patches for ranger which should automatically update the DB patches (during the upgrade process) and fix the issue.
- Issue is addressed and should be fixed in the upcoming releases of the the Cloudera Manager product line.
The workaround for this issue:
- Stop the Ranger Admin service.
1. Login in into CM UI -> Ranger -> Instances -> Select Ranger Admin.
2. From the drop down actions menu, select "Upgrade Ranger database and apply patches".
3. This step will manually apply the patches and will finish.
4. Once finished, you can restart the Ranger Admin service.
The atlas policy which is missing the permission (the id of policy can be different in your environment):
ā
We need something similar to this:
ā
Created ā01-11-2021 05:02 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Parth,
I apply the fix that you sent and it works fine.
Really, the problem was in upgrade ranger database after last upgrade.
thanks very much.
best regards
Eduardo
Created ā12-16-2020 09:41 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
how did you resolved this problem?
BR,
Gabor
Created ā12-16-2020 10:07 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Gabor
We didnĀ“t resolve this problem yet.
I will try to open a case on Cloudera Support.
Thanks
Eduardo
Created ā12-16-2020 10:11 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
19986569-41:] ~ Exception while fetching groups (AtlasAbstractAuthenticationProvider:137) java.io.IOException: No groups found for user HTTP
Do you see this kind of errors in your Atlas Logs? Btw, we already upgraded to 7.1.5, but the same problem. Before upgrade it was working fine. If I get an update on this, I will inform you.
BR,
Gabor
Created ā12-16-2020 11:29 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Gabor
Thanks for your information.
I will upgrade to 7.1.5 and check if this resolved your problem.
I will tell you the results soon.
Regards
Eduardo
Created ā01-04-2021 11:53 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Eduardo,
any update on this?
BR,
Gabor
Created ā01-04-2021 11:53 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Do you have Ranger?
Created ā01-06-2021 02:24 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Gabor
Not yet. we decided to apply the upgrade after the holidays.
we wish to do this week.
thank your contact.
Eduardo
Created ā01-06-2021 12:45 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- This happens because the "Read Type" permission is absent in the Ranger-Atlas plugin repository for the Atlas service.
- During the upgrade, a step to upgrade the ranger DB with the patches is skipped. Which is causing this permission to be not present after the CDP upgrade.
- The update handler needs to call the right script to install the DB patches for ranger which should automatically update the DB patches (during the upgrade process) and fix the issue.
- Issue is addressed and should be fixed in the upcoming releases of the the Cloudera Manager product line.
The workaround for this issue:
- Stop the Ranger Admin service.
1. Login in into CM UI -> Ranger -> Instances -> Select Ranger Admin.
2. From the drop down actions menu, select "Upgrade Ranger database and apply patches".
3. This step will manually apply the patches and will finish.
4. Once finished, you can restart the Ranger Admin service.
The atlas policy which is missing the permission (the id of policy can be different in your environment):
ā
We need something similar to this:
ā
Created ā01-06-2021 12:50 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you Parth for your support,
it's working now. Even in DEV, that was just a login problem with a wrong username.
BR,
Gabor
