[jira] [Commented] (AMBARI-23066) Freeze the hostname column in Assign Slaves/Clients page (Install and Add Service Wizards)

[Hudson (JIRA)]

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

Hudson commented on AMBARI-23066:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8778 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/8778/])
[AMBARI-23066] Freeze the hostname column in Assign Slaves/Clients page 
(github: 
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=8b8c832d8edff102407ff4273eca28053ed1d750])
* (edit) ambari-web/app/views/wizard/step6_view.js
* (edit) ambari-web/app/templates/wizard/step6.hbs
* (edit) ambari-web/app/controllers/wizard/step6_controller.js
* (edit) ambari-web/app/styles/wizard.less


> Freeze the hostname column in Assign Slaves/Clients page (Install and Add 
> Service Wizards)
> --
>
> Key: AMBARI-23066
> URL: https://issues.apache.org/jira/browse/AMBARI-23066
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: trunk
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
>Priority: Major
>  Labels: pull-request-available
> Fix For: trunk
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> we just want to freeze the hostname column so that when the user scrolls 
> horizontally, the hostname column remains in place. 



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

[jira] [Commented] (AMBARI-23043) 'Table or view not found error' with livy/livy2 interpreter on upgraded cluster to Fenton-M30

[Hudson (JIRA)]

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

Hudson commented on AMBARI-23043:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8778 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/8778/])
[AMBARI-23043] "Table or view not found error" with livy/livy2 (github: 
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=2cbb34854ef4fdd7fdacfd105ce830008cdd8d66])
* (edit) 
ambari-server/src/test/python/stacks/2.6/ZEPPELIN/interpreter_json_generated.py


> 'Table or view not found error' with livy/livy2 interpreter on upgraded 
> cluster to Fenton-M30
> -
>
> Key: AMBARI-23043
> URL: https://issues.apache.org/jira/browse/AMBARI-23043
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.6.2
>
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> The test has been performed as below:
> CentOS6 + Ambari-2.5.1 + HDP-2.6.1 -> AU to Ambari-2.6.2 -> Full EU to 
> HDP-2.6.5.0-74 (Fenton-M30) -> Run stack tests
> I see that with livy2 interpreter, anytime we register a temporary view or 
> table - the corresponding query on that table will fail with 'Table or view 
> not found error'
> {code:java}
> org.apache.spark.sql.AnalysisException: Table or view not found: word_counts; 
> line 2 pos 24
>  at 
> org.apache.spark.sql.catalyst.analysis.package$AnalysisErrorAt.failAnalysis(package.scala:42)
>  at 
> org.apache.spark.sql.catalyst.analysis.Analyzer$ResolveRelations$.org$apache$spark$sql$catalyst$analysis$Analyzer$ResolveRelations$$lookupTableFromCatalog(Analyzer.scala:649)
>  at 
> org.apache.spark.sql.catalyst.analysis.Analyzer$ResolveRelations$.resolveRelation(Analyzer.scala:601)
>  at 
> org.apache.spark.sql.catalyst.analysis.Analyzer$ResolveRelations$$anonfun$apply$8.applyOrElse(Analyzer.scala:631)
>  at 
> org.apache.spark.sql.catalyst.analysis.Analyzer$ResolveRelations$$anonfun$apply$8.applyOrElse(Analyzer.scala:624)
>  at 
> org.apache.spark.sql.catalyst.plans.logical.LogicalPlan$$anonfun$resolveOperators$1.apply(LogicalPlan.scala:62)
>  at 
> org.apache.spark.sql.catalyst.plans.logical.LogicalPlan$$anonfun$resolveOperators$1.apply(LogicalPlan.scala:62)
>  at 
> org.apache.spark.sql.catalyst.trees.CurrentOrigin$.withOrigin(TreeNode.scala:70)
>  at 
> org.apache.spark.sql.catalyst.plans.logical.LogicalPlan.resolveOperators(LogicalPlan.scala:61)
>  at 
> org.apache.spark.sql.catalyst.plans.logical.LogicalPlan$$anonfun$1.apply(LogicalPlan.scala:59)
>  at 
> org.apache.spark.sql.catalyst.plans.logical.LogicalPlan$$anonfun$1.apply(LogicalPlan.scala:59)
>  at 
> org.apache.spark.sql.catalyst.trees.TreeNode$$anonfun$4.apply(TreeNode.scala:306)
>  at 
> org.apache.spark.sql.catalyst.trees.TreeNode.mapProductIterator(TreeNode.scala:187)
>  at 
> org.apache.spark.sql.catalyst.trees.TreeNode.mapChildren(TreeNode.scala:304)
>  at 
> org.apache.spark.sql.catalyst.plans.logical.LogicalPlan.resolveOperators(LogicalPlan.scala:59)
>  at 
> org.apache.spark.sql.catalyst.plans.logical.LogicalPlan$$anonfun$1.apply(LogicalPlan.scala:59)
>  at 
> org.apache.spark.sql.catalyst.plans.logical.LogicalPlan$$anonfun$1.apply(LogicalPlan.scala:59)
>  at 
> org.apache.spark.sql.catalyst.trees.TreeNode$$anonfun$4.apply(TreeNode.scala:306)
>  at 
> org.apache.spark.sql.catalyst.trees.TreeNode.mapProductIterator(TreeNode.scala:187)
>  at 
> org.apache.spark.sql.catalyst.trees.TreeNode.mapChildren(TreeNode.scala:304)
>  at 
> org.apache.spark.sql.catalyst.plans.logical.LogicalPlan.resolveOperators(LogicalPlan.scala:59)
>  at 
> org.apache.spark.sql.catalyst.analysis.Analyzer$ResolveRelations$.apply(Analyzer.scala:624)
>  at 
> org.apache.spark.sql.catalyst.analysis.Analyzer$ResolveRelations$.apply(Analyzer.scala:570)
>  at 
> org.apache.spark.sql.catalyst.rules.RuleExecutor$$anonfun$execute$1$$anonfun$apply$1.apply(RuleExecutor.scala:85)
>  at 
> org.apache.spark.sql.catalyst.rules.RuleExecutor$$anonfun$execute$1$$anonfun$apply$1.apply(RuleExecutor.scala:82)
>  at 
> scala.collection.LinearSeqOptimized$class.foldLeft(LinearSeqOptimized.scala:124)
>  at scala.collection.immutable.List.foldLeft(List.scala:84)
>  at 
> org.apache.spark.sql.catalyst.rules.RuleExecutor$$anonfun$execute$1.apply(RuleExecutor.scala:82)
>  at 
> org.apache.spark.sql.catalyst.rules.RuleExecutor$$anonfun$execute$1.apply(RuleExecutor.scala:74)
>  at scala.collection.immutable.List.foreach(List.scala:381)
>  at 
> org.apache.spark.sql.catalyst.rules.RuleExecutor.execute(RuleExecutor.scala:74)
>  at 
> 

[jira] [Updated] (AMBARI-23079) Log Feeder: support to use load balancer for Solr API (not only cloud client)

[JIRA]

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

Olivér Szabó updated AMBARI-23079:
--
Component/s: ambari-logsearch

> Log Feeder: support to use load balancer for Solr API (not only cloud client) 
> --
>
> Key: AMBARI-23079
> URL: https://issues.apache.org/jira/browse/AMBARI-23079
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
> Fix For: 2.7.0
>
>




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

[jira] [Created] (AMBARI-23079) Log Feeder: support to use load balancer for Solr API (not only cloud client)

[JIRA]

Olivér Szabó created AMBARI-23079:
-

 Summary: Log Feeder: support to use load balancer for Solr API 
(not only cloud client) 
 Key: AMBARI-23079
 URL: https://issues.apache.org/jira/browse/AMBARI-23079
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.7.0
Reporter: Olivér Szabó
Assignee: Olivér Szabó
 Fix For: 2.7.0






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

[jira] [Created] (AMBARI-23080) Log Search: use comositeId instead of implicit routing by default for collections

[JIRA]

Olivér Szabó created AMBARI-23080:
-

 Summary: Log Search: use comositeId instead of implicit routing by 
default for collections
 Key: AMBARI-23080
 URL: https://issues.apache.org/jira/browse/AMBARI-23080
 Project: Ambari
  Issue Type: Bug
  Components: ambari-logsearch
Affects Versions: 2.7.0
Reporter: Olivér Szabó
Assignee: Olivér Szabó
 Fix For: 2.7.0






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

[jira] [Commented] (AMBARI-23069) Wrong reference in params.py files for zookeeper hosts

[Hudson (JIRA)]

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

Hudson commented on AMBARI-23069:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8777 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/8777/])
[AMBARI-23069] Wrong reference in params.py files for zookeeper hosts (github: 
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=7c1f557827332c340ce5161083ade8654bcd6c38])
* (edit) 
ambari-server/src/main/resources/common-services/FLUME/1.4.0.2.0/package/scripts/params.py
* (edit) 
ambari-server/src/main/resources/stack-hooks/before-START/scripts/params.py
* (edit) 
ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/package/scripts/params.py
* (edit) 
ambari-server/src/main/resources/stack-hooks/before-INSTALL/scripts/params.py
* (edit) 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/ZOOKEEPER/package/scripts/params.py
* (edit) 
ambari-server/src/main/resources/stacks/HDPWIN/2.1/hooks/after-INSTALL/scripts/params.py
* (edit) 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-START/scripts/params.py
* (edit) 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-INSTALL/scripts/params.py


> Wrong reference in params.py files for zookeeper hosts
> --
>
> Key: AMBARI-23069
> URL: https://issues.apache.org/jira/browse/AMBARI-23069
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Blocker
>  Labels: pull-request-available, quickfix
> Fix For: 2.7.0
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>




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

[jira] [Created] (AMBARI-23078) Log Search: redesign Solr schema (service/audits) - use better types

[JIRA]

Olivér Szabó created AMBARI-23078:
-

 Summary: Log Search: redesign Solr schema (service/audits) - use 
better types
 Key: AMBARI-23078
 URL: https://issues.apache.org/jira/browse/AMBARI-23078
 Project: Ambari
  Issue Type: Bug
  Components: ambari-logsearch
Affects Versions: 2.7.0
Reporter: Olivér Szabó
Assignee: Olivér Szabó
 Fix For: 2.7.0






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

[jira] [Created] (AMBARI-23077) LogFeeder: create socket input

[JIRA]

Olivér Szabó created AMBARI-23077:
-

 Summary: LogFeeder: create socket input
 Key: AMBARI-23077
 URL: https://issues.apache.org/jira/browse/AMBARI-23077
 Project: Ambari
  Issue Type: Bug
  Components: ambari-logsearch
Affects Versions: 2.7.0
Reporter: Olivér Szabó
Assignee: Olivér Szabó
 Fix For: 2.7.0






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

[jira] [Assigned] (AMBARI-23076) Log Search configurable zookeeper usage for config API (zookeeper implementation)

[JIRA]

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

