[jira] [Created] (AMBARI-19314) Include Hadoop conf directory in Atlas class path

[Vishal Suvagia (JIRA)]

Vishal Suvagia created AMBARI-19314:
---

 Summary: Include Hadoop conf directory in Atlas class path
 Key: AMBARI-19314
 URL: https://issues.apache.org/jira/browse/AMBARI-19314
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.5.0
Reporter: Vishal Suvagia
Assignee: Vishal Suvagia
 Fix For: 2.5.0


Need to include Hadoop conf directory in Atlas environment classpath.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19275) Single API to download all client configs

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784129#comment-15784129
 ] 

Hudson commented on AMBARI-19275:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #607 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/607/])
AMBARI-19275. Single API to download all client configs. (jaimin) (jaimin: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=08a9984553d26d939b227800cbe2414fbf7d1856])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/api/services/ComponentService.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/api/services/HostComponentService.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClientConfigResourceProvider.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/api/services/ComponentServiceTest.java
* (edit) ambari-server/pom.xml
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/api/services/HostComponentServiceTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClientConfigResourceProviderTest.java


> Single API to download all client configs 
> --
>
> Key: AMBARI-19275
> URL: https://issues.apache.org/jira/browse/AMBARI-19275
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jaimin Jetly
>Assignee: Jaimin Jetly
> Fix For: 2.5.0
>
> Attachments: AMBARI-19275.1.patch, AMBARI-19275.2.patch, 
> AMBARI-19275.3.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19312) Improve and Fix "Alerts page" after new guidelines

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784100#comment-15784100
 ] 

Hudson commented on AMBARI-19312:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6319 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6319/])
AMBARI-19312. Improve and Fix 'Alerts page' after new guidelines. (xiwang: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6add93ea482555084e5d001c47bf1f86f2dfe99b])
* (edit) ambari-web/app/styles/alerts.less
* (edit) ambari-web/app/styles/application.less


> Improve and Fix "Alerts page" after new guidelines
> --
>
> Key: AMBARI-19312
> URL: https://issues.apache.org/jira/browse/AMBARI-19312
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 3.0.0
>
> Attachments: AMBARI-19312.patch, Screen Shot 2016-12-28 at 1.38.43 
> PM.png
>
>
> Alerts Table:
> 1. Texts not centered every row.
> 2. Active Filter in each column should not have shadow, no remove icon.
> Alert Instance page:
> 3. Texts not centered every row.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19305) Improve and Fix "Services page" after new guidelines

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784101#comment-15784101
 ] 

Hudson commented on AMBARI-19305:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6319 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6319/])
AMBARI-19305. Improve and Fix 'Services page' after new (xiwang: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a2c907b2d9c2da58c7907e0ee9a3b5ad5376f361])
* (edit) ambari-web/app/styles/enhanced_service_dashboard.less
* (edit) ambari-web/app/views/main/service/widgets/create/expression_view.js


> Improve and Fix "Services page" after new guidelines
> 
>
> Key: AMBARI-19305
> URL: https://issues.apache.org/jira/browse/AMBARI-19305
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 3.0.0
>
> Attachments: AMBARI-19305.patch
>
>
> Create wizard: 
> Step 2:
> The preview should be centered.
> Add Metric submenu, when a metric/operator got selected, the submenu should 
> not disappear. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19275) Single API to download all client configs

[Jaimin Jetly (JIRA)]

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

Jaimin Jetly updated AMBARI-19275:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Received +1 on review board.
Patch committed to trunk and branch-2.5

> Single API to download all client configs 
> --
>
> Key: AMBARI-19275
> URL: https://issues.apache.org/jira/browse/AMBARI-19275
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jaimin Jetly
>Assignee: Jaimin Jetly
> Fix For: 2.5.0
>
> Attachments: AMBARI-19275.1.patch, AMBARI-19275.2.patch, 
> AMBARI-19275.3.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19275) Single API to download all client configs

[Jaimin Jetly (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784051#comment-15784051
 ] 

Jaimin Jetly commented on AMBARI-19275:
---

The above failure in org.apache.ambari.server.state.ServicePropertiesTest is 
unrelated to this patch. This was caused due to initial commit of AMBARI-19274 
patch.


> Single API to download all client configs 
> --
>
> Key: AMBARI-19275
> URL: https://issues.apache.org/jira/browse/AMBARI-19275
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jaimin Jetly
>Assignee: Jaimin Jetly
> Fix For: 2.5.0
>
> Attachments: AMBARI-19275.1.patch, AMBARI-19275.2.patch, 
> AMBARI-19275.3.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19206) When Namenode HA is enabled, hbase.rootdir property for ambari-metrics (distributed) does not get updated

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784044#comment-15784044
 ] 

Hudson commented on AMBARI-19206:
-

ABORTED: Integrated in Jenkins build Ambari-trunk-Commit #6318 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6318/])
AMBARI-19206: When Namenode HA is enabled, hbase.rootdir property for 
(sangeetar: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=540f4ee9ac15d1d1794e8a57db043114dd441dc5])
* (edit) 
ambari-web/test/controllers/main/admin/highAvailability/nameNode/step3_controller_test.js
* (edit) ambari-web/app/messages.js
* (edit) 
ambari-web/app/controllers/main/admin/highAvailability/nameNode/step9_controller.js
* (edit) 
ambari-web/app/controllers/main/admin/highAvailability/nameNode/rollback_controller.js


> When Namenode HA is enabled, hbase.rootdir property for ambari-metrics 
> (distributed) does not get updated
> -
>
> Key: AMBARI-19206
> URL: https://issues.apache.org/jira/browse/AMBARI-19206
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0, 2.4.2
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19206.patch, AMSHbaseRootdirPostNNHAEnabling.jpg, 
> NNHAWizard1.jpg, NNHAWizard2.jpg
>
>
> On a cluster with ambari-metrics in distributed operation mode, enable 
> Namenode HA.
> After HA wizard is run, the amabri-metrics property for hbase.rootdir should 
> point to hdfs://, but it actually still points to the 
> explicit Namenode.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19206) When Namenode HA is enabled, hbase.rootdir property for ambari-metrics (distributed) does not get updated

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783923#comment-15783923
 ] 

Hudson commented on AMBARI-19206:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #606 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/606/])
AMBARI-19206: When Namenode HA is enabled, hbase.rootdir property for 
(sangeetar: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=eae2a4c5e4b4b5dc279d9553d025fb00eb337849])
* (edit) 
ambari-web/test/controllers/main/admin/highAvailability/nameNode/step3_controller_test.js
* (edit) ambari-web/app/messages.js
* (edit) 
ambari-web/app/controllers/main/admin/highAvailability/nameNode/rollback_controller.js
* (edit) 
ambari-web/app/controllers/main/admin/highAvailability/nameNode/step9_controller.js


> When Namenode HA is enabled, hbase.rootdir property for ambari-metrics 
> (distributed) does not get updated
> -
>
> Key: AMBARI-19206
> URL: https://issues.apache.org/jira/browse/AMBARI-19206
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0, 2.4.2
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19206.patch, AMSHbaseRootdirPostNNHAEnabling.jpg, 
> NNHAWizard1.jpg, NNHAWizard2.jpg
>
>
> On a cluster with ambari-metrics in distributed operation mode, enable 
> Namenode HA.
> After HA wizard is run, the amabri-metrics property for hbase.rootdir should 
> point to hdfs://, but it actually still points to the 
> explicit Namenode.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18952) Register BackupObserver and BackupHFileCleaner

[Ted Yu (JIRA)]

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

Ted Yu updated AMBARI-18952:

Description: 
Over in HBASE-14417, two new classes are added.

org.apache.hadoop.hbase.backup.BackupHFileCleaner should be registered through 
hbase.master.hfilecleaner.plugins . It is responsible for keeping bulk loaded 
hfiles so that incremental backup can pick them up.

org.apache.hadoop.hbase.backup.BackupObserver should be registered through 
hbase.coprocessor.region.classes
It is notified when bulk load completes and writes records into hbase:backup 
table.

  was:
Over in HBASE-14417, two new classes are added.

BackupHFileCleaner should be registered through 
hbase.master.hfilecleaner.plugins . It is responsible for keeping bulk loaded 
hfiles so that incremental backup can pick them up.


BackupObserver should be registered through hbase.coprocessor.region.classes
It is notified when bulk load completes and writes records into hbase:backup 
table.


> Register BackupObserver and BackupHFileCleaner
> --
>
> Key: AMBARI-18952
> URL: https://issues.apache.org/jira/browse/AMBARI-18952
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Ted Yu
>
> Over in HBASE-14417, two new classes are added.
> org.apache.hadoop.hbase.backup.BackupHFileCleaner should be registered 
> through hbase.master.hfilecleaner.plugins . It is responsible for keeping 
> bulk loaded hfiles so that incremental backup can pick them up.
> org.apache.hadoop.hbase.backup.BackupObserver should be registered through 
> hbase.coprocessor.region.classes
> It is notified when bulk load completes and writes records into hbase:backup 
> table.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14958) Alerts: Create new Alerts Notification type for SNMP to handle Ambari MIB

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-14958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783871#comment-15783871
 ] 

Hudson commented on AMBARI-14958:
-

ABORTED: Integrated in Jenkins build Ambari-branch-2.5 #605 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/605/])
AMBARI-14958. Alerts: Create new Alerts Notification type for SNMP to (yusaku: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4f8934d68575a4de01a579c731671fb6e22679da])
* (edit) 
ambari-web/app/controllers/main/alerts/manage_alert_notifications_controller.js
* (edit) ambari-web/app/views/main/alerts/manage_alert_notifications_view.js
* (edit) ambari-web/app/templates/main/alerts/create_alert_notification.hbs


> Alerts: Create new Alerts Notification type for SNMP to handle Ambari MIB
> -
>
> Key: AMBARI-14958
> URL: https://issues.apache.org/jira/browse/AMBARI-14958
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Vivek Ratnavel Subramanian
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-14958.patch, AMBARI-14958.v0.patch, 
> AMBARI-14958.v1.branch-2.5.patch, AMBARI-14958.v1.trunk.patch
>
>
> 1) Rename current notification type "SNMP" to "Custom SNMP"
> 2) Create a new notification type "SNMP" that prompts for version, community, 
> hosts, ports
> 3) When this is chosen, Ambari under-the-hood generates the SNMP traps based 
> on the MIB.
> 4) The MIB file should be shipped with Ambari.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19252) Incorrect Method types displayed in the description of created Alert notification

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783872#comment-15783872
 ] 

