[jira] [Created] (AMBARI-23619) Mpack Advisor Python Module

[Scott Duan (JIRA)]

Scott Duan created AMBARI-23619:
---

 Summary: Mpack Advisor Python Module
 Key: AMBARI-23619
 URL: https://issues.apache.org/jira/browse/AMBARI-23619
 Project: Ambari
  Issue Type: New Feature
  Components: ambari-server
Affects Versions: 3.0.0
Reporter: Scott Duan
Assignee: Scott Duan
 Fix For: 3.0.0






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

[jira] [Resolved] (AMBARI-23618) Requesting non-existing metric (including wildcard) to AMS gets HTTP 500

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan resolved AMBARI-23618.

Resolution: Fixed

> Requesting non-existing metric (including wildcard) to AMS gets HTTP 500
> 
>
> Key: AMBARI-23618
> URL: https://issues.apache.org/jira/browse/AMBARI-23618
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.7.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Below links are throwing HTTP 500:
> http://:6188/ws/v1/timeline/metrics?appId=nimbus==topology.streamline-1-simple-yelp-review.3-SINK.%25.--fail-count.%25=1522734868701=1522736668701
> http://:3000/api/datasources/proxy/1/ws/v1/timeline/metrics?metricNames=topology.streamline-1-simple-yelp-review.%.--fail-count.%._avg=nimbus=1522715768=1522737368=sum
> Please note that such kind of metrics are not in metadata, but I guess we are 
> returning empty map here, not throwing HTTP 500. 



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

[jira] [Updated] (AMBARI-23618) Requesting non-existing metric (including wildcard) to AMS gets HTTP 500

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot updated AMBARI-23618:

Labels: pull-request-available  (was: )

> Requesting non-existing metric (including wildcard) to AMS gets HTTP 500
> 
>
> Key: AMBARI-23618
> URL: https://issues.apache.org/jira/browse/AMBARI-23618
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.7.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>
> Below links are throwing HTTP 500:
> http://:6188/ws/v1/timeline/metrics?appId=nimbus==topology.streamline-1-simple-yelp-review.3-SINK.%25.--fail-count.%25=1522734868701=1522736668701
> http://:3000/api/datasources/proxy/1/ws/v1/timeline/metrics?metricNames=topology.streamline-1-simple-yelp-review.%.--fail-count.%._avg=nimbus=1522715768=1522737368=sum
> Please note that such kind of metrics are not in metadata, but I guess we are 
> returning empty map here, not throwing HTTP 500. 



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

[jira] [Resolved] (AMBARI-22740) Rename ambari metrics collector package to org.apache.ambari.metrics

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan resolved AMBARI-22740.

Resolution: Fixed

> Rename ambari metrics collector package to org.apache.ambari.metrics
> 
>
> Key: AMBARI-22740
> URL: https://issues.apache.org/jira/browse/AMBARI-22740
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-metrics
>Affects Versions: 2.7.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-22740-3.patch
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> Fixing all integration tests in AMS timeline-service module. 
> Renamed 'org.apache.hadoop.yarn.server.applicationhistoryservice' package to 
> 'org.apache.ambari.metrics'.



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

[jira] [Created] (AMBARI-23618) Requesting non-existing metric (including wildcard) to AMS gets HTTP 500

[Aravindan Vijayan (JIRA)]

Aravindan Vijayan created AMBARI-23618:
--

 Summary: Requesting non-existing metric (including wildcard) to 
AMS gets HTTP 500
 Key: AMBARI-23618
 URL: https://issues.apache.org/jira/browse/AMBARI-23618
 Project: Ambari
  Issue Type: Bug
  Components: ambari-metrics
Affects Versions: 2.7.0
Reporter: Aravindan Vijayan
Assignee: Aravindan Vijayan
 Fix For: 2.7.0


Below links are throwing HTTP 500:

http://:6188/ws/v1/timeline/metrics?appId=nimbus==topology.streamline-1-simple-yelp-review.3-SINK.%25.--fail-count.%25=1522734868701=1522736668701

http://:3000/api/datasources/proxy/1/ws/v1/timeline/metrics?metricNames=topology.streamline-1-simple-yelp-review.%.--fail-count.%._avg=nimbus=1522715768=1522737368=sum

Please note that such kind of metrics are not in metadata, but I guess we are 
returning empty map here, not throwing HTTP 500. 




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

[jira] [Updated] (AMBARI-23617) Change cardinality for Zeppelin

[Vitaly Brodetskyi (JIRA)]

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

Vitaly Brodetskyi updated AMBARI-23617:
---
Status: Patch Available  (was: Open)

> Change cardinality for Zeppelin
> ---
>
> Key: AMBARI-23617
> URL: https://issues.apache.org/jira/browse/AMBARI-23617
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.7.0
>
>
> User should be able to add more than 1 Zeppelin and Livy servers.



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

[jira] [Created] (AMBARI-23617) Change cardinality for Zeppelin

[Vitaly Brodetskyi (JIRA)]

Vitaly Brodetskyi created AMBARI-23617:
--

 Summary: Change cardinality for Zeppelin
 Key: AMBARI-23617
 URL: https://issues.apache.org/jira/browse/AMBARI-23617
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
 Fix For: 2.7.0


User should be able to add more than 1 Zeppelin and Livy servers.



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

[jira] [Updated] (AMBARI-23616) Change cardinality for SHS

[Vitaly Brodetskyi (JIRA)]

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

Vitaly Brodetskyi updated AMBARI-23616:
---
Status: Patch Available  (was: Open)

> Change cardinality for SHS
> --
>
> Key: AMBARI-23616
> URL: https://issues.apache.org/jira/browse/AMBARI-23616
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.7.0
>
>
> User should be able to add more than 1 SHS.



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

[jira] [Created] (AMBARI-23616) Change cardinality for SHS

[Vitaly Brodetskyi (JIRA)]

Vitaly Brodetskyi created AMBARI-23616:
--

 Summary: Change cardinality for SHS
 Key: AMBARI-23616
 URL: https://issues.apache.org/jira/browse/AMBARI-23616
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
 Fix For: 2.7.0


User should be able to add more than 1 SHS.



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

[jira] [Resolved] (AMBARI-23614) Move NameNode wizard is stuck on Review step after enabling federation

[Andrii Babiichuk (JIRA)]

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

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

Merged to trunk

> Move NameNode wizard is stuck on Review step after enabling federation
> --
>
> Key: AMBARI-23614
> URL: https://issues.apache.org/jira/browse/AMBARI-23614
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> - Infinite spinner is displayed
> - 'Next' button is disabled
> - JS error is thrown: {{app.js:31501 Uncaught TypeError: Cannot read property 
> 'indexOf' of undefined}}



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

[jira] [Created] (AMBARI-23615) Header missing in Step2 Select hosts page in NN Federation Wizard

[Vivek Rathod (JIRA)]

Vivek Rathod created AMBARI-23615:
-

 Summary: Header missing in Step2 Select hosts page in NN 
Federation Wizard
 Key: AMBARI-23615
 URL: https://issues.apache.org/jira/browse/AMBARI-23615
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.7.0
 Environment: ambari-server --hash
22cf9683c7c6d5dc0f84a2fd312ef14326ec9d35 
Reporter: Vivek Rathod
 Fix For: 2.7.0
 Attachments: Screen Shot 2018-04-18 at 1.50.43 PM.png

Header missing in Step2 Select hosts page in NN Federation Wizard. All other 
pages have proper headers



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

[jira] [Updated] (AMBARI-23590) Return mpack info even when attempting to register duplicate mpack

[Madhuvanthi Radhakrishnan (JIRA)]

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

Madhuvanthi Radhakrishnan updated AMBARI-23590:
---
Status: Patch Available  (was: In Progress)

> Return mpack info even when attempting to register duplicate mpack
> --
>
> Key: AMBARI-23590
> URL: https://issues.apache.org/jira/browse/AMBARI-23590
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
>Priority: Major
>  Labels: pull-request-available
> Fix For: 3.0.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> When registering an mpack, if the mpack has already been registered, the 
> server returns a 409. However, we also need the server to return the same 
> data that it returns when the mpack is initially registered (most 
> importantly, the registered mpack ID). This is required so that we can have 
> the UI behave the same way – the operation needs to appear idempotent, even 
> if the response code is a 409.



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

[jira] [Updated] (AMBARI-23590) Return mpack info even when attempting to register duplicate mpack

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot updated AMBARI-23590:

Labels: pull-request-available  (was: )

> Return mpack info even when attempting to register duplicate mpack
> --
>
> Key: AMBARI-23590
> URL: https://issues.apache.org/jira/browse/AMBARI-23590
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
>Priority: Major
>  Labels: pull-request-available
> Fix For: 3.0.0
>
>
> When registering an mpack, if the mpack has already been registered, the 
> server returns a 409. However, we also need the server to return the same 
> data that it returns when the mpack is initially registered (most 
> importantly, the registered mpack ID). This is required so that we can have 
> the UI behave the same way – the operation needs to appear idempotent, even 
> if the response code is a 409.



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