Olivér Szabó reassigned AMBARI-23076:
-

Assignee: Olivér Szabó

> Log Search configurable zookeeper usage for config API (zookeeper 
> implementation)
> -
>
> Key: AMBARI-23076
> URL: https://issues.apache.org/jira/browse/AMBARI-23076
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
> Fix For: 2.7.0
>
>




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

[jira] [Created] (AMBARI-23076) Log Search configurable zookeeper usage for config API (zookeeper implementation)

[JIRA]

Olivér Szabó created AMBARI-23076:
-

 Summary: Log Search configurable zookeeper usage for config API 
(zookeeper implementation)
 Key: AMBARI-23076
 URL: https://issues.apache.org/jira/browse/AMBARI-23076
 Project: Ambari
  Issue Type: Bug
  Components: ambari-logsearch
Affects Versions: 2.7.0
Reporter: Olivér Szabó
 Fix For: 2.7.0






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

[jira] [Created] (AMBARI-23075) Log Search: Zookeeper tick time is too low for Config API

[JIRA]

Olivér Szabó created AMBARI-23075:
-

 Summary: Log Search: Zookeeper tick time is too low for Config API
 Key: AMBARI-23075
 URL: https://issues.apache.org/jira/browse/AMBARI-23075
 Project: Ambari
  Issue Type: Bug
  Components: ambari-logsearch
Affects Versions: 2.7.0
Reporter: Olivér Szabó
Assignee: Olivér Szabó
 Fix For: 2.7.0






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

[jira] [Created] (AMBARI-23074) Change the default datadir for Infra Solr

[JIRA]

Olivér Szabó created AMBARI-23074:
-

 Summary: Change the default datadir for Infra Solr
 Key: AMBARI-23074
 URL: https://issues.apache.org/jira/browse/AMBARI-23074
 Project: Ambari
  Issue Type: Bug
  Components: ambari-infra, ambari-server
Affects Versions: 2.7.0
Reporter: Olivér Szabó
Assignee: Olivér Szabó
 Fix For: 2.7.0






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

[jira] [Created] (AMBARI-23073) Create custom commands for upgrade and backup Solr collections

[JIRA]

Olivér Szabó created AMBARI-23073:
-

 Summary: Create custom commands for upgrade and backup Solr 
collections
 Key: AMBARI-23073
 URL: https://issues.apache.org/jira/browse/AMBARI-23073
 Project: Ambari
  Issue Type: Bug
  Components: ambari-infra, ambari-server
Affects Versions: 2.7.0
Reporter: Olivér Szabó
Assignee: Olivér Szabó
 Fix For: 2.7.0






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

[jira] [Updated] (AMBARI-23072) Handle some configs moved

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-23072:
-
Attachment: AMBARI-23072.patch

> Handle some configs moved
> -
>
> Key: AMBARI-23072
> URL: https://issues.apache.org/jira/browse/AMBARI-23072
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-23072.patch, AMBARI-23072.patch, 
> AMBARI-23072.patch
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




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

[jira] [Updated] (AMBARI-23069) Wrong reference in params.py files for zookeeper hosts

[JIRA]

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

Olivér Szabó updated AMBARI-23069:
--
Labels: pull-request-available quickfix  (was: pull-request-available)

> Wrong reference in params.py files for zookeeper hosts
> --
>
> Key: AMBARI-23069
> URL: https://issues.apache.org/jira/browse/AMBARI-23069
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Blocker
>  Labels: pull-request-available, quickfix
> Fix For: 2.7.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>




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

[jira] [Updated] (AMBARI-23072) Handle some configs moved

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-23072:
-
Attachment: AMBARI-23072.patch

> Handle some configs moved
> -
>
> Key: AMBARI-23072
> URL: https://issues.apache.org/jira/browse/AMBARI-23072
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-23072.patch, AMBARI-23072.patch
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




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

[jira] [Updated] (AMBARI-23072) Handle some configs moved

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-23072:
-
Attachment: AMBARI-23072.patch

> Handle some configs moved
> -
>
> Key: AMBARI-23072
> URL: https://issues.apache.org/jira/browse/AMBARI-23072
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-23072.patch, AMBARI-23072.patch
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




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

[jira] [Updated] (AMBARI-23072) Handle some configs moved

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-23072:
-
Attachment: (was: AMBARI-23072.patch)

> Handle some configs moved
> -
>
> Key: AMBARI-23072
> URL: https://issues.apache.org/jira/browse/AMBARI-23072
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




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

[jira] [Updated] (AMBARI-23072) Handle some configs moved

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot updated AMBARI-23072:

Labels: pull-request-available  (was: )

> Handle some configs moved
> -
>
> Key: AMBARI-23072
> URL: https://issues.apache.org/jira/browse/AMBARI-23072
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-23072.patch
>
>




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

[jira] [Created] (AMBARI-23072) Handle some configs moved

[Andrew Onischuk (JIRA)]

Andrew Onischuk created AMBARI-23072:


 Summary: Handle some configs moved
 Key: AMBARI-23072
 URL: https://issues.apache.org/jira/browse/AMBARI-23072
 Project: Ambari
  Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
 Fix For: 2.7.0
 Attachments: AMBARI-23072.patch





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

[jira] [Updated] (AMBARI-23072) Handle some configs moved

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-23072:
-
Attachment: AMBARI-23072.patch

> Handle some configs moved
> -
>
> Key: AMBARI-23072
> URL: https://issues.apache.org/jira/browse/AMBARI-23072
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Fix For: 2.7.0
>
> Attachments: AMBARI-23072.patch
>
>




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

[jira] [Updated] (AMBARI-23072) Handle some configs moved

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-23072:
-
Status: Patch Available  (was: Open)

> Handle some configs moved
> -
>
> Key: AMBARI-23072
> URL: https://issues.apache.org/jira/browse/AMBARI-23072
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Fix For: 2.7.0
>
> Attachments: AMBARI-23072.patch
>
>




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

[jira] [Updated] (AMBARI-23071) Handle some configs moved

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-23071:
-
Status: Patch Available  (was: Open)

> Handle some configs moved
> -
>
> Key: AMBARI-23071
> URL: https://issues.apache.org/jira/browse/AMBARI-23071
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Fix For: 2.7.0
>
> Attachments: AMBARI-23071.patch
>
>




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

[jira] [Updated] (AMBARI-23071) Handle some configs moved

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-23071:
-
Attachment: AMBARI-23071.patch

> Handle some configs moved
> -
>
> Key: AMBARI-23071
> URL: https://issues.apache.org/jira/browse/AMBARI-23071
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Fix For: 2.7.0
>
> Attachments: AMBARI-23071.patch
>
>




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

[jira] [Created] (AMBARI-23071) Handle some configs moved

[Andrew Onischuk (JIRA)]

Andrew Onischuk created AMBARI-23071:


 Summary: Handle some configs moved
 Key: AMBARI-23071
 URL: https://issues.apache.org/jira/browse/AMBARI-23071
 Project: Ambari
  Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
 Fix For: 2.7.0
 Attachments: AMBARI-23071.patch





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

[jira] [Commented] (AMBARI-23064) Remove dependency on com.fasterxml.jackson.core:jackson-databind before version 2.9.4 for Ambari Server

[Hudson (JIRA)]

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

Hudson commented on AMBARI-23064:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #625 (See 
[https://builds.apache.org/job/Ambari-branch-2.6/625/])
AMBARI-23064. Upgrading jackson-databind (plus jackson-annotations and (rlevas: 
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=5f386f3febfa010710a9ade7f81a4fac6d8c7fb7])
* (edit) ambari-server/pom.xml
* (edit) ambari-project/pom.xml


> Remove dependency on com.fasterxml.jackson.core:jackson-databind before 
> version 2.9.4 for Ambari Server
> ---
>
> Key: AMBARI-23064
> URL: https://issues.apache.org/jira/browse/AMBARI-23064
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Blocker
>  Labels: black-duck, pull-request-available
> Fix For: 2.6.2, 2.7.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Remove dependency on com.fasterxml.jackson.core:jackson-databind before 
> version 2.9.4 due to security concerns. See
>  * CVE-2018-5968 - [https://nvd.nist.gov/vuln/detail/CVE-2018-5968]
>  * CVE-2017-17485 - [https://nvd.nist.gov/vuln/detail/CVE-2017-17485]
> {noformat}
>  --- maven-dependency-plugin:2.8:tree (default-cli) @ ambari-server ---
>  org.apache.ambari:ambari-server:jar:2.6.1.0.0
>  \- com.networknt:json-schema-validator:jar:0.1.10:test
> \- com.fasterxml.jackson.core:jackson-databind:jar:2.8.7:test
> {noformat}



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

[jira] [Created] (AMBARI-23070) Yarn Registry DNS is not added in Stale Component restart when yarn-env.sh is modified

[Yesha Vora (JIRA)]

Yesha Vora created AMBARI-23070:
---

 Summary: Yarn Registry DNS is not added in Stale Component restart 
when yarn-env.sh is modified
 Key: AMBARI-23070
 URL: https://issues.apache.org/jira/browse/AMBARI-23070
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.7.0
Reporter: Yesha Vora


Scenario:
Create a secure Hdp 3 cluster. Yarn DNS server was stopped.

1) Update yarn-env.sh
{code:java|title=example add below block to yarn-env.sh}
{% if security_enabled %}
export 
YARN_REGISTRYDNS_OPTS="-Djava.security.auth.login.config={{yarn_ats_jaas_file}}"
{% endif %}{code}
2) Click on Restart stale components

Here, Yarn DNS registry component is not restarted. Only Resourcemanager, 
nodemanagers. TimelineServer, TimelineReader v.2 are restarted.

Yarn DNS registry server should be restarted by stale component restart.



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

[jira] [Commented] (AMBARI-23054) Remove dependency on commons-beanutils:commons-beanutils before version 1.9.2 for Ambari Server

[Hudson (JIRA)]

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

Hudson commented on AMBARI-23054:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #624 (See 
[https://builds.apache.org/job/Ambari-branch-2.6/624/])
AMBARI-23054. Upgaring commons-beanutils dependency in ambari-server to 
(rlevas: 
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=8a7312ab36f57939c61c92d440d3d406855e2afd])
* (edit) utility/pom.xml
* (edit) ambari-project/pom.xml
AMBARI-23054. Removing commons-beanutils-core dependency from (rlevas: 
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=10583f327c032ddf75e15e44c1c78de6bd298016])
* (edit) ambari-server/pom.xml


