[jira] [Resolved] (AMBARI-22518) Error while viewing topology details - Storm View
[
https://issues.apache.org/jira/browse/AMBARI-22518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanket Shah resolved AMBARI-22518.
--
Resolution: Duplicate
> Error while viewing topology details - Storm View
> -
>
> Key: AMBARI-22518
> URL: https://issues.apache.org/jira/browse/AMBARI-22518
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.6.1
> Environment: ambari-server --version
> 2.6.1.0-59
>Reporter: Supreeth Sharma
>Assignee: Sanket Shah
>Priority: Blocker
> Fix For: 2.6.1
>
>
> Steps to reproduce :
> 1) Create storm view.
> 2) Deploy the wordcount topology for storm
> 3) Navigate to storm view page
> 4) Click on wordcount topology
> Action is failing with below UI error :
> {code}
> Uncaught Error: Minified React error #130; visit
> http://facebook.github.io/react/docs/error-decoder.html?invariant=130[]=object[]=%20Check%20the%20render%20method%20of%20%60e%60.
> for the full message or use the non-minified dev environment for full errors
> and additional helpful warnings.
> at n (vendor.bundle.js:4)
> at a (vendor.bundle.js:6)
> at Object.updateChildren (vendor.bundle.js:2)
> at v._reconcilerUpdateChildren (vendor.bundle.js:3)
> at v._updateChildren (vendor.bundle.js:3)
> at v.updateChildren (vendor.bundle.js:3)
> at v._updateDOMChildren (vendor.bundle.js:2)
> at v.updateComponent (vendor.bundle.js:2)
> at v.receiveComponent (vendor.bundle.js:2)
> at Object.receiveComponent (vendor.bundle.js:2)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-22518) Error while viewing topology details - Storm View
[
https://issues.apache.org/jira/browse/AMBARI-22518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanket Shah reassigned AMBARI-22518:
Assignee: Sanket Shah
> Error while viewing topology details - Storm View
> -
>
> Key: AMBARI-22518
> URL: https://issues.apache.org/jira/browse/AMBARI-22518
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.6.1
> Environment: ambari-server --version
> 2.6.1.0-59
>Reporter: Supreeth Sharma
>Assignee: Sanket Shah
>Priority: Blocker
> Fix For: 2.6.1
>
>
> Steps to reproduce :
> 1) Create storm view.
> 2) Deploy the wordcount topology for storm
> 3) Navigate to storm view page
> 4) Click on wordcount topology
> Action is failing with below UI error :
> {code}
> Uncaught Error: Minified React error #130; visit
> http://facebook.github.io/react/docs/error-decoder.html?invariant=130[]=object[]=%20Check%20the%20render%20method%20of%20%60e%60.
> for the full message or use the non-minified dev environment for full errors
> and additional helpful warnings.
> at n (vendor.bundle.js:4)
> at a (vendor.bundle.js:6)
> at Object.updateChildren (vendor.bundle.js:2)
> at v._reconcilerUpdateChildren (vendor.bundle.js:3)
> at v._updateChildren (vendor.bundle.js:3)
> at v.updateChildren (vendor.bundle.js:3)
> at v._updateDOMChildren (vendor.bundle.js:2)
> at v.updateComponent (vendor.bundle.js:2)
> at v.receiveComponent (vendor.bundle.js:2)
> at Object.receiveComponent (vendor.bundle.js:2)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22608) Update HBASE 2.0.0.3.0 with proper pid file name for Phoenix Query Server
[ https://issues.apache.org/jira/browse/AMBARI-22608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16281263#comment-16281263 ] Hudson commented on AMBARI-22608: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8502 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8502/]) AMBARI-22608. Update HBASE 2.0.0.3.0 with proper pid file name for (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=fcc92aaeea346ebef13a70ed0cfaa686785c6a0d]) * (edit) ambari-server/src/main/resources/common-services/HBASE/2.0.0.3.0/package/scripts/status_params.py > Update HBASE 2.0.0.3.0 with proper pid file name for Phoenix Query Server > -- > > Key: AMBARI-22608 > URL: https://issues.apache.org/jira/browse/AMBARI-22608 > Project: Ambari > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Sergey Soldatov > Fix For: 3.0.0 > > Attachments: AMBARI-22608.patch > > > Phoenix Query Server has changed the pid file name, so Ambari is unable to > track that service is running. > Ambari expects "phoenix-username-server.pid" > Actual pid name is "phoenix-username-queryserver.pid" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22608) Update HBASE 2.0.0.3.0 with proper pid file name for Phoenix Query Server
[ https://issues.apache.org/jira/browse/AMBARI-22608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-22608: - Resolution: Fixed Status: Resolved (was: Patch Available) > Update HBASE 2.0.0.3.0 with proper pid file name for Phoenix Query Server > -- > > Key: AMBARI-22608 > URL: https://issues.apache.org/jira/browse/AMBARI-22608 > Project: Ambari > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Sergey Soldatov > Fix For: 3.0.0 > > Attachments: AMBARI-22608.patch > > > Phoenix Query Server has changed the pid file name, so Ambari is unable to > track that service is running. > Ambari expects "phoenix-username-server.pid" > Actual pid name is "phoenix-username-queryserver.pid" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22608) Update HBASE 2.0.0.3.0 with proper pid file name for Phoenix Query Server
[
https://issues.apache.org/jira/browse/AMBARI-22608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16281231#comment-16281231
]
Swapan Shridhar commented on AMBARI-22608:
--
Committed to trunk
{code}
commit fcc92aaeea346ebef13a70ed0cfaa686785c6a0d
Author: Swapan Shridhar
Date: Wed Dec 6 17:54:40 2017 -0800
AMBARI-22608. Update HBASE 2.0.0.3.0 with proper pid file name for Phoenix
Query Server. (Sergey Soldatov via sshridhar).
{code}
> Update HBASE 2.0.0.3.0 with proper pid file name for Phoenix Query Server
> --
>
> Key: AMBARI-22608
> URL: https://issues.apache.org/jira/browse/AMBARI-22608
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Sergey Soldatov
> Fix For: 3.0.0
>
> Attachments: AMBARI-22608.patch
>
>
> Phoenix Query Server has changed the pid file name, so Ambari is unable to
> track that service is running.
> Ambari expects "phoenix-username-server.pid"
> Actual pid name is "phoenix-username-queryserver.pid"
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (AMBARI-22608) Update HBASE 2.0.0.3.0 with proper pid file name for Phoenix Query Server
[ https://issues.apache.org/jira/browse/AMBARI-22608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16281222#comment-16281222 ] Swapan Shridhar edited comment on AMBARI-22608 at 12/7/17 1:32 AM: --- +1 for [^AMBARI-22608.patch] was (Author: swapanshridhar): +1 for [AMBARI-22608.patch] > Update HBASE 2.0.0.3.0 with proper pid file name for Phoenix Query Server > -- > > Key: AMBARI-22608 > URL: https://issues.apache.org/jira/browse/AMBARI-22608 > Project: Ambari > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Sergey Soldatov > Fix For: 3.0.0 > > Attachments: AMBARI-22608.patch > > > Phoenix Query Server has changed the pid file name, so Ambari is unable to > track that service is running. > Ambari expects "phoenix-username-server.pid" > Actual pid name is "phoenix-username-queryserver.pid" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22608) Update HBASE 2.0.0.3.0 with proper pid file name for Phoenix Query Server
[ https://issues.apache.org/jira/browse/AMBARI-22608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16281222#comment-16281222 ] Swapan Shridhar commented on AMBARI-22608: -- +1 for [AMBARI-22608.patch] > Update HBASE 2.0.0.3.0 with proper pid file name for Phoenix Query Server > -- > > Key: AMBARI-22608 > URL: https://issues.apache.org/jira/browse/AMBARI-22608 > Project: Ambari > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Sergey Soldatov > Fix For: 3.0.0 > > Attachments: AMBARI-22608.patch > > > Phoenix Query Server has changed the pid file name, so Ambari is unable to > track that service is running. > Ambari expects "phoenix-username-server.pid" > Actual pid name is "phoenix-username-queryserver.pid" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22608) Update HBASE 2.0.0.3.0 with proper pid file name for Phoenix Query Server
[ https://issues.apache.org/jira/browse/AMBARI-22608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Soldatov updated AMBARI-22608: - Status: Patch Available (was: Open) > Update HBASE 2.0.0.3.0 with proper pid file name for Phoenix Query Server > -- > > Key: AMBARI-22608 > URL: https://issues.apache.org/jira/browse/AMBARI-22608 > Project: Ambari > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Sergey Soldatov > Fix For: 3.0.0 > > Attachments: AMBARI-22608.patch > > > Phoenix Query Server has changed the pid file name, so Ambari is unable to > track that service is running. > Ambari expects "phoenix-username-server.pid" > Actual pid name is "phoenix-username-queryserver.pid" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22608) Update HBASE 2.0.0.3.0 with proper pid file name for Phoenix Query Server
[ https://issues.apache.org/jira/browse/AMBARI-22608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Soldatov updated AMBARI-22608: - Attachment: AMBARI-22608.patch > Update HBASE 2.0.0.3.0 with proper pid file name for Phoenix Query Server > -- > > Key: AMBARI-22608 > URL: https://issues.apache.org/jira/browse/AMBARI-22608 > Project: Ambari > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Sergey Soldatov > Fix For: 3.0.0 > > Attachments: AMBARI-22608.patch > > > Phoenix Query Server has changed the pid file name, so Ambari is unable to > track that service is running. > Ambari expects "phoenix-username-server.pid" > Actual pid name is "phoenix-username-queryserver.pid" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22608) Update HBASE 2.0.0.3.0 with proper pid file name for Phoenix Query Server
Sergey Soldatov created AMBARI-22608: Summary: Update HBASE 2.0.0.3.0 with proper pid file name for Phoenix Query Server Key: AMBARI-22608 URL: https://issues.apache.org/jira/browse/AMBARI-22608 Project: Ambari Issue Type: Bug Affects Versions: 3.0.0 Reporter: Sergey Soldatov Fix For: 3.0.0 Phoenix Query Server has changed the pid file name, so Ambari is unable to track that service is running. Ambari expects "phoenix-username-server.pid" Actual pid name is "phoenix-username-queryserver.pid" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22606) Service actions for R4ML not loaded
[
https://issues.apache.org/jira/browse/AMBARI-22606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16281042#comment-16281042
]
Hudson commented on AMBARI-22606:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8501 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8501/])
AMBARI-22606. Service actions for R4ML not loaded (akovalenko) (akovalenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=466379c2f8a9d0a724166bc4b3f3d9ef50bfc877])
* (edit) ambari-web/app/controllers/main/service/item.js
> Service actions for R4ML not loaded
> ---
>
> Key: AMBARI-22606
> URL: https://issues.apache.org/jira/browse/AMBARI-22606
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.1
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22606.patch, AMBARI-22606_branch-2.6.patch
>
>
> While trying to delete R4ML service, the Service actions menu doesn't load
> with next js error:
> {code}
> app.js:180350 Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.createServiceConfig (app.js:180350)
> at app.js:30065
> at Array.forEach ()
> at Object. (app.js:30060)
> at o (vendor.js:106)
> at Object.add [as done] (vendor.js:106)
> at Object. (app.js:30054)
> at o (vendor.js:106)
> at Object.fireWith (vendor.js:106)
> at Object.fire [as resolve] (vendor.js:106)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22607) Design and implement an AD job scheduler.
Aravindan Vijayan created AMBARI-22607: -- Summary: Design and implement an AD job scheduler. Key: AMBARI-22607 URL: https://issues.apache.org/jira/browse/AMBARI-22607 Project: Ambari Issue Type: Task Components: ambari-metrics Affects Versions: 3.0.0 Reporter: Aravindan Vijayan Design and implement a scheduler for starting and managing AD jobs on Spark. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-22607) Design and implement an AD job scheduler.
[ https://issues.apache.org/jira/browse/AMBARI-22607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan reassigned AMBARI-22607: -- Assignee: Aravindan Vijayan > Design and implement an AD job scheduler. > -- > > Key: AMBARI-22607 > URL: https://issues.apache.org/jira/browse/AMBARI-22607 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > > Design and implement a scheduler for starting and managing AD jobs on Spark. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22492) A bad WebHDFS request is issued when starting Hive Metastore
[
https://issues.apache.org/jira/browse/AMBARI-22492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16280996#comment-16280996
]
David Tucker commented on AMBARI-22492:
---
Excellent to see a patch for this, thanks!
I see this has been marked resolved, but it seems the patch only changes checks
in constructing the bad request. I am not familiar enough with this code to say
whether that is enough or not. If it isn't, though, this may expose HDFS-12846
in regular (i.e. non-OneFS) deployments.
> A bad WebHDFS request is issued when starting Hive Metastore
>
>
> Key: AMBARI-22492
> URL: https://issues.apache.org/jira/browse/AMBARI-22492
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: David Tucker
>Assignee: Attila Magyar
> Fix For: 2.6.1
>
> Attachments: AMBARI-22492.patch
>
>
> When deploying a cluster with Hive (1.2.1000, in this case), Ambari issues an
> incorrect WebHDFS request:
> {code}
> 2017-11-20 20:21:21,839 - call['ambari-sudo.sh su hdfs -l -s /bin/bash -c
> 'curl -sS -L -w '"'"'%{http_code}'"'"' -X GET
> '"'"'http://dtucker-rjy277d.west.isilon.com:8082/webhdfs/v1?op=GETFILESTATUS=hdfs'"'"'
> 1>/tmp/tmpzipnFe 2>/tmp/tmpbGajx_''] {'logoutput': None, 'quiet': False}
> {code}
> That command should be:
> {code}
> curl -sS -L -w '%{http_code}' -X GET
> 'http://dtucker-rjy277d.west.isilon.com:8082/webhdfs/v1/?op=GETFILESTATUS=hdfs'
> {code}
> (Note the / after v1.)
> On Apache, this results in a FileNotFoundException (404); however, this
> causes problems with OneFS which returns an IllegalArgumentException (400)
> and prevents the Metastore from starting.
> Here is the full traceback:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 203, in
>HiveMetastore().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 367, in execute
>method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 54, in start
>self.configure(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 120, in locking_configure
>original_configure(obj, *args, **kw)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 72, in configure
>hive(name = 'metastore')
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
>return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py",
> line 343, in hive
>mode = 01777)
> 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/libraries/providers/hdfs_resource.py",
> line 604, in action_create_on_execute
>self.action_delayed("create")
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 601, in action_delayed
>self.get_hdfs_resource_executor().action_delayed(action_name, self)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 328, in action_delayed
>self._assert_valid()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 287, in _assert_valid
>self.target_status = self._get_file_status(target)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 430, in _get_file_status
>list_status = self.util.run_command(target, 'GETFILESTATUS', method='GET',
> ignore_status_codes=['404'], assertable_result=False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 177, in run_command
>return self._run_command(*args, **kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 248, in _run_command
>raise WebHDFSCallException(err_msg, result_dict)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22606) Service actions for R4ML not loaded
[
https://issues.apache.org/jira/browse/AMBARI-22606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko updated AMBARI-22606:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Service actions for R4ML not loaded
> ---
>
> Key: AMBARI-22606
> URL: https://issues.apache.org/jira/browse/AMBARI-22606
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.1
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22606.patch, AMBARI-22606_branch-2.6.patch
>
>
> While trying to delete R4ML service, the Service actions menu doesn't load
> with next js error:
> {code}
> app.js:180350 Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.createServiceConfig (app.js:180350)
> at app.js:30065
> at Array.forEach ()
> at Object. (app.js:30060)
> at o (vendor.js:106)
> at Object.add [as done] (vendor.js:106)
> at Object. (app.js:30054)
> at o (vendor.js:106)
> at Object.fireWith (vendor.js:106)
> at Object.fire [as resolve] (vendor.js:106)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22606) Service actions for R4ML not loaded
[
https://issues.apache.org/jira/browse/AMBARI-22606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16280994#comment-16280994
]
Aleksandr Kovalenko commented on AMBARI-22606:
--
committed to trunk and branch-2.6
> Service actions for R4ML not loaded
> ---
>
> Key: AMBARI-22606
> URL: https://issues.apache.org/jira/browse/AMBARI-22606
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.1
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22606.patch, AMBARI-22606_branch-2.6.patch
>
>
> While trying to delete R4ML service, the Service actions menu doesn't load
> with next js error:
> {code}
> app.js:180350 Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.createServiceConfig (app.js:180350)
> at app.js:30065
> at Array.forEach ()
> at Object. (app.js:30060)
> at o (vendor.js:106)
> at Object.add [as done] (vendor.js:106)
> at Object. (app.js:30054)
> at o (vendor.js:106)
> at Object.fireWith (vendor.js:106)
> at Object.fire [as resolve] (vendor.js:106)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22492) A bad WebHDFS request is issued when starting Hive Metastore
[
https://issues.apache.org/jira/browse/AMBARI-22492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16280979#comment-16280979
]
Hudson commented on AMBARI-22492:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8500 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8500/])
AMBARI-22492. A bad WebHDFS request is issued when starting Hive (amagyar:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=420385362200f3f5f714db50a20d3af727767513])
* (edit)
ambari-server/src/main/resources/common-services/HIVE/2.1.0.3.0/package/scripts/hive.py
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py
* (edit)
ambari-common/src/main/python/resource_management/libraries/providers/hdfs_resource.py
> A bad WebHDFS request is issued when starting Hive Metastore
>
>
> Key: AMBARI-22492
> URL: https://issues.apache.org/jira/browse/AMBARI-22492
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: David Tucker
>Assignee: Attila Magyar
> Fix For: 2.6.1
>
> Attachments: AMBARI-22492.patch
>
>
> When deploying a cluster with Hive (1.2.1000, in this case), Ambari issues an
> incorrect WebHDFS request:
> {code}
> 2017-11-20 20:21:21,839 - call['ambari-sudo.sh su hdfs -l -s /bin/bash -c
> 'curl -sS -L -w '"'"'%{http_code}'"'"' -X GET
> '"'"'http://dtucker-rjy277d.west.isilon.com:8082/webhdfs/v1?op=GETFILESTATUS=hdfs'"'"'
> 1>/tmp/tmpzipnFe 2>/tmp/tmpbGajx_''] {'logoutput': None, 'quiet': False}
> {code}
> That command should be:
> {code}
> curl -sS -L -w '%{http_code}' -X GET
> 'http://dtucker-rjy277d.west.isilon.com:8082/webhdfs/v1/?op=GETFILESTATUS=hdfs'
> {code}
> (Note the / after v1.)
> On Apache, this results in a FileNotFoundException (404); however, this
> causes problems with OneFS which returns an IllegalArgumentException (400)
> and prevents the Metastore from starting.
> Here is the full traceback:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 203, in
>HiveMetastore().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 367, in execute
>method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 54, in start
>self.configure(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 120, in locking_configure
>original_configure(obj, *args, **kw)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 72, in configure
>hive(name = 'metastore')
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
>return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py",
> line 343, in hive
>mode = 01777)
> 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/libraries/providers/hdfs_resource.py",
> line 604, in action_create_on_execute
>self.action_delayed("create")
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 601, in action_delayed
>self.get_hdfs_resource_executor().action_delayed(action_name, self)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 328, in action_delayed
>self._assert_valid()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 287, in _assert_valid
>self.target_status = self._get_file_status(target)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 430, in _get_file_status
>list_status = self.util.run_command(target, 'GETFILESTATUS', method='GET',
> ignore_status_codes=['404'], assertable_result=False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 177, in run_command
>return self._run_command(*args, **kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 248, in _run_command
>raise
[jira] [Commented] (AMBARI-22606) Service actions for R4ML not loaded
[
https://issues.apache.org/jira/browse/AMBARI-22606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16280973#comment-16280973
]
Hadoop QA commented on AMBARI-22606:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12900920/AMBARI-22606.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12808//console
This message is automatically generated.
> Service actions for R4ML not loaded
> ---
>
> Key: AMBARI-22606
> URL: https://issues.apache.org/jira/browse/AMBARI-22606
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.1
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22606.patch, AMBARI-22606_branch-2.6.patch
>
>
> While trying to delete R4ML service, the Service actions menu doesn't load
> with next js error:
> {code}
> app.js:180350 Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.createServiceConfig (app.js:180350)
> at app.js:30065
> at Array.forEach ()
> at Object. (app.js:30060)
> at o (vendor.js:106)
> at Object.add [as done] (vendor.js:106)
> at Object. (app.js:30054)
> at o (vendor.js:106)
> at Object.fireWith (vendor.js:106)
> at Object.fire [as resolve] (vendor.js:106)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22492) A bad WebHDFS request is issued when starting Hive Metastore
[
https://issues.apache.org/jira/browse/AMBARI-22492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16280958#comment-16280958
]
Hudson commented on AMBARI-22492:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #541 (See
[https://builds.apache.org/job/Ambari-branch-2.6/541/])
AMBARI-22492. A bad WebHDFS request is issued when starting Hive (amagyar:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2915d563cfd770f8281b341b6ce00c80164da93f])
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py
* (edit)
ambari-common/src/main/python/resource_management/libraries/providers/hdfs_resource.py
> A bad WebHDFS request is issued when starting Hive Metastore
>
>
> Key: AMBARI-22492
> URL: https://issues.apache.org/jira/browse/AMBARI-22492
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: David Tucker
>Assignee: Attila Magyar
> Fix For: 2.6.1
>
> Attachments: AMBARI-22492.patch
>
>
> When deploying a cluster with Hive (1.2.1000, in this case), Ambari issues an
> incorrect WebHDFS request:
> {code}
> 2017-11-20 20:21:21,839 - call['ambari-sudo.sh su hdfs -l -s /bin/bash -c
> 'curl -sS -L -w '"'"'%{http_code}'"'"' -X GET
> '"'"'http://dtucker-rjy277d.west.isilon.com:8082/webhdfs/v1?op=GETFILESTATUS=hdfs'"'"'
> 1>/tmp/tmpzipnFe 2>/tmp/tmpbGajx_''] {'logoutput': None, 'quiet': False}
> {code}
> That command should be:
> {code}
> curl -sS -L -w '%{http_code}' -X GET
> 'http://dtucker-rjy277d.west.isilon.com:8082/webhdfs/v1/?op=GETFILESTATUS=hdfs'
> {code}
> (Note the / after v1.)
> On Apache, this results in a FileNotFoundException (404); however, this
> causes problems with OneFS which returns an IllegalArgumentException (400)
> and prevents the Metastore from starting.
> Here is the full traceback:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 203, in
>HiveMetastore().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 367, in execute
>method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 54, in start
>self.configure(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 120, in locking_configure
>original_configure(obj, *args, **kw)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 72, in configure
>hive(name = 'metastore')
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
>return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py",
> line 343, in hive
>mode = 01777)
> 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/libraries/providers/hdfs_resource.py",
> line 604, in action_create_on_execute
>self.action_delayed("create")
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 601, in action_delayed
>self.get_hdfs_resource_executor().action_delayed(action_name, self)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 328, in action_delayed
>self._assert_valid()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 287, in _assert_valid
>self.target_status = self._get_file_status(target)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 430, in _get_file_status
>list_status = self.util.run_command(target, 'GETFILESTATUS', method='GET',
> ignore_status_codes=['404'], assertable_result=False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 177, in run_command
>return self._run_command(*args, **kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 248, in _run_command
>raise WebHDFSCallException(err_msg, result_dict)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22492) A bad WebHDFS request is issued when starting Hive Metastore
[
https://issues.apache.org/jira/browse/AMBARI-22492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Magyar updated AMBARI-22492:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
commited to branch-2.6
2915d563cfd770f8281b341b6ce00c80164da93f
and trunk:
420385362200f3f5f714db50a20d3af727767513
> A bad WebHDFS request is issued when starting Hive Metastore
>
>
> Key: AMBARI-22492
> URL: https://issues.apache.org/jira/browse/AMBARI-22492
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: David Tucker
>Assignee: Attila Magyar
> Fix For: 2.6.1
>
> Attachments: AMBARI-22492.patch
>
>
> When deploying a cluster with Hive (1.2.1000, in this case), Ambari issues an
> incorrect WebHDFS request:
> {code}
> 2017-11-20 20:21:21,839 - call['ambari-sudo.sh su hdfs -l -s /bin/bash -c
> 'curl -sS -L -w '"'"'%{http_code}'"'"' -X GET
> '"'"'http://dtucker-rjy277d.west.isilon.com:8082/webhdfs/v1?op=GETFILESTATUS=hdfs'"'"'
> 1>/tmp/tmpzipnFe 2>/tmp/tmpbGajx_''] {'logoutput': None, 'quiet': False}
> {code}
> That command should be:
> {code}
> curl -sS -L -w '%{http_code}' -X GET
> 'http://dtucker-rjy277d.west.isilon.com:8082/webhdfs/v1/?op=GETFILESTATUS=hdfs'
> {code}
> (Note the / after v1.)
> On Apache, this results in a FileNotFoundException (404); however, this
> causes problems with OneFS which returns an IllegalArgumentException (400)
> and prevents the Metastore from starting.
> Here is the full traceback:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 203, in
>HiveMetastore().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 367, in execute
>method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 54, in start
>self.configure(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 120, in locking_configure
>original_configure(obj, *args, **kw)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 72, in configure
>hive(name = 'metastore')
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
>return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py",
> line 343, in hive
>mode = 01777)
> 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/libraries/providers/hdfs_resource.py",
> line 604, in action_create_on_execute
>self.action_delayed("create")
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 601, in action_delayed
>self.get_hdfs_resource_executor().action_delayed(action_name, self)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 328, in action_delayed
>self._assert_valid()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 287, in _assert_valid
>self.target_status = self._get_file_status(target)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 430, in _get_file_status
>list_status = self.util.run_command(target, 'GETFILESTATUS', method='GET',
> ignore_status_codes=['404'], assertable_result=False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 177, in run_command
>return self._run_command(*args, **kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 248, in _run_command
>raise WebHDFSCallException(err_msg, result_dict)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-22487) New endpoint service_config_version for creating new config versions via service endpoint instead of cluster update
[ https://issues.apache.org/jira/browse/AMBARI-22487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan resolved AMBARI-22487. Resolution: Fixed > New endpoint service_config_version for creating new config versions via > service endpoint instead of cluster update > --- > > Key: AMBARI-22487 > URL: https://issues.apache.org/jira/browse/AMBARI-22487 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 3.0.0 > > > We should modify the service config versions API to support creation of new > service config versions and entirely get rid of desired cluster configs. > New APIs > Create new service config version > POST > api/v2/clusters//servicegroups//services//configurations/service_config_versions -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22492) A bad WebHDFS request is issued when starting Hive Metastore
[
https://issues.apache.org/jira/browse/AMBARI-22492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16280932#comment-16280932
]
Hadoop QA commented on AMBARI-22492:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12900952/AMBARI-22492.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12807//console
This message is automatically generated.
> A bad WebHDFS request is issued when starting Hive Metastore
>
>
> Key: AMBARI-22492
> URL: https://issues.apache.org/jira/browse/AMBARI-22492
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: David Tucker
>Assignee: Attila Magyar
> Fix For: 2.6.1
>
> Attachments: AMBARI-22492.patch
>
>
> When deploying a cluster with Hive (1.2.1000, in this case), Ambari issues an
> incorrect WebHDFS request:
> {code}
> 2017-11-20 20:21:21,839 - call['ambari-sudo.sh su hdfs -l -s /bin/bash -c
> 'curl -sS -L -w '"'"'%{http_code}'"'"' -X GET
> '"'"'http://dtucker-rjy277d.west.isilon.com:8082/webhdfs/v1?op=GETFILESTATUS=hdfs'"'"'
> 1>/tmp/tmpzipnFe 2>/tmp/tmpbGajx_''] {'logoutput': None, 'quiet': False}
> {code}
> That command should be:
> {code}
> curl -sS -L -w '%{http_code}' -X GET
> 'http://dtucker-rjy277d.west.isilon.com:8082/webhdfs/v1/?op=GETFILESTATUS=hdfs'
> {code}
> (Note the / after v1.)
> On Apache, this results in a FileNotFoundException (404); however, this
> causes problems with OneFS which returns an IllegalArgumentException (400)
> and prevents the Metastore from starting.
> Here is the full traceback:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 203, in
>HiveMetastore().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 367, in execute
>method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 54, in start
>self.configure(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 120, in locking_configure
>original_configure(obj, *args, **kw)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 72, in configure
>hive(name = 'metastore')
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
>return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py",
> line 343, in hive
>mode = 01777)
> 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/libraries/providers/hdfs_resource.py",
> line 604, in action_create_on_execute
>self.action_delayed("create")
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 601, in action_delayed
>self.get_hdfs_resource_executor().action_delayed(action_name, self)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 328, in action_delayed
>self._assert_valid()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 287, in _assert_valid
>self.target_status = self._get_file_status(target)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 430, in _get_file_status
>list_status = self.util.run_command(target, 'GETFILESTATUS', method='GET',
> ignore_status_codes=['404'], assertable_result=False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 177, in run_command
>return self._run_command(*args, **kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 248, in _run_command
>raise WebHDFSCallException(err_msg, result_dict)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22492) A bad WebHDFS request is issued when starting Hive Metastore
[
https://issues.apache.org/jira/browse/AMBARI-22492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Magyar updated AMBARI-22492:
---
Fix Version/s: 2.6.1
> A bad WebHDFS request is issued when starting Hive Metastore
>
>
> Key: AMBARI-22492
> URL: https://issues.apache.org/jira/browse/AMBARI-22492
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: David Tucker
>Assignee: Attila Magyar
> Fix For: 2.6.1
>
> Attachments: AMBARI-22492.patch
>
>
> When deploying a cluster with Hive (1.2.1000, in this case), Ambari issues an
> incorrect WebHDFS request:
> {code}
> 2017-11-20 20:21:21,839 - call['ambari-sudo.sh su hdfs -l -s /bin/bash -c
> 'curl -sS -L -w '"'"'%{http_code}'"'"' -X GET
> '"'"'http://dtucker-rjy277d.west.isilon.com:8082/webhdfs/v1?op=GETFILESTATUS=hdfs'"'"'
> 1>/tmp/tmpzipnFe 2>/tmp/tmpbGajx_''] {'logoutput': None, 'quiet': False}
> {code}
> That command should be:
> {code}
> curl -sS -L -w '%{http_code}' -X GET
> 'http://dtucker-rjy277d.west.isilon.com:8082/webhdfs/v1/?op=GETFILESTATUS=hdfs'
> {code}
> (Note the / after v1.)
> On Apache, this results in a FileNotFoundException (404); however, this
> causes problems with OneFS which returns an IllegalArgumentException (400)
> and prevents the Metastore from starting.
> Here is the full traceback:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 203, in
>HiveMetastore().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 367, in execute
>method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 54, in start
>self.configure(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 120, in locking_configure
>original_configure(obj, *args, **kw)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 72, in configure
>hive(name = 'metastore')
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
>return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py",
> line 343, in hive
>mode = 01777)
> 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/libraries/providers/hdfs_resource.py",
> line 604, in action_create_on_execute
>self.action_delayed("create")
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 601, in action_delayed
>self.get_hdfs_resource_executor().action_delayed(action_name, self)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 328, in action_delayed
>self._assert_valid()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 287, in _assert_valid
>self.target_status = self._get_file_status(target)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 430, in _get_file_status
>list_status = self.util.run_command(target, 'GETFILESTATUS', method='GET',
> ignore_status_codes=['404'], assertable_result=False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 177, in run_command
>return self._run_command(*args, **kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 248, in _run_command
>raise WebHDFSCallException(err_msg, result_dict)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22492) A bad WebHDFS request is issued when starting Hive Metastore
[
https://issues.apache.org/jira/browse/AMBARI-22492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Magyar updated AMBARI-22492:
---
Status: Patch Available (was: In Progress)
> A bad WebHDFS request is issued when starting Hive Metastore
>
>
> Key: AMBARI-22492
> URL: https://issues.apache.org/jira/browse/AMBARI-22492
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: David Tucker
>Assignee: Attila Magyar
> Attachments: AMBARI-22492.patch
>
>
> When deploying a cluster with Hive (1.2.1000, in this case), Ambari issues an
> incorrect WebHDFS request:
> {code}
> 2017-11-20 20:21:21,839 - call['ambari-sudo.sh su hdfs -l -s /bin/bash -c
> 'curl -sS -L -w '"'"'%{http_code}'"'"' -X GET
> '"'"'http://dtucker-rjy277d.west.isilon.com:8082/webhdfs/v1?op=GETFILESTATUS=hdfs'"'"'
> 1>/tmp/tmpzipnFe 2>/tmp/tmpbGajx_''] {'logoutput': None, 'quiet': False}
> {code}
> That command should be:
> {code}
> curl -sS -L -w '%{http_code}' -X GET
> 'http://dtucker-rjy277d.west.isilon.com:8082/webhdfs/v1/?op=GETFILESTATUS=hdfs'
> {code}
> (Note the / after v1.)
> On Apache, this results in a FileNotFoundException (404); however, this
> causes problems with OneFS which returns an IllegalArgumentException (400)
> and prevents the Metastore from starting.
> Here is the full traceback:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 203, in
>HiveMetastore().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 367, in execute
>method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 54, in start
>self.configure(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 120, in locking_configure
>original_configure(obj, *args, **kw)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 72, in configure
>hive(name = 'metastore')
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
>return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py",
> line 343, in hive
>mode = 01777)
> 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/libraries/providers/hdfs_resource.py",
> line 604, in action_create_on_execute
>self.action_delayed("create")
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 601, in action_delayed
>self.get_hdfs_resource_executor().action_delayed(action_name, self)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 328, in action_delayed
>self._assert_valid()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 287, in _assert_valid
>self.target_status = self._get_file_status(target)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 430, in _get_file_status
>list_status = self.util.run_command(target, 'GETFILESTATUS', method='GET',
> ignore_status_codes=['404'], assertable_result=False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 177, in run_command
>return self._run_command(*args, **kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 248, in _run_command
>raise WebHDFSCallException(err_msg, result_dict)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22492) A bad WebHDFS request is issued when starting Hive Metastore
[
https://issues.apache.org/jira/browse/AMBARI-22492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Magyar updated AMBARI-22492:
---
Attachment: AMBARI-22492.patch
> A bad WebHDFS request is issued when starting Hive Metastore
>
>
> Key: AMBARI-22492
> URL: https://issues.apache.org/jira/browse/AMBARI-22492
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: David Tucker
>Assignee: Attila Magyar
> Attachments: AMBARI-22492.patch
>
>
> When deploying a cluster with Hive (1.2.1000, in this case), Ambari issues an
> incorrect WebHDFS request:
> {code}
> 2017-11-20 20:21:21,839 - call['ambari-sudo.sh su hdfs -l -s /bin/bash -c
> 'curl -sS -L -w '"'"'%{http_code}'"'"' -X GET
> '"'"'http://dtucker-rjy277d.west.isilon.com:8082/webhdfs/v1?op=GETFILESTATUS=hdfs'"'"'
> 1>/tmp/tmpzipnFe 2>/tmp/tmpbGajx_''] {'logoutput': None, 'quiet': False}
> {code}
> That command should be:
> {code}
> curl -sS -L -w '%{http_code}' -X GET
> 'http://dtucker-rjy277d.west.isilon.com:8082/webhdfs/v1/?op=GETFILESTATUS=hdfs'
> {code}
> (Note the / after v1.)
> On Apache, this results in a FileNotFoundException (404); however, this
> causes problems with OneFS which returns an IllegalArgumentException (400)
> and prevents the Metastore from starting.
> Here is the full traceback:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 203, in
>HiveMetastore().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 367, in execute
>method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 54, in start
>self.configure(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 120, in locking_configure
>original_configure(obj, *args, **kw)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 72, in configure
>hive(name = 'metastore')
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
>return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py",
> line 343, in hive
>mode = 01777)
> 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/libraries/providers/hdfs_resource.py",
> line 604, in action_create_on_execute
>self.action_delayed("create")
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 601, in action_delayed
>self.get_hdfs_resource_executor().action_delayed(action_name, self)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 328, in action_delayed
>self._assert_valid()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 287, in _assert_valid
>self.target_status = self._get_file_status(target)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 430, in _get_file_status
>list_status = self.util.run_command(target, 'GETFILESTATUS', method='GET',
> ignore_status_codes=['404'], assertable_result=False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 177, in run_command
>return self._run_command(*args, **kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 248, in _run_command
>raise WebHDFSCallException(err_msg, result_dict)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22583) Ambari should not force accounts created in IPA to be added a user named 'ambari-managed-principals'
[
https://issues.apache.org/jira/browse/AMBARI-22583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16280871#comment-16280871
]
Doroszlai, Attila commented on AMBARI-22583:
Thanks!
> Ambari should not force accounts created in IPA to be added a user named
> 'ambari-managed-principals'
>
>
> Key: AMBARI-22583
> URL: https://issues.apache.org/jira/browse/AMBARI-22583
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: freeipa, kerberos
> Fix For: 3.0.0
>
> Attachments: AMBARI-22583_trunk_01.patch,
> AMBARI-22583_trunk_01_amend_01.patch
>
>
> When creating user principals while enabling Kerberos using FreeIPA, Ambari
> should not force accounts to be added a user named
> 'ambari-managed-principals'.
> This occurs because the default value of {{kerberos-env/ipa_user_group}} is
> "ambari-managed-principals". To stop forcing this, the default value should
> be empty.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22606) Service actions for R4ML not loaded
[
https://issues.apache.org/jira/browse/AMBARI-22606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16280763#comment-16280763
]
Hadoop QA commented on AMBARI-22606:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12900920/AMBARI-22606.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12806//console
This message is automatically generated.
> Service actions for R4ML not loaded
> ---
>
> Key: AMBARI-22606
> URL: https://issues.apache.org/jira/browse/AMBARI-22606
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.1
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22606.patch, AMBARI-22606_branch-2.6.patch
>
>
> While trying to delete R4ML service, the Service actions menu doesn't load
> with next js error:
> {code}
> app.js:180350 Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.createServiceConfig (app.js:180350)
> at app.js:30065
> at Array.forEach ()
> at Object. (app.js:30060)
> at o (vendor.js:106)
> at Object.add [as done] (vendor.js:106)
> at Object. (app.js:30054)
> at o (vendor.js:106)
> at Object.fireWith (vendor.js:106)
> at Object.fire [as resolve] (vendor.js:106)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22606) Service actions for R4ML not loaded
[
https://issues.apache.org/jira/browse/AMBARI-22606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16280697#comment-16280697
]
Denys Buzhor commented on AMBARI-22606:
---
+1 for patch
> Service actions for R4ML not loaded
> ---
>
> Key: AMBARI-22606
> URL: https://issues.apache.org/jira/browse/AMBARI-22606
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.1
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22606.patch, AMBARI-22606_branch-2.6.patch
>
>
> While trying to delete R4ML service, the Service actions menu doesn't load
> with next js error:
> {code}
> app.js:180350 Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.createServiceConfig (app.js:180350)
> at app.js:30065
> at Array.forEach ()
> at Object. (app.js:30060)
> at o (vendor.js:106)
> at Object.add [as done] (vendor.js:106)
> at Object. (app.js:30054)
> at o (vendor.js:106)
> at Object.fireWith (vendor.js:106)
> at Object.fire [as resolve] (vendor.js:106)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22606) Service actions for R4ML not loaded
[
https://issues.apache.org/jira/browse/AMBARI-22606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko updated AMBARI-22606:
-
Status: Patch Available (was: Open)
> Service actions for R4ML not loaded
> ---
>
> Key: AMBARI-22606
> URL: https://issues.apache.org/jira/browse/AMBARI-22606
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.1
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22606.patch, AMBARI-22606_branch-2.6.patch
>
>
> While trying to delete R4ML service, the Service actions menu doesn't load
> with next js error:
> {code}
> app.js:180350 Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.createServiceConfig (app.js:180350)
> at app.js:30065
> at Array.forEach ()
> at Object. (app.js:30060)
> at o (vendor.js:106)
> at Object.add [as done] (vendor.js:106)
> at Object. (app.js:30054)
> at o (vendor.js:106)
> at Object.fireWith (vendor.js:106)
> at Object.fire [as resolve] (vendor.js:106)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22606) Service actions for R4ML not loaded
[
https://issues.apache.org/jira/browse/AMBARI-22606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko updated AMBARI-22606:
-
Attachment: AMBARI-22606.patch
> Service actions for R4ML not loaded
> ---
>
> Key: AMBARI-22606
> URL: https://issues.apache.org/jira/browse/AMBARI-22606
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.1
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22606.patch, AMBARI-22606_branch-2.6.patch
>
>
> While trying to delete R4ML service, the Service actions menu doesn't load
> with next js error:
> {code}
> app.js:180350 Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.createServiceConfig (app.js:180350)
> at app.js:30065
> at Array.forEach ()
> at Object. (app.js:30060)
> at o (vendor.js:106)
> at Object.add [as done] (vendor.js:106)
> at Object. (app.js:30054)
> at o (vendor.js:106)
> at Object.fireWith (vendor.js:106)
> at Object.fire [as resolve] (vendor.js:106)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22606) Service actions for R4ML not loaded
[
https://issues.apache.org/jira/browse/AMBARI-22606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko updated AMBARI-22606:
-
Attachment: (was: AMBARI-22606_barnch-2.6.patch)
> Service actions for R4ML not loaded
> ---
>
> Key: AMBARI-22606
> URL: https://issues.apache.org/jira/browse/AMBARI-22606
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.1
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22606_branch-2.6.patch
>
>
> While trying to delete R4ML service, the Service actions menu doesn't load
> with next js error:
> {code}
> app.js:180350 Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.createServiceConfig (app.js:180350)
> at app.js:30065
> at Array.forEach ()
> at Object. (app.js:30060)
> at o (vendor.js:106)
> at Object.add [as done] (vendor.js:106)
> at Object. (app.js:30054)
> at o (vendor.js:106)
> at Object.fireWith (vendor.js:106)
> at Object.fire [as resolve] (vendor.js:106)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22606) Service actions for R4ML not loaded
[
https://issues.apache.org/jira/browse/AMBARI-22606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko updated AMBARI-22606:
-
Attachment: AMBARI-22606_barnch-2.6.patch
> Service actions for R4ML not loaded
> ---
>
> Key: AMBARI-22606
> URL: https://issues.apache.org/jira/browse/AMBARI-22606
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.1
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22606_branch-2.6.patch
>
>
> While trying to delete R4ML service, the Service actions menu doesn't load
> with next js error:
> {code}
> app.js:180350 Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.createServiceConfig (app.js:180350)
> at app.js:30065
> at Array.forEach ()
> at Object. (app.js:30060)
> at o (vendor.js:106)
> at Object.add [as done] (vendor.js:106)
> at Object. (app.js:30054)
> at o (vendor.js:106)
> at Object.fireWith (vendor.js:106)
> at Object.fire [as resolve] (vendor.js:106)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22606) Service actions for R4ML not loaded
[
https://issues.apache.org/jira/browse/AMBARI-22606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko updated AMBARI-22606:
-
Attachment: AMBARI-22606_branch-2.6.patch
> Service actions for R4ML not loaded
> ---
>
> Key: AMBARI-22606
> URL: https://issues.apache.org/jira/browse/AMBARI-22606
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.1
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22606_branch-2.6.patch
>
>
> While trying to delete R4ML service, the Service actions menu doesn't load
> with next js error:
> {code}
> app.js:180350 Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.createServiceConfig (app.js:180350)
> at app.js:30065
> at Array.forEach ()
> at Object. (app.js:30060)
> at o (vendor.js:106)
> at Object.add [as done] (vendor.js:106)
> at Object. (app.js:30054)
> at o (vendor.js:106)
> at Object.fireWith (vendor.js:106)
> at Object.fire [as resolve] (vendor.js:106)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22606) Service actions for R4ML not loaded
Aleksandr Kovalenko created AMBARI-22606:
Summary: Service actions for R4ML not loaded
Key: AMBARI-22606
URL: https://issues.apache.org/jira/browse/AMBARI-22606
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.6.1
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
Priority: Blocker
Fix For: 2.6.1
While trying to delete R4ML service, the Service actions menu doesn't load with
next js error:
{code}
app.js:180350 Uncaught TypeError: Cannot read property 'get' of undefined
at Class.createServiceConfig (app.js:180350)
at app.js:30065
at Array.forEach ()
at Object. (app.js:30060)
at o (vendor.js:106)
at Object.add [as done] (vendor.js:106)
at Object. (app.js:30054)
at o (vendor.js:106)
at Object.fireWith (vendor.js:106)
at Object.fire [as resolve] (vendor.js:106)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22583) Ambari should not force accounts created in IPA to be added a user named 'ambari-managed-principals'
[
https://issues.apache.org/jira/browse/AMBARI-22583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16280645#comment-16280645
]
Hudson commented on AMBARI-22583:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8499 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8499/])
AMBARI-22583. Ambari should not force accounts created in IPA to be (rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9f93a0186c54d66d6da28edf1eeae4a554f8d28d])
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/configuration/kerberos-env.xml
* (edit)
ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-10/configuration/kerberos-env.xml
* (edit)
ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-30/configuration/kerberos-env.xml
Revert "AMBARI-22583. Ambari should not force accounts created in IPA to
(rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=76c4fa1cabfb1b68d9cfe1599b874bf764130957])
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/configuration/kerberos-env.xml
* (edit)
ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-30/configuration/kerberos-env.xml
* (edit)
ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-10/configuration/kerberos-env.xml
Revert "AMBARI-22583. Ambari should not force accounts created in IPA to
(rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9b1fde342378c91859bc60bb442b6f5ae682bec4])
* (edit)
ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-10/configuration/kerberos-env.xml
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/configuration/kerberos-env.xml
* (edit)
ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-30/configuration/kerberos-env.xml
AMBARI-22583. Ambari should not force accounts created in IPA to be (rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=814f5b456814ca278a02c06b5df3eba009c5caca])
* (edit)
ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-30/configuration/kerberos-env.xml
* (edit)
ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-10/configuration/kerberos-env.xml
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/configuration/kerberos-env.xml
> Ambari should not force accounts created in IPA to be added a user named
> 'ambari-managed-principals'
>
>
> Key: AMBARI-22583
> URL: https://issues.apache.org/jira/browse/AMBARI-22583
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: freeipa, kerberos
> Fix For: 3.0.0
>
> Attachments: AMBARI-22583_trunk_01.patch,
> AMBARI-22583_trunk_01_amend_01.patch
>
>
> When creating user principals while enabling Kerberos using FreeIPA, Ambari
> should not force accounts to be added a user named
> 'ambari-managed-principals'.
> This occurs because the default value of {{kerberos-env/ipa_user_group}} is
> "ambari-managed-principals". To stop forcing this, the default value should
> be empty.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22605) Tez service check hangs when adding service
Myroslav Papirkovskyi created AMBARI-22605: -- Summary: Tez service check hangs when adding service Key: AMBARI-22605 URL: https://issues.apache.org/jira/browse/AMBARI-22605 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.6.1 Reporter: Myroslav Papirkovskyi Assignee: Myroslav Papirkovskyi Priority: Blocker Fix For: 2.6.0 STR: Deploy minimal cluster (HDFS, YARN+MR2, ZooKeeper). Add Tez service. Service check hangs for a long time. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22597) Jetty Session Timeout Is Overridden By Views Initialization
[
https://issues.apache.org/jira/browse/AMBARI-22597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16280586#comment-16280586
]
Hudson commented on AMBARI-22597:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8498 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8498/])
AMBARI-22597. Jetty Session Timeout Is Overridden By Views (mpapyrkovskyy:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=cfb2321f8769bdc92a1c08ad354e604f104ac629])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java
> Jetty Session Timeout Is Overridden By Views Initialization
> ---
>
> Key: AMBARI-22597
> URL: https://issues.apache.org/jira/browse/AMBARI-22597
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Fix For: 3.0.0
>
>
> Setting {{server.http.session.inactive_timeout=60}} does not work as
> expected. After 60 seconds, the session which was created is still active and
> has not been invalidated by the Jetty scavenger.
> Upon inspection, this valid is being set correctly by {{AmbariServer.java}}
> in the Jetty {{SessionManager}}. However, when a new session is opened, the
> original value of 1800 is being used. The instance of the {{SessionManager}}
> is the same, which means that something has reset this value after we set it
> correctly.
> I believe that View-initialization might be causing this...
> STR:
> - Change server.http.session.inactive_timeout=60 and restart ambari server
> - $ curl -i -u admin:admin -b /tmp/ambarisessionfile -c
> /tmp/ambarisessionfile http://ambari-host:8080/api/v1/clusters
> - Wait for 2 minutes
> - $ curl -i -b /tmp/ambarisessionfile -c /tmp/ambarisessionfile
> http://ambari-host:8080/api/v1/clusters
> The final command will still work, even though the session should be
> invalidated.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22583) Ambari should not force accounts created in IPA to be added a user named 'ambari-managed-principals'
[
https://issues.apache.org/jira/browse/AMBARI-22583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16280574#comment-16280574
]
Robert Levas commented on AMBARI-22583:
---
I wound up reverting the original patch then committing the combination of the
original patch and the amendment.
Committed to trunk
{noformat}
commit 814f5b456814ca278a02c06b5df3eba009c5caca
Author: Robert Levas
Date: Wed Dec 6 12:49:01 2017 -0500
{noformat}
> Ambari should not force accounts created in IPA to be added a user named
> 'ambari-managed-principals'
>
>
> Key: AMBARI-22583
> URL: https://issues.apache.org/jira/browse/AMBARI-22583
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: freeipa, kerberos
> Fix For: 3.0.0
>
> Attachments: AMBARI-22583_trunk_01.patch,
> AMBARI-22583_trunk_01_amend_01.patch
>
>
> When creating user principals while enabling Kerberos using FreeIPA, Ambari
> should not force accounts to be added a user named
> 'ambari-managed-principals'.
> This occurs because the default value of {{kerberos-env/ipa_user_group}} is
> "ambari-managed-principals". To stop forcing this, the default value should
> be empty.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22583) Ambari should not force accounts created in IPA to be added a user named 'ambari-managed-principals'
[
https://issues.apache.org/jira/browse/AMBARI-22583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-22583:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Ambari should not force accounts created in IPA to be added a user named
> 'ambari-managed-principals'
>
>
> Key: AMBARI-22583
> URL: https://issues.apache.org/jira/browse/AMBARI-22583
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: freeipa, kerberos
> Fix For: 3.0.0
>
> Attachments: AMBARI-22583_trunk_01.patch,
> AMBARI-22583_trunk_01_amend_01.patch
>
>
> When creating user principals while enabling Kerberos using FreeIPA, Ambari
> should not force accounts to be added a user named
> 'ambari-managed-principals'.
> This occurs because the default value of {{kerberos-env/ipa_user_group}} is
> "ambari-managed-principals". To stop forcing this, the default value should
> be empty.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22583) Ambari should not force accounts created in IPA to be added a user named 'ambari-managed-principals'
[
https://issues.apache.org/jira/browse/AMBARI-22583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16280566#comment-16280566
]
Robert Levas commented on AMBARI-22583:
---
Locally, applying [^AMBARI-22583_trunk_01_amend_01.patch] resulted in
{noformat}
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 28:58 min
[INFO] Finished at: 2017-12-06T12:05:49-05:00
[INFO] Final Memory: 98M/1986M
[INFO]
{noformat}
> Ambari should not force accounts created in IPA to be added a user named
> 'ambari-managed-principals'
>
>
> Key: AMBARI-22583
> URL: https://issues.apache.org/jira/browse/AMBARI-22583
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: freeipa, kerberos
> Fix For: 3.0.0
>
> Attachments: AMBARI-22583_trunk_01.patch,
> AMBARI-22583_trunk_01_amend_01.patch
>
>
> When creating user principals while enabling Kerberos using FreeIPA, Ambari
> should not force accounts to be added a user named
> 'ambari-managed-principals'.
> This occurs because the default value of {{kerberos-env/ipa_user_group}} is
> "ambari-managed-principals". To stop forcing this, the default value should
> be empty.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22583) Ambari should not force accounts created in IPA to be added a user named 'ambari-managed-principals'
[
https://issues.apache.org/jira/browse/AMBARI-22583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16280540#comment-16280540
]
Hadoop QA commented on AMBARI-22583:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12900892/AMBARI-22583_trunk_01_amend_01.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12805//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12805//console
This message is automatically generated.
> Ambari should not force accounts created in IPA to be added a user named
> 'ambari-managed-principals'
>
>
> Key: AMBARI-22583
> URL: https://issues.apache.org/jira/browse/AMBARI-22583
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: freeipa, kerberos
> Fix For: 3.0.0
>
> Attachments: AMBARI-22583_trunk_01.patch,
> AMBARI-22583_trunk_01_amend_01.patch
>
>
> When creating user principals while enabling Kerberos using FreeIPA, Ambari
> should not force accounts to be added a user named
> 'ambari-managed-principals'.
> This occurs because the default value of {{kerberos-env/ipa_user_group}} is
> "ambari-managed-principals". To stop forcing this, the default value should
> be empty.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-22597) Jetty Session Timeout Is Overridden By Views Initialization
[
https://issues.apache.org/jira/browse/AMBARI-22597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myroslav Papirkovskyi resolved AMBARI-22597.
Resolution: Fixed
Pushed to trunk
> Jetty Session Timeout Is Overridden By Views Initialization
> ---
>
> Key: AMBARI-22597
> URL: https://issues.apache.org/jira/browse/AMBARI-22597
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Fix For: 3.0.0
>
>
> Setting {{server.http.session.inactive_timeout=60}} does not work as
> expected. After 60 seconds, the session which was created is still active and
> has not been invalidated by the Jetty scavenger.
> Upon inspection, this valid is being set correctly by {{AmbariServer.java}}
> in the Jetty {{SessionManager}}. However, when a new session is opened, the
> original value of 1800 is being used. The instance of the {{SessionManager}}
> is the same, which means that something has reset this value after we set it
> correctly.
> I believe that View-initialization might be causing this...
> STR:
> - Change server.http.session.inactive_timeout=60 and restart ambari server
> - $ curl -i -u admin:admin -b /tmp/ambarisessionfile -c
> /tmp/ambarisessionfile http://ambari-host:8080/api/v1/clusters
> - Wait for 2 minutes
> - $ curl -i -b /tmp/ambarisessionfile -c /tmp/ambarisessionfile
> http://ambari-host:8080/api/v1/clusters
> The final command will still work, even though the session should be
> invalidated.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22583) Ambari should not force accounts created in IPA to be added a user named 'ambari-managed-principals'
[
https://issues.apache.org/jira/browse/AMBARI-22583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-22583:
--
Status: Patch Available (was: Reopened)
> Ambari should not force accounts created in IPA to be added a user named
> 'ambari-managed-principals'
>
>
> Key: AMBARI-22583
> URL: https://issues.apache.org/jira/browse/AMBARI-22583
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: freeipa, kerberos
> Fix For: 3.0.0
>
> Attachments: AMBARI-22583_trunk_01.patch,
> AMBARI-22583_trunk_01_amend_01.patch
>
>
> When creating user principals while enabling Kerberos using FreeIPA, Ambari
> should not force accounts to be added a user named
> 'ambari-managed-principals'.
> This occurs because the default value of {{kerberos-env/ipa_user_group}} is
> "ambari-managed-principals". To stop forcing this, the default value should
> be empty.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22583) Ambari should not force accounts created in IPA to be added a user named 'ambari-managed-principals'
[
https://issues.apache.org/jira/browse/AMBARI-22583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-22583:
--
Attachment: AMBARI-22583_trunk_01_amend_01.patch
> Ambari should not force accounts created in IPA to be added a user named
> 'ambari-managed-principals'
>
>
> Key: AMBARI-22583
> URL: https://issues.apache.org/jira/browse/AMBARI-22583
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: freeipa, kerberos
> Fix For: 3.0.0
>
> Attachments: AMBARI-22583_trunk_01.patch,
> AMBARI-22583_trunk_01_amend_01.patch
>
>
> When creating user principals while enabling Kerberos using FreeIPA, Ambari
> should not force accounts to be added a user named
> 'ambari-managed-principals'.
> This occurs because the default value of {{kerberos-env/ipa_user_group}} is
> "ambari-managed-principals". To stop forcing this, the default value should
> be empty.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22583) Ambari should not force accounts created in IPA to be added a user named 'ambari-managed-principals'
[
https://issues.apache.org/jira/browse/AMBARI-22583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16280430#comment-16280430
]
Robert Levas commented on AMBARI-22583:
---
[~adoroszlai], Thanks for catching this. I thought that I ran the unit tests,
hmm. Sorry about that.
I will do a quick fix in an amended patch.
> Ambari should not force accounts created in IPA to be added a user named
> 'ambari-managed-principals'
>
>
> Key: AMBARI-22583
> URL: https://issues.apache.org/jira/browse/AMBARI-22583
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: freeipa, kerberos
> Fix For: 3.0.0
>
> Attachments: AMBARI-22583_trunk_01.patch
>
>
> When creating user principals while enabling Kerberos using FreeIPA, Ambari
> should not force accounts to be added a user named
> 'ambari-managed-principals'.
> This occurs because the default value of {{kerberos-env/ipa_user_group}} is
> "ambari-managed-principals". To stop forcing this, the default value should
> be empty.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22600) LogFeeder: filter objects for wildcard input paths need to be cloned
[ https://issues.apache.org/jira/browse/AMBARI-22600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16280398#comment-16280398 ] Hudson commented on AMBARI-22600: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #540 (See [https://builds.apache.org/job/Ambari-branch-2.6/540/]) AMBARI-22600. LogFeeder: filters for wildcard input paths need to be (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b68b2ea53e48fa351070e9253ce1f240c46458c7]) * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/input/Input.java * (edit) ambari-logsearch/docker/test-config/logfeeder/shipper-conf/input.config-storm.json * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/filter/FilterGrok.java * (edit) ambari-logsearch/docker/test-logs/storm/worker-logs/streamline-1-TestAgg-2-3/6701/worker.log * (add) ambari-logsearch/docker/test-logs/storm/worker-logs/streamline-2-TestAgg2-4-5/6700/worker.log * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/filter/Filter.java > LogFeeder: filter objects for wildcard input paths need to be cloned > > > Key: AMBARI-22600 > URL: https://issues.apache.org/jira/browse/AMBARI-22600 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.6.1 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Critical > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (AMBARI-22583) Ambari should not force accounts created in IPA to be added a user named 'ambari-managed-principals'
[
https://issues.apache.org/jira/browse/AMBARI-22583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila reopened AMBARI-22583:
Hi [~rlevas], schema validation in
[ServicePropertiesTest|https://builds.apache.org/job/Ambari-trunk-Commit/8497/testReport/junit/org.apache.ambari.server.state/ServicePropertiesTest/validatePropertySchemaOfServiceXMLs/]
is failing due to this commit. I guess {{on-ambari-upgrade}} should not be
removed, rather set to {{false}}. Can you please check?
> Ambari should not force accounts created in IPA to be added a user named
> 'ambari-managed-principals'
>
>
> Key: AMBARI-22583
> URL: https://issues.apache.org/jira/browse/AMBARI-22583
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: freeipa, kerberos
> Fix For: 3.0.0
>
> Attachments: AMBARI-22583_trunk_01.patch
>
>
> When creating user principals while enabling Kerberos using FreeIPA, Ambari
> should not force accounts to be added a user named
> 'ambari-managed-principals'.
> This occurs because the default value of {{kerberos-env/ipa_user_group}} is
> "ambari-managed-principals". To stop forcing this, the default value should
> be empty.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-22600) LogFeeder: filter objects for wildcard input paths need to be cloned
[
https://issues.apache.org/jira/browse/AMBARI-22600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó resolved AMBARI-22600.
---
Resolution: Fixed
committed to branch 2.6:
{code:java}
commit b68b2ea53e48fa351070e9253ce1f240c46458c7
Author: Oliver Szabo
Date: Tue Dec 5 20:50:13 2017 +0100
AMBARI-22600. LogFeeder: filters for wildcard input paths need to be cloned
(oleewere)
{code}
> LogFeeder: filter objects for wildcard input paths need to be cloned
>
>
> Key: AMBARI-22600
> URL: https://issues.apache.org/jira/browse/AMBARI-22600
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.6.1
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Critical
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22583) Ambari should not force accounts created in IPA to be added a user named 'ambari-managed-principals'
[
https://issues.apache.org/jira/browse/AMBARI-22583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16280322#comment-16280322
]
Hudson commented on AMBARI-22583:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8497 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8497/])
AMBARI-22583. Ambari should not force accounts created in IPA to be (rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e973986e2292323e18282ce2fc6e75fdcdcb718f])
* (edit)
ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-30/configuration/kerberos-env.xml
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/configuration/kerberos-env.xml
* (edit)
ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-10/configuration/kerberos-env.xml
> Ambari should not force accounts created in IPA to be added a user named
> 'ambari-managed-principals'
>
>
> Key: AMBARI-22583
> URL: https://issues.apache.org/jira/browse/AMBARI-22583
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: freeipa, kerberos
> Fix For: 3.0.0
>
> Attachments: AMBARI-22583_trunk_01.patch
>
>
> When creating user principals while enabling Kerberos using FreeIPA, Ambari
> should not force accounts to be added a user named
> 'ambari-managed-principals'.
> This occurs because the default value of {{kerberos-env/ipa_user_group}} is
> "ambari-managed-principals". To stop forcing this, the default value should
> be empty.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21219) Update LDAP Authentication process to work with improved user management facility
[
https://issues.apache.org/jira/browse/AMBARI-21219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-21219:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to branch-feature-AMBARI-20859
{noformat}
commit 637c521972cb3a064bd108e97a1007be10d7ef09
Author: Robert Levas
Date: Wed Dec 6 10:00:48 2017 -0500
{noformat}
> Update LDAP Authentication process to work with improved user management
> facility
> --
>
> Key: AMBARI-21219
> URL: https://issues.apache.org/jira/browse/AMBARI-21219
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Fix For: 3.0.0
>
> Attachments: AMBARI-21219_branch-feature-AMBARI-20859_01.patch,
> AMBARI-21219_branch-feature-AMBARI-20859_02.patch
>
>
> Update LDAP Authentication process to work with improved user management
> facility
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22598) Pig service check failed after PU with LzoCodec CNF
[
https://issues.apache.org/jira/browse/AMBARI-22598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16280274#comment-16280274
]
Hudson commented on AMBARI-22598:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8496 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8496/])
AMBARI-22598 - Pig service check failed after PU with LzoCodec CNF (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=508eba0c62aa42cea5bcc660a4661ff373a5af91])
* (edit)
ambari-server/src/main/resources/common-services/PIG/0.12.0.2.0/package/scripts/pig.py
* (edit)
ambari-server/src/main/resources/common-services/MAHOUT/1.0.0.2.3/package/scripts/mahout.py
* (edit)
ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/setup_spark.py
* (edit)
ambari-server/src/main/resources/common-services/PIG/0.16.1.3.0/package/scripts/pig.py
* (edit)
ambari-server/src/main/resources/common-services/SPARK/1.2.1/package/scripts/setup_spark.py
* (edit)
ambari-server/src/main/resources/common-services/SPARK/2.2.0/package/scripts/setup_spark.py
> Pig service check failed after PU with LzoCodec CNF
> ---
>
> Key: AMBARI-22598
> URL: https://issues.apache.org/jira/browse/AMBARI-22598
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Vivek Sharma
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22598.patch
>
>
> *STR*
> # Deployed cluster with Ambari version: 2.5.1.0-159 and HDP version:
> 2.6.1.0-129 (HDFS has lzo enabled)
> # Upgrade Ambari to Target Version: 2.6.1.0-84
> # Perform full stack upgrade to 2.6.4.0-55
> # Perform 4th digit PU of some services in batches (see attached for list)
> # Run Pig service check
> *Result*
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/PIG/0.12.0.2.0/package/scripts/service_check.py",
> line 141, in
> PigServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 367, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/PIG/0.12.0.2.0/package/scripts/service_check.py",
> line 85, in service_check
> 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 'pig
> /var/lib/ambari-agent/tmp/pigSmoke.sh' returned 6. 17/12/04 12:07:26 INFO
> pig.ExecTypeProvider: Trying ExecType : LOCAL
> 17/12/04 12:07:26 INFO pig.ExecTypeProvider: Trying ExecType : MAPREDUCE
> 17/12/04 12:07:26 INFO pig.ExecTypeProvider: Trying ExecType : TEZ_LOCAL
> 17/12/04 12:07:26 INFO pig.ExecTypeProvider: Trying ExecType : TEZ
> 17/12/04 12:07:26 INFO pig.ExecTypeProvider: Picked TEZ as the ExecType
> 2017-12-04 12:07:27,044 [main] INFO org.apache.pig.Main - Apache Pig version
> 0.16.0.2.6.4.1-12 (rexported) compiled Nov 29 2017, 15:19:29
> 2017-12-04 12:07:27,044 [main] INFO org.apache.pig.Main - Logging error
> messages to: /home/ambari-qa/pig_1512389247042.log
> 2017-12-04 12:07:27,738 [main] INFO org.apache.pig.impl.util.Utils - Default
> bootup file /home/ambari-qa/.pigbootup not found
> 2017-12-04 12:07:27,860 [main] INFO
> org.apache.pig.backend.hadoop.executionengine.HExecutionEngine - Connecting
> to hadoop file system at:
> hdfs://ctr-e135-1512069032975-4843-01-06.hwx.site:8020
> 2017-12-04 12:07:28,422 [main] INFO org.apache.pig.PigServer - Pig Script ID
> for the session: PIG-pigSmoke.sh-04da505f-7f53-4f4d-bab5-be5732c283fb
> 2017-12-04 12:07:28,743 [main]
[jira] [Updated] (AMBARI-22583) Ambari should not force accounts created in IPA to be added a user named 'ambari-managed-principals'
[
https://issues.apache.org/jira/browse/AMBARI-22583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-22583:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
{noformat}
commit e973986e2292323e18282ce2fc6e75fdcdcb718f
Author: Robert Levas
Date: Wed Dec 6 09:20:24 2017 -0500
{noformat}
> Ambari should not force accounts created in IPA to be added a user named
> 'ambari-managed-principals'
>
>
> Key: AMBARI-22583
> URL: https://issues.apache.org/jira/browse/AMBARI-22583
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: freeipa, kerberos
> Fix For: 3.0.0
>
> Attachments: AMBARI-22583_trunk_01.patch
>
>
> When creating user principals while enabling Kerberos using FreeIPA, Ambari
> should not force accounts to be added a user named
> 'ambari-managed-principals'.
> This occurs because the default value of {{kerberos-env/ipa_user_group}} is
> "ambari-managed-principals". To stop forcing this, the default value should
> be empty.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22604) Fix hostConfigMappingEntity cluster_id, concurrency in ClusterImpl and serviceConfigTypes initialization
Dmytro Sen created AMBARI-22604: --- Summary: Fix hostConfigMappingEntity cluster_id, concurrency in ClusterImpl and serviceConfigTypes initialization Key: AMBARI-22604 URL: https://issues.apache.org/jira/browse/AMBARI-22604 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: ambari-server Reporter: Dmytro Sen Assignee: Dmytro Sen Priority: Critical Fix For: 3.0.0 1) HostConfigMappingEntity is not correct. You can't use same field cluster_id for current entity and for joined columns. Use ClusterTest.testDesiredConfig() to see this issue. 2) As you can see in ClusterImpl we are using concurrent maps/lists and locks in methods. Please do the same for your code chnages. 3) Initialize map serviceConfigTypes, it will prevent many NPE and additional check for NULL. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22598) Pig service check failed after PU with LzoCodec CNF
[
https://issues.apache.org/jira/browse/AMBARI-22598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16280226#comment-16280226
]
Hudson commented on AMBARI-22598:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #539 (See
[https://builds.apache.org/job/Ambari-branch-2.6/539/])
AMBARI-22598 - Pig service check failed after PU with LzoCodec CNF (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=973ec464063196e03652ce01912aef4b24bcc07f])
* (edit)
ambari-server/src/main/resources/common-services/MAHOUT/1.0.0.2.3/package/scripts/mahout.py
* (edit)
ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/setup_spark.py
* (edit)
ambari-server/src/main/resources/common-services/SPARK/1.2.1/package/scripts/setup_spark.py
* (edit)
ambari-server/src/main/resources/common-services/PIG/0.12.0.2.0/package/scripts/pig.py
> Pig service check failed after PU with LzoCodec CNF
> ---
>
> Key: AMBARI-22598
> URL: https://issues.apache.org/jira/browse/AMBARI-22598
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Vivek Sharma
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22598.patch
>
>
> *STR*
> # Deployed cluster with Ambari version: 2.5.1.0-159 and HDP version:
> 2.6.1.0-129 (HDFS has lzo enabled)
> # Upgrade Ambari to Target Version: 2.6.1.0-84
> # Perform full stack upgrade to 2.6.4.0-55
> # Perform 4th digit PU of some services in batches (see attached for list)
> # Run Pig service check
> *Result*
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/PIG/0.12.0.2.0/package/scripts/service_check.py",
> line 141, in
> PigServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 367, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/PIG/0.12.0.2.0/package/scripts/service_check.py",
> line 85, in service_check
> 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 'pig
> /var/lib/ambari-agent/tmp/pigSmoke.sh' returned 6. 17/12/04 12:07:26 INFO
> pig.ExecTypeProvider: Trying ExecType : LOCAL
> 17/12/04 12:07:26 INFO pig.ExecTypeProvider: Trying ExecType : MAPREDUCE
> 17/12/04 12:07:26 INFO pig.ExecTypeProvider: Trying ExecType : TEZ_LOCAL
> 17/12/04 12:07:26 INFO pig.ExecTypeProvider: Trying ExecType : TEZ
> 17/12/04 12:07:26 INFO pig.ExecTypeProvider: Picked TEZ as the ExecType
> 2017-12-04 12:07:27,044 [main] INFO org.apache.pig.Main - Apache Pig version
> 0.16.0.2.6.4.1-12 (rexported) compiled Nov 29 2017, 15:19:29
> 2017-12-04 12:07:27,044 [main] INFO org.apache.pig.Main - Logging error
> messages to: /home/ambari-qa/pig_1512389247042.log
> 2017-12-04 12:07:27,738 [main] INFO org.apache.pig.impl.util.Utils - Default
> bootup file /home/ambari-qa/.pigbootup not found
> 2017-12-04 12:07:27,860 [main] INFO
> org.apache.pig.backend.hadoop.executionengine.HExecutionEngine - Connecting
> to hadoop file system at:
> hdfs://ctr-e135-1512069032975-4843-01-06.hwx.site:8020
> 2017-12-04 12:07:28,422 [main] INFO org.apache.pig.PigServer - Pig Script ID
> for the session: PIG-pigSmoke.sh-04da505f-7f53-4f4d-bab5-be5732c283fb
> 2017-12-04 12:07:28,743 [main] INFO
> org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl - Timeline service
> address:
> http://ctr-e135-1512069032975-4843-01-03.hwx.site:8188/ws/v1/timeline/
> 2017-12-04 12:07:28,994 [main]
[jira] [Commented] (AMBARI-22592) Set ambari.repo. in ambari-server setup script
[
https://issues.apache.org/jira/browse/AMBARI-22592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16280213#comment-16280213
]
Hadoop QA commented on AMBARI-22592:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12900850/AMBARI-22592.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12804//console
This message is automatically generated.
> Set ambari.repo. in ambari-server setup script
> -
>
> Key: AMBARI-22592
> URL: https://issues.apache.org/jira/browse/AMBARI-22592
> Project: Ambari
> Issue Type: Sub-task
> Components: ambari-server
>Reporter: Yussuf Shaikh
>Assignee: Yussuf Shaikh
>Priority: Minor
> Attachments: AMBARI-22592.patch
>
>
> Allow to store Ambari repo base URL for each OS type.
> The ambari-server setup script needs to be update to include Ambari repo base
> URL for each OS type to support Hybrid setup.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22598) Pig service check failed after PU with LzoCodec CNF
[
https://issues.apache.org/jira/browse/AMBARI-22598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-22598:
-
Status: Patch Available (was: Open)
> Pig service check failed after PU with LzoCodec CNF
> ---
>
> Key: AMBARI-22598
> URL: https://issues.apache.org/jira/browse/AMBARI-22598
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Vivek Sharma
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22598.patch
>
>
> *STR*
> # Deployed cluster with Ambari version: 2.5.1.0-159 and HDP version:
> 2.6.1.0-129 (HDFS has lzo enabled)
> # Upgrade Ambari to Target Version: 2.6.1.0-84
> # Perform full stack upgrade to 2.6.4.0-55
> # Perform 4th digit PU of some services in batches (see attached for list)
> # Run Pig service check
> *Result*
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/PIG/0.12.0.2.0/package/scripts/service_check.py",
> line 141, in
> PigServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 367, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/PIG/0.12.0.2.0/package/scripts/service_check.py",
> line 85, in service_check
> 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 'pig
> /var/lib/ambari-agent/tmp/pigSmoke.sh' returned 6. 17/12/04 12:07:26 INFO
> pig.ExecTypeProvider: Trying ExecType : LOCAL
> 17/12/04 12:07:26 INFO pig.ExecTypeProvider: Trying ExecType : MAPREDUCE
> 17/12/04 12:07:26 INFO pig.ExecTypeProvider: Trying ExecType : TEZ_LOCAL
> 17/12/04 12:07:26 INFO pig.ExecTypeProvider: Trying ExecType : TEZ
> 17/12/04 12:07:26 INFO pig.ExecTypeProvider: Picked TEZ as the ExecType
> 2017-12-04 12:07:27,044 [main] INFO org.apache.pig.Main - Apache Pig version
> 0.16.0.2.6.4.1-12 (rexported) compiled Nov 29 2017, 15:19:29
> 2017-12-04 12:07:27,044 [main] INFO org.apache.pig.Main - Logging error
> messages to: /home/ambari-qa/pig_1512389247042.log
> 2017-12-04 12:07:27,738 [main] INFO org.apache.pig.impl.util.Utils - Default
> bootup file /home/ambari-qa/.pigbootup not found
> 2017-12-04 12:07:27,860 [main] INFO
> org.apache.pig.backend.hadoop.executionengine.HExecutionEngine - Connecting
> to hadoop file system at:
> hdfs://ctr-e135-1512069032975-4843-01-06.hwx.site:8020
> 2017-12-04 12:07:28,422 [main] INFO org.apache.pig.PigServer - Pig Script ID
> for the session: PIG-pigSmoke.sh-04da505f-7f53-4f4d-bab5-be5732c283fb
> 2017-12-04 12:07:28,743 [main] INFO
> org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl - Timeline service
> address:
> http://ctr-e135-1512069032975-4843-01-03.hwx.site:8188/ws/v1/timeline/
> 2017-12-04 12:07:28,994 [main] INFO
> org.apache.pig.backend.hadoop.PigATSClient - Created ATS Hook
> 2017-12-04 12:07:29,800 [main] INFO org.apache.hadoop.hdfs.DFSClient -
> Created HDFS_DELEGATION_TOKEN token 1084 for ambari-qa on 172.27.73.145:8020
> 2017-12-04 12:07:29,827 [main] INFO
> org.apache.hadoop.mapreduce.security.TokenCache - Got dt for
> hdfs://ctr-e135-1512069032975-4843-01-06.hwx.site:8020; Kind:
> HDFS_DELEGATION_TOKEN, Service: 172.27.73.145:8020, Ident:
> (HDFS_DELEGATION_TOKEN token 1084 for ambari-qa)
> 2017-12-04 12:07:29,844 [main] INFO
> org.apache.pig.tools.pigstats.ScriptState - Pig features used in the script:
> UNKNOWN
> 2017-12-04 12:07:29,895 [main] INFO
[jira] [Updated] (AMBARI-22598) Pig service check failed after PU with LzoCodec CNF
[
https://issues.apache.org/jira/browse/AMBARI-22598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-22598:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Pig service check failed after PU with LzoCodec CNF
> ---
>
> Key: AMBARI-22598
> URL: https://issues.apache.org/jira/browse/AMBARI-22598
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Vivek Sharma
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22598.patch
>
>
> *STR*
> # Deployed cluster with Ambari version: 2.5.1.0-159 and HDP version:
> 2.6.1.0-129 (HDFS has lzo enabled)
> # Upgrade Ambari to Target Version: 2.6.1.0-84
> # Perform full stack upgrade to 2.6.4.0-55
> # Perform 4th digit PU of some services in batches (see attached for list)
> # Run Pig service check
> *Result*
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/PIG/0.12.0.2.0/package/scripts/service_check.py",
> line 141, in
> PigServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 367, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/PIG/0.12.0.2.0/package/scripts/service_check.py",
> line 85, in service_check
> 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 'pig
> /var/lib/ambari-agent/tmp/pigSmoke.sh' returned 6. 17/12/04 12:07:26 INFO
> pig.ExecTypeProvider: Trying ExecType : LOCAL
> 17/12/04 12:07:26 INFO pig.ExecTypeProvider: Trying ExecType : MAPREDUCE
> 17/12/04 12:07:26 INFO pig.ExecTypeProvider: Trying ExecType : TEZ_LOCAL
> 17/12/04 12:07:26 INFO pig.ExecTypeProvider: Trying ExecType : TEZ
> 17/12/04 12:07:26 INFO pig.ExecTypeProvider: Picked TEZ as the ExecType
> 2017-12-04 12:07:27,044 [main] INFO org.apache.pig.Main - Apache Pig version
> 0.16.0.2.6.4.1-12 (rexported) compiled Nov 29 2017, 15:19:29
> 2017-12-04 12:07:27,044 [main] INFO org.apache.pig.Main - Logging error
> messages to: /home/ambari-qa/pig_1512389247042.log
> 2017-12-04 12:07:27,738 [main] INFO org.apache.pig.impl.util.Utils - Default
> bootup file /home/ambari-qa/.pigbootup not found
> 2017-12-04 12:07:27,860 [main] INFO
> org.apache.pig.backend.hadoop.executionengine.HExecutionEngine - Connecting
> to hadoop file system at:
> hdfs://ctr-e135-1512069032975-4843-01-06.hwx.site:8020
> 2017-12-04 12:07:28,422 [main] INFO org.apache.pig.PigServer - Pig Script ID
> for the session: PIG-pigSmoke.sh-04da505f-7f53-4f4d-bab5-be5732c283fb
> 2017-12-04 12:07:28,743 [main] INFO
> org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl - Timeline service
> address:
> http://ctr-e135-1512069032975-4843-01-03.hwx.site:8188/ws/v1/timeline/
> 2017-12-04 12:07:28,994 [main] INFO
> org.apache.pig.backend.hadoop.PigATSClient - Created ATS Hook
> 2017-12-04 12:07:29,800 [main] INFO org.apache.hadoop.hdfs.DFSClient -
> Created HDFS_DELEGATION_TOKEN token 1084 for ambari-qa on 172.27.73.145:8020
> 2017-12-04 12:07:29,827 [main] INFO
> org.apache.hadoop.mapreduce.security.TokenCache - Got dt for
> hdfs://ctr-e135-1512069032975-4843-01-06.hwx.site:8020; Kind:
> HDFS_DELEGATION_TOKEN, Service: 172.27.73.145:8020, Ident:
> (HDFS_DELEGATION_TOKEN token 1084 for ambari-qa)
> 2017-12-04 12:07:29,844 [main] INFO
> org.apache.pig.tools.pigstats.ScriptState - Pig features used in the script:
> UNKNOWN
> 2017-12-04
[jira] [Updated] (AMBARI-22598) Pig service check failed after PU with LzoCodec CNF
[
https://issues.apache.org/jira/browse/AMBARI-22598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-22598:
-
Attachment: AMBARI-22598.patch
> Pig service check failed after PU with LzoCodec CNF
> ---
>
> Key: AMBARI-22598
> URL: https://issues.apache.org/jira/browse/AMBARI-22598
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Vivek Sharma
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22598.patch
>
>
> *STR*
> # Deployed cluster with Ambari version: 2.5.1.0-159 and HDP version:
> 2.6.1.0-129 (HDFS has lzo enabled)
> # Upgrade Ambari to Target Version: 2.6.1.0-84
> # Perform full stack upgrade to 2.6.4.0-55
> # Perform 4th digit PU of some services in batches (see attached for list)
> # Run Pig service check
> *Result*
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/PIG/0.12.0.2.0/package/scripts/service_check.py",
> line 141, in
> PigServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 367, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/PIG/0.12.0.2.0/package/scripts/service_check.py",
> line 85, in service_check
> 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 'pig
> /var/lib/ambari-agent/tmp/pigSmoke.sh' returned 6. 17/12/04 12:07:26 INFO
> pig.ExecTypeProvider: Trying ExecType : LOCAL
> 17/12/04 12:07:26 INFO pig.ExecTypeProvider: Trying ExecType : MAPREDUCE
> 17/12/04 12:07:26 INFO pig.ExecTypeProvider: Trying ExecType : TEZ_LOCAL
> 17/12/04 12:07:26 INFO pig.ExecTypeProvider: Trying ExecType : TEZ
> 17/12/04 12:07:26 INFO pig.ExecTypeProvider: Picked TEZ as the ExecType
> 2017-12-04 12:07:27,044 [main] INFO org.apache.pig.Main - Apache Pig version
> 0.16.0.2.6.4.1-12 (rexported) compiled Nov 29 2017, 15:19:29
> 2017-12-04 12:07:27,044 [main] INFO org.apache.pig.Main - Logging error
> messages to: /home/ambari-qa/pig_1512389247042.log
> 2017-12-04 12:07:27,738 [main] INFO org.apache.pig.impl.util.Utils - Default
> bootup file /home/ambari-qa/.pigbootup not found
> 2017-12-04 12:07:27,860 [main] INFO
> org.apache.pig.backend.hadoop.executionengine.HExecutionEngine - Connecting
> to hadoop file system at:
> hdfs://ctr-e135-1512069032975-4843-01-06.hwx.site:8020
> 2017-12-04 12:07:28,422 [main] INFO org.apache.pig.PigServer - Pig Script ID
> for the session: PIG-pigSmoke.sh-04da505f-7f53-4f4d-bab5-be5732c283fb
> 2017-12-04 12:07:28,743 [main] INFO
> org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl - Timeline service
> address:
> http://ctr-e135-1512069032975-4843-01-03.hwx.site:8188/ws/v1/timeline/
> 2017-12-04 12:07:28,994 [main] INFO
> org.apache.pig.backend.hadoop.PigATSClient - Created ATS Hook
> 2017-12-04 12:07:29,800 [main] INFO org.apache.hadoop.hdfs.DFSClient -
> Created HDFS_DELEGATION_TOKEN token 1084 for ambari-qa on 172.27.73.145:8020
> 2017-12-04 12:07:29,827 [main] INFO
> org.apache.hadoop.mapreduce.security.TokenCache - Got dt for
> hdfs://ctr-e135-1512069032975-4843-01-06.hwx.site:8020; Kind:
> HDFS_DELEGATION_TOKEN, Service: 172.27.73.145:8020, Ident:
> (HDFS_DELEGATION_TOKEN token 1084 for ambari-qa)
> 2017-12-04 12:07:29,844 [main] INFO
> org.apache.pig.tools.pigstats.ScriptState - Pig features used in the script:
> UNKNOWN
> 2017-12-04 12:07:29,895 [main] INFO
[jira] [Commented] (AMBARI-22596) Ambari Builds Are Failing With Python Test Errors
[
https://issues.apache.org/jira/browse/AMBARI-22596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16280143#comment-16280143
]
Hadoop QA commented on AMBARI-22596:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12900854/AMBARI-22596.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12803//console
This message is automatically generated.
> Ambari Builds Are Failing With Python Test Errors
> -
>
> Key: AMBARI-22596
> URL: https://issues.apache.org/jira/browse/AMBARI-22596
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22596.patch
>
>
> Ambari builds have been failing for a long time:
> https://builds.apache.org/job/Ambari-branch-2.6
> Looks like some Python problems:
> {code}
> ==
> ERROR: test_check_database_name_property (TestAmbariServer.TestAmbariServer)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-branch-2.6/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-branch-2.6/ambari-server/src/test/python/TestAmbariServer.py",
> line 7997, in test_check_database_name_property
> args = parser.parse_args()
> File "/usr/lib/python2.7/optparse.py", line 1402, in parse_args
> self.error(str(err))
> File "/usr/lib/python2.7/optparse.py", line 1584, in error
> self.exit(2, "%s: error: %s\n" % (self.get_prog_name(), msg))
> File "/usr/lib/python2.7/optparse.py", line 1574, in exit
> sys.exit(status)
> SystemExit: 2
> --
> Ran 276 tests in 7.423s
> FAILED (errors=1)
> --
> Failed tests:
> ERROR: test_check_database_name_property (TestAmbariServer.TestAmbariServer)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-branch-2.6/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-branch-2.6/ambari-server/src/test/python/TestAmbariServer.py",
> line 7997, in test_check_database_name_property
> args = parser.parse_args()
> File "/usr/lib/python2.7/optparse.py", line 1402, in parse_args
> self.error(str(err))
> File "/usr/lib/python2.7/optparse.py", line 1584, in error
> self.exit(2, "%s: error: %s\n" % (self.get_prog_name(), msg))
> File "/usr/lib/python2.7/optparse.py", line 1574, in exit
> sys.exit(status)
> SystemExit: 2
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22596) Ambari Builds Are Failing With Python Test Errors
[
https://issues.apache.org/jira/browse/AMBARI-22596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16280129#comment-16280129
]
Hudson commented on AMBARI-22596:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #538 (See
[https://builds.apache.org/job/Ambari-branch-2.6/538/])
AMBARI-22596. Ambari Builds Are Failing With Python Test Errors (aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f52e5f93effdaaceb13a3f8d201b26e052f559c1])
* (edit) ambari-server/src/test/python/TestAmbariServer.py
> Ambari Builds Are Failing With Python Test Errors
> -
>
> Key: AMBARI-22596
> URL: https://issues.apache.org/jira/browse/AMBARI-22596
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22596.patch
>
>
> Ambari builds have been failing for a long time:
> https://builds.apache.org/job/Ambari-branch-2.6
> Looks like some Python problems:
> {code}
> ==
> ERROR: test_check_database_name_property (TestAmbariServer.TestAmbariServer)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-branch-2.6/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-branch-2.6/ambari-server/src/test/python/TestAmbariServer.py",
> line 7997, in test_check_database_name_property
> args = parser.parse_args()
> File "/usr/lib/python2.7/optparse.py", line 1402, in parse_args
> self.error(str(err))
> File "/usr/lib/python2.7/optparse.py", line 1584, in error
> self.exit(2, "%s: error: %s\n" % (self.get_prog_name(), msg))
> File "/usr/lib/python2.7/optparse.py", line 1574, in exit
> sys.exit(status)
> SystemExit: 2
> --
> Ran 276 tests in 7.423s
> FAILED (errors=1)
> --
> Failed tests:
> ERROR: test_check_database_name_property (TestAmbariServer.TestAmbariServer)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-branch-2.6/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-branch-2.6/ambari-server/src/test/python/TestAmbariServer.py",
> line 7997, in test_check_database_name_property
> args = parser.parse_args()
> File "/usr/lib/python2.7/optparse.py", line 1402, in parse_args
> self.error(str(err))
> File "/usr/lib/python2.7/optparse.py", line 1584, in error
> self.exit(2, "%s: error: %s\n" % (self.get_prog_name(), msg))
> File "/usr/lib/python2.7/optparse.py", line 1574, in exit
> sys.exit(status)
> SystemExit: 2
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22596) Ambari Builds Are Failing With Python Test Errors
[
https://issues.apache.org/jira/browse/AMBARI-22596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-22596:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to branch-2.6
> Ambari Builds Are Failing With Python Test Errors
> -
>
> Key: AMBARI-22596
> URL: https://issues.apache.org/jira/browse/AMBARI-22596
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22596.patch
>
>
> Ambari builds have been failing for a long time:
> https://builds.apache.org/job/Ambari-branch-2.6
> Looks like some Python problems:
> {code}
> ==
> ERROR: test_check_database_name_property (TestAmbariServer.TestAmbariServer)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-branch-2.6/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-branch-2.6/ambari-server/src/test/python/TestAmbariServer.py",
> line 7997, in test_check_database_name_property
> args = parser.parse_args()
> File "/usr/lib/python2.7/optparse.py", line 1402, in parse_args
> self.error(str(err))
> File "/usr/lib/python2.7/optparse.py", line 1584, in error
> self.exit(2, "%s: error: %s\n" % (self.get_prog_name(), msg))
> File "/usr/lib/python2.7/optparse.py", line 1574, in exit
> sys.exit(status)
> SystemExit: 2
> --
> Ran 276 tests in 7.423s
> FAILED (errors=1)
> --
> Failed tests:
> ERROR: test_check_database_name_property (TestAmbariServer.TestAmbariServer)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-branch-2.6/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-branch-2.6/ambari-server/src/test/python/TestAmbariServer.py",
> line 7997, in test_check_database_name_property
> args = parser.parse_args()
> File "/usr/lib/python2.7/optparse.py", line 1402, in parse_args
> self.error(str(err))
> File "/usr/lib/python2.7/optparse.py", line 1584, in error
> self.exit(2, "%s: error: %s\n" % (self.get_prog_name(), msg))
> File "/usr/lib/python2.7/optparse.py", line 1574, in exit
> sys.exit(status)
> SystemExit: 2
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22596) Ambari Builds Are Failing With Python Test Errors
[
https://issues.apache.org/jira/browse/AMBARI-22596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-22596:
-
Attachment: AMBARI-22596.patch
> Ambari Builds Are Failing With Python Test Errors
> -
>
> Key: AMBARI-22596
> URL: https://issues.apache.org/jira/browse/AMBARI-22596
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22596.patch
>
>
> Ambari builds have been failing for a long time:
> https://builds.apache.org/job/Ambari-branch-2.6
> Looks like some Python problems:
> {code}
> ==
> ERROR: test_check_database_name_property (TestAmbariServer.TestAmbariServer)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-branch-2.6/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-branch-2.6/ambari-server/src/test/python/TestAmbariServer.py",
> line 7997, in test_check_database_name_property
> args = parser.parse_args()
> File "/usr/lib/python2.7/optparse.py", line 1402, in parse_args
> self.error(str(err))
> File "/usr/lib/python2.7/optparse.py", line 1584, in error
> self.exit(2, "%s: error: %s\n" % (self.get_prog_name(), msg))
> File "/usr/lib/python2.7/optparse.py", line 1574, in exit
> sys.exit(status)
> SystemExit: 2
> --
> Ran 276 tests in 7.423s
> FAILED (errors=1)
> --
> Failed tests:
> ERROR: test_check_database_name_property (TestAmbariServer.TestAmbariServer)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-branch-2.6/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-branch-2.6/ambari-server/src/test/python/TestAmbariServer.py",
> line 7997, in test_check_database_name_property
> args = parser.parse_args()
> File "/usr/lib/python2.7/optparse.py", line 1402, in parse_args
> self.error(str(err))
> File "/usr/lib/python2.7/optparse.py", line 1584, in error
> self.exit(2, "%s: error: %s\n" % (self.get_prog_name(), msg))
> File "/usr/lib/python2.7/optparse.py", line 1574, in exit
> sys.exit(status)
> SystemExit: 2
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22596) Ambari Builds Are Failing With Python Test Errors
[
https://issues.apache.org/jira/browse/AMBARI-22596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-22596:
-
Status: Patch Available (was: Open)
> Ambari Builds Are Failing With Python Test Errors
> -
>
> Key: AMBARI-22596
> URL: https://issues.apache.org/jira/browse/AMBARI-22596
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22596.patch
>
>
> Ambari builds have been failing for a long time:
> https://builds.apache.org/job/Ambari-branch-2.6
> Looks like some Python problems:
> {code}
> ==
> ERROR: test_check_database_name_property (TestAmbariServer.TestAmbariServer)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-branch-2.6/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-branch-2.6/ambari-server/src/test/python/TestAmbariServer.py",
> line 7997, in test_check_database_name_property
> args = parser.parse_args()
> File "/usr/lib/python2.7/optparse.py", line 1402, in parse_args
> self.error(str(err))
> File "/usr/lib/python2.7/optparse.py", line 1584, in error
> self.exit(2, "%s: error: %s\n" % (self.get_prog_name(), msg))
> File "/usr/lib/python2.7/optparse.py", line 1574, in exit
> sys.exit(status)
> SystemExit: 2
> --
> Ran 276 tests in 7.423s
> FAILED (errors=1)
> --
> Failed tests:
> ERROR: test_check_database_name_property (TestAmbariServer.TestAmbariServer)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-branch-2.6/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-branch-2.6/ambari-server/src/test/python/TestAmbariServer.py",
> line 7997, in test_check_database_name_property
> args = parser.parse_args()
> File "/usr/lib/python2.7/optparse.py", line 1402, in parse_args
> self.error(str(err))
> File "/usr/lib/python2.7/optparse.py", line 1584, in error
> self.exit(2, "%s: error: %s\n" % (self.get_prog_name(), msg))
> File "/usr/lib/python2.7/optparse.py", line 1574, in exit
> sys.exit(status)
> SystemExit: 2
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22592) Set ambari.repo. in ambari-server setup script
[ https://issues.apache.org/jira/browse/AMBARI-22592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yussuf Shaikh updated AMBARI-22592: --- Status: Patch Available (was: In Progress) Submitting the patch file on behalf of [~skanekar] > Set ambari.repo. in ambari-server setup script > - > > Key: AMBARI-22592 > URL: https://issues.apache.org/jira/browse/AMBARI-22592 > Project: Ambari > Issue Type: Sub-task > Components: ambari-server >Reporter: Yussuf Shaikh >Assignee: Yussuf Shaikh >Priority: Minor > Attachments: AMBARI-22592.patch > > > Allow to store Ambari repo base URL for each OS type. > The ambari-server setup script needs to be update to include Ambari repo base > URL for each OS type to support Hybrid setup. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22592) Set ambari.repo. in ambari-server setup script
[ https://issues.apache.org/jira/browse/AMBARI-22592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yussuf Shaikh updated AMBARI-22592: --- Attachment: AMBARI-22592.patch > Set ambari.repo. in ambari-server setup script > - > > Key: AMBARI-22592 > URL: https://issues.apache.org/jira/browse/AMBARI-22592 > Project: Ambari > Issue Type: Sub-task > Components: ambari-server >Reporter: Yussuf Shaikh >Assignee: Yussuf Shaikh >Priority: Minor > Attachments: AMBARI-22592.patch > > > Allow to store Ambari repo base URL for each OS type. > The ambari-server setup script needs to be update to include Ambari repo base > URL for each OS type to support Hybrid setup. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-22492) A bad WebHDFS request is issued when starting Hive Metastore
[
https://issues.apache.org/jira/browse/AMBARI-22492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Magyar reassigned AMBARI-22492:
--
Assignee: Attila Magyar
> A bad WebHDFS request is issued when starting Hive Metastore
>
>
> Key: AMBARI-22492
> URL: https://issues.apache.org/jira/browse/AMBARI-22492
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: David Tucker
>Assignee: Attila Magyar
>
> When deploying a cluster with Hive (1.2.1000, in this case), Ambari issues an
> incorrect WebHDFS request:
> {code}
> 2017-11-20 20:21:21,839 - call['ambari-sudo.sh su hdfs -l -s /bin/bash -c
> 'curl -sS -L -w '"'"'%{http_code}'"'"' -X GET
> '"'"'http://dtucker-rjy277d.west.isilon.com:8082/webhdfs/v1?op=GETFILESTATUS=hdfs'"'"'
> 1>/tmp/tmpzipnFe 2>/tmp/tmpbGajx_''] {'logoutput': None, 'quiet': False}
> {code}
> That command should be:
> {code}
> curl -sS -L -w '%{http_code}' -X GET
> 'http://dtucker-rjy277d.west.isilon.com:8082/webhdfs/v1/?op=GETFILESTATUS=hdfs'
> {code}
> (Note the / after v1.)
> On Apache, this results in a FileNotFoundException (404); however, this
> causes problems with OneFS which returns an IllegalArgumentException (400)
> and prevents the Metastore from starting.
> Here is the full traceback:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 203, in
>HiveMetastore().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 367, in execute
>method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 54, in start
>self.configure(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 120, in locking_configure
>original_configure(obj, *args, **kw)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 72, in configure
>hive(name = 'metastore')
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
>return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py",
> line 343, in hive
>mode = 01777)
> 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/libraries/providers/hdfs_resource.py",
> line 604, in action_create_on_execute
>self.action_delayed("create")
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 601, in action_delayed
>self.get_hdfs_resource_executor().action_delayed(action_name, self)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 328, in action_delayed
>self._assert_valid()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 287, in _assert_valid
>self.target_status = self._get_file_status(target)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 430, in _get_file_status
>list_status = self.util.run_command(target, 'GETFILESTATUS', method='GET',
> ignore_status_codes=['404'], assertable_result=False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 177, in run_command
>return self._run_command(*args, **kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 248, in _run_command
>raise WebHDFSCallException(err_msg, result_dict)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22591) MD interpreter fails with NPE (Zeppelin)
[ https://issues.apache.org/jira/browse/AMBARI-22591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16279985#comment-16279985 ] Hudson commented on AMBARI-22591: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8495 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8495/]) AMBARI-22591.MD interpreter fails with NPE (Zeppelin)(Prabhjyot Singh (venkatasairam.lanka: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=97ceed034a8d23f5caf6276fa48c02332d58c234]) * (edit) ambari-server/src/test/python/stacks/2.6/ZEPPELIN/interpreter_json_generated.py * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.7.0/package/scripts/interpreter_json_template.py > MD interpreter fails with NPE (Zeppelin) > > > Key: AMBARI-22591 > URL: https://issues.apache.org/jira/browse/AMBARI-22591 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.6.0 >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: AMBARI-22591_trunk_v1.patch > > > While trying to run multiple MarkDown paragraph at once since pegdown-parser > is not thread safe, it fails to render HTLM. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22595) Livy2 keytabs are not getting configured automatically in zeppelin
[
https://issues.apache.org/jira/browse/AMBARI-22595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16279972#comment-16279972
]
Hadoop QA commented on AMBARI-22595:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12900834/AMBARI-22595_trunk_v1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12802//console
This message is automatically generated.
> Livy2 keytabs are not getting configured automatically in zeppelin
> --
>
> Key: AMBARI-22595
> URL: https://issues.apache.org/jira/browse/AMBARI-22595
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.1
> Environment: HDP-2.6.4.0-55
> ambari-server --version 2.6.1.0-91
>Reporter: Supreeth Sharma
>Assignee: Prabhjyot Singh
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22595_trunk_v1.patch, zeppelin.png
>
>
> 'zeppelin.livy.keytab' and 'zeppelin.livy.principal' are not configured for
> zeppelin after installation on secured cluster.
> Because of this zeppelin notebook with livy interpreter is failing with
> un-authenticated 401 error:
> {code:java}
> org.apache.zeppelin.livy.LivyException: Error with 401 StatusCode:
>
>
> Error 401
>
>
> HTTP ERROR: 401
> Problem accessing /version. Reason:
> Authentication required
> Powered by Jetty://
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22591) MD interpreter fails with NPE (Zeppelin)
[ https://issues.apache.org/jira/browse/AMBARI-22591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16279960#comment-16279960 ] Hudson commented on AMBARI-22591: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #537 (See [https://builds.apache.org/job/Ambari-branch-2.6/537/]) AMBARI-22591.MD interpreter fails with NPE (Zeppelin)(Prabhjyot Singh (venkatasairam.lanka: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8de808b78debcaec63a658435607c1d1f7b8d10c]) * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.7.0/package/scripts/interpreter_json_template.py > MD interpreter fails with NPE (Zeppelin) > > > Key: AMBARI-22591 > URL: https://issues.apache.org/jira/browse/AMBARI-22591 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.6.0 >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: AMBARI-22591_trunk_v1.patch > > > While trying to run multiple MarkDown paragraph at once since pegdown-parser > is not thread safe, it fails to render HTLM. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22602) Add 'clusterSettings' and 'stackSettings' parameters in Execution Command.
[ https://issues.apache.org/jira/browse/AMBARI-22602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-22602: - Issue Type: Task (was: Bug) > Add 'clusterSettings' and 'stackSettings' parameters in Execution Command. > --- > > Key: AMBARI-22602 > URL: https://issues.apache.org/jira/browse/AMBARI-22602 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 3.0.0 > > > AMBARI-22198 added "stack settings", and AMBARI-22196 introduced "cluster > settings" in Ambari. > This JIRA adds 2 new parameters to Execution Command : *(1).* clusterSettings > and *(2).* stackSettings, and adds their respective set of key-values pairs. > - This enables these parameters to be passed in to the ambari-agent's > *command\*.json*. > CC [~jluniya] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22603) Add Unit Tests for AMBARI-22602 (Add 'clusterSettings' and 'stackSettings' parameters in Execution Command.)
[ https://issues.apache.org/jira/browse/AMBARI-22603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-22603: - Issue Type: Task (was: Bug) > Add Unit Tests for AMBARI-22602 (Add 'clusterSettings' and 'stackSettings' > parameters in Execution Command.) > > > Key: AMBARI-22603 > URL: https://issues.apache.org/jira/browse/AMBARI-22603 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22603) Add Unit Tests for AMBARI-22602 (Add 'clusterSettings' and 'stackSettings' parameters in Execution Command.)
Swapan Shridhar created AMBARI-22603: Summary: Add Unit Tests for AMBARI-22602 (Add 'clusterSettings' and 'stackSettings' parameters in Execution Command.) Key: AMBARI-22603 URL: https://issues.apache.org/jira/browse/AMBARI-22603 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Swapan Shridhar Assignee: Swapan Shridhar Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22602) Add 'clusterSettings' and 'stackSettings' parameters in Execution Command.
[ https://issues.apache.org/jira/browse/AMBARI-22602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-22602: - Description: AMBARI-22198 added "stack settings", and AMBARI-22196 introduced "cluster settings" in Ambari. This JIRA adds 2 new parameters to Execution Command : *(1).* clusterSettings and *(2).* stackSettings, and adds their respective set of key-values pairs. - This enables these parameters to be passed in to the ambari-agent's *command\*.json*. CC [~jluniya] was: AMBARI-22198 added "stack settings", and AMBARI-22196 introduced "cluster settings" in Ambari. This JIRA adds 2 new parameters to Execution Command : *(1).* clusterSettings and *(2).* stackSettings, and adds their respective set of key-values pairs. - This enables these parameters to be passed in to the ambari-agent's *command\*.json*. > Add 'clusterSettings' and 'stackSettings' parameters in Execution Command. > --- > > Key: AMBARI-22602 > URL: https://issues.apache.org/jira/browse/AMBARI-22602 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 3.0.0 > > > AMBARI-22198 added "stack settings", and AMBARI-22196 introduced "cluster > settings" in Ambari. > This JIRA adds 2 new parameters to Execution Command : *(1).* clusterSettings > and *(2).* stackSettings, and adds their respective set of key-values pairs. > - This enables these parameters to be passed in to the ambari-agent's > *command\*.json*. > CC [~jluniya] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22602) Add 'clusterSettings' and 'stackSettings' parameters in Execution Command.
[ https://issues.apache.org/jira/browse/AMBARI-22602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-22602: - Description: AMBARI-22198 added "stack settings", and AMBARI-22196 introduced "cluster settings" in Ambari. This JIRA adds 2 new parameters to Execution Command : *(1).* clusterSettings and *(2).* stackSettings, and adds their respective set of key-values pairs. - This enables these parameters to be passed in to the ambari-agent's *command/*.json*. was: AMBARI-22198 added "stack settings", and AMBARI-22196 introduced "cluster settings" in Ambari. This JIRA adds 2 new parameters to Execution Command : *(1).* clusterSettings and *(2).* stackSettings, and adds their respective set of key-values pairs. - This enables these parameters to be passed in to the ambari-agent's *command*.json*. > Add 'clusterSettings' and 'stackSettings' parameters in Execution Command. > --- > > Key: AMBARI-22602 > URL: https://issues.apache.org/jira/browse/AMBARI-22602 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 3.0.0 > > > AMBARI-22198 added "stack settings", and AMBARI-22196 introduced "cluster > settings" in Ambari. > This JIRA adds 2 new parameters to Execution Command : *(1).* clusterSettings > and *(2).* stackSettings, and adds their respective set of key-values pairs. > - This enables these parameters to be passed in to the ambari-agent's > *command/*.json*. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22602) Add 'clusterSettings' and 'stackSettings' parameters in Execution Command.
[ https://issues.apache.org/jira/browse/AMBARI-22602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-22602: - Description: AMBARI-22198 added "stack settings", and AMBARI-22196 introduced "cluster settings" in Ambari. This JIRA adds 2 new parameters to Execution Command : *(1).* clusterSettings and *(2).* stackSettings, and adds their respective set of key-values pairs. - This enables these parameters to be passed in to the ambari-agent's *command*.json*. was: AMBARI-22198 added "stack settings", and AMBARI-22196 introduced "cluster settings" in Ambari. This bug adds 2 new parameters to Execution Command : *(1).* clusterSettings and *(2).* stackSettings, and adds their respective set of key-values pairs. - This enables these parameters to be passed in to the ambari-agent's *command*.json*. > Add 'clusterSettings' and 'stackSettings' parameters in Execution Command. > --- > > Key: AMBARI-22602 > URL: https://issues.apache.org/jira/browse/AMBARI-22602 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 3.0.0 > > > AMBARI-22198 added "stack settings", and AMBARI-22196 introduced "cluster > settings" in Ambari. > This JIRA adds 2 new parameters to Execution Command : *(1).* clusterSettings > and *(2).* stackSettings, and adds their respective set of key-values pairs. > - This enables these parameters to be passed in to the ambari-agent's > *command*.json*. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22602) Add 'clusterSettings' and 'stackSettings' parameters in Execution Command.
[ https://issues.apache.org/jira/browse/AMBARI-22602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-22602: - Description: AMBARI-22198 added "stack settings", and AMBARI-22196 introduced "cluster settings" in Ambari. This bug adds 2 new parameters to Execution Command : *(1).* clusterSettings and *(2).* stackSettings, and adds their respective set of key-values pairs. - This enables these parameters to be passed in to the ambari-agent's *command*.json*. was: AMBARI-22198 added "stack settings", and AMBARI-22196 introduced "cluster settings" in Ambari. This bug adds 2 new parameters to Execution Command : (1). clusterSettings and (2). stackSettings, and adds their respective set of key-values pairs. - This enables these parameters to be passed in to the ambari-agent's *command*.json*. > Add 'clusterSettings' and 'stackSettings' parameters in Execution Command. > --- > > Key: AMBARI-22602 > URL: https://issues.apache.org/jira/browse/AMBARI-22602 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 3.0.0 > > > AMBARI-22198 added "stack settings", and AMBARI-22196 introduced "cluster > settings" in Ambari. > This bug adds 2 new parameters to Execution Command : *(1).* clusterSettings > and *(2).* stackSettings, and adds their respective set of key-values pairs. > - This enables these parameters to be passed in to the ambari-agent's > *command*.json*. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22602) Add 'clusterSettings' and 'stackSettings' parameters in Execution Command.
[ https://issues.apache.org/jira/browse/AMBARI-22602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-22602: - Description: AMBARI-22198 added "stack settings", and AMBARI-22196 introduced "cluster settings" in Ambari. This JIRA adds 2 new parameters to Execution Command : *(1).* clusterSettings and *(2).* stackSettings, and adds their respective set of key-values pairs. - This enables these parameters to be passed in to the ambari-agent's *command\*.json*. was: AMBARI-22198 added "stack settings", and AMBARI-22196 introduced "cluster settings" in Ambari. This JIRA adds 2 new parameters to Execution Command : *(1).* clusterSettings and *(2).* stackSettings, and adds their respective set of key-values pairs. - This enables these parameters to be passed in to the ambari-agent's *command/*.json*. > Add 'clusterSettings' and 'stackSettings' parameters in Execution Command. > --- > > Key: AMBARI-22602 > URL: https://issues.apache.org/jira/browse/AMBARI-22602 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 3.0.0 > > > AMBARI-22198 added "stack settings", and AMBARI-22196 introduced "cluster > settings" in Ambari. > This JIRA adds 2 new parameters to Execution Command : *(1).* clusterSettings > and *(2).* stackSettings, and adds their respective set of key-values pairs. > - This enables these parameters to be passed in to the ambari-agent's > *command\*.json*. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22602) Add 'clusterSettings' and 'stackSettings' parameters in Execution Command.
[ https://issues.apache.org/jira/browse/AMBARI-22602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-22602: - Description: AMBARI-22198 added "stack settings", and AMBARI-22196 introduced "cluster settings" in Ambari. This bug adds 2 new parameters to Execution Command : (1). clusterSettings and (2). stackSettings, and adds their respective set of key-values pairs. - This enables these parameters to be passed in to the ambari-agent's *command*.json*. > Add 'clusterSettings' and 'stackSettings' parameters in Execution Command. > --- > > Key: AMBARI-22602 > URL: https://issues.apache.org/jira/browse/AMBARI-22602 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 3.0.0 > > > AMBARI-22198 added "stack settings", and AMBARI-22196 introduced "cluster > settings" in Ambari. > This bug adds 2 new parameters to Execution Command : (1). clusterSettings > and (2). stackSettings, and adds their respective set of key-values pairs. > - This enables these parameters to be passed in to the ambari-agent's > *command*.json*. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22602) Add 'clusterSettings' and 'stackSettings' parameters in Execution Command.
Swapan Shridhar created AMBARI-22602: Summary: Add 'clusterSettings' and 'stackSettings' parameters in Execution Command. Key: AMBARI-22602 URL: https://issues.apache.org/jira/browse/AMBARI-22602 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Swapan Shridhar Assignee: Swapan Shridhar Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22595) Livy2 keytabs are not getting configured automatically in zeppelin
[
https://issues.apache.org/jira/browse/AMBARI-22595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prabhjyot Singh updated AMBARI-22595:
-
Status: Patch Available (was: Open)
> Livy2 keytabs are not getting configured automatically in zeppelin
> --
>
> Key: AMBARI-22595
> URL: https://issues.apache.org/jira/browse/AMBARI-22595
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.1
> Environment: HDP-2.6.4.0-55
> ambari-server --version 2.6.1.0-91
>Reporter: Supreeth Sharma
>Assignee: Prabhjyot Singh
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22595_trunk_v1.patch, zeppelin.png
>
>
> 'zeppelin.livy.keytab' and 'zeppelin.livy.principal' are not configured for
> zeppelin after installation on secured cluster.
> Because of this zeppelin notebook with livy interpreter is failing with
> un-authenticated 401 error:
> {code:java}
> org.apache.zeppelin.livy.LivyException: Error with 401 StatusCode:
>
>
> Error 401
>
>
> HTTP ERROR: 401
> Problem accessing /version. Reason:
> Authentication required
> Powered by Jetty://
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22595) Livy2 keytabs are not getting configured automatically in zeppelin
[
https://issues.apache.org/jira/browse/AMBARI-22595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prabhjyot Singh updated AMBARI-22595:
-
Attachment: AMBARI-22595_trunk_v1.patch
> Livy2 keytabs are not getting configured automatically in zeppelin
> --
>
> Key: AMBARI-22595
> URL: https://issues.apache.org/jira/browse/AMBARI-22595
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.1
> Environment: HDP-2.6.4.0-55
> ambari-server --version 2.6.1.0-91
>Reporter: Supreeth Sharma
>Assignee: Prabhjyot Singh
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22595_trunk_v1.patch, zeppelin.png
>
>
> 'zeppelin.livy.keytab' and 'zeppelin.livy.principal' are not configured for
> zeppelin after installation on secured cluster.
> Because of this zeppelin notebook with livy interpreter is failing with
> un-authenticated 401 error:
> {code:java}
> org.apache.zeppelin.livy.LivyException: Error with 401 StatusCode:
>
>
> Error 401
>
>
> HTTP ERROR: 401
> Problem accessing /version. Reason:
> Authentication required
> Powered by Jetty://
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-22595) Livy2 keytabs are not getting configured automatically in zeppelin
[
https://issues.apache.org/jira/browse/AMBARI-22595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prabhjyot Singh reassigned AMBARI-22595:
Assignee: Prabhjyot Singh
> Livy2 keytabs are not getting configured automatically in zeppelin
> --
>
> Key: AMBARI-22595
> URL: https://issues.apache.org/jira/browse/AMBARI-22595
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.1
> Environment: HDP-2.6.4.0-55
> ambari-server --version 2.6.1.0-91
>Reporter: Supreeth Sharma
>Assignee: Prabhjyot Singh
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: zeppelin.png
>
>
> 'zeppelin.livy.keytab' and 'zeppelin.livy.principal' are not configured for
> zeppelin after installation on secured cluster.
> Because of this zeppelin notebook with livy interpreter is failing with
> un-authenticated 401 error:
> {code:java}
> org.apache.zeppelin.livy.LivyException: Error with 401 StatusCode:
>
>
> Error 401
>
>
> HTTP ERROR: 401
> Problem accessing /version. Reason:
> Authentication required
> Powered by Jetty://
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
