[jira] [Commented] (AMBARI-21542) AMS fail to start after IOP 4.2 to HDP 2.6.2 upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095749#comment-16095749 ] Hudson commented on AMBARI-21542: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1730 (See

[jira] [Resolved] (AMBARI-21542) AMS fail to start after IOP 4.2 to HDP 2.6.2 upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle resolved AMBARI-21542. -- Resolution: Fixed Pushed to branch-2.5 > AMS fail to start after IOP 4.2 to HDP

[jira] [Commented] (AMBARI-21541) Restart services failed post Ambari Upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095635#comment-16095635 ] Hudson commented on AMBARI-21541: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1729 (See

[jira] [Updated] (AMBARI-21541) Restart services failed post Ambari Upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-21541: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Restart services failed post Ambari

[jira] [Commented] (AMBARI-21541) Restart services failed post Ambari Upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095613#comment-16095613 ] Di Li commented on AMBARI-21541: pushed to branch-2.5 as

[jira] [Created] (AMBARI-21542) AMS fail to start after IOP 4.2 to HDP 2.6.2 upgrade

Siddharth Wagle created AMBARI-21542: Summary: AMS fail to start after IOP 4.2 to HDP 2.6.2 upgrade Key: AMBARI-21542 URL: https://issues.apache.org/jira/browse/AMBARI-21542 Project: Ambari

[jira] [Reopened] (AMBARI-21463) Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error, stack_tools.py is missing get_stack_name in __all__, disable BigInsights in UI

