[jira] [Updated] (AMBARI-18148) Kerberos UI labels should be specific to differentiate between SPARK and SPARK2 properties
[ https://issues.apache.org/jira/browse/AMBARI-18148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-18148: - Reporter: Kishor Ramakrishnan (was: Andrii Babiichuk) > Kerberos UI labels should be specific to differentiate between SPARK and > SPARK2 properties > -- > > Key: AMBARI-18148 > URL: https://issues.apache.org/jira/browse/AMBARI-18148 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Kishor Ramakrishnan >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18148.patch > > > Kerberos UI labels should be specific to differentiate between SPARK and > SPARK2 properties. Currently the keytab and principal property labels for > SPARK and SPARK2 are the same and might confuse the admin user if both > services are present. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-18148) Kerberos UI labels should be specific to differentiate between SPARK and SPARK2 properties
[ https://issues.apache.org/jira/browse/AMBARI-18148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-18148: -- Fix Version/s: (was: trunk) 2.5.0 > Kerberos UI labels should be specific to differentiate between SPARK and > SPARK2 properties > -- > > Key: AMBARI-18148 > URL: https://issues.apache.org/jira/browse/AMBARI-18148 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18148.patch > > > Kerberos UI labels should be specific to differentiate between SPARK and > SPARK2 properties. Currently the keytab and principal property labels for > SPARK and SPARK2 are the same and might confuse the admin user if both > services are present. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18148) Kerberos UI labels should be specific to differentiate between SPARK and SPARK2 properties
[ https://issues.apache.org/jira/browse/AMBARI-18148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-18148: - Fix Version/s: (was: 2.5.0) trunk > Kerberos UI labels should be specific to differentiate between SPARK and > SPARK2 properties > -- > > Key: AMBARI-18148 > URL: https://issues.apache.org/jira/browse/AMBARI-18148 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-18148.patch > > > Kerberos UI labels should be specific to differentiate between SPARK and > SPARK2 properties. Currently the keytab and principal property labels for > SPARK and SPARK2 are the same and might confuse the admin user if both > services are present. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18148) Kerberos UI labels should be specific to differentiate between SPARK and SPARK2 properties
[ https://issues.apache.org/jira/browse/AMBARI-18148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-18148: -- Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk > Kerberos UI labels should be specific to differentiate between SPARK and > SPARK2 properties > -- > > Key: AMBARI-18148 > URL: https://issues.apache.org/jira/browse/AMBARI-18148 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18148.patch > > > Kerberos UI labels should be specific to differentiate between SPARK and > SPARK2 properties. Currently the keytab and principal property labels for > SPARK and SPARK2 are the same and might confuse the admin user if both > services are present. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18148) Kerberos UI labels should be specific to differentiate between SPARK and SPARK2 properties
[ https://issues.apache.org/jira/browse/AMBARI-18148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-18148: -- Attachment: AMBARI-18148.patch > Kerberos UI labels should be specific to differentiate between SPARK and > SPARK2 properties > -- > > Key: AMBARI-18148 > URL: https://issues.apache.org/jira/browse/AMBARI-18148 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18148.patch > > > Kerberos UI labels should be specific to differentiate between SPARK and > SPARK2 properties. Currently the keytab and principal property labels for > SPARK and SPARK2 are the same and might confuse the admin user if both > services are present. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18148) Kerberos UI labels should be specific to differentiate between SPARK and SPARK2 properties
[ https://issues.apache.org/jira/browse/AMBARI-18148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-18148: -- Status: Patch Available (was: Open) 29767 tests complete (26 seconds) 154 tests pending > Kerberos UI labels should be specific to differentiate between SPARK and > SPARK2 properties > -- > > Key: AMBARI-18148 > URL: https://issues.apache.org/jira/browse/AMBARI-18148 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18148.patch > > > Kerberos UI labels should be specific to differentiate between SPARK and > SPARK2 properties. Currently the keytab and principal property labels for > SPARK and SPARK2 are the same and might confuse the admin user if both > services are present. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