Hudson commented on AMBARI-19252:
-

ABORTED: Integrated in Jenkins build Ambari-branch-2.5 #605 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/605/])
AMBARI-19252. Incorrect Method types displayed in the description of (yusaku: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a76c5c8b2ce19b8d46805b12baf22d64c45d0f6e])
* (edit) 
ambari-web/test/controllers/main/alerts/manage_alert_notifications_controller_test.js
* (edit) 
ambari-web/app/templates/main/alerts/manage_alert_notifications_popup.hbs
* (edit) 
ambari-web/app/controllers/main/alerts/manage_alert_notifications_controller.js
* (edit) ambari-web/app/views/main/alerts/manage_alert_notifications_view.js


> Incorrect Method types displayed in the description of created Alert 
> notification
> -
>
> Key: AMBARI-19252
> URL: https://issues.apache.org/jira/browse/AMBARI-19252
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19252.v0.branch-2.5.patch, 
> AMBARI-19252.v0.trunk.patch
>
>
> Incorrect Method types displayed in the description of created Alert 
> notification.
> STR:
> 1. Create Alert Notifications with Methods "Custom SNMP" and "SNMP"
> 2. After creation, select the created "Custom SNMP" notification the method 
> type is displayed as "SNMP" in the UI
> 3. Select the created "SNMP" notification the method type is displayed as 
> "AMBARI_SNMP" in the UI



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19305) Improve and Fix "Services page" after new guidelines

[Xi Wang (JIRA)]

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

Xi Wang updated AMBARI-19305:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk

> Improve and Fix "Services page" after new guidelines
> 
>
> Key: AMBARI-19305
> URL: https://issues.apache.org/jira/browse/AMBARI-19305
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 3.0.0
>
> Attachments: AMBARI-19305.patch
>
>
> Create wizard: 
> Step 2:
> The preview should be centered.
> Add Metric submenu, when a metric/operator got selected, the submenu should 
> not disappear. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19312) Improve and Fix "Alerts page" after new guidelines

[Xi Wang (JIRA)]

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

Xi Wang updated AMBARI-19312:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk

> Improve and Fix "Alerts page" after new guidelines
> --
>
> Key: AMBARI-19312
> URL: https://issues.apache.org/jira/browse/AMBARI-19312
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 3.0.0
>
> Attachments: AMBARI-19312.patch, Screen Shot 2016-12-28 at 1.38.43 
> PM.png
>
>
> Alerts Table:
> 1. Texts not centered every row.
> 2. Active Filter in each column should not have shadow, no remove icon.
> Alert Instance page:
> 3. Texts not centered every row.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19312) Improve and Fix "Alerts page" after new guidelines

[Jaimin Jetly (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783813#comment-15783813
 ] 

Jaimin Jetly commented on AMBARI-19312:
---

+1 for the patch

> Improve and Fix "Alerts page" after new guidelines
> --
>
> Key: AMBARI-19312
> URL: https://issues.apache.org/jira/browse/AMBARI-19312
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 3.0.0
>
> Attachments: AMBARI-19312.patch, Screen Shot 2016-12-28 at 1.38.43 
> PM.png
>
>
> Alerts Table:
> 1. Texts not centered every row.
> 2. Active Filter in each column should not have shadow, no remove icon.
> Alert Instance page:
> 3. Texts not centered every row.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19312) Improve and Fix "Alerts page" after new guidelines

[Xi Wang (JIRA)]

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

Xi Wang updated AMBARI-19312:
-
Attachment: Screen Shot 2016-12-28 at 1.38.43 PM.png

> Improve and Fix "Alerts page" after new guidelines
> --
>
> Key: AMBARI-19312
> URL: https://issues.apache.org/jira/browse/AMBARI-19312
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 3.0.0
>
> Attachments: AMBARI-19312.patch, Screen Shot 2016-12-28 at 1.38.43 
> PM.png
>
>
> Alerts Table:
> 1. Texts not centered every row.
> 2. Active Filter in each column should not have shadow, no remove icon.
> Alert Instance page:
> 3. Texts not centered every row.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19312) Improve and Fix "Alerts page" after new guidelines

[Xi Wang (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783784#comment-15783784
 ] 

Xi Wang commented on AMBARI-19312:
--

19835 passing (21s)
  153 pending

> Improve and Fix "Alerts page" after new guidelines
> --
>
> Key: AMBARI-19312
> URL: https://issues.apache.org/jira/browse/AMBARI-19312
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 3.0.0
>
> Attachments: AMBARI-19312.patch
>
>
> Alerts Table:
> 1. Texts not centered every row.
> 2. Active Filter in each column should not have shadow, no remove icon.
> Alert Instance page:
> 3. Texts not centered every row.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19312) Improve and Fix "Alerts page" after new guidelines

[Xi Wang (JIRA)]

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

Xi Wang updated AMBARI-19312:
-
Status: Patch Available  (was: Open)

> Improve and Fix "Alerts page" after new guidelines
> --
>
> Key: AMBARI-19312
> URL: https://issues.apache.org/jira/browse/AMBARI-19312
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 3.0.0
>
> Attachments: AMBARI-19312.patch
>
>
> Alerts Table:
> 1. Texts not centered every row.
> 2. Active Filter in each column should not have shadow, no remove icon.
> Alert Instance page:
> 3. Texts not centered every row.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19312) Improve and Fix "Alerts page" after new guidelines

[Xi Wang (JIRA)]

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

Xi Wang updated AMBARI-19312:
-
Attachment: AMBARI-19312.patch

> Improve and Fix "Alerts page" after new guidelines
> --
>
> Key: AMBARI-19312
> URL: https://issues.apache.org/jira/browse/AMBARI-19312
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 3.0.0
>
> Attachments: AMBARI-19312.patch
>
>
> Alerts Table:
> 1. Texts not centered every row.
> 2. Active Filter in each column should not have shadow, no remove icon.
> Alert Instance page:
> 3. Texts not centered every row.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-19313) Improve and Fix "Hosts page" after new guidelines

[Xi Wang (JIRA)]

Xi Wang created AMBARI-19313:


 Summary: Improve and Fix "Hosts page" after new guidelines
 Key: AMBARI-19313
 URL: https://issues.apache.org/jira/browse/AMBARI-19313
 Project: Ambari
  Issue Type: Task
  Components: ambari-web
Affects Versions: 3.0.0
Reporter: Xi Wang
Assignee: Xi Wang
 Fix For: 3.0.0


Hosts filter:
1. Not aligned with Actions button.
2. Filter dropdown menu, all host filter texts should be same font family as 
other texts
3. Remove icon has shadow, should not

Hosts table:
4. Text in every table row was not centered.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-19312) Improve and Fix "Alerts page" after new guidelines

[Xi Wang (JIRA)]

Xi Wang created AMBARI-19312:


 Summary: Improve and Fix "Alerts page" after new guidelines
 Key: AMBARI-19312
 URL: https://issues.apache.org/jira/browse/AMBARI-19312
 Project: Ambari
  Issue Type: Task
  Components: ambari-web
Affects Versions: 3.0.0
Reporter: Xi Wang
Assignee: Xi Wang
 Fix For: 3.0.0


Alerts Table:
1. Texts not centered every row.
2. Active Filter in each column should not have shadow, no remove icon.

Alert Instance page:
3. Texts not centered every row.





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19308) Non-editable properties should be handled for add/delete host component

[Andrii Babiichuk (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783718#comment-15783718
 ] 

Andrii Babiichuk commented on AMBARI-19308:
---

Committed to trunk

> Non-editable properties should be handled for add/delete host component
> ---
>
> Key: AMBARI-19308
> URL: https://issues.apache.org/jira/browse/AMBARI-19308
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19308_trunk.patch
>
>
> Some properties updated after adding/deleting host component may be 
> read-only. For example, user can edit nimbus.seeds value only before cluster 
> install. Such cases should be handled.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19308) Non-editable properties should be handled for add/delete host component

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783694#comment-15783694
 ] 

Hadoop QA commented on AMBARI-19308:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12844965/AMBARI-19308_trunk.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-web.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9849//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9849//console

This message is automatically generated.

> Non-editable properties should be handled for add/delete host component
> ---
>
> Key: AMBARI-19308
> URL: https://issues.apache.org/jira/browse/AMBARI-19308
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19308_trunk.patch
>
>
> Some properties updated after adding/deleting host component may be 
> read-only. For example, user can edit nimbus.seeds value only before cluster 
> install. Such cases should be handled.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19206) When Namenode HA is enabled, hbase.rootdir property for ambari-metrics (distributed) does not get updated

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-19206:

   Resolution: Fixed
Fix Version/s: trunk
   Status: Resolved  (was: Patch Available)

Committed to branch-2.5 as 
commit eae2a4c5e4b4b5dc279d9553d025fb00eb337849
Author: Sangeeta Ravindran 
Date:   Wed Dec 28 11:25:14 2016 -0800

AMBARI-19206: When Namenode HA is enabled, hbase.rootdir property for 
ambari-metrics (distributed) does not get updated (sangeetar)

and trunk as

commit 540f4ee9ac15d1d1794e8a57db043114dd441dc5
Author: Sangeeta Ravindran 
Date:   Wed Dec 28 11:51:06 2016 -0800

AMBARI-19206: When Namenode HA is enabled, hbase.rootdir property for 
ambari-metrics (distributed) does not get updated (sangeetar)

> When Namenode HA is enabled, hbase.rootdir property for ambari-metrics 
> (distributed) does not get updated
> -
>
> Key: AMBARI-19206
> URL: https://issues.apache.org/jira/browse/AMBARI-19206
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0, 2.4.2
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19206.patch, AMSHbaseRootdirPostNNHAEnabling.jpg, 
> NNHAWizard1.jpg, NNHAWizard2.jpg
>
>
> On a cluster with ambari-metrics in distributed operation mode, enable 
> Namenode HA.
> After HA wizard is run, the amabri-metrics property for hbase.rootdir should 
> point to hdfs://, but it actually still points to the 
> explicit Namenode.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19310) Failed to build Ambari - missed repositories declaration

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783555#comment-15783555
 ] 