[jira] [Updated] (AMBARI-23610) Enable NameNode HA fails after Ambari Upgrade due to AttributeError

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot updated AMBARI-23610:

Labels: pull-request-available  (was: )

> Enable NameNode HA fails after Ambari Upgrade due to AttributeError
> ---
>
> Key: AMBARI-23610
> URL: https://issues.apache.org/jira/browse/AMBARI-23610
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.7.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>
> STR
> # Install a Ambari Cluster with Ambari 2.6.1
> # Upgrade to Ambari 2.7
> # Try to enable NameNode HA
> Result:
> {noformat}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode.py",
>  line 143, in 
> JournalNode().execute()
>   File 
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", 
> line 353, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode.py",
>  line 39, in install
> import params
>   File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/params.py",
>  line 25, in 
> from params_linux import *
>   File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py",
>  line 330, in 
> if hostname.lower() in nn_host.lower() or public_hostname.lower() in 
> nn_host.lower():
> AttributeError: 'NoneType' object has no attribute 'lower'
> {noformat}
> Problem:
> {noformat:title=command*json}
> "public_hostname": null
> {noformat}



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

[jira] [Updated] (AMBARI-23610) Enable NameNode HA fails after Ambari Upgrade due to AttributeError

[Doroszlai, Attila (JIRA)]

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

Doroszlai, Attila updated AMBARI-23610:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Enable NameNode HA fails after Ambari Upgrade due to AttributeError
> ---
>
> Key: AMBARI-23610
> URL: https://issues.apache.org/jira/browse/AMBARI-23610
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.7.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> STR
> # Install a Ambari Cluster with Ambari 2.6.1
> # Upgrade to Ambari 2.7
> # Try to enable NameNode HA
> Result:
> {noformat}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode.py",
>  line 143, in 
> JournalNode().execute()
>   File 
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", 
> line 353, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode.py",
>  line 39, in install
> import params
>   File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/params.py",
>  line 25, in 
> from params_linux import *
>   File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py",
>  line 330, in 
> if hostname.lower() in nn_host.lower() or public_hostname.lower() in 
> nn_host.lower():
> AttributeError: 'NoneType' object has no attribute 'lower'
> {noformat}
> Problem:
> {noformat:title=command*json}
> "public_hostname": null
> {noformat}



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

[jira] [Updated] (AMBARI-23612) Wizards do not load correctly when opening from different browser

[Vivek Rathod (JIRA)]

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

Vivek Rathod updated AMBARI-23612:
--
Attachment: Screen Shot 2018-04-17 at 2.14.29 PM.png
Screen Shot 2018-04-13 at 4.39.52 PM.png

> Wizards do not load correctly when opening from different browser
> -
>
> Key: AMBARI-23612
> URL: https://issues.apache.org/jira/browse/AMBARI-23612
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.7.0
> Environment: ambari-server --hash
> 5507ee62ae19676fbf35b889b602648a54185289
>Reporter: Vivek Rathod
>Priority: Major
> Fix For: 2.7.0
>
> Attachments: Screen Shot 2018-04-17 at 2.14.29 PM.png, Screen Shot 
> 2018-04-17 at 2.17.56 PM.png
>
>
> Wizards do not load when opening from different browser
> STR: Launch any wizard like Add New HDFS Namespace or Move master wizard. 
> While in the middle of the wizard, try to open it in another browser
> Verified the Move master wizard with ambari 262 build and it works fine there



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

[jira] [Updated] (AMBARI-23612) Wizards do not load correctly when opening from different browser

[Vivek Rathod (JIRA)]

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

Vivek Rathod updated AMBARI-23612:
--
Attachment: (was: Screen Shot 2018-04-13 at 4.39.52 PM.png)

> Wizards do not load correctly when opening from different browser
> -
>
> Key: AMBARI-23612
> URL: https://issues.apache.org/jira/browse/AMBARI-23612
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.7.0
> Environment: ambari-server --hash
> 5507ee62ae19676fbf35b889b602648a54185289
>Reporter: Vivek Rathod
>Priority: Major
> Fix For: 2.7.0
>
> Attachments: Screen Shot 2018-04-17 at 2.14.29 PM.png, Screen Shot 
> 2018-04-17 at 2.17.56 PM.png
>
>
> Wizards do not load when opening from different browser
> STR: Launch any wizard like Add New HDFS Namespace or Move master wizard. 
> While in the middle of the wizard, try to open it in another browser
> Verified the Move master wizard with ambari 262 build and it works fine there



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

[jira] [Updated] (AMBARI-23612) Wizards do not load correctly when opening from different browser

[Vivek Rathod (JIRA)]

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

Vivek Rathod updated AMBARI-23612:
--
Attachment: Screen Shot 2018-04-17 at 2.17.56 PM.png

> Wizards do not load correctly when opening from different browser
> -
>
> Key: AMBARI-23612
> URL: https://issues.apache.org/jira/browse/AMBARI-23612
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.7.0
> Environment: ambari-server --hash
> 5507ee62ae19676fbf35b889b602648a54185289
>Reporter: Vivek Rathod
>Priority: Major
> Fix For: 2.7.0
>
> Attachments: Screen Shot 2018-04-17 at 2.14.29 PM.png, Screen Shot 
> 2018-04-17 at 2.17.56 PM.png
>
>
> Wizards do not load when opening from different browser
> STR: Launch any wizard like Add New HDFS Namespace or Move master wizard. 
> While in the middle of the wizard, try to open it in another browser
> Verified the Move master wizard with ambari 262 build and it works fine there



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

[jira] [Updated] (AMBARI-23614) Move NameNode wizard is stuck on Review step after enabling federation

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot updated AMBARI-23614:

Labels: pull-request-available  (was: )

> Move NameNode wizard is stuck on Review step after enabling federation
> --
>
> Key: AMBARI-23614
> URL: https://issues.apache.org/jira/browse/AMBARI-23614
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>
> - Infinite spinner is displayed
> - 'Next' button is disabled
> - JS error is thrown: {{app.js:31501 Uncaught TypeError: Cannot read property 
> 'indexOf' of undefined}}



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

[jira] [Created] (AMBARI-23614) Move NameNode wizard is stuck on Review step after enabling federation

[Andrii Babiichuk (JIRA)]

Andrii Babiichuk created AMBARI-23614:
-

 Summary: Move NameNode wizard is stuck on Review step after 
enabling federation
 Key: AMBARI-23614
 URL: https://issues.apache.org/jira/browse/AMBARI-23614
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.7.0
Reporter: Andrii Babiichuk
Assignee: Andrii Babiichuk
 Fix For: 2.7.0


- Infinite spinner is displayed
- 'Next' button is disabled
- JS error is thrown: {{app.js:31501 Uncaught TypeError: Cannot read property 
'indexOf' of undefined}}



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

[jira] [Created] (AMBARI-23613) View instances not created by default

[Srikanth Janardhan (JIRA)]

Srikanth Janardhan created AMBARI-23613:
---

 Summary: View instances not created by default
 Key: AMBARI-23613
 URL: https://issues.apache.org/jira/browse/AMBARI-23613
 Project: Ambari
  Issue Type: Bug
  Components: ambari-views
Affects Versions: 2.7.0
Reporter: Srikanth Janardhan
 Fix For: 2.7.0


In ambari-2.7.0, the view instances are not created by default. 

In previous versions, the instances of YARN, Files, Hive, Hive 2.0, Smartsense 
and Tez  were created automatically. 



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

[jira] [Created] (AMBARI-23612) Wizards do not load correctly when opening from different browser

[Vivek Rathod (JIRA)]

Vivek Rathod created AMBARI-23612:
-

 Summary: Wizards do not load correctly when opening from different 
browser
 Key: AMBARI-23612
 URL: https://issues.apache.org/jira/browse/AMBARI-23612
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.7.0
 Environment: ambari-server --hash
5507ee62ae19676fbf35b889b602648a54185289
Reporter: Vivek Rathod
 Fix For: 2.7.0


Wizards do not load when opening from different browser

STR: Launch any wizard like Add New HDFS Namespace or Move master wizard. While 
in the middle of the wizard, try to open it in another browser

Verified the Move master wizard with ambari 262 build and it works fine there



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

[jira] [Created] (AMBARI-23611) Add Service Group to various start/stop/restart API calls

[Jason Golieb (JIRA)]

Jason Golieb created AMBARI-23611:
-

 Summary: Add Service Group to various start/stop/restart API calls
 Key: AMBARI-23611
 URL: https://issues.apache.org/jira/browse/AMBARI-23611
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 3.0.0
Reporter: Jason Golieb
Assignee: Jason Golieb
 Fix For: 3.0.0


