[jira] [Updated] (AMBARI-17295) Views in Ambari UI don't render when proxied by Knox
[ https://issues.apache.org/jira/browse/AMBARI-17295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-17295: - Status: Patch Available (was: Open) > Views in Ambari UI don't render when proxied by Knox > > > Key: AMBARI-17295 > URL: https://issues.apache.org/jira/browse/AMBARI-17295 > Project: Ambari > Issue Type: Bug > Components: ambari-admin, ambari-views, ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17295.patch > > > When using Knox's AMBARIUI service to proxy the Ambari service's UI, the > various 'views' don't render. The rest of the UI around management of > services works correctly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17297) While deleting a service, confirmation popup took a long time (~30 seconds) to appear
[ https://issues.apache.org/jira/browse/AMBARI-17297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-17297: - Attachment: AMBARI-17297.patch > While deleting a service, confirmation popup took a long time (~30 seconds) > to appear > -- > > Key: AMBARI-17297 > URL: https://issues.apache.org/jira/browse/AMBARI-17297 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17297.patch > > > STR: > For Ranger, Enable all the plugins > Delete Ranger from UI. After clicking the confirm button, the service > deletion confirmation popup took about 28-30 seconds to appear. The test > already waits for 20 seconds. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17243) Change livy principal to service type
[
https://issues.apache.org/jira/browse/AMBARI-17243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Zhang updated AMBARI-17243:
Summary: Change livy principal to service type (was: Use "
livy-${cluster-name}@${realm}" instead of " livy@${realm}" for identity
"livy.server.kerberos.principal")
> Change livy principal to service type
> -
>
> Key: AMBARI-17243
> URL: https://issues.apache.org/jira/browse/AMBARI-17243
> Project: Ambari
> Issue Type: Improvement
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Jeff Zhang
>Assignee: Jeff Zhang
> Fix For: 2.4.0
>
>
> To have unique principal names that is the convention followed by rest of the
> principals.
> Noticed in stack deploy this principal does not have cluster name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17278) Unable to delete permission with type VIEW
[
https://issues.apache.org/jira/browse/AMBARI-17278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15336107#comment-15336107
]
Hudson commented on AMBARI-17278:
-
FAILURE: Integrated in Ambari-trunk-Commit #5103 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5103/])
AMBARI-17278. Unable to delete permission with type VIEW (akovalenko)
(akovalenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b6cb758b54c00986cd58d8e39ca594ab737c6fc1])
* ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/View.js
*
ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/PermissionsSaver.js
*
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/groups/GroupsEditCtrl.js
*
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/users/UsersShowCtrl.js
> Unable to delete permission with type VIEW
> --
>
> Key: AMBARI-17278
> URL: https://issues.apache.org/jira/browse/AMBARI-17278
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin, ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17278.patch
>
>
> When we are removing some user, UI sends request to remove all privileges
> associated with user. But if there is some privilege with type VIEW server
> returns:
> {noformat}
> {
> "status" : 500,
> "message" : "org.apache.ambari.server.controller.spi.SystemException: An
> internal system exception occurred: Caught exception deleting privilege."
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17292) Operations during upgrade are permitted by all roles
[
https://issues.apache.org/jira/browse/AMBARI-17292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15336110#comment-15336110
]
Hadoop QA commented on AMBARI-17292:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12811338/AMBARI-17292.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 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7402//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7402//console
This message is automatically generated.
> Operations during upgrade are permitted by all roles
>
>
> Key: AMBARI-17292
> URL: https://issues.apache.org/jira/browse/AMBARI-17292
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17292.patch
>
>
> ambari-server --hash
> 9a2943ba77371f1c20b4f3da900abb7c2e89d22b
> Build# ambari-server-2.4.0.0-591.x86_64
> **Steps**
> 1. Create user with different roles like Cluster user, Service
> Administrator etc.
> 2. Login as Ambari admin user and start Express Upgrade (register version,
> install packages and start EU)
> 3. Pause the Upgrade at any step that requires manual intervention (like
> stop YARN queue or backup DB or even at Finalize step)
> 4. Logout and login as cluster user
> **Result**:
> The logged in user has complete access to Upgrade Wizard and can resume
> upgrade
> Also do actions like Downgrade, 'Ignore and Proceed', 'Retry'
> The same is true for other roles like service administrator too, both during
> upgrade and downgrade
> **Expected Result:** Only Ambari Admin and Cluster Admin should be permitted
> to perform actions during cluster upgrade
> Screenshots attached for reference while logged in as cluster user role
> (cluser)
> Another observation: While upgrade is in progress, login in a different
> session as cluster user - the cluster user can view the upgrade wizard in
> exact same way as admin
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-17297) While deleting a service, confirmation popup took a long time (~30 seconds) to appear
Aleksandr Kovalenko created AMBARI-17297: Summary: While deleting a service, confirmation popup took a long time (~30 seconds) to appear Key: AMBARI-17297 URL: https://issues.apache.org/jira/browse/AMBARI-17297 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Priority: Critical Fix For: 2.4.0 STR: For Ranger, Enable all the plugins Delete Ranger from UI. After clicking the confirm button, the service deletion confirmation popup took about 28-30 seconds to appear. The test already waits for 20 seconds. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17297) While deleting a service, confirmation popup took a long time (~30 seconds) to appear
[ https://issues.apache.org/jira/browse/AMBARI-17297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-17297: - Attachment: (was: AMBARI-17297.patch) > While deleting a service, confirmation popup took a long time (~30 seconds) > to appear > -- > > Key: AMBARI-17297 > URL: https://issues.apache.org/jira/browse/AMBARI-17297 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17297.patch, AMBARI-17297_branch-2.4.patch > > > STR: > For Ranger, Enable all the plugins > Delete Ranger from UI. After clicking the confirm button, the service > deletion confirmation popup took about 28-30 seconds to appear. The test > already waits for 20 seconds. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17298) Add View Operational Logs role info to RBAC help table
[ https://issues.apache.org/jira/browse/AMBARI-17298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15336168#comment-15336168 ] Andrii Tkach commented on AMBARI-17298: --- +1 for the patch > Add View Operational Logs role info to RBAC help table > -- > > Key: AMBARI-17298 > URL: https://issues.apache.org/jira/browse/AMBARI-17298 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17298_branch-2.4.patch > > > RBAC table (Ambari Admin -> Roles) should contain info about 'View > Operational Logs' permission on Cluster level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17293) Ambari does not refresh yarn queues when HiveServerIntearctive component is restarted
Aleksandr Kovalenko created AMBARI-17293: Summary: Ambari does not refresh yarn queues when HiveServerIntearctive component is restarted Key: AMBARI-17293 URL: https://issues.apache.org/jira/browse/AMBARI-17293 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Priority: Critical Fix For: 2.4.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12885) Dynamic stack extensions - install and upgrade support for custom services
[ https://issues.apache.org/jira/browse/AMBARI-12885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-12885: Status: Patch Available (was: Open) > Dynamic stack extensions - install and upgrade support for custom services > -- > > Key: AMBARI-12885 > URL: https://issues.apache.org/jira/browse/AMBARI-12885 > Project: Ambari > Issue Type: New Feature > Components: ambari-agent, ambari-server, ambari-web >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Attachments: AMBARI-12885 Example.pdf, AMBARI-12885.patch, Dynamic > Stack Extensions - High Level Design v5.pdf > > > The purpose of this proposal is to facilitate adding custom services to an > existing stack. Ideally this would support adding and upgrading custom > services separately from the core services defined in the stack. In > particular we are looking at custom services that need to support several > different stacks (different distributions of Ambari). The release cycle of > the custom services may be different from that of the core stack; that is, a > custom service may be upgraded at a different rate than the core distribution > itself and may be upgraded multiple times within the lifespan of a single > release of the core distribution. > One possible approach to handling this would be dynamically extending a stack > (after install time). It would be best to extend the stack in packages where > a stack extension package can have one or more custom services. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12885) Dynamic stack extensions - install and upgrade support for custom services
[ https://issues.apache.org/jira/browse/AMBARI-12885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-12885: Attachment: AMBARI-12885.patch Fixed patch to apply over trunk > Dynamic stack extensions - install and upgrade support for custom services > -- > > Key: AMBARI-12885 > URL: https://issues.apache.org/jira/browse/AMBARI-12885 > Project: Ambari > Issue Type: New Feature > Components: ambari-agent, ambari-server, ambari-web >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Attachments: AMBARI-12885 Example.pdf, AMBARI-12885.patch, Dynamic > Stack Extensions - High Level Design v5.pdf > > > The purpose of this proposal is to facilitate adding custom services to an > existing stack. Ideally this would support adding and upgrading custom > services separately from the core services defined in the stack. In > particular we are looking at custom services that need to support several > different stacks (different distributions of Ambari). The release cycle of > the custom services may be different from that of the core stack; that is, a > custom service may be upgraded at a different rate than the core distribution > itself and may be upgraded multiple times within the lifespan of a single > release of the core distribution. > One possible approach to handling this would be dynamically extending a stack > (after install time). It would be best to extend the stack in packages where > a stack extension package can have one or more custom services. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17293) Ambari does not refresh yarn queues when HiveServerIntearctive component is restarted
[ https://issues.apache.org/jira/browse/AMBARI-17293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-17293: - Status: Patch Available (was: Open) > Ambari does not refresh yarn queues when HiveServerIntearctive component is > restarted > - > > Key: AMBARI-17293 > URL: https://issues.apache.org/jira/browse/AMBARI-17293 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17293.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17293) Ambari does not refresh yarn queues when HiveServerIntearctive component is restarted
[ https://issues.apache.org/jira/browse/AMBARI-17293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-17293: - Attachment: AMBARI-17293.patch > Ambari does not refresh yarn queues when HiveServerIntearctive component is > restarted > - > > Key: AMBARI-17293 > URL: https://issues.apache.org/jira/browse/AMBARI-17293 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17293.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17295) Views in Ambari UI don't render when proxied by Knox
Aleksandr Kovalenko created AMBARI-17295: Summary: Views in Ambari UI don't render when proxied by Knox Key: AMBARI-17295 URL: https://issues.apache.org/jira/browse/AMBARI-17295 Project: Ambari Issue Type: Bug Components: ambari-admin, ambari-views, ambari-web Affects Versions: 2.4.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Priority: Critical Fix For: 2.4.0 When using Knox's AMBARIUI service to proxy the Ambari service's UI, the various 'views' don't render. The rest of the UI around management of services works correctly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17270) Show better error message when remote cluster attached to view is deleted
[ https://issues.apache.org/jira/browse/AMBARI-17270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15336108#comment-15336108 ] Hudson commented on AMBARI-17270: - FAILURE: Integrated in Ambari-trunk-Commit #5103 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5103/]) AMBARI-17270. Show better error message when remote cluster attached to (dipayan.bhowmick: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c7cbaf22eae31c8dc1300bdcdfc09e6ede8f7ab1]) * ambari-server/src/main/java/org/apache/ambari/server/view/ViewRegistry.java * ambari-server/src/main/java/org/apache/ambari/server/view/IllegalClusterException.java * contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/HelpService.java * ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/ambariViews/ViewsEditCtrl.js * ambari-server/src/main/java/org/apache/ambari/server/view/RemoteAmbariClusterRegistry.java * contrib/views/hive/src/main/java/org/apache/ambari/view/hive/HelpService.java > Show better error message when remote cluster attached to view is deleted > - > > Key: AMBARI-17270 > URL: https://issues.apache.org/jira/browse/AMBARI-17270 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.4.0 > > Attachments: AMBARI-17270_branch-2.4.patch, Screen Shot 2016-06-13 at > 12.31.02 AM.png > > > After deleting remote cluster, view shows null pointer exception for service > checks: -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17275) All created views disappear after upgrade to 2.4.0.0 [views page]
[ https://issues.apache.org/jira/browse/AMBARI-17275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15336106#comment-15336106 ] Hudson commented on AMBARI-17275: - FAILURE: Integrated in Ambari-trunk-Commit #5103 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5103/]) AMBARI-17275. All created views disappear after upgrade to 2.4.0.0 (dipayan.bhowmick: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=978cc64e237c48e7d6bb8eac012c9fe33c93805e]) * ambari-server/src/main/python/ambari_server/serverUpgrade.py * ambari-server/src/main/python/ambari_server/serverConfiguration.py > All created views disappear after upgrade to 2.4.0.0 [views page] > - > > Key: AMBARI-17275 > URL: https://issues.apache.org/jira/browse/AMBARI-17275 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.4.0 > > Attachments: AMBARI-17275_branch-2.4.patch, Screen Shot 2016-06-16 at > 6.30.34 pm.png > > > STR: > 1) Install old version (2.1.2 in our case, but it is reproducible for some > another configurations too) > 2) Create all possible views (through API or by using UI) > 3)Make ambari only upgrade > Actual result: > All created views disappear after upgrade to 2.4.0.0 views page -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17296) Ambari displays a warning about config values not being at optimal values right after a clean install with no customization
Andrew Onischuk created AMBARI-17296: Summary: Ambari displays a warning about config values not being at optimal values right after a clean install with no customization Key: AMBARI-17296 URL: https://issues.apache.org/jira/browse/AMBARI-17296 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.4.0 Attachments: AMBARI-17296.patch With nothing changed manually on a new install, Ambari displayed a message saying that certain configs are not at the recommended values. Given this was a new install with no modifications - the values should have been populated by Ambari itself. I don't know what the final values was because the cluster install failed (likely due to repo issues) Attaching a screenshot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17296) Ambari displays a warning about config values not being at optimal values right after a clean install with no customization
[ https://issues.apache.org/jira/browse/AMBARI-17296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-17296: - Status: Patch Available (was: Open) > Ambari displays a warning about config values not being at optimal values > right after a clean install with no customization > --- > > Key: AMBARI-17296 > URL: https://issues.apache.org/jira/browse/AMBARI-17296 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.0 > > Attachments: AMBARI-17296.patch > > > With nothing changed manually on a new install, Ambari displayed a message > saying that certain configs are not at the recommended values. > Given this was a new install with no modifications - the values should have > been populated by Ambari itself. > I don't know what the final values was because the cluster install failed > (likely due to repo issues) > Attaching a screenshot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17298) Add View Operational Logs role info to RBAC help table
[ https://issues.apache.org/jira/browse/AMBARI-17298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-17298: - Status: Patch Available (was: Open) > Add View Operational Logs role info to RBAC help table > -- > > Key: AMBARI-17298 > URL: https://issues.apache.org/jira/browse/AMBARI-17298 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17298_branch-2.4.patch > > > RBAC table (Ambari Admin -> Roles) should contain info about 'View > Operational Logs' permission on Cluster level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17298) Add View Operational Logs role info to RBAC help table
[ https://issues.apache.org/jira/browse/AMBARI-17298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-17298: - Attachment: AMBARI-17298_branch-2.4.patch > Add View Operational Logs role info to RBAC help table > -- > > Key: AMBARI-17298 > URL: https://issues.apache.org/jira/browse/AMBARI-17298 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17298_branch-2.4.patch > > > RBAC table (Ambari Admin -> Roles) should contain info about 'View > Operational Logs' permission on Cluster level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17297) While deleting a service, confirmation popup took a long time (~30 seconds) to appear
[ https://issues.apache.org/jira/browse/AMBARI-17297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15336171#comment-15336171 ] Andrii Tkach commented on AMBARI-17297: --- +1 for the patch > While deleting a service, confirmation popup took a long time (~30 seconds) > to appear > -- > > Key: AMBARI-17297 > URL: https://issues.apache.org/jira/browse/AMBARI-17297 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17297.patch, AMBARI-17297_branch-2.4.patch > > > STR: > For Ranger, Enable all the plugins > Delete Ranger from UI. After clicking the confirm button, the service > deletion confirmation popup took about 28-30 seconds to appear. The test > already waits for 20 seconds. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17053) Add explicit ambari-server log line indicating cluster creation complete
[
https://issues.apache.org/jira/browse/AMBARI-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335546#comment-15335546
]
Sebastian Toader commented on AMBARI-17053:
---
Committed to trunk:
{code}
commit 438a3cec25798a4e0565fe7914a440c306362ec6
Author: Daniel Gergely
Date: Fri Jun 17 06:58:33 2016 +0200
AMBARI-17053. Add explicit ambari-server log line indicating cluster
creation complete. (Daniel Gergely via stoader)
{code}
Committed to branch-2.4:
{code}
commit 2f6d7fbc9637e9714ed30ae63be3f0e5b92583b7
Author: Daniel Gergely
Date: Fri Jun 17 06:58:33 2016 +0200
AMBARI-17053. Add explicit ambari-server log line indicating cluster
creation complete. (Daniel Gergely via stoader)
{code}
> Add explicit ambari-server log line indicating cluster creation complete
>
>
> Key: AMBARI-17053
> URL: https://issues.apache.org/jira/browse/AMBARI-17053
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Reporter: Daniel Gergely
>Assignee: Daniel Gergely
> Fix For: 2.4.0, 2.2-next
>
> Attachments: AMBARI-17053_2.2-next.patch,
> AMBARI-17053_branch-2.4_and_trunk.patch
>
>
> Add a log message to see when the cluster is ready to use (cluster creation
> finishes)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17053) Add explicit ambari-server log line indicating cluster creation complete
[ https://issues.apache.org/jira/browse/AMBARI-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-17053: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Add explicit ambari-server log line indicating cluster creation complete > > > Key: AMBARI-17053 > URL: https://issues.apache.org/jira/browse/AMBARI-17053 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: Daniel Gergely >Assignee: Daniel Gergely > Fix For: 2.4.0, 2.2-next > > Attachments: AMBARI-17053_2.2-next.patch, > AMBARI-17053_branch-2.4_and_trunk.patch > > > Add a log message to see when the cluster is ready to use (cluster creation > finishes) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17291) zookeeper.quorum in storm-metrics2.properties is broken
Masahiro Tanaka created AMBARI-17291:
Summary: zookeeper.quorum in storm-metrics2.properties is broken
Key: AMBARI-17291
URL: https://issues.apache.org/jira/browse/AMBARI-17291
Project: Ambari
Issue Type: Bug
Affects Versions: trunk
Environment: CentOS7.2
Reporter: Masahiro Tanaka
Assignee: Masahiro Tanaka
When installed Storm, {{zookeeper.quorum}} in
/etc/storm/conf/storm-metrics2.properties is looks like this.
{code}
zookeeper.quorum=[:2181,':2181,c:2181,7:2181,2:2181,0:2181,1:2181,.:2181,a:2181,m:2181,b:2181,a:2181,r:2181,i:2181,.:2181,a:2181,p:2181,a:2181,c:2181,h:2181,e:2181,.:2181,o:2181,r:2181,g:2181,':2181,,:2181,':2181,c:2181,7:2181,2:2181,0:2181,2:2181,.:2181,a:2181,m:2181,b:2181,a:2181,r:2181,i:2181,.:2181,a:2181,p:2181,a:2181,c:2181,h:2181,e:2181,.:2181,o:2181,r:2181,g:2181,':2181,,:2181,':2181,c:2181,7:2181,2:2181,0:2181,3:2181,.:2181,a:2181,m:2181,b:2181,a:2181,r:2181,i:2181,.:2181,a:2181,p:2181,a:2181,c:2181,h:2181,e:2181,.:2181,o:2181,r:2181,g:2181,':2181,]:2181
{code}
storm.zookeeper.servers is
{{['c7201.ambari.apache.org','c7202.ambari.apache.org','c7203.ambari.apache.org']}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17291) zookeeper.quorum in storm-metrics2.properties is broken
[
https://issues.apache.org/jira/browse/AMBARI-17291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-17291:
-
Component/s: ambari-server
ambari-metrics
> zookeeper.quorum in storm-metrics2.properties is broken
> ---
>
> Key: AMBARI-17291
> URL: https://issues.apache.org/jira/browse/AMBARI-17291
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics, ambari-server
>Affects Versions: trunk
> Environment: CentOS7.2
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>
> When installed Storm, {{zookeeper.quorum}} in
> /etc/storm/conf/storm-metrics2.properties is looks like this.
> {code}
> zookeeper.quorum=[:2181,':2181,c:2181,7:2181,2:2181,0:2181,1:2181,.:2181,a:2181,m:2181,b:2181,a:2181,r:2181,i:2181,.:2181,a:2181,p:2181,a:2181,c:2181,h:2181,e:2181,.:2181,o:2181,r:2181,g:2181,':2181,,:2181,':2181,c:2181,7:2181,2:2181,0:2181,2:2181,.:2181,a:2181,m:2181,b:2181,a:2181,r:2181,i:2181,.:2181,a:2181,p:2181,a:2181,c:2181,h:2181,e:2181,.:2181,o:2181,r:2181,g:2181,':2181,,:2181,':2181,c:2181,7:2181,2:2181,0:2181,3:2181,.:2181,a:2181,m:2181,b:2181,a:2181,r:2181,i:2181,.:2181,a:2181,p:2181,a:2181,c:2181,h:2181,e:2181,.:2181,o:2181,r:2181,g:2181,':2181,]:2181
> {code}
> storm.zookeeper.servers is
> {{['c7201.ambari.apache.org','c7202.ambari.apache.org','c7203.ambari.apache.org']}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16954) SERVICE_CHECK Upgrade pre-check does not throw error when its expected to
[
https://issues.apache.org/jira/browse/AMBARI-16954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-16954:
Resolution: Incomplete
Status: Resolved (was: Patch Available)
> SERVICE_CHECK Upgrade pre-check does not throw error when its expected to
> -
>
> Key: AMBARI-16954
> URL: https://issues.apache.org/jira/browse/AMBARI-16954
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-16954.patch
>
>
> *Steps*
> # Deploy HDP-2.4.0.0 cluster with Ambari 2.2.2
> # Upgrade Ambari to 2.4.0.0
> # Register HDP-2.5.0.0 version and install the bits
> # Modify configs for some of the service like HDFS, ZK, YARN
> # Start EU
> *Result*:
> EU pre-check does *not* report below error for the three services whose
> config was modified in step 4
> "The following service configurations have been updated and their Service
> Checks should be run again:"
> Upon further investigation found that the pre-check does not work if a
> service check has never been run for a service at all AND reports success in
> such cases
> In other words, the comparison between last config modification time and last
> service check time succeeds if service check never ran at all and the output
> of below query returns empty:
> {code}
> SELECT start_time FROM host_role_command where role = 'HDFS_SERVICE_CHECK'
> AND status = 'COMPLETED' ORDER BY start_time DESC;
> {code}
> In this case when I manually ran a service check for HDFS and retried EU, the
> pre-check caught the mismatch and reported error
> *Note*: I believe we do run service check as part of cluster install, but
> looks like it does not get updated in the DB tables for all services.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17276) Zeppelin: Intermittent failure while downloading example notebooks
[
https://issues.apache.org/jira/browse/AMBARI-17276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
DIPAYAN BHOWMICK updated AMBARI-17276:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to branch-2.4, trunk.
> Zeppelin: Intermittent failure while downloading example notebooks
> --
>
> Key: AMBARI-17276
> URL: https://issues.apache.org/jira/browse/AMBARI-17276
> Project: Ambari
> Issue Type: Bug
>Affects Versions: ambari-2.4.0
>Reporter: Renjith Kamath
>Assignee: Renjith Kamath
> Fix For: ambari-2.4.0
>
> Attachments: AMBARI-17276_trunk+branch-2.4_v1.patch
>
>
> {code:title=stderr}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py",
> line 203, in
> Master().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 257, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py",
> line 58, in install
> user=params.zeppelin_user)
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, 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 273, 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 70, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 92, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 293, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of
> '/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/setup_snapshot.sh
> /usr/hdp/current/zeppelin-server c6401.ambari.apache.org 9083 10001
> c6401.ambari.apache.org 9995 True
> /var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package
> /usr/jdk64/jdk1.8.0_66 >> /var/log/zeppelin/zeppelin-setup.log' returned 1.
> --2016-06-16 11:32:11--
> https://github.com/hortonworks-gallery/zeppelin-notebooks/archive/master.zip
> Resolving github.com... 192.30.252.129
> Connecting to github.com|192.30.252.129|:443... connected.
> HTTP request sent, awaiting response... 302 Found
> Location:
> https://codeload.github.com/hortonworks-gallery/zeppelin-notebooks/zip/master
> [following]
> --2016-06-16 11:32:13--
> https://codeload.github.com/hortonworks-gallery/zeppelin-notebooks/zip/master
> Resolving codeload.github.com... 192.30.253.121
> Connecting to codeload.github.com|192.30.253.121|:443... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: unspecified [application/zip]
> Saving to: “notebooks.zip”
> 0K .. .. .. .. .. 83.0K
> 50K .. .. .. .. .. 79.2K
>100K .. .. .. .. .. 164K
>150K .. .. .. .. .. 87.8K
>200K .. .. .. .. .. 176K
>250K .. .. .. .. .. 175K
>300K .. .. .. .. .. 167K
>350K .. .. .. .. .. 177K
>400K .. .. .. .. .. 174K
>450K .. .. .. .. .. 174K
>500K .. .. .. .. .. 182K
>550K .. .. .. .. .. 174K
>600K .. .. .. .. .. 176K
>650K .. .. .. .. .. 164K
>700K .. .. .. .. .. 174K
>750K .. .. .. .. .. 179K
>800K .. .. .. . 164K=5.8s
> 2016-06-16 11:32:28 (145 KB/s) - “notebooks.zip” saved [855111]
> warning [notebooks.zip]: 7 extra bytes at beginning or within zipfile
>
[jira] [Commented] (AMBARI-17053) Add explicit ambari-server log line indicating cluster creation complete
[ https://issues.apache.org/jira/browse/AMBARI-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335810#comment-15335810 ] Hudson commented on AMBARI-17053: - FAILURE: Integrated in Ambari-trunk-Commit #5101 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5101/]) AMBARI-17053. Add explicit ambari-server log line indicating cluster (stoader: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=438a3cec25798a4e0565fe7914a440c306362ec6]) * ambari-server/src/main/java/org/apache/ambari/server/events/AmbariEvent.java * ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionDBAccessorImpl.java * ambari-server/src/test/java/org/apache/ambari/server/topology/TopologyManagerTest.java * ambari-server/src/main/java/org/apache/ambari/server/topology/TopologyManager.java * ambari-server/src/main/java/org/apache/ambari/server/topology/PersistedState.java * ambari-server/src/main/java/org/apache/ambari/server/topology/PersistedStateImpl.java * ambari-server/src/main/java/org/apache/ambari/server/events/RequestFinishedEvent.java > Add explicit ambari-server log line indicating cluster creation complete > > > Key: AMBARI-17053 > URL: https://issues.apache.org/jira/browse/AMBARI-17053 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: Daniel Gergely >Assignee: Daniel Gergely > Fix For: 2.4.0, 2.2-next > > Attachments: AMBARI-17053_2.2-next.patch, > AMBARI-17053_branch-2.4_and_trunk.patch > > > Add a log message to see when the cluster is ready to use (cluster creation > finishes) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17292) Operations during upgrade are permitted by all roles
[ https://issues.apache.org/jira/browse/AMBARI-17292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-17292: - Status: Patch Available (was: Open) > Operations during upgrade are permitted by all roles > > > Key: AMBARI-17292 > URL: https://issues.apache.org/jira/browse/AMBARI-17292 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.0 > > Attachments: AMBARI-17292.patch > > > ambari-server --hash > 9a2943ba77371f1c20b4f3da900abb7c2e89d22b > Build# ambari-server-2.4.0.0-591.x86_64 > **Steps** > 1. Create user with different roles like Cluster user, Service > Administrator etc. > 2. Login as Ambari admin user and start Express Upgrade (register version, > install packages and start EU) > 3. Pause the Upgrade at any step that requires manual intervention (like > stop YARN queue or backup DB or even at Finalize step) > 4. Logout and login as cluster user > **Result**: > The logged in user has complete access to Upgrade Wizard and can resume > upgrade > Also do actions like Downgrade, 'Ignore and Proceed', 'Retry' > The same is true for other roles like service administrator too, both during > upgrade and downgrade > **Expected Result:** Only Ambari Admin and Cluster Admin should be permitted > to perform actions during cluster upgrade > Screenshots attached for reference while logged in as cluster user role > (cluser) > Another observation: While upgrade is in progress, login in a different > session as cluster user - the cluster user can view the upgrade wizard in > exact same way as admin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17292) Operations during upgrade are permitted by all roles
[ https://issues.apache.org/jira/browse/AMBARI-17292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-17292: - Attachment: AMBARI-17292.patch > Operations during upgrade are permitted by all roles > > > Key: AMBARI-17292 > URL: https://issues.apache.org/jira/browse/AMBARI-17292 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.0 > > Attachments: AMBARI-17292.patch > > > ambari-server --hash > 9a2943ba77371f1c20b4f3da900abb7c2e89d22b > Build# ambari-server-2.4.0.0-591.x86_64 > **Steps** > 1. Create user with different roles like Cluster user, Service > Administrator etc. > 2. Login as Ambari admin user and start Express Upgrade (register version, > install packages and start EU) > 3. Pause the Upgrade at any step that requires manual intervention (like > stop YARN queue or backup DB or even at Finalize step) > 4. Logout and login as cluster user > **Result**: > The logged in user has complete access to Upgrade Wizard and can resume > upgrade > Also do actions like Downgrade, 'Ignore and Proceed', 'Retry' > The same is true for other roles like service administrator too, both during > upgrade and downgrade > **Expected Result:** Only Ambari Admin and Cluster Admin should be permitted > to perform actions during cluster upgrade > Screenshots attached for reference while logged in as cluster user role > (cluser) > Another observation: While upgrade is in progress, login in a different > session as cluster user - the cluster user can view the upgrade wizard in > exact same way as admin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17292) Operations during upgrade are permitted by all roles
Andrew Onischuk created AMBARI-17292: Summary: Operations during upgrade are permitted by all roles Key: AMBARI-17292 URL: https://issues.apache.org/jira/browse/AMBARI-17292 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.4.0 Attachments: AMBARI-17292.patch ambari-server --hash 9a2943ba77371f1c20b4f3da900abb7c2e89d22b Build# ambari-server-2.4.0.0-591.x86_64 **Steps** 1. Create user with different roles like Cluster user, Service Administrator etc. 2. Login as Ambari admin user and start Express Upgrade (register version, install packages and start EU) 3. Pause the Upgrade at any step that requires manual intervention (like stop YARN queue or backup DB or even at Finalize step) 4. Logout and login as cluster user **Result**: The logged in user has complete access to Upgrade Wizard and can resume upgrade Also do actions like Downgrade, 'Ignore and Proceed', 'Retry' The same is true for other roles like service administrator too, both during upgrade and downgrade **Expected Result:** Only Ambari Admin and Cluster Admin should be permitted to perform actions during cluster upgrade Screenshots attached for reference while logged in as cluster user role (cluser) Another observation: While upgrade is in progress, login in a different session as cluster user - the cluster user can view the upgrade wizard in exact same way as admin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17270) Show better error message when remote cluster attached to view is deleted
[ https://issues.apache.org/jira/browse/AMBARI-17270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DIPAYAN BHOWMICK updated AMBARI-17270: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.4, trunk. > Show better error message when remote cluster attached to view is deleted > - > > Key: AMBARI-17270 > URL: https://issues.apache.org/jira/browse/AMBARI-17270 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.4.0 > > Attachments: AMBARI-17270_branch-2.4.patch, Screen Shot 2016-06-13 at > 12.31.02 AM.png > > > After deleting remote cluster, view shows null pointer exception for service > checks: -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17275) All created views disappear after upgrade to 2.4.0.0 [views page]
[ https://issues.apache.org/jira/browse/AMBARI-17275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DIPAYAN BHOWMICK updated AMBARI-17275: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.4, trunk. > All created views disappear after upgrade to 2.4.0.0 [views page] > - > > Key: AMBARI-17275 > URL: https://issues.apache.org/jira/browse/AMBARI-17275 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.4.0 > > Attachments: AMBARI-17275_branch-2.4.patch, Screen Shot 2016-06-16 at > 6.30.34 pm.png > > > STR: > 1) Install old version (2.1.2 in our case, but it is reproducible for some > another configurations too) > 2) Create all possible views (through API or by using UI) > 3)Make ambari only upgrade > Actual result: > All created views disappear after upgrade to 2.4.0.0 views page -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17302) Ambari-server upgrade results in "DB configs consistency check failed. " when upgrading Azure IaaS offering
Vitaly Brodetskyi created AMBARI-17302: -- Summary: Ambari-server upgrade results in "DB configs consistency check failed. " when upgrading Azure IaaS offering Key: AMBARI-17302 URL: https://issues.apache.org/jira/browse/AMBARI-17302 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Vitaly Brodetskyi Assignee: Vitaly Brodetskyi Priority: Blocker Fix For: 2.4.0 2016-06-16 01:19:10,963 INFO - *** Check database started *** 2016-06-16 01:19:14,660 INFO - Checking for configs not mapped to any cluster 2016-06-16 01:19:14,681 INFO - Checking for configs selected more than once 2016-06-16 01:19:14,683 INFO - Checking for hosts without state 2016-06-16 01:19:14,684 INFO - Checking host component states count equals host component desired states count 2016-06-16 01:19:14,685 INFO - Checking services and their configs 2016-06-16 01:19:16,045 ERROR - Required config(s): slider-client is(are) not available for service SLIDER with service config version 2 in cluster hortonhdp 2016-06-16 01:19:16,161 INFO - *** Check database completed *** -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17302) Ambari-server upgrade results in "DB configs consistency check failed. " when upgrading Azure IaaS offering
[ https://issues.apache.org/jira/browse/AMBARI-17302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-17302: --- Description: Cluster deployed via BP based on ambari 2.2.1 have no slider-client config. After upgrade to ambari 2.4.0 this issue appears 2016-06-16 01:19:10,963 INFO - *** Check database started *** 2016-06-16 01:19:14,660 INFO - Checking for configs not mapped to any cluster 2016-06-16 01:19:14,681 INFO - Checking for configs selected more than once 2016-06-16 01:19:14,683 INFO - Checking for hosts without state 2016-06-16 01:19:14,684 INFO - Checking host component states count equals host component desired states count 2016-06-16 01:19:14,685 INFO - Checking services and their configs 2016-06-16 01:19:16,045 ERROR - Required config(s): slider-client is(are) not available for service SLIDER with service config version 2 in cluster hortonhdp 2016-06-16 01:19:16,161 INFO - *** Check database completed *** was: 2016-06-16 01:19:10,963 INFO - *** Check database started *** 2016-06-16 01:19:14,660 INFO - Checking for configs not mapped to any cluster 2016-06-16 01:19:14,681 INFO - Checking for configs selected more than once 2016-06-16 01:19:14,683 INFO - Checking for hosts without state 2016-06-16 01:19:14,684 INFO - Checking host component states count equals host component desired states count 2016-06-16 01:19:14,685 INFO - Checking services and their configs 2016-06-16 01:19:16,045 ERROR - Required config(s): slider-client is(are) not available for service SLIDER with service config version 2 in cluster hortonhdp 2016-06-16 01:19:16,161 INFO - *** Check database completed *** > Ambari-server upgrade results in "DB configs consistency check failed. " when > upgrading Azure IaaS offering > --- > > Key: AMBARI-17302 > URL: https://issues.apache.org/jira/browse/AMBARI-17302 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Blocker > Fix For: 2.4.0 > > > Cluster deployed via BP based on ambari 2.2.1 have no slider-client config. > After upgrade to ambari 2.4.0 this issue appears > 2016-06-16 01:19:10,963 INFO - *** Check > database started *** > 2016-06-16 01:19:14,660 INFO - Checking for configs not mapped to any cluster > 2016-06-16 01:19:14,681 INFO - Checking for configs selected more than once > 2016-06-16 01:19:14,683 INFO - Checking for hosts without state > 2016-06-16 01:19:14,684 INFO - Checking host component states count equals > host component desired states count > 2016-06-16 01:19:14,685 INFO - Checking services and their configs > 2016-06-16 01:19:16,045 ERROR - Required config(s): slider-client is(are) not > available for service SLIDER with service config version 2 in cluster > hortonhdp > 2016-06-16 01:19:16,161 INFO - *** Check > database completed *** -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17254) Log Search default log levels can not be altered
[ https://issues.apache.org/jira/browse/AMBARI-17254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15336692#comment-15336692 ] Hudson commented on AMBARI-17254: - FAILURE: Integrated in Ambari-trunk-Commit #5105 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5105/]) AMBARI-17254. Log Search default log levels can not be altered (Miklos (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=797a759a52f3da9838b1ee1bba5bf174c5aa0e63]) * ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-properties.xml > Log Search default log levels can not be altered > > > Key: AMBARI-17254 > URL: https://issues.apache.org/jira/browse/AMBARI-17254 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.4.0 > > > The default log levels (log levels to include) can not be altered, forever > the ones set during the installation (more precisely: the one which is the > value of the property during the first run of the portal) would be in effect. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17300) RU: YARN service check failed during RU
[ https://issues.apache.org/jira/browse/AMBARI-17300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15336691#comment-15336691 ] Hudson commented on AMBARI-17300: - FAILURE: Integrated in Ambari-trunk-Commit #5105 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5105/]) AMBARI-17300. RU: YARN service check failed during RU (dlysnichenko) (dlysnichenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6708cf0b16502c87b691b9b2716bc524a9b20baf]) * ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/metainfo.xml > RU: YARN service check failed during RU > --- > > Key: AMBARI-17300 > URL: https://issues.apache.org/jira/browse/AMBARI-17300 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Fix For: 2.4.0 > > Attachments: AMBARI-17300.patch > > > STR: > # Deploy HDP 2.4 in Ambari2.2.2.0 > # Enable NN HA > # Enable security > # Perform upgrade to ambari2.4.0.0 > # Register and install HDP 2.5.0.0 > # Perform RU > Result: Storm service check failed during RU > The property > "yarn.nodemanager.container-executor.class" changed from > "org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor" to > "org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor" > during "Update configs after ATLAS has been removed" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17299) Ambari Metrics service check failed exceed timeout
[
https://issues.apache.org/jira/browse/AMBARI-17299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15336690#comment-15336690
]
Hudson commented on AMBARI-17299:
-
FAILURE: Integrated in Ambari-trunk-Commit #5105 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5105/])
AMBARI-17299 Ambari Metrics service check failed exceed timeout (dsen) (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=da8195fb839a3ba4090301551c15067cb50a9635])
* ambari-metrics/ambari-metrics-timelineservice/pom.xml
> Ambari Metrics service check failed exceed timeout
> --
>
> Key: AMBARI-17299
> URL: https://issues.apache.org/jira/browse/AMBARI-17299
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17299.patch
>
>
> Service check failed stderr:
> {noformat}
> Python script has been killed due to timeout after waiting 600 secs
> {noformat}
> No phoenix-server.jar in /usr/lib/ams-hbase/lib/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (AMBARI-16740) Atlas Integration : Rename atlas lineage configurations
[ https://issues.apache.org/jira/browse/AMBARI-16740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez reassigned AMBARI-16740: Assignee: Alejandro Fernandez (was: Tom Beerbower) > Atlas Integration : Rename atlas lineage configurations > --- > > Key: AMBARI-16740 > URL: https://issues.apache.org/jira/browse/AMBARI-16740 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Tom Beerbower >Assignee: Alejandro Fernandez > Fix For: 2.4.0 > > > As part of ATLAS-713, the following changes are required in atlas > configuration that is set by Ambari: > # atlas.lineage.hive.table.schema.query.Table renamed to > atlas.lineage.schema.query.Table > # atlas.lineage.hive.table.schema.query.hive_table renamed to > atlas.lineage.schema.query.hive_table -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16740) Atlas Integration : Rename atlas lineage configurations
[ https://issues.apache.org/jira/browse/AMBARI-16740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-16740: - Affects Version/s: 2.4.0 > Atlas Integration : Rename atlas lineage configurations > --- > > Key: AMBARI-16740 > URL: https://issues.apache.org/jira/browse/AMBARI-16740 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Tom Beerbower >Assignee: Alejandro Fernandez > Fix For: 2.4.0 > > > As part of ATLAS-713, the following changes are required in atlas > configuration that is set by Ambari: > # atlas.lineage.hive.table.schema.query.Table renamed to > atlas.lineage.schema.query.Table > # atlas.lineage.hive.table.schema.query.hive_table renamed to > atlas.lineage.schema.query.hive_table -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-14853) Atlas Integration: Support deploying latest Atlas(which depends on kafka) using Ambari
[
https://issues.apache.org/jira/browse/AMBARI-14853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-14853:
-
Fix Version/s: 2.4.0
> Atlas Integration: Support deploying latest Atlas(which depends on kafka)
> using Ambari
> --
>
> Key: AMBARI-14853
> URL: https://issues.apache.org/jira/browse/AMBARI-14853
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Fix For: 2.4.0
>
> Attachments: AMBARI-14853.patch
>
>
> Three additional steps need to be done to to install Atlas 0.6 via Ambari.
> 1. Add new Atlas Kafka related properties to the Atlas configuration
> ‘application.properties’
> {code}
> atlas.notification.embedded" : false,
> atlas.kafka.data = /tmp
> atlas.kafka.bootstrap.servers = c6401.ambari.apache.org:6667
> atlas.kafka.zookeeper.connect = c6401.ambari.apache.org:2181
> atlas.kafka.hook.group.id = atlas
> atlas.kafka.entities.group.id = entities
> {code}
> * Note:
> For “atlas.kafka.bootstrap.servers” and “atlas.kafka.zookeeper.connect”,
> modify host names based on your cluster topology.
> The directory specified in “atlas.kaka.data” should exist.
> 2. Add an export of HADOOP_CLASSPATH which includes the required atlas
> directories to hive-env.xml in the 2.3 HDP stack
> {code}
> export
> HADOOP_CLASSPATH=/etc/atlas/conf:/usr/hdp/current/atlas-server/hook/hive:${HADOOP_CLASSPATH}
> {code}
> *Note:
> It is important that the atlas directories are prepended to the existing
> classpath.
> 3. Restart the Atlas and Hive services after the cluster is fully provisioned
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-14888) Atlas Integration : Look into Atlas-Hive properties for RU
[
https://issues.apache.org/jira/browse/AMBARI-14888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez resolved AMBARI-14888.
--
Resolution: Duplicate
Fixed already in AMBARI-14853
> Atlas Integration : Look into Atlas-Hive properties for RU
> --
>
> Key: AMBARI-14888
> URL: https://issues.apache.org/jira/browse/AMBARI-14888
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Fix For: 2.4.0
>
>
> An Atlas install adds an export of HADOOP_CLASSPATH which includes the
> required atlas directories to hive-env.xml in the 2.3 HDP stack
> {code}
> export
> HADOOP_CLASSPATH=/etc/atlas/conf:/usr/hdp/current/atlas-server/hook/hive:${HADOOP_CLASSPATH}
> {code}
> It needs to be set during RU/EU from HDP 2.2 to 2.3 by modifying the config
> packs.
> E.g.,
> ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml
> {code}
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17302) Ambari-server upgrade results in "DB configs consistency check failed. "
[ https://issues.apache.org/jira/browse/AMBARI-17302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-17302: --- Summary: Ambari-server upgrade results in "DB configs consistency check failed. " (was: Ambari-server upgrade results in "DB configs consistency check failed. " when upgrading Azure IaaS offering) > Ambari-server upgrade results in "DB configs consistency check failed. " > > > Key: AMBARI-17302 > URL: https://issues.apache.org/jira/browse/AMBARI-17302 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17302.patch > > > Cluster deployed via BP based on ambari 2.2.1 have no slider-client config. > After upgrade to ambari 2.4.0 this issue appears > 2016-06-16 01:19:10,963 INFO - *** Check > database started *** > 2016-06-16 01:19:14,660 INFO - Checking for configs not mapped to any cluster > 2016-06-16 01:19:14,681 INFO - Checking for configs selected more than once > 2016-06-16 01:19:14,683 INFO - Checking for hosts without state > 2016-06-16 01:19:14,684 INFO - Checking host component states count equals > host component desired states count > 2016-06-16 01:19:14,685 INFO - Checking services and their configs > 2016-06-16 01:19:16,045 ERROR - Required config(s): slider-client is(are) not > available for service SLIDER with service config version 2 in cluster > hortonhdp > 2016-06-16 01:19:16,161 INFO - *** Check > database completed *** -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12885) Dynamic stack extensions - install and upgrade support for custom services
[
https://issues.apache.org/jira/browse/AMBARI-12885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15336729#comment-15336729
]
Hadoop QA commented on AMBARI-12885:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12811353/AMBARI-12885.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 36 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.controller.internal.ConfigGroupResourceProviderTest
org.apache.ambari.server.upgrade.UpgradeCatalog240Test
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7412//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7412//console
This message is automatically generated.
> Dynamic stack extensions - install and upgrade support for custom services
> --
>
> Key: AMBARI-12885
> URL: https://issues.apache.org/jira/browse/AMBARI-12885
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-agent, ambari-server, ambari-web
>Reporter: Tim Thorpe
>Assignee: Tim Thorpe
> Attachments: AMBARI-12885 Example.pdf, AMBARI-12885.patch, Dynamic
> Stack Extensions - High Level Design v5.pdf
>
>
> The purpose of this proposal is to facilitate adding custom services to an
> existing stack. Ideally this would support adding and upgrading custom
> services separately from the core services defined in the stack. In
> particular we are looking at custom services that need to support several
> different stacks (different distributions of Ambari). The release cycle of
> the custom services may be different from that of the core stack; that is, a
> custom service may be upgraded at a different rate than the core distribution
> itself and may be upgraded multiple times within the lifespan of a single
> release of the core distribution.
> One possible approach to handling this would be dynamically extending a stack
> (after install time). It would be best to extend the stack in packages where
> a stack extension package can have one or more custom services.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17298) Add View Operational Logs role info to RBAC help table
[
https://issues.apache.org/jira/browse/AMBARI-17298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15336482#comment-15336482
]
Hadoop QA commented on AMBARI-17298:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12811375/AMBARI-17298_branch-2.4.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/7408//console
This message is automatically generated.
> Add View Operational Logs role info to RBAC help table
> --
>
> Key: AMBARI-17298
> URL: https://issues.apache.org/jira/browse/AMBARI-17298
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17298_branch-2.4.patch
>
>
> RBAC table (Ambari Admin -> Roles) should contain info about 'View
> Operational Logs' permission on Cluster level.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17298) Add View Operational Logs role info to RBAC help table
[ https://issues.apache.org/jira/browse/AMBARI-17298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15336498#comment-15336498 ] Aleksandr Kovalenko commented on AMBARI-17298: -- committed to trunk 2.4 > Add View Operational Logs role info to RBAC help table > -- > > Key: AMBARI-17298 > URL: https://issues.apache.org/jira/browse/AMBARI-17298 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17298_branch-2.4.patch > > > RBAC table (Ambari Admin -> Roles) should contain info about 'View > Operational Logs' permission on Cluster level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17297) While deleting a service, confirmation popup took a long time (~30 seconds) to appear
[ https://issues.apache.org/jira/browse/AMBARI-17297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-17297: - Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and branch-2.4 > While deleting a service, confirmation popup took a long time (~30 seconds) > to appear > -- > > Key: AMBARI-17297 > URL: https://issues.apache.org/jira/browse/AMBARI-17297 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17297.patch, AMBARI-17297_branch-2.4.patch > > > STR: > For Ranger, Enable all the plugins > Delete Ranger from UI. After clicking the confirm button, the service > deletion confirmation popup took about 28-30 seconds to appear. The test > already waits for 20 seconds. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-17298) Add View Operational Logs role info to RBAC help table
[ https://issues.apache.org/jira/browse/AMBARI-17298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15336498#comment-15336498 ] Aleksandr Kovalenko edited comment on AMBARI-17298 at 6/17/16 5:19 PM: --- committed to branch-2.4 was (Author: akovalenko): committed to trunk 2.4 > Add View Operational Logs role info to RBAC help table > -- > > Key: AMBARI-17298 > URL: https://issues.apache.org/jira/browse/AMBARI-17298 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17298_branch-2.4.patch > > > RBAC table (Ambari Admin -> Roles) should contain info about 'View > Operational Logs' permission on Cluster level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16899) Add service check for Log Search service
[ https://issues.apache.org/jira/browse/AMBARI-16899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-16899: -- Attachment: AMBARI-16899.patch > Add service check for Log Search service > > > Key: AMBARI-16899 > URL: https://issues.apache.org/jira/browse/AMBARI-16899 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.4.0 > > Attachments: AMBARI-16899.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-14888) Atlas Integration : Look into Atlas-Hive properties for RU
[
https://issues.apache.org/jira/browse/AMBARI-14888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-14888:
-
Affects Version/s: 2.4.0
> Atlas Integration : Look into Atlas-Hive properties for RU
> --
>
> Key: AMBARI-14888
> URL: https://issues.apache.org/jira/browse/AMBARI-14888
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
>
> An Atlas install adds an export of HADOOP_CLASSPATH which includes the
> required atlas directories to hive-env.xml in the 2.3 HDP stack
> {code}
> export
> HADOOP_CLASSPATH=/etc/atlas/conf:/usr/hdp/current/atlas-server/hook/hive:${HADOOP_CLASSPATH}
> {code}
> It needs to be set during RU/EU from HDP 2.2 to 2.3 by modifying the config
> packs.
> E.g.,
> ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml
> {code}
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-14888) Atlas Integration : Look into Atlas-Hive properties for RU
[
https://issues.apache.org/jira/browse/AMBARI-14888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-14888:
-
Fix Version/s: 2.4.0
> Atlas Integration : Look into Atlas-Hive properties for RU
> --
>
> Key: AMBARI-14888
> URL: https://issues.apache.org/jira/browse/AMBARI-14888
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Fix For: 2.4.0
>
>
> An Atlas install adds an export of HADOOP_CLASSPATH which includes the
> required atlas directories to hive-env.xml in the 2.3 HDP stack
> {code}
> export
> HADOOP_CLASSPATH=/etc/atlas/conf:/usr/hdp/current/atlas-server/hook/hive:${HADOOP_CLASSPATH}
> {code}
> It needs to be set during RU/EU from HDP 2.2 to 2.3 by modifying the config
> packs.
> E.g.,
> ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml
> {code}
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17302) Ambari-server upgrade results in "DB configs consistency check failed. " when upgrading Azure IaaS offering
[ https://issues.apache.org/jira/browse/AMBARI-17302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-17302: --- Status: Patch Available (was: Open) > Ambari-server upgrade results in "DB configs consistency check failed. " when > upgrading Azure IaaS offering > --- > > Key: AMBARI-17302 > URL: https://issues.apache.org/jira/browse/AMBARI-17302 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17302.patch > > > Cluster deployed via BP based on ambari 2.2.1 have no slider-client config. > After upgrade to ambari 2.4.0 this issue appears > 2016-06-16 01:19:10,963 INFO - *** Check > database started *** > 2016-06-16 01:19:14,660 INFO - Checking for configs not mapped to any cluster > 2016-06-16 01:19:14,681 INFO - Checking for configs selected more than once > 2016-06-16 01:19:14,683 INFO - Checking for hosts without state > 2016-06-16 01:19:14,684 INFO - Checking host component states count equals > host component desired states count > 2016-06-16 01:19:14,685 INFO - Checking services and their configs > 2016-06-16 01:19:16,045 ERROR - Required config(s): slider-client is(are) not > available for service SLIDER with service config version 2 in cluster > hortonhdp > 2016-06-16 01:19:16,161 INFO - *** Check > database completed *** -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-16920) Follow up issue for Spark2 stack definition
[ https://issues.apache.org/jira/browse/AMBARI-16920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya resolved AMBARI-16920. Resolution: Fixed > Follow up issue for Spark2 stack definition > --- > > Key: AMBARI-16920 > URL: https://issues.apache.org/jira/browse/AMBARI-16920 > Project: Ambari > Issue Type: Sub-task > Components: stacks >Affects Versions: 2.4.0 >Reporter: Jeff Zhang >Assignee: Jeff Zhang > Fix For: 2.4.0 > > Attachments: AMBARI-16920-7.patch > > > 1. Spark2 thrift server can not started due to miss of > spark-thrift-fairscheduler.xml > 2. Miss of add spark2 cache file in copy_barball.py > 3. Miss the role_commnad_order of spark2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17302) Ambari-server upgrade results in "DB configs consistency check failed. " when upgrading Azure IaaS offering
[ https://issues.apache.org/jira/browse/AMBARI-17302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-17302: --- Attachment: AMBARI-17302.patch > Ambari-server upgrade results in "DB configs consistency check failed. " when > upgrading Azure IaaS offering > --- > > Key: AMBARI-17302 > URL: https://issues.apache.org/jira/browse/AMBARI-17302 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17302.patch > > > Cluster deployed via BP based on ambari 2.2.1 have no slider-client config. > After upgrade to ambari 2.4.0 this issue appears > 2016-06-16 01:19:10,963 INFO - *** Check > database started *** > 2016-06-16 01:19:14,660 INFO - Checking for configs not mapped to any cluster > 2016-06-16 01:19:14,681 INFO - Checking for configs selected more than once > 2016-06-16 01:19:14,683 INFO - Checking for hosts without state > 2016-06-16 01:19:14,684 INFO - Checking host component states count equals > host component desired states count > 2016-06-16 01:19:14,685 INFO - Checking services and their configs > 2016-06-16 01:19:16,045 ERROR - Required config(s): slider-client is(are) not > available for service SLIDER with service config version 2 in cluster > hortonhdp > 2016-06-16 01:19:16,161 INFO - *** Check > database completed *** -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16740) Atlas Integration : Rename atlas lineage configurations
[ https://issues.apache.org/jira/browse/AMBARI-16740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-16740: - Assignee: Tom Beerbower (was: Alejandro Fernandez) > Atlas Integration : Rename atlas lineage configurations > --- > > Key: AMBARI-16740 > URL: https://issues.apache.org/jira/browse/AMBARI-16740 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Tom Beerbower >Assignee: Tom Beerbower > Fix For: 2.4.0 > > > As part of ATLAS-713, the following changes are required in atlas > configuration that is set by Ambari: > # atlas.lineage.hive.table.schema.query.Table renamed to > atlas.lineage.schema.query.Table > # atlas.lineage.hive.table.schema.query.hive_table renamed to > atlas.lineage.schema.query.hive_table -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16740) Atlas Integration : Rename atlas lineage configurations
[ https://issues.apache.org/jira/browse/AMBARI-16740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15336791#comment-15336791 ] Alejandro Fernandez commented on AMBARI-16740: -- Closed already in AMBARI-16730. > Atlas Integration : Rename atlas lineage configurations > --- > > Key: AMBARI-16740 > URL: https://issues.apache.org/jira/browse/AMBARI-16740 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Tom Beerbower >Assignee: Tom Beerbower > Fix For: 2.4.0 > > > As part of ATLAS-713, the following changes are required in atlas > configuration that is set by Ambari: > # atlas.lineage.hive.table.schema.query.Table renamed to > atlas.lineage.schema.query.Table > # atlas.lineage.hive.table.schema.query.hive_table renamed to > atlas.lineage.schema.query.hive_table -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-13364) Parameterize stack information used by common services
[ https://issues.apache.org/jira/browse/AMBARI-13364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-13364: --- Summary: Parameterize stack information used by common services (was: Stack featurization: Parameterize stack information used by common services) > Parameterize stack information used by common services > -- > > Key: AMBARI-13364 > URL: https://issues.apache.org/jira/browse/AMBARI-13364 > Project: Ambari > Issue Type: Story > Components: ambari-server >Affects Versions: 2.1.0, 2.2.0 >Reporter: Tuong Truong >Assignee: Juanjo Marron > Fix For: 2.4.0 > > Attachments: AMBARI-13364.patch, stack_featurizer.patch > > > This feature will add a basic framework to remove hardcoded stack information > out of the common services and use parameter to get access to stack > information. Currently, common services hardcodes much information specific > to Hortonworks' HDP stack including name (HDP), specific versions (2.0, 2.1, > 2.2), and install location. This feature will propose a way of > configuration these information and parameterize them into the services for > reference as require. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12697) Rolling upgrade: Ambari UI should be able to display rolling upgrade history
[
https://issues.apache.org/jira/browse/AMBARI-12697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15336486#comment-15336486
]
Hadoop QA commented on AMBARI-12697:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12811385/Upgrade_Details_view.png
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/7411//console
This message is automatically generated.
> Rolling upgrade: Ambari UI should be able to display rolling upgrade history
>
>
> Key: AMBARI-12697
> URL: https://issues.apache.org/jira/browse/AMBARI-12697
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server, ambari-web
>Affects Versions: 2.1.0
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-12697.patch, Upgrade_Details_view.png,
> Upgrade_History_UI.pdf, Upgrade_History_view.png
>
>
> Ambari UI shows operation history in the ops prompt. All upgrade and
> downgrade attempts are not shown on the UI once user finalizes it and close
> the upgrade/downgrade UI.
> The information is in the database already. This JIRA is to propose a way to
> add UI elements to display a list of upgrades/downgrades associated with the
> cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17298) Add View Operational Logs role info to RBAC help table
[ https://issues.apache.org/jira/browse/AMBARI-17298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15336496#comment-15336496 ] Aleksandr Kovalenko commented on AMBARI-17298: -- PhantomJS 1.9.7 (Mac OS X): Executed 76 of 76 SUCCESS (0.428 secs / 0.61 secs) > Add View Operational Logs role info to RBAC help table > -- > > Key: AMBARI-17298 > URL: https://issues.apache.org/jira/browse/AMBARI-17298 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17298_branch-2.4.patch > > > RBAC table (Ambari Admin -> Roles) should contain info about 'View > Operational Logs' permission on Cluster level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16920) Follow up issue for Spark2 stack definition
[ https://issues.apache.org/jira/browse/AMBARI-16920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15336607#comment-15336607 ] Jayush Luniya commented on AMBARI-16920: Unit test failure is not related to this change > Follow up issue for Spark2 stack definition > --- > > Key: AMBARI-16920 > URL: https://issues.apache.org/jira/browse/AMBARI-16920 > Project: Ambari > Issue Type: Sub-task > Components: stacks >Affects Versions: 2.4.0 >Reporter: Jeff Zhang >Assignee: Jeff Zhang > Fix For: 2.4.0 > > Attachments: AMBARI-16920-7.patch > > > 1. Spark2 thrift server can not started due to miss of > spark-thrift-fairscheduler.xml > 2. Miss of add spark2 cache file in copy_barball.py > 3. Miss the role_commnad_order of spark2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-13364) Stack featurization: Parameterize stack information used by common services
[ https://issues.apache.org/jira/browse/AMBARI-13364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-13364: --- Summary: Stack featurization: Parameterize stack information used by common services (was: Parameterize stack information used by common services) > Stack featurization: Parameterize stack information used by common services > > > Key: AMBARI-13364 > URL: https://issues.apache.org/jira/browse/AMBARI-13364 > Project: Ambari > Issue Type: Story > Components: ambari-server >Affects Versions: 2.1.0, 2.2.0 >Reporter: Tuong Truong >Assignee: Juanjo Marron > Fix For: 2.4.0 > > Attachments: AMBARI-13364.patch, stack_featurizer.patch > > > This feature will add a basic framework to remove hardcoded stack information > out of the common services and use parameter to get access to stack > information. Currently, common services hardcodes much information specific > to Hortonworks' HDP stack including name (HDP), specific versions (2.0, 2.1, > 2.2), and install location. This feature will propose a way of > configuration these information and parameterize them into the services for > reference as require. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16730) Atlas Integration : Rename atlas lineage configurations
[ https://issues.apache.org/jira/browse/AMBARI-16730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-16730: - Affects Version/s: 2.4.0 > Atlas Integration : Rename atlas lineage configurations > --- > > Key: AMBARI-16730 > URL: https://issues.apache.org/jira/browse/AMBARI-16730 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Tom Beerbower >Assignee: Tom Beerbower > Fix For: 2.4.0 > > > As part of ATLAS-713, the following changes are required in atlas > configuration that is set by Ambari: > # atlas.lineage.hive.table.schema.query.Table renamed to > atlas.lineage.schema.query.Table > # atlas.lineage.hive.table.schema.query.hive_table renamed to > atlas.lineage.schema.query.hive_table -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17298) Add View Operational Logs role info to RBAC help table
[ https://issues.apache.org/jira/browse/AMBARI-17298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-17298: - Resolution: Fixed Status: Resolved (was: Patch Available) > Add View Operational Logs role info to RBAC help table > -- > > Key: AMBARI-17298 > URL: https://issues.apache.org/jira/browse/AMBARI-17298 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17298_branch-2.4.patch > > > RBAC table (Ambari Admin -> Roles) should contain info about 'View > Operational Logs' permission on Cluster level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17295) Views in Ambari UI don't render when proxied by Knox
[ https://issues.apache.org/jira/browse/AMBARI-17295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-17295: - Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and branch-2.4 > Views in Ambari UI don't render when proxied by Knox > > > Key: AMBARI-17295 > URL: https://issues.apache.org/jira/browse/AMBARI-17295 > Project: Ambari > Issue Type: Bug > Components: ambari-admin, ambari-views, ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17295.patch > > > When using Knox's AMBARIUI service to proxy the Ambari service's UI, the > various 'views' don't render. The rest of the UI around management of > services works correctly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17293) Ambari does not refresh yarn queues when HiveServerIntearctive component is restarted
[ https://issues.apache.org/jira/browse/AMBARI-17293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-17293: - Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and branch-2.4 > Ambari does not refresh yarn queues when HiveServerIntearctive component is > restarted > - > > Key: AMBARI-17293 > URL: https://issues.apache.org/jira/browse/AMBARI-17293 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17293.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-16740) Atlas Integration : Rename atlas lineage configurations
[ https://issues.apache.org/jira/browse/AMBARI-16740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez resolved AMBARI-16740. -- Resolution: Duplicate > Atlas Integration : Rename atlas lineage configurations > --- > > Key: AMBARI-16740 > URL: https://issues.apache.org/jira/browse/AMBARI-16740 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Tom Beerbower >Assignee: Tom Beerbower > Fix For: 2.4.0 > > > As part of ATLAS-713, the following changes are required in atlas > configuration that is set by Ambari: > # atlas.lineage.hive.table.schema.query.Table renamed to > atlas.lineage.schema.query.Table > # atlas.lineage.hive.table.schema.query.hive_table renamed to > atlas.lineage.schema.query.hive_table -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16730) Atlas Integration : Rename atlas lineage configurations
[ https://issues.apache.org/jira/browse/AMBARI-16730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-16730: - Fix Version/s: 2.4.0 > Atlas Integration : Rename atlas lineage configurations > --- > > Key: AMBARI-16730 > URL: https://issues.apache.org/jira/browse/AMBARI-16730 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Tom Beerbower >Assignee: Tom Beerbower > Fix For: 2.4.0 > > > As part of ATLAS-713, the following changes are required in atlas > configuration that is set by Ambari: > # atlas.lineage.hive.table.schema.query.Table renamed to > atlas.lineage.schema.query.Table > # atlas.lineage.hive.table.schema.query.hive_table renamed to > atlas.lineage.schema.query.hive_table -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-17299) Ambari Metrics service check failed exceed timeout
[
https://issues.apache.org/jira/browse/AMBARI-17299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen reassigned AMBARI-17299:
---
Assignee: Dmytro Sen
> Ambari Metrics service check failed exceed timeout
> --
>
> Key: AMBARI-17299
> URL: https://issues.apache.org/jira/browse/AMBARI-17299
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17299.patch
>
>
> Service check failed stderr:
> {noformat}
> Python script has been killed due to timeout after waiting 600 secs
> {noformat}
> No phoenix-server.jar in /usr/lib/ams-hbase/lib/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17180) Fix HA enabled logic in the alerts
[ https://issues.apache.org/jira/browse/AMBARI-17180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15336461#comment-15336461 ] Hudson commented on AMBARI-17180: - FAILURE: Integrated in Ambari-trunk-Commit #5104 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5104/]) AMBARI-17180. Fix HA enabled logic in the alerts (Miklos Gergely via (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5bd5e2da8b62a83c1275e0b7e484edd78577a34e]) * ambari-agent/src/main/python/ambari_agent/alerts/base_alert.py > Fix HA enabled logic in the alerts > -- > > Key: AMBARI-17180 > URL: https://issues.apache.org/jira/browse/AMBARI-17180 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.4.0 > > Attachments: AMBARI-17180.patch > > > base_alert.py puts a warning into the log if there are properties referenced > in the HA nameservice or the alias which are not present in the > configuration. The absence of these properties is an indicator that the HA is > not enabled, it is not a cause for warning. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16920) Follow up issue for Spark2 stack definition
[ https://issues.apache.org/jira/browse/AMBARI-16920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15336462#comment-15336462 ] Hudson commented on AMBARI-16920: - FAILURE: Integrated in Ambari-trunk-Commit #5104 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5104/]) AMBARI-16920: Follow up issue for Spark2 stack definition (Jeff Zhang (jluniya: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a6e2d9203092ef36d141c781938b086518db8385]) * ambari-server/src/main/resources/stacks/HDP/2.5/role_command_order.json * ambari-common/src/main/python/resource_management/libraries/functions/copy_tarball.py * ambari-server/src/test/python/stacks/2.0.6/hooks/after-INSTALL/test_after_install.py * ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/params.py * ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/spark_service.py * ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py > Follow up issue for Spark2 stack definition > --- > > Key: AMBARI-16920 > URL: https://issues.apache.org/jira/browse/AMBARI-16920 > Project: Ambari > Issue Type: Sub-task > Components: stacks >Affects Versions: 2.4.0 >Reporter: Jeff Zhang >Assignee: Jeff Zhang > Fix For: 2.4.0 > > Attachments: AMBARI-16920-7.patch > > > 1. Spark2 thrift server can not started due to miss of > spark-thrift-fairscheduler.xml > 2. Miss of add spark2 cache file in copy_barball.py > 3. Miss the role_commnad_order of spark2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17304) Ambari Flume Sink Unit Test failure
[
https://issues.apache.org/jira/browse/AMBARI-17304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-17304:
---
Status: Patch Available (was: Open)
> Ambari Flume Sink Unit Test failure
> ---
>
> Key: AMBARI-17304
> URL: https://issues.apache.org/jira/browse/AMBARI-17304
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17304.patch
>
>
> https://builds.apache.org/job/Ambari-trunk-Commit/5087/testReport/junit/org.apache.hadoop.metrics2.sink.flume/FlumeTimelineMetricsSinkTest/initializationError/
> {noformat}
> Error Message
> Failed to transform class with name
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink. Reason:
> findLiveCollectorHostsFromKnownCollector
> (Ljava/lang/String;Ljava/lang/String;)Ljava/util/Collection; in
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink: failed
> to resolve types
> Stacktrace
> java.lang.IllegalStateException: Failed to transform class with name
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink. Reason:
> findLiveCollectorHostsFromKnownCollector
> (Ljava/lang/String;Ljava/lang/String;)Ljava/util/Collection; in
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink: failed
> to resolve types
> Caused by: javassist.CannotCompileException:
> findLiveCollectorHostsFromKnownCollector
> (Ljava/lang/String;Ljava/lang/String;)Ljava/util/Collection; in
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink: failed
> to resolve types
> Caused by: javassist.bytecode.BadBytecode:
> findLiveCollectorHostsFromKnownCollector
> (Ljava/lang/String;Ljava/lang/String;)Ljava/util/Collection; in
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink: failed
> to resolve types
> Caused by: javassist.bytecode.BadBytecode: failed to resolve types
> Caused by: javassist.NotFoundException: com.google.common.reflect.TypeToken
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-17305) Local User not displaying in View All option in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-17305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang resolved AMBARI-17305. --- Resolution: Fixed Committed to trunk and 2.4 4de9961707a2b977cecbd84e5f65570c16c71b52 > Local User not displaying in View All option in Ambari > -- > > Key: AMBARI-17305 > URL: https://issues.apache.org/jira/browse/AMBARI-17305 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.4.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.4.0 > > Attachments: AMBARI-17305.patch > > > From Ambari dashboard, click on Admin -> Manage Ambari -> Users. You will see > message "No users to display". To see the local user, you will have to select > "Type" to "Local". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17253) Ambari Alert causes too many wanings in ZooKeeper logs.
[
https://issues.apache.org/jira/browse/AMBARI-17253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-17253:
-
Attachment: AMBARI-17253.patch
> Ambari Alert causes too many wanings in ZooKeeper logs.
> ---
>
> Key: AMBARI-17253
> URL: https://issues.apache.org/jira/browse/AMBARI-17253
> Project: Ambari
> Issue Type: Bug
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-17253.patch
>
>
> There are too many WARNING in ZooKeeper log.
> {code}
> 2016-06-15 21:02:15,405 - WARN
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@357] - caught end of
> stream exception
> EndOfStreamException: Unable to read additional data from client sessionid
> 0x0, likely client has closed socket
> at
> org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:228)
> at
> org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:208)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> It may be because of Ambari Alert. Ambari Alert pings to the zookeeper port
> to do monitoring.
> We should use 'ruok' to monitor zookeepers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17302) Ambari-server upgrade results in "DB configs consistency check failed. "
[
https://issues.apache.org/jira/browse/AMBARI-17302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15337433#comment-15337433
]
Hadoop QA commented on AMBARI-17302:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12811422/AMBARI-17302.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7417//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7417//console
This message is automatically generated.
> Ambari-server upgrade results in "DB configs consistency check failed. "
>
>
> Key: AMBARI-17302
> URL: https://issues.apache.org/jira/browse/AMBARI-17302
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17302.patch
>
>
> Cluster deployed via BP based on ambari 2.2.1 have no slider-client config.
> After upgrade to ambari 2.4.0 this issue appears
> 2016-06-16 01:19:10,963 INFO - *** Check
> database started ***
> 2016-06-16 01:19:14,660 INFO - Checking for configs not mapped to any cluster
> 2016-06-16 01:19:14,681 INFO - Checking for configs selected more than once
> 2016-06-16 01:19:14,683 INFO - Checking for hosts without state
> 2016-06-16 01:19:14,684 INFO - Checking host component states count equals
> host component desired states count
> 2016-06-16 01:19:14,685 INFO - Checking services and their configs
> 2016-06-16 01:19:16,045 ERROR - Required config(s): slider-client is(are) not
> available for service SLIDER with service config version 2 in cluster
> hortonhdp
> 2016-06-16 01:19:16,161 INFO - *** Check
> database completed ***
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17304) Ambari Flume Sink Unit Test failure
[
https://issues.apache.org/jira/browse/AMBARI-17304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15337458#comment-15337458
]
Hudson commented on AMBARI-17304:
-
SUCCESS: Integrated in Ambari-trunk-Commit #5109 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5109/])
AMBARI-17304 : Ambari Flume Sink Unit Test failure (avijayan) (avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3d13eb4f2344174e615fe1fa4f3a1f4adedbddaa])
* ambari-metrics/ambari-metrics-flume-sink/pom.xml
> Ambari Flume Sink Unit Test failure
> ---
>
> Key: AMBARI-17304
> URL: https://issues.apache.org/jira/browse/AMBARI-17304
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17304.patch
>
>
> https://builds.apache.org/job/Ambari-trunk-Commit/5087/testReport/junit/org.apache.hadoop.metrics2.sink.flume/FlumeTimelineMetricsSinkTest/initializationError/
> {noformat}
> Error Message
> Failed to transform class with name
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink. Reason:
> findLiveCollectorHostsFromKnownCollector
> (Ljava/lang/String;Ljava/lang/String;)Ljava/util/Collection; in
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink: failed
> to resolve types
> Stacktrace
> java.lang.IllegalStateException: Failed to transform class with name
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink. Reason:
> findLiveCollectorHostsFromKnownCollector
> (Ljava/lang/String;Ljava/lang/String;)Ljava/util/Collection; in
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink: failed
> to resolve types
> Caused by: javassist.CannotCompileException:
> findLiveCollectorHostsFromKnownCollector
> (Ljava/lang/String;Ljava/lang/String;)Ljava/util/Collection; in
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink: failed
> to resolve types
> Caused by: javassist.bytecode.BadBytecode:
> findLiveCollectorHostsFromKnownCollector
> (Ljava/lang/String;Ljava/lang/String;)Ljava/util/Collection; in
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink: failed
> to resolve types
> Caused by: javassist.bytecode.BadBytecode: failed to resolve types
> Caused by: javassist.NotFoundException: com.google.common.reflect.TypeToken
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17305) Local User not displaying in View All option in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-17305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15337457#comment-15337457 ] Hudson commented on AMBARI-17305: - SUCCESS: Integrated in Ambari-trunk-Commit #5109 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5109/]) AMBARI-17305 - Local User not displaying in View All option in Ambari (rzang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4de9961707a2b977cecbd84e5f65570c16c71b52]) * ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/users/UsersListCtrl.js * ambari-admin/src/main/resources/ui/admin-web/app/scripts/app.js > Local User not displaying in View All option in Ambari > -- > > Key: AMBARI-17305 > URL: https://issues.apache.org/jira/browse/AMBARI-17305 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.4.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.4.0 > > Attachments: AMBARI-17305.patch > > > From Ambari dashboard, click on Admin -> Manage Ambari -> Users. You will see > message "No users to display". To see the local user, you will have to select > "Type" to "Local". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17303) [Grafana] Updated dashboards
[ https://issues.apache.org/jira/browse/AMBARI-17303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15337459#comment-15337459 ] Hudson commented on AMBARI-17303: - SUCCESS: Integrated in Ambari-trunk-Commit #5109 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5109/]) AMBARI-17303. [Grafana] Updated dashboards. (Prajwal Rao via yusaku) (yusaku: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e960eb6b6c29b8697851d00c31b97415bb69730d]) * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-hbase-tables.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-hdfs-datanodes.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-kafka-hosts.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-hbase-users.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/default/grafana-system-servers.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-yarn-nodemanagers.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-hbase-regionservers.json * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-hbase-misc.json > [Grafana] Updated dashboards > > > Key: AMBARI-17303 > URL: https://issues.apache.org/jira/browse/AMBARI-17303 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: ambari-2.4.0 >Reporter: Prajwal Rao >Assignee: Prajwal Rao >Priority: Critical > Fix For: ambari-2.4.0 > > Attachments: AMBARI-17303.patch > > > Updated the following dashboards > - hbase-misc - (topN) > - hbase-regionservers - (topN) > - hbase-tables - (added how-to enable) > - hbase-users - (added how-to enable) > - hdfs-datanodes - (topN) > - kafka-hosts - (topN) > - yarn-nodemanagers - (topN) > - system-servers - (topN) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17291) zookeeper.quorum in storm-metrics2.properties is broken
[
https://issues.apache.org/jira/browse/AMBARI-17291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-17291:
-
Status: Patch Available (was: In Progress)
> zookeeper.quorum in storm-metrics2.properties is broken
> ---
>
> Key: AMBARI-17291
> URL: https://issues.apache.org/jira/browse/AMBARI-17291
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics, ambari-server
>Affects Versions: trunk
> Environment: CentOS7.2
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-17291.patch
>
>
> When installed Storm, {{zookeeper.quorum}} in
> /etc/storm/conf/storm-metrics2.properties is looks like this.
> {code}
> zookeeper.quorum=[:2181,':2181,c:2181,7:2181,2:2181,0:2181,1:2181,.:2181,a:2181,m:2181,b:2181,a:2181,r:2181,i:2181,.:2181,a:2181,p:2181,a:2181,c:2181,h:2181,e:2181,.:2181,o:2181,r:2181,g:2181,':2181,,:2181,':2181,c:2181,7:2181,2:2181,0:2181,2:2181,.:2181,a:2181,m:2181,b:2181,a:2181,r:2181,i:2181,.:2181,a:2181,p:2181,a:2181,c:2181,h:2181,e:2181,.:2181,o:2181,r:2181,g:2181,':2181,,:2181,':2181,c:2181,7:2181,2:2181,0:2181,3:2181,.:2181,a:2181,m:2181,b:2181,a:2181,r:2181,i:2181,.:2181,a:2181,p:2181,a:2181,c:2181,h:2181,e:2181,.:2181,o:2181,r:2181,g:2181,':2181,]:2181
> {code}
> storm.zookeeper.servers is
> {{['c7201.ambari.apache.org','c7202.ambari.apache.org','c7203.ambari.apache.org']}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17291) zookeeper.quorum in storm-metrics2.properties is broken
[
https://issues.apache.org/jira/browse/AMBARI-17291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15337508#comment-15337508
]
Masahiro Tanaka commented on AMBARI-17291:
--
After the patch:
{code}
zookeeper.quorum=c7201.ambari.apache.org:2181,c7202.ambari.apache.org:2181,c7203.ambari.apache.org:2181
{code}
> zookeeper.quorum in storm-metrics2.properties is broken
> ---
>
> Key: AMBARI-17291
> URL: https://issues.apache.org/jira/browse/AMBARI-17291
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics, ambari-server
>Affects Versions: trunk
> Environment: CentOS7.2
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-17291.patch
>
>
> When installed Storm, {{zookeeper.quorum}} in
> /etc/storm/conf/storm-metrics2.properties is looks like this.
> {code}
> zookeeper.quorum=[:2181,':2181,c:2181,7:2181,2:2181,0:2181,1:2181,.:2181,a:2181,m:2181,b:2181,a:2181,r:2181,i:2181,.:2181,a:2181,p:2181,a:2181,c:2181,h:2181,e:2181,.:2181,o:2181,r:2181,g:2181,':2181,,:2181,':2181,c:2181,7:2181,2:2181,0:2181,2:2181,.:2181,a:2181,m:2181,b:2181,a:2181,r:2181,i:2181,.:2181,a:2181,p:2181,a:2181,c:2181,h:2181,e:2181,.:2181,o:2181,r:2181,g:2181,':2181,,:2181,':2181,c:2181,7:2181,2:2181,0:2181,3:2181,.:2181,a:2181,m:2181,b:2181,a:2181,r:2181,i:2181,.:2181,a:2181,p:2181,a:2181,c:2181,h:2181,e:2181,.:2181,o:2181,r:2181,g:2181,':2181,]:2181
> {code}
> storm.zookeeper.servers is
> {{['c7201.ambari.apache.org','c7202.ambari.apache.org','c7203.ambari.apache.org']}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17274) As part of atlas startup,"/usr/lib/ambari-logsearch-solr-client/solrCloudCli.sh" script is executed by ambari, which fails with "java.io.FileNotFoundException"
[
https://issues.apache.org/jira/browse/AMBARI-17274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15337360#comment-15337360
]
Hudson commented on AMBARI-17274:
-
FAILURE: Integrated in Ambari-trunk-Commit #5108 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5108/])
AMBARI-17274. As part of atlas startup, (afernandez:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=92237462de2e5f4177113a07129b10834a9c5ca0])
* ambari-server/src/test/python/stacks/2.3/configs/default.json
*
ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/configuration/atlas-solrconfig.xml
* ambari-server/src/test/python/stacks/2.3/ATLAS/test_metadata_server.py
*
ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/params.py
* ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/metainfo.xml
* ambari-server/src/test/python/stacks/2.5/ATLAS/test_atlas_server.py
* ambari-server/src/test/python/stacks/2.3/configs/secure.json
* ambari-server/src/test/python/stacks/2.5/configs/default.json
*
ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata.py
> As part of atlas
> startup,"/usr/lib/ambari-logsearch-solr-client/solrCloudCli.sh" script is
> executed by ambari, which fails with "java.io.FileNotFoundException"
> ---
>
> Key: AMBARI-17274
> URL: https://issues.apache.org/jira/browse/AMBARI-17274
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Fix For: 2.4.0
>
>
> Below is the error log.
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py",
> line 173, in
> MetadataServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 257, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py",
> line 69, in start
> self.configure(env)
> File
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py",
> line 53, in configure
> metadata()
> File
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata.py",
> line 101, in metadata
> upload_conf_set('basic_configs', random_num)
> File
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata.py",
> line 122, in upload_conf_set
> user=params.metadata_user)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/solr_cloud_util.py",
> line 49, in upload_configuration_to_zk
> user=user
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, 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 273, 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 70, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 92, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 293, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'export
> JAVA_HOME=/usr/jdk64/jdk1.8.0_77 ;
> /usr/lib/ambari-logsearch-solr-client/solrCloudCli.sh -z
> os-d7-unsecure-atlas-3.openstacklocal:2181,os-d7-unsecure-atlas-1.openstacklocal:2181/ambari-solr
> --upload-config -d
> /usr/lib/ambari-logsearch-solr/server/solr/configsets/basic_configs/conf -cs
> basic_configs -rt 5 -i 10' returned 1. log4j:ERROR setFile(null,true) call
> failed.
> java.io.FileNotFoundException: (No such file or directory)
> at java.io.FileOutputStream.open0(Native Method)
> at java.io.FileOutputStream.open(FileOutputStream.java:270)
> at java.io.FileOutputStream.(FileOutputStream.java:213)
> at java.io.FileOutputStream.(FileOutputStream.java:133)
> at
[jira] [Commented] (AMBARI-17286) Service config links should use public host name
[ https://issues.apache.org/jira/browse/AMBARI-17286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15337361#comment-15337361 ] Hudson commented on AMBARI-17286: - FAILURE: Integrated in Ambari-trunk-Commit #5108 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5108/]) AMBARI-17286 Service config links should use public host name (zhewang) (zhewang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=54d76f5b8fe9d1b6fbcbab1732267b7e13413118]) * ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py * ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py * ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py * ambari-server/src/test/python/unitTests.py * ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py > Service config links should use public host name > > > Key: AMBARI-17286 > URL: https://issues.apache.org/jira/browse/AMBARI-17286 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-17286.v0.patch, AMBARI-17286.v1.patch > > > Service config links (e.g. tez.tez-ui.history-url.base) need to use the > Ambari server's public name / IP instead of the private one. (Since > tez.tez-ui.history-url.base is used to navigate from RM UI to Tez View.) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17304) Ambari Flume Sink Unit Test failure
[
https://issues.apache.org/jira/browse/AMBARI-17304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-17304:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to trunk and branch-2.4
> Ambari Flume Sink Unit Test failure
> ---
>
> Key: AMBARI-17304
> URL: https://issues.apache.org/jira/browse/AMBARI-17304
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17304.patch
>
>
> https://builds.apache.org/job/Ambari-trunk-Commit/5087/testReport/junit/org.apache.hadoop.metrics2.sink.flume/FlumeTimelineMetricsSinkTest/initializationError/
> {noformat}
> Error Message
> Failed to transform class with name
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink. Reason:
> findLiveCollectorHostsFromKnownCollector
> (Ljava/lang/String;Ljava/lang/String;)Ljava/util/Collection; in
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink: failed
> to resolve types
> Stacktrace
> java.lang.IllegalStateException: Failed to transform class with name
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink. Reason:
> findLiveCollectorHostsFromKnownCollector
> (Ljava/lang/String;Ljava/lang/String;)Ljava/util/Collection; in
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink: failed
> to resolve types
> Caused by: javassist.CannotCompileException:
> findLiveCollectorHostsFromKnownCollector
> (Ljava/lang/String;Ljava/lang/String;)Ljava/util/Collection; in
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink: failed
> to resolve types
> Caused by: javassist.bytecode.BadBytecode:
> findLiveCollectorHostsFromKnownCollector
> (Ljava/lang/String;Ljava/lang/String;)Ljava/util/Collection; in
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink: failed
> to resolve types
> Caused by: javassist.bytecode.BadBytecode: failed to resolve types
> Caused by: javassist.NotFoundException: com.google.common.reflect.TypeToken
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17291) zookeeper.quorum in storm-metrics2.properties is broken
[
https://issues.apache.org/jira/browse/AMBARI-17291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-17291:
-
Attachment: AMBARI-17291.patch
> zookeeper.quorum in storm-metrics2.properties is broken
> ---
>
> Key: AMBARI-17291
> URL: https://issues.apache.org/jira/browse/AMBARI-17291
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics, ambari-server
>Affects Versions: trunk
> Environment: CentOS7.2
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-17291.patch
>
>
> When installed Storm, {{zookeeper.quorum}} in
> /etc/storm/conf/storm-metrics2.properties is looks like this.
> {code}
> zookeeper.quorum=[:2181,':2181,c:2181,7:2181,2:2181,0:2181,1:2181,.:2181,a:2181,m:2181,b:2181,a:2181,r:2181,i:2181,.:2181,a:2181,p:2181,a:2181,c:2181,h:2181,e:2181,.:2181,o:2181,r:2181,g:2181,':2181,,:2181,':2181,c:2181,7:2181,2:2181,0:2181,2:2181,.:2181,a:2181,m:2181,b:2181,a:2181,r:2181,i:2181,.:2181,a:2181,p:2181,a:2181,c:2181,h:2181,e:2181,.:2181,o:2181,r:2181,g:2181,':2181,,:2181,':2181,c:2181,7:2181,2:2181,0:2181,3:2181,.:2181,a:2181,m:2181,b:2181,a:2181,r:2181,i:2181,.:2181,a:2181,p:2181,a:2181,c:2181,h:2181,e:2181,.:2181,o:2181,r:2181,g:2181,':2181,]:2181
> {code}
> storm.zookeeper.servers is
> {{['c7201.ambari.apache.org','c7202.ambari.apache.org','c7203.ambari.apache.org']}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-17306) Filter out MOTD logging from 'llapstatus' command in order to get the output which is JSON parsable.
Swapan Shridhar created AMBARI-17306: Summary: Filter out MOTD logging from 'llapstatus' command in order to get the output which is JSON parsable. Key: AMBARI-17306 URL: https://issues.apache.org/jira/browse/AMBARI-17306 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Swapan Shridhar Assignee: Swapan Shridhar Fix For: 2.4.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-17306) Filter out MOTD logging from 'llapstatus' command in order to get the output which is JSON parsable.
[
https://issues.apache.org/jira/browse/AMBARI-17306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15337391#comment-15337391
]
Swapan Shridhar edited comment on AMBARI-17306 at 6/18/16 1:14 AM:
---
So, for *CASE A*, check for filtering is as follows :
- the current line to be : *"{"*, and
- next line to be *""amInfo" : {"*.
- And last line to be *"}"*
OR
for *CASE B*, check for filtering is as follows:
- the current line to be : *"{"*, and
- next line to be *"state" :*.
- And next to next line to be *"}"* and line is the last one.
To figure out the start of JSON output.
was (Author: swapanshridhar):
So, for *CASE A*, check for filtering is as follows :
- the current line to be : *"{"*, and
- next line to be *""amInfo" : {"*.
- And last line to be *"}"*
OR
for *CASE B*, check for filtering is as follows:
- the current line to be : *"{"*, and
- next line to be *"state" :*.
- And next to next line to be *"}"* and line is the last one.
- to figure out the start of JSON output.
> Filter out MOTD logging from 'llapstatus' command in order to get the output
> which is JSON parsable.
>
>
> Key: AMBARI-17306
> URL: https://issues.apache.org/jira/browse/AMBARI-17306
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
>
> Example of expected response which can be JSON parsed:
> *CASE A:*
> {code}
> {
> "amInfo" : {
> "appName" : "llap0",
> "appType" : "org-apache-slider",
> "appId" : "application_1466036628595_0010",
> "containerId" : "container_1466036628595_0010_01_01",
> "hostname" : "ts-hs2ia-0615-r-2.openstacklocal",
> "amWebUrl" : "http://ts-hs2ia-0615-r-2.openstacklocal:60865/;
> },
> "state" : "LAUNCHING",
> "originalConfigurationPath" :
> "hdfs://ts-hs2ia-0615-r-5.openstacklocal:8020/user/hive/.slider/cluster/llap0/snapshot",
> "generatedConfigurationPath" :
> "hdfs://ts-hs2ia-0615-r-5.openstacklocal:8020/user/hive/.slider/cluster/llap0/generated",
> "desiredInstances" : 1,
> "liveInstances" : 0,
> "appStartTime" : 1466123287309
> }
> {code}
> The same output with MOTD message:
> {code}
> This is MOTD message
> This is MOTD message1
> {
> "amInfo" : {
> "appName" : "llap0",
> "appType" : "org-apache-slider",
> "appId" : "application_1466036628595_0010",
> "containerId" : "container_1466036628595_0010_01_01",
> "hostname" : "ts-hs2ia-0615-r-2.openstacklocal",
> "amWebUrl" : "http://ts-hs2ia-0615-r-2.openstacklocal:60865/;
> },
> "state" : "LAUNCHING",
> "originalConfigurationPath" :
> "hdfs://ts-hs2ia-0615-r-5.openstacklocal:8020/user/hive/.slider/cluster/llap0/snapshot",
> "generatedConfigurationPath" :
> "hdfs://ts-hs2ia-0615-r-5.openstacklocal:8020/user/hive/.slider/cluster/llap0/generated",
> "desiredInstances" : 1,
> "liveInstances" : 0,
> "appStartTime" : 1466123287309
> }
> {code}
> Other scenario can be (eg: APP_NOTFOUND):
> *CASE B:*
> {code}
> This is MOTD message
> This is MOTD message1
> {
> "state" : "APP_NOT_FOUND"
> }
> {code}
> - We need to filter out extra lines initially added on top of JSON parseable
> string.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-17306) Filter out MOTD logging from 'llapstatus' command in order to get the output which is JSON parsable.
[
https://issues.apache.org/jira/browse/AMBARI-17306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15337391#comment-15337391
]
Swapan Shridhar edited comment on AMBARI-17306 at 6/18/16 1:15 AM:
---
So, for *CASE A*, check for filtering is as follows :
- the current line to be : *"{"*, and
- next line to be *""amInfo" : {"*
- And last line to be *"}"*
OR
for *CASE B*, check for filtering is as follows:
- the current line to be : *"{"*, and
- next line to be *"state" :*
- And next to next line to be *"}"* and line is the last one.
To figure out the start of JSON output.
was (Author: swapanshridhar):
So, for *CASE A*, check for filtering is as follows :
- the current line to be : *"{"*, and
- next line to be *""amInfo" : {"*
- And last line to be *"}"*
OR
for *CASE B*, check for filtering is as follows:
- the current line to be : *"{"*, and
- next line to be *"state" :*
- And next to next line to be *"}"* and line is the last one.
To figure out the start of JSON output.
> Filter out MOTD logging from 'llapstatus' command in order to get the output
> which is JSON parsable.
>
>
> Key: AMBARI-17306
> URL: https://issues.apache.org/jira/browse/AMBARI-17306
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
>
> Example of expected response which can be JSON parsed:
> *CASE A:*
> {code}
> {
> "amInfo" : {
> "appName" : "llap0",
> "appType" : "org-apache-slider",
> "appId" : "application_1466036628595_0010",
> "containerId" : "container_1466036628595_0010_01_01",
> "hostname" : "ts-hs2ia-0615-r-2.openstacklocal",
> "amWebUrl" : "http://ts-hs2ia-0615-r-2.openstacklocal:60865/;
> },
> "state" : "LAUNCHING",
> "originalConfigurationPath" :
> "hdfs://ts-hs2ia-0615-r-5.openstacklocal:8020/user/hive/.slider/cluster/llap0/snapshot",
> "generatedConfigurationPath" :
> "hdfs://ts-hs2ia-0615-r-5.openstacklocal:8020/user/hive/.slider/cluster/llap0/generated",
> "desiredInstances" : 1,
> "liveInstances" : 0,
> "appStartTime" : 1466123287309
> }
> {code}
> The same output with MOTD message:
> {code}
> This is MOTD message
> This is MOTD message1
> {
> "amInfo" : {
> "appName" : "llap0",
> "appType" : "org-apache-slider",
> "appId" : "application_1466036628595_0010",
> "containerId" : "container_1466036628595_0010_01_01",
> "hostname" : "ts-hs2ia-0615-r-2.openstacklocal",
> "amWebUrl" : "http://ts-hs2ia-0615-r-2.openstacklocal:60865/;
> },
> "state" : "LAUNCHING",
> "originalConfigurationPath" :
> "hdfs://ts-hs2ia-0615-r-5.openstacklocal:8020/user/hive/.slider/cluster/llap0/snapshot",
> "generatedConfigurationPath" :
> "hdfs://ts-hs2ia-0615-r-5.openstacklocal:8020/user/hive/.slider/cluster/llap0/generated",
> "desiredInstances" : 1,
> "liveInstances" : 0,
> "appStartTime" : 1466123287309
> }
> {code}
> Other scenario can be (eg: APP_NOTFOUND):
> *CASE B:*
> {code}
> This is MOTD message
> This is MOTD message1
> {
> "state" : "APP_NOT_FOUND"
> }
> {code}
> - We need to filter out extra lines initially added on top of JSON parseable
> string.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-17306) Filter out MOTD logging from 'llapstatus' command in order to get the output which is JSON parsable.
[
https://issues.apache.org/jira/browse/AMBARI-17306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15337391#comment-15337391
]
Swapan Shridhar edited comment on AMBARI-17306 at 6/18/16 1:15 AM:
---
So, for *CASE A*, check for filtering is as follows :
- the current line to be : *"{"*, and
- next line to be *""amInfo" : {"*
- And last line to be *"}"*
OR
for *CASE B*, check for filtering is as follows:
- the current line to be : *"{"*, and
- next line to be *"state" :*
- And next to next line to be *"}"* and line is the last one.
To figure out the start of JSON output.
was (Author: swapanshridhar):
So, for *CASE A*, check for filtering is as follows :
- the current line to be : *"{"*, and
- next line to be *""amInfo" : {"*.
- And last line to be *"}"*
OR
for *CASE B*, check for filtering is as follows:
- the current line to be : *"{"*, and
- next line to be *"state" :*.
- And next to next line to be *"}"* and line is the last one.
To figure out the start of JSON output.
> Filter out MOTD logging from 'llapstatus' command in order to get the output
> which is JSON parsable.
>
>
> Key: AMBARI-17306
> URL: https://issues.apache.org/jira/browse/AMBARI-17306
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
>
> Example of expected response which can be JSON parsed:
> *CASE A:*
> {code}
> {
> "amInfo" : {
> "appName" : "llap0",
> "appType" : "org-apache-slider",
> "appId" : "application_1466036628595_0010",
> "containerId" : "container_1466036628595_0010_01_01",
> "hostname" : "ts-hs2ia-0615-r-2.openstacklocal",
> "amWebUrl" : "http://ts-hs2ia-0615-r-2.openstacklocal:60865/;
> },
> "state" : "LAUNCHING",
> "originalConfigurationPath" :
> "hdfs://ts-hs2ia-0615-r-5.openstacklocal:8020/user/hive/.slider/cluster/llap0/snapshot",
> "generatedConfigurationPath" :
> "hdfs://ts-hs2ia-0615-r-5.openstacklocal:8020/user/hive/.slider/cluster/llap0/generated",
> "desiredInstances" : 1,
> "liveInstances" : 0,
> "appStartTime" : 1466123287309
> }
> {code}
> The same output with MOTD message:
> {code}
> This is MOTD message
> This is MOTD message1
> {
> "amInfo" : {
> "appName" : "llap0",
> "appType" : "org-apache-slider",
> "appId" : "application_1466036628595_0010",
> "containerId" : "container_1466036628595_0010_01_01",
> "hostname" : "ts-hs2ia-0615-r-2.openstacklocal",
> "amWebUrl" : "http://ts-hs2ia-0615-r-2.openstacklocal:60865/;
> },
> "state" : "LAUNCHING",
> "originalConfigurationPath" :
> "hdfs://ts-hs2ia-0615-r-5.openstacklocal:8020/user/hive/.slider/cluster/llap0/snapshot",
> "generatedConfigurationPath" :
> "hdfs://ts-hs2ia-0615-r-5.openstacklocal:8020/user/hive/.slider/cluster/llap0/generated",
> "desiredInstances" : 1,
> "liveInstances" : 0,
> "appStartTime" : 1466123287309
> }
> {code}
> Other scenario can be (eg: APP_NOTFOUND):
> *CASE B:*
> {code}
> This is MOTD message
> This is MOTD message1
> {
> "state" : "APP_NOT_FOUND"
> }
> {code}
> - We need to filter out extra lines initially added on top of JSON parseable
> string.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17306) Filter out MOTD logging from 'llapstatus' command in order to get the output which is JSON parsable.
[
https://issues.apache.org/jira/browse/AMBARI-17306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15337391#comment-15337391
]
Swapan Shridhar commented on AMBARI-17306:
--
So, for *CASE A*, check for filtering is as follows :
- the current line to be : *"{"*, and
- next line to be *""amInfo" : {"*.
- And last line to be *"}"*
OR
for *CASE B*, check for filtering is as follows:
- the current line to be : *"{"*, and
- next line to be *"state" :*.
- And next to next line to be *"}"* and line is the last one.
- to figure out the start of JSON output.
> Filter out MOTD logging from 'llapstatus' command in order to get the output
> which is JSON parsable.
>
>
> Key: AMBARI-17306
> URL: https://issues.apache.org/jira/browse/AMBARI-17306
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
>
> Example of expected response which can be JSON parsed:
> *CASE A:*
> {code}
> {
> "amInfo" : {
> "appName" : "llap0",
> "appType" : "org-apache-slider",
> "appId" : "application_1466036628595_0010",
> "containerId" : "container_1466036628595_0010_01_01",
> "hostname" : "ts-hs2ia-0615-r-2.openstacklocal",
> "amWebUrl" : "http://ts-hs2ia-0615-r-2.openstacklocal:60865/;
> },
> "state" : "LAUNCHING",
> "originalConfigurationPath" :
> "hdfs://ts-hs2ia-0615-r-5.openstacklocal:8020/user/hive/.slider/cluster/llap0/snapshot",
> "generatedConfigurationPath" :
> "hdfs://ts-hs2ia-0615-r-5.openstacklocal:8020/user/hive/.slider/cluster/llap0/generated",
> "desiredInstances" : 1,
> "liveInstances" : 0,
> "appStartTime" : 1466123287309
> }
> {code}
> The same output with MOTD message:
> {code}
> This is MOTD message
> This is MOTD message1
> {
> "amInfo" : {
> "appName" : "llap0",
> "appType" : "org-apache-slider",
> "appId" : "application_1466036628595_0010",
> "containerId" : "container_1466036628595_0010_01_01",
> "hostname" : "ts-hs2ia-0615-r-2.openstacklocal",
> "amWebUrl" : "http://ts-hs2ia-0615-r-2.openstacklocal:60865/;
> },
> "state" : "LAUNCHING",
> "originalConfigurationPath" :
> "hdfs://ts-hs2ia-0615-r-5.openstacklocal:8020/user/hive/.slider/cluster/llap0/snapshot",
> "generatedConfigurationPath" :
> "hdfs://ts-hs2ia-0615-r-5.openstacklocal:8020/user/hive/.slider/cluster/llap0/generated",
> "desiredInstances" : 1,
> "liveInstances" : 0,
> "appStartTime" : 1466123287309
> }
> {code}
> Other scenario can be (eg: APP_NOTFOUND):
> *CASE B:*
> {code}
> This is MOTD message
> This is MOTD message1
> {
> "state" : "APP_NOT_FOUND"
> }
> {code}
> - We need to filter out extra lines initially added on top of JSON parseable
> string.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17306) Filter out MOTD logging from 'llapstatus' command in order to get the output which is JSON parsable.
[
https://issues.apache.org/jira/browse/AMBARI-17306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-17306:
-
Description:
Example of expected response which can be JSON parsed:
*CASE A:*
{code}
{
"amInfo" : {
"appName" : "llap0",
"appType" : "org-apache-slider",
"appId" : "application_1466036628595_0010",
"containerId" : "container_1466036628595_0010_01_01",
"hostname" : "ts-hs2ia-0615-r-2.openstacklocal",
"amWebUrl" : "http://ts-hs2ia-0615-r-2.openstacklocal:60865/;
},
"state" : "LAUNCHING",
"originalConfigurationPath" :
"hdfs://ts-hs2ia-0615-r-5.openstacklocal:8020/user/hive/.slider/cluster/llap0/snapshot",
"generatedConfigurationPath" :
"hdfs://ts-hs2ia-0615-r-5.openstacklocal:8020/user/hive/.slider/cluster/llap0/generated",
"desiredInstances" : 1,
"liveInstances" : 0,
"appStartTime" : 1466123287309
}
{code}
The same output with MOTD message:
{code}
This is MOTD message
This is MOTD message1
{
"amInfo" : {
"appName" : "llap0",
"appType" : "org-apache-slider",
"appId" : "application_1466036628595_0010",
"containerId" : "container_1466036628595_0010_01_01",
"hostname" : "ts-hs2ia-0615-r-2.openstacklocal",
"amWebUrl" : "http://ts-hs2ia-0615-r-2.openstacklocal:60865/;
},
"state" : "LAUNCHING",
"originalConfigurationPath" :
"hdfs://ts-hs2ia-0615-r-5.openstacklocal:8020/user/hive/.slider/cluster/llap0/snapshot",
"generatedConfigurationPath" :
"hdfs://ts-hs2ia-0615-r-5.openstacklocal:8020/user/hive/.slider/cluster/llap0/generated",
"desiredInstances" : 1,
"liveInstances" : 0,
"appStartTime" : 1466123287309
}
{code}
Other scenario can be (eg: APP_NOTFOUND):
*CASE B:*
{code}
This is MOTD message
This is MOTD message1
{
"state" : "APP_NOT_FOUND"
}
{code}
- We need to filter out extra lines initially added on top of JSON parseable
string.
> Filter out MOTD logging from 'llapstatus' command in order to get the output
> which is JSON parsable.
>
>
> Key: AMBARI-17306
> URL: https://issues.apache.org/jira/browse/AMBARI-17306
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
>
> Example of expected response which can be JSON parsed:
> *CASE A:*
> {code}
> {
> "amInfo" : {
> "appName" : "llap0",
> "appType" : "org-apache-slider",
> "appId" : "application_1466036628595_0010",
> "containerId" : "container_1466036628595_0010_01_01",
> "hostname" : "ts-hs2ia-0615-r-2.openstacklocal",
> "amWebUrl" : "http://ts-hs2ia-0615-r-2.openstacklocal:60865/;
> },
> "state" : "LAUNCHING",
> "originalConfigurationPath" :
> "hdfs://ts-hs2ia-0615-r-5.openstacklocal:8020/user/hive/.slider/cluster/llap0/snapshot",
> "generatedConfigurationPath" :
> "hdfs://ts-hs2ia-0615-r-5.openstacklocal:8020/user/hive/.slider/cluster/llap0/generated",
> "desiredInstances" : 1,
> "liveInstances" : 0,
> "appStartTime" : 1466123287309
> }
> {code}
> The same output with MOTD message:
> {code}
> This is MOTD message
> This is MOTD message1
> {
> "amInfo" : {
> "appName" : "llap0",
> "appType" : "org-apache-slider",
> "appId" : "application_1466036628595_0010",
> "containerId" : "container_1466036628595_0010_01_01",
> "hostname" : "ts-hs2ia-0615-r-2.openstacklocal",
> "amWebUrl" : "http://ts-hs2ia-0615-r-2.openstacklocal:60865/;
> },
> "state" : "LAUNCHING",
> "originalConfigurationPath" :
> "hdfs://ts-hs2ia-0615-r-5.openstacklocal:8020/user/hive/.slider/cluster/llap0/snapshot",
> "generatedConfigurationPath" :
> "hdfs://ts-hs2ia-0615-r-5.openstacklocal:8020/user/hive/.slider/cluster/llap0/generated",
> "desiredInstances" : 1,
> "liveInstances" : 0,
> "appStartTime" : 1466123287309
> }
> {code}
> Other scenario can be (eg: APP_NOTFOUND):
> *CASE B:*
> {code}
> This is MOTD message
> This is MOTD message1
> {
> "state" : "APP_NOT_FOUND"
> }
> {code}
> - We need to filter out extra lines initially added on top of JSON parseable
> string.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17253) Ambari Alert causes too many wanings in ZooKeeper logs.
[
https://issues.apache.org/jira/browse/AMBARI-17253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-17253:
-
Status: Patch Available (was: Open)
> Ambari Alert causes too many wanings in ZooKeeper logs.
> ---
>
> Key: AMBARI-17253
> URL: https://issues.apache.org/jira/browse/AMBARI-17253
> Project: Ambari
> Issue Type: Bug
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-17253.patch
>
>
> There are too many WARNING in ZooKeeper log.
> {code}
> 2016-06-15 21:02:15,405 - WARN
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@357] - caught end of
> stream exception
> EndOfStreamException: Unable to read additional data from client sessionid
> 0x0, likely client has closed socket
> at
> org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:228)
> at
> org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:208)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> It may be because of Ambari Alert. Ambari Alert pings to the zookeeper port
> to do monitoring.
> We should use 'ruok' to monitor zookeepers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17306) Filter out MOTD logging from 'llapstatus' command in order to get the output which is JSON parsable.
[
https://issues.apache.org/jira/browse/AMBARI-17306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-17306:
-
Attachment: AMBARI-17306.patch
> Filter out MOTD logging from 'llapstatus' command in order to get the output
> which is JSON parsable.
>
>
> Key: AMBARI-17306
> URL: https://issues.apache.org/jira/browse/AMBARI-17306
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17306.patch
>
>
> Example of expected response which can be JSON parsed:
> *CASE A:*
> {code}
> {
> "amInfo" : {
> "appName" : "llap0",
> "appType" : "org-apache-slider",
> "appId" : "application_1466036628595_0010",
> "containerId" : "container_1466036628595_0010_01_01",
> "hostname" : "hostname",
> "amWebUrl" : "http://hostname:60865/;
> },
> "state" : "LAUNCHING",
> "originalConfigurationPath" :
> "hdfs://hostname:8020/user/hive/.slider/cluster/llap0/snapshot",
> "generatedConfigurationPath" :
> "hdfs://hostname:8020/user/hive/.slider/cluster/llap0/generated",
> "desiredInstances" : 1,
> "liveInstances" : 0,
> "appStartTime" : 1466123287309
> }
> {code}
> The same output with MOTD message:
> {code}
> This is MOTD message
> This is MOTD message1
> {
> "amInfo" : {
> "appName" : "llap0",
> "appType" : "org-apache-slider",
> "appId" : "application_1466036628595_0010",
> "containerId" : "container_1466036628595_0010_01_01",
> "hostname" : "hostname",
> "amWebUrl" : "http://hostname:60865/;
> },
> "state" : "LAUNCHING",
> "originalConfigurationPath" :
> "hdfs://hostname:8020/user/hive/.slider/cluster/llap0/snapshot",
> "generatedConfigurationPath" :
> "hdfs://hostname:8020/user/hive/.slider/cluster/llap0/generated",
> "desiredInstances" : 1,
> "liveInstances" : 0,
> "appStartTime" : 1466123287309
> }
> {code}
> Other scenario can be (eg: APP_NOTFOUND):
> *CASE B:*
> {code}
> This is MOTD message
> This is MOTD message1
> {
> "state" : "APP_NOT_FOUND"
> }
> {code}
> - We need to filter out extra lines initially added on top of JSON parseable
> string.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17306) Filter out MOTD logging from 'llapstatus' command in order to get the output which is JSON parsable.
[
https://issues.apache.org/jira/browse/AMBARI-17306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-17306:
-
Status: Patch Available (was: Open)
> Filter out MOTD logging from 'llapstatus' command in order to get the output
> which is JSON parsable.
>
>
> Key: AMBARI-17306
> URL: https://issues.apache.org/jira/browse/AMBARI-17306
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17306.patch
>
>
> Example of expected response which can be JSON parsed:
> *CASE A:*
> {code}
> {
> "amInfo" : {
> "appName" : "llap0",
> "appType" : "org-apache-slider",
> "appId" : "application_1466036628595_0010",
> "containerId" : "container_1466036628595_0010_01_01",
> "hostname" : "hostname",
> "amWebUrl" : "http://hostname:60865/;
> },
> "state" : "LAUNCHING",
> "originalConfigurationPath" :
> "hdfs://hostname:8020/user/hive/.slider/cluster/llap0/snapshot",
> "generatedConfigurationPath" :
> "hdfs://hostname:8020/user/hive/.slider/cluster/llap0/generated",
> "desiredInstances" : 1,
> "liveInstances" : 0,
> "appStartTime" : 1466123287309
> }
> {code}
> The same output with MOTD message:
> {code}
> This is MOTD message
> This is MOTD message1
> {
> "amInfo" : {
> "appName" : "llap0",
> "appType" : "org-apache-slider",
> "appId" : "application_1466036628595_0010",
> "containerId" : "container_1466036628595_0010_01_01",
> "hostname" : "hostname",
> "amWebUrl" : "http://hostname:60865/;
> },
> "state" : "LAUNCHING",
> "originalConfigurationPath" :
> "hdfs://hostname:8020/user/hive/.slider/cluster/llap0/snapshot",
> "generatedConfigurationPath" :
> "hdfs://hostname:8020/user/hive/.slider/cluster/llap0/generated",
> "desiredInstances" : 1,
> "liveInstances" : 0,
> "appStartTime" : 1466123287309
> }
> {code}
> Other scenario can be (eg: APP_NOTFOUND):
> *CASE B:*
> {code}
> This is MOTD message
> This is MOTD message1
> {
> "state" : "APP_NOT_FOUND"
> }
> {code}
> - We need to filter out extra lines initially added on top of JSON parseable
> string.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-17305) Local User not displaying in View All option in Ambari
Richard Zang created AMBARI-17305: - Summary: Local User not displaying in View All option in Ambari Key: AMBARI-17305 URL: https://issues.apache.org/jira/browse/AMBARI-17305 Project: Ambari Issue Type: Bug Components: ambari-admin Affects Versions: 2.4.0 Reporter: Richard Zang Assignee: Richard Zang Fix For: 2.4.0 >From Ambari dashboard, click on Admin -> Manage Ambari -> Users. You will see >message "No users to display". To see the local user, you will have to select >"Type" to "Local". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-17186) Tez View: Improve proxy logging
[ https://issues.apache.org/jira/browse/AMBARI-17186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan reopened AMBARI-17186: Reverted the commit from branch-2.4 and trunk, since this is causing a build break in Ambari. > Tez View: Improve proxy logging > --- > > Key: AMBARI-17186 > URL: https://issues.apache.org/jira/browse/AMBARI-17186 > Project: Ambari > Issue Type: Bug >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17186.1.patch, AMBARI-17186.2.patch > > > More log messages would help us to debug EARs faster. > # Add error log when configuration fetch fails. > # Add debug log when request proxying / redirection succeed > # Add error log when request proxying / redirection fails > With effect from AMBARI-14084, each view would have separate log file. > - For Tez view that is /var/log/ambari-server/tez-view/tez-view.log. > - Debug log would be logged only when the debug mode is enabled. (Set > log4j.logger.org.apache.ambari.view.tez=DEBUG,tezView in > view.log4j.properties for the same) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17200) Tez, Pig, Hive, MapReduce service checks will fail on non standard queue names
[
https://issues.apache.org/jira/browse/AMBARI-17200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15336952#comment-15336952
]
Hadoop QA commented on AMBARI-17200:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12811349/AMBARI-17200.patch.2
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 5 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7413//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7413//console
This message is automatically generated.
> Tez, Pig, Hive, MapReduce service checks will fail on non standard queue names
> --
>
> Key: AMBARI-17200
> URL: https://issues.apache.org/jira/browse/AMBARI-17200
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17200.patch, AMBARI-17200.patch.1,
> AMBARI-17200.patch.2
>
>
> If user will change queue names in a way when default queue will be missing -
> Tez, Hive and Pig service checks will fail coz no default queue found
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17303) [Grafana] Updated dashboards
[
https://issues.apache.org/jira/browse/AMBARI-17303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15337254#comment-15337254
]
Hadoop QA commented on AMBARI-17303:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12811467/AMBARI-17303.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7416//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7416//console
This message is automatically generated.
> [Grafana] Updated dashboards
>
>
> Key: AMBARI-17303
> URL: https://issues.apache.org/jira/browse/AMBARI-17303
> Project: Ambari
> Issue Type: Task
> Components: ambari-metrics
>Affects Versions: ambari-2.4.0
>Reporter: Prajwal Rao
>Assignee: Prajwal Rao
>Priority: Critical
> Fix For: ambari-2.4.0
>
> Attachments: AMBARI-17303.patch
>
>
> Updated the following dashboards
> - hbase-misc - (topN)
> - hbase-regionservers - (topN)
> - hbase-tables - (added how-to enable)
> - hbase-users - (added how-to enable)
> - hdfs-datanodes - (topN)
> - kafka-hosts - (topN)
> - yarn-nodemanagers - (topN)
> - system-servers - (topN)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17186) Tez View: Improve proxy logging
[ https://issues.apache.org/jira/browse/AMBARI-17186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-17186: --- Affects Version/s: (was: 2.4.0) > Tez View: Improve proxy logging > --- > > Key: AMBARI-17186 > URL: https://issues.apache.org/jira/browse/AMBARI-17186 > Project: Ambari > Issue Type: Bug >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17186.1.patch, AMBARI-17186.2.patch > > > More log messages would help us to debug EARs faster. > # Add error log when configuration fetch fails. > # Add debug log when request proxying / redirection succeed > # Add error log when request proxying / redirection fails > With effect from AMBARI-14084, each view would have separate log file. > - For Tez view that is /var/log/ambari-server/tez-view/tez-view.log. > - Debug log would be logged only when the debug mode is enabled. (Set > log4j.logger.org.apache.ambari.view.tez=DEBUG,tezView in > view.log4j.properties for the same) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17186) Tez View: Improve proxy logging
[ https://issues.apache.org/jira/browse/AMBARI-17186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-17186: --- Affects Version/s: 2.4.0 > Tez View: Improve proxy logging > --- > > Key: AMBARI-17186 > URL: https://issues.apache.org/jira/browse/AMBARI-17186 > Project: Ambari > Issue Type: Bug >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17186.1.patch, AMBARI-17186.2.patch > > > More log messages would help us to debug EARs faster. > # Add error log when configuration fetch fails. > # Add debug log when request proxying / redirection succeed > # Add error log when request proxying / redirection fails > With effect from AMBARI-14084, each view would have separate log file. > - For Tez view that is /var/log/ambari-server/tez-view/tez-view.log. > - Debug log would be logged only when the debug mode is enabled. (Set > log4j.logger.org.apache.ambari.view.tez=DEBUG,tezView in > view.log4j.properties for the same) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17303) [Grafana] Updated dashboards
[ https://issues.apache.org/jira/browse/AMBARI-17303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-17303: - Issue Type: Task (was: Bug) > [Grafana] Updated dashboards > > > Key: AMBARI-17303 > URL: https://issues.apache.org/jira/browse/AMBARI-17303 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: ambari-2.4.0 >Reporter: Prajwal Rao >Assignee: Prajwal Rao >Priority: Critical > Fix For: ambari-2.4.0 > > Attachments: AMBARI-17303.patch > > > Updated the following dashboards > - hbase-misc - (topN) > - hbase-regionservers - (topN) > - hbase-tables - (added how-to enable) > - hbase-users - (added how-to enable) > - hdfs-datanodes - (topN) > - kafka-hosts - (topN) > - yarn-nodemanagers - (topN) > - system-servers - (topN) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17299) Ambari Metrics service check failed exceed timeout
[
https://issues.apache.org/jira/browse/AMBARI-17299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-17299:
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.4
> Ambari Metrics service check failed exceed timeout
> --
>
> Key: AMBARI-17299
> URL: https://issues.apache.org/jira/browse/AMBARI-17299
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17299.patch
>
>
> Service check failed stderr:
> {noformat}
> Python script has been killed due to timeout after waiting 600 secs
> {noformat}
> No phoenix-server.jar in /usr/lib/ams-hbase/lib/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