> Remove dependency on commons-beanutils:commons-beanutils before version 1.9.2 
> for Ambari Server
> ---
>
> Key: AMBARI-23054
> URL: https://issues.apache.org/jira/browse/AMBARI-23054
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Blocker
>  Labels: pull-request-available
> Fix For: 2.6.2, 2.7.0
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Remove dependency on commons-beanutils:commons-beanutils before version 1.9.2 
> due to security concerns. See CVE-2014-0114 - 
> [https://nvd.nist.gov/vuln/detail/CVE-2014-0114]
> {noformat}
> --- maven-dependency-plugin:2.8:tree(default-cli) @ ambari-server ---
>  org.apache.ambari:ambari-server:jar:2.6.1.0.0
>  +- org.apache.hadoop:hadoop-common:jar:2.7.2:compile
>  |  \- commons-configuration:commons-configuration:jar:1.6:compile
>  | +- commons-digester:commons-digester:jar:1.8:compile
>  | |  \- commons-beanutils:commons-beanutils:jar:1.9.2:compile
>  | \- commons-beanutils:commons-beanutils-core:jar:1.8.0:compile
>  \- utility:utility:jar:1.0.0.0-SNAPSHOT:test
> \- com.puppycrawl.tools:checkstyle:jar:6.19:test
>\- (commons-beanutils:commons-beanutils:jar:1.9.2:compile -{noformat}



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

[jira] [Commented] (AMBARI-23064) Remove dependency on com.fasterxml.jackson.core:jackson-databind before version 2.9.4 for Ambari Server

[Robert Levas (JIRA)]

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

Robert Levas commented on AMBARI-23064:
---

[~smolnar] This (or something similar) needs to go into trunk as well.  

 

> Remove dependency on com.fasterxml.jackson.core:jackson-databind before 
> version 2.9.4 for Ambari Server
> ---
>
> Key: AMBARI-23064
> URL: https://issues.apache.org/jira/browse/AMBARI-23064
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Blocker
>  Labels: black-duck, pull-request-available
> Fix For: 2.6.2, 2.7.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Remove dependency on com.fasterxml.jackson.core:jackson-databind before 
> version 2.9.4 due to security concerns. See
>  * CVE-2018-5968 - [https://nvd.nist.gov/vuln/detail/CVE-2018-5968]
>  * CVE-2017-17485 - [https://nvd.nist.gov/vuln/detail/CVE-2017-17485]
> {noformat}
>  --- maven-dependency-plugin:2.8:tree (default-cli) @ ambari-server ---
>  org.apache.ambari:ambari-server:jar:2.6.1.0.0
>  \- com.networknt:json-schema-validator:jar:0.1.10:test
> \- com.fasterxml.jackson.core:jackson-databind:jar:2.8.7:test
> {noformat}



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

[jira] [Updated] (AMBARI-23026) WEB type alerts authentication in Kerberos secured cluster

[Robert Levas (JIRA)]

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

Robert Levas updated AMBARI-23026:
--
Fix Version/s: 2.7.0

> WEB type alerts authentication in Kerberos secured cluster
> --
>
> Key: AMBARI-23026
> URL: https://issues.apache.org/jira/browse/AMBARI-23026
> Project: Ambari
>  Issue Type: Bug
>  Components: alerts
>Affects Versions: 2.5.2, trunk, 2.6.2
> Environment: Ambari 2.5.2
> Hortonworks HDP-2.5.3.0-37
>Reporter: David F. Quiroga
>Assignee: Robert Levas
>Priority: Minor
> Fix For: 2.7.0
>
>
> In a Kerberized cluster some web endpoints (App Timeline Web UI, 
> ResourceManger Web UI, etc.) require authentication. Any Ambari alerts 
> checking those endpoints must then be able to authenticate.
> This was addressed in AMBARI-9586, however the default principal and keytab 
> used in the alerts.json is that of the "bare" SPNEGO principal 
> HTTP/_HOST@REALM. 
>  My understanding is that the HTTP service principal is used to authenticate 
> users to a service, not used to authenticate to another service.
> 1. Since most endpoints involved are Web UI, would it be more appropriate to 
> use the smokeuser in the alerts?
> 2. This was first observed in Ranger Audit, the YARN Ranger Plug-in showed 
> many access denied from HTTP user. [This 
> post|https://community.hortonworks.com/content/supportkb/150206/ranger-audit-logs-refers-to-access-denied-for-http.html]
>  provided some direction as to where those requests were coming from. We have 
> updated the ResourceManger Web UI alert definition to use 
> cluster-env/smokeuser_keytab and cluster-env/smokeuser_principal_name and 
> this has resolved the initial HTTP access denied. 
>  Would it also be advisable to make the change in the other secure Web UI 
> alert definitions?



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

[jira] [Assigned] (AMBARI-23026) WEB type alerts authentication in Kerberos secured cluster

[Robert Levas (JIRA)]

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

Robert Levas reassigned AMBARI-23026:
-

Assignee: Robert Levas

> WEB type alerts authentication in Kerberos secured cluster
> --
>
> Key: AMBARI-23026
> URL: https://issues.apache.org/jira/browse/AMBARI-23026
> Project: Ambari
>  Issue Type: Bug
>  Components: alerts
>Affects Versions: 2.5.2, trunk, 2.6.2
> Environment: Ambari 2.5.2
> Hortonworks HDP-2.5.3.0-37
>Reporter: David F. Quiroga
>Assignee: Robert Levas
>Priority: Minor
>
> In a Kerberized cluster some web endpoints (App Timeline Web UI, 
> ResourceManger Web UI, etc.) require authentication. Any Ambari alerts 
> checking those endpoints must then be able to authenticate.
> This was addressed in AMBARI-9586, however the default principal and keytab 
> used in the alerts.json is that of the "bare" SPNEGO principal 
> HTTP/_HOST@REALM. 
>  My understanding is that the HTTP service principal is used to authenticate 
> users to a service, not used to authenticate to another service.
> 1. Since most endpoints involved are Web UI, would it be more appropriate to 
> use the smokeuser in the alerts?
> 2. This was first observed in Ranger Audit, the YARN Ranger Plug-in showed 
> many access denied from HTTP user. [This 
> post|https://community.hortonworks.com/content/supportkb/150206/ranger-audit-logs-refers-to-access-denied-for-http.html]
>  provided some direction as to where those requests were coming from. We have 
> updated the ResourceManger Web UI alert definition to use 
> cluster-env/smokeuser_keytab and cluster-env/smokeuser_principal_name and 
> this has resolved the initial HTTP access denied. 
>  Would it also be advisable to make the change in the other secure Web UI 
> alert definitions?



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

[jira] [Updated] (AMBARI-23069) Wrong reference in params.py files for zookeeper hosts

[JIRA]

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

Olivér Szabó updated AMBARI-23069:
--
Summary: Wrong reference in params.py files for zookeeper hosts  (was: 
Wrong reference in infra-solr params.py for zookeeper hosts)

> Wrong reference in params.py files for zookeeper hosts
> --
>
> Key: AMBARI-23069
> URL: https://issues.apache.org/jira/browse/AMBARI-23069
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Blocker
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




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

[jira] [Commented] (AMBARI-23044) Version upgrades of 3rd party dependencies for Log Search and Infra

[Hudson (JIRA)]

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

Hudson commented on AMBARI-23044:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8776 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/8776/])
AMBARI-23044. Version upgrades of 3rd party dependencies for Log Sear… (github: 
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=5a6285ab2707a4173183baf0eb5e99a9c8fc5c1b])
* (edit) ambari-logsearch/ambari-logsearch-logfeeder/pom.xml
* (edit) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/util/JSONUtil.java
* (edit) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/web/filters/LogsearchKrbFilter.java
* (edit) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/common/ExternalServerClient.java
* (edit) ambari-infra/ambari-infra-manager/pom.xml
* (edit) ambari-infra/ambari-infra-solr-client/pom.xml
* (edit) ambari-logsearch/pom.xml
* (edit) ambari-logsearch/ambari-logsearch-config-zookeeper/pom.xml
* (edit) ambari-infra/pom.xml
* (edit) ambari-infra/ambari-infra-assembly/pom.xml
* (edit) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/configurer/SolrCollectionConfigurer.java
* (delete) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/handler/UpgradeSchemaHandler.java
* (edit) ambari-logsearch/ambari-logsearch-server/pom.xml


> Version upgrades of 3rd party dependencies for Log Search and Infra
> ---
>
> Key: AMBARI-23044
> URL: https://issues.apache.org/jira/browse/AMBARI-23044
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-infra, ambari-logsearch
>Affects Versions: 2.6.2
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Blocker
>  Labels: pull-request-available
> Fix For: 2.6.2
>
>  Time Spent: 1h 50m
>  Remaining Estimate: 0h
>




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

[jira] [Updated] (AMBARI-23069) Wrong reference in infra-solr params.py for zookeeper hosts

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot updated AMBARI-23069:

Labels: pull-request-available  (was: )

> Wrong reference in infra-solr params.py for zookeeper hosts
> ---
>
> Key: AMBARI-23069
> URL: https://issues.apache.org/jira/browse/AMBARI-23069
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Blocker
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>




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

[jira] [Created] (AMBARI-23069) Wrong reference in infra-solr params.py for zookeeper hosts

[JIRA]

Olivér Szabó created AMBARI-23069:
-

 Summary: Wrong reference in infra-solr params.py for zookeeper 
hosts
 Key: AMBARI-23069
 URL: https://issues.apache.org/jira/browse/AMBARI-23069
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.7.0
Reporter: Olivér Szabó
Assignee: Olivér Szabó
 Fix For: 2.7.0






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

[jira] [Resolved] (AMBARI-23045) Default Solr operator is not working anymore for history collection

[JIRA]

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

Olivér Szabó resolved AMBARI-23045.
---
Resolution: Fixed

> Default Solr operator is not working anymore for history collection
> ---
>
> Key: AMBARI-23045
> URL: https://issues.apache.org/jira/browse/AMBARI-23045
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>




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

[jira] [Resolved] (AMBARI-23044) Version upgrades of 3rd party dependencies for Log Search and Infra

[JIRA]

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

Olivér Szabó resolved AMBARI-23044.
---
Resolution: Fixed

> Version upgrades of 3rd party dependencies for Log Search and Infra
> ---
>
> Key: AMBARI-23044
> URL: https://issues.apache.org/jira/browse/AMBARI-23044
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-infra, ambari-logsearch
>Affects Versions: 2.6.2
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Blocker
>  Labels: pull-request-available
> Fix For: 2.6.2
>
>  Time Spent: 1h 50m
>  Remaining Estimate: 0h
>




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

[jira] [Updated] (AMBARI-23066) Freeze the hostname column in Assign Slaves/Clients page (Install and Add Service Wizards)

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot updated AMBARI-23066:

Labels: pull-request-available  (was: )

> Freeze the hostname column in Assign Slaves/Clients page (Install and Add 
> Service Wizards)
> --
>
> Key: AMBARI-23066
> URL: https://issues.apache.org/jira/browse/AMBARI-23066
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: trunk
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
>Priority: Major
>  Labels: pull-request-available
> Fix For: trunk
>
>
> we just want to freeze the hostname column so that when the user scrolls 
> horizontally, the hostname column remains in place. 



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

[jira] [Commented] (AMBARI-23052) Extend service actions dropdowns with namespace-specific items

[Hudson (JIRA)]

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

Hudson commented on AMBARI-23052:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8775 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/8775/])
AMBARI-23052 Extend service actions dropdowns with namespace-specific (github: 
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=3c4f83048bd35e5b11838dfbdc11eb765f208cfc])
* (edit) ambari-web/app/models/service/hdfs.js
* (edit) ambari-web/app/messages.js
* (edit) ambari-web/app/utils/ajax/ajax.js
* (edit) ambari-web/test/controllers/main/service/item_test.js
* (edit) ambari-web/app/templates/main/service/info/summary.hbs
* (edit) ambari-web/app/views/main/service/info/summary.js
* (edit) ambari-web/app/views/main/service/item.js
* (edit) ambari-web/app/models/service.js
* (edit) ambari-web/test/views/main/service/item_test.js
* (edit) ambari-web/app/utils/batch_scheduled_requests.js
* (edit) ambari-web/app/controllers/main/service/item.js
* (edit) ambari-web/app/app.js
* (edit) ambari-web/app/models/host_component.js
* (edit) ambari-web/app/templates/main/service/item.hbs