The UI exposes various Start, Stop, and Restart API calls which now must be 
updated to include Service Groups. The functions in scope for this issue are:

* Start/Stop All Services
* Restart All Stale Services
* Restart Service on Selected Hosts
* Restart Service (on all hosts)
* Restart Component (on specific Host)
* Restart Stale Components (on specific Host)
* Restart All Components (on specific Host)
* Configure Client (restart client component)
* Service Check

For these functions, in the body of the {{RequestInfo, resource_filters}} are 
used to actually target the intended recipients of the command (when not using 
a specific URL). Any time that the resource_filter contains a service_name, we 
will add service_group_name. If multiple service groups are in scope, then the 
resource_filter will be duplicated for each service group.

There are two exceptions to this pattern that are also in scope:
 * Start/Stop Service - these requests are made to the specific service 
endpoint, and the service group will be indicated in the URL
 * Start/Stop (Host) Component - these requests are made to the specific host 
component endpoint, and the specific component is targeted either by including 
its ID in the URL (which obviates the need to indicate the service group) or by 
including identifying information (including the service group) in the request 
body.



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

[jira] [Updated] (AMBARI-23609) Credential store is not working

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot updated AMBARI-23609:

Labels: pull-request-available  (was: )

> Credential store is not working
> ---
>
> Key: AMBARI-23609
> URL: https://issues.apache.org/jira/browse/AMBARI-23609
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>
> The command json element "configuration_credentials" are not present in the 
> command jsons on the agents, though they are present on the server side 
> command json (at least it is present in the json persisted at 
> HostRoleCommand.constructExecutionCommandEntity(HostRoleCommand:239)). This 
> causes that the credential store is not working, as this command json element 
> is essential.



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

[jira] [Updated] (AMBARI-23610) Enable NameNode HA fails after Ambari Upgrade due to AttributeError

[Doroszlai, Attila (JIRA)]

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

Doroszlai, Attila updated AMBARI-23610:
---
Status: Patch Available  (was: Open)

> Enable NameNode HA fails after Ambari Upgrade due to AttributeError
> ---
>
> Key: AMBARI-23610
> URL: https://issues.apache.org/jira/browse/AMBARI-23610
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.7.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 2.7.0
>
>
> STR
> # Install a Ambari Cluster with Ambari 2.6.1
> # Upgrade to Ambari 2.7
> # Try to enable NameNode HA
> Result:
> {noformat}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode.py",
>  line 143, in 
> JournalNode().execute()
>   File 
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", 
> line 353, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode.py",
>  line 39, in install
> import params
>   File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/params.py",
>  line 25, in 
> from params_linux import *
>   File 
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py",
>  line 330, in 
> if hostname.lower() in nn_host.lower() or public_hostname.lower() in 
> nn_host.lower():
> AttributeError: 'NoneType' object has no attribute 'lower'
> {noformat}
> Problem:
> {noformat:title=command*json}
> "public_hostname": null
> {noformat}



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

[jira] [Created] (AMBARI-23610) Enable NameNode HA fails after Ambari Upgrade due to AttributeError

[Doroszlai, Attila (JIRA)]

Doroszlai, Attila created AMBARI-23610:
--

 Summary: Enable NameNode HA fails after Ambari Upgrade due to 
AttributeError
 Key: AMBARI-23610
 URL: https://issues.apache.org/jira/browse/AMBARI-23610
 Project: Ambari
  Issue Type: Bug
  Components: ambari-agent
Affects Versions: 2.7.0
Reporter: Doroszlai, Attila
Assignee: Doroszlai, Attila
 Fix For: 2.7.0


STR

# Install a Ambari Cluster with Ambari 2.6.1
# Upgrade to Ambari 2.7
# Try to enable NameNode HA

Result:

{noformat}
Traceback (most recent call last):
  File 
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode.py",
 line 143, in 
JournalNode().execute()
  File 
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", 
line 353, in execute
method(env)
  File 
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode.py",
 line 39, in install
import params
  File 
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/params.py",
 line 25, in 
from params_linux import *
  File 
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py",
 line 330, in 
if hostname.lower() in nn_host.lower() or public_hostname.lower() in 
nn_host.lower():
AttributeError: 'NoneType' object has no attribute 'lower'
{noformat}

Problem:

{noformat:title=command*json}
"public_hostname": null
{noformat}



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

[jira] [Updated] (AMBARI-23553) Unable to delete Slider after Ambari upgrade, due to Hive dependency

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot updated AMBARI-23553:

Labels: express_upgrade pull-request-available  (was: express_upgrade)

> Unable to delete Slider after Ambari upgrade, due to Hive dependency
> 
>
> Key: AMBARI-23553
> URL: https://issues.apache.org/jira/browse/AMBARI-23553
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Vivek Sharma
>Assignee: Attila Magyar
>Priority: Blocker
>  Labels: express_upgrade, pull-request-available
> Fix For: 2.7.0
>
>
> *STR*
>  # Deploy HDP-2.6.3.0 with Ambari-2.6.0.0 (that stack includes services such 
> as Slider, Mahout etc. which are unsupported in HDP-3.0 stack)
>  # Upgrade Ambari to 2.7.0.0
>  # Try to delete Slider (this is required since stack upgrade to HDP-3.0 
> needs the unsupported services to be removed)
> *Result*
> Slider prompts to delete Hive due to dependency
> We need to remove the dependency, else asking customer to delete Hive may not 
> be viable



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

[jira] [Created] (AMBARI-23609) Credential store is not working

[Dmytro Sen (JIRA)]

Dmytro Sen created AMBARI-23609:
---

 Summary: Credential store is not working
 Key: AMBARI-23609
 URL: https://issues.apache.org/jira/browse/AMBARI-23609
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.7.0
Reporter: Dmytro Sen
Assignee: Dmytro Sen
 Fix For: 2.7.0


The command json element "configuration_credentials" are not present in the 
command jsons on the agents, though they are present on the server side command 
json (at least it is present in the json persisted at 
HostRoleCommand.constructExecutionCommandEntity(HostRoleCommand:239)). This 
causes that the credential store is not working, as this command json element 
is essential.



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

[jira] [Commented] (AMBARI-23599) It is hectic whether or not a setting a property attribute in the service advisor gets into the recommendations

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander commented on AMBARI-23599:
--

Committed to trunk

> It is hectic whether or not a setting a property attribute in the service 
> advisor gets into the recommendations
> ---
>
> Key: AMBARI-23599
> URL: https://issues.apache.org/jira/browse/AMBARI-23599
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Expected behavior of the field "HA HSI namespace":
> When the switch is off, it should not be visible.
> When the switch is on, and 1 host is selected, it should not be visible.
> When the switch is on, and 2 hosts are selected then it should be visible.
> Experienced behavior:
> At first it is not visible. If I select two hosts, it is still not visible, 
> though the service advisor sets the visibility attribute to true. When I 
> discard it, it is visible, as for some reason the service advisor sees that 
> there are two HSI hosts, though there are none, I've just discarded it.
> I've added a message in the service advisor log starting "Setting the 
> visibily of hive.server2.active.passive.ha.registry.namespace to" to make it 
> easier to see what decision it made.
>  



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

[jira] [Updated] (AMBARI-23599) It is hectic whether or not a setting a property attribute in the service advisor gets into the recommendations

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander updated AMBARI-23599:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> It is hectic whether or not a setting a property attribute in the service 
> advisor gets into the recommendations
> ---
>
> Key: AMBARI-23599
> URL: https://issues.apache.org/jira/browse/AMBARI-23599
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Expected behavior of the field "HA HSI namespace":
> When the switch is off, it should not be visible.
> When the switch is on, and 1 host is selected, it should not be visible.
> When the switch is on, and 2 hosts are selected then it should be visible.
> Experienced behavior:
> At first it is not visible. If I select two hosts, it is still not visible, 
> though the service advisor sets the visibility attribute to true. When I 
> discard it, it is visible, as for some reason the service advisor sees that 
> there are two HSI hosts, though there are none, I've just discarded it.
> I've added a message in the service advisor log starting "Setting the 
> visibily of hive.server2.active.passive.ha.registry.namespace to" to make it 
> easier to see what decision it made.
>  



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

[jira] [Resolved] (AMBARI-23600) cluster name validation issue in ADMIN view

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander resolved AMBARI-23600.
--
Resolution: Fixed

> cluster name validation issue in ADMIN view
> ---
>
> Key: AMBARI-23600
> URL: https://issues.apache.org/jira/browse/AMBARI-23600
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.7.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Cluster name is limited to 100 characters. Need to remove all another UI 
> validation



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

