[jira] [Commented] (AMBARI-21418) Ambari rebuilds custom auth_to_local rules changing its case sensitiveness option (/L) depending on the case_insensitive_username_rules.

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

[jira] [Created] (AMBARI-21708) History Server cannot be started due to wrong permissions of /mr-history

Doroszlai, Attila created AMBARI-21708: -- Summary: History Server cannot be started due to wrong permissions of /mr-history Key: AMBARI-21708 URL: https://issues.apache.org/jira/browse/AMBARI-21708

[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: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Do not use 'dbo'

[jira] [Resolved] (AMBARI-21116) Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission of the "root path"

[ https://issues.apache.org/jira/browse/AMBARI-21116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila resolved AMBARI-21116. Resolution: Fixed Nevermind, will fix in AMBARI-21708. > Setting

[jira] [Commented] (AMBARI-21704) Upgrade Wizard Has Incorrect Title

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

[jira] [Updated] (AMBARI-21704) Upgrade Wizard Has Incorrect Title

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

[jira] [Updated] (AMBARI-21708) History Server cannot be started due to wrong permissions of /mr-history

[ https://issues.apache.org/jira/browse/AMBARI-21708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-21708: --- Status: Patch Available (was: In Progress) > History Server cannot be started due

[jira] [Updated] (AMBARI-21708) History Server cannot be started due to wrong permissions of /mr-history

[ https://issues.apache.org/jira/browse/AMBARI-21708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-21708: --- Attachment: AMBARI-21708.patch > History Server cannot be started due to wrong

[jira] [Updated] (AMBARI-21709) Finalize Warns that it is Permanent Even For PATCH Upgrades

[ https://issues.apache.org/jira/browse/AMBARI-21709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21709: -- Attachment: Screen Shot 2017-08-03 at 2.01.52 PM.png > Finalize Warns that it is Permanent

[jira] [Commented] (AMBARI-21619) More ResourceManager HA host group placeholders in blueprints

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

[jira] [Created] (AMBARI-21709) Finalize Warns that it is Permanent Even For PATCH Upgrades

Andrii Tkach created AMBARI-21709: - Summary: Finalize Warns that it is Permanent Even For PATCH Upgrades Key: AMBARI-21709 URL: https://issues.apache.org/jira/browse/AMBARI-21709 Project: Ambari

[jira] [Commented] (AMBARI-21608) Spark shell is not working after upgrade

[ https://issues.apache.org/jira/browse/AMBARI-21608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123214#comment-16123214 ] Doroszlai, Attila commented on AMBARI-21608: Reproduced on BI 4.2 _before_ any upgrade.

[jira] [Updated] (AMBARI-21619) More ResourceManager HA host group placeholders in blueprints

[ https://issues.apache.org/jira/browse/AMBARI-21619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-21619: --- Fix Version/s: (was: trunk) > More ResourceManager HA host group placeholders

[jira] [Commented] (AMBARI-21619) More ResourceManager HA host group placeholders in blueprints

[ https://issues.apache.org/jira/browse/AMBARI-21619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123244#comment-16123244 ] Doroszlai, Attila commented on AMBARI-21619: Committed to

[jira] [Updated] (AMBARI-21709) Finalize Warns that it is Permanent Even For PATCH Upgrades

[ https://issues.apache.org/jira/browse/AMBARI-21709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21709: -- Attachment: AMBARI-21709.patch > Finalize Warns that it is Permanent Even For PATCH Upgrades

[jira] [Commented] (AMBARI-21709) Finalize Warns that it is Permanent Even For PATCH Upgrades

[ https://issues.apache.org/jira/browse/AMBARI-21709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123362#comment-16123362 ] Andrii Tkach commented on AMBARI-21709: --- 30464 passing (25s) 157 pending > Finalize Warns that

[jira] [Updated] (AMBARI-21709) Finalize Warns that it is Permanent Even For PATCH Upgrades

[ https://issues.apache.org/jira/browse/AMBARI-21709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21709: -- Status: Patch Available (was: Open) > Finalize Warns that it is Permanent Even For PATCH

[jira] [Updated] (AMBARI-21692) dfs.include file is created on all datanode hosts when Ambari manages include/exclude files

[ https://issues.apache.org/jira/browse/AMBARI-21692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-21692: Attachment: AMBARI-21692_2.patch > dfs.include file is created on all datanode hosts when Ambari

[jira] [Commented] (AMBARI-21692) dfs.include file is created on all datanode hosts when Ambari manages include/exclude files

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

[jira] [Commented] (AMBARI-21692) dfs.include file is created on all datanode hosts when Ambari manages include/exclude files

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

[jira] [Commented] (AMBARI-21692) dfs.include file is created on all datanode hosts when Ambari manages include/exclude files

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

[jira] [Commented] (AMBARI-21692) dfs.include file is created on all datanode hosts when Ambari manages include/exclude files

[ https://issues.apache.org/jira/browse/AMBARI-21692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123209#comment-16123209 ] Dmytro Sen commented on AMBARI-21692: - Test failure is not caused by the commit > dfs.include file

[jira] [Updated] (AMBARI-21703) UI must consume API to show whether a service will be upgraded

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

[jira] [Commented] (AMBARI-21682) Patched Service Doesn't Display Correct Hadoop Version on Stacks Page

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

[jira] [Updated] (AMBARI-21703) UI must consume API to show whether a service will be upgraded

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

[jira] [Updated] (AMBARI-21703) UI must consume API to show whether a service will be upgraded

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

[jira] [Commented] (AMBARI-21703) UI must consume API to show whether a service will be upgraded

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

[jira] [Updated] (AMBARI-21076) Move superset as a top-level module in HDP

[ https://issues.apache.org/jira/browse/AMBARI-21076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21076: -- Status: Patch Available (was: Open) > Move superset as a top-level module in HDP >

[jira] [Issue Comment Deleted] (AMBARI-21682) Patched Service Doesn't Display Correct Hadoop Version on Stacks Page

[ https://issues.apache.org/jira/browse/AMBARI-21682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21682: - Comment: was deleted (was: committed to branch-feature-AMBARI-21450 ) >

[jira] [Commented] (AMBARI-21703) UI must consume API to show whether a service will be upgraded

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

[jira] [Commented] (AMBARI-21692) dfs.include file is created on all datanode hosts when Ambari manages include/exclude files

[ https://issues.apache.org/jira/browse/AMBARI-21692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123163#comment-16123163 ] Dmytro Sen commented on AMBARI-21692: - Committed to trunk, branch-2.5, branch-2.6 > dfs.include

[jira] [Updated] (AMBARI-21692) dfs.include file is created on all datanode hosts when Ambari manages include/exclude files

[ https://issues.apache.org/jira/browse/AMBARI-21692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-21692: Resolution: Fixed Status: Resolved (was: Patch Available) > dfs.include file is created

[jira] [Updated] (AMBARI-21076) Move superset as a top-level module in HDP

[ https://issues.apache.org/jira/browse/AMBARI-21076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21076: -- Attachment: AMBARI-21076.1.patch > Move superset as a top-level module in HDP >

[jira] [Updated] (AMBARI-21076) Move superset as a top-level module in HDP

[ https://issues.apache.org/jira/browse/AMBARI-21076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21076: -- Status: Open (was: Patch Available) > Move superset as a top-level module in HDP >

[jira] [Updated] (AMBARI-21703) UI must consume API to show whether a service will be upgraded

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

[jira] [Updated] (AMBARI-21703) UI must consume API to show whether a service will be upgraded

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

[jira] [Commented] (AMBARI-21703) UI must consume API to show whether a service will be upgraded

[ https://issues.apache.org/jira/browse/AMBARI-21703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123230#comment-16123230 ] Antonenko Alexander commented on AMBARI-21703: -- PATCH APPLICATION FAILED as it was applied

[jira] [Updated] (AMBARI-21702) ambari-agent registration fails due to invalid public hostname

[ https://issues.apache.org/jira/browse/AMBARI-21702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Davie updated AMBARI-21702: --- Description: * The script {{hostname.py}}

[jira] [Assigned] (AMBARI-21630) Delete datanode operation shows up as Decommission in bgops

[ https://issues.apache.org/jira/browse/AMBARI-21630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan reassigned AMBARI-21630: -- Assignee: Dmytro Sen > Delete datanode operation shows up as Decommission in

[jira] [Resolved] (AMBARI-21631) Hostname and operation shown in bgops is incorrect when Ambari manages include/exclude files

[ https://issues.apache.org/jira/browse/AMBARI-21631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-21631. Resolution: Duplicate Assignee: Dmytro Sen > Hostname and operation shown

[jira] [Commented] (AMBARI-21471) ATS going down due to missing org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin

[ https://issues.apache.org/jira/browse/AMBARI-21471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124153#comment-16124153 ] Aravindan Vijayan commented on AMBARI-21471: [~sumitmohanty] Is there any other work work

[jira] [Commented] (AMBARI-21706) Fix exception messages whenever empty host list is passed in predicate.

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

[jira] [Commented] (AMBARI-21076) Move superset as a top-level module in HDP

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

[jira] [Commented] (AMBARI-21708) History Server cannot be started due to wrong permissions of /mr-history

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

[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=16124145#comment-16124145 ] Aravindan Vijayan commented on AMBARI-21345: [~dsen] What is the status of the jira? > Add

[jira] [Commented] (AMBARI-21045) Enable Storm's AutoTGT configs in secure mode

[ https://issues.apache.org/jira/browse/AMBARI-21045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124160#comment-16124160 ] Aravindan Vijayan commented on AMBARI-21045: [~sriharsha] Is there any work pending on this

[jira] [Updated] (AMBARI-21471) ATS going down due to missing org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin

[ https://issues.apache.org/jira/browse/AMBARI-21471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-21471: --- Resolution: Fixed Status: Resolved (was: Patch Available) > ATS going down due to

[jira] [Commented] (AMBARI-21706) Fix exception messages whenever empty host list is passed in predicate.

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

[jira] [Updated] (AMBARI-21512) Stack Advisor reported an error: KeyError: 'stack_name' while Issued INSTALLED as new state for NODEMANAGER

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

[jira] [Resolved] (AMBARI-21630) Delete datanode operation shows up as Decommission in bgops

[ https://issues.apache.org/jira/browse/AMBARI-21630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-21630. Resolution: Duplicate > Delete datanode operation shows up as Decommission in

[jira] [Updated] (AMBARI-21706) Fix exception messages whenever empty host list is passed in predicate.

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

[jira] [Commented] (AMBARI-21110) ambari-server setup fails with default postgres

[ https://issues.apache.org/jira/browse/AMBARI-21110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124159#comment-16124159 ] Aravindan Vijayan commented on AMBARI-21110: [~aonishuk] Can you commit this to branch-2.5

[jira] [Comment Edited] (AMBARI-21471) ATS going down due to missing org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin

[ https://issues.apache.org/jira/browse/AMBARI-21471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124153#comment-16124153 ] Aravindan Vijayan edited comment on AMBARI-21471 at 8/11/17 9:55 PM: -

[jira] [Created] (AMBARI-21710) Yarn-Queues dashboard not displaying data in Grafana.

Aravindan Vijayan created AMBARI-21710: -- Summary: Yarn-Queues dashboard not displaying data in Grafana. Key: AMBARI-21710 URL: https://issues.apache.org/jira/browse/AMBARI-21710 Project: Ambari

[jira] [Updated] (AMBARI-21710) Yarn-Queues dashboard not displaying data in Grafana.

[ https://issues.apache.org/jira/browse/AMBARI-21710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-21710: --- Description: There is no data or error saying 'timeseries data request error'. The

[jira] [Commented] (AMBARI-21711) Seeing SQL errors in ambari server log when installing HDF 3.1

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

[jira] [Created] (AMBARI-21711) Seeing SQL errors in ambari server log when installing HDF 3.1

Sumit Mohanty created AMBARI-21711: -- Summary: Seeing SQL errors in ambari server log when installing HDF 3.1 Key: AMBARI-21711 URL: https://issues.apache.org/jira/browse/AMBARI-21711 Project: Ambari

[jira] [Updated] (AMBARI-21711) Seeing SQL errors in ambari server log when installing HDF 3.1

[ https://issues.apache.org/jira/browse/AMBARI-21711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-21711: --- Attachment: AMBARI-21711.patch > Seeing SQL errors in ambari server log when installing HDF

[jira] [Commented] (AMBARI-21711) Seeing SQL errors in ambari server log when installing HDF 3.1

[ https://issues.apache.org/jira/browse/AMBARI-21711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124238#comment-16124238 ] Jonathan Hurley commented on AMBARI-21711: -- +1 > Seeing SQL errors in ambari server log when

[jira] [Resolved] (AMBARI-21711) Seeing SQL errors in ambari server log when installing HDF 3.1

[ https://issues.apache.org/jira/browse/AMBARI-21711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved AMBARI-21711. Resolution: Fixed Committed to trunk, branch-2.5, branch-2.6 > Seeing SQL errors in

[jira] [Updated] (AMBARI-21710) Yarn-Queues dashboard not displaying data in Grafana.

[ https://issues.apache.org/jira/browse/AMBARI-21710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-21710: --- Fix Version/s: (was: 2.6.0) 2.5.2 > Yarn-Queues dashboard

[jira] [Updated] (AMBARI-21710) Yarn-Queues dashboard not displaying data in Grafana.

[ https://issues.apache.org/jira/browse/AMBARI-21710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-21710: --- Priority: Blocker (was: Critical) > Yarn-Queues dashboard not displaying data in

[jira] [Commented] (AMBARI-21711) Seeing SQL errors in ambari server log when installing HDF 3.1

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

[jira] [Commented] (AMBARI-21711) Seeing SQL errors in ambari server log when installing HDF 3.1

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

[jira] [Updated] (AMBARI-21702) ambari-agent registration fails due to invalid public hostname

[ https://issues.apache.org/jira/browse/AMBARI-21702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Davie updated AMBARI-21702: --- Description: * The script {{hostname.py}}

[jira] [Updated] (AMBARI-21702) ambari-agent registration fails due to invalid public hostname

[ https://issues.apache.org/jira/browse/AMBARI-21702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Davie updated AMBARI-21702: --- Priority: Critical (was: Major) > ambari-agent registration fails due to invalid public

[jira] [Commented] (AMBARI-21709) Finalize Warns that it is Permanent Even For PATCH Upgrades

[ https://issues.apache.org/jira/browse/AMBARI-21709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123422#comment-16123422 ] Andrii Babiichuk commented on AMBARI-21709: --- +1 for the patch > Finalize Warns that it is

[jira] [Commented] (AMBARI-21709) Finalize Warns that it is Permanent Even For PATCH Upgrades

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

[jira] [Updated] (AMBARI-21709) Finalize Warns that it is Permanent Even For PATCH Upgrades

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