[jira] [Commented] (AMBARI-21650) Ranger Usersync process starts with older stack script during cross stack upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114024#comment-16114024 ] Hudson commented on AMBARI-21650: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.

[jira] [Commented] (AMBARI-21650) Ranger Usersync process starts with older stack script during cross stack upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114022#comment-16114022 ] Mugdha Varadkar commented on AMBARI-21650: -- Committed to branch-2.6 [328735d6e

[jira] [Updated] (AMBARI-21650) Ranger Usersync process starts with older stack script during cross stack upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-21650: - Fix Version/s: 2.6.0 > Ranger Usersync process starts with older stack script during cro

[jira] [Updated] (AMBARI-21650) Ranger Usersync process starts with older stack script during cross stack upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-21650: - Fix Version/s: trunk > Ranger Usersync process starts with older stack script during cro

[jira] [Updated] (AMBARI-21650) Ranger Usersync process starts with older stack script during cross stack upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-21650: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2

[jira] [Commented] (AMBARI-21654) Post Ambari upgrade, BI value add 4.2 services should still be able to restart

[ https://issues.apache.org/jira/browse/AMBARI-21654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113998#comment-16113998 ] Hadoop QA commented on AMBARI-21654: {color:red}-1 overall{color}. Here are the res

[jira] [Commented] (AMBARI-21658) Check for config group host mapping left behind after host delete

[ https://issues.apache.org/jira/browse/AMBARI-21658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113993#comment-16113993 ] Hudson commented on AMBARI-21658: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.

[jira] [Updated] (AMBARI-21655) Add Upgrade Mpack Recommendations

[ https://issues.apache.org/jira/browse/AMBARI-21655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-21655: --- Issue Type: Task (was: Bug) > Add Upgrade Mpack Recommendations > -

[jira] [Resolved] (AMBARI-21645) Dynamic Reload Stacks

[ https://issues.apache.org/jira/browse/AMBARI-21645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya resolved AMBARI-21645. Resolution: Fixed > Dynamic Reload Stacks > - > > Key:

[jira] [Resolved] (AMBARI-21655) Add Upgrade Mpack Recommendations

[ https://issues.apache.org/jira/browse/AMBARI-21655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya resolved AMBARI-21655. Resolution: Fixed > Add Upgrade Mpack Recommendations > -

[jira] [Commented] (AMBARI-21658) Check for config group host mapping left behind after host delete

[ https://issues.apache.org/jira/browse/AMBARI-21658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113950#comment-16113950 ] Hudson commented on AMBARI-21658: - FAILURE: Integrated in Jenkins build Ambari-branch-2.

[jira] [Updated] (AMBARI-21658) Check for config group host mapping left behind after host delete

[ https://issues.apache.org/jira/browse/AMBARI-21658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-21658: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to 2.5 > Chec

[jira] [Updated] (AMBARI-21658) Check for config group host mapping left behind after host delete

[ https://issues.apache.org/jira/browse/AMBARI-21658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-21658: - Status: Patch Available (was: Open) > Check for config group host mapping left behind a

[jira] [Updated] (AMBARI-21658) Check for config group host mapping left behind after host delete

[ https://issues.apache.org/jira/browse/AMBARI-21658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-21658: - Attachment: AMBARI-21658.patch > Check for config group host mapping left behind after h

[jira] [Updated] (AMBARI-21658) Check for config group host mapping left behind after host delete

[ https://issues.apache.org/jira/browse/AMBARI-21658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-21658: - Summary: Check for config group host mapping left behind after host delete (was: Addres

[jira] [Created] (AMBARI-21658) Address config group host mapping left behind after host delete

Siddharth Wagle created AMBARI-21658: Summary: Address config group host mapping left behind after host delete Key: AMBARI-21658 URL: https://issues.apache.org/jira/browse/AMBARI-21658 Project: Am

[jira] [Comment Edited] (AMBARI-21607) Hive can not write to session directory after upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113859#comment-16113859 ] Eric Yang edited comment on AMBARI-21607 at 8/4/17 3:20 AM:

[jira] [Assigned] (AMBARI-21607) Hive can not write to session directory after upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Yang reassigned AMBARI-21607: -- Assignee: Doroszlai, Attila (was: Siddharth Wagle) > Hive can not write to session directory

[jira] [Commented] (AMBARI-21607) Hive can not write to session directory after upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113859#comment-16113859 ] Eric Yang commented on AMBARI-21607: [~adoroszlai] Could you add a way to maintain h

[jira] [Created] (AMBARI-21657) Ambari does not display metric data on widgets when the JMX path contains the '-' character.

Aravindan Vijayan created AMBARI-21657: -- Summary: Ambari does not display metric data on widgets when the JMX path contains the '-' character. Key: AMBARI-21657 URL: https://issues.apache.org/jira/browse/AMBA

[jira] [Commented] (AMBARI-21554) Regenerating keytabs fails in Stack Advisor after upgrading Ambari

[ https://issues.apache.org/jira/browse/AMBARI-21554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113546#comment-16113546 ] Hudson commented on AMBARI-21554: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.

[jira] [Updated] (AMBARI-21328) NameNode alerts in Unknown state after Ambari upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-21328: --- Fix Version/s: 2.5.2 > NameNode alerts in Unknown state after Ambari upgrade > -

[jira] [Updated] (AMBARI-21328) NameNode alerts in Unknown state after Ambari upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-21328: --- Affects Version/s: 2.5.1 > NameNode alerts in Unknown state after Ambari upgrade > -

[jira] [Updated] (AMBARI-21554) Regenerating keytabs fails in Stack Advisor after upgrading Ambari

[ https://issues.apache.org/jira/browse/AMBARI-21554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-21554: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to [br

[jira] [Commented] (AMBARI-21607) Hive can not write to session directory after upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113488#comment-16113488 ] Doroszlai, Attila commented on AMBARI-21607: [~eyang], Hive shell issue is f

[jira] [Updated] (AMBARI-21654) Post Ambari upgrade, BI value add 4.2 services should still be able to restart

[ https://issues.apache.org/jira/browse/AMBARI-21654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-21654: --- Status: Patch Available (was: Open) > Post Ambari upgrade, BI value add 4.2 services should still be able t

[jira] [Created] (AMBARI-21656) Patch/Service Downgrades Are Not Correctly Scoped

Jonathan Hurley created AMBARI-21656: Summary: Patch/Service Downgrades Are Not Correctly Scoped Key: AMBARI-21656 URL: https://issues.apache.org/jira/browse/AMBARI-21656 Project: Ambari

[jira] [Updated] (AMBARI-21654) Post Ambari upgrade, BI value add 4.2 services should still be able to restart

[ https://issues.apache.org/jira/browse/AMBARI-21654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-21654: --- Attachment: AMBARI-21654.patch > Post Ambari upgrade, BI value add 4.2 services should still be able to rest

[jira] [Created] (AMBARI-21655) Add Upgrade Mpack Recommendations

Jayush Luniya created AMBARI-21655: -- Summary: Add Upgrade Mpack Recommendations Key: AMBARI-21655 URL: https://issues.apache.org/jira/browse/AMBARI-21655 Project: Ambari Issue Type: Bug

[jira] [Commented] (AMBARI-21625) Failed to update custom repos defined via service extension after such a service is installed to cluster

[ https://issues.apache.org/jira/browse/AMBARI-21625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113401#comment-16113401 ] Di Li commented on AMBARI-21625: Hi Balázs Bence Sári , my QA is verifying a new set o

[jira] [Updated] (AMBARI-21558) Software Registry Recommendations API

[ https://issues.apache.org/jira/browse/AMBARI-21558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-21558: --- Status: Patch Available (was: In Progress) > Software Registry Recommendations API > --

[jira] [Updated] (AMBARI-21558) Software Registry Recommendations API

[ https://issues.apache.org/jira/browse/AMBARI-21558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-21558: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Software Registry Recom

[jira] [Created] (AMBARI-21654) Post Ambari upgrade, BI value add 4.2 services should still be able to restart

Di Li created AMBARI-21654: -- Summary: Post Ambari upgrade, BI value add 4.2 services should still be able to restart Key: AMBARI-21654 URL: https://issues.apache.org/jira/browse/AMBARI-21654 Project: Ambari

[jira] [Commented] (AMBARI-21607) Hive can not write to session directory after upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113307#comment-16113307 ] Eric Yang commented on AMBARI-21607: The correct solution is to make sure Hive is co

[jira] [Commented] (AMBARI-21643) Annotate upgrade packs for scope

[ https://issues.apache.org/jira/browse/AMBARI-21643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113240#comment-16113240 ] Hudson commented on AMBARI-21643: - FAILURE: Integrated in Jenkins build Ambari-trunk-Com

[jira] [Commented] (AMBARI-21653) Create VDF and xsd to support MAINT upgrades

[ https://issues.apache.org/jira/browse/AMBARI-21653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113239#comment-16113239 ] Hudson commented on AMBARI-21653: - FAILURE: Integrated in Jenkins build Ambari-trunk-Com

[jira] [Commented] (AMBARI-21554) Regenerating keytabs fails in Stack Advisor after upgrading Ambari

[ https://issues.apache.org/jira/browse/AMBARI-21554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113236#comment-16113236 ] Hadoop QA commented on AMBARI-21554: {color:red}-1 overall{color}. Here are the res

[jira] [Commented] (AMBARI-21648) Do not use 'dbo' schema name in idempotent Ambari DDL generator for AzureDB.

[ https://issues.apache.org/jira/browse/AMBARI-21648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113191#comment-16113191 ] Hadoop QA commented on AMBARI-21648: {color:red}-1 overall{color}. Here are the res

[jira] [Updated] (AMBARI-21643) Annotate upgrade packs for scope

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

[jira] [Commented] (AMBARI-21640) Certain templated Grafana dashboards not showing data.

[ https://issues.apache.org/jira/browse/AMBARI-21640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113135#comment-16113135 ] Hudson commented on AMBARI-21640: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.

[jira] [Commented] (AMBARI-21640) Certain templated Grafana dashboards not showing data.

[ https://issues.apache.org/jira/browse/AMBARI-21640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113125#comment-16113125 ] Hudson commented on AMBARI-21640: - FAILURE: Integrated in Jenkins build Ambari-trunk-Com

[jira] [Commented] (AMBARI-21650) Ranger Usersync process starts with older stack script during cross stack upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113098#comment-16113098 ] Hadoop QA commented on AMBARI-21650: {color:red}-1 overall{color}. Here are the res

[jira] [Updated] (AMBARI-21640) Certain templated Grafana dashboards not showing data.

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

[jira] [Resolved] (AMBARI-21591) Send execution commands to agents user topic via STOMP

[ https://issues.apache.org/jira/browse/AMBARI-21591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myroslav Papirkovskyi resolved AMBARI-21591. Resolution: Fixed Pushed to branch-3.0-perf > Send execution commands to

[jira] [Created] (AMBARI-21653) Create VDF and xsd to support MAINT upgrades

Nate Cole created AMBARI-21653: -- Summary: Create VDF and xsd to support MAINT upgrades Key: AMBARI-21653 URL: https://issues.apache.org/jira/browse/AMBARI-21653 Project: Ambari Issue Type: Task

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

[ https://issues.apache.org/jira/browse/AMBARI-21651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reopened AMBARI-21651: -- additional commit required > Backport AMBARI-12556 UI Work For Patch/Service Upg

[jira] [Resolved] (AMBARI-21600) Grafana Kafka-Topic dashboard is forming incorrect url 'NaNundefined' appended

[ https://issues.apache.org/jira/browse/AMBARI-21600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-21600. Resolution: Duplicate > Grafana Kafka-Topic dashboard is forming incorrect url 'Na

[jira] [Updated] (AMBARI-21652) Upgrade History Page Doesn't Display After Performing a PATCH Upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21652: - Resolution: Fixed Status: Resolved (was: Patch Available) > Upgrade His

[jira] [Commented] (AMBARI-21652) Upgrade History Page Doesn't Display After Performing a PATCH Upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112776#comment-16112776 ] Antonenko Alexander commented on AMBARI-21652: -- test failed cuz of wrong br

[jira] [Commented] (AMBARI-21652) Upgrade History Page Doesn't Display After Performing a PATCH Upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112777#comment-16112777 ] Antonenko Alexander commented on AMBARI-21652: -- committed to branch-feature

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

[ https://issues.apache.org/jira/browse/AMBARI-21651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21651: - Affects Version/s: (was: 2.6.0) 2.5.3 > Backport AMBA

[jira] [Assigned] (AMBARI-21652) Upgrade History Page Doesn't Display After Performing a PATCH Upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-21652: Assignee: Antonenko Alexander > Upgrade History Page Doesn't Display Afte

[jira] [Commented] (AMBARI-21652) Upgrade History Page Doesn't Display After Performing a PATCH Upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112775#comment-16112775 ] Andrii Tkach commented on AMBARI-21652: --- +1 for the patch > Upgrade History Page

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

[ https://issues.apache.org/jira/browse/AMBARI-21651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21651: - Fix Version/s: (was: 2.6.0) 2.5.3 > Backport AMBARI-12556

[jira] [Commented] (AMBARI-21652) Upgrade History Page Doesn't Display After Performing a PATCH Upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112774#comment-16112774 ] Hadoop QA commented on AMBARI-21652: {color:red}-1 overall{color}. Here are the res

[jira] [Updated] (AMBARI-21652) Upgrade History Page Doesn't Display After Performing a PATCH Upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21652: - Fix Version/s: (was: 2.6.0) 2.5.3 > Upgrade History Page

[jira] [Updated] (AMBARI-21652) Upgrade History Page Doesn't Display After Performing a PATCH Upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21652: - Affects Version/s: (was: 2.6.0) 2.5.3 > Upgrade Histo

[jira] [Updated] (AMBARI-21652) Upgrade History Page Doesn't Display After Performing a PATCH Upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21652: - Attachment: AMBARI-21652.patch > Upgrade History Page Doesn't Display After Perf

[jira] [Updated] (AMBARI-21652) Upgrade History Page Doesn't Display After Performing a PATCH Upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21652: - Status: Patch Available (was: Open) > Upgrade History Page Doesn't Display Afte

[jira] [Created] (AMBARI-21652) Upgrade History Page Doesn't Display After Performing a PATCH Upgrade

Antonenko Alexander created AMBARI-21652: Summary: Upgrade History Page Doesn't Display After Performing a PATCH Upgrade Key: AMBARI-21652 URL: https://issues.apache.org/jira/browse/AMBARI-21652

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

[ https://issues.apache.org/jira/browse/AMBARI-21651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112725#comment-16112725 ] Antonenko Alexander commented on AMBARI-21651: -- committed to branch-featur

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

[ https://issues.apache.org/jira/browse/AMBARI-21651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21651: - Resolution: Fixed Status: Resolved (was: Patch Available) > Backport AM

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

[ https://issues.apache.org/jira/browse/AMBARI-21651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112721#comment-16112721 ] Antonenko Alexander commented on AMBARI-21651: -- test failed cuz of wrong br

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

[ https://issues.apache.org/jira/browse/AMBARI-21651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112719#comment-16112719 ] Hadoop QA commented on AMBARI-21651: {color:red}-1 overall{color}. Here are the res

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

[ https://issues.apache.org/jira/browse/AMBARI-21651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-21651: Assignee: Antonenko Alexander > Backport AMBARI-12556 UI Work For Patch/S

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

[ https://issues.apache.org/jira/browse/AMBARI-21651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112717#comment-16112717 ] Oleg Nechiporenko commented on AMBARI-21651: +1 for patch > Backport AMBARI

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

[ https://issues.apache.org/jira/browse/AMBARI-21651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21651: - Status: Patch Available (was: Open) > Backport AMBARI-12556 UI Work For Patch/S

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

[ https://issues.apache.org/jira/browse/AMBARI-21651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21651: - Attachment: AMBARI-21651.patch > Backport AMBARI-12556 UI Work For Patch/Service

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

Antonenko Alexander created AMBARI-21651: Summary: Backport AMBARI-12556 UI Work For Patch/Service Upgrades Key: AMBARI-21651 URL: https://issues.apache.org/jira/browse/AMBARI-21651 Project: Am

[jira] [Assigned] (AMBARI-21600) Grafana Kafka-Topic dashboard is forming incorrect url 'NaNundefined' appended

[ https://issues.apache.org/jira/browse/AMBARI-21600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JaySenSharma reassigned AMBARI-21600: - Assignee: Aravindan Vijayan (was: JaySenSharma) > Grafana Kafka-Topic dashboard is for

[jira] [Updated] (AMBARI-21650) Ranger Usersync process starts with older stack script during cross stack upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-21650: - Status: Patch Available (was: In Progress) > Ranger Usersync process starts with older

[jira] [Updated] (AMBARI-21650) Ranger Usersync process starts with older stack script during cross stack upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-21650: - Attachment: AMBARI-21650.patch > Ranger Usersync process starts with older stack script

[jira] [Updated] (AMBARI-21648) Do not use 'dbo' schema name in idempotent Ambari DDL generator for AzureDB.

[ https://issues.apache.org/jira/browse/AMBARI-21648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-21648: -- Status: Patch Available (was: In Progress) > Do not use 'dbo' schema name in idempote

[jira] [Updated] (AMBARI-21648) Do not use 'dbo' schema name in idempotent Ambari DDL generator for AzureDB.

[ https://issues.apache.org/jira/browse/AMBARI-21648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-21648: -- Attachment: AMBARI-21648.v1.patch > Do not use 'dbo' schema name in idempotent Ambari

[jira] [Updated] (AMBARI-21648) Do not use 'dbo' schema name in idempotent Ambari DDL generator for AzureDB.

[ https://issues.apache.org/jira/browse/AMBARI-21648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-21648: -- Fix Version/s: (was: 2.5.3) 2.6.0 > Do not use 'dbo' schema nam

[jira] [Created] (AMBARI-21650) Ranger Usersync process starts with older stack script during cross stack upgrade

Mugdha Varadkar created AMBARI-21650: Summary: Ranger Usersync process starts with older stack script during cross stack upgrade Key: AMBARI-21650 URL: https://issues.apache.org/jira/browse/AMBARI-21650

[jira] [Updated] (AMBARI-21554) Regenerating keytabs fails in Stack Advisor after upgrading Ambari

[ https://issues.apache.org/jira/browse/AMBARI-21554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-21554: --- Status: Patch Available (was: In Progress) > Regenerating keytabs fails in Stack Ad

[jira] [Updated] (AMBARI-21554) Regenerating keytabs fails in Stack Advisor after upgrading Ambari

[ https://issues.apache.org/jira/browse/AMBARI-21554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-21554: --- Attachment: AMBARI-21554.patch > Regenerating keytabs fails in Stack Advisor after u

[jira] [Created] (AMBARI-21649) Update Atlas log4j to reflect latest configurations

Vishal Suvagia created AMBARI-21649: --- Summary: Update Atlas log4j to reflect latest configurations Key: AMBARI-21649 URL: https://issues.apache.org/jira/browse/AMBARI-21649 Project: Ambari

[jira] [Updated] (AMBARI-21554) Regenerating keytabs fails in Stack Advisor after upgrading Ambari

[ https://issues.apache.org/jira/browse/AMBARI-21554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-21554: --- Fix Version/s: (was: 2.5.3) 2.5.2 > Regenerating keytabs fail

[jira] [Updated] (AMBARI-21554) Regenerating keytabs fails in Stack Advisor after upgrading Ambari

[ https://issues.apache.org/jira/browse/AMBARI-21554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-21554: --- Summary: Regenerating keytabs fails in Stack Advisor after upgrading Ambari (was: C

[jira] [Commented] (AMBARI-21625) Failed to update custom repos defined via service extension after such a service is installed to cluster

[ https://issues.apache.org/jira/browse/AMBARI-21625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112657#comment-16112657 ] Balázs Bence Sári commented on AMBARI-21625: Hey [~dili], extension repo's w

[jira] [Commented] (AMBARI-21621) Do not call refreshnodes command after deleting a slave

[ https://issues.apache.org/jira/browse/AMBARI-21621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112651#comment-16112651 ] Hudson commented on AMBARI-21621: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.

[jira] [Assigned] (AMBARI-21554) Cross-stack upgrade, regenerating keytabs after upgrading Ambari fails in Stack Advisor

[ https://issues.apache.org/jira/browse/AMBARI-21554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila reassigned AMBARI-21554: -- Assignee: Doroszlai, Attila > Cross-stack upgrade, regenerating keytabs after

[jira] [Commented] (AMBARI-21621) Do not call refreshnodes command after deleting a slave

[ https://issues.apache.org/jira/browse/AMBARI-21621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112646#comment-16112646 ] Hudson commented on AMBARI-21621: - FAILURE: Integrated in Jenkins build Ambari-trunk-Com

[jira] [Created] (AMBARI-21648) Do not use 'dbo' schema name in idempotent Ambari DDL generator for AzureDB.

Sebastian Toader created AMBARI-21648: - Summary: Do not use 'dbo' schema name in idempotent Ambari DDL generator for AzureDB. Key: AMBARI-21648 URL: https://issues.apache.org/jira/browse/AMBARI-21648

[jira] [Updated] (AMBARI-21647) PATCH upgrade with version less than current should be displayed

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

[jira] [Commented] (AMBARI-21647) PATCH upgrade with version less than current should be displayed

[ https://issues.apache.org/jira/browse/AMBARI-21647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112625#comment-16112625 ] Andrii Tkach commented on AMBARI-21647: --- committed to branch-feature-AMBARI-21450

[jira] [Updated] (AMBARI-21621) Do not call refreshnodes command after deleting a slave

[ https://issues.apache.org/jira/browse/AMBARI-21621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-21621: Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk and branch-2.5

[jira] [Updated] (AMBARI-21646) Race condition causing execution commands to fail

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

[jira] [Commented] (AMBARI-21647) PATCH upgrade with version less than current should be displayed

[ https://issues.apache.org/jira/browse/AMBARI-21647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112580#comment-16112580 ] Andrii Babiichuk commented on AMBARI-21647: --- +1 for the patch > PATCH upgrade

[jira] [Commented] (AMBARI-21647) PATCH upgrade with version less than current should be displayed

[ https://issues.apache.org/jira/browse/AMBARI-21647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112578#comment-16112578 ] Hadoop QA commented on AMBARI-21647: {color:red}-1 overall{color}. Here are the res

[jira] [Commented] (AMBARI-21647) PATCH upgrade with version less than current should be displayed

[ https://issues.apache.org/jira/browse/AMBARI-21647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112575#comment-16112575 ] Andrii Tkach commented on AMBARI-21647: --- 30404 passing (26s) 157 pending > PATC

[jira] [Updated] (AMBARI-21647) PATCH upgrade with version less than current should be displayed

[ https://issues.apache.org/jira/browse/AMBARI-21647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21647: -- Status: Patch Available (was: Open) > PATCH upgrade with version less than current should be

[jira] [Updated] (AMBARI-21647) PATCH upgrade with version less than current should be displayed

[ https://issues.apache.org/jira/browse/AMBARI-21647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21647: -- Attachment: AMBARI-21647.patch > PATCH upgrade with version less than current should be displa

[jira] [Created] (AMBARI-21647) PATCH upgrade with version less than current should be displayed

Andrii Tkach created AMBARI-21647: - Summary: PATCH upgrade with version less than current should be displayed Key: AMBARI-21647 URL: https://issues.apache.org/jira/browse/AMBARI-21647 Project: Ambari

[jira] [Commented] (AMBARI-21613) Dynamically determine what keytab files have been distributed

[ https://issues.apache.org/jira/browse/AMBARI-21613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112556#comment-16112556 ] Hudson commented on AMBARI-21613: - FAILURE: Integrated in Jenkins build Ambari-trunk-Com

[jira] [Commented] (AMBARI-21621) Do not call refreshnodes command after deleting a slave

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

[jira] [Updated] (AMBARI-21613) Dynamically determine what keytab files have been distributed

[ https://issues.apache.org/jira/browse/AMBARI-21613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar updated AMBARI-21613: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Dynamically determine w

[jira] [Commented] (AMBARI-21497) Conflicts in the ambari config groups

[ https://issues.apache.org/jira/browse/AMBARI-21497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112519#comment-16112519 ] Hudson commented on AMBARI-21497: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.

  1   2   >