[jira] [Comment Edited] (AMBARI-23600) cluster name validation issue in ADMIN view

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander edited comment on AMBARI-23600 at 4/18/18 12:08 PM:


Committed to trunk


was (Author: aantonenko):
Committed to master

> cluster name validation issue in ADMIN view
> ---
>
> Key: AMBARI-23600
> URL: https://issues.apache.org/jira/browse/AMBARI-23600
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.7.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Cluster name is limited to 100 characters. Need to remove all another UI 
> validation



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

[jira] [Commented] (AMBARI-23600) cluster name validation issue in ADMIN view

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander commented on AMBARI-23600:
--

Committed to master

> cluster name validation issue in ADMIN view
> ---
>
> Key: AMBARI-23600
> URL: https://issues.apache.org/jira/browse/AMBARI-23600
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.7.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Cluster name is limited to 100 characters. Need to remove all another UI 
> validation



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

[jira] [Resolved] (AMBARI-23608) Unable to update credentials of a remotely registered cluster

[Andrii Babiichuk (JIRA)]

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

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

Merged to trunk

> Unable to update credentials of a remotely registered cluster
> -
>
> Key: AMBARI-23608
> URL: https://issues.apache.org/jira/browse/AMBARI-23608
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> *STR*
> # Register a remote cluster with Ambari server
> # Go to Admin - Remote Cluster page and select the cluster
> # Hit 'Update Credentials' and supply new/existing admin credentials of 
> remote cluster
> # Hit Update
> Result: Credentials are not updated and UI shows an error



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

[jira] [Updated] (AMBARI-23587) Ambari Schema Upgrade Failing source 2.6.1.0 target 2.7.0.0

[Doroszlai, Attila (JIRA)]

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

Doroszlai, Attila updated AMBARI-23587:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Ambari Schema Upgrade Failing source 2.6.1.0 target 2.7.0.0
> ---
>
> Key: AMBARI-23587
> URL: https://issues.apache.org/jira/browse/AMBARI-23587
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Pradarttana
>Assignee: Doroszlai, Attila
>Priority: Critical
>  Labels: pull-request-available, upgrade
> Fix For: 2.7.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> {code:title=ambari-server.log}
> 16 Apr 2018 11:04:47,676 INFO [main] DBAccessorImpl:876 - Executing query: 
> ALTER TABLE stage ADD status VARCHAR2(255) NULL
> 16 Apr 2018 11:04:47,695 ERROR [main] SchemaUpgradeHelper:207 - Upgrade 
> failed.
> java.sql.SQLSyntaxErrorException: ORA-00904: "PENDING": invalid identifier
> at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:447)
>  at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
>  at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:951)
>  at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:513)
>  at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:227)
>  at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)
>  at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:195)
>  at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:1036)
>  at 
> oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1336)
>  at 
> oracle.jdbc.driver.OracleStatement.executeUpdateInternal(OracleStatement.java:1845)
>  at 
> oracle.jdbc.driver.OracleStatement.executeUpdate(OracleStatement.java:1810)
>  at 
> oracle.jdbc.driver.OracleStatementWrapper.executeUpdate(OracleStatementWrapper.java:294)
>  at 
> org.apache.ambari.server.orm.DBAccessorImpl.updateTable(DBAccessorImpl.java:829)
>  at 
> org.apache.ambari.server.orm.DBAccessorImpl.addColumn(DBAccessorImpl.java:632)
>  at 
> org.apache.ambari.server.upgrade.UpgradeCatalog270.updateStageTable(UpgradeCatalog270.java:842)
>  at 
> org.apache.ambari.server.upgrade.UpgradeCatalog270.executeDDLUpdates(UpgradeCatalog270.java:283)
>  at 
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:973)
>  at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:205)
>  at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:448)
> 16 Apr 2018 11:04:47,695 ERROR [main] SchemaUpgradeHelper:473 - Exception 
> occurred during upgrade, failed
> org.apache.ambari.server.AmbariException: ORA-00904: "PENDING": invalid 
> identifier
> at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:208)
>  at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:448)
> Caused by: java.sql.SQLSyntaxErrorException: ORA-00904: "PENDING": invalid 
> identifier
> at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:447)
>  at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
>  at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:951)
>  at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:513)
>  at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:227)
>  at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)
>  at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:195)
>  at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:1036)
>  at 
> oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1336)
>  at 
> oracle.jdbc.driver.OracleStatement.executeUpdateInternal(OracleStatement.java:1845)
>  at 
> oracle.jdbc.driver.OracleStatement.executeUpdate(OracleStatement.java:1810)
>  at 
> oracle.jdbc.driver.OracleStatementWrapper.executeUpdate(OracleStatementWrapper.java:294)
>  at 
> org.apache.ambari.server.orm.DBAccessorImpl.updateTable(DBAccessorImpl.java:829)
>  at 
> org.apache.ambari.server.orm.DBAccessorImpl.addColumn(DBAccessorImpl.java:632)
>  at 
> org.apache.ambari.server.upgrade.UpgradeCatalog270.updateStageTable(UpgradeCatalog270.java:842)
>  at 
> org.apache.ambari.server.upgrade.UpgradeCatalog270.executeDDLUpdates(UpgradeCatalog270.java:283)
>  at 
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:973)
>  at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:205)
>  ... 1 more
> {code}



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

[jira] [Updated] (AMBARI-21816) test_kms_server timing issue

[Doroszlai, Attila (JIRA)]

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

Doroszlai, Attila updated AMBARI-21816:
---
Fix Version/s: (was: 3.0.0)
   trunk