> Extend service actions dropdowns with namespace-specific items
> --
>
> Key: AMBARI-23052
> URL: https://issues.apache.org/jira/browse/AMBARI-23052
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> - User should be able to apply the service action (if it can be executed for 
> certain components only) to the given namespace
> - Add Restart NameNodes item



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

[jira] [Commented] (AMBARI-23056) Fix AMS dependencies that have security issues.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-23056:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8774 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/8774/])
AMBARI-23056 : Fix AMS dependencies that have security issues. (avijayan: 
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=463602a2e65da8e038306de25aebd6ca556f9b8c])
* (edit) ambari-metrics/ambari-metrics-common/pom.xml
* (edit) ambari-metrics/ambari-metrics-hadoop-sink/pom.xml
* (edit) ambari-metrics/pom.xml
* (edit) ambari-metrics/ambari-metrics-timelineservice/pom.xml
* (edit) ambari-metrics/ambari-metrics-flume-sink/pom.xml


> Fix AMS dependencies that have security issues.
> ---
>
> Key: AMBARI-23056
> URL: https://issues.apache.org/jira/browse/AMBARI-23056
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-metrics
>Affects Versions: 2.6.2
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
>  Labels: pull-request-available
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>




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

[jira] [Commented] (AMBARI-23056) Fix AMS dependencies that have security issues.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-23056:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #623 (See 
[https://builds.apache.org/job/Ambari-branch-2.6/623/])
AMBARI-23056 : Fix AMS dependencies that have security issues. (avijayan: 
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=a61bfe2e10b0083e9c3a4d3ca11d730dbe61cc49])
* (edit) ambari-metrics/ambari-metrics-timelineservice/pom.xml
* (edit) ambari-metrics/ambari-metrics-common/pom.xml
* (edit) ambari-metrics/ambari-metrics-hadoop-sink/pom.xml
* (edit) ambari-metrics/ambari-metrics-flume-sink/pom.xml
* (edit) ambari-metrics/pom.xml


> Fix AMS dependencies that have security issues.
> ---
>
> Key: AMBARI-23056
> URL: https://issues.apache.org/jira/browse/AMBARI-23056
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-metrics
>Affects Versions: 2.6.2
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
>  Labels: pull-request-available
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>




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

[jira] [Resolved] (AMBARI-23052) Extend service actions dropdowns with namespace-specific items

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk resolved AMBARI-23052.
---
Resolution: Fixed

Merged to trunk

> Extend service actions dropdowns with namespace-specific items
> --
>
> Key: AMBARI-23052
> URL: https://issues.apache.org/jira/browse/AMBARI-23052
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> - User should be able to apply the service action (if it can be executed for 
> certain components only) to the given namespace
> - Add Restart NameNodes item



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

[jira] [Commented] (AMBARI-22934) [API] Updating current stack repo without GPL repos in the body does not throw any error

[Hudson (JIRA)]

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

Hudson commented on AMBARI-22934:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8773 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/8773/])
Reverts AMBARI-22934. [API] Updating current stack repo without GPL (github: 
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=b78b61b1f092d5e68fc3f08396d533cd1d99d67a])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/RepositoryVersionHelper.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProvider.java
* (delete) 
ambari-server/src/test/java/org/apache/ambari/server/state/stack/upgrade/RepositoryVersionHelperTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProviderTest.java


> [API] Updating current stack repo without GPL repos in the body does not 
> throw any error
> 
>
> Key: AMBARI-22934
> URL: https://issues.apache.org/jira/browse/AMBARI-22934
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.6.2
>
>  Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> # Install HDP 2.6.4.0 stack with Ambari 2.6.1
>  # Update the current repository versions with the following body on 
> ambari-2.6.1
> {code:java}
> PUT 
> http://:8080/api/v1/stacks/HDP/versions/2.6/repository_versions/1
> {
>  "operating_systems": [
>  {
>  "OperatingSystems": {
>  "os_type": "debian7",
>  "ambari_managed_repositories": true
>  },
>  "repositories": [
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP/debian7/2.x/updates/2.6.0.3;,
>  "repo_id": "HDP-2.6",
>  "repo_name": "HDP"
>  }
>  },
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/debian6;,
>  "repo_id": "HDP-UTILS-1.1.0.21",
>  "repo_name": "HDP-UTILS"
>  }
>  }
>  ]
>  },
>  {
>  "OperatingSystems": {
>  "os_type": "redhat6",
>  "ambari_managed_repositories": true
>  },
>  "repositories": [
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP/centos6/2.x/updates/2.4.2.0/;,
>  "repo_id": "HDP-2.6",
>  "repo_name": "HDP"
>  }
>  },
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/centos6;,
>  "repo_id": "HDP-UTILS-1.1.0.21",
>  "repo_name": "HDP-UTILS"
>  }
>  }
>  ]
>  },
>  {
>  "OperatingSystems": {
>  "os_type": "redhat7",
>  "ambari_managed_repositories": true
>  },
>  "repositories": [
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP/centos7/2.x/updates/2.6.0.3;,
>  "repo_id": "HDP-2.6",
>  "repo_name": "HDP"
>  }
>  },
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/centos7;,
>  "repo_id": "HDP-UTILS-1.1.0.21",
>  "repo_name": "HDP-UTILS"
>  }
>  }
>  ]
>  },
>  {
>  "OperatingSystems": {
>  "os_type": "suse11",
>  "ambari_managed_repositories": true
>  },
>  "repositories": [
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP/suse11sp3/2.x/updates/2.6.0.3;,
>  "repo_id": "HDP-2.6",
>  "repo_name": "HDP"
>  }
>  },
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/suse11sp3;,
>  "repo_id": "HDP-UTILS-1.1.0.21",
>  "repo_name": "HDP-UTILS"
>  }
>  }
>  ]
>  },
>  {
>  "OperatingSystems": {
>  "os_type": "suse12",
>  "ambari_managed_repositories": true
>  },
>  "repositories": [
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP/suse11sp3/2.x/updates/2.6.0.3;,
>  "repo_id": "HDP-2.6",
>  "repo_name": "HDP"
>  }
>  },
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/suse11sp3;,
>  "repo_id": "HDP-UTILS-1.1.0.21",
>  "repo_name": "HDP-UTILS"
>  }
>  }
>  ]
>  },
>  {
>  "OperatingSystems": {
>  "os_type": "ubuntu12",
>  "ambari_managed_repositories": true
>  },
>  "repositories": [
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP/ubuntu12/2.x/updates/2.6.0.3;,
>  "repo_id": "HDP-2.6",
>  "repo_name": "HDP"
>  }
>  },
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/ubuntu12;,
>  "repo_id": "HDP-UTILS-1.1.0.21",

[jira] [Commented] (AMBARI-22934) [API] Updating current stack repo without GPL repos in the body does not throw any error

[Hudson (JIRA)]

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

Hudson commented on AMBARI-22934:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #622 (See 
[https://builds.apache.org/job/Ambari-branch-2.6/622/])
Revert "AMBARI-22934. [API] Updating current stack repo without GPL (github: 
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=89dfc60ea77877dc0213596930f9c83ae7c3317e])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProvider.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProviderTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/RepositoryVersionHelper.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/state/stack/upgrade/RepositoryVersionHelperTest.java


> [API] Updating current stack repo without GPL repos in the body does not 
> throw any error
> 
>
> Key: AMBARI-22934
> URL: https://issues.apache.org/jira/browse/AMBARI-22934
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.6.2
>
>  Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> # Install HDP 2.6.4.0 stack with Ambari 2.6.1
>  # Update the current repository versions with the following body on 
> ambari-2.6.1
> {code:java}
> PUT 
> http://:8080/api/v1/stacks/HDP/versions/2.6/repository_versions/1
> {
>  "operating_systems": [
>  {
>  "OperatingSystems": {
>  "os_type": "debian7",
>  "ambari_managed_repositories": true
>  },
>  "repositories": [
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP/debian7/2.x/updates/2.6.0.3;,
>  "repo_id": "HDP-2.6",
>  "repo_name": "HDP"
>  }
>  },
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/debian6;,
>  "repo_id": "HDP-UTILS-1.1.0.21",
>  "repo_name": "HDP-UTILS"
>  }
>  }
>  ]
>  },
>  {
>  "OperatingSystems": {
>  "os_type": "redhat6",
>  "ambari_managed_repositories": true
>  },
>  "repositories": [
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP/centos6/2.x/updates/2.4.2.0/;,
>  "repo_id": "HDP-2.6",
>  "repo_name": "HDP"
>  }
>  },
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/centos6;,
>  "repo_id": "HDP-UTILS-1.1.0.21",
>  "repo_name": "HDP-UTILS"
>  }
>  }
>  ]
>  },
>  {
>  "OperatingSystems": {
>  "os_type": "redhat7",
>  "ambari_managed_repositories": true
>  },
>  "repositories": [
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP/centos7/2.x/updates/2.6.0.3;,
>  "repo_id": "HDP-2.6",
>  "repo_name": "HDP"
>  }
>  },
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/centos7;,
>  "repo_id": "HDP-UTILS-1.1.0.21",
>  "repo_name": "HDP-UTILS"
>  }
>  }
>  ]
>  },
>  {
>  "OperatingSystems": {
>  "os_type": "suse11",
>  "ambari_managed_repositories": true
>  },
>  "repositories": [
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP/suse11sp3/2.x/updates/2.6.0.3;,
>  "repo_id": "HDP-2.6",
>  "repo_name": "HDP"
>  }
>  },
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/suse11sp3;,
>  "repo_id": "HDP-UTILS-1.1.0.21",
>  "repo_name": "HDP-UTILS"
>  }
>  }
>  ]
>  },
>  {
>  "OperatingSystems": {
>  "os_type": "suse12",
>  "ambari_managed_repositories": true
>  },
>  "repositories": [
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP/suse11sp3/2.x/updates/2.6.0.3;,
>  "repo_id": "HDP-2.6",
>  "repo_name": "HDP"
>  }
>  },
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/suse11sp3;,
>  "repo_id": "HDP-UTILS-1.1.0.21",
>  "repo_name": "HDP-UTILS"
>  }
>  }
>  ]
>  },
>  {
>  "OperatingSystems": {
>  "os_type": "ubuntu12",
>  "ambari_managed_repositories": true
>  },
>  "repositories": [
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP/ubuntu12/2.x/updates/2.6.0.3;,
>  "repo_id": "HDP-2.6",
>  "repo_name": "HDP"
>  }
>  },
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/ubuntu12;,
>  "repo_id": "HDP-UTILS-1.1.0.21",
>  

