You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Sandor Molnar (JIRA)" <ji...@apache.org> on 2018/06/07 18:08:00 UTC
[jira] [Created] (AMBARI-24054) Test Kerberos Client fail after
reenter of right realm value
Sandor Molnar created AMBARI-24054:
--------------------------------------
Summary: Test Kerberos Client fail after reenter of right realm value
Key: AMBARI-24054
URL: https://issues.apache.org/jira/browse/AMBARI-24054
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Sandor Molnar
Assignee: Sandor Molnar
Fix For: 2.7.0
Test Kerberos Client fail after reenter of right realm value during kerberos enabling
STR:
1)Start of kerberos enabling
2)Select existing MIT
3)Go to Configure Kerberos page
4)Set wrong "Realm name" value. As an example: "example.com" (expected EXAMPLE.COM)
5)Go to Install and Test Kerberos Client step
6)Wait of Test Kerberos Client fail
7)Back to Configure Kerberos step
8)Enter right "Realm name" value
9)Go to Install and Test Kerberos Client step
Expected:
Test Kerberos Client pass successfully
Actual:
Test Kerberos Client fail
The supposed main reason is using old realm value for principals creation:
{code:java}
2018-05-30 11:13:38,895 - Failed to create principal, cl1-053018@example.com - Failed to create service principal for cl1-053018@example.com
STDOUT: Authenticating as principal admin/admin@EXAMPLE.COM with existing credentials.
STDERR: WARNING: no policy specified for cl1-053018@example.com; defaulting to no policy
add_principal: No such entry in the database while creating "cl1-053018@example.com".
Administration credentials NOT DESTROYED.
{code}
This is happening only using MySQL.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)