Amabri local users are not visible in user management page after upgrade to 2.5.x from 2.4

[#1]

Just upgraded ambari from 2.4.x to 2.5.x. Also upgraded HDP from 2.5.0.x to 2.6.0.3. Ambari user logins are not working except for admin user. All are local users. On login as admin, in user management view no users are displayed, but when tried to create user which was existing earlier, getting error that "User already exists". What could be wrong. I have followed steps as in [1]

[1] -

https://docs.hortonworks.com/HDPDocuments/Ambari-2.5.0.3/bk_ambari-upgrade/content/post_ambari_upgra...

[#2 · Accepted solution]

@Vinuraj M

After restart ambari server put the ambari-server.log in tail and then try to login from ambari UI as "admin" user and then see if you get any error. Please share the log in case if you find any error/warning.

# tail -f /var/log/ambari-server/ambari-server.log

.

[#3]

Getting this exception.

13 Jun 2017 18:15:40,081 ERROR [ambari-client-thread-26] ReadHandler:102 - Caught a runtime exception executing a query com.google.common.cache.CacheLoader$InvalidCacheLoadException: CacheLoader returned null for key 10. at com.google.common.cache.LocalCache$Segment.getAndRecordStats(LocalCache.java:2348) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2318) at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2280) at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2195)

[#4]

@Vinuraj M

Please try the following:

Step1).

Take ambari server DB dump. (As we are going to modify the ambari DB entries), You might find that the mentioned resource is Zeppelin most probably. Because Zeppelin View is removed from Ambari 2.5 onwards.

select * from adminprivilege where resource_id = 10;

select * from adminresource where resource_id = 10;

select * from adminresourcetype where resource_type_id IN (select resource_type_id from adminresource where resource_id = 10);   

Step2). Delete the entries with key 10

SELECT adminresource.resource_id FROM adminresource LEFT OUTER JOIN viewinstance USING (resource_id) WHERE  adminresource.resource_type_id = 10 AND viewinstance.view_instance_id IS NULL; 

DELETE FROM adminprivilege where resource_id in (10);

DELETE FROM adminresource where resource_id in (10);

Step3). Now restart ambari server.

.

[#5]

@Vinuraj M

Your issue looks related to : https://community.hortonworks.com/questions/103489/after-upgrading-ambari-from-242-to-250-not-able-t...

[#6]

Users are back after following the steps suggested. Thanks for the quick response