[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Attachment: AMBARI-18423_1.patch > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18423.patch, AMBARI-18423_1.patch, > create_alert_notification.png, edit_alert_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP in web client. > This patch aims to support another notification type:ALERT_SCRIPT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Attachment: (was: AMBARI-18423_01.patch) > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18423.patch, create_alert_notification.png, > edit_alert_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP in web client. > This patch aims to support another notification type:ALERT_SCRIPT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Attachment: AMBARI-18423_01.patch > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18423.patch, AMBARI-18423_01.patch, > create_alert_notification.png, edit_alert_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP in web client. > This patch aims to support another notification type:ALERT_SCRIPT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18576) When multiple requests are running, aborting any will incorrectly abort all requests instead the desired one
[ https://issues.apache.org/jira/browse/AMBARI-18576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15570464#comment-15570464 ] Hudson commented on AMBARI-18576: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5793 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5793/]) AMBARI-18576. When multiple requests are running, aborting any will (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2131466610b41af761fd1a105312c6553685c5ac]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/StageDAO.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/StageEntity.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionDBAccessor.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionScheduler.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/actionmanager/TestActionScheduler.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionDBAccessorImpl.java > When multiple requests are running, aborting any will incorrectly abort all > requests instead the desired one > > > Key: AMBARI-18576 > URL: https://issues.apache.org/jira/browse/AMBARI-18576 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Critical > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18576.branch-2.5.patch, AMBARI-18576.trunk.patch > > > STR: > * Install Ambari 2.4.0.1 with any HDP stack (e.g., 2.5) and HDFS, YARN, ZK > * Run multiple commands in parallel (such as service checks) > * Attempt to abort any one of them > Instead of aborting just the desired one, it will abort all requests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18576) When multiple requests are running, aborting any will incorrectly abort all requests instead the desired one
[ https://issues.apache.org/jira/browse/AMBARI-18576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15570374#comment-15570374 ] Hudson commented on AMBARI-18576: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #140 (See [https://builds.apache.org/job/Ambari-branch-2.5/140/]) AMBARI-18576. When multiple requests are running, aborting any will (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0d6c7729c5088ade492d96f9edcf6275078f0c8b]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionDBAccessorImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/StageDAO.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionDBAccessor.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionScheduler.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/StageEntity.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/actionmanager/TestActionScheduler.java > When multiple requests are running, aborting any will incorrectly abort all > requests instead the desired one > > > Key: AMBARI-18576 > URL: https://issues.apache.org/jira/browse/AMBARI-18576 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Critical > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18576.branch-2.5.patch, AMBARI-18576.trunk.patch > > > STR: > * Install Ambari 2.4.0.1 with any HDP stack (e.g., 2.5) and HDFS, YARN, ZK > * Run multiple commands in parallel (such as service checks) > * Attempt to abort any one of them > Instead of aborting just the desired one, it will abort all requests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17636) Service Configs page: can't see all config versions in dropdown
[ https://issues.apache.org/jira/browse/AMBARI-17636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-17636: Status: Patch Available (was: Open) > Service Configs page: can't see all config versions in dropdown > --- > > Key: AMBARI-17636 > URL: https://issues.apache.org/jira/browse/AMBARI-17636 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-17636.v0.patch, AMBARI-17636.v3.patch, > AMBARI-17636.v4.patch, AMBARI-17636.v5.patch, AMBARI-17636.v6.patch, > bugfix.gif > > > * Go to Service->Configs page (that have more than ~ 30 versions) > * Open versions dropdown > *Result:* > Number of visible versions limited by window height. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18575) Fix for improving time taken by 'ExecutionScheduleManagerTest' and 'UpgradeCatalog221Test' java tests.
[ https://issues.apache.org/jira/browse/AMBARI-18575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15570375#comment-15570375 ] Hudson commented on AMBARI-18575: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #140 (See [https://builds.apache.org/job/Ambari-branch-2.5/140/]) AMBARI-18575. Fix for improving time taken by (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4512f5525d129bdd4f73b68dfa139631d0368c35]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/scheduler/ExecutionScheduleManagerTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog221Test.java > Fix for improving time taken by 'ExecutionScheduleManagerTest' and > 'UpgradeCatalog221Test' java tests. > -- > > Key: AMBARI-18575 > URL: https://issues.apache.org/jira/browse/AMBARI-18575 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.5.0, 2.4.2 > > Attachments: AMBARI-18575.patch > > > Current time taken: > ||Test||Count||Time (s)|| > |org.apache.ambari.server.upgrade.UpgradeCatalog221Test |13|36.586| > |org.apache.ambari.server.scheduler.ExecutionScheduleManagerTest|9|30.685| > Initially reported as part of test improvements (along with other tests) in > BUG : BUG-65777 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17636) Service Configs page: can't see all config versions in dropdown
[ https://issues.apache.org/jira/browse/AMBARI-17636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-17636: Status: Open (was: Patch Available) > Service Configs page: can't see all config versions in dropdown > --- > > Key: AMBARI-17636 > URL: https://issues.apache.org/jira/browse/AMBARI-17636 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-17636.v0.patch, AMBARI-17636.v3.patch, > AMBARI-17636.v4.patch, AMBARI-17636.v5.patch, AMBARI-17636.v6.patch, > bugfix.gif > > > * Go to Service->Configs page (that have more than ~ 30 versions) > * Open versions dropdown > *Result:* > Number of visible versions limited by window height. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17636) Service Configs page: can't see all config versions in dropdown
[ https://issues.apache.org/jira/browse/AMBARI-17636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-17636: Attachment: AMBARI-17636.v6.patch > Service Configs page: can't see all config versions in dropdown > --- > > Key: AMBARI-17636 > URL: https://issues.apache.org/jira/browse/AMBARI-17636 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-17636.v0.patch, AMBARI-17636.v3.patch, > AMBARI-17636.v4.patch, AMBARI-17636.v5.patch, AMBARI-17636.v6.patch, > bugfix.gif > > > * Go to Service->Configs page (that have more than ~ 30 versions) > * Open versions dropdown > *Result:* > Number of visible versions limited by window height. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18566) Installer wizard-> Select Versions page: Selecting Red Hat Satellite option and clicking next button makes wizard stuck
[ https://issues.apache.org/jira/browse/AMBARI-18566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15570244#comment-15570244 ] Hudson commented on AMBARI-18566: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5792 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5792/]) AMBARI-18566 Installer wizard-> Select Versions page: Selecting Red Hat (zhewang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2709304c50a934679069c2ac63e1dfe64e7dfc3c]) * (edit) ambari-web/app/views/wizard/step1_view.js * (edit) ambari-web/app/controllers/installer.js > Installer wizard-> Select Versions page: Selecting Red Hat Satellite option > and clicking next button makes wizard stuck > --- > > Key: AMBARI-18566 > URL: https://issues.apache.org/jira/browse/AMBARI-18566 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18566.v0.patch, AMBARI-18566.v1.patch > > > *STR:* > # Got to select versions page > # Choose "Use Local Repository" option and then choose "Use RedHat > Satellite/Spacewalk" option > # Next button will get enabled. click on next button. > *Expected Result:* wizard goes to next page > *Actual Result:* On clicking next button, next button gets disabled and > wizard does not go to next page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18355) Introduce conditional dependencies in stack defition to handle blueprint validation gracefully
[
https://issues.apache.org/jira/browse/AMBARI-18355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15570182#comment-15570182
]
Hadoop QA commented on AMBARI-18355:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12832980/AMBARI-18355_v7.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:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8856//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8856//console
This message is automatically generated.
> Introduce conditional dependencies in stack defition to handle blueprint
> validation gracefully
> --
>
> Key: AMBARI-18355
> URL: https://issues.apache.org/jira/browse/AMBARI-18355
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-18355.patch, AMBARI-18355_v4.patch,
> AMBARI-18355_v5.patch, AMBARI-18355_v6.patch, AMBARI-18355_v7.patch, Adding
> Conditional Dependencies.pdf
>
>
> Currently stack definitions do not list conditional dependencies, adding
> those to the stack definitions would make it easy to validate errors in case
> of blueprint deployment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18575) Fix for improving time taken by 'ExecutionScheduleManagerTest' and 'UpgradeCatalog221Test' java tests.
[
https://issues.apache.org/jira/browse/AMBARI-18575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15570147#comment-15570147
]
Swapan Shridhar commented on AMBARI-18575:
--
*commits:*
*trunk:*
{code}
commit 911deb744485aa0366aad168c98566cf6381d4cc
Author: Swapan Shridhar
Date: Tue Oct 11 16:09:00 2016 -0700
AMBARI-18575. Fix for improving time taken by
'ExecutionScheduleManagerTest' and 'UpgradeCatalog221Test' java tests.
{code}
*branch-2.4:*
{code}
commit fdc5bd3fdf23b2035a27648d2db20e22c2159a0b
Author: Swapan Shridhar
Date: Wed Oct 12 15:51:26 2016 -0700
AMBARI-18575. Fix for improving time taken by
'ExecutionScheduleManagerTest' and 'UpgradeCatalog221Test' java tests.
{code}
*branch-2.5:*
{code}
commit 4512f5525d129bdd4f73b68dfa139631d0368c35
Author: Swapan Shridhar
Date: Tue Oct 11 16:09:00 2016 -0700
AMBARI-18575. Fix for improving time taken by
'ExecutionScheduleManagerTest' and 'UpgradeCatalog221Test' java tests.
{code}
> Fix for improving time taken by 'ExecutionScheduleManagerTest' and
> 'UpgradeCatalog221Test' java tests.
> --
>
> Key: AMBARI-18575
> URL: https://issues.apache.org/jira/browse/AMBARI-18575
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-18575.patch
>
>
> Current time taken:
> ||Test||Count||Time (s)||
> |org.apache.ambari.server.upgrade.UpgradeCatalog221Test |13|36.586|
> |org.apache.ambari.server.scheduler.ExecutionScheduleManagerTest|9|30.685|
> Initially reported as part of test improvements (along with other tests) in
> BUG : BUG-65777
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18575) Fix for improving time taken by 'ExecutionScheduleManagerTest' and 'UpgradeCatalog221Test' java tests.
[ https://issues.apache.org/jira/browse/AMBARI-18575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-18575: - Resolution: Fixed Status: Resolved (was: Patch Available) > Fix for improving time taken by 'ExecutionScheduleManagerTest' and > 'UpgradeCatalog221Test' java tests. > -- > > Key: AMBARI-18575 > URL: https://issues.apache.org/jira/browse/AMBARI-18575 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.5.0, 2.4.2 > > Attachments: AMBARI-18575.patch > > > Current time taken: > ||Test||Count||Time (s)|| > |org.apache.ambari.server.upgrade.UpgradeCatalog221Test |13|36.586| > |org.apache.ambari.server.scheduler.ExecutionScheduleManagerTest|9|30.685| > Initially reported as part of test improvements (along with other tests) in > BUG : BUG-65777 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18576) When multiple requests are running, aborting any will incorrectly abort all requests instead the desired one
[ https://issues.apache.org/jira/browse/AMBARI-18576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18576: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk, commit 2131466610b41af761fd1a105312c6553685c5ac branch-2.5, commit 0d6c7729c5088ade492d96f9edcf6275078f0c8b > When multiple requests are running, aborting any will incorrectly abort all > requests instead the desired one > > > Key: AMBARI-18576 > URL: https://issues.apache.org/jira/browse/AMBARI-18576 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Critical > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18576.branch-2.5.patch, AMBARI-18576.trunk.patch > > > STR: > * Install Ambari 2.4.0.1 with any HDP stack (e.g., 2.5) and HDFS, YARN, ZK > * Run multiple commands in parallel (such as service checks) > * Attempt to abort any one of them > Instead of aborting just the desired one, it will abort all requests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18380) For rolling upgrade of Kafka 0.10.0.1 we need to configs for backward compatibility
[
https://issues.apache.org/jira/browse/AMBARI-18380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-18380:
-
Assignee: (was: Alejandro Fernandez)
> For rolling upgrade of Kafka 0.10.0.1 we need to configs for backward
> compatibility
>
>
> Key: AMBARI-18380
> URL: https://issues.apache.org/jira/browse/AMBARI-18380
> Project: Ambari
> Issue Type: Bug
>Reporter: Sriharsha Chintalapani
>Priority: Blocker
> Fix For: 2.4.2
>
>
> following properties need to be set
> {code}
> inter.broker.protocol.version=0.9.0.0
> log.message.format.version=0.9.0.0
> {code}
> after upgrade is done we should delte the inter.broker.protocol.version.
> Users should remove log.message.format.version once they update their clients.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18566) Installer wizard-> Select Versions page: Selecting Red Hat Satellite option and clicking next button makes wizard stuck
[ https://issues.apache.org/jira/browse/AMBARI-18566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15570081#comment-15570081 ] Hudson commented on AMBARI-18566: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #139 (See [https://builds.apache.org/job/Ambari-branch-2.5/139/]) AMBARI-18566 Installer wizard-> Select Versions page: Selecting Red Hat (zhewang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2355ee6c47f2116fa5b8150b658f153e3e41ec63]) * (edit) ambari-web/app/views/wizard/step1_view.js * (edit) ambari-web/app/controllers/installer.js > Installer wizard-> Select Versions page: Selecting Red Hat Satellite option > and clicking next button makes wizard stuck > --- > > Key: AMBARI-18566 > URL: https://issues.apache.org/jira/browse/AMBARI-18566 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18566.v0.patch, AMBARI-18566.v1.patch > > > *STR:* > # Got to select versions page > # Choose "Use Local Repository" option and then choose "Use RedHat > Satellite/Spacewalk" option > # Next button will get enabled. click on next button. > *Expected Result:* wizard goes to next page > *Actual Result:* On clicking next button, next button gets disabled and > wizard does not go to next page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18575) Fix for improving time taken by 'ExecutionScheduleManagerTest' and 'UpgradeCatalog221Test' java tests.
[ https://issues.apache.org/jira/browse/AMBARI-18575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15570015#comment-15570015 ] Hudson commented on AMBARI-18575: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5791 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5791/]) AMBARI-18575. Fix for improving time taken by (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=911deb744485aa0366aad168c98566cf6381d4cc]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog221Test.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/scheduler/ExecutionScheduleManagerTest.java > Fix for improving time taken by 'ExecutionScheduleManagerTest' and > 'UpgradeCatalog221Test' java tests. > -- > > Key: AMBARI-18575 > URL: https://issues.apache.org/jira/browse/AMBARI-18575 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.5.0, 2.4.2 > > Attachments: AMBARI-18575.patch > > > Current time taken: > ||Test||Count||Time (s)|| > |org.apache.ambari.server.upgrade.UpgradeCatalog221Test |13|36.586| > |org.apache.ambari.server.scheduler.ExecutionScheduleManagerTest|9|30.685| > Initially reported as part of test improvements (along with other tests) in > BUG : BUG-65777 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18355) Introduce conditional dependencies in stack defition to handle blueprint validation gracefully
[ https://issues.apache.org/jira/browse/AMBARI-18355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-18355: --- Status: Patch Available (was: In Progress) > Introduce conditional dependencies in stack defition to handle blueprint > validation gracefully > -- > > Key: AMBARI-18355 > URL: https://issues.apache.org/jira/browse/AMBARI-18355 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-18355.patch, AMBARI-18355_v4.patch, > AMBARI-18355_v5.patch, AMBARI-18355_v6.patch, AMBARI-18355_v7.patch, Adding > Conditional Dependencies.pdf > > > Currently stack definitions do not list conditional dependencies, adding > those to the stack definitions would make it easy to validate errors in case > of blueprint deployment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18355) Introduce conditional dependencies in stack defition to handle blueprint validation gracefully
[ https://issues.apache.org/jira/browse/AMBARI-18355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-18355: --- Attachment: AMBARI-18355_v7.patch > Introduce conditional dependencies in stack defition to handle blueprint > validation gracefully > -- > > Key: AMBARI-18355 > URL: https://issues.apache.org/jira/browse/AMBARI-18355 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-18355.patch, AMBARI-18355_v4.patch, > AMBARI-18355_v5.patch, AMBARI-18355_v6.patch, AMBARI-18355_v7.patch, Adding > Conditional Dependencies.pdf > > > Currently stack definitions do not list conditional dependencies, adding > those to the stack definitions would make it easy to validate errors in case > of blueprint deployment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18355) Introduce conditional dependencies in stack defition to handle blueprint validation gracefully
[ https://issues.apache.org/jira/browse/AMBARI-18355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-18355: --- Status: Open (was: Patch Available) > Introduce conditional dependencies in stack defition to handle blueprint > validation gracefully > -- > > Key: AMBARI-18355 > URL: https://issues.apache.org/jira/browse/AMBARI-18355 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-18355.patch, AMBARI-18355_v4.patch, > AMBARI-18355_v5.patch, AMBARI-18355_v6.patch, Adding Conditional > Dependencies.pdf > > > Currently stack definitions do not list conditional dependencies, adding > those to the stack definitions would make it easy to validate errors in case > of blueprint deployment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18576) When multiple requests are running, aborting any will incorrectly abort all requests instead the desired one
[ https://issues.apache.org/jira/browse/AMBARI-18576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18576: - Status: Open (was: Patch Available) > When multiple requests are running, aborting any will incorrectly abort all > requests instead the desired one > > > Key: AMBARI-18576 > URL: https://issues.apache.org/jira/browse/AMBARI-18576 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Critical > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18576.branch-2.5.patch, AMBARI-18576.trunk.patch > > > STR: > * Install Ambari 2.4.0.1 with any HDP stack (e.g., 2.5) and HDFS, YARN, ZK > * Run multiple commands in parallel (such as service checks) > * Attempt to abort any one of them > Instead of aborting just the desired one, it will abort all requests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18576) When multiple requests are running, aborting any will incorrectly abort all requests instead the desired one
[ https://issues.apache.org/jira/browse/AMBARI-18576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18576: - Attachment: AMBARI-18576.branch-2.5.patch AMBARI-18576.trunk.patch > When multiple requests are running, aborting any will incorrectly abort all > requests instead the desired one > > > Key: AMBARI-18576 > URL: https://issues.apache.org/jira/browse/AMBARI-18576 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Critical > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18576.branch-2.5.patch, AMBARI-18576.trunk.patch > > > STR: > * Install Ambari 2.4.0.1 with any HDP stack (e.g., 2.5) and HDFS, YARN, ZK > * Run multiple commands in parallel (such as service checks) > * Attempt to abort any one of them > Instead of aborting just the desired one, it will abort all requests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18576) When multiple requests are running, aborting any will incorrectly abort all requests instead the desired one
[ https://issues.apache.org/jira/browse/AMBARI-18576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18576: - Status: Patch Available (was: Open) > When multiple requests are running, aborting any will incorrectly abort all > requests instead the desired one > > > Key: AMBARI-18576 > URL: https://issues.apache.org/jira/browse/AMBARI-18576 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Critical > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18576.branch-2.5.patch, AMBARI-18576.trunk.patch > > > STR: > * Install Ambari 2.4.0.1 with any HDP stack (e.g., 2.5) and HDFS, YARN, ZK > * Run multiple commands in parallel (such as service checks) > * Attempt to abort any one of them > Instead of aborting just the desired one, it will abort all requests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18576) When multiple requests are running, aborting any will incorrectly abort all requests instead the desired one
[ https://issues.apache.org/jira/browse/AMBARI-18576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18576: - Attachment: (was: AMBARI-18576.branch-2.5.patch) > When multiple requests are running, aborting any will incorrectly abort all > requests instead the desired one > > > Key: AMBARI-18576 > URL: https://issues.apache.org/jira/browse/AMBARI-18576 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Critical > Fix For: trunk, 2.5.0 > > > STR: > * Install Ambari 2.4.0.1 with any HDP stack (e.g., 2.5) and HDFS, YARN, ZK > * Run multiple commands in parallel (such as service checks) > * Attempt to abort any one of them > Instead of aborting just the desired one, it will abort all requests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18576) When multiple requests are running, aborting any will incorrectly abort all requests instead the desired one
[ https://issues.apache.org/jira/browse/AMBARI-18576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18576: - Attachment: (was: AMBARI-18576.trunk.patch) > When multiple requests are running, aborting any will incorrectly abort all > requests instead the desired one > > > Key: AMBARI-18576 > URL: https://issues.apache.org/jira/browse/AMBARI-18576 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Critical > Fix For: trunk, 2.5.0 > > > STR: > * Install Ambari 2.4.0.1 with any HDP stack (e.g., 2.5) and HDFS, YARN, ZK > * Run multiple commands in parallel (such as service checks) > * Attempt to abort any one of them > Instead of aborting just the desired one, it will abort all requests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18566) Installer wizard-> Select Versions page: Selecting Red Hat Satellite option and clicking next button makes wizard stuck
[ https://issues.apache.org/jira/browse/AMBARI-18566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18566: Resolution: Fixed Status: Resolved (was: Patch Available) Patch committed to trunk, branch-2.4 and branch-2.5 2709304c50a934679069c2ac63e1dfe64e7dfc3c > Installer wizard-> Select Versions page: Selecting Red Hat Satellite option > and clicking next button makes wizard stuck > --- > > Key: AMBARI-18566 > URL: https://issues.apache.org/jira/browse/AMBARI-18566 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18566.v0.patch, AMBARI-18566.v1.patch > > > *STR:* > # Got to select versions page > # Choose "Use Local Repository" option and then choose "Use RedHat > Satellite/Spacewalk" option > # Next button will get enabled. click on next button. > *Expected Result:* wizard goes to next page > *Actual Result:* On clicking next button, next button gets disabled and > wizard does not go to next page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18579) Grafana fails to start after deployment
[ https://issues.apache.org/jira/browse/AMBARI-18579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569801#comment-15569801 ] Hudson commented on AMBARI-18579: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #138 (See [https://builds.apache.org/job/Ambari-branch-2.5/138/]) AMBARI-18579. Grafana fails to start after deployment (aonishuk) (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f5df03a9e1b50c924e5ca2ca31b082ef96b2a4b6]) * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/default_ams_embedded.json * (edit) ambari-server/src/test/python/stacks/2.0.6/AMBARI_METRICS/test_metrics_grafana.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params_linux.py > Grafana fails to start after deployment > --- > > Key: AMBARI-18579 > URL: https://issues.apache.org/jira/browse/AMBARI-18579 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.2 > > Attachments: AMBARI-18579.patch > > > Noticed this issue in Ambari system tests clusters that run on YCloud, that > Grafana fails to start after deployment with the below error > > > > "stderr" : "Traceback (most recent call last):\n File > \"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py\", > line 67, in \nAmsGrafana().execute()\n File > \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\", > line 280, in execute\nmethod(env)\n File > \"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py\", > line 46, in start\nuser=params.ams_user\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line > 155, in __init__\nself.env.run()\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", > line 160, in run\nself.run_action(resource, action)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", > line 124, in run_action\nprovider_action()\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\", > line 273, in action_run\ntries=self.resource.tries, > try_sleep=self.resource.try_sleep)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line > 71, in inner\nresult = function(command, **kwargs)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line > 93, in checked_call\ntries=tries, try_sleep=try_sleep)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line > 141, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line > 294, in _call\nraise > Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of > '/usr/sbin/ambari-metrics-grafana start' returned 1. Hortonworks > #\nThis is MOTD message, added for testing in qe infra\nStarting > Ambari Metrics Grafana: FAILED", > > > Please find the artifacts for the run [here](http://qelog.hortonworks.com/log > /nat-yc-ambari-2-4-2-0-amb-r7-dmyu-ambari-config-6/test-logs/ambari-config/art > ifacts/screenshots/com.hw.ambari.ui.tests.installer.InstallHadoop/install/_8_2 > 3_23_7_Component__Phoenix_Query_Server__is_not__STARTED__on_host__ctr_e45_1475 > 874954070_0581_01_/lastAvailableRequests.txt) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18543) Option to enable request/access logs in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-18543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569791#comment-15569791 ] Hudson commented on AMBARI-18543: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5790 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5790/]) AMBARI-18543. Option to enable request/access logs in Ambari. (Amarnath (swagle: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=60dc240216bf54f35dfb5d3fea823ccceee2c9a4]) * (edit) ambari-server/conf/windows/ambari.properties * (edit) ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java > Option to enable request/access logs in Ambari > -- > > Key: AMBARI-18543 > URL: https://issues.apache.org/jira/browse/AMBARI-18543 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: amarnathreddy >Assignee: amarnathreddy >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-18543.patch > > > Currently there is no option to enable the request/access logs. these logs > would be useful for support team. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (AMBARI-18566) Installer wizard-> Select Versions page: Selecting Red Hat Satellite option and clicking next button makes wizard stuck
[ https://issues.apache.org/jira/browse/AMBARI-18566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18566: Comment: was deleted (was: The failure is not related to the patch.) > Installer wizard-> Select Versions page: Selecting Red Hat Satellite option > and clicking next button makes wizard stuck > --- > > Key: AMBARI-18566 > URL: https://issues.apache.org/jira/browse/AMBARI-18566 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18566.v0.patch, AMBARI-18566.v1.patch > > > *STR:* > # Got to select versions page > # Choose "Use Local Repository" option and then choose "Use RedHat > Satellite/Spacewalk" option > # Next button will get enabled. click on next button. > *Expected Result:* wizard goes to next page > *Actual Result:* On clicking next button, next button gets disabled and > wizard does not go to next page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18566) Installer wizard-> Select Versions page: Selecting Red Hat Satellite option and clicking next button makes wizard stuck
[ https://issues.apache.org/jira/browse/AMBARI-18566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569782#comment-15569782 ] Zhe (Joe) Wang commented on AMBARI-18566: - The failure is not related to the patch. > Installer wizard-> Select Versions page: Selecting Red Hat Satellite option > and clicking next button makes wizard stuck > --- > > Key: AMBARI-18566 > URL: https://issues.apache.org/jira/browse/AMBARI-18566 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18566.v0.patch, AMBARI-18566.v1.patch > > > *STR:* > # Got to select versions page > # Choose "Use Local Repository" option and then choose "Use RedHat > Satellite/Spacewalk" option > # Next button will get enabled. click on next button. > *Expected Result:* wizard goes to next page > *Actual Result:* On clicking next button, next button gets disabled and > wizard does not go to next page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18566) Installer wizard-> Select Versions page: Selecting Red Hat Satellite option and clicking next button makes wizard stuck
[ https://issues.apache.org/jira/browse/AMBARI-18566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569781#comment-15569781 ] Zhe (Joe) Wang commented on AMBARI-18566: - The failure is not related to the patch. > Installer wizard-> Select Versions page: Selecting Red Hat Satellite option > and clicking next button makes wizard stuck > --- > > Key: AMBARI-18566 > URL: https://issues.apache.org/jira/browse/AMBARI-18566 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18566.v0.patch, AMBARI-18566.v1.patch > > > *STR:* > # Got to select versions page > # Choose "Use Local Repository" option and then choose "Use RedHat > Satellite/Spacewalk" option > # Next button will get enabled. click on next button. > *Expected Result:* wizard goes to next page > *Actual Result:* On clicking next button, next button gets disabled and > wizard does not go to next page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18568) Hive shows restart indicator after RU
[ https://issues.apache.org/jira/browse/AMBARI-18568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569590#comment-15569590 ] Hudson commented on AMBARI-18568: - ABORTED: Integrated in Jenkins build Ambari-branch-2.5 #137 (See [https://builds.apache.org/job/Ambari-branch-2.5/137/]) AMBARI-18568. Hive shows restart indicator after RU (ncole) (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=52bb18496452128204b4802581f2332d1138f10a]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.5.xml > Hive shows restart indicator after RU > - > > Key: AMBARI-18568 > URL: https://issues.apache.org/jira/browse/AMBARI-18568 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18568.patch > > > After RU including Hive, the Hive service shows a restart indicator. This is > because orchestration sets up Hive Metastore FIRST, then HiveServer. > HiveServer has config changes for port. > Since metastore has already been restarted before the config change and > depends on hive-site, it reports having stale configs. > Change is only for HDP-2.5 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18532) Getting errors with max length 1000byte, when using Mysql db with charset UTF8
[
https://issues.apache.org/jira/browse/AMBARI-18532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569577#comment-15569577
]
Hadoop QA commented on AMBARI-18532:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12832946/AMBARI-18532_part2.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/8855//console
This message is automatically generated.
> Getting errors with max length 1000byte, when using Mysql db with charset UTF8
> --
>
> Key: AMBARI-18532
> URL: https://issues.apache.org/jira/browse/AMBARI-18532
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, ambari-upgrade
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18532.patch, AMBARI-18532_part2.patch
>
>
> ERROR 1071 (42000): Specified key was too long; max key length is 1000 bytes
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18581) Oozie start script ignores sysprep_skip_copy_oozie_share_lib_to_hdfs flag
[
https://issues.apache.org/jira/browse/AMBARI-18581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569572#comment-15569572
]
Hadoop QA commented on AMBARI-18581:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12832947/AMBARI-18581.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/8854//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8854//console
This message is automatically generated.
> Oozie start script ignores sysprep_skip_copy_oozie_share_lib_to_hdfs flag
> -
>
> Key: AMBARI-18581
> URL: https://issues.apache.org/jira/browse/AMBARI-18581
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-18581.patch
>
>
> Oozie service script never executes "sysprepped" branch, because it looks for
> sysprep_skip_copy_oozie_share_lib_to_hdfs flag in the wrong place.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18579) Grafana fails to start after deployment
[ https://issues.apache.org/jira/browse/AMBARI-18579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569569#comment-15569569 ] Hudson commented on AMBARI-18579: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5789 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5789/]) AMBARI-18579. Grafana fails to start after deployment (aonishuk) (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=5d007e248e24e02d4d8c5c818a1125830370936c]) * (edit) ambari-server/src/test/python/stacks/2.0.6/configs/default_ams_embedded.json * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params_linux.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py * (edit) ambari-server/src/test/python/stacks/2.0.6/AMBARI_METRICS/test_metrics_grafana.py > Grafana fails to start after deployment > --- > > Key: AMBARI-18579 > URL: https://issues.apache.org/jira/browse/AMBARI-18579 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.2 > > Attachments: AMBARI-18579.patch > > > Noticed this issue in Ambari system tests clusters that run on YCloud, that > Grafana fails to start after deployment with the below error > > > > "stderr" : "Traceback (most recent call last):\n File > \"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py\", > line 67, in \nAmsGrafana().execute()\n File > \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\", > line 280, in execute\nmethod(env)\n File > \"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py\", > line 46, in start\nuser=params.ams_user\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line > 155, in __init__\nself.env.run()\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", > line 160, in run\nself.run_action(resource, action)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", > line 124, in run_action\nprovider_action()\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\", > line 273, in action_run\ntries=self.resource.tries, > try_sleep=self.resource.try_sleep)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line > 71, in inner\nresult = function(command, **kwargs)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line > 93, in checked_call\ntries=tries, try_sleep=try_sleep)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line > 141, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line > 294, in _call\nraise > Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of > '/usr/sbin/ambari-metrics-grafana start' returned 1. Hortonworks > #\nThis is MOTD message, added for testing in qe infra\nStarting > Ambari Metrics Grafana: FAILED", > > > Please find the artifacts for the run [here](http://qelog.hortonworks.com/log > /nat-yc-ambari-2-4-2-0-amb-r7-dmyu-ambari-config-6/test-logs/ambari-config/art > ifacts/screenshots/com.hw.ambari.ui.tests.installer.InstallHadoop/install/_8_2 > 3_23_7_Component__Phoenix_Query_Server__is_not__STARTED__on_host__ctr_e45_1475 > 874954070_0581_01_/lastAvailableRequests.txt) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18431) Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes.
[ https://issues.apache.org/jira/browse/AMBARI-18431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-18431: Fix Version/s: 2.4.2 > Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes. > - > > Key: AMBARI-18431 > URL: https://issues.apache.org/jira/browse/AMBARI-18431 > Project: Ambari > Issue Type: Improvement >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani > Fix For: 2.4.2 > > Attachments: > 0001-Changed-topology-DAG-Fixed-Kafka-Spout-Lag-data-form.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18380) For rolling upgrade of Kafka 0.10.0.1 we need to configs for backward compatibility
[
https://issues.apache.org/jira/browse/AMBARI-18380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani updated AMBARI-18380:
Fix Version/s: 2.4.2
> For rolling upgrade of Kafka 0.10.0.1 we need to configs for backward
> compatibility
>
>
> Key: AMBARI-18380
> URL: https://issues.apache.org/jira/browse/AMBARI-18380
> Project: Ambari
> Issue Type: Bug
>Reporter: Sriharsha Chintalapani
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Fix For: 2.4.2
>
>
> following properties need to be set
> {code}
> inter.broker.protocol.version=0.9.0.0
> log.message.format.version=0.9.0.0
> {code}
> after upgrade is done we should delte the inter.broker.protocol.version.
> Users should remove log.message.format.version once they update their clients.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18380) For rolling upgrade of Kafka 0.10.0.1 we need to configs for backward compatibility
[
https://issues.apache.org/jira/browse/AMBARI-18380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani updated AMBARI-18380:
Assignee: Alejandro Fernandez (was: Sriharsha Chintalapani)
> For rolling upgrade of Kafka 0.10.0.1 we need to configs for backward
> compatibility
>
>
> Key: AMBARI-18380
> URL: https://issues.apache.org/jira/browse/AMBARI-18380
> Project: Ambari
> Issue Type: Bug
>Reporter: Sriharsha Chintalapani
>Assignee: Alejandro Fernandez
>Priority: Blocker
>
> following properties need to be set
> {code}
> inter.broker.protocol.version=0.9.0.0
> log.message.format.version=0.9.0.0
> {code}
> after upgrade is done we should delte the inter.broker.protocol.version.
> Users should remove log.message.format.version once they update their clients.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18380) For rolling upgrade of Kafka 0.10.0.1 we need to configs for backward compatibility
[
https://issues.apache.org/jira/browse/AMBARI-18380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569547#comment-15569547
]
Sriharsha Chintalapani commented on AMBARI-18380:
-
[~afernandez] appreciate if you take this up
> For rolling upgrade of Kafka 0.10.0.1 we need to configs for backward
> compatibility
>
>
> Key: AMBARI-18380
> URL: https://issues.apache.org/jira/browse/AMBARI-18380
> Project: Ambari
> Issue Type: Bug
>Reporter: Sriharsha Chintalapani
>Assignee: Alejandro Fernandez
>Priority: Blocker
>
> following properties need to be set
> {code}
> inter.broker.protocol.version=0.9.0.0
> log.message.format.version=0.9.0.0
> {code}
> after upgrade is done we should delte the inter.broker.protocol.version.
> Users should remove log.message.format.version once they update their clients.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18575) Fix for improving time taken by 'ExecutionScheduleManagerTest' and 'UpgradeCatalog221Test' java tests.
[ https://issues.apache.org/jira/browse/AMBARI-18575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569448#comment-15569448 ] Swapan Shridhar commented on AMBARI-18575: -- After the fix, improved timings are as follows: *ExecutionScheduleManagerTest :* ||After Improvements|| Before Improvement|| |~11.3 secs| ~30.6 secs| *UpgradeCatalog221Test :* ||After Improvements|| Before Improvement|| |~11.0 secs| ~30.5 secs| > Fix for improving time taken by 'ExecutionScheduleManagerTest' and > 'UpgradeCatalog221Test' java tests. > -- > > Key: AMBARI-18575 > URL: https://issues.apache.org/jira/browse/AMBARI-18575 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.5.0, 2.4.2 > > Attachments: AMBARI-18575.patch > > > Current time taken: > ||Test||Count||Time (s)|| > |org.apache.ambari.server.upgrade.UpgradeCatalog221Test |13|36.586| > |org.apache.ambari.server.scheduler.ExecutionScheduleManagerTest|9|30.685| > Initially reported as part of test improvements (along with other tests) in > BUG : BUG-65777 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18581) Oozie start script ignores sysprep_skip_copy_oozie_share_lib_to_hdfs flag
[ https://issues.apache.org/jira/browse/AMBARI-18581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-18581: --- Fix Version/s: 3.0.0 > Oozie start script ignores sysprep_skip_copy_oozie_share_lib_to_hdfs flag > - > > Key: AMBARI-18581 > URL: https://issues.apache.org/jira/browse/AMBARI-18581 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila > Fix For: 3.0.0, 2.5.0 > > Attachments: AMBARI-18581.patch > > > Oozie service script never executes "sysprepped" branch, because it looks for > sysprep_skip_copy_oozie_share_lib_to_hdfs flag in the wrong place. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18581) Oozie start script ignores sysprep_skip_copy_oozie_share_lib_to_hdfs flag
[ https://issues.apache.org/jira/browse/AMBARI-18581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-18581: --- Status: Patch Available (was: Open) > Oozie start script ignores sysprep_skip_copy_oozie_share_lib_to_hdfs flag > - > > Key: AMBARI-18581 > URL: https://issues.apache.org/jira/browse/AMBARI-18581 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila > Fix For: 3.0.0, 2.5.0 > > Attachments: AMBARI-18581.patch > > > Oozie service script never executes "sysprepped" branch, because it looks for > sysprep_skip_copy_oozie_share_lib_to_hdfs flag in the wrong place. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18581) Oozie start script ignores sysprep_skip_copy_oozie_share_lib_to_hdfs flag
[ https://issues.apache.org/jira/browse/AMBARI-18581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-18581: --- Attachment: AMBARI-18581.patch > Oozie start script ignores sysprep_skip_copy_oozie_share_lib_to_hdfs flag > - > > Key: AMBARI-18581 > URL: https://issues.apache.org/jira/browse/AMBARI-18581 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila > Fix For: 3.0.0, 2.5.0 > > Attachments: AMBARI-18581.patch > > > Oozie service script never executes "sysprepped" branch, because it looks for > sysprep_skip_copy_oozie_share_lib_to_hdfs flag in the wrong place. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-18532) Getting errors with max length 1000byte, when using Mysql db with charset UTF8
[ https://issues.apache.org/jira/browse/AMBARI-18532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi reopened AMBARI-18532: > Getting errors with max length 1000byte, when using Mysql db with charset UTF8 > -- > > Key: AMBARI-18532 > URL: https://issues.apache.org/jira/browse/AMBARI-18532 > Project: Ambari > Issue Type: Bug > Components: ambari-server, ambari-upgrade >Affects Versions: 2.4.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18532.patch, AMBARI-18532_part2.patch > > > ERROR 1071 (42000): Specified key was too long; max key length is 1000 bytes -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18532) Getting errors with max length 1000byte, when using Mysql db with charset UTF8
[ https://issues.apache.org/jira/browse/AMBARI-18532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18532: --- Attachment: AMBARI-18532_part2.patch > Getting errors with max length 1000byte, when using Mysql db with charset UTF8 > -- > > Key: AMBARI-18532 > URL: https://issues.apache.org/jira/browse/AMBARI-18532 > Project: Ambari > Issue Type: Bug > Components: ambari-server, ambari-upgrade >Affects Versions: 2.4.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18532.patch, AMBARI-18532_part2.patch > > > ERROR 1071 (42000): Specified key was too long; max key length is 1000 bytes -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18532) Getting errors with max length 1000byte, when using Mysql db with charset UTF8
[ https://issues.apache.org/jira/browse/AMBARI-18532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18532: --- Status: Patch Available (was: Reopened) > Getting errors with max length 1000byte, when using Mysql db with charset UTF8 > -- > > Key: AMBARI-18532 > URL: https://issues.apache.org/jira/browse/AMBARI-18532 > Project: Ambari > Issue Type: Bug > Components: ambari-server, ambari-upgrade >Affects Versions: 2.4.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18532.patch, AMBARI-18532_part2.patch > > > ERROR 1071 (42000): Specified key was too long; max key length is 1000 bytes -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18581) Oozie start script ignores sysprep_skip_copy_oozie_share_lib_to_hdfs flag
[
https://issues.apache.org/jira/browse/AMBARI-18581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569360#comment-15569360
]
Doroszlai, Attila commented on AMBARI-18581:
{noformat}
$ grep -r 'default("/configurations/cluster-env/'
ambari-server/src/main/resources | wc -l
22
$ grep -r 'default("/cluster-env/' ambari-server/src/main/resources | wc -l
1
{noformat}
> Oozie start script ignores sysprep_skip_copy_oozie_share_lib_to_hdfs flag
> -
>
> Key: AMBARI-18581
> URL: https://issues.apache.org/jira/browse/AMBARI-18581
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 2.5.0
>
>
> Oozie service script never executes "sysprepped" branch, because it looks for
> sysprep_skip_copy_oozie_share_lib_to_hdfs flag in the wrong place.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18579) Grafana fails to start after deployment
[ https://issues.apache.org/jira/browse/AMBARI-18579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18579: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 and branch-2.4 > Grafana fails to start after deployment > --- > > Key: AMBARI-18579 > URL: https://issues.apache.org/jira/browse/AMBARI-18579 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.2 > > Attachments: AMBARI-18579.patch > > > Noticed this issue in Ambari system tests clusters that run on YCloud, that > Grafana fails to start after deployment with the below error > > > > "stderr" : "Traceback (most recent call last):\n File > \"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py\", > line 67, in \nAmsGrafana().execute()\n File > \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\", > line 280, in execute\nmethod(env)\n File > \"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py\", > line 46, in start\nuser=params.ams_user\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line > 155, in __init__\nself.env.run()\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", > line 160, in run\nself.run_action(resource, action)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", > line 124, in run_action\nprovider_action()\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\", > line 273, in action_run\ntries=self.resource.tries, > try_sleep=self.resource.try_sleep)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line > 71, in inner\nresult = function(command, **kwargs)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line > 93, in checked_call\ntries=tries, try_sleep=try_sleep)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line > 141, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line > 294, in _call\nraise > Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of > '/usr/sbin/ambari-metrics-grafana start' returned 1. Hortonworks > #\nThis is MOTD message, added for testing in qe infra\nStarting > Ambari Metrics Grafana: FAILED", > > > Please find the artifacts for the run [here](http://qelog.hortonworks.com/log > /nat-yc-ambari-2-4-2-0-amb-r7-dmyu-ambari-config-6/test-logs/ambari-config/art > ifacts/screenshots/com.hw.ambari.ui.tests.installer.InstallHadoop/install/_8_2 > 3_23_7_Component__Phoenix_Query_Server__is_not__STARTED__on_host__ctr_e45_1475 > 874954070_0581_01_/lastAvailableRequests.txt) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18579) Grafana fails to start after deployment
[
https://issues.apache.org/jira/browse/AMBARI-18579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569346#comment-15569346
]
Hadoop QA commented on AMBARI-18579:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12832931/AMBARI-18579.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/8853//console
This message is automatically generated.
> Grafana fails to start after deployment
> ---
>
> Key: AMBARI-18579
> URL: https://issues.apache.org/jira/browse/AMBARI-18579
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.2
>
> Attachments: AMBARI-18579.patch
>
>
> Noticed this issue in Ambari system tests clusters that run on YCloud, that
> Grafana fails to start after deployment with the below error
>
>
>
> "stderr" : "Traceback (most recent call last):\n File
> \"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py\",
> line 67, in \nAmsGrafana().execute()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 280, in execute\nmethod(env)\n File
> \"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py\",
> line 46, in start\nuser=params.ams_user\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line
> 155, in __init__\nself.env.run()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 160, in run\nself.run_action(resource, action)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 124, in run_action\nprovider_action()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 273, in action_run\ntries=self.resource.tries,
> try_sleep=self.resource.try_sleep)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 71, in inner\nresult = function(command, **kwargs)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 93, in checked_call\ntries=tries, try_sleep=try_sleep)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 141, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 294, in _call\nraise
> Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of
> '/usr/sbin/ambari-metrics-grafana start' returned 1. Hortonworks
> #\nThis is MOTD message, added for testing in qe infra\nStarting
> Ambari Metrics Grafana: FAILED",
>
>
> Please find the artifacts for the run [here](http://qelog.hortonworks.com/log
> /nat-yc-ambari-2-4-2-0-amb-r7-dmyu-ambari-config-6/test-logs/ambari-config/art
> ifacts/screenshots/com.hw.ambari.ui.tests.installer.InstallHadoop/install/_8_2
> 3_23_7_Component__Phoenix_Query_Server__is_not__STARTED__on_host__ctr_e45_1475
> 874954070_0581_01_/lastAvailableRequests.txt)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18581) Oozie start script ignores sysprep_skip_copy_oozie_share_lib_to_hdfs flag
Doroszlai, Attila created AMBARI-18581: -- Summary: Oozie start script ignores sysprep_skip_copy_oozie_share_lib_to_hdfs flag Key: AMBARI-18581 URL: https://issues.apache.org/jira/browse/AMBARI-18581 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Doroszlai, Attila Assignee: Doroszlai, Attila Fix For: 2.5.0 Oozie service script never executes "sysprepped" branch, because it looks for sysprep_skip_copy_oozie_share_lib_to_hdfs flag in the wrong place. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18580) Delete host throws 500 Error with unique constraint violation
Myroslav Papirkovskyi created AMBARI-18580: -- Summary: Delete host throws 500 Error with unique constraint violation Key: AMBARI-18580 URL: https://issues.apache.org/jira/browse/AMBARI-18580 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.2.0 Reporter: Myroslav Papirkovskyi Assignee: Myroslav Papirkovskyi Priority: Critical Fix For: 2.4.2 Delete host request fails for blueprint deployed clusters in case when topology_host_request with empty hostname exists. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18543) Option to enable request/access logs in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-18543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569316#comment-15569316 ] amarnathreddy commented on AMBARI-18543: Code review request for the patch - https://reviews.apache.org/r/52583/ > Option to enable request/access logs in Ambari > -- > > Key: AMBARI-18543 > URL: https://issues.apache.org/jira/browse/AMBARI-18543 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: amarnathreddy >Assignee: amarnathreddy >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-18543.patch > > > Currently there is no option to enable the request/access logs. these logs > would be useful for support team. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18579) Grafana fails to start after deployment
[
https://issues.apache.org/jira/browse/AMBARI-18579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569286#comment-15569286
]
Andrew Onischuk commented on AMBARI-18579:
--
{noformat}
[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0
approved: 149 licence.
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Ambari Views .. SUCCESS [2.057s]
[INFO] Ambari Metrics Common . SUCCESS [1.299s]
[INFO] Ambari Server . SUCCESS [1:12.730s]
[INFO] Ambari Agent .. SUCCESS [11.955s]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1:28.933s
[INFO] Finished at: Wed Oct 12 20:11:45 EEST 2016
[INFO] Final Memory: 64M/1174M
[INFO]
{noformat}
> Grafana fails to start after deployment
> ---
>
> Key: AMBARI-18579
> URL: https://issues.apache.org/jira/browse/AMBARI-18579
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.2
>
> Attachments: AMBARI-18579.patch
>
>
> Noticed this issue in Ambari system tests clusters that run on YCloud, that
> Grafana fails to start after deployment with the below error
>
>
>
> "stderr" : "Traceback (most recent call last):\n File
> \"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py\",
> line 67, in \nAmsGrafana().execute()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 280, in execute\nmethod(env)\n File
> \"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py\",
> line 46, in start\nuser=params.ams_user\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line
> 155, in __init__\nself.env.run()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 160, in run\nself.run_action(resource, action)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 124, in run_action\nprovider_action()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 273, in action_run\ntries=self.resource.tries,
> try_sleep=self.resource.try_sleep)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 71, in inner\nresult = function(command, **kwargs)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 93, in checked_call\ntries=tries, try_sleep=try_sleep)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 141, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 294, in _call\nraise
> Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of
> '/usr/sbin/ambari-metrics-grafana start' returned 1. Hortonworks
> #\nThis is MOTD message, added for testing in qe infra\nStarting
> Ambari Metrics Grafana: FAILED",
>
>
> Please find the artifacts for the run [here](http://qelog.hortonworks.com/log
> /nat-yc-ambari-2-4-2-0-amb-r7-dmyu-ambari-config-6/test-logs/ambari-config/art
> ifacts/screenshots/com.hw.ambari.ui.tests.installer.InstallHadoop/install/_8_2
> 3_23_7_Component__Phoenix_Query_Server__is_not__STARTED__on_host__ctr_e45_1475
> 874954070_0581_01_/lastAvailableRequests.txt)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18579) Grafana fails to start after deployment
[ https://issues.apache.org/jira/browse/AMBARI-18579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569281#comment-15569281 ] Andrew Onischuk commented on AMBARI-18579: -- The patch was for branch-2.5 that's why it failed to apply. > Grafana fails to start after deployment > --- > > Key: AMBARI-18579 > URL: https://issues.apache.org/jira/browse/AMBARI-18579 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.2 > > Attachments: AMBARI-18579.patch > > > Noticed this issue in Ambari system tests clusters that run on YCloud, that > Grafana fails to start after deployment with the below error > > > > "stderr" : "Traceback (most recent call last):\n File > \"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py\", > line 67, in \nAmsGrafana().execute()\n File > \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\", > line 280, in execute\nmethod(env)\n File > \"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py\", > line 46, in start\nuser=params.ams_user\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line > 155, in __init__\nself.env.run()\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", > line 160, in run\nself.run_action(resource, action)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", > line 124, in run_action\nprovider_action()\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\", > line 273, in action_run\ntries=self.resource.tries, > try_sleep=self.resource.try_sleep)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line > 71, in inner\nresult = function(command, **kwargs)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line > 93, in checked_call\ntries=tries, try_sleep=try_sleep)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line > 141, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line > 294, in _call\nraise > Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of > '/usr/sbin/ambari-metrics-grafana start' returned 1. Hortonworks > #\nThis is MOTD message, added for testing in qe infra\nStarting > Ambari Metrics Grafana: FAILED", > > > Please find the artifacts for the run [here](http://qelog.hortonworks.com/log > /nat-yc-ambari-2-4-2-0-amb-r7-dmyu-ambari-config-6/test-logs/ambari-config/art > ifacts/screenshots/com.hw.ambari.ui.tests.installer.InstallHadoop/install/_8_2 > 3_23_7_Component__Phoenix_Query_Server__is_not__STARTED__on_host__ctr_e45_1475 > 874954070_0581_01_/lastAvailableRequests.txt) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18543) Option to enable request/access logs in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-18543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-18543: - Fix Version/s: (was: trnk) trunk > Option to enable request/access logs in Ambari > -- > > Key: AMBARI-18543 > URL: https://issues.apache.org/jira/browse/AMBARI-18543 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: amarnathreddy >Assignee: amarnathreddy >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-18543.patch > > > Currently there is no option to enable the request/access logs. these logs > would be useful for support team. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18543) Option to enable request/access logs in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-18543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569224#comment-15569224 ] amarnathreddy commented on AMBARI-18543: here is sample log. 0:0:0:0:0:0:0:1 - - [10/Oct/2016:19:08:43 +] "POST https://localhost:8441/agent/v1/heartbeat/c6407.ambari.apache.org HTTP/1.1" 200 167 "-" "-" 1 0:0:0:0:0:0:0:1 - - [10/Oct/2016:19:08:44 +] "POST https://localhost:8441/agent/v1/heartbeat/c6407.ambari.apache.org HTTP/1.1" 200 167 "-" "-" 2 192.168.64.1 - - [10/Oct/2016:19:08:44 +] "GET /api/v1/users/admin?fields=*,privileges/PrivilegeInfo/cluster_name,privileges/PrivilegeInfo/permission_name&_=1476126523432 HTTP/1.1" 200 0 "http://192.168.64.107:8080/"; "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36" 0 192.168.64.1 - - [10/Oct/2016:19:08:45 +] "GET /api/v1/users/admin/authorizations?fields=*&_=1476126523888 HTTP/1.1" 200 0 "http://192.168.64.107:8080/"; "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36" 0 192.168.64.1 - - [10/Oct/2016:19:08:45 +] "GET /font/fontawesome-webfont.woff?v=3.2.1 HTTP/1.1" 200 0 "http://192.168.64.107:8080/stylesheets/vendor.css"; "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36" 0 192.168.64.1 - - [10/Oct/2016:19:08:45 +] "GET /api/v1/settings/motd?_=1476126523980 HTTP/1.1" 200 0 "http://192.168.64.107:8080/"; "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36" 0 19 > Option to enable request/access logs in Ambari > -- > > Key: AMBARI-18543 > URL: https://issues.apache.org/jira/browse/AMBARI-18543 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: amarnathreddy >Assignee: amarnathreddy >Priority: Minor > Fix For: trnk > > Attachments: AMBARI-18543.patch > > > Currently there is no option to enable the request/access logs. these logs > would be useful for support team. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18579) Grafana fails to start after deployment
[
https://issues.apache.org/jira/browse/AMBARI-18579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569225#comment-15569225
]
Hadoop QA commented on AMBARI-18579:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12832931/AMBARI-18579.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/8852//console
This message is automatically generated.
> Grafana fails to start after deployment
> ---
>
> Key: AMBARI-18579
> URL: https://issues.apache.org/jira/browse/AMBARI-18579
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.2
>
> Attachments: AMBARI-18579.patch
>
>
> Noticed this issue in Ambari system tests clusters that run on YCloud, that
> Grafana fails to start after deployment with the below error
>
>
>
> "stderr" : "Traceback (most recent call last):\n File
> \"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py\",
> line 67, in \nAmsGrafana().execute()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 280, in execute\nmethod(env)\n File
> \"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py\",
> line 46, in start\nuser=params.ams_user\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line
> 155, in __init__\nself.env.run()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 160, in run\nself.run_action(resource, action)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 124, in run_action\nprovider_action()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 273, in action_run\ntries=self.resource.tries,
> try_sleep=self.resource.try_sleep)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 71, in inner\nresult = function(command, **kwargs)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 93, in checked_call\ntries=tries, try_sleep=try_sleep)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 141, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
> 294, in _call\nraise
> Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of
> '/usr/sbin/ambari-metrics-grafana start' returned 1. Hortonworks
> #\nThis is MOTD message, added for testing in qe infra\nStarting
> Ambari Metrics Grafana: FAILED",
>
>
> Please find the artifacts for the run [here](http://qelog.hortonworks.com/log
> /nat-yc-ambari-2-4-2-0-amb-r7-dmyu-ambari-config-6/test-logs/ambari-config/art
> ifacts/screenshots/com.hw.ambari.ui.tests.installer.InstallHadoop/install/_8_2
> 3_23_7_Component__Phoenix_Query_Server__is_not__STARTED__on_host__ctr_e45_1475
> 874954070_0581_01_/lastAvailableRequests.txt)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18579) Grafana fails to start after deployment
[ https://issues.apache.org/jira/browse/AMBARI-18579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18579: - Status: Patch Available (was: Open) > Grafana fails to start after deployment > --- > > Key: AMBARI-18579 > URL: https://issues.apache.org/jira/browse/AMBARI-18579 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.2 > > Attachments: AMBARI-18579.patch > > > Noticed this issue in Ambari system tests clusters that run on YCloud, that > Grafana fails to start after deployment with the below error > > > > "stderr" : "Traceback (most recent call last):\n File > \"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py\", > line 67, in \nAmsGrafana().execute()\n File > \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\", > line 280, in execute\nmethod(env)\n File > \"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py\", > line 46, in start\nuser=params.ams_user\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line > 155, in __init__\nself.env.run()\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", > line 160, in run\nself.run_action(resource, action)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", > line 124, in run_action\nprovider_action()\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\", > line 273, in action_run\ntries=self.resource.tries, > try_sleep=self.resource.try_sleep)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line > 71, in inner\nresult = function(command, **kwargs)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line > 93, in checked_call\ntries=tries, try_sleep=try_sleep)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line > 141, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line > 294, in _call\nraise > Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of > '/usr/sbin/ambari-metrics-grafana start' returned 1. Hortonworks > #\nThis is MOTD message, added for testing in qe infra\nStarting > Ambari Metrics Grafana: FAILED", > > > Please find the artifacts for the run [here](http://qelog.hortonworks.com/log > /nat-yc-ambari-2-4-2-0-amb-r7-dmyu-ambari-config-6/test-logs/ambari-config/art > ifacts/screenshots/com.hw.ambari.ui.tests.installer.InstallHadoop/install/_8_2 > 3_23_7_Component__Phoenix_Query_Server__is_not__STARTED__on_host__ctr_e45_1475 > 874954070_0581_01_/lastAvailableRequests.txt) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18579) Grafana fails to start after deployment
[ https://issues.apache.org/jira/browse/AMBARI-18579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18579: - Attachment: AMBARI-18579.patch > Grafana fails to start after deployment > --- > > Key: AMBARI-18579 > URL: https://issues.apache.org/jira/browse/AMBARI-18579 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.2 > > Attachments: AMBARI-18579.patch > > > Noticed this issue in Ambari system tests clusters that run on YCloud, that > Grafana fails to start after deployment with the below error > > > > "stderr" : "Traceback (most recent call last):\n File > \"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py\", > line 67, in \nAmsGrafana().execute()\n File > \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\", > line 280, in execute\nmethod(env)\n File > \"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py\", > line 46, in start\nuser=params.ams_user\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line > 155, in __init__\nself.env.run()\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", > line 160, in run\nself.run_action(resource, action)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", > line 124, in run_action\nprovider_action()\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\", > line 273, in action_run\ntries=self.resource.tries, > try_sleep=self.resource.try_sleep)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line > 71, in inner\nresult = function(command, **kwargs)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line > 93, in checked_call\ntries=tries, try_sleep=try_sleep)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line > 141, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line > 294, in _call\nraise > Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of > '/usr/sbin/ambari-metrics-grafana start' returned 1. Hortonworks > #\nThis is MOTD message, added for testing in qe infra\nStarting > Ambari Metrics Grafana: FAILED", > > > Please find the artifacts for the run [here](http://qelog.hortonworks.com/log > /nat-yc-ambari-2-4-2-0-amb-r7-dmyu-ambari-config-6/test-logs/ambari-config/art > ifacts/screenshots/com.hw.ambari.ui.tests.installer.InstallHadoop/install/_8_2 > 3_23_7_Component__Phoenix_Query_Server__is_not__STARTED__on_host__ctr_e45_1475 > 874954070_0581_01_/lastAvailableRequests.txt) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18578) Grafana fails to start after deployment
Andrew Onischuk created AMBARI-18578: Summary: Grafana fails to start after deployment Key: AMBARI-18578 URL: https://issues.apache.org/jira/browse/AMBARI-18578 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.4.2 Noticed this issue in Ambari system tests clusters that run on YCloud, that Grafana fails to start after deployment with the below error "stderr" : "Traceback (most recent call last):\n File \"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py\", line 67, in \nAmsGrafana().execute()\n File \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\", line 280, in execute\nmethod(env)\n File \"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py\", line 46, in start\nuser=params.ams_user\n File \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line 155, in __init__\nself.env.run()\n File \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", line 160, in run\nself.run_action(resource, action)\n File \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", line 124, in run_action\nprovider_action()\n File \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\", line 273, in action_run\ntries=self.resource.tries, try_sleep=self.resource.try_sleep)\n File \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 71, in inner\nresult = function(command, **kwargs)\n File \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 93, in checked_call\ntries=tries, try_sleep=try_sleep)\n File \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 141, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n File \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 294, in _call\nraise Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of '/usr/sbin/ambari-metrics-grafana start' returned 1. Hortonworks #\nThis is MOTD message, added for testing in qe infra\nStarting Ambari Metrics Grafana: FAILED", Please find the artifacts for the run [here](http://qelog.hortonworks.com/log /nat-yc-ambari-2-4-2-0-amb-r7-dmyu-ambari-config-6/test-logs/ambari-config/art ifacts/screenshots/com.hw.ambari.ui.tests.installer.InstallHadoop/install/_8_2 3_23_7_Component__Phoenix_Query_Server__is_not__STARTED__on_host__ctr_e45_1475 874954070_0581_01_/lastAvailableRequests.txt) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18579) Grafana fails to start after deployment
Andrew Onischuk created AMBARI-18579: Summary: Grafana fails to start after deployment Key: AMBARI-18579 URL: https://issues.apache.org/jira/browse/AMBARI-18579 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.4.2 Noticed this issue in Ambari system tests clusters that run on YCloud, that Grafana fails to start after deployment with the below error "stderr" : "Traceback (most recent call last):\n File \"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py\", line 67, in \nAmsGrafana().execute()\n File \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\", line 280, in execute\nmethod(env)\n File \"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py\", line 46, in start\nuser=params.ams_user\n File \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line 155, in __init__\nself.env.run()\n File \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", line 160, in run\nself.run_action(resource, action)\n File \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", line 124, in run_action\nprovider_action()\n File \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\", line 273, in action_run\ntries=self.resource.tries, try_sleep=self.resource.try_sleep)\n File \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 71, in inner\nresult = function(command, **kwargs)\n File \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 93, in checked_call\ntries=tries, try_sleep=try_sleep)\n File \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 141, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n File \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 294, in _call\nraise Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of '/usr/sbin/ambari-metrics-grafana start' returned 1. Hortonworks #\nThis is MOTD message, added for testing in qe infra\nStarting Ambari Metrics Grafana: FAILED", Please find the artifacts for the run [here](http://qelog.hortonworks.com/log /nat-yc-ambari-2-4-2-0-amb-r7-dmyu-ambari-config-6/test-logs/ambari-config/art ifacts/screenshots/com.hw.ambari.ui.tests.installer.InstallHadoop/install/_8_2 3_23_7_Component__Phoenix_Query_Server__is_not__STARTED__on_host__ctr_e45_1475 874954070_0581_01_/lastAvailableRequests.txt) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18568) Hive shows restart indicator after RU
[ https://issues.apache.org/jira/browse/AMBARI-18568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569194#comment-15569194 ] Hudson commented on AMBARI-18568: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5788 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5788/]) AMBARI-18568. Hive shows restart indicator after RU (ncole) (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=82afd3a0ff4dac37a8c56b914b37c1c9476c30ee]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.5.xml > Hive shows restart indicator after RU > - > > Key: AMBARI-18568 > URL: https://issues.apache.org/jira/browse/AMBARI-18568 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18568.patch > > > After RU including Hive, the Hive service shows a restart indicator. This is > because orchestration sets up Hive Metastore FIRST, then HiveServer. > HiveServer has config changes for port. > Since metastore has already been restarted before the config change and > depends on hive-site, it reports having stale configs. > Change is only for HDP-2.5 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18577) Installing ambari agent on Suse fails, when zypper has questions
[
https://issues.apache.org/jira/browse/AMBARI-18577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569099#comment-15569099
]
Hadoop QA commented on AMBARI-18577:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12832895/0001-AMBARI-18577-add-non-interactive-flag-to-zypper-comm.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/8851//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8851//console
This message is automatically generated.
> Installing ambari agent on Suse fails, when zypper has questions
>
>
> Key: AMBARI-18577
> URL: https://issues.apache.org/jira/browse/AMBARI-18577
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
> Environment: Suse 11p3
>Reporter: Zsombor Gegesy
> Fix For: trunk
>
> Attachments:
> 0001-AMBARI-18577-add-non-interactive-flag-to-zypper-comm.patch
>
>
> During installing the ambari-agent on hosts, the process stuck at :
> {noformat}
> 17829 pts/0Ss+0:00 | \_ /bin/bash
> /var/lib/ambari-agent/tmp/ambari-sudo.sh python
> /var/lib/ambari-agent/tmp/setupAgent1476267067.py
> os-sles11-3-cluster-3.openstacklocal DEV os-sles11
> 17855 pts/0S+ 0:00 | \_ python
> /var/lib/ambari-agent/tmp/setupAgent1476267067.py
> os-sles11-3-cluster-3.openstacklocal DEV os-sles11-3-cluster.openstacklocal
> root 2.4
> 18357 pts/0S+ 0:00 | \_ bash -c zypper --no-gpg-checks -q
> search -s --match-exact ambari-agent | grep ambari-agent | sed -re 's/\s+/
> /g' | cut -d '|' -f 4 | tr '\n' ', ' | sed -s 's/[-|
> 18358 pts/0S+ 0:00 | \_ zypper --no-gpg-checks -q
> search -s --match-exact ambari-agent
> 18359 pts/0S+ 0:00 | \_ grep ambari-agent
> 18360 pts/0S+ 0:00 | \_ sed -re s/\s+/ /g
> 18361 pts/0S+ 0:00 | \_ cut -d | -f 4
> 18362 pts/0S+ 0:00 | \_ tr \n ,
> 18363 pts/0S+ 0:00 | \_ sed -s s/[-|~][A-Za-z0-9]*//g
> {noformat}
> Unfortunately the process hangs there forever, other zypper processes refuses
> to do anything. After killing the processes, it is possible to use the system
> again, and check what happened. It seems, that zypper has a problem with one
> of the repository from Suse :
> {noformat}
> File '/repodata/repomd.xml' not found on medium
> 'http://download.opensuse.org/repositories/Cloud:/Tools/SLE_11_SP3/'
> Abort, retry, ignore? [a/r/i/?] (a):
> {noformat}
> This problem can be solved, with adding the --non-interactive flag
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18568) Hive shows restart indicator after RU
[ https://issues.apache.org/jira/browse/AMBARI-18568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-18568: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Hive shows restart indicator after RU > - > > Key: AMBARI-18568 > URL: https://issues.apache.org/jira/browse/AMBARI-18568 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18568.patch > > > After RU including Hive, the Hive service shows a restart indicator. This is > because orchestration sets up Hive Metastore FIRST, then HiveServer. > HiveServer has config changes for port. > Since metastore has already been restarted before the config change and > depends on hive-site, it reports having stale configs. > Change is only for HDP-2.5 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18577) Installing ambari agent on Suse fails, when zypper has questions
[
https://issues.apache.org/jira/browse/AMBARI-18577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zsombor Gegesy updated AMBARI-18577:
Attachment: 0001-AMBARI-18577-add-non-interactive-flag-to-zypper-comm.patch
Fix setupAgent
> Installing ambari agent on Suse fails, when zypper has questions
>
>
> Key: AMBARI-18577
> URL: https://issues.apache.org/jira/browse/AMBARI-18577
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
> Environment: Suse 11p3
>Reporter: Zsombor Gegesy
> Fix For: trunk
>
> Attachments:
> 0001-AMBARI-18577-add-non-interactive-flag-to-zypper-comm.patch
>
>
> During installing the ambari-agent on hosts, the process stuck at :
> {noformat}
> 17829 pts/0Ss+0:00 | \_ /bin/bash
> /var/lib/ambari-agent/tmp/ambari-sudo.sh python
> /var/lib/ambari-agent/tmp/setupAgent1476267067.py
> os-sles11-3-cluster-3.openstacklocal DEV os-sles11
> 17855 pts/0S+ 0:00 | \_ python
> /var/lib/ambari-agent/tmp/setupAgent1476267067.py
> os-sles11-3-cluster-3.openstacklocal DEV os-sles11-3-cluster.openstacklocal
> root 2.4
> 18357 pts/0S+ 0:00 | \_ bash -c zypper --no-gpg-checks -q
> search -s --match-exact ambari-agent | grep ambari-agent | sed -re 's/\s+/
> /g' | cut -d '|' -f 4 | tr '\n' ', ' | sed -s 's/[-|
> 18358 pts/0S+ 0:00 | \_ zypper --no-gpg-checks -q
> search -s --match-exact ambari-agent
> 18359 pts/0S+ 0:00 | \_ grep ambari-agent
> 18360 pts/0S+ 0:00 | \_ sed -re s/\s+/ /g
> 18361 pts/0S+ 0:00 | \_ cut -d | -f 4
> 18362 pts/0S+ 0:00 | \_ tr \n ,
> 18363 pts/0S+ 0:00 | \_ sed -s s/[-|~][A-Za-z0-9]*//g
> {noformat}
> Unfortunately the process hangs there forever, other zypper processes refuses
> to do anything. After killing the processes, it is possible to use the system
> again, and check what happened. It seems, that zypper has a problem with one
> of the repository from Suse :
> {noformat}
> File '/repodata/repomd.xml' not found on medium
> 'http://download.opensuse.org/repositories/Cloud:/Tools/SLE_11_SP3/'
> Abort, retry, ignore? [a/r/i/?] (a):
> {noformat}
> This problem can be solved, with adding the --non-interactive flag
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18577) Installing ambari agent on Suse fails, when zypper has questions
[
https://issues.apache.org/jira/browse/AMBARI-18577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zsombor Gegesy updated AMBARI-18577:
Fix Version/s: trunk
Status: Patch Available (was: Open)
> Installing ambari agent on Suse fails, when zypper has questions
>
>
> Key: AMBARI-18577
> URL: https://issues.apache.org/jira/browse/AMBARI-18577
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
> Environment: Suse 11p3
>Reporter: Zsombor Gegesy
> Fix For: trunk
>
>
> During installing the ambari-agent on hosts, the process stuck at :
> {noformat}
> 17829 pts/0Ss+0:00 | \_ /bin/bash
> /var/lib/ambari-agent/tmp/ambari-sudo.sh python
> /var/lib/ambari-agent/tmp/setupAgent1476267067.py
> os-sles11-3-cluster-3.openstacklocal DEV os-sles11
> 17855 pts/0S+ 0:00 | \_ python
> /var/lib/ambari-agent/tmp/setupAgent1476267067.py
> os-sles11-3-cluster-3.openstacklocal DEV os-sles11-3-cluster.openstacklocal
> root 2.4
> 18357 pts/0S+ 0:00 | \_ bash -c zypper --no-gpg-checks -q
> search -s --match-exact ambari-agent | grep ambari-agent | sed -re 's/\s+/
> /g' | cut -d '|' -f 4 | tr '\n' ', ' | sed -s 's/[-|
> 18358 pts/0S+ 0:00 | \_ zypper --no-gpg-checks -q
> search -s --match-exact ambari-agent
> 18359 pts/0S+ 0:00 | \_ grep ambari-agent
> 18360 pts/0S+ 0:00 | \_ sed -re s/\s+/ /g
> 18361 pts/0S+ 0:00 | \_ cut -d | -f 4
> 18362 pts/0S+ 0:00 | \_ tr \n ,
> 18363 pts/0S+ 0:00 | \_ sed -s s/[-|~][A-Za-z0-9]*//g
> {noformat}
> Unfortunately the process hangs there forever, other zypper processes refuses
> to do anything. After killing the processes, it is possible to use the system
> again, and check what happened. It seems, that zypper has a problem with one
> of the repository from Suse :
> {noformat}
> File '/repodata/repomd.xml' not found on medium
> 'http://download.opensuse.org/repositories/Cloud:/Tools/SLE_11_SP3/'
> Abort, retry, ignore? [a/r/i/?] (a):
> {noformat}
> This problem can be solved, with adding the --non-interactive flag
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18577) Installing ambari agent on Suse fails, when zypper has questions
Zsombor Gegesy created AMBARI-18577:
---
Summary: Installing ambari agent on Suse fails, when zypper has
questions
Key: AMBARI-18577
URL: https://issues.apache.org/jira/browse/AMBARI-18577
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.0
Environment: Suse 11p3
Reporter: Zsombor Gegesy
During installing the ambari-agent on hosts, the process stuck at :
{noformat}
17829 pts/0Ss+0:00 | \_ /bin/bash
/var/lib/ambari-agent/tmp/ambari-sudo.sh python
/var/lib/ambari-agent/tmp/setupAgent1476267067.py
os-sles11-3-cluster-3.openstacklocal DEV os-sles11
17855 pts/0S+ 0:00 | \_ python
/var/lib/ambari-agent/tmp/setupAgent1476267067.py
os-sles11-3-cluster-3.openstacklocal DEV os-sles11-3-cluster.openstacklocal
root 2.4
18357 pts/0S+ 0:00 | \_ bash -c zypper --no-gpg-checks -q
search -s --match-exact ambari-agent | grep ambari-agent | sed -re 's/\s+/ /g'
| cut -d '|' -f 4 | tr '\n' ', ' | sed -s 's/[-|
18358 pts/0S+ 0:00 | \_ zypper --no-gpg-checks -q search
-s --match-exact ambari-agent
18359 pts/0S+ 0:00 | \_ grep ambari-agent
18360 pts/0S+ 0:00 | \_ sed -re s/\s+/ /g
18361 pts/0S+ 0:00 | \_ cut -d | -f 4
18362 pts/0S+ 0:00 | \_ tr \n ,
18363 pts/0S+ 0:00 | \_ sed -s s/[-|~][A-Za-z0-9]*//g
{noformat}
Unfortunately the process hangs there forever, other zypper processes refuses
to do anything. After killing the processes, it is possible to use the system
again, and check what happened. It seems, that zypper has a problem with one of
the repository from Suse :
{noformat}
File '/repodata/repomd.xml' not found on medium
'http://download.opensuse.org/repositories/Cloud:/Tools/SLE_11_SP3/'
Abort, retry, ignore? [a/r/i/?] (a):
{noformat}
This problem can be solved, with adding the --non-interactive flag
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18571) 'HDFS Space Utilization' metric graph in HDFS service page is incorrect
[ https://issues.apache.org/jira/browse/AMBARI-18571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15568574#comment-15568574 ] Hudson commented on AMBARI-18571: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5787 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5787/]) AMBARI-18571 'HDFS Space Utilization' metric graph in HDFS service page (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9511638609f756cc70eaf0cca32a1cc55b40424c]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/services/HDFS/widgets.json > 'HDFS Space Utilization' metric graph in HDFS service page is incorrect > --- > > Key: AMBARI-18571 > URL: https://issues.apache.org/jira/browse/AMBARI-18571 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18571.patch, Screen Shot 2015-10-27 at 5.50.13 > PM.png, Screen Shot 2015-10-27 at 5.50.29 PM.png, Screen Shot 2015-10-27 at > 5.54.12 PM.png > > > On a 500 node cluster I generated 1TB of data using the teragen example. The > main dashboard and each DataNode alerts say that 98% of DFS space has been > used. However on the HDFS service page, the HDFS Space Utilization graph > shows 50% usage - which is misleading. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18566) Installer wizard-> Select Versions page: Selecting Red Hat Satellite option and clicking next button makes wizard stuck
[
https://issues.apache.org/jira/browse/AMBARI-18566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15568488#comment-15568488
]
Hadoop QA commented on AMBARI-18566:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12832797/AMBARI-18566.v1.patch
against trunk revision .
{color:red}-1 patch{color}. Trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8850//console
This message is automatically generated.
> Installer wizard-> Select Versions page: Selecting Red Hat Satellite option
> and clicking next button makes wizard stuck
> ---
>
> Key: AMBARI-18566
> URL: https://issues.apache.org/jira/browse/AMBARI-18566
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18566.v0.patch, AMBARI-18566.v1.patch
>
>
> *STR:*
> # Got to select versions page
> # Choose "Use Local Repository" option and then choose "Use RedHat
> Satellite/Spacewalk" option
> # Next button will get enabled. click on next button.
> *Expected Result:* wizard goes to next page
> *Actual Result:* On clicking next button, next button gets disabled and
> wizard does not go to next page.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18576) When multiple requests are running, aborting any will incorrectly abort all requests instead the desired one
[
https://issues.apache.org/jira/browse/AMBARI-18576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15568471#comment-15568471
]
Hadoop QA commented on AMBARI-18576:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12832792/AMBARI-18576.trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessorTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8849//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8849//console
This message is automatically generated.
> When multiple requests are running, aborting any will incorrectly abort all
> requests instead the desired one
>
>
> Key: AMBARI-18576
> URL: https://issues.apache.org/jira/browse/AMBARI-18576
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18576.branch-2.5.patch, AMBARI-18576.trunk.patch
>
>
> STR:
> * Install Ambari 2.4.0.1 with any HDP stack (e.g., 2.5) and HDFS, YARN, ZK
> * Run multiple commands in parallel (such as service checks)
> * Attempt to abort any one of them
> Instead of aborting just the desired one, it will abort all requests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18564) Ambari should be able to create arbitrary Kerberos identities for itself as declared in the Kerberos Descriptor
[
https://issues.apache.org/jira/browse/AMBARI-18564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15568393#comment-15568393
]
Hudson commented on AMBARI-18564:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #136 (See
[https://builds.apache.org/job/Ambari-branch-2.5/136/])
AMBARI-18564. Ambari should be able to create arbitrary Kerberos (rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=341b4d9adb989fd7ae41009c35a753ff66734fe0])
* (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/kerberos.json
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/ConfigureAmbariIdentitiesServerAction.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/KerberosHelperTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelperImpl.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/AbstractPrepareKerberosServerAction.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelper.java
> Ambari should be able to create arbitrary Kerberos identities for itself as
> declared in the Kerberos Descriptor
> ---
>
> Key: AMBARI-18564
> URL: https://issues.apache.org/jira/browse/AMBARI-18564
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: kerberos, kerberos_descriptor
> Fix For: 2.5.0
>
> Attachments: AMBARI-18564_branch-2.5_01.patch,
> AMBARI-18564_trunk_01.patch
>
>
> Ambari should be able to create arbitrary Kerberos identities for itself as
> declared in the Kerberos Descriptor.
> Currently, Ambari is hard-coded to create identities for itself and SPNEGO,
> but that may not be good enough for all scenarios. Therefore, there needs to
> be an {{AMBARI}} service block in the Kerberos descriptor to allow for
> arbitrary identities to be defined for the Ambari server - similar to how any
> other service is defined in the Kerberos descriptor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18564) Ambari should be able to create arbitrary Kerberos identities for itself as declared in the Kerberos Descriptor
[
https://issues.apache.org/jira/browse/AMBARI-18564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15568370#comment-15568370
]
Hudson commented on AMBARI-18564:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5786 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5786/])
AMBARI-18564. Ambari should be able to create arbitrary Kerberos (rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d2a926ee71f8a24a8d568fc977dc8ac06dc18493])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelper.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelperImpl.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/ConfigureAmbariIdentitiesServerAction.java
* (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/kerberos.json
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/AbstractPrepareKerberosServerAction.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/KerberosHelperTest.java
> Ambari should be able to create arbitrary Kerberos identities for itself as
> declared in the Kerberos Descriptor
> ---
>
> Key: AMBARI-18564
> URL: https://issues.apache.org/jira/browse/AMBARI-18564
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: kerberos, kerberos_descriptor
> Fix For: 2.5.0
>
> Attachments: AMBARI-18564_branch-2.5_01.patch,
> AMBARI-18564_trunk_01.patch
>
>
> Ambari should be able to create arbitrary Kerberos identities for itself as
> declared in the Kerberos Descriptor.
> Currently, Ambari is hard-coded to create identities for itself and SPNEGO,
> but that may not be good enough for all scenarios. Therefore, there needs to
> be an {{AMBARI}} service block in the Kerberos descriptor to allow for
> arbitrary identities to be defined for the Ambari server - similar to how any
> other service is defined in the Kerberos descriptor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18571) 'HDFS Space Utilization' metric graph in HDFS service page is incorrect
[ https://issues.apache.org/jira/browse/AMBARI-18571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15568174#comment-15568174 ] Andrii Tkach commented on AMBARI-18571: --- committed to trunk > 'HDFS Space Utilization' metric graph in HDFS service page is incorrect > --- > > Key: AMBARI-18571 > URL: https://issues.apache.org/jira/browse/AMBARI-18571 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18571.patch, Screen Shot 2015-10-27 at 5.50.13 > PM.png, Screen Shot 2015-10-27 at 5.50.29 PM.png, Screen Shot 2015-10-27 at > 5.54.12 PM.png > > > On a 500 node cluster I generated 1TB of data using the teragen example. The > main dashboard and each DataNode alerts say that 98% of DFS space has been > used. However on the HDFS service page, the HDFS Space Utilization graph > shows 50% usage - which is misleading. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18571) 'HDFS Space Utilization' metric graph in HDFS service page is incorrect
[ https://issues.apache.org/jira/browse/AMBARI-18571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-18571: -- Resolution: Fixed Status: Resolved (was: Patch Available) > 'HDFS Space Utilization' metric graph in HDFS service page is incorrect > --- > > Key: AMBARI-18571 > URL: https://issues.apache.org/jira/browse/AMBARI-18571 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18571.patch, Screen Shot 2015-10-27 at 5.50.13 > PM.png, Screen Shot 2015-10-27 at 5.50.29 PM.png, Screen Shot 2015-10-27 at > 5.54.12 PM.png > > > On a 500 node cluster I generated 1TB of data using the teragen example. The > main dashboard and each DataNode alerts say that 98% of DFS space has been > used. However on the HDFS service page, the HDFS Space Utilization graph > shows 50% usage - which is misleading. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18571) 'HDFS Space Utilization' metric graph in HDFS service page is incorrect
[ https://issues.apache.org/jira/browse/AMBARI-18571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15568149#comment-15568149 ] Oleg Nechiporenko commented on AMBARI-18571: +1 for patch > 'HDFS Space Utilization' metric graph in HDFS service page is incorrect > --- > > Key: AMBARI-18571 > URL: https://issues.apache.org/jira/browse/AMBARI-18571 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18571.patch, Screen Shot 2015-10-27 at 5.50.13 > PM.png, Screen Shot 2015-10-27 at 5.50.29 PM.png, Screen Shot 2015-10-27 at > 5.54.12 PM.png > > > On a 500 node cluster I generated 1TB of data using the teragen example. The > main dashboard and each DataNode alerts say that 98% of DFS space has been > used. However on the HDFS service page, the HDFS Space Utilization graph > shows 50% usage - which is misleading. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18564) Ambari should be able to create arbitrary Kerberos identities for itself as declared in the Kerberos Descriptor
[
https://issues.apache.org/jira/browse/AMBARI-18564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-18564:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
{noformat}
commit d2a926ee71f8a24a8d568fc977dc8ac06dc18493
Author: Robert Levas
Date: Wed Oct 12 05:01:14 2016 -0400
{noformat}
Committed to branch-2.5
{noformat}
commit 341b4d9adb989fd7ae41009c35a753ff66734fe0
Author: Robert Levas
Date: Wed Oct 12 05:02:11 2016 -0400
{noformat}
> Ambari should be able to create arbitrary Kerberos identities for itself as
> declared in the Kerberos Descriptor
> ---
>
> Key: AMBARI-18564
> URL: https://issues.apache.org/jira/browse/AMBARI-18564
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: kerberos, kerberos_descriptor
> Fix For: 2.5.0
>
> Attachments: AMBARI-18564_branch-2.5_01.patch,
> AMBARI-18564_trunk_01.patch
>
>
> Ambari should be able to create arbitrary Kerberos identities for itself as
> declared in the Kerberos Descriptor.
> Currently, Ambari is hard-coded to create identities for itself and SPNEGO,
> but that may not be good enough for all scenarios. Therefore, there needs to
> be an {{AMBARI}} service block in the Kerberos descriptor to allow for
> arbitrary identities to be defined for the Ambari server - similar to how any
> other service is defined in the Kerberos descriptor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-11705) Alerts Notifications: Groups and Severity cannot be edited
[ https://issues.apache.org/jira/browse/AMBARI-11705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15568087#comment-15568087 ] Joe Manning commented on AMBARI-11705: -- We have experienced this issue with Ambari 2.4 # rpm -q ambari-server ambari-server-2.4.1.0-22.x86_64 The issue occurs when we try to edit a notification for a service that is stopped. Or if one or more of the hosts running the service is not sending heartbeats to the ambari-server. To workaround the issue, we need restart the ambari server. > Alerts Notifications: Groups and Severity cannot be edited > -- > > Key: AMBARI-11705 > URL: https://issues.apache.org/jira/browse/AMBARI-11705 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.1.0 >Reporter: Chandana Mirashi > Labels: Alerts-UI > Attachments: AMBARI-11705.patch > > > 1. During install create alert notification. Select group and severity. > 2. Post install, edit alert notification. Make changes to Group and Severity > then save. > 3. Manage Alert Notifications text does not reflect the change. > 4. Edit notification displays same information as before the change. > 5. Close and reopen does not refresh information. > Same case seen even after creating new notifications post > install.Intermittently the clicking on save button does not close edit > notification. > One other scenario > 1. Edit notification and change just the severity and save. > 2. Manage Alert Notifications text does not reflect the change. > 3. Close manage notification and open again. The page is refreshed and >can see the changes made to Severity. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