Hadoop QA commented on AMBARI-19310:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12844950/add_missing_repos.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9847//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9847//console

This message is automatically generated.

> Failed to build Ambari - missed repositories declaration
> 
>
> Key: AMBARI-19310
> URL: https://issues.apache.org/jira/browse/AMBARI-19310
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-trunk
>Affects Versions: trunk
>Reporter: Dubkov Mikhail
>Priority: Critical
> Attachments: add_missing_repos.patch
>
>
> Hi,
> I'm facing the following error while building Ambari trunk:
> Downloading: 
> https://repository.apache.org/content/repositories/snapshots/org/apache/storm/storm-core/1.1.0-SNAPSHOT/maven-metadata.xml
> Downloading: 
> http://repo.hortonworks.com/content/groups/public/org/apache/storm/storm-core/1.1.0-SNAPSHOT/maven-metadata.xml
> Downloaded: 
> https://repository.apache.org/content/repositories/snapshots/org/apache/storm/storm-core/1.1.0-SNAPSHOT/maven-metadata.xml
>  (3 KB at 2.8 KB/sec)
> Downloading: 
> http://repo.hortonworks.com/content/groups/public/org/apache/storm/storm/1.1.0-SNAPSHOT/maven-metadata.xml
> Downloading: 
> https://repository.apache.org/content/repositories/snapshots/org/apache/storm/storm/1.1.0-SNAPSHOT/maven-metadata.xml
> Downloaded: 
> https://repository.apache.org/content/repositories/snapshots/org/apache/storm/storm/1.1.0-SNAPSHOT/maven-metadata.xml
>  (2 KB at 1.4 KB/sec)
> Downloading: 
> http://repo.hortonworks.com/content/groups/public/ring-cors/ring-cors/0.1.5/ring-cors-0.1.5.pom
> Downloading: 
> https://repository.apache.org/content/repositories/snapshots/ring-cors/ring-cors/0.1.5/ring-cors-0.1.5.pom
> Downloading: 
> https://repo.maven.apache.org/maven2/ring-cors/ring-cors/0.1.5/ring-cors-0.1.5.pom
> [WARNING] The POM for ring-cors:ring-cors:jar:0.1.5 is missing, no dependency 
> information available
> Downloading: 
> http://repo.hortonworks.com/content/groups/public/ring-cors/ring-cors/0.1.5/ring-cors-0.1.5.jar
> Downloading: 
> https://repository.apache.org/content/repositories/snapshots/ring-cors/ring-cors/0.1.5/ring-cors-0.1.5.jar
> Downloading: 
> https://repo.maven.apache.org/maven2/ring-cors/ring-cors/0.1.5/ring-cors-0.1.5.jar
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Ambari Main  SUCCESS [  9.552 
> s]
> [INFO] Apache Ambari Project POM .. SUCCESS [  0.014 
> s]
> [INFO] Ambari Web . SUCCESS [02:02 
> min]
> [INFO] Ambari Views ... SUCCESS [  1.564 
> s]
> [INFO] Ambari Admin View .. SUCCESS [ 12.363 
> s]
> [INFO] utility  SUCCESS [  0.289 
> s]
> [INFO] ambari-metrics . SUCCESS [  0.797 
> s]
> [INFO] Ambari Metrics Common .. SUCCESS [  4.526 
> s]
> [INFO] Ambari Metrics Hadoop Sink . SUCCESS [  3.002 
> s]
> [INFO] Ambari Metrics Flume Sink .. SUCCESS [  1.696 
> s]
> [INFO] Ambari Metrics Kafka Sink .. SUCCESS [  1.647 
> s]
> [INFO] Ambari Metrics Storm Sink .. FAILURE [  4.199 
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) . SKIPPED
> [INFO] Ambari Metrics Collector ... SKIPPED
> [INFO] Ambari Metrics Monitor . SKIPPED
> [INFO] Ambari Metrics Grafana . SKIPPED
> [INFO] Ambari Metrics Assembly 

[jira] [Commented] (AMBARI-19252) Incorrect Method types displayed in the description of created Alert notification

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783536#comment-15783536
 ] 

Hudson commented on AMBARI-19252:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6317 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6317/])
AMBARI-19252. Incorrect Method types displayed in the description of (yusaku: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=69e973c41cb35541ee165372212947c0d8357d6f])
* (edit) 
ambari-web/app/templates/main/alerts/manage_alert_notifications_popup.hbs
* (edit) ambari-web/app/views/main/alerts/manage_alert_notifications_view.js
* (edit) 
ambari-web/app/controllers/main/alerts/manage_alert_notifications_controller.js
* (edit) 
ambari-web/test/controllers/main/alerts/manage_alert_notifications_controller_test.js


> Incorrect Method types displayed in the description of created Alert 
> notification
> -
>
> Key: AMBARI-19252
> URL: https://issues.apache.org/jira/browse/AMBARI-19252
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19252.v0.branch-2.5.patch, 
> AMBARI-19252.v0.trunk.patch
>
>
> Incorrect Method types displayed in the description of created Alert 
> notification.
> STR:
> 1. Create Alert Notifications with Methods "Custom SNMP" and "SNMP"
> 2. After creation, select the created "Custom SNMP" notification the method 
> type is displayed as "SNMP" in the UI
> 3. Select the created "SNMP" notification the method type is displayed as 
> "AMBARI_SNMP" in the UI



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19206) When Namenode HA is enabled, hbase.rootdir property for ambari-metrics (distributed) does not get updated

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783505#comment-15783505
 ] 

Hadoop QA commented on AMBARI-19206:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12844959/AMBARI-19206.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-web.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9846//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9846//console

This message is automatically generated.

> When Namenode HA is enabled, hbase.rootdir property for ambari-metrics 
> (distributed) does not get updated
> -
>
> Key: AMBARI-19206
> URL: https://issues.apache.org/jira/browse/AMBARI-19206
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0, 2.4.2
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Fix For: 2.5.0
>
> Attachments: AMBARI-19206.patch, AMSHbaseRootdirPostNNHAEnabling.jpg, 
> NNHAWizard1.jpg, NNHAWizard2.jpg
>
>
> On a cluster with ambari-metrics in distributed operation mode, enable 
> Namenode HA.
> After HA wizard is run, the amabri-metrics property for hbase.rootdir should 
> point to hdfs://, but it actually still points to the 
> explicit Namenode.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19308) Non-editable properties should be handled for add/delete host component

[Andrii Babiichuk (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783485#comment-15783485
 ] 

Andrii Babiichuk commented on AMBARI-19308:
---

Updated the patch

> Non-editable properties should be handled for add/delete host component
> ---
>
> Key: AMBARI-19308
> URL: https://issues.apache.org/jira/browse/AMBARI-19308
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19308_trunk.patch
>
>
> Some properties updated after adding/deleting host component may be 
> read-only. For example, user can edit nimbus.seeds value only before cluster 
> install. Such cases should be handled.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19308) Non-editable properties should be handled for add/delete host component

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk updated AMBARI-19308:
--
Status: Patch Available  (was: In Progress)

> Non-editable properties should be handled for add/delete host component
> ---
>
> Key: AMBARI-19308
> URL: https://issues.apache.org/jira/browse/AMBARI-19308
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19308_trunk.patch
>
>
> Some properties updated after adding/deleting host component may be 
> read-only. For example, user can edit nimbus.seeds value only before cluster 
> install. Such cases should be handled.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19308) Non-editable properties should be handled for add/delete host component

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk updated AMBARI-19308:
--
Attachment: AMBARI-19308_trunk.patch

> Non-editable properties should be handled for add/delete host component
> ---
>
> Key: AMBARI-19308
> URL: https://issues.apache.org/jira/browse/AMBARI-19308
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19308_trunk.patch
>
>
> Some properties updated after adding/deleting host component may be 
> read-only. For example, user can edit nimbus.seeds value only before cluster 
> install. Such cases should be handled.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19261) AMS cannot start after NN HA is enabled due to hbase.rootdir pointing to Standby NN

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783442#comment-15783442
 ] 

Hudson commented on AMBARI-19261:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #604 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/604/])
AMBARI-19261 : AMS cannot start after NN HA is enabled due to (avijayan: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=dc566c6cc3790761a3abe5e7fe173c1f9ea31f1b])
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java


> AMS cannot start after NN HA is enabled due to hbase.rootdir pointing to 
> Standby NN
> ---
>
> Key: AMBARI-19261
> URL: https://issues.apache.org/jira/browse/AMBARI-19261
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19261-2.patch, AMBARI-19261.patch
>
>
> BUG
> Stack advisor never updates the hbase.rootdir for NN HA deployment.
> So AMS was pointing to standby NN instead of nameservice resulting in :
> {code}
> 2016-12-20 21:43:41,406 WARN  
> [natd77-ipvs-upg-sanity-2220-5:61300.activeMasterManager] 
> retry.RetryInvocationHandler: Exception while invoking 
> ClientNamenodeProtocolTranslatorPB.setSafeMode over null. Not retrying 
> because try once and fail.
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.StandbyException):
>  Operation category READ is not supported in state standby
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19261) AMS cannot start after NN HA is enabled due to hbase.rootdir pointing to Standby NN

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783437#comment-15783437
 ] 

Hudson commented on AMBARI-19261:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6316 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6316/])
AMBARI-19261 : AMS cannot start after NN HA is enabled due to (avijayan: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d1109a5ec1f761bc9cdc990f9c7c3804ff754c74])
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java


> AMS cannot start after NN HA is enabled due to hbase.rootdir pointing to 
> Standby NN
> ---
>
> Key: AMBARI-19261
> URL: https://issues.apache.org/jira/browse/AMBARI-19261
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19261-2.patch, AMBARI-19261.patch
>
>
> BUG
> Stack advisor never updates the hbase.rootdir for NN HA deployment.
> So AMS was pointing to standby NN instead of nameservice resulting in :
> {code}
> 2016-12-20 21:43:41,406 WARN  
> [natd77-ipvs-upg-sanity-2220-5:61300.activeMasterManager] 
> retry.RetryInvocationHandler: Exception while invoking 
> ClientNamenodeProtocolTranslatorPB.setSafeMode over null. Not retrying 
> because try once and fail.
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.StandbyException):
>  Operation category READ is not supported in state standby
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19206) When Namenode HA is enabled, hbase.rootdir property for ambari-metrics (distributed) does not get updated

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-19206:

