You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Robert Levas (JIRA)" <ji...@apache.org> on 2015/01/15 01:50:35 UTC
[jira] [Updated] (AMBARI-9136) Need to provide meaningful names for
the stage context in Kerb API call response
[ https://issues.apache.org/jira/browse/AMBARI-9136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Levas updated AMBARI-9136:
---------------------------------
Attachment: AMBARI-9136_01.patch
Fixed stage names.
No unit tests were added or updated since changes were cosmetic.
Patch File [^AMBARI-9136_01.patch]
> Need to provide meaningful names for the stage context in Kerb API call response
> --------------------------------------------------------------------------------
>
> Key: AMBARI-9136
> URL: https://issues.apache.org/jira/browse/AMBARI-9136
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Robert Levas
> Assignee: Robert Levas
> Labels: kerberos
> Fix For: 2.0.0
>
> Attachments: AMBARI-9136_01.patch
>
>
> In the API response for Kerberizing the cluster, stage_context is set to "Process Kerberos Operations" for all operations. This needs to be more specific (e.g., Generate Principals, Generate Keytabs, Distribute Keytabs, etc).
> Due to the current behavior, "Kerberize Cluster" page repeatedly shows "Process Kerberos Operations" one after another and it doesn't make much sense to the end user.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)