[jira] [Updated] (AMBARI-24522) Cannot connect to MIT KDC admin server when port is specified in kerberos-env/admin_server_host

2018-10-22 Thread Jayush Luniya (JIRA) 


 [ 
https://issues.apache.org/jira/browse/AMBARI-24522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayush Luniya updated AMBARI-24522:
---
Fix Version/s: (was: 2.7.2)
   2.7.3

> Cannot connect to MIT KDC admin server when port is specified in 
> kerberos-env/admin_server_host
> ---
>
> Key: AMBARI-24522
> URL: https://issues.apache.org/jira/browse/AMBARI-24522
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
>  Labels: kerberos, pull-request-available, regression
> Fix For: 2.7.3
>
>  Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> Cannot connect to MIT KDC admin server when port is specified in 
> {{kerberos-env/admin_server_host}}.  The following error is seen when 
> validating the KDC admin credentials:
> {noformat}
> kinit: Server not found in Kerberos database while getting initial credentials
> {noformat}
> The reason for this is due to how the credentials are created for accessing 
> the MIT KDC administration server. 
> {noformat}
> kinit -c  -S kadmin/  
> {noformat}
> If a port was added to the {{kerberos-env/admin_server_host}} value then the 
> server principal will be generated like {{kadmin/kdc.example.com:4749}} 
> rather than {{kadmin/kdc.example.com}}. Therefore the server principal is not 
> found.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24522) Cannot connect to MIT KDC admin server when port is specified in kerberos-env/admin_server_host

2018-08-30 Thread Robert Levas (JIRA) 


 [ 
https://issues.apache.org/jira/browse/AMBARI-24522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Levas updated AMBARI-24522:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Cannot connect to MIT KDC admin server when port is specified in 
> kerberos-env/admin_server_host
> ---
>
> Key: AMBARI-24522
> URL: https://issues.apache.org/jira/browse/AMBARI-24522
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
>  Labels: kerberos, pull-request-available, regression
> Fix For: 2.7.2
>
>  Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> Cannot connect to MIT KDC admin server when port is specified in 
> {{kerberos-env/admin_server_host}}.  The following error is seen when 
> validating the KDC admin credentials:
> {noformat}
> kinit: Server not found in Kerberos database while getting initial credentials
> {noformat}
> The reason for this is due to how the credentials are created for accessing 
> the MIT KDC administration server. 
> {noformat}
> kinit -c  -S kadmin/  
> {noformat}
> If a port was added to the {{kerberos-env/admin_server_host}} value then the 
> server principal will be generated like {{kadmin/kdc.example.com:4749}} 
> rather than {{kadmin/kdc.example.com}}. Therefore the server principal is not 
> found.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24522) Cannot connect to MIT KDC admin server when port is specified in kerberos-env/admin_server_host

2018-08-21 Thread Robert Levas (JIRA) 


 [ 
https://issues.apache.org/jira/browse/AMBARI-24522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Levas updated AMBARI-24522:
--
Status: Patch Available  (was: In Progress)

> Cannot connect to MIT KDC admin server when port is specified in 
> kerberos-env/admin_server_host
> ---
>
> Key: AMBARI-24522
> URL: https://issues.apache.org/jira/browse/AMBARI-24522
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
>  Labels: kerberos, pull-request-available, regression
> Fix For: 2.7.2
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Cannot connect to MIT KDC admin server when port is specified in 
> {{kerberos-env/admin_server_host}}.  The following error is seen when 
> validating the KDC admin credentials:
> {noformat}
> kinit: Server not found in Kerberos database while getting initial credentials
> {noformat}
> The reason for this is due to how the credentials are created for accessing 
> the MIT KDC administration server. 
> {noformat}
> kinit -c  -S kadmin/  
> {noformat}
> If a port was added to the {{kerberos-env/admin_server_host}} value then the 
> server principal will be generated like {{kadmin/kdc.example.com:4749}} 
> rather than {{kadmin/kdc.example.com}}. Therefore the server principal is not 
> found.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24522) Cannot connect to MIT KDC admin server when port is specified in kerberos-env/admin_server_host

2018-08-21 Thread ASF GitHub Bot (JIRA) 


 [ 
https://issues.apache.org/jira/browse/AMBARI-24522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated AMBARI-24522:

Labels: kerberos pull-request-available regression  (was: kerberos 
regression)

> Cannot connect to MIT KDC admin server when port is specified in 
> kerberos-env/admin_server_host
> ---
>
> Key: AMBARI-24522
> URL: https://issues.apache.org/jira/browse/AMBARI-24522
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
>  Labels: kerberos, pull-request-available, regression
> Fix For: 2.7.2
>
>
> Cannot connect to MIT KDC admin server when port is specified in 
> {{kerberos-env/admin_server_host}}.  The following error is seen when 
> validating the KDC admin credentials:
> {noformat}
> kinit: Server not found in Kerberos database while getting initial credentials
> {noformat}
> The reason for this is due to how the credentials are created for accessing 
> the MIT KDC administration server. 
> {noformat}
> kinit -c  -S kadmin/  
> {noformat}
> If a port was added to the {{kerberos-env/admin_server_host}} value then the 
> server principal will be generated like {{kadmin/kdc.example.com:4749}} 
> rather than {{kadmin/kdc.example.com}}. Therefore the server principal is not 
> found.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-24522) Cannot connect to MIT KDC admin server when port is specified in kerberos-env/admin_server_host

2018-08-21 Thread Robert Levas (JIRA) 


 [ 
https://issues.apache.org/jira/browse/AMBARI-24522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Levas updated AMBARI-24522:
--
Fix Version/s: (was: 2.7.1)
   2.7.2

> Cannot connect to MIT KDC admin server when port is specified in 
> kerberos-env/admin_server_host
> ---
>
> Key: AMBARI-24522
> URL: https://issues.apache.org/jira/browse/AMBARI-24522
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
>  Labels: kerberos, regression
> Fix For: 2.7.2
>
>
> Cannot connect to MIT KDC admin server when port is specified in 
> {{kerberos-env/admin_server_host}}.  The following error is seen when 
> validating the KDC admin credentials:
> {noformat}
> kinit: Server not found in Kerberos database while getting initial credentials
> {noformat}
> The reason for this is due to how the credentials are created for accessing 
> the MIT KDC administration server. 
> {noformat}
> kinit -c  -S kadmin/  
> {noformat}
> If a port was added to the {{kerberos-env/admin_server_host}} value then the 
> server principal will be generated like {{kadmin/kdc.example.com:4749}} 
> rather than {{kadmin/kdc.example.com}}. Therefore the server principal is not 
> found.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)