Status: Patch Available  (was: Open)

> When Namenode HA is enabled, hbase.rootdir property for ambari-metrics 
> (distributed) does not get updated
> -
>
> Key: AMBARI-19206
> URL: https://issues.apache.org/jira/browse/AMBARI-19206
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0, 2.4.2
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Fix For: 2.5.0
>
> Attachments: AMBARI-19206.patch, AMSHbaseRootdirPostNNHAEnabling.jpg, 
> NNHAWizard1.jpg, NNHAWizard2.jpg
>
>
> On a cluster with ambari-metrics in distributed operation mode, enable 
> Namenode HA.
> After HA wizard is run, the amabri-metrics property for hbase.rootdir should 
> point to hdfs://, but it actually still points to the 
> explicit Namenode.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-19311) Port AMBARI-16907 issue to branch 2.5 (issue with yarn.nodemanager.linux-container-executor.cgroups.mount-path)

[Dmytro Grinenko (JIRA)]

Dmytro Grinenko created AMBARI-19311:


 Summary: Port AMBARI-16907 issue to branch 2.5 (issue with 
yarn.nodemanager.linux-container-executor.cgroups.mount-path)
 Key: AMBARI-19311
 URL: https://issues.apache.org/jira/browse/AMBARI-19311
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.5.0
Reporter: Dmytro Grinenko
Assignee: Dmytro Grinenko
Priority: Critical
 Fix For: 2.5.0


Ambari web UI does not auto-set all required properties when user toggles on 
the Yarn CPU isolation feature on the web UI



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19206) When Namenode HA is enabled, hbase.rootdir property for ambari-metrics (distributed) does not get updated

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-19206:

Attachment: AMBARI-19206.patch

> When Namenode HA is enabled, hbase.rootdir property for ambari-metrics 
> (distributed) does not get updated
> -
>
> Key: AMBARI-19206
> URL: https://issues.apache.org/jira/browse/AMBARI-19206
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0, 2.4.2
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Fix For: 2.5.0
>
> Attachments: AMBARI-19206.patch, AMSHbaseRootdirPostNNHAEnabling.jpg, 
> NNHAWizard1.jpg, NNHAWizard2.jpg
>
>
> On a cluster with ambari-metrics in distributed operation mode, enable 
> Namenode HA.
> After HA wizard is run, the amabri-metrics property for hbase.rootdir should 
> point to hdfs://, but it actually still points to the 
> explicit Namenode.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19206) When Namenode HA is enabled, hbase.rootdir property for ambari-metrics (distributed) does not get updated

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-19206:

Attachment: (was: AMBARI-19206.patch)

> When Namenode HA is enabled, hbase.rootdir property for ambari-metrics 
> (distributed) does not get updated
> -
>
> Key: AMBARI-19206
> URL: https://issues.apache.org/jira/browse/AMBARI-19206
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0, 2.4.2
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Fix For: 2.5.0
>
> Attachments: AMSHbaseRootdirPostNNHAEnabling.jpg, NNHAWizard1.jpg, 
> NNHAWizard2.jpg
>
>
> On a cluster with ambari-metrics in distributed operation mode, enable 
> Namenode HA.
> After HA wizard is run, the amabri-metrics property for hbase.rootdir should 
> point to hdfs://, but it actually still points to the 
> explicit Namenode.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19206) When Namenode HA is enabled, hbase.rootdir property for ambari-metrics (distributed) does not get updated

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-19206:

Status: Open  (was: Patch Available)

> When Namenode HA is enabled, hbase.rootdir property for ambari-metrics 
> (distributed) does not get updated
> -
>
> Key: AMBARI-19206
> URL: https://issues.apache.org/jira/browse/AMBARI-19206
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0, 2.4.2
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Fix For: 2.5.0
>
> Attachments: AMSHbaseRootdirPostNNHAEnabling.jpg, NNHAWizard1.jpg, 
> NNHAWizard2.jpg
>
>
> On a cluster with ambari-metrics in distributed operation mode, enable 
> Namenode HA.
> After HA wizard is run, the amabri-metrics property for hbase.rootdir should 
> point to hdfs://, but it actually still points to the 
> explicit Namenode.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19252) Incorrect Method types displayed in the description of created Alert notification

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19252:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to branch-2.5.

> Incorrect Method types displayed in the description of created Alert 
> notification
> -
>
> Key: AMBARI-19252
> URL: https://issues.apache.org/jira/browse/AMBARI-19252
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19252.v0.branch-2.5.patch, 
> AMBARI-19252.v0.trunk.patch
>
>
> Incorrect Method types displayed in the description of created Alert 
> notification.
> STR:
> 1. Create Alert Notifications with Methods "Custom SNMP" and "SNMP"
> 2. After creation, select the created "Custom SNMP" notification the method 
> type is displayed as "SNMP" in the UI
> 3. Select the created "SNMP" notification the method type is displayed as 
> "AMBARI_SNMP" in the UI



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19252) Incorrect Method types displayed in the description of created Alert notification

[Yusaku Sako (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783398#comment-15783398
 ] 

Yusaku Sako commented on AMBARI-19252:
--

+1'd on RB.  Committed to trunk.

> Incorrect Method types displayed in the description of created Alert 
> notification
> -
>
> Key: AMBARI-19252
> URL: https://issues.apache.org/jira/browse/AMBARI-19252
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19252.v0.branch-2.5.patch, 
> AMBARI-19252.v0.trunk.patch
>
>
> Incorrect Method types displayed in the description of created Alert 
> notification.
> STR:
> 1. Create Alert Notifications with Methods "Custom SNMP" and "SNMP"
> 2. After creation, select the created "Custom SNMP" notification the method 
> type is displayed as "SNMP" in the UI
> 3. Select the created "SNMP" notification the method type is displayed as 
> "AMBARI_SNMP" in the UI



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14958) Alerts: Create new Alerts Notification type for SNMP to handle Ambari MIB

[Yusaku Sako (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-14958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783390#comment-15783390
 ] 

Yusaku Sako commented on AMBARI-14958:
--

Committed to branch-2.5.

> Alerts: Create new Alerts Notification type for SNMP to handle Ambari MIB
> -
>
> Key: AMBARI-14958
> URL: https://issues.apache.org/jira/browse/AMBARI-14958
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Vivek Ratnavel Subramanian
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-14958.patch, AMBARI-14958.v0.patch, 
> AMBARI-14958.v1.branch-2.5.patch, AMBARI-14958.v1.trunk.patch
>
>
> 1) Rename current notification type "SNMP" to "Custom SNMP"
> 2) Create a new notification type "SNMP" that prompts for version, community, 
> hosts, ports
> 3) When this is chosen, Ambari under-the-hood generates the SNMP traps based 
> on the MIB.
> 4) The MIB file should be shipped with Ambari.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-14958) Alerts: Create new Alerts Notification type for SNMP to handle Ambari MIB

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-14958:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Alerts: Create new Alerts Notification type for SNMP to handle Ambari MIB
> -
>
> Key: AMBARI-14958
> URL: https://issues.apache.org/jira/browse/AMBARI-14958
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Vivek Ratnavel Subramanian
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-14958.patch, AMBARI-14958.v0.patch, 
> AMBARI-14958.v1.branch-2.5.patch, AMBARI-14958.v1.trunk.patch
>
>
> 1) Rename current notification type "SNMP" to "Custom SNMP"
> 2) Create a new notification type "SNMP" that prompts for version, community, 
> hosts, ports
> 3) When this is chosen, Ambari under-the-hood generates the SNMP traps based 
> on the MIB.
> 4) The MIB file should be shipped with Ambari.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (AMBARI-19261) AMS cannot start after NN HA is enabled due to hbase.rootdir pointing to Standby NN

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan resolved AMBARI-19261.

Resolution: Fixed

Pushed UpgradeCatalog changes to branch-2.5 and trunk.


> AMS cannot start after NN HA is enabled due to hbase.rootdir pointing to 
> Standby NN
> ---
>
> Key: AMBARI-19261
> URL: https://issues.apache.org/jira/browse/AMBARI-19261
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19261-2.patch, AMBARI-19261.patch
>
>
> BUG
> Stack advisor never updates the hbase.rootdir for NN HA deployment.
> So AMS was pointing to standby NN instead of nameservice resulting in :
> {code}
> 2016-12-20 21:43:41,406 WARN  
> [natd77-ipvs-upg-sanity-2220-5:61300.activeMasterManager] 
> retry.RetryInvocationHandler: Exception while invoking 
> ClientNamenodeProtocolTranslatorPB.setSafeMode over null. Not retrying 
> because try once and fail.
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.StandbyException):
>  Operation category READ is not supported in state standby
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19296) When adding service, custom core-site properties get reverted back

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783331#comment-15783331
 ] 

Hudson commented on AMBARI-19296:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #603 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/603/])
AMBARI-19296. When adding service, custom core-site properties get 
(dlysnichenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ebaa0ea79c20702e2e03e1cdf331f8816515fecc])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.1/services/stack_advisor.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py
* (edit) ambari-server/src/test/python/stacks/2.0.6/common/test_stack_advisor.py


> When adding service, custom core-site properties get reverted back
> --
>
> Key: AMBARI-19296
> URL: https://issues.apache.org/jira/browse/AMBARI-19296
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Eugene Chekanskiy
>Assignee: Eugene Chekanskiy
> Fix For: 2.5.0
>
> Attachments: AMBARI-19296-branch-2.5.patch, AMBARI-19296.patch
>
>
> PROBLEM:  When adding a new services like Kafka, Flume, core-site properties 
> reverted.
> The below parameter vaues are changed. 
> hadoop.proxyuser.HTTP.groups 
> hadoop.proxyuser.HTTP.hosts 
> hadoop.proxyuser.knox.groups 
> hadoop.proxyuser.knox.hosts 
> hadoop.proxyuser.HTTP.groups default users we want * it changes to users 
> hadoop.proxyuser.HTTP.hosts it should be three namenodes but it reverts to 
> name2 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19307) UI should validate Ranger user password be more than 8 chars

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783273#comment-15783273
 ] 

