Support Questions
Find answers, ask questions, and share your expertise

Cloudera Atlas 2.0; error when acess any item, " Unknown Entity-Type"

Explorer

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"

image.png

 

But, looking the searching options we can´t find any ENTITY-TYPE:

image.png

 

Someone have any idea why  not show any ENTITY TYPE?

 

Thanks

Eduardo 

2 ACCEPTED SOLUTIONS

Accepted Solutions

Cloudera Employee
  • 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.

Screenshot 2021-01-06 at 1.59.32 PM.png

 

2. From the drop down actions menu, select "Upgrade Ranger database and apply patches".

Screenshot 2021-01-06 at 2.00.44 PM.png

 

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):

Screenshot 2021-01-06 at 2.10.59 PM.png

We need something similar to this:

Screenshot 2021-01-06 at 2.11.47 PM.png

 

View solution in original post

Explorer

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 

View solution in original post

11 REPLIES 11

Explorer

Hi

 

how did you resolved this problem?

 

BR,

Gabor

Explorer

Hi Gabor

  

 We didn´t resolve this problem yet.

 

I will try to open a case on Cloudera Support.

 

Thanks

Eduardo 

Explorer

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

Explorer

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

Explorer

Hi Eduardo,

 

any update on this?

 

BR,

Gabor

Explorer

Do you have Ranger?

Explorer

Hi Gabor

   

 Not yet.  we decided to apply the upgrade after the holidays.

 

we wish to do this week.

 

thank your contact.

 

Eduardo

Cloudera Employee
  • 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.

Screenshot 2021-01-06 at 1.59.32 PM.png

 

2. From the drop down actions menu, select "Upgrade Ranger database and apply patches".

Screenshot 2021-01-06 at 2.00.44 PM.png

 

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):

Screenshot 2021-01-06 at 2.10.59 PM.png

We need something similar to this:

Screenshot 2021-01-06 at 2.11.47 PM.png

 

View solution in original post

Explorer

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