[ https://issues.apache.org/jira/browse/AMBARI-21463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez reopened AMBARI-21463: -- > Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error, >

[jira] [Updated] (AMBARI-21463) Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error, stack_tools.py is missing get_stack_name in __all__, disable BigInsights in UI

[ https://issues.apache.org/jira/browse/AMBARI-21463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-21463: - Attachment: AMBARI-21463.patch > Cross-stack upgrade, Oozie restart fails with

[jira] [Updated] (AMBARI-21463) Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error, stack_tools.py is missing get_stack_name in __all__, disable BigInsights in UI

[ https://issues.apache.org/jira/browse/AMBARI-21463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-21463: - Status: Patch Available (was: Reopened) > Cross-stack upgrade, Oozie restart

[jira] [Updated] (AMBARI-21463) Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error, stack_tools.py is missing get_stack_name in __all__, disable BigInsights in UI

[ https://issues.apache.org/jira/browse/AMBARI-21463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-21463: - Attachment: AMBARI-21463.addendum.patch > Cross-stack upgrade, Oozie restart

[jira] [Commented] (AMBARI-21528) Zookeeper server has incorrect memory setting, missing m in Xmx value

[ https://issues.apache.org/jira/browse/AMBARI-21528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095505#comment-16095505 ] Hudson commented on AMBARI-21528: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7793 (See

[jira] [Commented] (AMBARI-21530) Service Checks During Upgrades Should Use Desired Stack

[ https://issues.apache.org/jira/browse/AMBARI-21530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095457#comment-16095457 ] Hudson commented on AMBARI-21530: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7792 (See

[jira] [Commented] (AMBARI-21528) Zookeeper server has incorrect memory setting, missing m in Xmx value

[ https://issues.apache.org/jira/browse/AMBARI-21528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095450#comment-16095450 ] Hudson commented on AMBARI-21528: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1728 (See

[jira] [Commented] (AMBARI-21345) Add host doesn't fully add a node when include/exclude files are used

[ https://issues.apache.org/jira/browse/AMBARI-21345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095443#comment-16095443 ] Hadoop QA commented on AMBARI-21345: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (AMBARI-21528) Zookeeper server has incorrect memory setting, missing m in Xmx value

[ https://issues.apache.org/jira/browse/AMBARI-21528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-21528: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to

[jira] [Commented] (AMBARI-21541) Restart services failed post Ambari Upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095390#comment-16095390 ] Hadoop QA commented on AMBARI-21541: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (AMBARI-21539) Resource Manager fails to restart properly during an IOP to HDP upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-21539: --- Priority: Critical (was: Major) > Resource Manager fails to restart properly during an IOP

[jira] [Updated] (AMBARI-21539) Resource Manager fails to restart properly during an IOP to HDP upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-21539: --- Fix Version/s: 2.5.2 > Resource Manager fails to restart properly during an IOP to HDP

[jira] [Assigned] (AMBARI-21539) Resource Manager fails to restart properly during an IOP to HDP upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty reassigned AMBARI-21539: -- Assignee: Attila Magyar > Resource Manager fails to restart properly during an IOP

[jira] [Updated] (AMBARI-21541) Restart services failed post Ambari Upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-21541: --- Status: Patch Available (was: Open) > Restart services failed post Ambari Upgrade >

[jira] [Updated] (AMBARI-21541) Restart services failed post Ambari Upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-21541: --- Attachment: AMBARI-21541.patch > Restart services failed post Ambari Upgrade >

[jira] [Created] (AMBARI-21541) Restart services failed post Ambari Upgrade

Di Li created AMBARI-21541: -- Summary: Restart services failed post Ambari Upgrade Key: AMBARI-21541 URL: https://issues.apache.org/jira/browse/AMBARI-21541 Project: Ambari Issue Type: Bug

[jira] [Resolved] (AMBARI-21527) Restart of MR2 History Server failed due to wrong NameNode RPC address

[ https://issues.apache.org/jira/browse/AMBARI-21527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li resolved AMBARI-21527. Resolution: Fixed > Restart of MR2 History Server failed due to wrong NameNode RPC address >

[jira] [Commented] (AMBARI-21539) Resource Manager fails to restart properly during an IOP to HDP upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095307#comment-16095307 ] Tim Thorpe commented on AMBARI-21539: - I have tried changing the

[jira] [Updated] (AMBARI-21538) Zeppelin quick links and service check failing in SSL enabled environment.

[ https://issues.apache.org/jira/browse/AMBARI-21538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] amarnath reddy pappu updated AMBARI-21538: -- Description: >From Ambari documentation

[jira] [Updated] (AMBARI-21538) Zeppelin quick links and service check failing in SSL enabled environment.

[ https://issues.apache.org/jira/browse/AMBARI-21538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] amarnath reddy pappu updated AMBARI-21538: -- Component/s: (was: ambari-admin) ambari-server >

[jira] [Updated] (AMBARI-21538) Zeppelin quick links and service check failing in SSL enabled environment.

[ https://issues.apache.org/jira/browse/AMBARI-21538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krishnama Raju K updated AMBARI-21538: -- Description: >From Ambari documentation

[jira] [Commented] (AMBARI-21527) Restart of MR2 History Server failed due to wrong NameNode RPC address

[ https://issues.apache.org/jira/browse/AMBARI-21527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095202#comment-16095202 ] Hudson commented on AMBARI-21527: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1727 (See

[jira] [Created] (AMBARI-21540) Kerberos related enhancement request

amarnath reddy pappu created AMBARI-21540: - Summary: Kerberos related enhancement request Key: AMBARI-21540 URL: https://issues.apache.org/jira/browse/AMBARI-21540 Project: Ambari

[jira] [Created] (AMBARI-21539) Resource Manager fails to restart properly during an IOP to HDP upgrade

Tim Thorpe created AMBARI-21539: --- Summary: Resource Manager fails to restart properly during an IOP to HDP upgrade Key: AMBARI-21539 URL: https://issues.apache.org/jira/browse/AMBARI-21539 Project:

[jira] [Commented] (AMBARI-21527) Restart of MR2 History Server failed due to wrong NameNode RPC address

[ https://issues.apache.org/jira/browse/AMBARI-21527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095154#comment-16095154 ] Di Li commented on AMBARI-21527: pushed to branch-2.5 as

[jira] [Updated] (AMBARI-21538) Zeppelin quick links and service check failing in SSL enabled environment.

[ https://issues.apache.org/jira/browse/AMBARI-21538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krishnama Raju K updated AMBARI-21538: -- Description: >From Ambari documentation

[jira] [Updated] (AMBARI-21538) Zeppelin quick links and service check failing in SSL enabled environment.

[ https://issues.apache.org/jira/browse/AMBARI-21538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krishnama Raju K updated AMBARI-21538: -- Summary: Zeppelin quick links and service check failing in SSL enabled environment.

[jira] [Updated] (AMBARI-21538) Zeppelin service check failing in SSL enabled environment.

[ https://issues.apache.org/jira/browse/AMBARI-21538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krishnama Raju K updated AMBARI-21538: -- Description: >From Ambari documentation

[jira] [Updated] (AMBARI-21538) Zeppelin service check failing in SSL enabled environment.

[ https://issues.apache.org/jira/browse/AMBARI-21538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krishnama Raju K updated AMBARI-21538: -- Summary: Zeppelin service check failing in SSL enabled environment. (was: Zeppelin

[jira] [Created] (AMBARI-21538) Zeppelin quicklink and service check failing in SSL enabled environment.

Krishnama Raju K created AMBARI-21538: - Summary: Zeppelin quicklink and service check failing in SSL enabled environment. Key: AMBARI-21538 URL: https://issues.apache.org/jira/browse/AMBARI-21538

[jira] [Updated] (AMBARI-21527) Restart of MR2 History Server failed due to wrong NameNode RPC address

[ https://issues.apache.org/jira/browse/AMBARI-21527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-21527: --- Description: P.S This happens on NN restart (kerberos cluster) and remote DS restart (non secured

[jira] [Commented] (AMBARI-21527) Restart of MR2 History Server failed due to wrong NameNode RPC address

[ https://issues.apache.org/jira/browse/AMBARI-21527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094889#comment-16094889 ] Di Li commented on AMBARI-21527: Hello Attila, Sorry that I took this JIRA for the time being. I

[jira] [Assigned] (AMBARI-21527) Restart of MR2 History Server failed due to wrong NameNode RPC address

[ https://issues.apache.org/jira/browse/AMBARI-21527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li reassigned AMBARI-21527: -- Assignee: Di Li (was: Doroszlai, Attila) > Restart of MR2 History Server failed due to wrong

[jira] [Updated] (AMBARI-21527) Restart of MR2 History Server failed due to wrong NameNode RPC address

[ https://issues.apache.org/jira/browse/AMBARI-21527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-21527: --- Attachment: AMBARI-21527-HA_and_NonHA.patch This is a problem for both secured and non secured cluster

[jira] [Commented] (AMBARI-21345) Add host doesn't fully add a node when include/exclude files are used

[ https://issues.apache.org/jira/browse/AMBARI-21345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094822#comment-16094822 ] Hadoop QA commented on AMBARI-21345: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (AMBARI-21345) Add host doesn't fully add a node when include/exclude files are used

[ https://issues.apache.org/jira/browse/AMBARI-21345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-21345: Attachment: AMBARI-21345_addiotional.patch > Add host doesn't fully add a node when

[jira] [Updated] (AMBARI-21345) Add host doesn't fully add a node when include/exclude files are used

[ https://issues.apache.org/jira/browse/AMBARI-21345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-21345: Status: Patch Available (was: Reopened) > Add host doesn't fully add a node when include/exclude

[jira] [Reopened] (AMBARI-21345) Add host doesn't fully add a node when include/exclude files are used

[ https://issues.apache.org/jira/browse/AMBARI-21345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen reopened AMBARI-21345: - > Add host doesn't fully add a node when include/exclude files are used >

[jira] [Assigned] (AMBARI-21527) Restart of MR2 History Server failed due to wrong NameNode RPC address

[ https://issues.apache.org/jira/browse/AMBARI-21527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila reassigned AMBARI-21527: -- Assignee: Doroszlai, Attila (was: Siddharth Wagle) > Restart of MR2 History

[jira] [Commented] (AMBARI-21535) ACTIVITY_ANALYZER Install failed: Error: Unable to run the custom hook script

[ https://issues.apache.org/jira/browse/AMBARI-21535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094725#comment-16094725 ] Hudson commented on AMBARI-21535: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1726 (See

[jira] [Commented] (AMBARI-21535) ACTIVITY_ANALYZER Install failed: Error: Unable to run the custom hook script

[ https://issues.apache.org/jira/browse/AMBARI-21535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094722#comment-16094722 ] Hudson commented on AMBARI-21535: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7791 (See

[jira] [Commented] (AMBARI-21535) ACTIVITY_ANALYZER Install failed: Error: Unable to run the custom hook script

[ https://issues.apache.org/jira/browse/AMBARI-21535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094685#comment-16094685 ] Hadoop QA commented on AMBARI-21535: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (AMBARI-21535) ACTIVITY_ANALYZER Install failed: Error: Unable to run the custom hook script

[ https://issues.apache.org/jira/browse/AMBARI-21535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-21535: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk

[jira] [Created] (AMBARI-21537) Backport AMBARI-12556 UI Work For Patch/Service Upgrades

Jonathan Hurley created AMBARI-21537: Summary: Backport AMBARI-12556 UI Work For Patch/Service Upgrades Key: AMBARI-21537 URL: https://issues.apache.org/jira/browse/AMBARI-21537 Project: Ambari

[jira] [Updated] (AMBARI-21536) Trigger alert check via Ambari UI

[ https://issues.apache.org/jira/browse/AMBARI-21536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hari Sekhon updated AMBARI-21536: - Description: Feature Request add UI ability to trigger an alert check. For example, Ranger

[jira] [Updated] (AMBARI-21536) Trigger alert check via Ambari UI

[ https://issues.apache.org/jira/browse/AMBARI-21536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hari Sekhon updated AMBARI-21536: - Priority: Major (was: Minor) > Trigger alert check via Ambari UI >

[jira] [Created] (AMBARI-21536) Trigger alert check via Ambari UI

Hari Sekhon created AMBARI-21536: Summary: Trigger alert check via Ambari UI Key: AMBARI-21536 URL: https://issues.apache.org/jira/browse/AMBARI-21536 Project: Ambari Issue Type: New Feature

[jira] [Commented] (AMBARI-21530) Service Checks During Upgrades Should Use Desired Stack

[ https://issues.apache.org/jira/browse/AMBARI-21530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094648#comment-16094648 ] Hudson commented on AMBARI-21530: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1725 (See

[jira] [Created] (AMBARI-21535) ACTIVITY_ANALYZER Install failed: Error: Unable to run the custom hook script

Andrew Onischuk created AMBARI-21535: Summary: ACTIVITY_ANALYZER Install failed: Error: Unable to run the custom hook script Key: AMBARI-21535 URL: https://issues.apache.org/jira/browse/AMBARI-21535

[jira] [Updated] (AMBARI-21535) ACTIVITY_ANALYZER Install failed: Error: Unable to run the custom hook script

[ https://issues.apache.org/jira/browse/AMBARI-21535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-21535: - Status: Patch Available (was: Open) > ACTIVITY_ANALYZER Install failed: Error: Unable

[jira] [Updated] (AMBARI-21535) ACTIVITY_ANALYZER Install failed: Error: Unable to run the custom hook script

[ https://issues.apache.org/jira/browse/AMBARI-21535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-21535: - Attachment: AMBARI-21535.patch > ACTIVITY_ANALYZER Install failed: Error: Unable to run

[jira] [Commented] (AMBARI-21534) Spinner doesnt disappear and hosts not loading even after 5 minutes

[ https://issues.apache.org/jira/browse/AMBARI-21534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094605#comment-16094605 ] Hudson commented on AMBARI-21534: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1724 (See

[jira] [Updated] (AMBARI-21530) Service Checks During Upgrades Should Use Desired Stack

[ https://issues.apache.org/jira/browse/AMBARI-21530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-21530: - Status: Patch Available (was: Open) > Service Checks During Upgrades Should Use

[jira] [Updated] (AMBARI-21530) Service Checks During Upgrades Should Use Desired Stack

[ https://issues.apache.org/jira/browse/AMBARI-21530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-21530: - Resolution: Fixed Status: Resolved (was: Patch Available) > Service Checks

[jira] [Updated] (AMBARI-21530) Service Checks During Upgrades Should Use Desired Stack

[ https://issues.apache.org/jira/browse/AMBARI-21530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-21530: - Attachment: AMBARI-21530.patch > Service Checks During Upgrades Should Use Desired

[jira] [Updated] (AMBARI-21534) Spinner doesnt disappear and hosts not loading even after 5 minutes

[ https://issues.apache.org/jira/browse/AMBARI-21534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21534: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Spinner doesnt disappear

[jira] [Commented] (AMBARI-21534) Spinner doesnt disappear and hosts not loading even after 5 minutes

[ https://issues.apache.org/jira/browse/AMBARI-21534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094577#comment-16094577 ] Andrii Tkach commented on AMBARI-21534: --- committed to branch-2.5 > Spinner doesnt disappear and

[jira] [Updated] (AMBARI-21534) Spinner doesnt disappear and hosts not loading even after 5 minutes

[ https://issues.apache.org/jira/browse/AMBARI-21534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21534: -- Attachment: AMBARI-21534.patch > Spinner doesnt disappear and hosts not loading even after 5

[jira] [Updated] (AMBARI-21534) Spinner doesnt disappear and hosts not loading even after 5 minutes

[ https://issues.apache.org/jira/browse/AMBARI-21534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21534: -- Attachment: (was: AMBARI-21534.patch) > Spinner doesnt disappear and hosts not loading

[jira] [Updated] (AMBARI-21406) Refresh configurations without restarting components

[ https://issues.apache.org/jira/browse/AMBARI-21406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-21406: Summary: Refresh configurations without restarting components (was: Refresh

[jira] [Commented] (AMBARI-21534) Spinner doesnt disappear and hosts not loading even after 5 minutes

[ https://issues.apache.org/jira/browse/AMBARI-21534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094570#comment-16094570 ] Aleksandr Kovalenko commented on AMBARI-21534: -- +1 for the patch > Spinner doesnt

[jira] [Commented] (AMBARI-21533) Text change for bypassing prechecks

[ https://issues.apache.org/jira/browse/AMBARI-21533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094567#comment-16094567 ] Hudson commented on AMBARI-21533: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1723 (See

[jira] [Commented] (AMBARI-21498) DB consistency checker throws errors for missing 'product-info' configs after Ambari upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094564#comment-16094564 ] Hudson commented on AMBARI-21498: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7790 (See

[jira] [Commented] (AMBARI-21531) Client component restart fails after Ambari upgrade while running custom hook script on Suse 11

[ https://issues.apache.org/jira/browse/AMBARI-21531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094563#comment-16094563 ] Hudson commented on AMBARI-21531: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7790 (See

[jira] [Commented] (AMBARI-21532) Namenode restart - PID file delete happens before the call to check status

[ https://issues.apache.org/jira/browse/AMBARI-21532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094545#comment-16094545 ] Hadoop QA commented on AMBARI-21532: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (AMBARI-21531) Client component restart fails after Ambari upgrade while running custom hook script on Suse 11

[ https://issues.apache.org/jira/browse/AMBARI-21531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094532#comment-16094532 ] Hudson commented on AMBARI-21531: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1722 (See

[jira] [Updated] (AMBARI-21534) Spinner doesnt disappear and hosts not loading even after 5 minutes

[ https://issues.apache.org/jira/browse/AMBARI-21534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21534: -- Status: Patch Available (was: Open) > Spinner doesnt disappear and hosts not loading even

[jira] [Commented] (AMBARI-21534) Spinner doesnt disappear and hosts not loading even after 5 minutes

[ https://issues.apache.org/jira/browse/AMBARI-21534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094529#comment-16094529 ] Andrii Tkach commented on AMBARI-21534: --- 30389 passing (26s) 157 pending > Spinner doesnt

[jira] [Updated] (AMBARI-21534) Spinner doesnt disappear and hosts not loading even after 5 minutes

[ https://issues.apache.org/jira/browse/AMBARI-21534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21534: -- Attachment: AMBARI-21534.patch > Spinner doesnt disappear and hosts not loading even after 5

[jira] [Created] (AMBARI-21534) Spinner doesnt disappear and hosts not loading even after 5 minutes

Andrii Tkach created AMBARI-21534: - Summary: Spinner doesnt disappear and hosts not loading even after 5 minutes Key: AMBARI-21534 URL: https://issues.apache.org/jira/browse/AMBARI-21534 Project:

[jira] [Commented] (AMBARI-21516) Log Search docker test environment build front/backend only

[ https://issues.apache.org/jira/browse/AMBARI-21516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094526#comment-16094526 ] Hudson commented on AMBARI-21516: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7789 (See

[jira] [Commented] (AMBARI-21531) Client component restart fails after Ambari upgrade while running custom hook script on Suse 11

[ https://issues.apache.org/jira/browse/AMBARI-21531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094522#comment-16094522 ] Hadoop QA commented on AMBARI-21531: {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (AMBARI-21533) Text change for bypassing prechecks

[ https://issues.apache.org/jira/browse/AMBARI-21533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094517#comment-16094517 ] Andrii Tkach commented on AMBARI-21533: --- committed to branch-2.5 > Text change for bypassing

[jira] [Updated] (AMBARI-21533) Text change for bypassing prechecks

[ https://issues.apache.org/jira/browse/AMBARI-21533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21533: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Text change for

[jira] [Commented] (AMBARI-21533) Text change for bypassing prechecks

[ https://issues.apache.org/jira/browse/AMBARI-21533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094512#comment-16094512 ] Aleksandr Kovalenko commented on AMBARI-21533: -- +1 for the patch > Text change for

[jira] [Commented] (AMBARI-21533) Text change for bypassing prechecks

[ https://issues.apache.org/jira/browse/AMBARI-21533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094510#comment-16094510 ] Andrii Tkach commented on AMBARI-21533: --- 30389 passing (24s) 157 pending > Text change for

[jira] [Updated] (AMBARI-21533) Text change for bypassing prechecks

[ https://issues.apache.org/jira/browse/AMBARI-21533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21533: -- Status: Patch Available (was: Open) > Text change for bypassing prechecks >

[jira] [Updated] (AMBARI-21533) Text change for bypassing prechecks

[ https://issues.apache.org/jira/browse/AMBARI-21533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21533: -- Attachment: AMBARI-21533.patch > Text change for bypassing prechecks >

[jira] [Created] (AMBARI-21533) Text change for bypassing prechecks

Andrii Tkach created AMBARI-21533: - Summary: Text change for bypassing prechecks Key: AMBARI-21533 URL: https://issues.apache.org/jira/browse/AMBARI-21533 Project: Ambari Issue Type: Bug

[jira] [Updated] (AMBARI-21532) Namenode restart - PID file delete happens before the call to check status

[ https://issues.apache.org/jira/browse/AMBARI-21532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-21532: Fix Version/s: 2.5.3 > Namenode restart - PID file delete happens before the call

[jira] [Commented] (AMBARI-21498) DB consistency checker throws errors for missing 'product-info' configs after Ambari upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094498#comment-16094498 ] Dmitry Lysnichenko commented on AMBARI-21498: - Committed to trunk To

[jira] [Updated] (AMBARI-21532) Namenode restart - PID file delete happens before the call to check status

[ https://issues.apache.org/jira/browse/AMBARI-21532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-21532: Component/s: ambari-server > Namenode restart - PID file delete happens before

[jira] [Updated] (AMBARI-21532) Namenode restart - PID file delete happens before the call to check status

[ https://issues.apache.org/jira/browse/AMBARI-21532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-21532: Attachment: AMBARI-21532.patch > Namenode restart - PID file delete happens

[jira] [Created] (AMBARI-21532) Namenode restart - PID file delete happens before the call to check status

Dmitry Lysnichenko created AMBARI-21532: --- Summary: Namenode restart - PID file delete happens before the call to check status Key: AMBARI-21532 URL: https://issues.apache.org/jira/browse/AMBARI-21532

[jira] [Updated] (AMBARI-21532) Namenode restart - PID file delete happens before the call to check status

[ https://issues.apache.org/jira/browse/AMBARI-21532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-21532: Status: Patch Available (was: Open) > Namenode restart - PID file delete happens

[jira] [Updated] (AMBARI-21531) Client component restart fails after Ambari upgrade while running custom hook script on Suse 11

[ https://issues.apache.org/jira/browse/AMBARI-21531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-21531: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk

[jira] [Updated] (AMBARI-21531) Client component restart fails after Ambari upgrade while running custom hook script on Suse 11

[ https://issues.apache.org/jira/browse/AMBARI-21531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-21531: - Status: Patch Available (was: Open) > Client component restart fails after Ambari

[jira] [Updated] (AMBARI-21531) Client component restart fails after Ambari upgrade while running custom hook script on Suse 11

[ https://issues.apache.org/jira/browse/AMBARI-21531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-21531: - Attachment: AMBARI-21531.patch > Client component restart fails after Ambari upgrade

[jira] [Created] (AMBARI-21531) Client component restart fails after Ambari upgrade while running custom hook script on Suse 11

Andrew Onischuk created AMBARI-21531: Summary: Client component restart fails after Ambari upgrade while running custom hook script on Suse 11 Key: AMBARI-21531 URL:

[jira] [Commented] (AMBARI-21169) Service and Patch Upgrade Catalog Changes

[ https://issues.apache.org/jira/browse/AMBARI-21169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094480#comment-16094480 ] Hadoop QA commented on AMBARI-21169: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (AMBARI-21516) Log Search docker test environment build front/backend only

[ https://issues.apache.org/jira/browse/AMBARI-21516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094478#comment-16094478 ] Miklos Gergely commented on AMBARI-21516: - committed to trunk: {code:java} commit

[jira] [Resolved] (AMBARI-21516) Log Search docker test environment build front/backend only

[ https://issues.apache.org/jira/browse/AMBARI-21516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely resolved AMBARI-21516. - Resolution: Fixed > Log Search docker test environment build front/backend only >

[jira] [Commented] (AMBARI-9510) Metric Monitor can not be started

[ https://issues.apache.org/jira/browse/AMBARI-9510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094459#comment-16094459 ] Dmytro Sen commented on AMBARI-9510: [~WanderingEachDay] There is no ld util installed on your

[jira] [Updated] (AMBARI-21516) Log Search docker test environment build front/backend only

[ https://issues.apache.org/jira/browse/AMBARI-21516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-21516: Attachment: AMBARI-21516.patch > Log Search docker test environment build front/backend

  1   2   >