Hudson commented on AMBARI-19307:
-

ABORTED: Integrated in Jenkins build Ambari-branch-2.5 #602 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/602/])
AMBARI-19307. UI should validate Ranger user password be more than 8 
(onechiporenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=cf28b98aab7522796ecde08051533a8d38f28369])
* (edit) ambari-web/test/models/configs/objects/service_config_property_test.js
* (edit) ambari-web/app/utils/config.js
* (edit) ambari-web/app/messages.js


> UI should validate Ranger user password be more than 8 chars
> 
>
> Key: AMBARI-19307
> URL: https://issues.apache.org/jira/browse/AMBARI-19307
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19307.patch
>
>
> During Ranger deploy, on config tab, user should set password for admin user. 
> UI do not validate password to be more than 8 characters. As the result, when 
> we will try to create it in Ranger, this user will not be valid (you can't 
> use this name/password to enter Ranger UI). Related alert will show critical 
> message. So, i think it should be fixed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19310) Failed to build Ambari - missed repositories declaration

[Dubkov Mikhail (JIRA)]

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

Dubkov Mikhail updated AMBARI-19310:

Status: Patch Available  (was: Open)

Patch submitted. 

> Failed to build Ambari - missed repositories declaration
> 
>
> Key: AMBARI-19310
> URL: https://issues.apache.org/jira/browse/AMBARI-19310
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-trunk
>Affects Versions: trunk
>Reporter: Dubkov Mikhail
>Priority: Critical
> Attachments: add_missing_repos.patch
>
>
> Hi,
> I'm facing the following error while building Ambari trunk:
> Downloading: 
> https://repository.apache.org/content/repositories/snapshots/org/apache/storm/storm-core/1.1.0-SNAPSHOT/maven-metadata.xml
> Downloading: 
> http://repo.hortonworks.com/content/groups/public/org/apache/storm/storm-core/1.1.0-SNAPSHOT/maven-metadata.xml
> Downloaded: 
> https://repository.apache.org/content/repositories/snapshots/org/apache/storm/storm-core/1.1.0-SNAPSHOT/maven-metadata.xml
>  (3 KB at 2.8 KB/sec)
> Downloading: 
> http://repo.hortonworks.com/content/groups/public/org/apache/storm/storm/1.1.0-SNAPSHOT/maven-metadata.xml
> Downloading: 
> https://repository.apache.org/content/repositories/snapshots/org/apache/storm/storm/1.1.0-SNAPSHOT/maven-metadata.xml
> Downloaded: 
> https://repository.apache.org/content/repositories/snapshots/org/apache/storm/storm/1.1.0-SNAPSHOT/maven-metadata.xml
>  (2 KB at 1.4 KB/sec)
> Downloading: 
> http://repo.hortonworks.com/content/groups/public/ring-cors/ring-cors/0.1.5/ring-cors-0.1.5.pom
> Downloading: 
> https://repository.apache.org/content/repositories/snapshots/ring-cors/ring-cors/0.1.5/ring-cors-0.1.5.pom
> Downloading: 
> https://repo.maven.apache.org/maven2/ring-cors/ring-cors/0.1.5/ring-cors-0.1.5.pom
> [WARNING] The POM for ring-cors:ring-cors:jar:0.1.5 is missing, no dependency 
> information available
> Downloading: 
> http://repo.hortonworks.com/content/groups/public/ring-cors/ring-cors/0.1.5/ring-cors-0.1.5.jar
> Downloading: 
> https://repository.apache.org/content/repositories/snapshots/ring-cors/ring-cors/0.1.5/ring-cors-0.1.5.jar
> Downloading: 
> https://repo.maven.apache.org/maven2/ring-cors/ring-cors/0.1.5/ring-cors-0.1.5.jar
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Ambari Main  SUCCESS [  9.552 
> s]
> [INFO] Apache Ambari Project POM .. SUCCESS [  0.014 
> s]
> [INFO] Ambari Web . SUCCESS [02:02 
> min]
> [INFO] Ambari Views ... SUCCESS [  1.564 
> s]
> [INFO] Ambari Admin View .. SUCCESS [ 12.363 
> s]
> [INFO] utility  SUCCESS [  0.289 
> s]
> [INFO] ambari-metrics . SUCCESS [  0.797 
> s]
> [INFO] Ambari Metrics Common .. SUCCESS [  4.526 
> s]
> [INFO] Ambari Metrics Hadoop Sink . SUCCESS [  3.002 
> s]
> [INFO] Ambari Metrics Flume Sink .. SUCCESS [  1.696 
> s]
> [INFO] Ambari Metrics Kafka Sink .. SUCCESS [  1.647 
> s]
> [INFO] Ambari Metrics Storm Sink .. FAILURE [  4.199 
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) . SKIPPED
> [INFO] Ambari Metrics Collector ... SKIPPED
> [INFO] Ambari Metrics Monitor . SKIPPED
> [INFO] Ambari Metrics Grafana . SKIPPED
> [INFO] Ambari Metrics Assembly  SKIPPED
> [INFO] Ambari Server .. SKIPPED
> [INFO] Ambari Functional Tests  SKIPPED
> [INFO] Ambari Agent ... SKIPPED
> [INFO] Ambari Client .. SKIPPED
> [INFO] Ambari Python Client ... SKIPPED
> [INFO] Ambari Groovy Client ... SKIPPED
> [INFO] Ambari Shell ... SKIPPED
> [INFO] Ambari Python Shell  SKIPPED
> [INFO] Ambari Groovy Shell  SKIPPED
> [INFO] ambari-logsearch ... SKIPPED
> [INFO] Ambari Logsearch Appender .. SKIPPED
> [INFO] Ambari Logsearch Solr Client ... SKIPPED
> [INFO] Ambari Logsearch Portal  SKIPPED
> [INFO] Ambari Logsearch Log Feeder  SKIPPED
> [INFO] Ambari Logsearch Assembly .. SKIPPED
> [INFO] 

[jira] [Updated] (AMBARI-19310) Failed to build Ambari - missed repositories declaration

[Dubkov Mikhail (JIRA)]

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

Dubkov Mikhail updated AMBARI-19310:

Attachment: add_missing_repos.patch

> Failed to build Ambari - missed repositories declaration
> 
>
> Key: AMBARI-19310
> URL: https://issues.apache.org/jira/browse/AMBARI-19310
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-trunk
>Affects Versions: trunk
>Reporter: Dubkov Mikhail
>Priority: Critical
> Attachments: add_missing_repos.patch
>
>
> Hi,
> I'm facing the following error while building Ambari trunk:
> Downloading: 
> https://repository.apache.org/content/repositories/snapshots/org/apache/storm/storm-core/1.1.0-SNAPSHOT/maven-metadata.xml
> Downloading: 
> http://repo.hortonworks.com/content/groups/public/org/apache/storm/storm-core/1.1.0-SNAPSHOT/maven-metadata.xml
> Downloaded: 
> https://repository.apache.org/content/repositories/snapshots/org/apache/storm/storm-core/1.1.0-SNAPSHOT/maven-metadata.xml
>  (3 KB at 2.8 KB/sec)
> Downloading: 
> http://repo.hortonworks.com/content/groups/public/org/apache/storm/storm/1.1.0-SNAPSHOT/maven-metadata.xml
> Downloading: 
> https://repository.apache.org/content/repositories/snapshots/org/apache/storm/storm/1.1.0-SNAPSHOT/maven-metadata.xml
> Downloaded: 
> https://repository.apache.org/content/repositories/snapshots/org/apache/storm/storm/1.1.0-SNAPSHOT/maven-metadata.xml
>  (2 KB at 1.4 KB/sec)
> Downloading: 
> http://repo.hortonworks.com/content/groups/public/ring-cors/ring-cors/0.1.5/ring-cors-0.1.5.pom
> Downloading: 
> https://repository.apache.org/content/repositories/snapshots/ring-cors/ring-cors/0.1.5/ring-cors-0.1.5.pom
> Downloading: 
> https://repo.maven.apache.org/maven2/ring-cors/ring-cors/0.1.5/ring-cors-0.1.5.pom
> [WARNING] The POM for ring-cors:ring-cors:jar:0.1.5 is missing, no dependency 
> information available
> Downloading: 
> http://repo.hortonworks.com/content/groups/public/ring-cors/ring-cors/0.1.5/ring-cors-0.1.5.jar
> Downloading: 
> https://repository.apache.org/content/repositories/snapshots/ring-cors/ring-cors/0.1.5/ring-cors-0.1.5.jar
> Downloading: 
> https://repo.maven.apache.org/maven2/ring-cors/ring-cors/0.1.5/ring-cors-0.1.5.jar
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Ambari Main  SUCCESS [  9.552 
> s]
> [INFO] Apache Ambari Project POM .. SUCCESS [  0.014 
> s]
> [INFO] Ambari Web . SUCCESS [02:02 
> min]
> [INFO] Ambari Views ... SUCCESS [  1.564 
> s]
> [INFO] Ambari Admin View .. SUCCESS [ 12.363 
> s]
> [INFO] utility  SUCCESS [  0.289 
> s]
> [INFO] ambari-metrics . SUCCESS [  0.797 
> s]
> [INFO] Ambari Metrics Common .. SUCCESS [  4.526 
> s]
> [INFO] Ambari Metrics Hadoop Sink . SUCCESS [  3.002 
> s]
> [INFO] Ambari Metrics Flume Sink .. SUCCESS [  1.696 
> s]
> [INFO] Ambari Metrics Kafka Sink .. SUCCESS [  1.647 
> s]
> [INFO] Ambari Metrics Storm Sink .. FAILURE [  4.199 
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) . SKIPPED
> [INFO] Ambari Metrics Collector ... SKIPPED
> [INFO] Ambari Metrics Monitor . SKIPPED
> [INFO] Ambari Metrics Grafana . SKIPPED
> [INFO] Ambari Metrics Assembly  SKIPPED
> [INFO] Ambari Server .. SKIPPED
> [INFO] Ambari Functional Tests  SKIPPED
> [INFO] Ambari Agent ... SKIPPED
> [INFO] Ambari Client .. SKIPPED
> [INFO] Ambari Python Client ... SKIPPED
> [INFO] Ambari Groovy Client ... SKIPPED
> [INFO] Ambari Shell ... SKIPPED
> [INFO] Ambari Python Shell  SKIPPED
> [INFO] Ambari Groovy Shell  SKIPPED
> [INFO] ambari-logsearch ... SKIPPED
> [INFO] Ambari Logsearch Appender .. SKIPPED
> [INFO] Ambari Logsearch Solr Client ... SKIPPED
> [INFO] Ambari Logsearch Portal  SKIPPED
> [INFO] Ambari Logsearch Log Feeder  SKIPPED
> [INFO] Ambari Logsearch Assembly .. SKIPPED
> [INFO] Ambari Logsearch 