> test_kms_server timing issue
> 
>
> Key: AMBARI-21816
> URL: https://issues.apache.org/jira/browse/AMBARI-21816
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Doroszlai, Attila
>Priority: Minor
> Fix For: trunk
>
>
> Python unit test in {{test_kms_server}} occasionally fails due to timing.  
> Expected and actual output use two separate calls to get current time, which 
> may be different if happens to be executed around the turn of a second.
> {noformat}
> FAIL: test_start_secured (test_kms_server.TestRangerKMS)
> --
> Traceback (most recent call last):
>   File 
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-common/src/test/python/mock/mock.py",
>  line 1199, in patched
> return func(*args, **keywargs)
>   File 
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/stacks/2.5/RANGER_KMS/test_kms_server.py",
>  line 522, in test_start_secured
> mode = 0644
>   File 
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
>  line 330, in assertResourceCalled
> self.assertEquals(kwargs, resource.arguments)
> AssertionError: {'owner': 'kms', 'content': '\n2017-08-25 
> 11:02:46\n< [truncated]... != {'content': 
> '\n2017-08-25 11:02:45\n', 'owne 
> [truncated]...
> - {'content': '\n2017-08-25 11:02:46\n',
> ?   ^
> + {'content': '\n2017-08-25 11:02:45\n',
> ?   ^
> -  'group': 'kms',
> +  'group': u'kms',
> ?   +
>'mode': 420,
> -  'owner': 'kms'}
> +  'owner': u'kms'}
> ?   +
> {noformat}
> Affected code: {{test_start_default}} and {{test_start_secured}} in 
> {{ambari-server/src/test/python/stacks/2.5/RANGER_KMS/test_kms_server.py}}.



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

[jira] [Updated] (AMBARI-22853) NFS Gateway is not logging at the correct location

[Andrew Onischuk (JIRA)]

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

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

Committed to trunk

> NFS Gateway is not logging at the correct location
> --
>
> Key: AMBARI-22853
> URL: https://issues.apache.org/jira/browse/AMBARI-22853
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 3.0.0
>
> Attachments: AMBARI-22853.patch
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> /grid/0/log/**hdfs//hadoop-hdfs-root-
> nfs3-ctr-e137-1514896590304-8236-01-02.hwx.site.out**
> 
> 
> 
> [root@ctr-e137-1514896590304-8236-01-02 ~]# cd /grid/0/log/hdfs/
> [root@ctr-e137-1514896590304-8236-01-02 hdfs]# ls -ltr
> total 500
> -rw--- 1 root root0 Jan  9 22:52 
> hadoop-hdfs-root-nfs3-ctr-e137-1514896590304-8236-01-02.hwx.site.out
> -rw--- 1 hdfs hadoop  0 Jan  9 22:52 SecurityAuth.audit
> -rw-r--r-- 1 root root  714 Jan  9 22:52 
> privileged-root-nfs3-ctr-e137-1514896590304-8236-01-02.hwx.site.out
> -rw--- 1 root root  117 Jan  9 23:00 
> privileged-root-nfs3-ctr-e137-1514896590304-8236-01-02.hwx.site.err
> drwxrwxr-x 2 root hadoop   4096 Jan  9 23:54 root
> drwxr-xr-x 2 hdfs hadoop   4096 Jan  9 23:59 hdfs
> -rw--- 1 hdfs hadoop 493804 Jan 10 00:58 
> hadoop-hdfs-root-nfs3-ctr-e137-1514896590304-8236-01-02.hwx.site.log
> [root@ctr-e137-1514896590304-8236-01-02 hdfs]# ps -ef| grep nfs
> root   10637   1  0 Jan09 ?00:00:00 jsvc.exec -Dproc_nfs3 
> -outfile 
> /grid/0/log/hdfs//hadoop-hdfs-root-nfs3-ctr-e137-1514896590304-8236-01-02.hwx.site.out
>  -errfile 
> /grid/0/log/hdfs//privileged-root-nfs3-ctr-e137-1514896590304-8236-01-02.hwx.site.err
>  -pidfile /var/run/hadoop//hadoop-hdfs-root-nfs3.pid -nodetach -user hdfs -cp 
> 

[jira] [Updated] (AMBARI-23434) Fix stack issues in HDFS to support Namenode Federation setup

[Andrew Onischuk (JIRA)]

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

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

Committed to trunk

> Fix stack issues in HDFS to support Namenode Federation setup
> -
>
> Key: AMBARI-23434
> URL: https://issues.apache.org/jira/browse/AMBARI-23434
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-23434.patch
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> For example, here are 2 things I found to be probably wrong.
> 1\. Journal node restart failed because we cannot find hdfs-site :
> dfs.journalnode.edits.dir. We delete that property in the wizard. We may have
> to change that to dfs.journalnode.edits.dir.nameservice
> 2\. The following snippet in params_linux.py on HDFS 3.0 stack seems wrong. It
> has been designed to work with only 1 nameservice.
> 
> 
> 
> dfs_ha_enabled = False
> dfs_ha_nameservices = 
> default('/configurations/hdfs-site/dfs.internal.nameservices', None)
> if dfs_ha_nameservices is None:
>   dfs_ha_nameservices = 
> default('/configurations/hdfs-site/dfs.nameservices', None)
> dfs_ha_namenode_ids = 
> default(format("/configurations/hdfs-site/dfs.ha.namenodes.{dfs_ha_nameservices}"),
>  None)
> 
> 3\. After setting up NN Fed, when I restart namenodes, I see the following
> error.
> 
> 
> 
> main_resource.resource.security_enabled, 
> main_resource.resource.logoutput)
>   File 
> "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
>  line 154, in __init__
> security_enabled, run_user)
>   File 
> "/usr/lib/ambari-agent/lib/resource_management/libraries/functions/namenode_ha_utils.py",
>  line 204, in get_property_for_active_namenode
> if INADDR_ANY in value and rpc_key in hdfs_site:
>   File 
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/config_dictionary.py",
>  line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found 
> in configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 
> 'dfs.namenode.https-address.ns2.nn1' was not found in configurations 
> dictionary!
> 
> This is probably because the namenode_ha_utils is not equipped to handle
> multiple nameservices.
> We may have to create to fix such stack errors when the wizard is done.



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

[jira] [Updated] (AMBARI-23490) NN Federation Wizard: Bootstrap NameNode failed

[Andrew Onischuk (JIRA)]

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

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

Committed to trunk

> NN Federation Wizard: Bootstrap NameNode failed
> ---
>
> Key: AMBARI-23490
> URL: https://issues.apache.org/jira/browse/AMBARI-23490
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-23490.patch, AMBARI-23490.patch
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Bootstrap NameNode command fails due to stopped NameNode. Actually NameNode
> should be started and command to start it was sent correctly from UI, but was
> ignored by BE due to:
> 
> 
> Ignoring ServiceComponentHost as the current state matches the new 
> desired state, clusterName=c, serviceName=HDFS, componentName=NAMENODE, 
> hostname=c7404.ambari.apache.org, currentState=STARTED, 
> newDesiredState=STARTED
> This is because Format NameNode command starts NameNode for a little period of
> time and then stops it back, but component's current state is not updated
> immediately and BE thinks that NameNode is still started.  
> From Format NameNode log:
> 
> 
> 
> 18/04/04 11:44:31 INFO namenode.NameNode: STARTUP_MSG: 
> /
> STARTUP_MSG: Starting NameNode
> 
> ...
> 
> 18/04/04 11:44:35 INFO namenode.NameNode: SHUTDOWN_MSG: 
> /
> SHUTDOWN_MSG: Shutting down NameNode at 
> c7404.ambari.apache.org/192.168.74.104
> 



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

[jira] [Updated] (AMBARI-23511) Format ZKFC fails while adding new HDFS namespace through UI in secure environment

[Andrew Onischuk (JIRA)]

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

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

Committed to trunk

> Format ZKFC fails while adding new HDFS namespace through UI in secure 
> environment
> --
>
> Key: AMBARI-23511
> URL: https://issues.apache.org/jira/browse/AMBARI-23511
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-23511.patch
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Tried to add new HDFS namespace with latest available build from yesterday
> evening #262  
> Format ZKFC is failing with below error
> 
> 
> 
> 18/04/05 16:30:10 INFO zookeeper.ClientCnxn: Session establishment 
> complete on server 
> ctr-e138-1518143905142-202626-01-06.hwx.site/172.27.29.151:2181, 
> sessionid = 0x26293f2ead15e74, negotiated timeout = 9000
> 18/04/05 16:30:10 INFO ha.ActiveStandbyElector: Session connected.
> 18/04/05 16:30:10 ERROR ha.ZKFailoverController: The failover controller 
> encounters runtime error
> java.io.IOException: Couldn't create /hadoop-ha/ns1
>   at 
> org.apache.hadoop.ha.ActiveStandbyElector.ensureParentZNode(ActiveStandbyElector.java:358)
>   at 
> org.apache.hadoop.ha.ZKFailoverController.formatZK(ZKFailoverController.java:286)
>   at 
> org.apache.hadoop.ha.ZKFailoverController.doRun(ZKFailoverController.java:216)
>   at 
> org.apache.hadoop.ha.ZKFailoverController.access$000(ZKFailoverController.java:60)
>   at 
> org.apache.hadoop.ha.ZKFailoverController$1.run(ZKFailoverController.java:175)
>   at 
> org.apache.hadoop.ha.ZKFailoverController$1.run(ZKFailoverController.java:171)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:360)
>   at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1662)
>   at 
> org.apache.hadoop.security.SecurityUtil.doAsLoginUserOrFatal(SecurityUtil.java:480)
>   at 
> org.apache.hadoop.ha.ZKFailoverController.run(ZKFailoverController.java:171)
>   at 
> org.apache.hadoop.hdfs.tools.DFSZKFailoverController.main(DFSZKFailoverController.java:195)
> Caused by: org.apache.zookeeper.KeeperException$NoAuthException: 
> KeeperErrorCode = NoAuth for /hadoop-ha/ns1
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:113)
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
>   at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:783)
>   at 
> org.apache.hadoop.ha.ActiveStandbyElector$3.run(ActiveStandbyElector.java:1033)
>   at 
> org.apache.hadoop.ha.ActiveStandbyElector$3.run(ActiveStandbyElector.java:1030)
>   at 
> org.apache.hadoop.ha.ActiveStandbyElector.zkDoWithRetries(ActiveStandbyElector.java:1095)
>   at 
> org.apache.hadoop.ha.ActiveStandbyElector.zkDoWithRetries(ActiveStandbyElector.java:1087)
>   at 
> org.apache.hadoop.ha.ActiveStandbyElector.createWithRetries(ActiveStandbyElector.java:1030)
>   at 
> org.apache.hadoop.ha.ActiveStandbyElector.ensureParentZNode(ActiveStandbyElector.java:347)
>   ... 11 more
> 18/04/05 16:30:11 INFO zookeeper.ZooKeeper: Session: 0x26293f2ead15e74 
> closed
> 18/04/05 16:30:11 FATAL tools.DFSZKFailoverController: 
> DFSZKFailOverController exiting due to earlier exception java.io.IOException: 
> Couldn't create /hadoop-ha/ns1
> 18/04/05 16:30:11 INFO zookeeper.ClientCnxn: EventThread shut down
> 18/04/05 16:30:11 INFO util.ExitUtil: Exiting with status 1: 
> java.io.IOException: Couldn't create /hadoop-ha/ns1
> 18/04/05 16:30:11 INFO tools.DFSZKFailoverController: SHUTDOWN_MSG: 
> /
> SHUTDOWN_MSG: Shutting down DFSZKFailoverController at 
> ctr-e138-1518143905142-202626-01-05.hwx.site/172.27.26.14
> /
> 



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

[jira] [Updated] (AMBARI-23502) Format Namenode step in NN Fed wizard should pass in HDFS ClusterId as argument.

[Andrew Onischuk (JIRA)]

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

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

Committed to trunk

> Format Namenode step in NN Fed wizard should pass in HDFS ClusterId as 
> argument.
> 
>
> Key: AMBARI-23502
> URL: https://issues.apache.org/jira/browse/AMBARI-23502
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Fix For: 2.7.0
>
> Attachments: AMBARI-23502.patch
>
>




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

[jira] [Updated] (AMBARI-23536) Fix TestCustomServiceOrchestrator.py and TestRegistration.py on branch-3.0-perf

[Andrew Onischuk (JIRA)]

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

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

Committed to trunk

> Fix TestCustomServiceOrchestrator.py and TestRegistration.py on 
> branch-3.0-perf
> ---
>
> Key: AMBARI-23536
> URL: https://issues.apache.org/jira/browse/AMBARI-23536
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-23536.patch
>
>  Time Spent: 4h 20m
>  Remaining Estimate: 0h
>
> TestCustomServiceOchestrator requires rewriting since configs building routine
> changed quite a lot on branch-3.0-perf



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

[jira] [Updated] (AMBARI-23412) Knox service check fails if parameters from ambari-env.sh are necessary for python command

[Andrew Onischuk (JIRA)]

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

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

Committed to trunk and branch-2.6

> Knox service check fails if parameters from ambari-env.sh are necessary for 
> python command
> --
>
> Key: AMBARI-23412
> URL: https://issues.apache.org/jira/browse/AMBARI-23412
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.6.2
>
> Attachments: AMBARI-23412.patch, AMBARI-23412.patch
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>




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

[jira] [Updated] (AMBARI-23222) Ambari-agent fails to connect to server with two_way_auth enabled

[Andrew Onischuk (JIRA)]

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

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

Committed to trunk

> Ambari-agent fails to connect to server with two_way_auth enabled
> -
>
> Key: AMBARI-23222
> URL: https://issues.apache.org/jira/browse/AMBARI-23222
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-23222.patch
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> ERROR 2018-03-13 17:15:04,264 security.py:122 - Could not connect to 
> wss://ctr-e138-1518143905142-94896-01-02.hwx.site:8441/agent/stomp/v1
> Traceback (most recent call last):
>   File "/usr/lib/ambari-agent/lib/ambari_agent/security.py", line 113, in 
> establish_connection
> conn.start()
>   File "/usr/lib/ambari-agent/lib/ambari_stomp/connect.py", line 46, in 
> start
> self.transport.start()
>   File "/usr/lib/ambari-agent/lib/ambari_stomp/transport.py", line 109, 
> in start
> self.attempt_connection()
>   File "/usr/lib/ambari-agent/lib/ambari_stomp/adapter/websocket.py", 
> line 89, in attempt_connection
> self.ws.connect()
>   File "/usr/lib/ambari-agent/lib/ambari_ws4py/client/__init__.py", line 
> 216, in connect
> self.sock.connect(self.bind_addr)
>   File "/usr/lib64/python2.7/ssl.py", line 869, in connect
> self._real_connect(addr, False)
>   File "/usr/lib64/python2.7/ssl.py", line 860, in _real_connect
> self.do_handshake()
>   File "/usr/lib64/python2.7/ssl.py", line 833, in do_handshake
> self._sslobj.do_handshake()
> SSLError: [SSL: SSLV3_ALERT_BAD_CERTIFICATE] sslv3 alert bad certificate 
> (_ssl.c:579)
> 



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

[jira] [Updated] (AMBARI-23330) Bump up ws4py websocket lib version from 0.4.2 to 0.5.1 to fix connection drop

[Andrew Onischuk (JIRA)]

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

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

Committed to trunk

> Bump up ws4py websocket lib version from 0.4.2 to 0.5.1 to fix connection drop
> --
>
> Key: AMBARI-23330
> URL: https://issues.apache.org/jira/browse/AMBARI-23330
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-23330.patch
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>




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

[jira] [Updated] (AMBARI-23560) Refactor base_alert to support multiple nameservices

[Andrew Onischuk (JIRA)]

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

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

Committed to trunk

> Refactor base_alert to support multiple nameservices
> 
>
> Key: AMBARI-23560
> URL: https://issues.apache.org/jira/browse/AMBARI-23560
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-23560.patch
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> _NameNode Web UI_ alert is in critical state for all NameNodes with the
> 
> 
> 
> [Alert][namenode_webui] HA nameservice value is present but there are no 
> aliases for {{hdfs-site/dfs.ha.namenodes.ns1,ns2}}
> 



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

[jira] [Updated] (AMBARI-23373) Fix formatZKFC

[Andrew Onischuk (JIRA)]

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

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

Committed to trunk

> Fix formatZKFC
> --
>
> Key: AMBARI-23373
> URL: https://issues.apache.org/jira/browse/AMBARI-23373
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-23373.patch
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> resource_management.core.exceptions.Fail: Script '/var/lib/ambari-
> agent/cache/stacks/HDP/3.0/services/HDFS/package/scripts/zkfc_slave.py' has no
> method 'format'



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

[jira] [Updated] (AMBARI-23337) Remove python3 files from ws4py since they can cause build failure

[Andrew Onischuk (JIRA)]

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

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

Committed to trunk

> Remove python3 files from ws4py since they can cause build failure
> --
>
> Key: AMBARI-23337
> URL: https://issues.apache.org/jira/browse/AMBARI-23337
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-23337.patch
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> On some envs (not reproducible for me) it can result in failure like this:
> 
> 
> 2018/03/22 23:49:21 INFO: [INFO]   File 
> "/usr/lib/ambari-agent/lib/ambari_ws4py/async_websocket.py", line 85
> 2018/03/22 23:49:21 INFO: [INFO] yield from 
> self.proto.writer.drain()
> 2018/03/22 23:49:21 INFO: [INFO]  ^
> 2018/03/22 23:49:21 INFO: [INFO] SyntaxError: invalid syntax
> 2018/03/22 23:49:21 INFO: [INFO] 
> 2018/03/22 23:49:21 INFO: [INFO] Compiling 
> /grid/0/jenkins/workspace/Zuul_Ambari_Build_Job/build-support/SOURCES/ambari/ambari-agent/target/rpm/ambari-agent/buildroot/usr/lib/ambari-agent/lib/ambari_ws4py/server/tulipserver.py
>  ...
> 2018/03/22 23:49:21 INFO: [INFO]   File 
> "/usr/lib/ambari-agent/lib/ambari_ws4py/server/tulipserver.py", line 101
> 2018/03/22 23:49:21 INFO: [INFO] request_line = yield from 
> self.next_line()
> 2018/03/22 23:49:21 INFO: [INFO] ^
> 2018/03/22 23:49:21 INFO: [INFO] SyntaxError: invalid syntax
> 2018/03/22 23:49:21 INFO: [INFO] 
> 



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

[jira] [Updated] (AMBARI-23323) Locking configure to single process causes deadlock

[Andrew Onischuk (JIRA)]

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

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

Committed to trunk

> Locking configure to single process causes deadlock
> ---
>
> Key: AMBARI-23323
> URL: https://issues.apache.org/jira/browse/AMBARI-23323
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-23323.patch
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> 1\. Component1 needs component2 to be started to do configure  
> 2\. Component1 grabs the lock and retries in configure  
> 3\. Component2 cannot grab the lock waiting forever
> This causes variety of timeout errors in different components.  
> Than finally one component will fail with at the end
> 
> 
> 2018-03-22 08:53:01,593 - Trying to acquire a lock on 
> /var/lib/ambari-agent/tmp/link_configs_lock_file
> 



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

[jira] [Updated] (AMBARI-23305) Grafana install fails with "KeyError: 'getpwnam(): name not found: ams'"

[Andrew Onischuk (JIRA)]

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

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

Committed to trunk

> Grafana install fails with "KeyError: 'getpwnam(): name not found: ams'"
> 
>
> Key: AMBARI-23305
> URL: https://issues.apache.org/jira/browse/AMBARI-23305
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-23305.patch, AMBARI-23305.patch, 
> AMBARI-23305.patch, AMBARI-23305.patch, AMBARI-23305.patch, AMBARI-23305.patch
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>




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

[jira] [Updated] (AMBARI-23359) When credential store is enabled status commands should not generate jceks

[Andrew Onischuk (JIRA)]

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

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

Committed to trunk

> When credential store is enabled status commands should not generate jceks
> --
>
> Key: AMBARI-23359
> URL: https://issues.apache.org/jira/browse/AMBARI-23359
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-23359.patch
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Status commands should not generate jceks as they don't need them. This was
> the behavior in previous release.
> Currently jceks are generated for every status command, flooding ambari-agent
> logs and making status commands run unnecessary longer.



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

[jira] [Updated] (AMBARI-23105) Exception caught while installing Timeline Service V2.0

[Andrew Onischuk (JIRA)]

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

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

Committed to trunk

> Exception caught while installing Timeline Service V2.0 
> 
>
> Key: AMBARI-23105
> URL: https://issues.apache.org/jira/browse/AMBARI-23105
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-23105.patch
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> While installing Timeline Service V2.0 during CI run, the following error is
> captured:
> 
> 
> Caught an exception while executing custom service command:  'exceptions.Exception'>: Command requires configs with 
> timestamp=1519782088331 but configs on agent have timestamp=1519783511993; 
> Command requires configs with timestamp=1519782088331 but configs on agent 
> have timestamp=1519783511993
> 
> See  (up until 8pm ET 3/1)



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

[jira] [Updated] (AMBARI-23211) Hive client Installation is failing

[Andrew Onischuk (JIRA)]

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

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

Committed to trunk

> Hive client Installation is failing 
> 
>
> Key: AMBARI-23211
> URL: https://issues.apache.org/jira/browse/AMBARI-23211
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-23211.patch
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>




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

[jira] [Updated] (AMBARI-22896) Fix TestAlertSchedulerHandler.py and TestAlerts.py

[Andrew Onischuk (JIRA)]

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

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

Committed to trunk

> Fix TestAlertSchedulerHandler.py and TestAlerts.py
> --
>
> Key: AMBARI-22896
> URL: https://issues.apache.org/jira/browse/AMBARI-22896
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-22896.patch, AMBARI-22896.patch
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> How the configs and alerts definitions are consumed by the alerts framework
> has completely changed on branch-3.0-perf so most alert-related tests require
> rewriting.



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

[jira] [Updated] (AMBARI-23000) Timeline Service V2.0 reader install fails if wget is not already installed on the host

[Andrew Onischuk (JIRA)]

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

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

Committed to trunk

> Timeline Service V2.0 reader install fails if wget is not already installed 
> on the host
> ---
>
> Key: AMBARI-23000
> URL: https://issues.apache.org/jira/browse/AMBARI-23000
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Fix For: 3.0.0
>
> Attachments: AMBARI-23000.patch, AMBARI-23000.patch, 
> AMBARI-23000.patch, AMBARI-23000.patch, AMBARI-23000.patch
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> Encountered while testing Atlantic Beta 1.  
> Timeline Service V2.0 reader install fails if wget is already not installed on
> the host beforehand.
> 
> 
> stderr: 
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/timelinereader.py",
>  line 101, in 
> ApplicationTimelineReader().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 376, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/timelinereader.py",
>  line 45, in install
> hbase_service.install_hbase(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/YARN/3.0.0.3.0/package/scripts/hbase_service.py",
>  line 82, in install_hbase
> Execute(hbase_download_cmd, user="root", logoutput=True)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 
> 166, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 160, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 124, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 72, in inner
> result = function(command, **kwargs)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 102, in checked_call
> tries=tries, try_sleep=try_sleep, 
> timeout_kill_strategy=timeout_kill_strategy)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 'umask 
> 0022;wget --no-cookies --no-check-certificate 
> http://public-repo-1.hortonworks.com/ARTIFACTS/dist/hbase/1.2.6/hadoop-2.7.5/hbase-1.2.6-bin.tar.gz
>  && tar -xzf hbase-1.2.6-bin.tar.gz && rm -rf hbase-1.2.6-bin.tar.gz && rm 
> -rf /usr/hdp/3.0.0.0-809/hadoop-yarn-hbase && mv hbase-* 
> /usr/hdp/3.0.0.0-809/hadoop-yarn-hbase' returned 127. -bash: wget: command 
> not found
>  stdout:
> 2018-02-13 07:39:31,705 - Stack Feature Version Info: Cluster Stack=3.0, 
> Command Stack=None, Command Version=None -> 3.0
> 2018-02-13 07:39:31,711 - Using hadoop conf dir: 
> /usr/hdp/current/hadoop-client/conf
> 2018-02-13 07:39:31,713 - Group['livy'] {}
> 2018-02-13 07:39:31,714 - Group['spark'] {}
> 2018-02-13 07:39:31,714 - Group['hdfs'] {}
> 2018-02-13 07:39:31,714 - Group['zeppelin'] {}
> 2018-02-13 07:39:31,714 - Group['hadoop'] {}
> 2018-02-13 07:39:31,715 - Group['users'] {}
> 2018-02-13 07:39:31,715 - Group['knox'] {}
> 2018-02-13 07:39:31,716 - User['hive'] {'gid': 'hadoop', 
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-02-13 07:39:31,717 - User['zookeeper'] {'gid': 'hadoop', 
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-02-13 07:39:31,718 - User['infra-solr'] {'gid': 'hadoop', 
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-02-13 07:39:31,719 - User['atlas'] {'gid': 'hadoop', 
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-02-13 07:39:31,720 - User['ams'] {'gid': 'hadoop', 
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 

[jira] [Updated] (AMBARI-23515) Rearranging configuration file creation for Ranger Plugins.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot updated AMBARI-23515:

Labels: pull-request-available  (was: )

> Rearranging configuration file creation for Ranger Plugins.
> ---
>
> Key: AMBARI-23515
> URL: https://issues.apache.org/jira/browse/AMBARI-23515
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>
> When enabling Ranger plug-ins for Storm, Knox and Kafka certain configuration 
> files are created for the plug-in enabled components, need to re-arrange 
> logic to create the configuration files to allow better flexibility.



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

[jira] [Updated] (AMBARI-23608) Unable to update credentials of a remotely registered cluster

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot updated AMBARI-23608:

Labels: pull-request-available  (was: )

> Unable to update credentials of a remotely registered cluster
> -
>
> Key: AMBARI-23608
> URL: https://issues.apache.org/jira/browse/AMBARI-23608
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>
> *STR*
> # Register a remote cluster with Ambari server
> # Go to Admin - Remote Cluster page and select the cluster
> # Hit 'Update Credentials' and supply new/existing admin credentials of 
> remote cluster
> # Hit Update
> Result: Credentials are not updated and UI shows an error



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

[jira] [Created] (AMBARI-23608) Unable to update credentials of a remotely registered cluster

[Andrii Babiichuk (JIRA)]

Andrii Babiichuk created AMBARI-23608:
-

 Summary: Unable to update credentials of a remotely registered 
cluster
 Key: AMBARI-23608
 URL: https://issues.apache.org/jira/browse/AMBARI-23608
 Project: Ambari
  Issue Type: Bug
  Components: ambari-admin
Affects Versions: 2.7.0
Reporter: Andrii Babiichuk
Assignee: Andrii Babiichuk
 Fix For: 2.7.0


*STR*
# Register a remote cluster with Ambari server
# Go to Admin - Remote Cluster page and select the cluster
# Hit 'Update Credentials' and supply new/existing admin credentials of remote 
cluster
# Hit Update

Result: Credentials are not updated and UI shows an error



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

[jira] [Updated] (AMBARI-23585) Register VDF failing for AmazonLinux2

[Andrew Onischuk (JIRA)]

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

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

> Register VDF failing for AmazonLinux2 
> --
>
> Key: AMBARI-23585
> URL: https://issues.apache.org/jira/browse/AMBARI-23585
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Attachments: AMBARI-23585.patch, AMBARI-23585.patch, 
> AMBARI-23585.patch
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> 
> -bash-4.2# curl -v -k -u admin:admin -H "X-Requested-By:ambari" -X POST 
> http://ctr-e138-1518143905142-226218-01-02.hwx.site:8080/api/v1/version_definitions
>  -d '{ "VersionDefinition": { "version_url": 
> "http://s3.amazonaws.com/dev.hortonworks.com/HDP/amazonlinux2/3.x/BUILDS/3.0.0.0-1189/HDP-3.0.0.0-1189.xml;
>  } }'
> Note: Unnecessary use of -X or --request, POST is already inferred.
> *   Trying 172.27.80.4...
> * TCP_NODELAY set
> * Connected to ctr-e138-1518143905142-226218-01-02.hwx.site 
> (172.27.80.4) port 8080 (#0)
> * Server auth using Basic with user 'admin'
> > POST /api/v1/version_definitions HTTP/1.1
> > Host: ctr-e138-1518143905142-226218-01-02.hwx.site:8080
> > Authorization: Basic YWRtaW46YWRtaW4=
> > User-Agent: curl/7.55.1
> > Accept: */*
> > X-Requested-By:ambari
> > Content-Length: 151
> > Content-Type: application/x-www-form-urlencoded
> >
> * upload completely sent off: 151 out of 151 bytes
> < HTTP/1.1 500 Internal Server Error
> < Date: Fri, 13 Apr 2018 10:09:15 GMT
> < X-Frame-Options: DENY
> < X-XSS-Protection: 1; mode=block
> < X-Content-Type-Options: nosniff
> < Cache-Control: no-store
> < Pragma: no-cache
> < X-Content-Type-Options: nosniff
> < X-Frame-Options: DENY
> < Set-Cookie: 
> AMBARISESSIONID=node018hn2df5vsjqjuo7g1yr9mvno8.node0;Path=/;HttpOnly
> < Expires: Thu, 01 Jan 1970 00:00:00 GMT
> < User: admin
> < Content-Type: text/plain;charset=utf-8
> < Transfer-Encoding: chunked
> <
> {
>   "status" : 500,
>   "message" : "An internal system exception occurred: Could not load url 
> from 
> http://s3.amazonaws.com/dev.hortonworks.com/HDP/amazonlinux2/3.x/BUILDS/3.0.0.0-1189/HDP-3.0.0.0-1189.xml.
>   null"
> * Connection #0 to host ctr-e138-1518143905142-226218-01-02.hwx.site 
> left intact
> }-bash-4.2#
> -bash-4.2#
> 
> Build Used:
> 
> 
> 
> -bash-4.2# cat /etc/yum.repos.d/ambari.repo
> #VERSION_NUMBER=2.7.0.0-309
> [ambari-2.7.0.0-309]
> name=ambari Version - ambari-2.7.0.0-309
> 
> baseurl=http://s3.amazonaws.com/dev.hortonworks.com/ambari/amazonlinux2/2.x/BUILDS/2.7.0.0-309
> gpgcheck=1
> 
> gpgkey=http://s3.amazonaws.com/dev.hortonworks.com/ambari/amazonlinux2/2.x/BUILDS/2.7.0.0-309/RPM-GPG-KEY/RPM-GPG-KEY-Jenkins
> enabled=1
> priority=1
> 



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

[jira] [Updated] (AMBARI-23585) Register VDF failing for AmazonLinux2

[Andrew Onischuk (JIRA)]

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

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

> Register VDF failing for AmazonLinux2 
> --
>
> Key: AMBARI-23585
> URL: https://issues.apache.org/jira/browse/AMBARI-23585
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
>  Labels: pull-request-available
> Attachments: AMBARI-23585.patch, AMBARI-23585.patch, 
> AMBARI-23585.patch
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> 
> -bash-4.2# curl -v -k -u admin:admin -H "X-Requested-By:ambari" -X POST 
> http://ctr-e138-1518143905142-226218-01-02.hwx.site:8080/api/v1/version_definitions
>  -d '{ "VersionDefinition": { "version_url": 
> "http://s3.amazonaws.com/dev.hortonworks.com/HDP/amazonlinux2/3.x/BUILDS/3.0.0.0-1189/HDP-3.0.0.0-1189.xml;
>  } }'
> Note: Unnecessary use of -X or --request, POST is already inferred.
> *   Trying 172.27.80.4...
> * TCP_NODELAY set
> * Connected to ctr-e138-1518143905142-226218-01-02.hwx.site 
> (172.27.80.4) port 8080 (#0)
> * Server auth using Basic with user 'admin'
> > POST /api/v1/version_definitions HTTP/1.1
> > Host: ctr-e138-1518143905142-226218-01-02.hwx.site:8080
> > Authorization: Basic YWRtaW46YWRtaW4=
> > User-Agent: curl/7.55.1
> > Accept: */*
> > X-Requested-By:ambari
> > Content-Length: 151
> > Content-Type: application/x-www-form-urlencoded
> >
> * upload completely sent off: 151 out of 151 bytes
> < HTTP/1.1 500 Internal Server Error
> < Date: Fri, 13 Apr 2018 10:09:15 GMT
> < X-Frame-Options: DENY
> < X-XSS-Protection: 1; mode=block
> < X-Content-Type-Options: nosniff
> < Cache-Control: no-store
> < Pragma: no-cache
> < X-Content-Type-Options: nosniff
> < X-Frame-Options: DENY
> < Set-Cookie: 
> AMBARISESSIONID=node018hn2df5vsjqjuo7g1yr9mvno8.node0;Path=/;HttpOnly
> < Expires: Thu, 01 Jan 1970 00:00:00 GMT
> < User: admin
> < Content-Type: text/plain;charset=utf-8
> < Transfer-Encoding: chunked
> <
> {
>   "status" : 500,
>   "message" : "An internal system exception occurred: Could not load url 
> from 
> http://s3.amazonaws.com/dev.hortonworks.com/HDP/amazonlinux2/3.x/BUILDS/3.0.0.0-1189/HDP-3.0.0.0-1189.xml.
>   null"
> * Connection #0 to host ctr-e138-1518143905142-226218-01-02.hwx.site 
> left intact
> }-bash-4.2#
> -bash-4.2#
> 
> Build Used:
> 
> 
> 
> -bash-4.2# cat /etc/yum.repos.d/ambari.repo
> #VERSION_NUMBER=2.7.0.0-309
> [ambari-2.7.0.0-309]
> name=ambari Version - ambari-2.7.0.0-309
> 
> baseurl=http://s3.amazonaws.com/dev.hortonworks.com/ambari/amazonlinux2/2.x/BUILDS/2.7.0.0-309
> gpgcheck=1
> 
> gpgkey=http://s3.amazonaws.com/dev.hortonworks.com/ambari/amazonlinux2/2.x/BUILDS/2.7.0.0-309/RPM-GPG-KEY/RPM-GPG-KEY-Jenkins
> enabled=1
> priority=1
> 



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

[jira] [Updated] (AMBARI-23597) Config's tags should be cached

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot updated AMBARI-23597:

Labels: pull-request-available  (was: )

> Config's tags should be cached
> --
>
> Key: AMBARI-23597
> URL: https://issues.apache.org/jira/browse/AMBARI-23597
> Project: Ambari
>  Issue Type: Task
>  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
>
>
> UI often make calls to fetch current tags, which can be cached and updated on 
> WebSocket event.



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

[jira] [Resolved] (AMBARI-23470) None of the Ambari View works because of 'X-Frame-Options' to 'deny' error

[Myroslav Papirkovskyi (JIRA)]

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

Myroslav Papirkovskyi resolved AMBARI-23470.

Resolution: Fixed

Merged to trunk

> None of the Ambari View works because of  'X-Frame-Options' to 'deny' error
> ---
>
> Key: AMBARI-23470
> URL: https://issues.apache.org/jira/browse/AMBARI-23470
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views, ambari-web
>Affects Versions: trunk, 2.7.0
>Reporter: JaySenSharma
>Assignee: Myroslav Papirkovskyi
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> In Ambari 2.7.0,  While accessing any View like HiveView 2.0 we see a blank 
> page.
> On te Browser Debugger Console we see the XFrame related error as following:
> {code}
> Refused to display 
> 'http://latest1.example.com:8080/#/login?targetURI=/views/HIVE/2.0.0/Hive20/' 
> in a frame because it set 'X-Frame-Options' to 'deny'.
> Uncaught DOMException: Blocked a frame with origin 
> "http://latest1.example.com:8080; from accessing a cross-origin frame.
> at Class.resizeFunction 
> (http://latest1.example.com:8080/javascripts/app.js:237835:78)
> at http://latest1.example.com:8080/javascripts/app.js:237810:12
> {code} 



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

[jira] [Assigned] (AMBARI-23604) ParseException line 1:116 mismatched input 'ROW' expecting INTO near ')' in table buckets specification when uploading table using Hive view 2.0.

[Nitiraj Singh Rathore (JIRA)]

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

Nitiraj Singh Rathore reassigned AMBARI-23604:
--

Assignee: Nitiraj Singh Rathore

> ParseException line 1:116 mismatched input 'ROW' expecting INTO near ')' in 
> table buckets specification when uploading table using Hive view 2.0.
> -
>
> Key: AMBARI-23604
> URL: https://issues.apache.org/jira/browse/AMBARI-23604
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.6.1
> Environment: HDP 2.6.3
> Ambari 2.6.1
>Reporter: Sindhu Subhas
>Assignee: Nitiraj Singh Rathore
>Priority: Critical
> Attachments: test_csv.csv
>
>
> *Problem:*
> When uploading table using CSV file as transactional table, below is the 
> error see:
> {code:java}
> java.lang.Exception: org.apache.hive.service.cli.HiveSQLException: Error 
> while compiling statement: FAILED: ParseException line 1:116 mismatched input 
> 'ROW' expecting INTO near ')' in table buckets specification
> java.lang.Exception: org.apache.hive.service.cli.HiveSQLException: Error 
> while compiling statement: FAILED: ParseException line 1:116 mismatched input 
> 'ROW' expecting INTO near ')' in table buckets specification
>   at 
> org.apache.ambari.view.hive20.resources.jobs.JobService.getOne(JobService.java:147)
>   at sun.reflect.GeneratedMethodAccessor831.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>   at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> {code}
> *Steps to replicate:*
> 1. Upload the attached file.
> 2. Select any of the columns as 'clustered'.
> 3. Under Advanced options, enable transactional and buckets=4.
> 4. Click on create table.



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