Created on 12-14-2016 05:34 PM - edited 08-18-2019 05:38 AM
After upgrading to from Ambari 2.1.2.1 to Ambari 2.4.2.0 i can no longer edit Capacity Scheduler queues. I receive:
Warning! You do not have permission to edit the Capacity Scheduler configuration. Contact your Cluster administrator.
However, my user is Amabri Administrator user:
Even the Audit log confirms this:
If i login with the default local Admin user - it works and i can change queues configuration. The only thing that has changed is the Ambari version due to the upgrade. No changes were made to my user which is and always have been an Administrator user.
Any ideas ?
Created 04-04-2017 05:36 AM
Apparently it's caused due to this known bug: https://issues.apache.org/jira/browse/AMBARI-18520
I've received a fix from HW after opening a case 🙂
Adi
Created 12-14-2016 06:20 PM
Is LDAP working? Do you need to restart anything?
Created 12-15-2016 05:58 AM
Thank you for replying
LDAP is working - i'm able to login using my LDAP user & password and so do other users from LDAP. Also - after the upgrade, as part of the post-upgrade i have ran the ambari ldap setup again (as required in the upgrade manual) and restarted Ambari + All of the services of the cluster + the Ambari host itself - several times.
Created 04-03-2017 09:04 PM
I'm pretty sure the Capacity Scheduler permissions query against the Ambari API is incorrect. The change that introduced this is here:
https://github.com/apache/ambari/commit/82ccf224f0142b0b63c13e6ac0d58d45f55dd5ab
The related JIRA: https://issues.apache.org/jira/browse/AMBARI-16866
The correct url:
http://AMBARI/api/v1/users/USERNAME/privileges?PrivilegeInfo/permission_name=AMBARI.ADMINISTRATOR|(P...
This returns the list of privileges.
The incorrect url:
http://AMBARI/api/v1/users/USERNAME?privileges/PrivilegeInfo/permission_name=AMBARI.ADMINISTRATOR|(p...
This returns a blank page.
Created 04-04-2017 05:36 AM
Apparently it's caused due to this known bug: https://issues.apache.org/jira/browse/AMBARI-18520
I've received a fix from HW after opening a case 🙂
Adi
Created 05-03-2017 06:56 AM
I am having the same issues after upgrading from Ambari 2.4.0.1 to Ambari 2.5.0.3: The CapSched View is effectively unusable, as no Admin can access it anymore.
Created 05-03-2017 08:30 AM
@Roland Simonis Do you use LDAP for Ambari authentication ? If so, go to /etc/ambari-server/conf
edit ambari.properties Add: authentication.ldap.username.forceLowercase=true Ssave Restart Ambari Check CapSched again.
Created 05-03-2017 08:58 AM
@Adi Jabkowsky This did the trick! Thank you. Now it works.