[jira] [Created] (AMBARI-19310) Failed to build Ambari - missed repositories declaration

[Dubkov Mikhail (JIRA)]

Dubkov Mikhail created AMBARI-19310:
---

 Summary: Failed to build Ambari - missed repositories declaration
 Key: AMBARI-19310
 URL: https://issues.apache.org/jira/browse/AMBARI-19310
 Project: Ambari
  Issue Type: Bug
  Components: ambari-trunk
Affects Versions: trunk
Reporter: Dubkov Mikhail
Priority: Critical


Hi,

I'm facing the following error while building Ambari trunk:

Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/storm/storm-core/1.1.0-SNAPSHOT/maven-metadata.xml
Downloading: 
http://repo.hortonworks.com/content/groups/public/org/apache/storm/storm-core/1.1.0-SNAPSHOT/maven-metadata.xml
Downloaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/storm/storm-core/1.1.0-SNAPSHOT/maven-metadata.xml
 (3 KB at 2.8 KB/sec)
Downloading: 
http://repo.hortonworks.com/content/groups/public/org/apache/storm/storm/1.1.0-SNAPSHOT/maven-metadata.xml
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/storm/storm/1.1.0-SNAPSHOT/maven-metadata.xml
Downloaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/storm/storm/1.1.0-SNAPSHOT/maven-metadata.xml
 (2 KB at 1.4 KB/sec)
Downloading: 
http://repo.hortonworks.com/content/groups/public/ring-cors/ring-cors/0.1.5/ring-cors-0.1.5.pom
Downloading: 
https://repository.apache.org/content/repositories/snapshots/ring-cors/ring-cors/0.1.5/ring-cors-0.1.5.pom
Downloading: 
https://repo.maven.apache.org/maven2/ring-cors/ring-cors/0.1.5/ring-cors-0.1.5.pom
[WARNING] The POM for ring-cors:ring-cors:jar:0.1.5 is missing, no dependency 
information available
Downloading: 
http://repo.hortonworks.com/content/groups/public/ring-cors/ring-cors/0.1.5/ring-cors-0.1.5.jar
Downloading: 
https://repository.apache.org/content/repositories/snapshots/ring-cors/ring-cors/0.1.5/ring-cors-0.1.5.jar
Downloading: 
https://repo.maven.apache.org/maven2/ring-cors/ring-cors/0.1.5/ring-cors-0.1.5.jar
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Ambari Main  SUCCESS [  9.552 s]
[INFO] Apache Ambari Project POM .. SUCCESS [  0.014 s]
[INFO] Ambari Web . SUCCESS [02:02 min]
[INFO] Ambari Views ... SUCCESS [  1.564 s]
[INFO] Ambari Admin View .. SUCCESS [ 12.363 s]
[INFO] utility  SUCCESS [  0.289 s]
[INFO] ambari-metrics . SUCCESS [  0.797 s]
[INFO] Ambari Metrics Common .. SUCCESS [  4.526 s]
[INFO] Ambari Metrics Hadoop Sink . SUCCESS [  3.002 s]
[INFO] Ambari Metrics Flume Sink .. SUCCESS [  1.696 s]
[INFO] Ambari Metrics Kafka Sink .. SUCCESS [  1.647 s]
[INFO] Ambari Metrics Storm Sink .. FAILURE [  4.199 s]
[INFO] Ambari Metrics Storm Sink (Legacy) . SKIPPED
[INFO] Ambari Metrics Collector ... SKIPPED
[INFO] Ambari Metrics Monitor . SKIPPED
[INFO] Ambari Metrics Grafana . SKIPPED
[INFO] Ambari Metrics Assembly  SKIPPED
[INFO] Ambari Server .. SKIPPED
[INFO] Ambari Functional Tests  SKIPPED
[INFO] Ambari Agent ... SKIPPED
[INFO] Ambari Client .. SKIPPED
[INFO] Ambari Python Client ... SKIPPED
[INFO] Ambari Groovy Client ... SKIPPED
[INFO] Ambari Shell ... SKIPPED
[INFO] Ambari Python Shell  SKIPPED
[INFO] Ambari Groovy Shell  SKIPPED
[INFO] ambari-logsearch ... SKIPPED
[INFO] Ambari Logsearch Appender .. SKIPPED
[INFO] Ambari Logsearch Solr Client ... SKIPPED
[INFO] Ambari Logsearch Portal  SKIPPED
[INFO] Ambari Logsearch Log Feeder  SKIPPED
[INFO] Ambari Logsearch Assembly .. SKIPPED
[INFO] Ambari Logsearch Integration Test .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 02:45 min
[INFO] Finished at: 2016-12-28T18:48:00+02:00
[INFO] Final Memory: 77M/981M
[INFO] 
[ERROR] Failed to execute 

[jira] [Commented] (AMBARI-19305) Improve and Fix "Services page" after new guidelines

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783187#comment-15783187
 ] 

Hadoop QA commented on AMBARI-19305:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12844853/AMBARI-19305.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-web.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9845//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9845//console

This message is automatically generated.

> Improve and Fix "Services page" after new guidelines
> 
>
> Key: AMBARI-19305
> URL: https://issues.apache.org/jira/browse/AMBARI-19305
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 3.0.0
>
> Attachments: AMBARI-19305.patch
>
>
> Create wizard: 
> Step 2:
> The preview should be centered.
> Add Metric submenu, when a metric/operator got selected, the submenu should 
> not disappear. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19308) Non-editable properties should be handled for add/delete host component

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk updated AMBARI-19308:
--
Attachment: (was: AMBARI-19308_trunk.patch)

> Non-editable properties should be handled for add/delete host component
> ---
>
> Key: AMBARI-19308
> URL: https://issues.apache.org/jira/browse/AMBARI-19308
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.5.0
>
>
> Some properties updated after adding/deleting host component may be 
> read-only. For example, user can edit nimbus.seeds value only before cluster 
> install. Such cases should be handled.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19307) UI should validate Ranger user password be more than 8 chars

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783129#comment-15783129
 ] 

Hadoop QA commented on AMBARI-19307:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12844913/AMBARI-19307.patch
  against trunk revision .

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9844//console

This message is automatically generated.

> UI should validate Ranger user password be more than 8 chars
> 
>
> Key: AMBARI-19307
> URL: https://issues.apache.org/jira/browse/AMBARI-19307
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19307.patch
>
>
> During Ranger deploy, on config tab, user should set password for admin user. 
> UI do not validate password to be more than 8 characters. As the result, when 
> we will try to create it in Ranger, this user will not be valid (you can't 
> use this name/password to enter Ranger UI). Related alert will show critical 
> message. So, i think it should be fixed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19309) Stack advisor doesn't recommend distributed mode for AMS HA clusters

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783127#comment-15783127
 ] 

Hadoop QA commented on AMBARI-19309:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12844935/AMBARI-19309.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9843//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9843//console

This message is automatically generated.

> Stack advisor doesn't recommend distributed mode for AMS HA clusters
> 
>
> Key: AMBARI-19309
> URL: https://issues.apache.org/jira/browse/AMBARI-19309
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics, stacks
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19309.patch
>
>
> Start all services fails if AMS collector is installed on more then 1 host 
> with default SA recommendation during initial cluster installation.
> {code}raise Fail("AMS in embedded mode cannot have more than 1 instance. 
> Delete all but 1 instances or switch to Distributed mode ")
> resource_management.core.exceptions.Fail: AMS in embedded mode cannot have 
> more than 1 instance. Delete all but 1 instances or switch to Distributed 
> mode{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19296) When adding service, custom core-site properties get reverted back

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783123#comment-15783123
 ] 

Hudson commented on AMBARI-19296:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6315 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6315/])
AMBARI-19296. When adding service, custom core-site properties get 
(dlysnichenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d84aa3bcb184db60e8d1a68429e1c7abb3fa3646])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.1/services/stack_advisor.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py


> When adding service, custom core-site properties get reverted back
> --
>
> Key: AMBARI-19296
> URL: https://issues.apache.org/jira/browse/AMBARI-19296
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Eugene Chekanskiy
>Assignee: Eugene Chekanskiy
> Fix For: 2.5.0
>
> Attachments: AMBARI-19296-branch-2.5.patch, AMBARI-19296.patch
>
>
> PROBLEM:  When adding a new services like Kafka, Flume, core-site properties 
> reverted.
> The below parameter vaues are changed. 
> hadoop.proxyuser.HTTP.groups 
> hadoop.proxyuser.HTTP.hosts 
> hadoop.proxyuser.knox.groups 
> hadoop.proxyuser.knox.hosts 
> hadoop.proxyuser.HTTP.groups default users we want * it changes to users 
> hadoop.proxyuser.HTTP.hosts it should be three namenodes but it reverts to 
> name2 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19309) Stack advisor doesn't recommend distributed mode for AMS HA clusters

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783056#comment-15783056
 ] 

Hadoop QA commented on AMBARI-19309:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12844935/AMBARI-19309.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9842//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9842//console

This message is automatically generated.