[jira] [Reopened] (AMBARI-22934) [API] Updating current stack repo without GPL repos in the body does not throw any error

[Siddharth Wagle (JIRA)]

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

Siddharth Wagle reopened AMBARI-22934:
--

Causing deploy failures.

> [API] Updating current stack repo without GPL repos in the body does not 
> throw any error
> 
>
> Key: AMBARI-22934
> URL: https://issues.apache.org/jira/browse/AMBARI-22934
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.6.2
>
>  Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> # Install HDP 2.6.4.0 stack with Ambari 2.6.1
>  # Update the current repository versions with the following body on 
> ambari-2.6.1
> {code:java}
> PUT 
> http://:8080/api/v1/stacks/HDP/versions/2.6/repository_versions/1
> {
>  "operating_systems": [
>  {
>  "OperatingSystems": {
>  "os_type": "debian7",
>  "ambari_managed_repositories": true
>  },
>  "repositories": [
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP/debian7/2.x/updates/2.6.0.3;,
>  "repo_id": "HDP-2.6",
>  "repo_name": "HDP"
>  }
>  },
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/debian6;,
>  "repo_id": "HDP-UTILS-1.1.0.21",
>  "repo_name": "HDP-UTILS"
>  }
>  }
>  ]
>  },
>  {
>  "OperatingSystems": {
>  "os_type": "redhat6",
>  "ambari_managed_repositories": true
>  },
>  "repositories": [
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP/centos6/2.x/updates/2.4.2.0/;,
>  "repo_id": "HDP-2.6",
>  "repo_name": "HDP"
>  }
>  },
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/centos6;,
>  "repo_id": "HDP-UTILS-1.1.0.21",
>  "repo_name": "HDP-UTILS"
>  }
>  }
>  ]
>  },
>  {
>  "OperatingSystems": {
>  "os_type": "redhat7",
>  "ambari_managed_repositories": true
>  },
>  "repositories": [
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP/centos7/2.x/updates/2.6.0.3;,
>  "repo_id": "HDP-2.6",
>  "repo_name": "HDP"
>  }
>  },
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/centos7;,
>  "repo_id": "HDP-UTILS-1.1.0.21",
>  "repo_name": "HDP-UTILS"
>  }
>  }
>  ]
>  },
>  {
>  "OperatingSystems": {
>  "os_type": "suse11",
>  "ambari_managed_repositories": true
>  },
>  "repositories": [
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP/suse11sp3/2.x/updates/2.6.0.3;,
>  "repo_id": "HDP-2.6",
>  "repo_name": "HDP"
>  }
>  },
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/suse11sp3;,
>  "repo_id": "HDP-UTILS-1.1.0.21",
>  "repo_name": "HDP-UTILS"
>  }
>  }
>  ]
>  },
>  {
>  "OperatingSystems": {
>  "os_type": "suse12",
>  "ambari_managed_repositories": true
>  },
>  "repositories": [
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP/suse11sp3/2.x/updates/2.6.0.3;,
>  "repo_id": "HDP-2.6",
>  "repo_name": "HDP"
>  }
>  },
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/suse11sp3;,
>  "repo_id": "HDP-UTILS-1.1.0.21",
>  "repo_name": "HDP-UTILS"
>  }
>  }
>  ]
>  },
>  {
>  "OperatingSystems": {
>  "os_type": "ubuntu12",
>  "ambari_managed_repositories": true
>  },
>  "repositories": [
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP/ubuntu12/2.x/updates/2.6.0.3;,
>  "repo_id": "HDP-2.6",
>  "repo_name": "HDP"
>  }
>  },
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/ubuntu12;,
>  "repo_id": "HDP-UTILS-1.1.0.21",
>  "repo_name": "HDP-UTILS"
>  }
>  }
>  ]
>  },
>  {
>  "OperatingSystems": {
>  "os_type": "ubuntu14",
>  "ambari_managed_repositories": true
>  },
>  "repositories": [
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP/ubuntu14/2.x/updates/2.6.0.3;,
>  "repo_id": "HDP-2.6",
>  "repo_name": "HDP"
>  }
>  },
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/ubuntu14;,
>  "repo_id": "HDP-UTILS-1.1.0.21",
>  "repo_name": "HDP-UTILS"
>  }
>  }
>  ]
>  },
>  {
>  "OperatingSystems": {
>  "os_type": "ubuntu16",
>  "ambari_managed_repositories": true
>  },
>  "repositories": [
>  {
>  "Repositories": {
>  "base_url": 
> "http://public-repo-1.hortonworks.com/HDP/ubuntu16/2.x/updates/2.6.0.3;,
>  "repo_id": "HDP-2.6",
>  "repo_name": "HDP"
>  }
>  },
>  {
>  "Repositories": {
>  "base_url": 
> 

[jira] [Updated] (AMBARI-23068) Service Auto Start cannot be disabled

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot updated AMBARI-23068:

Labels: pull-request-available  (was: )

> Service Auto Start cannot be disabled
> -
>
> Key: AMBARI-23068
> URL: https://issues.apache.org/jira/browse/AMBARI-23068
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>
> *STR*
> # navigate / Admin / Service Auto Start
> # disable Auto Start
> # save 
> # refresh page



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

[jira] [Created] (AMBARI-23068) Service Auto Start cannot be disabled

[Andrii Tkach (JIRA)]

Andrii Tkach created AMBARI-23068:
-

 Summary: Service Auto Start cannot be disabled
 Key: AMBARI-23068
 URL: https://issues.apache.org/jira/browse/AMBARI-23068
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.7.0
Reporter: Andrii Tkach
Assignee: Andrii Tkach
 Fix For: 2.7.0


*STR*
# navigate / Admin / Service Auto Start
# disable Auto Start
# save 
# refresh page



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

[jira] [Commented] (AMBARI-23044) Version upgrades of 3rd party dependencies for Log Search and Infra

[Hudson (JIRA)]

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

Hudson commented on AMBARI-23044:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #621 (See 
[https://builds.apache.org/job/Ambari-branch-2.6/621/])
[AMBARI-23044]. Version upgrades of 3rd party dependencies for Log (github: 
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=591354683ed247a5dfafaba4d9fc685ca268664d])
* (edit) ambari-logsearch/ambari-logsearch-portal/pom.xml
* (edit) 
ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/util/JSONUtil.java
* (edit) ambari-logsearch/ambari-logsearch-assembly/pom.xml
* (edit) 
ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/common/ExternalServerClient.java
* (edit) ambari-logsearch/pom.xml
* (delete) 
ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/solr/metrics/SolrAmsClient.java
* (edit) ambari-logsearch/ambari-logsearch-logfeeder/pom.xml


> Version upgrades of 3rd party dependencies for Log Search and Infra
> ---
>
> Key: AMBARI-23044
> URL: https://issues.apache.org/jira/browse/AMBARI-23044
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-infra, ambari-logsearch
>Affects Versions: 2.6.2
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Blocker
>  Labels: pull-request-available
> Fix For: 2.6.2
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>




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

[jira] [Created] (AMBARI-23067) Remove dependency on commons-collections:commons-collections:jar before version 3.2.2 for Ambari Server

[Sandor Molnar (JIRA)]

Sandor Molnar created AMBARI-23067:
--

 Summary: Remove dependency on 
commons-collections:commons-collections:jar before version 3.2.2 for Ambari 
Server
 Key: AMBARI-23067
 URL: https://issues.apache.org/jira/browse/AMBARI-23067
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.6.2
Reporter: Sandor Molnar
Assignee: Sandor Molnar
 Fix For: 2.6.2, 2.7.0


Remove dependency on commons-collections:commons-collections before version 
3.2.2 due to security concerns. See
 * CVE-2015-6420 - [https://nvd.nist.gov/vuln/detail/CVE-2015-6420]
 * CVE-2015-7501 - [https://nvd.nist.gov/vuln/detail/CVE-2015-7501]
 * CVE-2017-15708 - [https://nvd.nist.gov/vuln/detail/CVE-2017-15708]

{noformat}
--- maven-dependency-plugin:2.8:tree(default-cli) @ ambari-server ---
 org.apache.ambari:ambari-server:jar:2.6.1.0.0
 +- org.apache.directory.server:apacheds-server-annotations:jar:2.0.0-M19:test
 |  +- org.apache.directory.server:apacheds-core-annotations:jar:2.0.0-M19:test
 |  |  +- org.apache.directory.server:apacheds-xdbm-partition:jar:2.0.0-M19:test
 |  |  |  \- (commons-collections:commons-collections:jar:3.2.1:test - omitted 
for duplicate)
 |  |  \- org.apache.directory.mavibot:mavibot:jar:1.0.0-M6:test
 |  | \- (commons-collections:commons-collections:jar:3.2.1:test - omitted 
for duplicate)
 |  \- org.apache.directory.api:api-ldap-codec-core:jar:1.0.0-M26:test
 | \- (commons-collections:commons-collections:jar:3.2.1:compile - scope 
updated from test; omitted for duplicate)
 +- org.apache.directory.server:apacheds-core-integ:jar:2.0.0-M19:test
 |  +- 
org.apache.directory.server:apacheds-interceptors-authn:jar:2.0.0-M19:test
 |  |  \- (commons-collections:commons-collections:jar:3.2.1:test - omitted for 
duplicate)
 |  \- org.apache.directory.server:apacheds-interceptors-hash:jar:2.0.0-M19:test
 | \- (commons-collections:commons-collections:jar:3.2.1:test - omitted for 
duplicate)
 +- org.apache.directory.server:apacheds-kerberos-codec:jar:2.0.0-M19:compile
 |  \- org.apache.directory.api:api-ldap-model:jar:1.0.0-M26:compile
 | \- (commons-collections:commons-collections:jar:3.2.1:compile - omitted 
for duplicate)
 +- org.apache.directory.server:apacheds-core:jar:2.0.0-M19:test
 |  \- 
org.apache.directory.server:apacheds-interceptors-exception:jar:2.0.0-M19:test
 | \- (commons-collections:commons-collections:jar:3.2.1:test - omitted for 
duplicate)
 +- org.apache.directory.shared:shared-ldap:jar:0.9.17:test
 |  \- (commons-collections:commons-collections:jar:3.2.1:compile - scope 
updated from test; omitted for duplicate)
 +- org.apache.velocity:velocity:jar:1.7:compile
 |  \- commons-collections:commons-collections:jar:3.2.1:compile
 +- org.apache.hadoop:hadoop-common:jar:2.7.2:compile
 |  +- (commons-collections:commons-collections:jar:3.2.2:compile - omitted for 
conflict with 3.2.1)
 |  \- commons-configuration:commons-configuration:jar:1.6:compile
 | \- (commons-collections:commons-collections:jar:3.2.1:compile - omitted 
for duplicate)
 \- utility:utility:jar:1.0.0.0-SNAPSHOT:test
\- com.puppycrawl.tools:checkstyle:jar:6.19:test
   \- (commons-collections:commons-collections:jar:3.2.2:test - omitted for 
conflict with 3.2.1){noformat}



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

[jira] [Updated] (AMBARI-23065) Remove dependency on org.apache.httpcomponents:httpclient before version 4.3.5.1 for Ambari Server

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot updated AMBARI-23065:

Labels: black-duck pull-request-available  (was: black-duck)

> Remove dependency on org.apache.httpcomponents:httpclient before version 
> 4.3.5.1 for Ambari Server
> --
>
> Key: AMBARI-23065
> URL: https://issues.apache.org/jira/browse/AMBARI-23065
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Critical
>  Labels: black-duck, pull-request-available
> Fix For: 2.6.2, 2.7.0
>
>
> Remove dependency on org.apache.httpcomponents:httpclient:jar before version 
> 4.3.5.1 due to security concerns. See
>  * CVE-2015-5262 - [https://nvd.nist.gov/vuln/detail/CVE-2015-5262]
>  * CVE-2014-3577 - [https://nvd.nist.gov/vuln/detail/CVE-2014-3577]
> {noformat}
> --- maven-dependency-plugin:2.8:tree(default-cli) @ ambari-server ---
>  org.apache.ambari:ambari-server:jar:2.6.1.0.0
>  +- org.apache.httpcomponents:httpclient:jar:4.2.5:compile
>  +- org.apache.ambari:ambari-metrics-common:jar:2.6.1.0.0:compile
>  |  \- (org.apache.httpcomponents:httpclient:jar:4.2.5:compile - omitted for 
> duplicate)
>  +- org.apache.hadoop:hadoop-auth:jar:2.7.2:compile
>  |  \- (org.apache.httpcomponents:httpclient:jar:4.2.5:compile - omitted for 
> duplicate)
>  \- org.apache.hadoop:hadoop-common:jar:2.7.2:compile
> \- net.java.dev.jets3t:jets3t:jar:0.9.0:compile
>\- (org.apache.httpcomponents:httpclient:jar:4.1.2:compile - omitted 
> for conflict with 4.2.5)
>  {noformat}
>  * 
>  * 
> [Options|https://hortonworks.jira.com/browse/BUG-97133?filter=54432]
> h2.  



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

[jira] [Created] (AMBARI-23066) Freeze the hostname column in Assign Slaves/Clients page (Install and Add Service Wizards)

[Ishan Bhatt (JIRA)]

Ishan Bhatt created AMBARI-23066:


 Summary: Freeze the hostname column in Assign Slaves/Clients page 
(Install and Add Service Wizards)
 Key: AMBARI-23066
 URL: https://issues.apache.org/jira/browse/AMBARI-23066
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: trunk
Reporter: Ishan Bhatt
Assignee: Ishan Bhatt
 Fix For: trunk


we just want to freeze the hostname column so that when the user scrolls 
horizontally, the hostname column remains in place. 



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

[jira] [Assigned] (AMBARI-23055) GPL repo is not hidden when default version is chosen in UI

[Andrii Tkach (JIRA)]

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

Andrii Tkach reassigned AMBARI-23055:
-

Assignee: (was: Andrii Tkach)

> GPL repo is not hidden when default version is chosen in UI
> ---
>
> Key: AMBARI-23055
> URL: https://issues.apache.org/jira/browse/AMBARI-23055
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: Vivek Sharma
>Priority: Critical
>  Labels: system_test
> Fix For: 2.6.2
>
>
> Ambari server has gpl license disabled i.e.
> {code}
> cat /etc/ambari-server/conf/ambari.properties | grep -i gpl
> gpl.license.accepted=false
> {code}
> - On register version page, upon choosing HDP-2.6.4.0 from the drop-down, the 
> GPL repo field is not masked (see default-version.png)
> - However upon choosing to upload the version from VDF URL, the GPL field is 
> correctly masked (see version-via-vdf.png)
> Looks like the problem is 
> [showRepo()|https://github.com/apache/ambari/blob/branch-2.6/ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsCreateCtrl.js#L50]
>  function which calls 
> [isGPLRepo|https://github.com/apache/ambari/blob/branch-2.6/ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsCreateCtrl.js#L46]
>  function where if we do not load version fromVDF URL the showRepo return true
>  



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

[jira] [Updated] (AMBARI-23063) "Stale Alerts" alert has to be re-done properly

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-23063:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk

> "Stale Alerts" alert has to be re-done properly
> ---
>
> Key: AMBARI-23063
> URL: https://issues.apache.org/jira/browse/AMBARI-23063
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-23063.patch
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>




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

[jira] [Reopened] (AMBARI-23043) 'Table or view not found error' with livy/livy2 interpreter on upgraded cluster to Fenton-M30

[Sandor Molnar (JIRA)]

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

Sandor Molnar reopened AMBARI-23043:


 

[~vbrodetskyi]

Your change seems to break a Python unit test on trunk; see this Jenkins job: 
[https://builds.apache.org/job/Ambari-trunk-Commit/8768/consoleFull]

Could you please fix it ASAP?

Thanks!

cc: [~rlevas]

> 'Table or view not found error' with livy/livy2 interpreter on upgraded 
> cluster to Fenton-M30
> -
>
> Key: AMBARI-23043
> URL: https://issues.apache.org/jira/browse/AMBARI-23043
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.6.2
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> The test has been performed as below:
> CentOS6 + Ambari-2.5.1 + HDP-2.6.1 -> AU to Ambari-2.6.2 -> Full EU to 
> HDP-2.6.5.0-74 (Fenton-M30) -> Run stack tests
> I see that with livy2 interpreter, anytime we register a temporary view or 
> table - the corresponding query on that table will fail with 'Table or view 
> not found error'
> {code:java}
> org.apache.spark.sql.AnalysisException: Table or view not found: word_counts; 
> line 2 pos 24
>  at 
> org.apache.spark.sql.catalyst.analysis.package$AnalysisErrorAt.failAnalysis(package.scala:42)
>  at 
> org.apache.spark.sql.catalyst.analysis.Analyzer$ResolveRelations$.org$apache$spark$sql$catalyst$analysis$Analyzer$ResolveRelations$$lookupTableFromCatalog(Analyzer.scala:649)
>  at 
> org.apache.spark.sql.catalyst.analysis.Analyzer$ResolveRelations$.resolveRelation(Analyzer.scala:601)
>  at 
> org.apache.spark.sql.catalyst.analysis.Analyzer$ResolveRelations$$anonfun$apply$8.applyOrElse(Analyzer.scala:631)
>  at 
> org.apache.spark.sql.catalyst.analysis.Analyzer$ResolveRelations$$anonfun$apply$8.applyOrElse(Analyzer.scala:624)
>  at 
> org.apache.spark.sql.catalyst.plans.logical.LogicalPlan$$anonfun$resolveOperators$1.apply(LogicalPlan.scala:62)
>  at 
> org.apache.spark.sql.catalyst.plans.logical.LogicalPlan$$anonfun$resolveOperators$1.apply(LogicalPlan.scala:62)
>  at 
> org.apache.spark.sql.catalyst.trees.CurrentOrigin$.withOrigin(TreeNode.scala:70)
>  at 
> org.apache.spark.sql.catalyst.plans.logical.LogicalPlan.resolveOperators(LogicalPlan.scala:61)
>  at 
> org.apache.spark.sql.catalyst.plans.logical.LogicalPlan$$anonfun$1.apply(LogicalPlan.scala:59)
>  at 
> org.apache.spark.sql.catalyst.plans.logical.LogicalPlan$$anonfun$1.apply(LogicalPlan.scala:59)
>  at 
> org.apache.spark.sql.catalyst.trees.TreeNode$$anonfun$4.apply(TreeNode.scala:306)
>  at 
> org.apache.spark.sql.catalyst.trees.TreeNode.mapProductIterator(TreeNode.scala:187)
>  at 
> org.apache.spark.sql.catalyst.trees.TreeNode.mapChildren(TreeNode.scala:304)
>  at 
> org.apache.spark.sql.catalyst.plans.logical.LogicalPlan.resolveOperators(LogicalPlan.scala:59)
>  at 
> org.apache.spark.sql.catalyst.plans.logical.LogicalPlan$$anonfun$1.apply(LogicalPlan.scala:59)
>  at 
> org.apache.spark.sql.catalyst.plans.logical.LogicalPlan$$anonfun$1.apply(LogicalPlan.scala:59)
>  at 
> org.apache.spark.sql.catalyst.trees.TreeNode$$anonfun$4.apply(TreeNode.scala:306)
>  at 
> org.apache.spark.sql.catalyst.trees.TreeNode.mapProductIterator(TreeNode.scala:187)
>  at 
> org.apache.spark.sql.catalyst.trees.TreeNode.mapChildren(TreeNode.scala:304)
>  at 
> org.apache.spark.sql.catalyst.plans.logical.LogicalPlan.resolveOperators(LogicalPlan.scala:59)
>  at 
> org.apache.spark.sql.catalyst.analysis.Analyzer$ResolveRelations$.apply(Analyzer.scala:624)
>  at 
> org.apache.spark.sql.catalyst.analysis.Analyzer$ResolveRelations$.apply(Analyzer.scala:570)
>  at 
> org.apache.spark.sql.catalyst.rules.RuleExecutor$$anonfun$execute$1$$anonfun$apply$1.apply(RuleExecutor.scala:85)
>  at 
> org.apache.spark.sql.catalyst.rules.RuleExecutor$$anonfun$execute$1$$anonfun$apply$1.apply(RuleExecutor.scala:82)
>  at 
> scala.collection.LinearSeqOptimized$class.foldLeft(LinearSeqOptimized.scala:124)
>  at scala.collection.immutable.List.foldLeft(List.scala:84)
>  at 
> org.apache.spark.sql.catalyst.rules.RuleExecutor$$anonfun$execute$1.apply(RuleExecutor.scala:82)
>  at 
> org.apache.spark.sql.catalyst.rules.RuleExecutor$$anonfun$execute$1.apply(RuleExecutor.scala:74)
>  at scala.collection.immutable.List.foreach(List.scala:381)
>  at 
> org.apache.spark.sql.catalyst.rules.RuleExecutor.execute(RuleExecutor.scala:74)
>  at 
> org.apache.spark.sql.execution.QueryExecution.analyzed$lzycompute(QueryExecution.scala:69)
>  at 
> org.apache.spark.sql.execution.QueryExecution.analyzed(QueryExecution.scala:67)
>  at 
> 

[jira] [Created] (AMBARI-23065) Remove dependency on org.apache.httpcomponents:httpclient before version 4.3.5.1 for Ambari Server

[Sandor Molnar (JIRA)]

Sandor Molnar created AMBARI-23065:
--

 Summary: Remove dependency on org.apache.httpcomponents:httpclient 
before version 4.3.5.1 for Ambari Server
 Key: AMBARI-23065
 URL: https://issues.apache.org/jira/browse/AMBARI-23065
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.6.2
Reporter: Sandor Molnar
Assignee: Sandor Molnar
 Fix For: 2.6.2, 2.7.0


Remove dependency on org.apache.httpcomponents:httpclient:jar before version 
4.3.5.1 due to security concerns. See
 * CVE-2015-5262 - [https://nvd.nist.gov/vuln/detail/CVE-2015-5262]
 * CVE-2014-3577 - [https://nvd.nist.gov/vuln/detail/CVE-2014-3577]

{noformat}
--- maven-dependency-plugin:2.8:tree(default-cli) @ ambari-server ---
 org.apache.ambari:ambari-server:jar:2.6.1.0.0
 +- org.apache.httpcomponents:httpclient:jar:4.2.5:compile
 +- org.apache.ambari:ambari-metrics-common:jar:2.6.1.0.0:compile
 |  \- (org.apache.httpcomponents:httpclient:jar:4.2.5:compile - omitted for 
duplicate)
 +- org.apache.hadoop:hadoop-auth:jar:2.7.2:compile
 |  \- (org.apache.httpcomponents:httpclient:jar:4.2.5:compile - omitted for 
duplicate)
 \- org.apache.hadoop:hadoop-common:jar:2.7.2:compile
\- net.java.dev.jets3t:jets3t:jar:0.9.0:compile
   \- (org.apache.httpcomponents:httpclient:jar:4.1.2:compile - omitted for 
conflict with 4.2.5)
 {noformat}
 * 
 * 
[Options|https://hortonworks.jira.com/browse/BUG-97133?filter=54432]

h2.  



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

[jira] [Updated] (AMBARI-23064) Remove dependency on com.fasterxml.jackson.core:jackson-databind before version 2.9.4 for Ambari Server

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot updated AMBARI-23064:

Labels: black-duck pull-request-available  (was: black-duck)

> Remove dependency on com.fasterxml.jackson.core:jackson-databind before 
> version 2.9.4 for Ambari Server
> ---
>
> Key: AMBARI-23064
> URL: https://issues.apache.org/jira/browse/AMBARI-23064
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Blocker
>  Labels: black-duck, pull-request-available
> Fix For: 2.6.2, 2.7.0
>
>
> Remove dependency on com.fasterxml.jackson.core:jackson-databind before 
> version 2.9.4 due to security concerns. See
>  * CVE-2018-5968 - [https://nvd.nist.gov/vuln/detail/CVE-2018-5968]
>  * CVE-2017-17485 - [https://nvd.nist.gov/vuln/detail/CVE-2017-17485]
> {noformat}
>  --- maven-dependency-plugin:2.8:tree (default-cli) @ ambari-server ---
>  org.apache.ambari:ambari-server:jar:2.6.1.0.0
>  \- com.networknt:json-schema-validator:jar:0.1.10:test
> \- com.fasterxml.jackson.core:jackson-databind:jar:2.8.7:test
> {noformat}



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

[jira] [Resolved] (AMBARI-23004) Create initial version of InstanceManager to create instance layout

[Dmytro Sen (JIRA)]

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

Dmytro Sen resolved AMBARI-23004.
-
Resolution: Fixed

> Create initial version of InstanceManager to create instance layout 
> 
>
> Key: AMBARI-23004
> URL: https://issues.apache.org/jira/browse/AMBARI-23004
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-agent
>Affects Versions: 3.0.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Major
>  Labels: pull-request-available
> Fix For: 3.0.0
>
>  Time Spent: 5h 50m
>  Remaining Estimate: 0h
>
> We need an instance manager tool for managing the lifecycle of mpack 
> instances, service instances, component instances. This will be the 
> replacement for hdp-select, conf-select
> Examples of few operations that we will need
> # create-mpack-instance
> # create-component-instance
> # set-component-instance-version
> # get-component-instance-version
> # get-component-instance-confdir



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

[jira] [Resolved] (AMBARI-22946) Download client configs API failing with 500 server error

[Attila Magyar (JIRA)]

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

Attila Magyar resolved AMBARI-22946.

   Resolution: Fixed
Fix Version/s: 2.7.0

updated HDP3.0 stack code

> Download client configs API failing with 500 server error
> -
>
> Key: AMBARI-22946
> URL: https://issues.apache.org/jira/browse/AMBARI-22946
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-sever
>Affects Versions: 2.6.2
>Reporter: Kishor Ramakrishnan
>Assignee: Attila Magyar
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.6.2, 2.7.0
>
>  Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> Download client configs API failing with 500 server error
> {code:java}
> http://:/api/v1/clusters/cl1/components?format=client_config_tar
> http://:/api/v1/clusters/cl1/hosts//host_components?format=client_config_tar
> { "status": 500, "message": 
> "org.apache.ambari.server.controller.spi.SystemException: Execution of 
> \"ambari-python-wrap 
> /var/lib/ambari-server/resources/common-services/KERBEROS/1.10.3-10/package/scripts/kerberos_client.py
>  generate_configs 
> /var/lib/ambari-server/data/tmp/KERBEROS_CLIENT2999359502875665328-configuration.json
>  /var/lib/ambari-server/resources/common-services/KERBEROS/1.10.3-10/package 
> /var/lib/ambari-server/data/tmp/structured-out.json INFO 
> /var/lib/ambari-server/data/tmp\" returned 1. java.lang.Throwable: Traceback 
> (most recent call last):\n File 
> \"/var/lib/ambari-server/resources/common-services/KERBEROS/1.10.3-10/package/scripts/kerberos_client.py\",
>  line 20, in \n from kerberos_common import *\n File 
> \"/var/lib/ambari-server/resources/common-services/KERBEROS/1.10.3-10/package/scripts/kerberos_common.py\",
>  line 32, in \n from ambari_agent import Constants\nImportError: No 
> module named ambari_agent\n" }
> {code}



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

[jira] [Reopened] (AMBARI-22946) Download client configs API failing with 500 server error

[Attila Magyar (JIRA)]

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

Attila Magyar reopened AMBARI-22946:


> Download client configs API failing with 500 server error
> -
>
> Key: AMBARI-22946
> URL: https://issues.apache.org/jira/browse/AMBARI-22946
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-sever
>Affects Versions: 2.6.2
>Reporter: Kishor Ramakrishnan
>Assignee: Attila Magyar
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.6.2
>
>  Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> Download client configs API failing with 500 server error
> {code:java}
> http://:/api/v1/clusters/cl1/components?format=client_config_tar
> http://:/api/v1/clusters/cl1/hosts//host_components?format=client_config_tar
> { "status": 500, "message": 
> "org.apache.ambari.server.controller.spi.SystemException: Execution of 
> \"ambari-python-wrap 
> /var/lib/ambari-server/resources/common-services/KERBEROS/1.10.3-10/package/scripts/kerberos_client.py
>  generate_configs 
> /var/lib/ambari-server/data/tmp/KERBEROS_CLIENT2999359502875665328-configuration.json
>  /var/lib/ambari-server/resources/common-services/KERBEROS/1.10.3-10/package 
> /var/lib/ambari-server/data/tmp/structured-out.json INFO 
> /var/lib/ambari-server/data/tmp\" returned 1. java.lang.Throwable: Traceback 
> (most recent call last):\n File 
> \"/var/lib/ambari-server/resources/common-services/KERBEROS/1.10.3-10/package/scripts/kerberos_client.py\",
>  line 20, in \n from kerberos_common import *\n File 
> \"/var/lib/ambari-server/resources/common-services/KERBEROS/1.10.3-10/package/scripts/kerberos_common.py\",
>  line 32, in \n from ambari_agent import Constants\nImportError: No 
> module named ambari_agent\n" }
> {code}



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

[jira] [Commented] (AMBARI-23048) Remove unsecure dependencies from Ambari Groovy Shell

[Hudson (JIRA)]

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

Hudson commented on AMBARI-23048:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #620 (See 
[https://builds.apache.org/job/Ambari-branch-2.6/620/])
AMBARI-23048. Remove unsecure dependencies from Ambari Groovy Shell (m.magyar3: 
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=f7de90723b6bf148c871eb8b283ff64f0b363dd0])
* (edit) ambari-shell/ambari-groovy-shell/pom.xml


> Remove unsecure dependencies from Ambari Groovy Shell
> -
>
> Key: AMBARI-23048
> URL: https://issues.apache.org/jira/browse/AMBARI-23048
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-shell
>Affects Versions: 2.6.2
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
>  Labels: pull-request-available
> Fix For: trunk, 2.6.2
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> * Remove dependency on org.apache.zookeeper:zookeeper before version 
> 3.4.6.2.0.0.0-579 for Ambari Groovy Shell
> * Remove dependency on xerces:xercesImpl before version 2.11.2 for Ambari 
> Groovy Shell
> * Remove dependency on tomcat:jasper-compiler and tomcat:jasper-runtime 
> before version 6.0.20.0 for Ambari Groovy Shell
> * Remove dependency on org.apache.httpcomponents:httpclient before version 
> 4.3.5.1 for Ambari Groovy Shell
> * Remove dependency on commons-httpclient:commons-httpclient before version 
> 3.1.0 for Ambari Groovy Shell
> * Remove dependency on commons-collections:commons-collections:jar before 
> version 3.2.2 for Ambari Groovy Shell
> * Remove dependency on commons-beanutils:commons-beanutils-core before 
> version 1.9.2 for Ambari Groovy Shell



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

[jira] [Commented] (AMBARI-23063) "Stale Alerts" alert has to be re-done properly

[Hudson (JIRA)]

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

Hudson commented on AMBARI-23063:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8772 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/8772/])
AMBARI-23063. "Stale Alerts" alert has to be re-done properly (aonishuk) 
(aonishuk: 
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=6e6b4a1d74b46b501c9b071aae1f849502871b3f])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/events/listeners/alerts/AlertReceivedListener.java
* (edit) ambari-agent/src/main/python/ambari_agent/InitializerModule.py
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/alerts/AlertRunnable.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/agent/stomp/AlertDefinitionsHolder.java
* (edit) ambari-agent/src/main/python/ambari_agent/alerts/base_alert.py
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/events/listeners/alerts/AlertDefinitionsUIUpdateListener.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertReceivedListenerTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/alerts/AmbariPerformanceRunnable.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/alerts/StaleAlertRunnableTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/agent/stomp/dto/AlertCluster.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/state/Cluster.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/agent/HeartBeatHandler.java
* (add) 
ambari-server/src/test/java/org/apache/ambari/server/alerts/AlertHelperTest.java
* (add) ambari-agent/src/main/python/ambari_agent/StaleAlertsMonitor.py
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/alerts/AmbariPerformanceRunnableTest.java
* (edit) ambari-agent/src/main/python/ambari_agent/AlertStatusReporter.py
* (edit) 
ambari-agent/src/main/python/ambari_agent/ClusterAlertDefinitionsCache.py
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertResourceProvider.java
* (add) 
ambari-server/src/main/java/org/apache/ambari/server/agent/StaleAlert.java
* (add) 
ambari-server/src/main/java/org/apache/ambari/server/state/alert/AlertHelper.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/alerts/StaleAlertRunnable.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/state/cluster/AlertDataManagerTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/agent/HeartBeat.java
* (edit) ambari-agent/src/main/python/ambari_agent/HeartbeatThread.py
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java


> "Stale Alerts" alert has to be re-done properly
> ---
>
> Key: AMBARI-23063
> URL: https://issues.apache.org/jira/browse/AMBARI-23063
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-23063.patch
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>




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

[jira] [Updated] (AMBARI-23049) Minor post merge fixes

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-23049:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Minor post merge fixes
> --
>
> Key: AMBARI-23049
> URL: https://issues.apache.org/jira/browse/AMBARI-23049
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-23049.patch, AMBARI-23049.patch, 
> AMBARI-23049.patch
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>




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

[jira] [Commented] (AMBARI-22897) Tez view button doesnt works in ambari hive views 1.5

[Akhil S Naik (JIRA)]

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

Akhil S Naik commented on AMBARI-22897:
---

Initially Hive Views 1.5 was using 'views' for tez , visualization, 
visual-explain and settings page and use the function 'this.render->into' for 
displaying the UI which was causing trouble as it was hitting the bug mentioned 
above.

I have rearranged the code such that all them will be now route's and we will 
route to corresponding routes once click on the buttons.
Pull Request Raised.


> Tez view button doesnt works in ambari hive views 1.5
> -
>
> Key: AMBARI-22897
> URL: https://issues.apache.org/jira/browse/AMBARI-22897
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.6.1
> Environment: Ambari 2.6.1
>Reporter: Akhil S Naik
>Assignee: Akhil S Naik
>Priority: Major
>  Labels: patch-available
> Fix For: 3.0.0
>
> Attachments: Screen Shot 2018-02-01 at 8.00.17 PM.png
>
>
> *Issue :* 
> Login to ambari version 2.6.1 navigate to hive view 1.5
> When click on tez button or visualization or visual explain  or settings 
> button
> the page throws a script error and it become a blank page 
> *Root Cause :*
> when click on the tez button, visualization or any other side button , 
> the following error is thrown from ember :
> Assertion Failed: You attempted to render into 'index' but it was not found
> attached the image error



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

[jira] [Updated] (AMBARI-23064) Remove dependency on com.fasterxml.jackson.core:jackson-databind before version 2.9.4 for Ambari Server

[Sandor Molnar (JIRA)]

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

Sandor Molnar updated AMBARI-23064:
---
Labels: black-duck  (was: )

> Remove dependency on com.fasterxml.jackson.core:jackson-databind before 
> version 2.9.4 for Ambari Server
> ---
>
> Key: AMBARI-23064
> URL: https://issues.apache.org/jira/browse/AMBARI-23064
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Blocker
>  Labels: black-duck
> Fix For: 2.6.2, 2.7.0
>
>
> Remove dependency on com.fasterxml.jackson.core:jackson-databind before 
> version 2.9.4 due to security concerns. See
>  * CVE-2018-5968 - [https://nvd.nist.gov/vuln/detail/CVE-2018-5968]
>  * CVE-2017-17485 - [https://nvd.nist.gov/vuln/detail/CVE-2017-17485]
> {noformat}
>  --- maven-dependency-plugin:2.8:tree (default-cli) @ ambari-server ---
>  org.apache.ambari:ambari-server:jar:2.6.1.0.0
>  \- com.networknt:json-schema-validator:jar:0.1.10:test
> \- com.fasterxml.jackson.core:jackson-databind:jar:2.8.7:test
> {noformat}



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

[jira] [Created] (AMBARI-23064) Remove dependency on com.fasterxml.jackson.core:jackson-databind before version 2.9.4 for Ambari Server

[Sandor Molnar (JIRA)]

Sandor Molnar created AMBARI-23064:
--

 Summary: Remove dependency on 
com.fasterxml.jackson.core:jackson-databind before version 2.9.4 for Ambari 
Server
 Key: AMBARI-23064
 URL: https://issues.apache.org/jira/browse/AMBARI-23064
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.6.2
Reporter: Sandor Molnar
Assignee: Sandor Molnar
 Fix For: 2.6.2, 2.7.0


Remove dependency on com.fasterxml.jackson.core:jackson-databind before version 
2.9.4 due to security concerns. See
 * CVE-2018-5968 - [https://nvd.nist.gov/vuln/detail/CVE-2018-5968]
 * CVE-2017-17485 - [https://nvd.nist.gov/vuln/detail/CVE-2017-17485]

{noformat}
 --- maven-dependency-plugin:2.8:tree (default-cli) @ ambari-server ---
 org.apache.ambari:ambari-server:jar:2.6.1.0.0
 \- com.networknt:json-schema-validator:jar:0.1.10:test
\- com.fasterxml.jackson.core:jackson-databind:jar:2.8.7:test
{noformat}



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

[jira] [Updated] (AMBARI-23063) "Stale Alerts" alert has to be re-done properly

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot updated AMBARI-23063:

Labels: pull-request-available  (was: )

> "Stale Alerts" alert has to be re-done properly
> ---
>
> Key: AMBARI-23063
> URL: https://issues.apache.org/jira/browse/AMBARI-23063
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-23063.patch
>
>




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

[jira] [Created] (AMBARI-23063) "Stale Alerts" alert has to be re-done properly

[Andrew Onischuk (JIRA)]

Andrew Onischuk created AMBARI-23063:


 Summary: "Stale Alerts" alert has to be re-done properly
 Key: AMBARI-23063
 URL: https://issues.apache.org/jira/browse/AMBARI-23063
 Project: Ambari
  Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
 Fix For: 2.7.0
 Attachments: AMBARI-23063.patch





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

[jira] [Updated] (AMBARI-23063) "Stale Alerts" alert has to be re-done properly

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-23063:
-
Attachment: AMBARI-23063.patch

> "Stale Alerts" alert has to be re-done properly
> ---
>
> Key: AMBARI-23063
> URL: https://issues.apache.org/jira/browse/AMBARI-23063
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Fix For: 2.7.0
>
> Attachments: AMBARI-23063.patch
>
>




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

[jira] [Updated] (AMBARI-23063) "Stale Alerts" alert has to be re-done properly

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-23063:
-
Status: Patch Available  (was: Open)

> "Stale Alerts" alert has to be re-done properly
> ---
>
> Key: AMBARI-23063
> URL: https://issues.apache.org/jira/browse/AMBARI-23063
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Fix For: 2.7.0
>
> Attachments: AMBARI-23063.patch
>
>




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

[jira] [Created] (AMBARI-23062) "Stale Alerts" alert has to be re-done properly

[Andrew Onischuk (JIRA)]

Andrew Onischuk created AMBARI-23062:


 Summary: "Stale Alerts" alert has to be re-done properly
 Key: AMBARI-23062
 URL: https://issues.apache.org/jira/browse/AMBARI-23062
 Project: Ambari
  Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
 Fix For: 2.7.0






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

[jira] [Created] (AMBARI-23060) "Stale Alerts" alert has to be re-done properly

[Andrew Onischuk (JIRA)]

Andrew Onischuk created AMBARI-23060:


 Summary: "Stale Alerts" alert has to be re-done properly
 Key: AMBARI-23060
 URL: https://issues.apache.org/jira/browse/AMBARI-23060
 Project: Ambari
  Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
 Fix For: 2.7.0
 Attachments: AMBARI-23060.patch

Since branch-3.0-perf changes it does not work as expected.


We need to re-design this a bit. The thing we have agreed upon is that agent
should send information to server on the alerts that were not updated for a
long time and server should mark them as stale, instead of hacking with
last_hb_timestamp





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

[jira] [Created] (AMBARI-23059) "Stale Alerts" alert has to be re-done properly

[Andrew Onischuk (JIRA)]

Andrew Onischuk created AMBARI-23059:


 Summary: "Stale Alerts" alert has to be re-done properly
 Key: AMBARI-23059
 URL: https://issues.apache.org/jira/browse/AMBARI-23059
 Project: Ambari
  Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
 Fix For: 2.7.0


Since branch-3.0-perf changes it does not work as expected.

As mentioned by Attila
the current solution to fix "stale alerts" alert  
  
is not the best one.

We need to re-design this a bit. The thing we have agreed upon is that agent
should send information to server on the alerts that were not updated for a
long time and server should mark them as stale, instead of hacking with
last_hb_timestamp





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

[jira] [Updated] (AMBARI-23061) "Stale Alerts" alert has to be re-done properly

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-23061:
-
Attachment: AMBARI-23061.patch

> "Stale Alerts" alert has to be re-done properly
> ---
>
> Key: AMBARI-23061
> URL: https://issues.apache.org/jira/browse/AMBARI-23061
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Fix For: 2.7.0
>
> Attachments: AMBARI-23061.patch
>
>




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

[jira] [Updated] (AMBARI-23060) "Stale Alerts" alert has to be re-done properly

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-23060:
-
Attachment: AMBARI-23060.patch

> "Stale Alerts" alert has to be re-done properly
> ---
>
> Key: AMBARI-23060
> URL: https://issues.apache.org/jira/browse/AMBARI-23060
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Fix For: 2.7.0
>
> Attachments: AMBARI-23060.patch
>
>
> Since branch-3.0-perf changes it does not work as expected.
> We need to re-design this a bit. The thing we have agreed upon is that agent
> should send information to server on the alerts that were not updated for a
> long time and server should mark them as stale, instead of hacking with
> last_hb_timestamp



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

[jira] [Created] (AMBARI-23061) "Stale Alerts" alert has to be re-done properly

[Andrew Onischuk (JIRA)]

Andrew Onischuk created AMBARI-23061:


 Summary: "Stale Alerts" alert has to be re-done properly
 Key: AMBARI-23061
 URL: https://issues.apache.org/jira/browse/AMBARI-23061
 Project: Ambari
  Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
 Fix For: 2.7.0
 Attachments: AMBARI-23061.patch





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