[jira] [Commented] (AMBARI-21985) Option to skip Host Check during the host add wizard
[ https://issues.apache.org/jira/browse/AMBARI-21985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172644#comment-16172644 ] Hudson commented on AMBARI-21985: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8097 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8097/]) AMBARI-21985. Option to skip Host Check during the host add wizard. (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=878dc6ac72b9d5d87a5f6c21991290886459eede]) * (edit) ambari-web/app/config.js * (edit) ambari-web/app/controllers/wizard/step2_controller.js * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/mixins/main/host/details/actions/check_host.js * (edit) ambari-web/app/templates/wizard/step2.hbs * (edit) ambari-web/app/views/wizard/step2_view.js > Option to skip Host Check during the host add wizard > > > Key: AMBARI-21985 > URL: https://issues.apache.org/jira/browse/AMBARI-21985 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk > > Attachments: AMBARI-21985.patch > > > some times we see customers were not able to add the new hosts to cluster. > message says it is checking for potential problems but it never gets > completed. because of that customers were not able to add the hosts. but > after that they were able to add the hosts with API call. This allows a the > administrator to skip Host Check after a due warning > Attach one or more files to this issue -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22001) Add service wizard stuck at step 8
[ https://issues.apache.org/jira/browse/AMBARI-22001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-22001: -- Resolution: Fixed Status: Resolved (was: Patch Available) Received +1 on reviewboard. Patch committed to trunk > Add service wizard stuck at step 8 > -- > > Key: AMBARI-22001 > URL: https://issues.apache.org/jira/browse/AMBARI-22001 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 3.0.0 > > Attachments: AMBARI-22001.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21917) Some services had issue coming up after express upgrade on IOP clusters
[
https://issues.apache.org/jira/browse/AMBARI-21917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Wagle updated AMBARI-21917:
-
Attachment: (was: AMBARI-21917.patch)
> Some services had issue coming up after express upgrade on IOP clusters
> ---
>
> Key: AMBARI-21917
> URL: https://issues.apache.org/jira/browse/AMBARI-21917
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.6.0
>
>
> The RCO cache gets cleared on an upgrade to make sure new RCO is loaded.
> However, certain test environments have reported seeing incorrect / older RCO
> still in effect after Finalize and the operations failing due to this.
> The server log does indicate RCO getting cleared:
> {code}
> 24 Aug 2017 17:15:26,701 INFO [Server Action Executor Worker 1509]
> StackUpgradeFinishListener:92 - Clearing RCO cache
> {code}
> But the initialization statements are missing. Making a defensive patch to
> for re-creation of RCO.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21966) "Next" button on "Assign Masters" page gets disabled when installing Ambari
[ https://issues.apache.org/jira/browse/AMBARI-21966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172573#comment-16172573 ] Hudson commented on AMBARI-21966: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.6 #249 (See [https://builds.apache.org/job/Ambari-branch-2.6/249/]) Revert "AMBARI-21966. "Next" button on "Assign Masters" page gets (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1140bbc077aa96df395a06a15c18cd281a3839e3]) * (edit) ambari-web/app/mixins/wizard/assign_master_components.js > "Next" button on "Assign Masters" page gets disabled when installing Ambari > --- > > Key: AMBARI-21966 > URL: https://issues.apache.org/jira/browse/AMBARI-21966 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21966_branch-2.6.patch, AMBARI-21966.patch > > > "Next" button on "Assign Masters" page (step 5) gets disabled if you revisit > the page from "Assign Slaves and Clients" page (step 6) by pressing "Back" > button when installing Ambari. > To enable the "Next" button again, we need to refresh the page in Browser. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21954) Option to skip Host Check during the host add wizard
[ https://issues.apache.org/jira/browse/AMBARI-21954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-21954: -- Resolution: Fixed Status: Resolved (was: Patch Available) Patch received +1 on reviewboard. Patch committed to branch-2.6 > Option to skip Host Check during the host add wizard > > > Key: AMBARI-21954 > URL: https://issues.apache.org/jira/browse/AMBARI-21954 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: 2.6.0 > > Attachments: AMBARI-21954_branch-2.6.patch, Skip Host Check > checkbox.png, Skip Host Check warning.png > > > some times we see customers were not able to add the new hosts to cluster. > message says it is checking for potential problems but it never gets > completed. because of that customers were not able to add the hosts. but > after that they were able to add the hosts with API call. This allows a the > administrator to skip Host Check after a due warning -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22001) Add service wizard stuck at step 8
[ https://issues.apache.org/jira/browse/AMBARI-22001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172667#comment-16172667 ] Hudson commented on AMBARI-22001: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8098 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8098/]) AMBARI-22001. Add service wizard stuck at step 8. (Jaimin) (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=87c4205c21489cfe8bab160fb82e3429c4fb832e]) * (edit) ambari-web/app/controllers/wizard/step8_controller.js > Add service wizard stuck at step 8 > -- > > Key: AMBARI-22001 > URL: https://issues.apache.org/jira/browse/AMBARI-22001 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 3.0.0 > > Attachments: AMBARI-22001.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21985) Option to skip Host Check during the host add wizard
[ https://issues.apache.org/jira/browse/AMBARI-21985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-21985: -- Resolution: Fixed Status: Resolved (was: Patch Available) Patch received +1 on reviewboard. Patch committed to trunk. > Option to skip Host Check during the host add wizard > > > Key: AMBARI-21985 > URL: https://issues.apache.org/jira/browse/AMBARI-21985 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk > > Attachments: AMBARI-21985.patch > > > some times we see customers were not able to add the new hosts to cluster. > message says it is checking for potential problems but it never gets > completed. because of that customers were not able to add the hosts. but > after that they were able to add the hosts with API call. This allows a the > administrator to skip Host Check after a due warning > Attach one or more files to this issue -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22001) Add service wizard stuck at step 8
[ https://issues.apache.org/jira/browse/AMBARI-22001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-22001: -- Attachment: AMBARI-22001.patch > Add service wizard stuck at step 8 > -- > > Key: AMBARI-22001 > URL: https://issues.apache.org/jira/browse/AMBARI-22001 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 3.0.0 > > Attachments: AMBARI-22001.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22001) Add service wizard stuck at step 8
[ https://issues.apache.org/jira/browse/AMBARI-22001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-22001: -- Status: Patch Available (was: Open) > Add service wizard stuck at step 8 > -- > > Key: AMBARI-22001 > URL: https://issues.apache.org/jira/browse/AMBARI-22001 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 3.0.0 > > Attachments: AMBARI-22001.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22001) Add service wizard stuck at step 8
Jaimin Jetly created AMBARI-22001: - Summary: Add service wizard stuck at step 8 Key: AMBARI-22001 URL: https://issues.apache.org/jira/browse/AMBARI-22001 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Jaimin Jetly Assignee: Jaimin Jetly Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21954) Option to skip Host Check during the host add wizard
[ https://issues.apache.org/jira/browse/AMBARI-21954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172635#comment-16172635 ] Hudson commented on AMBARI-21954: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.6 #250 (See [https://builds.apache.org/job/Ambari-branch-2.6/250/]) AMBARI-21954. Option to skip Host Check during the host add wizard. (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f49cf54e9655a9f99b33cce52436edf34c372676]) * (edit) ambari-web/app/controllers/wizard/step2_controller.js * (edit) ambari-web/app/config.js * (edit) ambari-web/app/controllers/wizard/step3_controller.js * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/templates/wizard/step2.hbs * (edit) ambari-web/app/views/wizard/step2_view.js > Option to skip Host Check during the host add wizard > > > Key: AMBARI-21954 > URL: https://issues.apache.org/jira/browse/AMBARI-21954 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: 2.6.0 > > Attachments: AMBARI-21954_branch-2.6.patch, Skip Host Check > checkbox.png, Skip Host Check warning.png > > > some times we see customers were not able to add the new hosts to cluster. > message says it is checking for potential problems but it never gets > completed. because of that customers were not able to add the hosts. but > after that they were able to add the hosts with API call. This allows a the > administrator to skip Host Check after a due warning -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21917) Some services had issue coming up after express upgrade on IOP clusters
[
https://issues.apache.org/jira/browse/AMBARI-21917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172485#comment-16172485
]
Hudson commented on AMBARI-21917:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8096 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8096/])
AMBARI-21917. Some services had issue coming up after express upgrade on
(swagle:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=23e080aba77ecddf69a16b973764f3bcb4b15607])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/metadata/CachedRoleCommandOrderProvider.java
> Some services had issue coming up after express upgrade on IOP clusters
> ---
>
> Key: AMBARI-21917
> URL: https://issues.apache.org/jira/browse/AMBARI-21917
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21917.patch
>
>
> The RCO cache gets cleared on an upgrade to make sure new RCO is loaded.
> However, certain test environments have reported seeing incorrect / older RCO
> still in effect after Finalize and the operations failing due to this.
> The server log does indicate RCO getting cleared:
> {code}
> 24 Aug 2017 17:15:26,701 INFO [Server Action Executor Worker 1509]
> StackUpgradeFinishListener:92 - Clearing RCO cache
> {code}
> But the initialization statements are missing. Making a defensive patch to
> for re-creation of RCO.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21917) Some services had issue coming up after express upgrade on IOP clusters
[
https://issues.apache.org/jira/browse/AMBARI-21917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Wagle updated AMBARI-21917:
-
Status: Patch Available (was: Open)
> Some services had issue coming up after express upgrade on IOP clusters
> ---
>
> Key: AMBARI-21917
> URL: https://issues.apache.org/jira/browse/AMBARI-21917
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21917.patch
>
>
> The RCO cache gets cleared on an upgrade to make sure new RCO is loaded.
> However, certain test environments have reported seeing incorrect / older RCO
> still in effect after Finalize and the operations failing due to this.
> The server log does indicate RCO getting cleared:
> {code}
> 24 Aug 2017 17:15:26,701 INFO [Server Action Executor Worker 1509]
> StackUpgradeFinishListener:92 - Clearing RCO cache
> {code}
> But the initialization statements are missing. Making a defensive patch to
> for re-creation of RCO.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21917) Some services had issue coming up after express upgrade on IOP clusters
[
https://issues.apache.org/jira/browse/AMBARI-21917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Wagle updated AMBARI-21917:
-
Attachment: AMBARI-21917.patch
> Some services had issue coming up after express upgrade on IOP clusters
> ---
>
> Key: AMBARI-21917
> URL: https://issues.apache.org/jira/browse/AMBARI-21917
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21917.patch
>
>
> The RCO cache gets cleared on an upgrade to make sure new RCO is loaded.
> However, certain test environments have reported seeing incorrect / older RCO
> still in effect after Finalize and the operations failing due to this.
> The server log does indicate RCO getting cleared:
> {code}
> 24 Aug 2017 17:15:26,701 INFO [Server Action Executor Worker 1509]
> StackUpgradeFinishListener:92 - Clearing RCO cache
> {code}
> But the initialization statements are missing. Making a defensive patch to
> for re-creation of RCO.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21917) Some services had issue coming up after express upgrade on IOP clusters
[
https://issues.apache.org/jira/browse/AMBARI-21917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172400#comment-16172400
]
Siddharth Wagle commented on AMBARI-21917:
--
Speculative patch awaiting test results.
> Some services had issue coming up after express upgrade on IOP clusters
> ---
>
> Key: AMBARI-21917
> URL: https://issues.apache.org/jira/browse/AMBARI-21917
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21917.patch
>
>
> The RCO cache gets cleared on an upgrade to make sure new RCO is loaded.
> However, certain test environments have reported seeing incorrect / older RCO
> still in effect after Finalize and the operations failing due to this.
> The server log does indicate RCO getting cleared:
> {code}
> 24 Aug 2017 17:15:26,701 INFO [Server Action Executor Worker 1509]
> StackUpgradeFinishListener:92 - Clearing RCO cache
> {code}
> But the initialization statements are missing. Making a defensive patch to
> for re-creation of RCO.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-22000) Select Hosts page while enabling HSI does not load
[ https://issues.apache.org/jira/browse/AMBARI-22000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly reassigned AMBARI-22000: - Assignee: (was: Jaimin Jetly) > Select Hosts page while enabling HSI does not load > -- > > Key: AMBARI-22000 > URL: https://issues.apache.org/jira/browse/AMBARI-22000 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Jaimin Jetly >Priority: Critical > Fix For: 2.6.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21917) Some services had issue coming up after express upgrade on IOP clusters
[
https://issues.apache.org/jira/browse/AMBARI-21917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172467#comment-16172467
]
Hudson commented on AMBARI-21917:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #248 (See
[https://builds.apache.org/job/Ambari-branch-2.6/248/])
AMBARI-21917. Some services had issue coming up after express upgrade on
(swagle:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3e8ba2a1f1b4bc8d4152492cf2fd65895111d926])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/metadata/CachedRoleCommandOrderProvider.java
> Some services had issue coming up after express upgrade on IOP clusters
> ---
>
> Key: AMBARI-21917
> URL: https://issues.apache.org/jira/browse/AMBARI-21917
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21917.patch
>
>
> The RCO cache gets cleared on an upgrade to make sure new RCO is loaded.
> However, certain test environments have reported seeing incorrect / older RCO
> still in effect after Finalize and the operations failing due to this.
> The server log does indicate RCO getting cleared:
> {code}
> 24 Aug 2017 17:15:26,701 INFO [Server Action Executor Worker 1509]
> StackUpgradeFinishListener:92 - Clearing RCO cache
> {code}
> But the initialization statements are missing. Making a defensive patch to
> for re-creation of RCO.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22000) Select Hosts page while enabling HSI does not load
Jaimin Jetly created AMBARI-22000: - Summary: Select Hosts page while enabling HSI does not load Key: AMBARI-22000 URL: https://issues.apache.org/jira/browse/AMBARI-22000 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.6.0 Reporter: Jaimin Jetly Assignee: Jaimin Jetly Priority: Critical Fix For: 2.6.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21979) Fixes to CommandStatusDict
[ https://issues.apache.org/jira/browse/AMBARI-21979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-21979: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-3.0-perf > Fixes to CommandStatusDict > -- > > Key: AMBARI-21979 > URL: https://issues.apache.org/jira/browse/AMBARI-21979 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0 > > Attachments: AMBARI-21979.patch > > > 1\. Fix COMPLETE status for command sent twice > 2\. Fix possible race conditions > 3\. Add setting to avoid periodically reporting stdout/stderr. Can be used on > perf clusters to reduce bandwidth usage for perf. Previously to do this > reporting thread had to be stopped which caused issues with delayed commands > status re-sending. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21989) Multiple fixes into branch-3.0-perf
[
https://issues.apache.org/jira/browse/AMBARI-21989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171345#comment-16171345
]
Hadoop QA commented on AMBARI-21989:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887853/AMBARI-21989.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/12271//console
This message is automatically generated.
> Multiple fixes into branch-3.0-perf
> ---
>
> Key: AMBARI-21989
> URL: https://issues.apache.org/jira/browse/AMBARI-21989
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-21989.patch
>
>
> * restart triggered by server should gracefully finish operations
> * if status command fails, exception should be logged.
> * move configs logic from InitializerModule into AmbariConfig, where it
> belongs
> * fix typo (alert_def*E*nitions into alert_def*I*nitions)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21990) Unable to add hosts to Config Groups
Andrii Tkach created AMBARI-21990: - Summary: Unable to add hosts to Config Groups Key: AMBARI-21990 URL: https://issues.apache.org/jira/browse/AMBARI-21990 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.6.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Priority: Blocker Fix For: 2.6.0 Unable to add hosts to Config Groups on a cluster with Ambari 260 + hdp 262. STR : For any service, create config group. Try to add hosts to this newly created config group -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21988) [Hive Metastore] can't start hive metastore service,occured exception in python file "logger.py"
kai zhao created AMBARI-21988: - Summary: [Hive Metastore] can't start hive metastore service,occured exception in python file "logger.py" Key: AMBARI-21988 URL: https://issues.apache.org/jira/browse/AMBARI-21988 Project: Ambari Issue Type: Bug Components: HiveServer2, Metastore, and Client Heap Sizes to Smart Configs Affects Versions: 2.4.2 Environment: linux version: CentOS 6 Linux wjw-syjg-03 2.6.32-431.el6.x86_64 #1 SMP Fri Nov 22 03:15:09 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux python version: Python 2.6.6 (r266:84292, Nov 22 2013, 12:16:22) [GCC 4.4.7 20120313 (Red Hat 4.4.7-4)] on linux2 ambari version: ambari-2.4.2.0-centos6.tar.gz HDP version: HDP-2.5.3.0-centos6-rpm.tar.gz HDP-UTILS version: HDP-UTILS-1.1.0.21-centos6.tar.gz download from:http://http://public-repo-1.hortonworks.com Reporter: kai zhao Priority: Critical 1.start ambari server 2.install Hive service 3.create hive user as 'hive' with password 'hive' in postgresqll database 4.create hive metaData database 'hive' 5.grant all privilege to user hive 6.modify pg_hba.conf file add below lines: local all all trust hostall all 127.0.0.1/32 trust hostall all ::1/128 trust 7.configure hive 8.try to start hive 9.MetaStore service can't start Result: occured Exception: File "/usr/lib/python2.6/site-packages/resource_management/core/logger.py", line 101, in filter_text text = text.replace(unprotected_string, protected_string) UnicodeDecodeError: 'ascii' codec can't decode byte 0xe8 in position 984: ordinal not in range(128) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21989) Multiple fixes into branch-3.0-perf
Andrew Onischuk created AMBARI-21989: Summary: Multiple fixes into branch-3.0-perf Key: AMBARI-21989 URL: https://issues.apache.org/jira/browse/AMBARI-21989 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 3.0.0 * restart triggered by server should gracefully finish operations * if status command fails, exception should be logged. * move configs logic from InitializerModule into AmbariConfig, where it belongs * fix typo (alert_def*E*nitions into alert_def*I*nitions) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21989) Multiple fixes into branch-3.0-perf
[ https://issues.apache.org/jira/browse/AMBARI-21989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-21989: - Status: Patch Available (was: Open) > Multiple fixes into branch-3.0-perf > --- > > Key: AMBARI-21989 > URL: https://issues.apache.org/jira/browse/AMBARI-21989 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0 > > Attachments: AMBARI-21989.patch > > > * restart triggered by server should gracefully finish operations > * if status command fails, exception should be logged. > * move configs logic from InitializerModule into AmbariConfig, where it > belongs > * fix typo (alert_def*E*nitions into alert_def*I*nitions) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21990) Unable to add hosts to Config Groups
[ https://issues.apache.org/jira/browse/AMBARI-21990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21990: -- Attachment: AMBARI-21990.patch > Unable to add hosts to Config Groups > > > Key: AMBARI-21990 > URL: https://issues.apache.org/jira/browse/AMBARI-21990 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.6.0 > > Attachments: AMBARI-21990.patch, Screen Shot 2017-09-18 at 11.24.44 > AM.png, Screen Shot 2017-09-18 at 2.36.47 PM.png > > > Unable to add hosts to Config Groups on a cluster with Ambari 260 + hdp 262. > STR : > For any service, create config group. Try to add hosts to this newly created > config group -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21925) Facilitate a parameter to provide HBase conf directory for atlas-env configurations.
[
https://issues.apache.org/jira/browse/AMBARI-21925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171205#comment-16171205
]
Hudson commented on AMBARI-21925:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #237 (See
[https://builds.apache.org/job/Ambari-branch-2.6/237/])
AMBARI-21925 : Facilitate a parameter to provide HBase conf directory (mugdha:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9a11f0512d3a97fe667e5683b5a55b9193a60abe])
* (edit)
ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/params.py
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/upgrade-2.6.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/config-upgrade.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/nonrolling-upgrade-2.6.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/services/ATLAS/configuration/atlas-env.xml
> Facilitate a parameter to provide HBase conf directory for atlas-env
> configurations.
>
>
> Key: AMBARI-21925
> URL: https://issues.apache.org/jira/browse/AMBARI-21925
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.6.0
>
> Attachments: AMBARI-21925-branch-2.6.patch, AMBARI-21925-trunk.patch
>
>
> Current configuration for Atlas atlas-env contains {{hbase_conf_dir}} which
> is set in environment as {{export HBASE_CONF_DIR=hbase_conf_dir}}
> However, hbase_conf_dir is currently not exposed in ambari and hence its not
> possible to set just {{hbase_conf_dir}} instead through blueprints we need to
> pass full atlas-env.sh content.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21925) Facilitate a parameter to provide HBase conf directory for atlas-env configurations.
[
https://issues.apache.org/jira/browse/AMBARI-21925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171221#comment-16171221
]
Hudson commented on AMBARI-21925:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8085 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8085/])
AMBARI-21925 : Facilitate a parameter to provide HBase conf directory (mugdha:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1f321e35693a1c8fe2c6c5a4ac3e1f454bf847e1])
* (edit)
ambari-server/src/main/resources/common-services/ATLAS/0.7.0.3.0/package/scripts/params.py
* (edit)
ambari-server/src/main/resources/common-services/ATLAS/0.7.0.3.0/configuration/atlas-env.xml
* (edit)
ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/params.py
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/config-upgrade.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/nonrolling-upgrade-2.6.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/upgrade-2.6.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/services/ATLAS/configuration/atlas-env.xml
> Facilitate a parameter to provide HBase conf directory for atlas-env
> configurations.
>
>
> Key: AMBARI-21925
> URL: https://issues.apache.org/jira/browse/AMBARI-21925
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.6.0
>
> Attachments: AMBARI-21925-branch-2.6.patch, AMBARI-21925-trunk.patch
>
>
> Current configuration for Atlas atlas-env contains {{hbase_conf_dir}} which
> is set in environment as {{export HBASE_CONF_DIR=hbase_conf_dir}}
> However, hbase_conf_dir is currently not exposed in ambari and hence its not
> possible to set just {{hbase_conf_dir}} instead through blueprints we need to
> pass full atlas-env.sh content.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21990) Unable to add hosts to Config Groups
[ https://issues.apache.org/jira/browse/AMBARI-21990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171397#comment-16171397 ] Andrii Tkach commented on AMBARI-21990: --- branch-2.6: 30492 passing (26s) 157 pending > Unable to add hosts to Config Groups > > > Key: AMBARI-21990 > URL: https://issues.apache.org/jira/browse/AMBARI-21990 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.6.0 > > Attachments: Screen Shot 2017-09-18 at 11.24.44 AM.png, Screen Shot > 2017-09-18 at 2.36.47 PM.png > > > Unable to add hosts to Config Groups on a cluster with Ambari 260 + hdp 262. > STR : > For any service, create config group. Try to add hosts to this newly created > config group -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21989) Multiple fixes into branch-3.0-perf
[ https://issues.apache.org/jira/browse/AMBARI-21989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-21989: - Attachment: AMBARI-21989.patch > Multiple fixes into branch-3.0-perf > --- > > Key: AMBARI-21989 > URL: https://issues.apache.org/jira/browse/AMBARI-21989 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0 > > Attachments: AMBARI-21989.patch > > > * restart triggered by server should gracefully finish operations > * if status command fails, exception should be logged. > * move configs logic from InitializerModule into AmbariConfig, where it > belongs > * fix typo (alert_def*E*nitions into alert_def*I*nitions) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21990) Unable to add hosts to Config Groups
[ https://issues.apache.org/jira/browse/AMBARI-21990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21990: -- Attachment: Screen Shot 2017-09-18 at 11.24.44 AM.png Screen Shot 2017-09-18 at 2.36.47 PM.png > Unable to add hosts to Config Groups > > > Key: AMBARI-21990 > URL: https://issues.apache.org/jira/browse/AMBARI-21990 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.6.0 > > Attachments: Screen Shot 2017-09-18 at 11.24.44 AM.png, Screen Shot > 2017-09-18 at 2.36.47 PM.png > > > Unable to add hosts to Config Groups on a cluster with Ambari 260 + hdp 262. > STR : > For any service, create config group. Try to add hosts to this newly created > config group -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21917) Some services had issue coming up after express upgrade on IOP clusters
[
https://issues.apache.org/jira/browse/AMBARI-21917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172435#comment-16172435
]
Hadoop QA commented on AMBARI-21917:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887980/AMBARI-21917.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/12289//console
This message is automatically generated.
> Some services had issue coming up after express upgrade on IOP clusters
> ---
>
> Key: AMBARI-21917
> URL: https://issues.apache.org/jira/browse/AMBARI-21917
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21917.patch
>
>
> The RCO cache gets cleared on an upgrade to make sure new RCO is loaded.
> However, certain test environments have reported seeing incorrect / older RCO
> still in effect after Finalize and the operations failing due to this.
> The server log does indicate RCO getting cleared:
> {code}
> 24 Aug 2017 17:15:26,701 INFO [Server Action Executor Worker 1509]
> StackUpgradeFinishListener:92 - Clearing RCO cache
> {code}
> But the initialization statements are missing. Making a defensive patch to
> for re-creation of RCO.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21917) Some services had issue coming up after express upgrade on IOP clusters
[
https://issues.apache.org/jira/browse/AMBARI-21917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172404#comment-16172404
]
Aravindan Vijayan commented on AMBARI-21917:
+1
> Some services had issue coming up after express upgrade on IOP clusters
> ---
>
> Key: AMBARI-21917
> URL: https://issues.apache.org/jira/browse/AMBARI-21917
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21917.patch
>
>
> The RCO cache gets cleared on an upgrade to make sure new RCO is loaded.
> However, certain test environments have reported seeing incorrect / older RCO
> still in effect after Finalize and the operations failing due to this.
> The server log does indicate RCO getting cleared:
> {code}
> 24 Aug 2017 17:15:26,701 INFO [Server Action Executor Worker 1509]
> StackUpgradeFinishListener:92 - Clearing RCO cache
> {code}
> But the initialization statements are missing. Making a defensive patch to
> for re-creation of RCO.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21999) Always Take Target Read-Only Properties On Stack Upgrade
[
https://issues.apache.org/jira/browse/AMBARI-21999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21999:
-
Attachment: AMBARI-21999.patch
> Always Take Target Read-Only Properties On Stack Upgrade
>
>
> Key: AMBARI-21999
> URL: https://issues.apache.org/jira/browse/AMBARI-21999
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21999.patch
>
>
> STR:
> - Install a stack, such as HDP 2.3
> - Modify the {{cluster-env/stack_features}} structure
> - Upgrade to HDP 2.6
> The auto-merge which happens can't properly merge
> {{cluster-env/stack_features}} since it has deviated from the stock values of
> HDP 2.3. This is dangerous since this is needed for proper operation.
> Because it's defined as a read-only value, we should be able to detect this
> in the auto-merge fro the upgrade and force it to the new stack's default
> value...
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21999) Always Take Target Read-Only Properties On Stack Upgrade
[
https://issues.apache.org/jira/browse/AMBARI-21999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21999:
-
Status: Patch Available (was: Open)
> Always Take Target Read-Only Properties On Stack Upgrade
>
>
> Key: AMBARI-21999
> URL: https://issues.apache.org/jira/browse/AMBARI-21999
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21999.patch
>
>
> STR:
> - Install a stack, such as HDP 2.3
> - Modify the {{cluster-env/stack_features}} structure
> - Upgrade to HDP 2.6
> The auto-merge which happens can't properly merge
> {{cluster-env/stack_features}} since it has deviated from the stock values of
> HDP 2.3. This is dangerous since this is needed for proper operation.
> Because it's defined as a read-only value, we should be able to detect this
> in the auto-merge fro the upgrade and force it to the new stack's default
> value...
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21145) allow wildcard for log directory folder in the path component of Logfeeder input
[ https://issues.apache.org/jira/browse/AMBARI-21145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172403#comment-16172403 ] Juanjo Marron commented on AMBARI-21145: Can we confirm this JIRA has been resolved by AMBARI-21387? In that case it could be marked as resolved > allow wildcard for log directory folder in the path component of Logfeeder > input > > > Key: AMBARI-21145 > URL: https://issues.apache.org/jira/browse/AMBARI-21145 > Project: Ambari > Issue Type: Improvement > Components: logsearch >Affects Versions: 2.5.0 >Reporter: Keta Patel >Assignee: Keta Patel >Priority: Minor > > The wildcard processing in Logfeeder is carried out only for the last file > component in the log path. For a few services, where there are multiple log > folders and log files from each of the folders is desired to be parsed in > Logsearch UI, the lack of a wildcard processing for the previous portions > becomes an issue. Hence, introducing wildcard processing for the log > directory part of the "path" in the Logfeeder's input for the service will > help resolve this issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21999) Always Take Target Read-Only Properties On Stack Upgrade
[
https://issues.apache.org/jira/browse/AMBARI-21999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172438#comment-16172438
]
Hadoop QA commented on AMBARI-21999:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887950/AMBARI-21999.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/12290//console
This message is automatically generated.
> Always Take Target Read-Only Properties On Stack Upgrade
>
>
> Key: AMBARI-21999
> URL: https://issues.apache.org/jira/browse/AMBARI-21999
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21999.patch
>
>
> STR:
> - Install a stack, such as HDP 2.3
> - Modify the {{cluster-env/stack_features}} structure
> - Upgrade to HDP 2.6
> The auto-merge which happens can't properly merge
> {{cluster-env/stack_features}} since it has deviated from the stock values of
> HDP 2.3. This is dangerous since this is needed for proper operation.
> Because it's defined as a read-only value, we should be able to detect this
> in the auto-merge fro the upgrade and force it to the new stack's default
> value...
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21987) Store Zeppelin's interpreter.json in HDFS
[ https://issues.apache.org/jira/browse/AMBARI-21987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-21987: - Attachment: AMBARI-21987_trunk_v2.patch > Store Zeppelin's interpreter.json in HDFS > - > > Key: AMBARI-21987 > URL: https://issues.apache.org/jira/browse/AMBARI-21987 > Project: Ambari > Issue Type: Bug >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: AMBARI-21987_trunk_v2.patch > > > With ZEPPELIN-2742 there is a plan to store all of Note, interpreter.json, > helium.json, notebook-authorization.json, and credentials.json to store in > HDFS. This JIRA is to maintain its related Ambari side changes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21978) UI need to add new fields to Repositories
[ https://issues.apache.org/jira/browse/AMBARI-21978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21978: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.6 > UI need to add new fields to Repositories > - > > Key: AMBARI-21978 > URL: https://issues.apache.org/jira/browse/AMBARI-21978 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21978.patch > > > On step "Review", UI send such PUT request, add fields "distribution" and > "component_name" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21735) Parameterize Maven Surefire Build argLine
[
https://issues.apache.org/jira/browse/AMBARI-21735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171497#comment-16171497
]
Dmitry Lysnichenko commented on AMBARI-21735:
-
[~jonathan.hurley],
Looks like DDLs has been updated, but upgrade catalogs stay intact. Is that
desired?
> Parameterize Maven Surefire Build argLine
> -
>
> Key: AMBARI-21735
> URL: https://issues.apache.org/jira/browse/AMBARI-21735
> Project: Ambari
> Issue Type: Task
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: 2.6.0
>
> Attachments: AMBARI-21735.patch
>
>
> Regardless of what options are set via {{MAVEN_OPTS}} or even
> {{-DargLine=...}}, the surefire plugin seems to force the hard coded arg
> lines for forked VMs:
> {code}
> /Library/Java/JavaVirtualMachines/jdk1.8.0_31.jdk/Contents/Home/jre/bin/java
> -Xms512m -Xmx1024m -jar
> {code}
> Setting argLines to different values is never picked up.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-21988) [Hive Metastore] can't start hive metastore service,occured exception in python file "logger.py"
[ https://issues.apache.org/jira/browse/AMBARI-21988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kai zhao resolved AMBARI-21988. --- Resolution: Fixed Fix Version/s: 2.4.2 change the linux locale as 'en_US.UTF-8' change the postgresql locale as 'en_US.UTF-' > [Hive Metastore] can't start hive metastore service,occured exception in > python file "logger.py" > > > Key: AMBARI-21988 > URL: https://issues.apache.org/jira/browse/AMBARI-21988 > Project: Ambari > Issue Type: Bug > Components: HiveServer2, Metastore, and Client Heap Sizes to Smart > Configs >Affects Versions: 2.4.2 > Environment: linux version: > CentOS 6 > Linux wjw-syjg-03 2.6.32-431.el6.x86_64 #1 SMP Fri Nov 22 03:15:09 UTC 2013 > x86_64 x86_64 x86_64 GNU/Linux > python version: > Python 2.6.6 (r266:84292, Nov 22 2013, 12:16:22) > [GCC 4.4.7 20120313 (Red Hat 4.4.7-4)] on linux2 > ambari version: > ambari-2.4.2.0-centos6.tar.gz > HDP version: > HDP-2.5.3.0-centos6-rpm.tar.gz > HDP-UTILS version: > HDP-UTILS-1.1.0.21-centos6.tar.gz > download from:http://http://public-repo-1.hortonworks.com >Reporter: kai zhao >Priority: Critical > Fix For: 2.4.2 > > > 1.start ambari server > 2.install Hive service > 3.create hive user as 'hive' with password 'hive' in postgresqll database > 4.create hive metaData database 'hive' > 5.grant all privilege to user hive > 6.modify pg_hba.conf file add below lines: > local all all trust > hostall all 127.0.0.1/32 trust >hostall all ::1/128 trust > 7.configure hive > 8.try to start hive > 9.MetaStore service can't start > Result: > occured Exception: > File "/usr/lib/python2.6/site-packages/resource_management/core/logger.py", > line 101, in filter_text > text = text.replace(unprotected_string, protected_string) > UnicodeDecodeError: 'ascii' codec can't decode byte 0xe8 in position 984: > ordinal not in range(128) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21991) Clarify MAINT Upgrade Message About Existing Services
[ https://issues.apache.org/jira/browse/AMBARI-21991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21991: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.6 > Clarify MAINT Upgrade Message About Existing Services > - > > Key: AMBARI-21991 > URL: https://issues.apache.org/jira/browse/AMBARI-21991 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21991.patch > > > The message that is displayed for the service's tooltip when it will not be > upgraded is a bit unclear: > "Update available, but already installed" > We should change it to read the following: > "The version of this service included in this repository is already installed > in the cluster." -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21991) Clarify MAINT Upgrade Message About Existing Services
[ https://issues.apache.org/jira/browse/AMBARI-21991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171593#comment-16171593 ] Hudson commented on AMBARI-21991: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #241 (See [https://builds.apache.org/job/Ambari-branch-2.6/241/]) AMBARI-21991. Clarify MAINT Upgrade Message About Existing Services (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3a1c3a6e46bd0c3f91b3cb3467f91617d10d57ce]) * (edit) ambari-web/app/messages.js > Clarify MAINT Upgrade Message About Existing Services > - > > Key: AMBARI-21991 > URL: https://issues.apache.org/jira/browse/AMBARI-21991 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21991.patch > > > The message that is displayed for the service's tooltip when it will not be > upgraded is a bit unclear: > "Update available, but already installed" > We should change it to read the following: > "The version of this service included in this repository is already installed > in the cluster." -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21984) APPLICATION_TIMELINE_SERVER filed to start, coz were already started
[ https://issues.apache.org/jira/browse/AMBARI-21984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Chekanskiy updated AMBARI-21984: --- Resolution: Not A Problem Status: Resolved (was: Patch Available) > APPLICATION_TIMELINE_SERVER filed to start, coz were already started > > > Key: AMBARI-21984 > URL: https://issues.apache.org/jira/browse/AMBARI-21984 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 2.6.0 > > Attachments: AMBARI-21984-branch-2.6.patch, AMBARI-21984-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21968) Log Feeder should not support german month names
[ https://issues.apache.org/jira/browse/AMBARI-21968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171529#comment-16171529 ] Hudson commented on AMBARI-21968: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8087 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8087/]) AMBARI-21968. ADDENDUM Log Feeder should not support german month names (mgergely: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8961a93c49b444b6c6ddc5e657e22540c39c13db]) * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/properties/logfeeder-default_grok_patterns.j2 > Log Feeder should not support german month names > > > Key: AMBARI-21968 > URL: https://issues.apache.org/jira/browse/AMBARI-21968 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.5.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.6.0 > > Attachments: AMBARI-21968.patch > > > Log Feeder grok patterns currently support german month names too. This has > almost no usefulness at all, as there are no german language logs, and we > don't even support german day names, but it may cause errors as the März > contains a ä character which may lead to encoding related errors. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21978) UI need to add new fields to Repositories
[ https://issues.apache.org/jira/browse/AMBARI-21978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171444#comment-16171444 ] Hudson commented on AMBARI-21978: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #238 (See [https://builds.apache.org/job/Ambari-branch-2.6/238/]) AMBARI-21978. UI need to add new fields to Repositories (alexantonenko) (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5a55a2ba0bf7dcce13bbb9978c00d4c6f13989b1]) * (edit) ambari-web/app/mappers/stack_mapper.js * (edit) ambari-web/app/controllers/installer.js * (edit) ambari-web/app/models/operating_system.js * (edit) ambari-web/app/models/repository.js > UI need to add new fields to Repositories > - > > Key: AMBARI-21978 > URL: https://issues.apache.org/jira/browse/AMBARI-21978 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21978.patch > > > On step "Review", UI send such PUT request, add fields "distribution" and > "component_name" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21990) Unable to add hosts to Config Groups
[ https://issues.apache.org/jira/browse/AMBARI-21990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171477#comment-16171477 ] Andrii Tkach commented on AMBARI-21990: --- committed to trunk and branch-2.6 > Unable to add hosts to Config Groups > > > Key: AMBARI-21990 > URL: https://issues.apache.org/jira/browse/AMBARI-21990 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.6.0 > > Attachments: AMBARI-21990.patch, AMBARI-21990_trunk.patch, Screen > Shot 2017-09-18 at 11.24.44 AM.png, Screen Shot 2017-09-18 at 2.36.47 PM.png > > > Unable to add hosts to Config Groups on a cluster with Ambari 260 + hdp 262. > STR : > For any service, create config group. Try to add hosts to this newly created > config group -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21989) Multiple fixes into branch-3.0-perf
[
https://issues.apache.org/jira/browse/AMBARI-21989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171492#comment-16171492
]
Hadoop QA commented on AMBARI-21989:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887853/AMBARI-21989.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/12274//console
This message is automatically generated.
> Multiple fixes into branch-3.0-perf
> ---
>
> Key: AMBARI-21989
> URL: https://issues.apache.org/jira/browse/AMBARI-21989
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-21989.patch
>
>
> * restart triggered by server should gracefully finish operations
> * if status command fails, exception should be logged.
> * move configs logic from InitializerModule into AmbariConfig, where it
> belongs
> * fix typo (alert_def*E*nitions into alert_def*I*nitions)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21991) Clarify MAINT Upgrade Message About Existing Services
[ https://issues.apache.org/jira/browse/AMBARI-21991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21991: - Attachment: AMBARI-21991.patch > Clarify MAINT Upgrade Message About Existing Services > - > > Key: AMBARI-21991 > URL: https://issues.apache.org/jira/browse/AMBARI-21991 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21991.patch > > > The message that is displayed for the service's tooltip when it will not be > upgraded is a bit unclear: > "Update available, but already installed" > We should change it to read the following: > "The version of this service included in this repository is already installed > in the cluster." -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21990) Unable to add hosts to Config Groups
[ https://issues.apache.org/jira/browse/AMBARI-21990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171465#comment-16171465 ] Andrii Babiichuk commented on AMBARI-21990: --- +1 for the patch > Unable to add hosts to Config Groups > > > Key: AMBARI-21990 > URL: https://issues.apache.org/jira/browse/AMBARI-21990 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.6.0 > > Attachments: AMBARI-21990.patch, AMBARI-21990_trunk.patch, Screen > Shot 2017-09-18 at 11.24.44 AM.png, Screen Shot 2017-09-18 at 2.36.47 PM.png > > > Unable to add hosts to Config Groups on a cluster with Ambari 260 + hdp 262. > STR : > For any service, create config group. Try to add hosts to this newly created > config group -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21978) UI need to add new fields to Repositories
[ https://issues.apache.org/jira/browse/AMBARI-21978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171490#comment-16171490 ] Hudson commented on AMBARI-21978: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8086 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8086/]) AMBARI-21978. UI need to add new fields to Repositories (alexantonenko) (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ea49b33c143fb0e00f16594fdb7dbf396f374981]) * (edit) ambari-web/app/models/repository.js * (edit) ambari-web/app/controllers/installer.js * (edit) ambari-web/app/mappers/stack_mapper.js * (edit) ambari-web/app/models/operating_system.js > UI need to add new fields to Repositories > - > > Key: AMBARI-21978 > URL: https://issues.apache.org/jira/browse/AMBARI-21978 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21978.patch > > > On step "Review", UI send such PUT request, add fields "distribution" and > "component_name" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21990) Unable to add hosts to Config Groups
[
https://issues.apache.org/jira/browse/AMBARI-21990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171489#comment-16171489
]
Hadoop QA commented on AMBARI-21990:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887859/AMBARI-21990_trunk.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12273//console
This message is automatically generated.
> Unable to add hosts to Config Groups
>
>
> Key: AMBARI-21990
> URL: https://issues.apache.org/jira/browse/AMBARI-21990
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-21990.patch, AMBARI-21990_trunk.patch, Screen
> Shot 2017-09-18 at 11.24.44 AM.png, Screen Shot 2017-09-18 at 2.36.47 PM.png
>
>
> Unable to add hosts to Config Groups on a cluster with Ambari 260 + hdp 262.
> STR :
> For any service, create config group. Try to add hosts to this newly created
> config group
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21968) Log Feeder should not support german month names
[ https://issues.apache.org/jira/browse/AMBARI-21968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171507#comment-16171507 ] Hudson commented on AMBARI-21968: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #240 (See [https://builds.apache.org/job/Ambari-branch-2.6/240/]) AMBARI-21968. ADDENDUM Log Feeder should not support german month names (mgergely: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=701d640ee41de173342ab69c4e16e5187ff60a6c]) * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/properties/logfeeder-default_grok_patterns.j2 > Log Feeder should not support german month names > > > Key: AMBARI-21968 > URL: https://issues.apache.org/jira/browse/AMBARI-21968 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.5.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.6.0 > > Attachments: AMBARI-21968.patch > > > Log Feeder grok patterns currently support german month names too. This has > almost no usefulness at all, as there are no german language logs, and we > don't even support german day names, but it may cause errors as the März > contains a ä character which may lead to encoding related errors. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21991) Clarify MAINT Upgrade Message About Existing Services
Antonenko Alexander created AMBARI-21991: Summary: Clarify MAINT Upgrade Message About Existing Services Key: AMBARI-21991 URL: https://issues.apache.org/jira/browse/AMBARI-21991 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.6.0 Reporter: Antonenko Alexander Priority: Critical Fix For: 2.6.0 The message that is displayed for the service's tooltip when it will not be upgraded is a bit unclear: "Update available, but already installed" We should change it to read the following: "The version of this service included in this repository is already installed in the cluster." -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-21991) Clarify MAINT Upgrade Message About Existing Services
[ https://issues.apache.org/jira/browse/AMBARI-21991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-21991: Assignee: Antonenko Alexander > Clarify MAINT Upgrade Message About Existing Services > - > > Key: AMBARI-21991 > URL: https://issues.apache.org/jira/browse/AMBARI-21991 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > > The message that is displayed for the service's tooltip when it will not be > upgraded is a bit unclear: > "Update available, but already installed" > We should change it to read the following: > "The version of this service included in this repository is already installed > in the cluster." -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21991) Clarify MAINT Upgrade Message About Existing Services
[ https://issues.apache.org/jira/browse/AMBARI-21991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171542#comment-16171542 ] Andrii Tkach commented on AMBARI-21991: --- +1 for the patch > Clarify MAINT Upgrade Message About Existing Services > - > > Key: AMBARI-21991 > URL: https://issues.apache.org/jira/browse/AMBARI-21991 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21991.patch > > > The message that is displayed for the service's tooltip when it will not be > upgraded is a bit unclear: > "Update available, but already installed" > We should change it to read the following: > "The version of this service included in this repository is already installed > in the cluster." -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21990) Unable to add hosts to Config Groups
[
https://issues.apache.org/jira/browse/AMBARI-21990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171456#comment-16171456
]
Hadoop QA commented on AMBARI-21990:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887859/AMBARI-21990_trunk.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12272//console
This message is automatically generated.
> Unable to add hosts to Config Groups
>
>
> Key: AMBARI-21990
> URL: https://issues.apache.org/jira/browse/AMBARI-21990
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-21990.patch, AMBARI-21990_trunk.patch, Screen
> Shot 2017-09-18 at 11.24.44 AM.png, Screen Shot 2017-09-18 at 2.36.47 PM.png
>
>
> Unable to add hosts to Config Groups on a cluster with Ambari 260 + hdp 262.
> STR :
> For any service, create config group. Try to add hosts to this newly created
> config group
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21990) Unable to add hosts to Config Groups
[ https://issues.apache.org/jira/browse/AMBARI-21990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21990: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Unable to add hosts to Config Groups > > > Key: AMBARI-21990 > URL: https://issues.apache.org/jira/browse/AMBARI-21990 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.6.0 > > Attachments: AMBARI-21990.patch, AMBARI-21990_trunk.patch, Screen > Shot 2017-09-18 at 11.24.44 AM.png, Screen Shot 2017-09-18 at 2.36.47 PM.png > > > Unable to add hosts to Config Groups on a cluster with Ambari 260 + hdp 262. > STR : > For any service, create config group. Try to add hosts to this newly created > config group -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21990) Unable to add hosts to Config Groups
[ https://issues.apache.org/jira/browse/AMBARI-21990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171493#comment-16171493 ] Hudson commented on AMBARI-21990: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #239 (See [https://builds.apache.org/job/Ambari-branch-2.6/239/]) AMBARI-21990 Unable to add hosts to Config Groups. (atkach) (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=10e9afaeeedd74c5e2fb8c5f22ad77ce2061535b]) * (edit) ambari-web/app/controllers/main/service/manage_config_groups_controller.js > Unable to add hosts to Config Groups > > > Key: AMBARI-21990 > URL: https://issues.apache.org/jira/browse/AMBARI-21990 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.6.0 > > Attachments: AMBARI-21990.patch, AMBARI-21990_trunk.patch, Screen > Shot 2017-09-18 at 11.24.44 AM.png, Screen Shot 2017-09-18 at 2.36.47 PM.png > > > Unable to add hosts to Config Groups on a cluster with Ambari 260 + hdp 262. > STR : > For any service, create config group. Try to add hosts to this newly created > config group -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21987) Store Zeppelin's interpreter.json in HDFS
[
https://issues.apache.org/jira/browse/AMBARI-21987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171495#comment-16171495
]
Hadoop QA commented on AMBARI-21987:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887868/AMBARI-21987_branch-2.6_v3.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/12275//console
This message is automatically generated.
> Store Zeppelin's interpreter.json in HDFS
> -
>
> Key: AMBARI-21987
> URL: https://issues.apache.org/jira/browse/AMBARI-21987
> Project: Ambari
> Issue Type: Bug
>Reporter: Prabhjyot Singh
>Assignee: Prabhjyot Singh
> Attachments: AMBARI-21987_branch-2.6_v3.patch,
> AMBARI-21987_trunk_v2.patch, AMBARI-21987_trunk_v3.patch
>
>
> With ZEPPELIN-2742 there is a plan to store all of Note, interpreter.json,
> helium.json, notebook-authorization.json, and credentials.json to store in
> HDFS. This JIRA is to maintain its related Ambari side changes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21990) Unable to add hosts to Config Groups
[ https://issues.apache.org/jira/browse/AMBARI-21990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21990: -- Attachment: AMBARI-21990_trunk.patch > Unable to add hosts to Config Groups > > > Key: AMBARI-21990 > URL: https://issues.apache.org/jira/browse/AMBARI-21990 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.6.0 > > Attachments: AMBARI-21990.patch, AMBARI-21990_trunk.patch, Screen > Shot 2017-09-18 at 11.24.44 AM.png, Screen Shot 2017-09-18 at 2.36.47 PM.png > > > Unable to add hosts to Config Groups on a cluster with Ambari 260 + hdp 262. > STR : > For any service, create config group. Try to add hosts to this newly created > config group -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (AMBARI-21990) Unable to add hosts to Config Groups
[ https://issues.apache.org/jira/browse/AMBARI-21990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171397#comment-16171397 ] Andrii Tkach edited comment on AMBARI-21990 at 9/19/17 9:37 AM: branch-2.6: 30492 passing (26s) 157 pending trunk: 21330 passing (32s) 128 pending was (Author: atkach): branch-2.6: 30492 passing (26s) 157 pending > Unable to add hosts to Config Groups > > > Key: AMBARI-21990 > URL: https://issues.apache.org/jira/browse/AMBARI-21990 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.6.0 > > Attachments: AMBARI-21990.patch, AMBARI-21990_trunk.patch, Screen > Shot 2017-09-18 at 11.24.44 AM.png, Screen Shot 2017-09-18 at 2.36.47 PM.png > > > Unable to add hosts to Config Groups on a cluster with Ambari 260 + hdp 262. > STR : > For any service, create config group. Try to add hosts to this newly created > config group -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21990) Unable to add hosts to Config Groups
[ https://issues.apache.org/jira/browse/AMBARI-21990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21990: -- Status: Patch Available (was: Open) > Unable to add hosts to Config Groups > > > Key: AMBARI-21990 > URL: https://issues.apache.org/jira/browse/AMBARI-21990 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.6.0 > > Attachments: AMBARI-21990.patch, AMBARI-21990_trunk.patch, Screen > Shot 2017-09-18 at 11.24.44 AM.png, Screen Shot 2017-09-18 at 2.36.47 PM.png > > > Unable to add hosts to Config Groups on a cluster with Ambari 260 + hdp 262. > STR : > For any service, create config group. Try to add hosts to this newly created > config group -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21978) UI need to add new fields to Repositories
[ https://issues.apache.org/jira/browse/AMBARI-21978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171421#comment-16171421 ] Andrii Tkach commented on AMBARI-21978: --- +1 for the patch > UI need to add new fields to Repositories > - > > Key: AMBARI-21978 > URL: https://issues.apache.org/jira/browse/AMBARI-21978 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21978.patch > > > On step "Review", UI send such PUT request, add fields "distribution" and > "component_name" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21987) Store Zeppelin's interpreter.json in HDFS
[ https://issues.apache.org/jira/browse/AMBARI-21987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-21987: - Attachment: AMBARI-21987_branch-2.6_v3.patch AMBARI-21987_trunk_v3.patch > Store Zeppelin's interpreter.json in HDFS > - > > Key: AMBARI-21987 > URL: https://issues.apache.org/jira/browse/AMBARI-21987 > Project: Ambari > Issue Type: Bug >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: AMBARI-21987_branch-2.6_v3.patch, > AMBARI-21987_trunk_v2.patch, AMBARI-21987_trunk_v3.patch > > > With ZEPPELIN-2742 there is a plan to store all of Note, interpreter.json, > helium.json, notebook-authorization.json, and credentials.json to store in > HDFS. This JIRA is to maintain its related Ambari side changes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21991) Clarify MAINT Upgrade Message About Existing Services
[ https://issues.apache.org/jira/browse/AMBARI-21991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21991: - Status: Patch Available (was: Open) > Clarify MAINT Upgrade Message About Existing Services > - > > Key: AMBARI-21991 > URL: https://issues.apache.org/jira/browse/AMBARI-21991 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21991.patch > > > The message that is displayed for the service's tooltip when it will not be > upgraded is a bit unclear: > "Update available, but already installed" > We should change it to read the following: > "The version of this service included in this repository is already installed > in the cluster." -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21990) Unable to add hosts to Config Groups
[ https://issues.apache.org/jira/browse/AMBARI-21990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171528#comment-16171528 ] Hudson commented on AMBARI-21990: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8087 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8087/]) AMBARI-21990 Unable to add hosts to Config Groups. (atkach) (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f6c1e47332482bfa9faeec67402bda58770aa6e9]) * (edit) ambari-web/app/controllers/main/service/manage_config_groups_controller.js > Unable to add hosts to Config Groups > > > Key: AMBARI-21990 > URL: https://issues.apache.org/jira/browse/AMBARI-21990 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.6.0 > > Attachments: AMBARI-21990.patch, AMBARI-21990_trunk.patch, Screen > Shot 2017-09-18 at 11.24.44 AM.png, Screen Shot 2017-09-18 at 2.36.47 PM.png > > > Unable to add hosts to Config Groups on a cluster with Ambari 260 + hdp 262. > STR : > For any service, create config group. Try to add hosts to this newly created > config group -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21991) Clarify MAINT Upgrade Message About Existing Services
[
https://issues.apache.org/jira/browse/AMBARI-21991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171539#comment-16171539
]
Hadoop QA commented on AMBARI-21991:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887872/AMBARI-21991.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12276//console
This message is automatically generated.
> Clarify MAINT Upgrade Message About Existing Services
> -
>
> Key: AMBARI-21991
> URL: https://issues.apache.org/jira/browse/AMBARI-21991
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21991.patch
>
>
> The message that is displayed for the service's tooltip when it will not be
> upgraded is a bit unclear:
> "Update available, but already installed"
> We should change it to read the following:
> "The version of this service included in this repository is already installed
> in the cluster."
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21735) Parameterize Maven Surefire Build argLine
[
https://issues.apache.org/jira/browse/AMBARI-21735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171592#comment-16171592
]
Jonathan Hurley commented on AMBARI-21735:
--
DDLs? Wrong Jira?
> Parameterize Maven Surefire Build argLine
> -
>
> Key: AMBARI-21735
> URL: https://issues.apache.org/jira/browse/AMBARI-21735
> Project: Ambari
> Issue Type: Task
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: 2.6.0
>
> Attachments: AMBARI-21735.patch
>
>
> Regardless of what options are set via {{MAVEN_OPTS}} or even
> {{-DargLine=...}}, the surefire plugin seems to force the hard coded arg
> lines for forked VMs:
> {code}
> /Library/Java/JavaVirtualMachines/jdk1.8.0_31.jdk/Contents/Home/jre/bin/java
> -Xms512m -Xmx1024m -jar
> {code}
> Setting argLines to different values is never picked up.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21991) Clarify MAINT Upgrade Message About Existing Services
[ https://issues.apache.org/jira/browse/AMBARI-21991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171623#comment-16171623 ] Hudson commented on AMBARI-21991: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8088 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8088/]) AMBARI-21991. Clarify MAINT Upgrade Message About Existing Services (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d0e44a15466548e06b977c9d514b4a4ff4f52296]) * (edit) ambari-web/app/messages.js > Clarify MAINT Upgrade Message About Existing Services > - > > Key: AMBARI-21991 > URL: https://issues.apache.org/jira/browse/AMBARI-21991 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21991.patch > > > The message that is displayed for the service's tooltip when it will not be > upgraded is a bit unclear: > "Update available, but already installed" > We should change it to read the following: > "The version of this service included in this repository is already installed > in the cluster." -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21992) Update Already Installed Icon Appears On Old Repo
[
https://issues.apache.org/jira/browse/AMBARI-21992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171656#comment-16171656
]
Hadoop QA commented on AMBARI-21992:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887883/AMBARI-21992_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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12278//console
This message is automatically generated.
> Update Already Installed Icon Appears On Old Repo
> -
>
> Key: AMBARI-21992
> URL: https://issues.apache.org/jira/browse/AMBARI-21992
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.6.0
>
> Attachments: AMBARI-21992.patch, AMBARI-21992_trunk.patch
>
>
> The "Update Available, but already installed." icon appears on repos which
> have previously been applied and then moved off of.
> STR:
> * Install HDP 2.6.0.0 for ZK and Storm
> * Register a PATCH HDP 2.6.0.1 for Storm
> * Apply the patch
> * Register a PATCH HDP 2.6.0.2 for Storm
> * Apply the patch
> The old repo moves into the correct state, but displays the icon indicating
> that Storm is already at the right version.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21992) Update Already Installed Icon Appears On Old Repo
[ https://issues.apache.org/jira/browse/AMBARI-21992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21992: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.6 > Update Already Installed Icon Appears On Old Repo > - > > Key: AMBARI-21992 > URL: https://issues.apache.org/jira/browse/AMBARI-21992 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21992.patch, AMBARI-21992_trunk.patch > > > The "Update Available, but already installed." icon appears on repos which > have previously been applied and then moved off of. > STR: > * Install HDP 2.6.0.0 for ZK and Storm > * Register a PATCH HDP 2.6.0.1 for Storm > * Apply the patch > * Register a PATCH HDP 2.6.0.2 for Storm > * Apply the patch > The old repo moves into the correct state, but displays the icon indicating > that Storm is already at the right version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21907) Ambari can demand an invalid python class name (containing hyphens) for the service advisor
[ https://issues.apache.org/jira/browse/AMBARI-21907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diego Santesteban updated AMBARI-21907: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari can demand an invalid python class name (containing hyphens) for the > service advisor > --- > > Key: AMBARI-21907 > URL: https://issues.apache.org/jira/browse/AMBARI-21907 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Diego Santesteban >Assignee: Diego Santesteban > Fix For: trunk, 2.5.3, 2.6.0 > > Attachments: AMBARI-21907.patch > > Original Estimate: 4h > Time Spent: 6h > Remaining Estimate: 0h > > The service advisor class name is created as 'stackName + versionString + > serviceName + "ServiceAdvisor"'. When stackName, versionString or serviceName > contains a hyphen, the class name that Ambari wants is not valid in python. > Ambari should remove non-alphanumeric characters from the service advisor > class name. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21993) Pre upgrade check dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-21993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21993: - Attachment: 3.png 2.png 1.png > Pre upgrade check dialog style issues > - > > Key: AMBARI-21993 > URL: https://issues.apache.org/jira/browse/AMBARI-21993 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, 2.png, 3.png > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21993) Pre upgrade check dialog style issues
Antonenko Alexander created AMBARI-21993: Summary: Pre upgrade check dialog style issues Key: AMBARI-21993 URL: https://issues.apache.org/jira/browse/AMBARI-21993 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.6.0 Reporter: Antonenko Alexander Priority: Critical Fix For: 2.6.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21992) Update Already Installed Icon Appears On Old Repo
[ https://issues.apache.org/jira/browse/AMBARI-21992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171677#comment-16171677 ] Hudson commented on AMBARI-21992: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #242 (See [https://builds.apache.org/job/Ambari-branch-2.6/242/]) AMBARI-21992. Update Already Installed Icon Appears On Old Repo (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5fd168a5fc0cab49820a4d394ea3b24c4c7a0422]) * (edit) ambari-web/test/views/main/admin/stack_upgrade/upgrade_version_column_view_test.js * (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_column_view.js > Update Already Installed Icon Appears On Old Repo > - > > Key: AMBARI-21992 > URL: https://issues.apache.org/jira/browse/AMBARI-21992 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21992.patch, AMBARI-21992_trunk.patch > > > The "Update Available, but already installed." icon appears on repos which > have previously been applied and then moved off of. > STR: > * Install HDP 2.6.0.0 for ZK and Storm > * Register a PATCH HDP 2.6.0.1 for Storm > * Apply the patch > * Register a PATCH HDP 2.6.0.2 for Storm > * Apply the patch > The old repo moves into the correct state, but displays the icon indicating > that Storm is already at the right version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21993) Pre upgrade check dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-21993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21993: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.6 > Pre upgrade check dialog style issues > - > > Key: AMBARI-21993 > URL: https://issues.apache.org/jira/browse/AMBARI-21993 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, 2.png, 3.png, AMBARI-21993.patch, > AMBARI-21993_trunk.patch > > > # Top whitespace between text and grey area is to small, but bottom > whitespace between grey area and button area is to big: > !1.png|thumbnail! > # Second text should be the same size as in check while upgrading: > !2.png|thumbnail! !3.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21994) Upgrade history view style issue
[ https://issues.apache.org/jira/browse/AMBARI-21994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171783#comment-16171783 ] Andrii Babiichuk commented on AMBARI-21994: --- +1 for the patch > Upgrade history view style issue > > > Key: AMBARI-21994 > URL: https://issues.apache.org/jira/browse/AMBARI-21994 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, AMBARI-21994.patch > > > Can we make sure all arrows and labels in dropdown are aligned? > Maybe have to boost the width on the ‘service name’ to accommodate longer > service names -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21993) Pre upgrade check dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-21993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171786#comment-16171786 ] Hudson commented on AMBARI-21993: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8090 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8090/]) AMBARI-21993. Pre upgrade check dialog style issues (alexantonenko) (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7cebdebbdfb6c249945c03e12f203b3fc05fe926]) * (edit) ambari-web/app/styles/stack_versions.less * (edit) ambari-web/app/templates/main/admin/stack_upgrade/upgrade_options.hbs > Pre upgrade check dialog style issues > - > > Key: AMBARI-21993 > URL: https://issues.apache.org/jira/browse/AMBARI-21993 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, 2.png, 3.png, AMBARI-21993.patch, > AMBARI-21993_trunk.patch > > > # Top whitespace between text and grey area is to small, but bottom > whitespace between grey area and button area is to big: > !1.png|thumbnail! > # Second text should be the same size as in check while upgrading: > !2.png|thumbnail! !3.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21992) Update Already Installed Icon Appears On Old Repo
[ https://issues.apache.org/jira/browse/AMBARI-21992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21992: - Status: Patch Available (was: Open) > Update Already Installed Icon Appears On Old Repo > - > > Key: AMBARI-21992 > URL: https://issues.apache.org/jira/browse/AMBARI-21992 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21992.patch, AMBARI-21992_trunk.patch > > > The "Update Available, but already installed." icon appears on repos which > have previously been applied and then moved off of. > STR: > * Install HDP 2.6.0.0 for ZK and Storm > * Register a PATCH HDP 2.6.0.1 for Storm > * Apply the patch > * Register a PATCH HDP 2.6.0.2 for Storm > * Apply the patch > The old repo moves into the correct state, but displays the icon indicating > that Storm is already at the right version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21992) Update Already Installed Icon Appears On Old Repo
[ https://issues.apache.org/jira/browse/AMBARI-21992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21992: - Attachment: AMBARI-21992.patch > Update Already Installed Icon Appears On Old Repo > - > > Key: AMBARI-21992 > URL: https://issues.apache.org/jira/browse/AMBARI-21992 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21992.patch, AMBARI-21992_trunk.patch > > > The "Update Available, but already installed." icon appears on repos which > have previously been applied and then moved off of. > STR: > * Install HDP 2.6.0.0 for ZK and Storm > * Register a PATCH HDP 2.6.0.1 for Storm > * Apply the patch > * Register a PATCH HDP 2.6.0.2 for Storm > * Apply the patch > The old repo moves into the correct state, but displays the icon indicating > that Storm is already at the right version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21992) Update Already Installed Icon Appears On Old Repo
[ https://issues.apache.org/jira/browse/AMBARI-21992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21992: - Attachment: AMBARI-21992_trunk.patch > Update Already Installed Icon Appears On Old Repo > - > > Key: AMBARI-21992 > URL: https://issues.apache.org/jira/browse/AMBARI-21992 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21992.patch, AMBARI-21992_trunk.patch > > > The "Update Available, but already installed." icon appears on repos which > have previously been applied and then moved off of. > STR: > * Install HDP 2.6.0.0 for ZK and Storm > * Register a PATCH HDP 2.6.0.1 for Storm > * Apply the patch > * Register a PATCH HDP 2.6.0.2 for Storm > * Apply the patch > The old repo moves into the correct state, but displays the icon indicating > that Storm is already at the right version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-21993) Pre upgrade check dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-21993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-21993: Assignee: Antonenko Alexander > Pre upgrade check dialog style issues > - > > Key: AMBARI-21993 > URL: https://issues.apache.org/jira/browse/AMBARI-21993 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, 2.png, 3.png > > > # Top whitespace between text and grey area is to small, but bottom > whitespace between grey area and button area is to big: > !1.png|thumbnail! > # Second text should be the same size as in check while upgrading: > !2.png|thumbnail! !3.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21993) Pre upgrade check dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-21993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21993: - Attachment: AMBARI-21993.patch > Pre upgrade check dialog style issues > - > > Key: AMBARI-21993 > URL: https://issues.apache.org/jira/browse/AMBARI-21993 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, 2.png, 3.png, AMBARI-21993.patch, > AMBARI-21993_trunk.patch > > > # Top whitespace between text and grey area is to small, but bottom > whitespace between grey area and button area is to big: > !1.png|thumbnail! > # Second text should be the same size as in check while upgrading: > !2.png|thumbnail! !3.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21993) Pre upgrade check dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-21993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21993: - Status: Patch Available (was: Open) > Pre upgrade check dialog style issues > - > > Key: AMBARI-21993 > URL: https://issues.apache.org/jira/browse/AMBARI-21993 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, 2.png, 3.png, AMBARI-21993.patch, > AMBARI-21993_trunk.patch > > > # Top whitespace between text and grey area is to small, but bottom > whitespace between grey area and button area is to big: > !1.png|thumbnail! > # Second text should be the same size as in check while upgrading: > !2.png|thumbnail! !3.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21993) Pre upgrade check dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-21993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21993: - Attachment: AMBARI-21993_trunk.patch > Pre upgrade check dialog style issues > - > > Key: AMBARI-21993 > URL: https://issues.apache.org/jira/browse/AMBARI-21993 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, 2.png, 3.png, AMBARI-21993.patch, > AMBARI-21993_trunk.patch > > > # Top whitespace between text and grey area is to small, but bottom > whitespace between grey area and button area is to big: > !1.png|thumbnail! > # Second text should be the same size as in check while upgrading: > !2.png|thumbnail! !3.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21992) Update Already Installed Icon Appears On Old Repo
[ https://issues.apache.org/jira/browse/AMBARI-21992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171660#comment-16171660 ] Andrii Tkach commented on AMBARI-21992: --- +1 for the patch > Update Already Installed Icon Appears On Old Repo > - > > Key: AMBARI-21992 > URL: https://issues.apache.org/jira/browse/AMBARI-21992 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21992.patch, AMBARI-21992_trunk.patch > > > The "Update Available, but already installed." icon appears on repos which > have previously been applied and then moved off of. > STR: > * Install HDP 2.6.0.0 for ZK and Storm > * Register a PATCH HDP 2.6.0.1 for Storm > * Apply the patch > * Register a PATCH HDP 2.6.0.2 for Storm > * Apply the patch > The old repo moves into the correct state, but displays the icon indicating > that Storm is already at the right version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21993) Pre upgrade check dialog style issues
[
https://issues.apache.org/jira/browse/AMBARI-21993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171714#comment-16171714
]
Hadoop QA commented on AMBARI-21993:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887888/AMBARI-21993_trunk.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12279//console
This message is automatically generated.
> Pre upgrade check dialog style issues
> -
>
> Key: AMBARI-21993
> URL: https://issues.apache.org/jira/browse/AMBARI-21993
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: 1.png, 2.png, 3.png, AMBARI-21993.patch,
> AMBARI-21993_trunk.patch
>
>
> # Top whitespace between text and grey area is to small, but bottom
> whitespace between grey area and button area is to big:
> !1.png|thumbnail!
> # Second text should be the same size as in check while upgrading:
> !2.png|thumbnail! !3.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21992) Update Already Installed Icon Appears On Old Repo
[ https://issues.apache.org/jira/browse/AMBARI-21992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171726#comment-16171726 ] Hudson commented on AMBARI-21992: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8089 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8089/]) AMBARI-21992. Update Already Installed Icon Appears On Old Repo (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=271fbc7ca83cfb67f7b4d2adec61000c571e8aff]) * (edit) ambari-web/test/views/main/admin/stack_upgrade/upgrade_version_column_view_test.js * (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_column_view.js > Update Already Installed Icon Appears On Old Repo > - > > Key: AMBARI-21992 > URL: https://issues.apache.org/jira/browse/AMBARI-21992 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21992.patch, AMBARI-21992_trunk.patch > > > The "Update Available, but already installed." icon appears on repos which > have previously been applied and then moved off of. > STR: > * Install HDP 2.6.0.0 for ZK and Storm > * Register a PATCH HDP 2.6.0.1 for Storm > * Apply the patch > * Register a PATCH HDP 2.6.0.2 for Storm > * Apply the patch > The old repo moves into the correct state, but displays the icon indicating > that Storm is already at the right version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21994) Upgrade history view style issue
[ https://issues.apache.org/jira/browse/AMBARI-21994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21994: -- Status: Patch Available (was: Open) > Upgrade history view style issue > > > Key: AMBARI-21994 > URL: https://issues.apache.org/jira/browse/AMBARI-21994 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, AMBARI-21994.patch > > > Can we make sure all arrows and labels in dropdown are aligned? > Maybe have to boost the width on the ‘service name’ to accommodate longer > service names -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21994) Upgrade history view style issue
[ https://issues.apache.org/jira/browse/AMBARI-21994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21994: -- Attachment: (was: AMBARI-21994.patch) > Upgrade history view style issue > > > Key: AMBARI-21994 > URL: https://issues.apache.org/jira/browse/AMBARI-21994 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, AMBARI-21994.patch > > > Can we make sure all arrows and labels in dropdown are aligned? > Maybe have to boost the width on the ‘service name’ to accommodate longer > service names -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21994) Upgrade history view style issue
[ https://issues.apache.org/jira/browse/AMBARI-21994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21994: -- Attachment: AMBARI-21994.patch > Upgrade history view style issue > > > Key: AMBARI-21994 > URL: https://issues.apache.org/jira/browse/AMBARI-21994 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, AMBARI-21994.patch > > > Can we make sure all arrows and labels in dropdown are aligned? > Maybe have to boost the width on the ‘service name’ to accommodate longer > service names -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21992) Update Already Installed Icon Appears On Old Repo
Antonenko Alexander created AMBARI-21992: Summary: Update Already Installed Icon Appears On Old Repo Key: AMBARI-21992 URL: https://issues.apache.org/jira/browse/AMBARI-21992 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.6.0 Reporter: Antonenko Alexander Fix For: 2.6.0 The "Update Available, but already installed." icon appears on repos which have previously been applied and then moved off of. STR: * Install HDP 2.6.0.0 for ZK and Storm * Register a PATCH HDP 2.6.0.1 for Storm * Apply the patch * Register a PATCH HDP 2.6.0.2 for Storm * Apply the patch The old repo moves into the correct state, but displays the icon indicating that Storm is already at the right version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-21992) Update Already Installed Icon Appears On Old Repo
[ https://issues.apache.org/jira/browse/AMBARI-21992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-21992: Assignee: Antonenko Alexander > Update Already Installed Icon Appears On Old Repo > - > > Key: AMBARI-21992 > URL: https://issues.apache.org/jira/browse/AMBARI-21992 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > > The "Update Available, but already installed." icon appears on repos which > have previously been applied and then moved off of. > STR: > * Install HDP 2.6.0.0 for ZK and Storm > * Register a PATCH HDP 2.6.0.1 for Storm > * Apply the patch > * Register a PATCH HDP 2.6.0.2 for Storm > * Apply the patch > The old repo moves into the correct state, but displays the icon indicating > that Storm is already at the right version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-21970) Enable sticky bit for curl_krb_cache
[
https://issues.apache.org/jira/browse/AMBARI-21970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Chekanskiy reassigned AMBARI-21970:
--
Assignee: Eugene Chekanskiy
> Enable sticky bit for curl_krb_cache
>
>
> Key: AMBARI-21970
> URL: https://issues.apache.org/jira/browse/AMBARI-21970
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Krishnama Raju K
>Assignee: Eugene Chekanskiy
>Priority: Minor
> Attachments: AMBARI-21970.patch
>
>
> In secure environment, we see that "/var/lib/ambari-agent/tmp" has sticky bit
> enabled. Trying to enable such permissions ( sticky bit or any other
> permissions ) for "curl_krb_request.py" is being over written after few
> seconds.
> It is observed that the chmod permissions set in "curl_krb_request.py"
> enforces periodic 0777 as shown in below snippet.
> {code:java}
> curl_krb_cache_path = os.path.join(tmp_dir, "curl_krb_cache")
> if not os.path.exists(curl_krb_cache_path):
> os.makedirs(curl_krb_cache_path)
> os.chmod(curl_krb_cache_path, 0777)
> {code}
> Ref:
> https://github.com/apache/ambari/blob/trunk/ambari-common/src/main/python/resource_management/libraries/functions/curl_krb_request.py
> Hence, code changes need to be done for setting the sticky bit to prevent
> access from users who did not create the specific file.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21970) Enable sticky bit for curl_krb_cache
[
https://issues.apache.org/jira/browse/AMBARI-21970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Chekanskiy updated AMBARI-21970:
---
Status: Patch Available (was: Open)
> Enable sticky bit for curl_krb_cache
>
>
> Key: AMBARI-21970
> URL: https://issues.apache.org/jira/browse/AMBARI-21970
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Krishnama Raju K
>Assignee: Eugene Chekanskiy
>Priority: Minor
> Attachments: AMBARI-21970.patch
>
>
> In secure environment, we see that "/var/lib/ambari-agent/tmp" has sticky bit
> enabled. Trying to enable such permissions ( sticky bit or any other
> permissions ) for "curl_krb_request.py" is being over written after few
> seconds.
> It is observed that the chmod permissions set in "curl_krb_request.py"
> enforces periodic 0777 as shown in below snippet.
> {code:java}
> curl_krb_cache_path = os.path.join(tmp_dir, "curl_krb_cache")
> if not os.path.exists(curl_krb_cache_path):
> os.makedirs(curl_krb_cache_path)
> os.chmod(curl_krb_cache_path, 0777)
> {code}
> Ref:
> https://github.com/apache/ambari/blob/trunk/ambari-common/src/main/python/resource_management/libraries/functions/curl_krb_request.py
> Hence, code changes need to be done for setting the sticky bit to prevent
> access from users who did not create the specific file.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21970) Enable sticky bit for curl_krb_cache
[
https://issues.apache.org/jira/browse/AMBARI-21970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Chekanskiy updated AMBARI-21970:
---
Attachment: AMBARI-21970.patch
> Enable sticky bit for curl_krb_cache
>
>
> Key: AMBARI-21970
> URL: https://issues.apache.org/jira/browse/AMBARI-21970
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Krishnama Raju K
>Assignee: Eugene Chekanskiy
>Priority: Minor
> Attachments: AMBARI-21970.patch
>
>
> In secure environment, we see that "/var/lib/ambari-agent/tmp" has sticky bit
> enabled. Trying to enable such permissions ( sticky bit or any other
> permissions ) for "curl_krb_request.py" is being over written after few
> seconds.
> It is observed that the chmod permissions set in "curl_krb_request.py"
> enforces periodic 0777 as shown in below snippet.
> {code:java}
> curl_krb_cache_path = os.path.join(tmp_dir, "curl_krb_cache")
> if not os.path.exists(curl_krb_cache_path):
> os.makedirs(curl_krb_cache_path)
> os.chmod(curl_krb_cache_path, 0777)
> {code}
> Ref:
> https://github.com/apache/ambari/blob/trunk/ambari-common/src/main/python/resource_management/libraries/functions/curl_krb_request.py
> Hence, code changes need to be done for setting the sticky bit to prevent
> access from users who did not create the specific file.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21993) Pre upgrade check dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-21993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171721#comment-16171721 ] Andrii Tkach commented on AMBARI-21993: --- +1 for the patch > Pre upgrade check dialog style issues > - > > Key: AMBARI-21993 > URL: https://issues.apache.org/jira/browse/AMBARI-21993 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, 2.png, 3.png, AMBARI-21993.patch, > AMBARI-21993_trunk.patch > > > # Top whitespace between text and grey area is to small, but bottom > whitespace between grey area and button area is to big: > !1.png|thumbnail! > # Second text should be the same size as in check while upgrading: > !2.png|thumbnail! !3.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21993) Pre upgrade check dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-21993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171757#comment-16171757 ] Hudson commented on AMBARI-21993: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #243 (See [https://builds.apache.org/job/Ambari-branch-2.6/243/]) AMBARI-21993. Pre upgrade check dialog style issues (alexantonenko) (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=af80df2ec3bc384f8a3ff44ce8fe141f849f0cbb]) * (edit) ambari-web/app/styles/stack_versions.less * (edit) ambari-web/app/templates/main/admin/stack_upgrade/upgrade_options.hbs > Pre upgrade check dialog style issues > - > > Key: AMBARI-21993 > URL: https://issues.apache.org/jira/browse/AMBARI-21993 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, 2.png, 3.png, AMBARI-21993.patch, > AMBARI-21993_trunk.patch > > > # Top whitespace between text and grey area is to small, but bottom > whitespace between grey area and button area is to big: > !1.png|thumbnail! > # Second text should be the same size as in check while upgrading: > !2.png|thumbnail! !3.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21994) Upgrade history view style issue
[ https://issues.apache.org/jira/browse/AMBARI-21994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21994: -- Attachment: AMBARI-21994.patch > Upgrade history view style issue > > > Key: AMBARI-21994 > URL: https://issues.apache.org/jira/browse/AMBARI-21994 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, AMBARI-21994.patch > > > Can we make sure all arrows and labels in dropdown are aligned? > Maybe have to boost the width on the ‘service name’ to accommodate longer > service names -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21993) Pre upgrade check dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-21993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21993: - Description: # Top whitespace between text and grey area is to small, but bottom whitespace between grey area and button area is to big: !1.png|thumbnail! # Second text should be the same size as in check while upgrading: !2.png|thumbnail! !3.png|thumbnail! > Pre upgrade check dialog style issues > - > > Key: AMBARI-21993 > URL: https://issues.apache.org/jira/browse/AMBARI-21993 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, 2.png, 3.png > > > # Top whitespace between text and grey area is to small, but bottom > whitespace between grey area and button area is to big: > !1.png|thumbnail! > # Second text should be the same size as in check while upgrading: > !2.png|thumbnail! !3.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