> Stack advisor doesn't recommend distributed mode for AMS HA clusters
> 
>
> Key: AMBARI-19309
> URL: https://issues.apache.org/jira/browse/AMBARI-19309
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics, stacks
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19309.patch
>
>
> Start all services fails if AMS collector is installed on more then 1 host 
> with default SA recommendation during initial cluster installation.
> {code}raise Fail("AMS in embedded mode cannot have more than 1 instance. 
> Delete all but 1 instances or switch to Distributed mode ")
> resource_management.core.exceptions.Fail: AMS in embedded mode cannot have 
> more than 1 instance. Delete all but 1 instances or switch to Distributed 
> mode{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19296) When adding service, custom core-site properties get reverted back

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-19296:

Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed
To https://git-wip-us.apache.org/repos/asf/ambari.git
   cf28b98..ebaa0ea  branch-2.5 -> branch-2.5
   1bfffc0..d84aa3b  trunk -> trunk


> When adding service, custom core-site properties get reverted back
> --
>
> Key: AMBARI-19296
> URL: https://issues.apache.org/jira/browse/AMBARI-19296
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Eugene Chekanskiy
>Assignee: Eugene Chekanskiy
> Fix For: 2.5.0
>
> Attachments: AMBARI-19296-branch-2.5.patch, AMBARI-19296.patch
>
>
> PROBLEM:  When adding a new services like Kafka, Flume, core-site properties 
> reverted.
> The below parameter vaues are changed. 
> hadoop.proxyuser.HTTP.groups 
> hadoop.proxyuser.HTTP.hosts 
> hadoop.proxyuser.knox.groups 
> hadoop.proxyuser.knox.hosts 
> hadoop.proxyuser.HTTP.groups default users we want * it changes to users 
> hadoop.proxyuser.HTTP.hosts it should be three namenodes but it reverts to 
> name2 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19308) Non-editable properties should be handled for add/delete host component

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk updated AMBARI-19308:
--
Status: In Progress  (was: Patch Available)

> Non-editable properties should be handled for add/delete host component
> ---
>
> Key: AMBARI-19308
> URL: https://issues.apache.org/jira/browse/AMBARI-19308
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19308_trunk.patch
>
>
> Some properties updated after adding/deleting host component may be 
> read-only. For example, user can edit nimbus.seeds value only before cluster 
> install. Such cases should be handled.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19308) Non-editable properties should be handled for add/delete host component

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782999#comment-15782999
 ] 

Hadoop QA commented on AMBARI-19308:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12844932/AMBARI-19308_trunk.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-web.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9841//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9841//console

This message is automatically generated.

> Non-editable properties should be handled for add/delete host component
> ---
>
> Key: AMBARI-19308
> URL: https://issues.apache.org/jira/browse/AMBARI-19308
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19308_trunk.patch
>
>
> Some properties updated after adding/deleting host component may be 
> read-only. For example, user can edit nimbus.seeds value only before cluster 
> install. Such cases should be handled.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19309) Stack advisor doesn't recommend distributed mode for AMS HA clusters

[Dmytro Sen (JIRA)]

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

Dmytro Sen updated AMBARI-19309:

Status: Patch Available  (was: Open)

> Stack advisor doesn't recommend distributed mode for AMS HA clusters
> 
>
> Key: AMBARI-19309
> URL: https://issues.apache.org/jira/browse/AMBARI-19309
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics, stacks
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19309.patch
>
>
> Start all services fails if AMS collector is installed on more then 1 host 
> with default SA recommendation during initial cluster installation.
> {code}raise Fail("AMS in embedded mode cannot have more than 1 instance. 
> Delete all but 1 instances or switch to Distributed mode ")
> resource_management.core.exceptions.Fail: AMS in embedded mode cannot have 
> more than 1 instance. Delete all but 1 instances or switch to Distributed 
> mode{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19309) Stack advisor doesn't recommend distributed mode for AMS HA clusters

[Dmytro Sen (JIRA)]

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

Dmytro Sen updated AMBARI-19309:

Attachment: AMBARI-19309.patch

> Stack advisor doesn't recommend distributed mode for AMS HA clusters
> 
>
> Key: AMBARI-19309
> URL: https://issues.apache.org/jira/browse/AMBARI-19309
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics, stacks
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19309.patch
>
>
> Start all services fails if AMS collector is installed on more then 1 host 
> with default SA recommendation during initial cluster installation.
> {code}raise Fail("AMS in embedded mode cannot have more than 1 instance. 
> Delete all but 1 instances or switch to Distributed mode ")
> resource_management.core.exceptions.Fail: AMS in embedded mode cannot have 
> more than 1 instance. Delete all but 1 instances or switch to Distributed 
> mode{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-19309) Stack advisor doesn't recommend distributed mode for AMS HA clusters

[Dmytro Sen (JIRA)]

Dmytro Sen created AMBARI-19309:
---

 Summary: Stack advisor doesn't recommend distributed mode for AMS 
HA clusters
 Key: AMBARI-19309
 URL: https://issues.apache.org/jira/browse/AMBARI-19309
 Project: Ambari
  Issue Type: Bug
  Components: ambari-metrics, stacks
Affects Versions: 2.5.0
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Priority: Critical
 Fix For: 2.5.0


Start all services fails if AMS collector is installed on more then 1 host with 
default SA recommendation during initial cluster installation.
{code}raise Fail("AMS in embedded mode cannot have more than 1 instance. Delete 
all but 1 instances or switch to Distributed mode ")
resource_management.core.exceptions.Fail: AMS in embedded mode cannot have more 
than 1 instance. Delete all but 1 instances or switch to Distributed mode{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19308) Non-editable properties should be handled for add/delete host component

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk updated AMBARI-19308:
--
Status: Patch Available  (was: Open)

> Non-editable properties should be handled for add/delete host component
> ---
>
> Key: AMBARI-19308
> URL: https://issues.apache.org/jira/browse/AMBARI-19308
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19308_trunk.patch
>
>
> Some properties updated after adding/deleting host component may be 
> read-only. For example, user can edit nimbus.seeds value only before cluster 
> install. Such cases should be handled.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19308) Non-editable properties should be handled for add/delete host component

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk updated AMBARI-19308:
--
Attachment: AMBARI-19308_trunk.patch

> Non-editable properties should be handled for add/delete host component
> ---
>
> Key: AMBARI-19308
> URL: https://issues.apache.org/jira/browse/AMBARI-19308
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19308_trunk.patch
>
>
> Some properties updated after adding/deleting host component may be 
> read-only. For example, user can edit nimbus.seeds value only before cluster 
> install. Such cases should be handled.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19307) UI should validate Ranger user password be more than 8 chars

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782911#comment-15782911
 ] 

Hudson commented on AMBARI-19307:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6314 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6314/])
AMBARI-19307. UI should validate Ranger user password be more than 8 
(onechiporenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1bfffc0c8f231b583dc259c4d4e3fd91079aec0b])
* (edit) ambari-web/app/utils/config.js
* (edit) ambari-web/test/models/configs/objects/service_config_property_test.js
* (edit) ambari-web/app/messages.js


> UI should validate Ranger user password be more than 8 chars
> 
>
> Key: AMBARI-19307
> URL: https://issues.apache.org/jira/browse/AMBARI-19307
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19307.patch
>
>
> During Ranger deploy, on config tab, user should set password for admin user. 
> UI do not validate password to be more than 8 characters. As the result, when 
> we will try to create it in Ranger, this user will not be valid (you can't 
> use this name/password to enter Ranger UI). Related alert will show critical 
> message. So, i think it should be fixed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-19308) Non-editable properties should be handled for add/delete host component

[Andrii Babiichuk (JIRA)]

Andrii Babiichuk created AMBARI-19308:
-

 Summary: Non-editable properties should be handled for add/delete 
host component
 Key: AMBARI-19308
 URL: https://issues.apache.org/jira/browse/AMBARI-19308
 Project: Ambari
  Issue Type: Task
  Components: ambari-web
Affects Versions: 2.5.0
Reporter: Andrii Babiichuk
Assignee: Andrii Babiichuk
Priority: Critical
 Fix For: 2.5.0


Some properties updated after adding/deleting host component may be read-only. 
For example, user can edit nimbus.seeds value only before cluster install. Such 
cases should be handled.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19307) UI should validate Ranger user password be more than 8 chars

[Oleg Nechiporenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782851#comment-15782851
 ] 

Oleg Nechiporenko commented on AMBARI-19307:


Committed to trunk and 2.5

> UI should validate Ranger user password be more than 8 chars
> 
>
> Key: AMBARI-19307
> URL: https://issues.apache.org/jira/browse/AMBARI-19307
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19307.patch
>
>
> During Ranger deploy, on config tab, user should set password for admin user. 
> UI do not validate password to be more than 8 characters. As the result, when 
> we will try to create it in Ranger, this user will not be valid (you can't 
> use this name/password to enter Ranger UI). Related alert will show critical 
> message. So, i think it should be fixed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19296) When adding service, custom core-site properties get reverted back

[Eugene Chekanskiy (JIRA)]

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

Eugene Chekanskiy updated AMBARI-19296:
---
Attachment: AMBARI-19296-branch-2.5.patch

> When adding service, custom core-site properties get reverted back
> --
>
> Key: AMBARI-19296
> URL: https://issues.apache.org/jira/browse/AMBARI-19296
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Eugene Chekanskiy
>Assignee: Eugene Chekanskiy
> Fix For: 2.5.0
>
> Attachments: AMBARI-19296-branch-2.5.patch, AMBARI-19296.patch
>
>
> PROBLEM:  When adding a new services like Kafka, Flume, core-site properties 
> reverted.
> The below parameter vaues are changed. 
> hadoop.proxyuser.HTTP.groups 
> hadoop.proxyuser.HTTP.hosts 
> hadoop.proxyuser.knox.groups 
> hadoop.proxyuser.knox.hosts 
> hadoop.proxyuser.HTTP.groups default users we want * it changes to users 
> hadoop.proxyuser.HTTP.hosts it should be three namenodes but it reverts to 
> name2 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19307) UI should validate Ranger user password be more than 8 chars

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782674#comment-15782674
 ] 

Hadoop QA commented on AMBARI-19307:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12844913/AMBARI-19307.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-web.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9840//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9840//console

This message is automatically generated.

> UI should validate Ranger user password be more than 8 chars
> 
>
> Key: AMBARI-19307
> URL: https://issues.apache.org/jira/browse/AMBARI-19307
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19307.patch
>
>
> During Ranger deploy, on config tab, user should set password for admin user. 
> UI do not validate password to be more than 8 characters. As the result, when 
> we will try to create it in Ranger, this user will not be valid (you can't 
> use this name/password to enter Ranger UI). Related alert will show critical 
> message. So, i think it should be fixed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19307) UI should validate Ranger user password be more than 8 chars

[Oleg Nechiporenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782620#comment-15782620
 ] 

Oleg Nechiporenko commented on AMBARI-19307:


+1 by [~atkach] on the review board

> UI should validate Ranger user password be more than 8 chars
> 
>
> Key: AMBARI-19307
> URL: https://issues.apache.org/jira/browse/AMBARI-19307
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19307.patch
>
>
> During Ranger deploy, on config tab, user should set password for admin user. 
> UI do not validate password to be more than 8 characters. As the result, when 
> we will try to create it in Ranger, this user will not be valid (you can't 
> use this name/password to enter Ranger UI). Related alert will show critical 
> message. So, i think it should be fixed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19307) UI should validate Ranger user password be more than 8 chars

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko updated AMBARI-19307:
---
Status: Patch Available  (was: Open)

> UI should validate Ranger user password be more than 8 chars
> 
>
> Key: AMBARI-19307
> URL: https://issues.apache.org/jira/browse/AMBARI-19307
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19307.patch
>
>
> During Ranger deploy, on config tab, user should set password for admin user. 
> UI do not validate password to be more than 8 characters. As the result, when 
> we will try to create it in Ranger, this user will not be valid (you can't 
> use this name/password to enter Ranger UI). Related alert will show critical 
> message. So, i think it should be fixed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19307) UI should validate Ranger user password be more than 8 chars

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko updated AMBARI-19307:
---
Attachment: AMBARI-19307.patch

> UI should validate Ranger user password be more than 8 chars
> 
>
> Key: AMBARI-19307
> URL: https://issues.apache.org/jira/browse/AMBARI-19307
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19307.patch
>
>
> During Ranger deploy, on config tab, user should set password for admin user. 
> UI do not validate password to be more than 8 characters. As the result, when 
> we will try to create it in Ranger, this user will not be valid (you can't 
> use this name/password to enter Ranger UI). Related alert will show critical 
> message. So, i think it should be fixed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-19307) UI should validate Ranger user password be more than 8 chars

[Oleg Nechiporenko (JIRA)]

Oleg Nechiporenko created AMBARI-19307:
--

 Summary: UI should validate Ranger user password be more than 8 
chars
 Key: AMBARI-19307
 URL: https://issues.apache.org/jira/browse/AMBARI-19307
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.5.0
Reporter: Oleg Nechiporenko
Assignee: Oleg Nechiporenko
Priority: Critical
 Fix For: 2.5.0


During Ranger deploy, on config tab, user should set password for admin user. 
UI do not validate password to be more than 8 characters. As the result, when 
we will try to create it in Ranger, this user will not be valid (you can't use 
this name/password to enter Ranger UI). Related alert will show critical 
message. So, i think it should be fixed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19301) JS-error on the Host details page

[Oleg Nechiporenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782589#comment-15782589
 ] 

Oleg Nechiporenko commented on AMBARI-19301:


Build failed not because of this patch
{noformat}
[INFO] Ambari Web . SUCCESS [03:43 min]
[INFO] Ambari Server .. FAILURE [15:59 min]
{noformat}

> JS-error on the Host details page
> -
>
> Key: AMBARI-19301
> URL: https://issues.apache.org/jira/browse/AMBARI-19301
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-19301.patch
>
>
> Fast switching tabs on the host details (summary, alerts, versions) causes JS 
> error



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19301) JS-error on the Host details page

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko updated AMBARI-19301:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> JS-error on the Host details page
> -
>
> Key: AMBARI-19301
> URL: https://issues.apache.org/jira/browse/AMBARI-19301
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-19301.patch
>
>
> Fast switching tabs on the host details (summary, alerts, versions) causes JS 
> error



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19302) Remove hive view 1.0

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782586#comment-15782586
 ] 

Hudson commented on AMBARI-19302:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6313 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6313/])
AMBARI-19302 : removed contrib/views/hive folder and made necessary 
(nitiraj.rathore: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e423a65e5deca78d8068216a273d9d89d37756c9])
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/tests/unit/components/tabs-wiget-test.js
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/app/templates/visualization-ui.hbs
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/udfs/UDFResourceProvider.java
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/uploads/parsers/DataParser.java
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/HelpService.java
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/jobs/ModifyNotificationInvocationHandler.java
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/jobs/rm/RMRequestsDelegateImpl.java
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/app/controllers/history.js
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/uploads/parsers/ParseUtils.java
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/persistence/utils/ItemNotFound.java
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/uploads/query/DeleteQueryInput.java
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/uploads/parsers/EndOfDocumentException.java
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/jobs/viewJobs/JobController.java
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/uploads/CSVParams.java
* (delete) contrib/views/hive/src/main/resources/ui/hive-web/big_tables.js
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/app/routes/index/index.js
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/app/controllers/index/history-query/logs.js
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/persistence/utils/OnlyOwnersFilteringStrategy.java
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/TestBean.java
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/tests/unit/components/query-editor-test.js
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/app/components/popover-widget.js
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/app/services/ldap-authentication.js
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/app/components/modal-widget.js
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/client/ConnectionFactory.java
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/tests/unit/components/typeahead-widget-test.js
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/vendor/codemirror/sql-hint.js
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/client/ColumnDescriptionShort.java
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/app/routes/loading.js
* (delete) contrib/views/hive/src/main/resources/ui/hive-web/app/models/udf.js
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/app/views/notification.js
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/jobs/atsJobs/ATSRequestsDelegate.java
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/app/controllers/messages.js
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/app/serializers/database.js
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/app/components/collapsible-widget.js
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/utils/NotFoundFormattedException.java
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/jobs/ConnectionController.java
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/app/models/database.js
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/app/transforms/date.js
* (delete) 
contrib/views/hive/src/test/java/org/apache/ambari/view/hive/HDFSTest.java
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/tests/unit/components/expander-widget-test.js
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/tests/unit/controllers/open-queries-test.js
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/app/templates/index/history-query/explain.hbs
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/udfs/UDFResourceManager.java
* (delete) 

[jira] [Commented] (AMBARI-19301) JS-error on the Host details page

[Oleg Nechiporenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782588#comment-15782588
 ] 

Oleg Nechiporenko commented on AMBARI-19301:


Patch was already committed

> JS-error on the Host details page
> -
>
> Key: AMBARI-19301
> URL: https://issues.apache.org/jira/browse/AMBARI-19301
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-19301.patch
>
>
> Fast switching tabs on the host details (summary, alerts, versions) causes JS 
> error



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19302) Remove hive view 1.0

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782570#comment-15782570
 ] 

Hudson commented on AMBARI-19302:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #601 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/601/])
AMBARI-19302 : removed contrib/views/hive folder and made necessary 
(nitiraj.rathore: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c0f9621f2008aff2b71a7e7075c8e13cea05db87])
* (delete) 
contrib/views/hive/src/test/java/org/apache/ambari/view/hive/resources/savedQueries/SavedQueryResourceManagerTest.java
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/jobs/IOperationHandleResourceManager.java
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/uploads/parsers/ParseOptions.java
* (delete) 
contrib/views/hive/src/test/java/org/apache/ambari/view/hive/BaseHiveTest.java
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/TestBean.java
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/jobs/OperationHandleControllerFactory.java
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/client/ColumnDescriptionShort.java
* (delete) 
contrib/views/hive/src/test/java/org/apache/ambari/view/hive/resources/upload/DataParserCSVTest.java
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/utils/MisconfigurationFormattedException.java
* (delete) contrib/views/hive/pom.xml
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/tests/unit/controllers/settings-test.js
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/tests/unit/services/notify-test.js
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/tests/unit/components/number-range-widget-test.js
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/SharedCRUDResourceManager.java
* (delete) 
contrib/views/hive/src/test/java/org/apache/ambari/view/hive/client/UtilsTest.java
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/client/HttpRequestInterceptorBase.java
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/app/components/collapsible-widget.js
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/app/components/modal-widget.js
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/uploads/query/LoadQueryInput.java
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/app/components/tabs-widget.js
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/app/controllers/visualization-ui.js
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/client/UserLocalConnection.java
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/udfs/UDFService.java
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/app/controllers/databases.js
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/app/templates/components/column-filter-widget.hbs
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/app/templates/notification.hbs
* (delete) contrib/views/hive/src/main/resources/ui/hive-web/app/models/.gitkeep
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/jobs/Aggregator.java
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/resources/FileResourceResourceManager.java
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/app/templates/.gitkeep
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/persistence/utils/Owned.java
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/client/HiveClientException.java
* (delete) contrib/views/hive/src/main/resources/ui/hive-web/README.md
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/app/views/visual-explain.js
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/app/services/file.js
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/tests/helpers/start-app.js
* (delete) 
contrib/views/hive/src/test/java/org/apache/ambari/view/hive/resources/upload/JsonParserTest.java
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/HiveViewImpl.java
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/uploads/parsers/json/JSONIterator.java
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/app/transforms/date.js
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/app/routes/index/history-query/results.js
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/app/components/udf-tr-view.js
* (delete) 
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/uploads/ColumnDescriptionImpl.java
* (delete) 
contrib/views/hive/src/main/resources/ui/hive-web/tests/unit/components/tabs-wiget-test.js
* 

[jira] [Resolved] (AMBARI-19302) Remove hive view 1.0

[Pallav Kulshreshtha (JIRA)]

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

Pallav Kulshreshtha resolved AMBARI-19302.
--
Resolution: Fixed

Committed to trunk and branch-2.5

> Remove hive view 1.0
> 
>
> Key: AMBARI-19302
> URL: https://issues.apache.org/jira/browse/AMBARI-19302
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Nitiraj Singh Rathore
>Assignee: Nitiraj Singh Rathore
> Fix For: 2.5.0
>
> Attachments: AMBARI-19302_branch-2.5.patch
>
>
> Hive 1.0 needs to be removed from Ambari Views in the 2.5 release. Need to 
> remove the codes from the following places:
> dir: /contrib/views/hive
> file: /contrib/views/pom.xml
> file: /pom.xml
> This is because new version of hive view will be introduced and only that 
> will be maintained from now on.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)