[jira] [Commented] (AMBARI-18502) Logging of ambari agent scheduling activities in debug mode
[ https://issues.apache.org/jira/browse/AMBARI-18502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15564553#comment-15564553 ] Hudson commented on AMBARI-18502: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5783 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5783/]) AMBARI-18502: Logging of ambari agent scheduling activities in debug (nsomasundaram: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3e4b368f9bde259b29d3a2e97fd84e773af434c3]) * (edit) ambari-agent/src/main/python/ambari_agent/apscheduler/threadpool.py * (edit) ambari-agent/src/main/python/ambari_agent/apscheduler/scheduler.py > Logging of ambari agent scheduling activities in debug mode > --- > > Key: AMBARI-18502 > URL: https://issues.apache.org/jira/browse/AMBARI-18502 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: trunk >Reporter: Ranjan Banerjee >Priority: Minor > Labels: ambari-agent > Fix For: trunk > > Attachments: AMBARI-18502.patch, AMBARI-18502.patch > > > We find lots of stale alerts in Ambari. On digging deeper from the > Ambari-agent logs it is found that there were many services that missed the > triggering window, but no insight as to why it is missed. The aim of this is > to add some debug logs on two steps primarily: > 1)When the scheduler iterates through the jobstore and decides it is time to > schedule the job. > 2)The threadpool, being forked and executing the callback function -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18502) Logging of ambari agent scheduling activities in debug mode
[ https://issues.apache.org/jira/browse/AMBARI-18502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ranjan Banerjee updated AMBARI-18502: - Resolution: Fixed Status: Resolved (was: Patch Available) Patch is submitted > Logging of ambari agent scheduling activities in debug mode > --- > > Key: AMBARI-18502 > URL: https://issues.apache.org/jira/browse/AMBARI-18502 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: trunk >Reporter: Ranjan Banerjee >Priority: Minor > Labels: ambari-agent > Fix For: trunk > > Attachments: AMBARI-18502.patch, AMBARI-18502.patch > > > We find lots of stale alerts in Ambari. On digging deeper from the > Ambari-agent logs it is found that there were many services that missed the > triggering window, but no insight as to why it is missed. The aim of this is > to add some debug logs on two steps primarily: > 1)When the scheduler iterates through the jobstore and decides it is time to > schedule the job. > 2)The threadpool, being forked and executing the callback function -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18502) Logging of ambari agent scheduling activities in debug mode
[ https://issues.apache.org/jira/browse/AMBARI-18502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1556#comment-1556 ] Ranjan Banerjee commented on AMBARI-18502: -- [~smnaha]Thanks for submitting the patch. I have resolved the issue > Logging of ambari agent scheduling activities in debug mode > --- > > Key: AMBARI-18502 > URL: https://issues.apache.org/jira/browse/AMBARI-18502 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: trunk >Reporter: Ranjan Banerjee >Priority: Minor > Labels: ambari-agent > Fix For: trunk > > Attachments: AMBARI-18502.patch, AMBARI-18502.patch > > > We find lots of stale alerts in Ambari. On digging deeper from the > Ambari-agent logs it is found that there were many services that missed the > triggering window, but no insight as to why it is missed. The aim of this is > to add some debug logs on two steps primarily: > 1)When the scheduler iterates through the jobstore and decides it is time to > schedule the job. > 2)The threadpool, being forked and executing the callback function -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18502) Logging of ambari agent scheduling activities in debug mode
[
https://issues.apache.org/jira/browse/AMBARI-18502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15564433#comment-15564433
]
Hadoop QA commented on AMBARI-18502:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12832586/AMBARI-18502.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/8841//console
This message is automatically generated.
> Logging of ambari agent scheduling activities in debug mode
> ---
>
> Key: AMBARI-18502
> URL: https://issues.apache.org/jira/browse/AMBARI-18502
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: trunk
>Reporter: Ranjan Banerjee
>Priority: Minor
> Labels: ambari-agent
> Fix For: trunk
>
> Attachments: AMBARI-18502.patch, AMBARI-18502.patch
>
>
> We find lots of stale alerts in Ambari. On digging deeper from the
> Ambari-agent logs it is found that there were many services that missed the
> triggering window, but no insight as to why it is missed. The aim of this is
> to add some debug logs on two steps primarily:
> 1)When the scheduler iterates through the jobstore and decides it is time to
> schedule the job.
> 2)The threadpool, being forked and executing the callback function
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18502) Logging of ambari agent scheduling activities in debug mode
[ https://issues.apache.org/jira/browse/AMBARI-18502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15564353#comment-15564353 ] Nahappan Somasundaram commented on AMBARI-18502: [~rabaner] I've submitted the patch. You may resolve the bug. > Logging of ambari agent scheduling activities in debug mode > --- > > Key: AMBARI-18502 > URL: https://issues.apache.org/jira/browse/AMBARI-18502 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: trunk >Reporter: Ranjan Banerjee >Priority: Minor > Labels: ambari-agent > Fix For: trunk > > Attachments: AMBARI-18502.patch, AMBARI-18502.patch > > > We find lots of stale alerts in Ambari. On digging deeper from the > Ambari-agent logs it is found that there were many services that missed the > triggering window, but no insight as to why it is missed. The aim of this is > to add some debug logs on two steps primarily: > 1)When the scheduler iterates through the jobstore and decides it is time to > schedule the job. > 2)The threadpool, being forked and executing the callback function -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18502) Logging of ambari agent scheduling activities in debug mode
[ https://issues.apache.org/jira/browse/AMBARI-18502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15564322#comment-15564322 ] Nahappan Somasundaram commented on AMBARI-18502: I will commit it on your behalf. > Logging of ambari agent scheduling activities in debug mode > --- > > Key: AMBARI-18502 > URL: https://issues.apache.org/jira/browse/AMBARI-18502 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: trunk >Reporter: Ranjan Banerjee >Priority: Minor > Labels: ambari-agent > Fix For: trunk > > Attachments: AMBARI-18502.patch, AMBARI-18502.patch > > > We find lots of stale alerts in Ambari. On digging deeper from the > Ambari-agent logs it is found that there were many services that missed the > triggering window, but no insight as to why it is missed. The aim of this is > to add some debug logs on two steps primarily: > 1)When the scheduler iterates through the jobstore and decides it is time to > schedule the job. > 2)The threadpool, being forked and executing the callback function -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18559) At "Add Service Wizard", when the installation is going on, if I click the close (X) on the wizard, the service will only get INSTALLED not STARTED.
[ https://issues.apache.org/jira/browse/AMBARI-18559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15564229#comment-15564229 ] Hudson commented on AMBARI-18559: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5782 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5782/]) AMBARI-18559 At "Add Service Wizard", when the installation is going on, (zhewang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6587fda470bcf063027e55b315292018dc1e64b4]) * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/routes/add_service_routes.js > At "Add Service Wizard", when the installation is going on, if I click the > close (X) on the wizard, the service will only get INSTALLED not STARTED. > > > Key: AMBARI-18559 > URL: https://issues.apache.org/jira/browse/AMBARI-18559 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 3.0.0 > > Attachments: AMBARI-18559.v0.patch > > > - Typically being in "Add Service Wizard", user expects the INSTALL and START > of sevices components. > - However, if user clicks on the close (X) on the wizard, the service will > only get INSTALLED not STARTED. > - Either apprising the user that only INSTALL will take place and START will > be skipped will help OR even if the close (X) on the wizard is hit, context > for START is still maintained. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18534) Advanced storm-atlas-application.properties panel is not opened by default upon filtering
[ https://issues.apache.org/jira/browse/AMBARI-18534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15564230#comment-15564230 ] Hudson commented on AMBARI-18534: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5782 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5782/]) AMBARI-18534 Advanced storm-atlas-application.properties panel is not (zhewang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8f51c9324a407fa8ce8e92e2e77ee0a250c5cbc9]) * (edit) ambari-web/app/views/common/configs/service_configs_by_category_view.js > Advanced storm-atlas-application.properties panel is not opened by default > upon filtering > - > > Key: AMBARI-18534 > URL: https://issues.apache.org/jira/browse/AMBARI-18534 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Dhanya Balasundaran >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18534.v0.patch > > > - Navigate to Storm configs page > - Type "hook" in the property filter > - Its expected that Advanced storm-atlas-application.properties panel opens > up by default > - Actual: its still closed. please see the screenshot attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18534) Advanced storm-atlas-application.properties panel is not opened by default upon filtering
[ https://issues.apache.org/jira/browse/AMBARI-18534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15564222#comment-15564222 ] Hudson commented on AMBARI-18534: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #134 (See [https://builds.apache.org/job/Ambari-branch-2.5/134/]) AMBARI-18534 Advanced storm-atlas-application.properties panel is not (zhewang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a50861338b39c61d5e7a611b150ef42d1afc1398]) * (edit) ambari-web/app/views/common/configs/service_configs_by_category_view.js > Advanced storm-atlas-application.properties panel is not opened by default > upon filtering > - > > Key: AMBARI-18534 > URL: https://issues.apache.org/jira/browse/AMBARI-18534 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Dhanya Balasundaran >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18534.v0.patch > > > - Navigate to Storm configs page > - Type "hook" in the property filter > - Its expected that Advanced storm-atlas-application.properties panel opens > up by default > - Actual: its still closed. please see the screenshot attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18502) Logging of ambari agent scheduling activities in debug mode
[ https://issues.apache.org/jira/browse/AMBARI-18502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15564206#comment-15564206 ] Ranjan Banerjee commented on AMBARI-18502: -- [~smnaha] Looks like I dont have commit access to apache ambari as I get a permission denied error. Is it possible for you/someone else to grant me commit access? > Logging of ambari agent scheduling activities in debug mode > --- > > Key: AMBARI-18502 > URL: https://issues.apache.org/jira/browse/AMBARI-18502 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: trunk >Reporter: Ranjan Banerjee >Priority: Minor > Labels: ambari-agent > Fix For: trunk > > Attachments: AMBARI-18502.patch, AMBARI-18502.patch > > > We find lots of stale alerts in Ambari. On digging deeper from the > Ambari-agent logs it is found that there were many services that missed the > triggering window, but no insight as to why it is missed. The aim of this is > to add some debug logs on two steps primarily: > 1)When the scheduler iterates through the jobstore and decides it is time to > schedule the job. > 2)The threadpool, being forked and executing the callback function -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-18502) Logging of ambari agent scheduling activities in debug mode
[ https://issues.apache.org/jira/browse/AMBARI-18502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15564089#comment-15564089 ] Ranjan Banerjee edited comment on AMBARI-18502 at 10/11/16 1:18 AM: [~smnaha] Thanks for your comment. Made the change was (Author: rabaner): [~smnaha] Made the change > Logging of ambari agent scheduling activities in debug mode > --- > > Key: AMBARI-18502 > URL: https://issues.apache.org/jira/browse/AMBARI-18502 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: trunk >Reporter: Ranjan Banerjee >Priority: Minor > Labels: ambari-agent > Fix For: trunk > > Attachments: AMBARI-18502.patch, AMBARI-18502.patch > > > We find lots of stale alerts in Ambari. On digging deeper from the > Ambari-agent logs it is found that there were many services that missed the > triggering window, but no insight as to why it is missed. The aim of this is > to add some debug logs on two steps primarily: > 1)When the scheduler iterates through the jobstore and decides it is time to > schedule the job. > 2)The threadpool, being forked and executing the callback function -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18502) Logging of ambari agent scheduling activities in debug mode
[ https://issues.apache.org/jira/browse/AMBARI-18502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15564092#comment-15564092 ] Nahappan Somasundaram commented on AMBARI-18502: Sure, please go ahead with the commit. Thank you. > Logging of ambari agent scheduling activities in debug mode > --- > > Key: AMBARI-18502 > URL: https://issues.apache.org/jira/browse/AMBARI-18502 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: trunk >Reporter: Ranjan Banerjee >Priority: Minor > Labels: ambari-agent > Fix For: trunk > > Attachments: AMBARI-18502.patch, AMBARI-18502.patch > > > We find lots of stale alerts in Ambari. On digging deeper from the > Ambari-agent logs it is found that there were many services that missed the > triggering window, but no insight as to why it is missed. The aim of this is > to add some debug logs on two steps primarily: > 1)When the scheduler iterates through the jobstore and decides it is time to > schedule the job. > 2)The threadpool, being forked and executing the callback function -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18502) Logging of ambari agent scheduling activities in debug mode
[ https://issues.apache.org/jira/browse/AMBARI-18502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15564089#comment-15564089 ] Ranjan Banerjee commented on AMBARI-18502: -- [~smnaha] Made the change > Logging of ambari agent scheduling activities in debug mode > --- > > Key: AMBARI-18502 > URL: https://issues.apache.org/jira/browse/AMBARI-18502 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: trunk >Reporter: Ranjan Banerjee >Priority: Minor > Labels: ambari-agent > Fix For: trunk > > Attachments: AMBARI-18502.patch, AMBARI-18502.patch > > > We find lots of stale alerts in Ambari. On digging deeper from the > Ambari-agent logs it is found that there were many services that missed the > triggering window, but no insight as to why it is missed. The aim of this is > to add some debug logs on two steps primarily: > 1)When the scheduler iterates through the jobstore and decides it is time to > schedule the job. > 2)The threadpool, being forked and executing the callback function -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18502) Logging of ambari agent scheduling activities in debug mode
[ https://issues.apache.org/jira/browse/AMBARI-18502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ranjan Banerjee updated AMBARI-18502: - Attachment: AMBARI-18502.patch > Logging of ambari agent scheduling activities in debug mode > --- > > Key: AMBARI-18502 > URL: https://issues.apache.org/jira/browse/AMBARI-18502 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: trunk >Reporter: Ranjan Banerjee >Priority: Minor > Labels: ambari-agent > Fix For: trunk > > Attachments: AMBARI-18502.patch, AMBARI-18502.patch > > > We find lots of stale alerts in Ambari. On digging deeper from the > Ambari-agent logs it is found that there were many services that missed the > triggering window, but no insight as to why it is missed. The aim of this is > to add some debug logs on two steps primarily: > 1)When the scheduler iterates through the jobstore and decides it is time to > schedule the job. > 2)The threadpool, being forked and executing the callback function -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18502) Logging of ambari agent scheduling activities in debug mode
[ https://issues.apache.org/jira/browse/AMBARI-18502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ranjan Banerjee updated AMBARI-18502: - Attachment: (was: AMBARI-18502.patch) > Logging of ambari agent scheduling activities in debug mode > --- > > Key: AMBARI-18502 > URL: https://issues.apache.org/jira/browse/AMBARI-18502 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: trunk >Reporter: Ranjan Banerjee >Priority: Minor > Labels: ambari-agent > Fix For: trunk > > Attachments: AMBARI-18502.patch > > > We find lots of stale alerts in Ambari. On digging deeper from the > Ambari-agent logs it is found that there were many services that missed the > triggering window, but no insight as to why it is missed. The aim of this is > to add some debug logs on two steps primarily: > 1)When the scheduler iterates through the jobstore and decides it is time to > schedule the job. > 2)The threadpool, being forked and executing the callback function -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18502) Logging of ambari agent scheduling activities in debug mode
[ https://issues.apache.org/jira/browse/AMBARI-18502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ranjan Banerjee updated AMBARI-18502: - Attachment: AMBARI-18502.patch > Logging of ambari agent scheduling activities in debug mode > --- > > Key: AMBARI-18502 > URL: https://issues.apache.org/jira/browse/AMBARI-18502 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: trunk >Reporter: Ranjan Banerjee >Priority: Minor > Labels: ambari-agent > Fix For: trunk > > Attachments: AMBARI-18502.patch, AMBARI-18502.patch > > > We find lots of stale alerts in Ambari. On digging deeper from the > Ambari-agent logs it is found that there were many services that missed the > triggering window, but no insight as to why it is missed. The aim of this is > to add some debug logs on two steps primarily: > 1)When the scheduler iterates through the jobstore and decides it is time to > schedule the job. > 2)The threadpool, being forked and executing the callback function -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18502) Logging of ambari agent scheduling activities in debug mode
[
https://issues.apache.org/jira/browse/AMBARI-18502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15564069#comment-15564069
]
Nahappan Somasundaram commented on AMBARI-18502:
[~rabaner]
Change looks good. A couple of nit-picks:
{code}
logger.debug("Scheduler submitting job %s to run",job.name) // add a space
before job.name
logger.debug('Worker thread starting job %s',args[0]) // add a space before
args[0]
{code}
> Logging of ambari agent scheduling activities in debug mode
> ---
>
> Key: AMBARI-18502
> URL: https://issues.apache.org/jira/browse/AMBARI-18502
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: trunk
>Reporter: Ranjan Banerjee
>Priority: Minor
> Labels: ambari-agent
> Fix For: trunk
>
> Attachments: AMBARI-18502.patch
>
>
> We find lots of stale alerts in Ambari. On digging deeper from the
> Ambari-agent logs it is found that there were many services that missed the
> triggering window, but no insight as to why it is missed. The aim of this is
> to add some debug logs on two steps primarily:
> 1)When the scheduler iterates through the jobstore and decides it is time to
> schedule the job.
> 2)The threadpool, being forked and executing the callback function
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18566) Installer wizard-> Select Versions page: Selecting Red Hat Satellite option and clicking next button makes wizard stuck
[
https://issues.apache.org/jira/browse/AMBARI-18566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15564041#comment-15564041
]
Hadoop QA commented on AMBARI-18566:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12832570/AMBARI-18566.v0.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8840//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8840//console
This message is automatically generated.
> Installer wizard-> Select Versions page: Selecting Red Hat Satellite option
> and clicking next button makes wizard stuck
> ---
>
> Key: AMBARI-18566
> URL: https://issues.apache.org/jira/browse/AMBARI-18566
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18566.v0.patch
>
>
> *STR:*
> # Got to select versions page
> # Choose "Use Local Repository" option and then choose "Use RedHat
> Satellite/Spacewalk" option
> # Next button will get enabled. click on next button.
> *Expected Result:* wizard goes to next page
> *Actual Result:* On clicking next button, next button gets disabled and
> wizard does not go to next page.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-18502) Logging of ambari agent scheduling activities in debug mode
[ https://issues.apache.org/jira/browse/AMBARI-18502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15564036#comment-15564036 ] Ranjan Banerjee edited comment on AMBARI-18502 at 10/11/16 12:48 AM: - No tests as it is a patch containing debug statements was (Author: rabaner): No tests as it is a debug patch > Logging of ambari agent scheduling activities in debug mode > --- > > Key: AMBARI-18502 > URL: https://issues.apache.org/jira/browse/AMBARI-18502 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: trunk >Reporter: Ranjan Banerjee >Priority: Minor > Labels: ambari-agent > Fix For: trunk > > Attachments: AMBARI-18502.patch > > > We find lots of stale alerts in Ambari. On digging deeper from the > Ambari-agent logs it is found that there were many services that missed the > triggering window, but no insight as to why it is missed. The aim of this is > to add some debug logs on two steps primarily: > 1)When the scheduler iterates through the jobstore and decides it is time to > schedule the job. > 2)The threadpool, being forked and executing the callback function -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18502) Logging of ambari agent scheduling activities in debug mode
[ https://issues.apache.org/jira/browse/AMBARI-18502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15564036#comment-15564036 ] Ranjan Banerjee commented on AMBARI-18502: -- No tests as it is a debug patch > Logging of ambari agent scheduling activities in debug mode > --- > > Key: AMBARI-18502 > URL: https://issues.apache.org/jira/browse/AMBARI-18502 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: trunk >Reporter: Ranjan Banerjee >Priority: Minor > Labels: ambari-agent > Fix For: trunk > > Attachments: AMBARI-18502.patch > > > We find lots of stale alerts in Ambari. On digging deeper from the > Ambari-agent logs it is found that there were many services that missed the > triggering window, but no insight as to why it is missed. The aim of this is > to add some debug logs on two steps primarily: > 1)When the scheduler iterates through the jobstore and decides it is time to > schedule the job. > 2)The threadpool, being forked and executing the callback function -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18502) Logging of ambari agent scheduling activities in debug mode
[
https://issues.apache.org/jira/browse/AMBARI-18502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15563993#comment-15563993
]
Hadoop QA commented on AMBARI-18502:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12832575/AMBARI-18502.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8839//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8839//console
This message is automatically generated.
> Logging of ambari agent scheduling activities in debug mode
> ---
>
> Key: AMBARI-18502
> URL: https://issues.apache.org/jira/browse/AMBARI-18502
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: trunk
>Reporter: Ranjan Banerjee
>Priority: Minor
> Labels: ambari-agent
> Fix For: trunk
>
> Attachments: AMBARI-18502.patch
>
>
> We find lots of stale alerts in Ambari. On digging deeper from the
> Ambari-agent logs it is found that there were many services that missed the
> triggering window, but no insight as to why it is missed. The aim of this is
> to add some debug logs on two steps primarily:
> 1)When the scheduler iterates through the jobstore and decides it is time to
> schedule the job.
> 2)The threadpool, being forked and executing the callback function
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18502) Logging of ambari agent scheduling activities in debug mode
[ https://issues.apache.org/jira/browse/AMBARI-18502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ranjan Banerjee updated AMBARI-18502: - Attachment: AMBARI-18502.patch > Logging of ambari agent scheduling activities in debug mode > --- > > Key: AMBARI-18502 > URL: https://issues.apache.org/jira/browse/AMBARI-18502 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: trunk >Reporter: Ranjan Banerjee >Priority: Minor > Labels: ambari-agent > Fix For: trunk > > Attachments: AMBARI-18502.patch > > > We find lots of stale alerts in Ambari. On digging deeper from the > Ambari-agent logs it is found that there were many services that missed the > triggering window, but no insight as to why it is missed. The aim of this is > to add some debug logs on two steps primarily: > 1)When the scheduler iterates through the jobstore and decides it is time to > schedule the job. > 2)The threadpool, being forked and executing the callback function -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18502) Logging of ambari agent scheduling activities in debug mode
[ https://issues.apache.org/jira/browse/AMBARI-18502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ranjan Banerjee updated AMBARI-18502: - Attachment: (was: AMBARI-18502.patch) > Logging of ambari agent scheduling activities in debug mode > --- > > Key: AMBARI-18502 > URL: https://issues.apache.org/jira/browse/AMBARI-18502 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: trunk >Reporter: Ranjan Banerjee >Priority: Minor > Labels: ambari-agent > Fix For: trunk > > > We find lots of stale alerts in Ambari. On digging deeper from the > Ambari-agent logs it is found that there were many services that missed the > triggering window, but no insight as to why it is missed. The aim of this is > to add some debug logs on two steps primarily: > 1)When the scheduler iterates through the jobstore and decides it is time to > schedule the job. > 2)The threadpool, being forked and executing the callback function -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18502) Logging of ambari agent scheduling activities in debug mode
[ https://issues.apache.org/jira/browse/AMBARI-18502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ranjan Banerjee updated AMBARI-18502: - Attachment: AMBARI-18502.patch > Logging of ambari agent scheduling activities in debug mode > --- > > Key: AMBARI-18502 > URL: https://issues.apache.org/jira/browse/AMBARI-18502 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: trunk >Reporter: Ranjan Banerjee >Priority: Minor > Labels: ambari-agent > Fix For: trunk > > Attachments: AMBARI-18502.patch > > > We find lots of stale alerts in Ambari. On digging deeper from the > Ambari-agent logs it is found that there were many services that missed the > triggering window, but no insight as to why it is missed. The aim of this is > to add some debug logs on two steps primarily: > 1)When the scheduler iterates through the jobstore and decides it is time to > schedule the job. > 2)The threadpool, being forked and executing the callback function -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18502) Logging of ambari agent scheduling activities in debug mode
[ https://issues.apache.org/jira/browse/AMBARI-18502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ranjan Banerjee updated AMBARI-18502: - Labels: ambari-agent (was: ) Fix Version/s: trunk Affects Version/s: trunk Status: Patch Available (was: Open) Added debug logging to better understand if a scheduler has missed scheduling the job or there is a threadpool delay in getting to the required job. Will help in the case of stale alerts > Logging of ambari agent scheduling activities in debug mode > --- > > Key: AMBARI-18502 > URL: https://issues.apache.org/jira/browse/AMBARI-18502 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: trunk >Reporter: Ranjan Banerjee >Priority: Minor > Labels: ambari-agent > Fix For: trunk > > > We find lots of stale alerts in Ambari. On digging deeper from the > Ambari-agent logs it is found that there were many services that missed the > triggering window, but no insight as to why it is missed. The aim of this is > to add some debug logs on two steps primarily: > 1)When the scheduler iterates through the jobstore and decides it is time to > schedule the job. > 2)The threadpool, being forked and executing the callback function -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18559) At "Add Service Wizard", when the installation is going on, if I click the close (X) on the wizard, the service will only get INSTALLED not STARTED.
[ https://issues.apache.org/jira/browse/AMBARI-18559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18559: Resolution: Fixed Status: Resolved (was: Patch Available) Patch committed to trunk 6587fda470bcf063027e55b315292018dc1e64b4 > At "Add Service Wizard", when the installation is going on, if I click the > close (X) on the wizard, the service will only get INSTALLED not STARTED. > > > Key: AMBARI-18559 > URL: https://issues.apache.org/jira/browse/AMBARI-18559 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 3.0.0 > > Attachments: AMBARI-18559.v0.patch > > > - Typically being in "Add Service Wizard", user expects the INSTALL and START > of sevices components. > - However, if user clicks on the close (X) on the wizard, the service will > only get INSTALLED not STARTED. > - Either apprising the user that only INSTALL will take place and START will > be skipped will help OR even if the close (X) on the wizard is hit, context > for START is still maintained. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18534) Advanced storm-atlas-application.properties panel is not opened by default upon filtering
[ https://issues.apache.org/jira/browse/AMBARI-18534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18534: Resolution: Fixed Status: Resolved (was: Patch Available) Patch committed to trunk and branch-2.5 8f51c9324a407fa8ce8e92e2e77ee0a250c5cbc9 > Advanced storm-atlas-application.properties panel is not opened by default > upon filtering > - > > Key: AMBARI-18534 > URL: https://issues.apache.org/jira/browse/AMBARI-18534 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Dhanya Balasundaran >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18534.v0.patch > > > - Navigate to Storm configs page > - Type "hook" in the property filter > - Its expected that Advanced storm-atlas-application.properties panel opens > up by default > - Actual: its still closed. please see the screenshot attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18566) Installer wizard-> Select Versions page: Selecting Red Hat Satellite option and clicking next button makes wizard stuck
[ https://issues.apache.org/jira/browse/AMBARI-18566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18566: Status: Patch Available (was: Open) > Installer wizard-> Select Versions page: Selecting Red Hat Satellite option > and clicking next button makes wizard stuck > --- > > Key: AMBARI-18566 > URL: https://issues.apache.org/jira/browse/AMBARI-18566 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18566.v0.patch > > > *STR:* > # Got to select versions page > # Choose "Use Local Repository" option and then choose "Use RedHat > Satellite/Spacewalk" option > # Next button will get enabled. click on next button. > *Expected Result:* wizard goes to next page > *Actual Result:* On clicking next button, next button gets disabled and > wizard does not go to next page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18566) Installer wizard-> Select Versions page: Selecting Red Hat Satellite option and clicking next button makes wizard stuck
[ https://issues.apache.org/jira/browse/AMBARI-18566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18566: Attachment: AMBARI-18566.v0.patch Local ambari-web test passed. 30374 tests complete (27 seconds) 151 tests pending Manual testing done > Installer wizard-> Select Versions page: Selecting Red Hat Satellite option > and clicking next button makes wizard stuck > --- > > Key: AMBARI-18566 > URL: https://issues.apache.org/jira/browse/AMBARI-18566 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18566.v0.patch > > > *STR:* > # Got to select versions page > # Choose "Use Local Repository" option and then choose "Use RedHat > Satellite/Spacewalk" option > # Next button will get enabled. click on next button. > *Expected Result:* wizard goes to next page > *Actual Result:* On clicking next button, next button gets disabled and > wizard does not go to next page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18566) Installer wizard-> Select Versions page: Selecting Red Hat Satellite option and clicking next button makes wizard stuck
Zhe (Joe) Wang created AMBARI-18566: --- Summary: Installer wizard-> Select Versions page: Selecting Red Hat Satellite option and clicking next button makes wizard stuck Key: AMBARI-18566 URL: https://issues.apache.org/jira/browse/AMBARI-18566 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Zhe (Joe) Wang Assignee: Zhe (Joe) Wang Priority: Critical Fix For: 2.4.2 *STR:* # Got to select versions page # Choose "Use Local Repository" option and then choose "Use RedHat Satellite/Spacewalk" option # Next button will get enabled. click on next button. *Expected Result:* wizard goes to next page *Actual Result:* On clicking next button, next button gets disabled and wizard does not go to next page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18355) Introduce conditional dependencies in stack defition to handle blueprint validation gracefully
[ https://issues.apache.org/jira/browse/AMBARI-18355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-18355: --- Attachment: (was: AMBARI-18355_v3.patch) > Introduce conditional dependencies in stack defition to handle blueprint > validation gracefully > -- > > Key: AMBARI-18355 > URL: https://issues.apache.org/jira/browse/AMBARI-18355 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-18355.patch, AMBARI-18355_v4.patch, > AMBARI-18355_v5.patch, AMBARI-18355_v6.patch, Adding Conditional > Dependencies.pdf > > > Currently stack definitions do not list conditional dependencies, adding > those to the stack definitions would make it easy to validate errors in case > of blueprint deployment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18355) Introduce conditional dependencies in stack defition to handle blueprint validation gracefully
[ https://issues.apache.org/jira/browse/AMBARI-18355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-18355: --- Attachment: (was: AMBARI-18355_v1.patch) > Introduce conditional dependencies in stack defition to handle blueprint > validation gracefully > -- > > Key: AMBARI-18355 > URL: https://issues.apache.org/jira/browse/AMBARI-18355 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-18355.patch, AMBARI-18355_v4.patch, > AMBARI-18355_v5.patch, AMBARI-18355_v6.patch, Adding Conditional > Dependencies.pdf > > > Currently stack definitions do not list conditional dependencies, adding > those to the stack definitions would make it easy to validate errors in case > of blueprint deployment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18355) Introduce conditional dependencies in stack defition to handle blueprint validation gracefully
[ https://issues.apache.org/jira/browse/AMBARI-18355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-18355: --- Attachment: (was: AMBARI-18355_v2.patch) > Introduce conditional dependencies in stack defition to handle blueprint > validation gracefully > -- > > Key: AMBARI-18355 > URL: https://issues.apache.org/jira/browse/AMBARI-18355 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-18355.patch, AMBARI-18355_v4.patch, > AMBARI-18355_v5.patch, AMBARI-18355_v6.patch, Adding Conditional > Dependencies.pdf > > > Currently stack definitions do not list conditional dependencies, adding > those to the stack definitions would make it easy to validate errors in case > of blueprint deployment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18355) Introduce conditional dependencies in stack defition to handle blueprint validation gracefully
[ https://issues.apache.org/jira/browse/AMBARI-18355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-18355: --- Status: Patch Available (was: In Progress) > Introduce conditional dependencies in stack defition to handle blueprint > validation gracefully > -- > > Key: AMBARI-18355 > URL: https://issues.apache.org/jira/browse/AMBARI-18355 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-18355.patch, AMBARI-18355_v1.patch, > AMBARI-18355_v2.patch, AMBARI-18355_v3.patch, AMBARI-18355_v4.patch, > AMBARI-18355_v5.patch, AMBARI-18355_v6.patch, Adding Conditional > Dependencies.pdf > > > Currently stack definitions do not list conditional dependencies, adding > those to the stack definitions would make it easy to validate errors in case > of blueprint deployment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18355) Introduce conditional dependencies in stack defition to handle blueprint validation gracefully
[ https://issues.apache.org/jira/browse/AMBARI-18355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-18355: --- Attachment: AMBARI-18355_v6.patch > Introduce conditional dependencies in stack defition to handle blueprint > validation gracefully > -- > > Key: AMBARI-18355 > URL: https://issues.apache.org/jira/browse/AMBARI-18355 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-18355.patch, AMBARI-18355_v1.patch, > AMBARI-18355_v2.patch, AMBARI-18355_v3.patch, AMBARI-18355_v4.patch, > AMBARI-18355_v5.patch, AMBARI-18355_v6.patch, Adding Conditional > Dependencies.pdf > > > Currently stack definitions do not list conditional dependencies, adding > those to the stack definitions would make it easy to validate errors in case > of blueprint deployment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18565) Deprecate old UpgradeCatalog Unit Tests
[ https://issues.apache.org/jira/browse/AMBARI-18565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18565: - Attachment: AMBARI-18565.branch-2.5.patch AMBARI-18565.trunk.patch > Deprecate old UpgradeCatalog Unit Tests > --- > > Key: AMBARI-18565 > URL: https://issues.apache.org/jira/browse/AMBARI-18565 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-18565.branch-2.5.patch, AMBARI-18565.trunk.patch > > > Deprecate the older UpgradeCatalog tests that are no longer needed to > decrease time it takes to run unit tests. > UpgradeCatalog150Test > UpgradeCatalog151Test > UpgradeCatalog160Test > UpgradeCatalog161Test > UpgradeCatalog170Test -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18565) Deprecate old UpgradeCatalog Unit Tests
Alejandro Fernandez created AMBARI-18565: Summary: Deprecate old UpgradeCatalog Unit Tests Key: AMBARI-18565 URL: https://issues.apache.org/jira/browse/AMBARI-18565 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 2.5.0 Reporter: Alejandro Fernandez Assignee: Alejandro Fernandez Fix For: 2.5.0 Deprecate the older UpgradeCatalog tests that are no longer needed to decrease time it takes to run unit tests. UpgradeCatalog150Test UpgradeCatalog151Test UpgradeCatalog160Test UpgradeCatalog161Test UpgradeCatalog170Test -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18543) Option to enable request/access logs in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-18543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] amarnathreddy updated AMBARI-18543: --- Resolution: Fixed Fix Version/s: trnk Status: Resolved (was: Patch Available) Adding "server.requestlogs.path" property in ambari.properties file will create and start logging request logs. > Option to enable request/access logs in Ambari > -- > > Key: AMBARI-18543 > URL: https://issues.apache.org/jira/browse/AMBARI-18543 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: amarnathreddy >Assignee: amarnathreddy >Priority: Minor > Fix For: trnk > > Attachments: AMBARI-18543.patch > > > Currently there is no option to enable the request/access logs. these logs > would be useful for support team. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18543) Option to enable request/access logs in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-18543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] amarnathreddy updated AMBARI-18543: --- Attachment: AMBARI-18543.patch > Option to enable request/access logs in Ambari > -- > > Key: AMBARI-18543 > URL: https://issues.apache.org/jira/browse/AMBARI-18543 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: amarnathreddy >Assignee: amarnathreddy >Priority: Minor > Attachments: AMBARI-18543.patch > > > Currently there is no option to enable the request/access logs. these logs > would be useful for support team. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18543) Option to enable request/access logs in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-18543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] amarnathreddy updated AMBARI-18543: --- Status: Patch Available (was: In Progress) > Option to enable request/access logs in Ambari > -- > > Key: AMBARI-18543 > URL: https://issues.apache.org/jira/browse/AMBARI-18543 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: amarnathreddy >Assignee: amarnathreddy >Priority: Minor > > Currently there is no option to enable the request/access logs. these logs > would be useful for support team. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18557) Create Component to Repo Version associations
[ https://issues.apache.org/jira/browse/AMBARI-18557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-18557: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Create Component to Repo Version associations > - > > Key: AMBARI-18557 > URL: https://issues.apache.org/jira/browse/AMBARI-18557 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18557.patch > > > Create schema changes for component->repo_version relationships. > This isn't the full implementation, just a separation of tasks for ease of > review. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18557) Create Component to Repo Version associations
[ https://issues.apache.org/jira/browse/AMBARI-18557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15563383#comment-15563383 ] Nate Cole commented on AMBARI-18557: Patch is against feature branch; tests won't pass on trunk > Create Component to Repo Version associations > - > > Key: AMBARI-18557 > URL: https://issues.apache.org/jira/browse/AMBARI-18557 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18557.patch > > > Create schema changes for component->repo_version relationships. > This isn't the full implementation, just a separation of tasks for ease of > review. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18554) Improve package handling in Microsoft R Server Mpack
[ https://issues.apache.org/jira/browse/AMBARI-18554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15563215#comment-15563215 ] Hudson commented on AMBARI-18554: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #131 (See [https://builds.apache.org/job/Ambari-branch-2.5/131/]) AMBARI-18554. Improve package handling in Microsoft R Server Mpack (smagyari: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=99668f91320edbf5cc24fdfdceeaa2b3988586f4]) * (edit) contrib/management-packs/microsoft-r_mpack/src/main/resources/common-services/MICROSOFT_R/8.0.5/package/scripts/microsoft_r.py * (edit) contrib/management-packs/microsoft-r_mpack/src/main/resources/custom-services/MICROSOFT_R/8.0.5/metainfo.xml > Improve package handling in Microsoft R Server Mpack > > > Key: AMBARI-18554 > URL: https://issues.apache.org/jira/browse/AMBARI-18554 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári > Fix For: 2.5.0, 2.4.2 > > Attachments: AMBARI-18554-improved-package-handling-trunk-v1.patch > > > 1. use self.install_packages() > 2. declare package list in metainfo.xml instead of the install script -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17311) Modify HTTP headers to follow best security practices
[ https://issues.apache.org/jira/browse/AMBARI-17311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-17311: Resolution: Fixed Status: Resolved (was: Patch Available) > Modify HTTP headers to follow best security practices > - > > Key: AMBARI-17311 > URL: https://issues.apache.org/jira/browse/AMBARI-17311 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: trunk > > Attachments: AMBARI-17311.patch, AMBARI-17311.patch > > > Add the following HTTP headers to follow security best practices. > X-Content-Type-Options: nosniff > Cache-control: no-store > Pragma: no-cache -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18302) Desired state of client component should not be changed in case configuration changes are applied through a "Restart"
[ https://issues.apache.org/jira/browse/AMBARI-18302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-18302: -- Fix Version/s: (was: trunk) 2.5.0 > Desired state of client component should not be changed in case configuration > changes are applied through a "Restart" > - > > Key: AMBARI-18302 > URL: https://issues.apache.org/jira/browse/AMBARI-18302 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Laszlo Puskas >Assignee: Laszlo Puskas > Fix For: 2.5.0 > > Attachments: AMBARI-18302.trunk.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > Configuration changes are propagated to host components by issuing a restart > of the affected components. > In case of master components this action will start the affected components > (regardless it is in INSTALLED or STARTED state) and the desired state will > be set to STARTED. > In Ambari client components are always expected to be in INSTALLED state. > However upon configuration changes, the desired state of these components are > also set to STARTED. This may be misleading for ambari API users that > determine component states by checking the desired state and actual state. > (The actual state in case of client components will always be INSTALLED) > This issue addresses this problem by not updating the desired state when > client components are restarted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18462) Cannot enable Atlas HA in HDP 2.5 because server cardinality should be 1+
[
https://issues.apache.org/jira/browse/AMBARI-18462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-18462:
-
Description:
In HDP 2.5, cannot enable Atlas Server HA because the cardinality is set to 1
instead of 1+
http://server:8080/api/v1/stacks/HDP/versions/2.5/services/ATLAS/components/ATLAS_SERVER
{code}
cardinality: "1"
{code}
Looks like a copy-paste error while committing on behalf of another dev,
https://github.com/apache/ambari/commit/e662dcb7c82ee3fa5ebad2b4d61d1459dd71a0f2
ambari-server/src/main/resources/stacks/HDP/2.5/services/ATLAS/metainfo.xml
*Workaround:*
Edit
/var/lib/ambari-server/resources/stacks/HDP/2.5/services/ATLAS/metainfo.xml and
change cardinality of Atlas Server from "1" to "1+" and restart Ambari Server
was:
In HDP 2.5, cannot enable Atlas Server HA because the cardinality is set to 1
instead of 1+
http://server:8080/api/v1/stacks/HDP/versions/2.5/services/ATLAS/components/ATLAS_SERVER
{code}
cardinality: "1"
{code}
Looks like a copy-paste error while committing on behalf of another dev,
https://github.com/apache/ambari/commit/e662dcb7c82ee3fa5ebad2b4d61d1459dd71a0f2
ambari-server/src/main/resources/stacks/HDP/2.5/services/ATLAS/metainfo.xml
> Cannot enable Atlas HA in HDP 2.5 because server cardinality should be 1+
> -
>
> Key: AMBARI-18462
> URL: https://issues.apache.org/jira/browse/AMBARI-18462
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1, 2.4.2
>Reporter: Ayub Khan
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18462.patch,
> Ambari-2.4.0.0-1144-HA-enable-working.png, Ambari-2.4.0.1-1-not-working.png
>
>
> In HDP 2.5, cannot enable Atlas Server HA because the cardinality is set to 1
> instead of 1+
> http://server:8080/api/v1/stacks/HDP/versions/2.5/services/ATLAS/components/ATLAS_SERVER
> {code}
> cardinality: "1"
> {code}
> Looks like a copy-paste error while committing on behalf of another dev,
> https://github.com/apache/ambari/commit/e662dcb7c82ee3fa5ebad2b4d61d1459dd71a0f2
> ambari-server/src/main/resources/stacks/HDP/2.5/services/ATLAS/metainfo.xml
> *Workaround:*
> Edit
> /var/lib/ambari-server/resources/stacks/HDP/2.5/services/ATLAS/metainfo.xml
> and change cardinality of Atlas Server from "1" to "1+" and restart Ambari
> Server
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18538) Microsoft R Server management pack should support for Redhat 7
[ https://issues.apache.org/jira/browse/AMBARI-18538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562943#comment-15562943 ] Hudson commented on AMBARI-18538: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5780 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5780/]) AMBARI-18538. Microsoft R Server management pack should support for (smagyari: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=24161edf9f8a81592b120640bfa75a6ef3b1e0a1]) * (edit) contrib/management-packs/microsoft-r_mpack/src/main/resources/custom-services/MICROSOFT_R/8.0.5/repos/repoinfo.xml > Microsoft R Server management pack should support for Redhat 7 > -- > > Key: AMBARI-18538 > URL: https://issues.apache.org/jira/browse/AMBARI-18538 > Project: Ambari > Issue Type: Test > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári > Fix For: 2.5.0, 2.4.2 > > Attachments: AMBARI-18538-centos-7-trunk-v1.patch > > > Add Redhat 7 support to repo.xml, test the mpack on Redhat 7. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18562) Cannot update repository on the UI
[ https://issues.apache.org/jira/browse/AMBARI-18562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562944#comment-15562944 ] Hudson commented on AMBARI-18562: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5780 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5780/]) AMBARI-18562 Cannot update repository on the UI. (atkach) (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=da7b2ae1f72dc3e264e2ad0919fe6204de9d9b97]) * (edit) ambari-web/test/controllers/main/admin/stack_and_upgrade_controller_test.js * (edit) ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js > Cannot update repository on the UI > -- > > Key: AMBARI-18562 > URL: https://issues.apache.org/jira/browse/AMBARI-18562 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.5.0 > > Attachments: AMBARI-18562.patch, save_repo_1.png, save_repo_2.png > > > The problem described below occurs on trunk builds. It does not occur on > branch-2.4 and branch-2.5 builds. > 1. Install a simple cluster (HDFS+YARN+ZK is enough) > 2. On the UI, go 'Admin' --> 'Stacks and versions' --> Select the 'Versions' > tab --> Click on the "show details" link --> click on the editor icon > 3. Change one of the repo url's to a different but valid one > 4. Press save > 5. Nothing happens. If you uncheck the "skip validation" checkbox, then the > repo is sometimes saved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18545) Kerberos server actions should not timeout in minutes as specified in configuration
[
https://issues.apache.org/jira/browse/AMBARI-18545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562941#comment-15562941
]
Hudson commented on AMBARI-18545:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5780 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5780/])
AMBARI-18545. Kerberos server actions should not timeout in minutes as (rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0a61db5666f3ee8b82cdab0d50a1c8450b177ae7])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelperImpl.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/serveraction/ServerAction.java
> Kerberos server actions should not timeout in minutes as specified in
> configuration
> ---
>
> Key: AMBARI-18545
> URL: https://issues.apache.org/jira/browse/AMBARI-18545
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: kerberos
> Fix For: 2.5.0
>
> Attachments: AMBARI-18545_branch-2.4_01.patch,
> AMBARI-18545_branch-2.4_02.patch, AMBARI-18545_branch-2.5_01.patch,
> AMBARI-18545_branch-2.5_02.patch, AMBARI-18545_trunk_01.patch,
> AMBARI-18545_trunk_02.patch
>
>
> Kerberos related server-side actions should not time out in minutes as
> specified in configuration. Some Kerberos-related task can potentially take
> a much longer time based on number of hosts and components installed in the
> cluster.
> The {{Create Principals}} and {{Create Keytab Files}} stages need to be set
> to a rather large timeout value such that
> {noformat}
> if server.task.timeout < X
> timeout = X;
> else
> timeout = server.task.timeout
> Where X is set to something like 10 hours.
> {noformat}
> 10 hours seems to be a reasonable timeout value since it is not possible to
> specified an unlimited amount of time give Ambari's current task processing
> infrastructure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17311) Modify HTTP headers to follow best security practices
[ https://issues.apache.org/jira/browse/AMBARI-17311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562940#comment-15562940 ] Hudson commented on AMBARI-17311: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5780 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5780/]) AMBARI-17311. Modify HTTP headers to follow best security practices (rlevas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=34c5686c3a0f80a5c7b78ddf05bb41cb13202438]) * (edit) ambari-server/conf/windows/ambari.properties * (edit) ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java * (edit) ambari-server/conf/unix/ambari.properties * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/AmbariViewsSecurityHeaderFilter.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/AmbariServerSecurityHeaderFilterTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/AmbariViewsSecurityHeaderFilterTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/AmbariServerSecurityHeaderFilter.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/AbstractSecurityHeaderFilter.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/AbstractSecurityHeaderFilterTest.java > Modify HTTP headers to follow best security practices > - > > Key: AMBARI-17311 > URL: https://issues.apache.org/jira/browse/AMBARI-17311 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: trunk > > Attachments: AMBARI-17311.patch, AMBARI-17311.patch > > > Add the following HTTP headers to follow security best practices. > X-Content-Type-Options: nosniff > Cache-control: no-store > Pragma: no-cache -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18554) Improve package handling in Microsoft R Server Mpack
[ https://issues.apache.org/jira/browse/AMBARI-18554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562933#comment-15562933 ] Hudson commented on AMBARI-18554: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5780 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5780/]) AMBARI-18554. Improve package handling in Microsoft R Server Mpack (smagyari: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0d7689d844c1099facc6f6c6c10ba19f786de28a]) * (edit) contrib/management-packs/microsoft-r_mpack/src/main/resources/custom-services/MICROSOFT_R/8.0.5/metainfo.xml * (edit) contrib/management-packs/microsoft-r_mpack/src/main/resources/common-services/MICROSOFT_R/8.0.5/package/scripts/microsoft_r.py > Improve package handling in Microsoft R Server Mpack > > > Key: AMBARI-18554 > URL: https://issues.apache.org/jira/browse/AMBARI-18554 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári > Fix For: 2.5.0, 2.4.2 > > Attachments: AMBARI-18554-improved-package-handling-trunk-v1.patch > > > 1. use self.install_packages() > 2. declare package list in metainfo.xml instead of the install script -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18563) Ambari startup script doesn't work on SUSE and potentially other OS's.
[ https://issues.apache.org/jira/browse/AMBARI-18563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562936#comment-15562936 ] Hudson commented on AMBARI-18563: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5780 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5780/]) AMBARI-18563. Ambari startup script doesn't work on SUSE and potentially (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a80c5a2dbaa0c48f7df87dae6a23a027c2ab6022]) * (edit) ambari-server/sbin/ambari-server * (edit) ambari-server/conf/unix/install-helper.sh > Ambari startup script doesn't work on SUSE and potentially other OS's. > -- > > Key: AMBARI-18563 > URL: https://issues.apache.org/jira/browse/AMBARI-18563 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.2 > > Attachments: AMBARI-18563.patch > > > Since installing the new 2.4.0.1 on SLES 11 the ambari startup script doesn't > work on server boot or reboot. It seems to be the SED line called in the > ambari startup script that doesn't account for a directory structure of > /etc/init.d/rc3.d to populate $ROOT. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18562) Cannot update repository on the UI
[ https://issues.apache.org/jira/browse/AMBARI-18562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562913#comment-15562913 ] Hudson commented on AMBARI-18562: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #130 (See [https://builds.apache.org/job/Ambari-branch-2.5/130/]) AMBARI-18562 Cannot update repository on the UI. (atkach) (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=eeccd3a777245de7be690d8f8e0e510582bcc680]) * (edit) ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js * (edit) ambari-web/test/controllers/main/admin/stack_and_upgrade_controller_test.js > Cannot update repository on the UI > -- > > Key: AMBARI-18562 > URL: https://issues.apache.org/jira/browse/AMBARI-18562 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.5.0 > > Attachments: AMBARI-18562.patch, save_repo_1.png, save_repo_2.png > > > The problem described below occurs on trunk builds. It does not occur on > branch-2.4 and branch-2.5 builds. > 1. Install a simple cluster (HDFS+YARN+ZK is enough) > 2. On the UI, go 'Admin' --> 'Stacks and versions' --> Select the 'Versions' > tab --> Click on the "show details" link --> click on the editor icon > 3. Change one of the repo url's to a different but valid one > 4. Press save > 5. Nothing happens. If you uncheck the "skip validation" checkbox, then the > repo is sometimes saved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18538) Microsoft R Server management pack should support for Redhat 7
[ https://issues.apache.org/jira/browse/AMBARI-18538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562908#comment-15562908 ] Hudson commented on AMBARI-18538: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #130 (See [https://builds.apache.org/job/Ambari-branch-2.5/130/]) AMBARI-18538. Microsoft R Server management pack should support for (smagyari: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4b45e3c86a593dad2a2351df4b95c0fa333198b5]) * (edit) contrib/management-packs/microsoft-r_mpack/src/main/resources/custom-services/MICROSOFT_R/8.0.5/repos/repoinfo.xml > Microsoft R Server management pack should support for Redhat 7 > -- > > Key: AMBARI-18538 > URL: https://issues.apache.org/jira/browse/AMBARI-18538 > Project: Ambari > Issue Type: Test > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári > Fix For: 2.5.0, 2.4.2 > > Attachments: AMBARI-18538-centos-7-trunk-v1.patch > > > Add Redhat 7 support to repo.xml, test the mpack on Redhat 7. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18545) Kerberos server actions should not timeout in minutes as specified in configuration
[
https://issues.apache.org/jira/browse/AMBARI-18545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562905#comment-15562905
]
Hudson commented on AMBARI-18545:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #130 (See
[https://builds.apache.org/job/Ambari-branch-2.5/130/])
AMBARI-18545. Kerberos server actions should not timeout in minutes as (rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=367c2c95b260fc41fc6708549efe9cbcb0b3bd95])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelperImpl.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/serveraction/ServerAction.java
> Kerberos server actions should not timeout in minutes as specified in
> configuration
> ---
>
> Key: AMBARI-18545
> URL: https://issues.apache.org/jira/browse/AMBARI-18545
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: kerberos
> Fix For: 2.5.0
>
> Attachments: AMBARI-18545_branch-2.4_01.patch,
> AMBARI-18545_branch-2.4_02.patch, AMBARI-18545_branch-2.5_01.patch,
> AMBARI-18545_branch-2.5_02.patch, AMBARI-18545_trunk_01.patch,
> AMBARI-18545_trunk_02.patch
>
>
> Kerberos related server-side actions should not time out in minutes as
> specified in configuration. Some Kerberos-related task can potentially take
> a much longer time based on number of hosts and components installed in the
> cluster.
> The {{Create Principals}} and {{Create Keytab Files}} stages need to be set
> to a rather large timeout value such that
> {noformat}
> if server.task.timeout < X
> timeout = X;
> else
> timeout = server.task.timeout
> Where X is set to something like 10 hours.
> {noformat}
> 10 hours seems to be a reasonable timeout value since it is not possible to
> specified an unlimited amount of time give Ambari's current task processing
> infrastructure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18563) Ambari startup script doesn't work on SUSE and potentially other OS's.
[ https://issues.apache.org/jira/browse/AMBARI-18563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562903#comment-15562903 ] Hudson commented on AMBARI-18563: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #130 (See [https://builds.apache.org/job/Ambari-branch-2.5/130/]) AMBARI-18563. Ambari startup script doesn't work on SUSE and potentially (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a0693e001020aa85c87c3a6803e775bace7f39d7]) * (edit) ambari-server/sbin/ambari-server * (edit) ambari-server/conf/unix/install-helper.sh > Ambari startup script doesn't work on SUSE and potentially other OS's. > -- > > Key: AMBARI-18563 > URL: https://issues.apache.org/jira/browse/AMBARI-18563 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.2 > > Attachments: AMBARI-18563.patch > > > Since installing the new 2.4.0.1 on SLES 11 the ambari startup script doesn't > work on server boot or reboot. It seems to be the SED line called in the > ambari startup script that doesn't account for a directory structure of > /etc/init.d/rc3.d to populate $ROOT. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18302) Desired state of client component should not be changed in case configuration changes are applied through a "Restart"
[ https://issues.apache.org/jira/browse/AMBARI-18302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562898#comment-15562898 ] Hudson commented on AMBARI-18302: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #130 (See [https://builds.apache.org/job/Ambari-branch-2.5/130/]) AMBARI-18302.Desired state of client component should not be changed in (stoader: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=551958219f170e31f951aaf8fffbeecf37ed0b18]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelper.java > Desired state of client component should not be changed in case configuration > changes are applied through a "Restart" > - > > Key: AMBARI-18302 > URL: https://issues.apache.org/jira/browse/AMBARI-18302 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Laszlo Puskas >Assignee: Laszlo Puskas > Fix For: trunk > > Attachments: AMBARI-18302.trunk.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > Configuration changes are propagated to host components by issuing a restart > of the affected components. > In case of master components this action will start the affected components > (regardless it is in INSTALLED or STARTED state) and the desired state will > be set to STARTED. > In Ambari client components are always expected to be in INSTALLED state. > However upon configuration changes, the desired state of these components are > also set to STARTED. This may be misleading for ambari API users that > determine component states by checking the desired state and actual state. > (The actual state in case of client components will always be INSTALLED) > This issue addresses this problem by not updating the desired state when > client components are restarted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18561) Capacity Scheduler View: Calculating absolute capacity for node labels and showing in sunburst chart
[
https://issues.apache.org/jira/browse/AMBARI-18561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562893#comment-15562893
]
Hadoop QA commented on AMBARI-18561:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12832472/AMBARI-18561.1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
contrib/views/capacity-scheduler.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8838//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8838//console
This message is automatically generated.
> Capacity Scheduler View: Calculating absolute capacity for node labels and
> showing in sunburst chart
>
>
> Key: AMBARI-18561
> URL: https://issues.apache.org/jira/browse/AMBARI-18561
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Akhil PB
>Assignee: Akhil PB
> Fix For: 2.5.0
>
> Attachments: AMBARI-18561.1.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18553) Provision actions to happen based only on specified dependencies
[
https://issues.apache.org/jira/browse/AMBARI-18553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562831#comment-15562831
]
Hadoop QA commented on AMBARI-18553:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12832478/AMBARI-18553.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 10 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8837//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8837//console
This message is automatically generated.
> Provision actions to happen based only on specified dependencies
>
>
> Key: AMBARI-18553
> URL: https://issues.apache.org/jira/browse/AMBARI-18553
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
> Fix For: 2.5.0
>
> Attachments: AMBARI-18553.patch
>
>
> Today, the START commands stored in role_command_orders table are bound to
> multiple stages created based on dependencies between components - a
> component in the second stage can only begin its START after the entire first
> stage is done as opposed to just its dependencies in the first stage. This
> eventually increases the overall blueprint deployment time.
> This Jira tracks STARTing components just based on dependency order as
> specified by the role_command_order as opposed to the current stage based
> model.
> The goal is to be able to configure a direct dependency based execution model
> of commands, for now only for Blueprint based deployment commands.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18560) Add more logging to track what condition resulted in skipping agent commands
[ https://issues.apache.org/jira/browse/AMBARI-18560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562660#comment-15562660 ] Hudson commented on AMBARI-18560: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5779 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5779/]) AMBARI-18560. Add more logging to track what condition resulted in (stoader: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2d1d5f9b00e39a137c5aea8341436f408975cf82]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/ServiceComponentHostRequest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostComponentResourceProvider.java > Add more logging to track what condition resulted in skipping agent commands > > > Key: AMBARI-18560 > URL: https://issues.apache.org/jira/browse/AMBARI-18560 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Sebastian Toader >Assignee: Sebastian Toader > Fix For: 2.5.0, 2.4.2 > > Attachments: AMBARI-18560.v1.patch > > > Component START/STOP requests received through REST calls may not generate > command to be executed by the agents. Currently it's hard track from the INFO > level logs if commands were not sent to agents due to legitimate conditions > what was the condition that resulted in skipping the creation of commands for > agents. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18562) Cannot update repository on the UI
[ https://issues.apache.org/jira/browse/AMBARI-18562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562633#comment-15562633 ] Andrii Tkach commented on AMBARI-18562: --- committed to trunk and branch-2.5 > Cannot update repository on the UI > -- > > Key: AMBARI-18562 > URL: https://issues.apache.org/jira/browse/AMBARI-18562 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.5.0 > > Attachments: AMBARI-18562.patch, save_repo_1.png, save_repo_2.png > > > The problem described below occurs on trunk builds. It does not occur on > branch-2.4 and branch-2.5 builds. > 1. Install a simple cluster (HDFS+YARN+ZK is enough) > 2. On the UI, go 'Admin' --> 'Stacks and versions' --> Select the 'Versions' > tab --> Click on the "show details" link --> click on the editor icon > 3. Change one of the repo url's to a different but valid one > 4. Press save > 5. Nothing happens. If you uncheck the "skip validation" checkbox, then the > repo is sometimes saved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18554) Improve package handling in Microsoft R Server Mpack
[ https://issues.apache.org/jira/browse/AMBARI-18554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562654#comment-15562654 ] Sandor Magyari commented on AMBARI-18554: - Committed to trunk, branch-2.4, branch-2.5. > Improve package handling in Microsoft R Server Mpack > > > Key: AMBARI-18554 > URL: https://issues.apache.org/jira/browse/AMBARI-18554 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári > Fix For: 2.5.0, 2.4.2 > > Attachments: AMBARI-18554-improved-package-handling-trunk-v1.patch > > > 1. use self.install_packages() > 2. declare package list in metainfo.xml instead of the install script -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18554) Improve package handling in Microsoft R Server Mpack
[ https://issues.apache.org/jira/browse/AMBARI-18554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-18554: Resolution: Fixed Status: Resolved (was: Patch Available) > Improve package handling in Microsoft R Server Mpack > > > Key: AMBARI-18554 > URL: https://issues.apache.org/jira/browse/AMBARI-18554 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári > Fix For: 2.5.0, 2.4.2 > > Attachments: AMBARI-18554-improved-package-handling-trunk-v1.patch > > > 1. use self.install_packages() > 2. declare package list in metainfo.xml instead of the install script -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18564) Ambari should be able to create arbitrary Kerberos identities for itself as declared in the Kerberos Descriptor
[
https://issues.apache.org/jira/browse/AMBARI-18564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562641#comment-15562641
]
Robert Levas commented on AMBARI-18564:
---
FYI: [~ssha...@hortonworks.com]
> Ambari should be able to create arbitrary Kerberos identities for itself as
> declared in the Kerberos Descriptor
> ---
>
> Key: AMBARI-18564
> URL: https://issues.apache.org/jira/browse/AMBARI-18564
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: kerberos, kerberos_descriptor
> Fix For: 2.5.0
>
>
> Ambari should be able to create arbitrary Kerberos identities for itself as
> declared in the Kerberos Descriptor.
> Currently, Ambari is hard-coded to create identities for itself and SPNEGO,
> but that may not be good enough for all scenarios. Therefore, there needs to
> be an {{AMBARI}} service block in the Kerberos descriptor to allow for
> arbitrary identities to be defined for the Ambari server - similar to how any
> other service is defined in the Kerberos descriptor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18560) Add more logging to track what condition resulted in skipping agent commands
[ https://issues.apache.org/jira/browse/AMBARI-18560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562645#comment-15562645 ] Hudson commented on AMBARI-18560: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #129 (See [https://builds.apache.org/job/Ambari-branch-2.5/129/]) AMBARI-18560. Add more logging to track what condition resulted in (stoader: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9d6d6785227dfc8baf758e842413a12ef626a3e8]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostComponentResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/ServiceComponentHostRequest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java > Add more logging to track what condition resulted in skipping agent commands > > > Key: AMBARI-18560 > URL: https://issues.apache.org/jira/browse/AMBARI-18560 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Sebastian Toader >Assignee: Sebastian Toader > Fix For: 2.5.0, 2.4.2 > > Attachments: AMBARI-18560.v1.patch > > > Component START/STOP requests received through REST calls may not generate > command to be executed by the agents. Currently it's hard track from the INFO > level logs if commands were not sent to agents due to legitimate conditions > what was the condition that resulted in skipping the creation of commands for > agents. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18562) Cannot update repository on the UI
[ https://issues.apache.org/jira/browse/AMBARI-18562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-18562: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Cannot update repository on the UI > -- > > Key: AMBARI-18562 > URL: https://issues.apache.org/jira/browse/AMBARI-18562 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.5.0 > > Attachments: AMBARI-18562.patch, save_repo_1.png, save_repo_2.png > > > The problem described below occurs on trunk builds. It does not occur on > branch-2.4 and branch-2.5 builds. > 1. Install a simple cluster (HDFS+YARN+ZK is enough) > 2. On the UI, go 'Admin' --> 'Stacks and versions' --> Select the 'Versions' > tab --> Click on the "show details" link --> click on the editor icon > 3. Change one of the repo url's to a different but valid one > 4. Press save > 5. Nothing happens. If you uncheck the "skip validation" checkbox, then the > repo is sometimes saved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18538) Microsoft R Server management pack should support for Redhat 7
[ https://issues.apache.org/jira/browse/AMBARI-18538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-18538: Resolution: Fixed Status: Resolved (was: Patch Available) > Microsoft R Server management pack should support for Redhat 7 > -- > > Key: AMBARI-18538 > URL: https://issues.apache.org/jira/browse/AMBARI-18538 > Project: Ambari > Issue Type: Test > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári > Fix For: 2.5.0, 2.4.2 > > Attachments: AMBARI-18538-centos-7-trunk-v1.patch > > > Add Redhat 7 support to repo.xml, test the mpack on Redhat 7. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18562) Cannot update repository on the UI
[
https://issues.apache.org/jira/browse/AMBARI-18562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562566#comment-15562566
]
Hadoop QA commented on AMBARI-18562:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12832479/AMBARI-18562.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8836//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8836//console
This message is automatically generated.
> Cannot update repository on the UI
> --
>
> Key: AMBARI-18562
> URL: https://issues.apache.org/jira/browse/AMBARI-18562
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.5.0
>
> Attachments: AMBARI-18562.patch, save_repo_1.png, save_repo_2.png
>
>
> The problem described below occurs on trunk builds. It does not occur on
> branch-2.4 and branch-2.5 builds.
> 1. Install a simple cluster (HDFS+YARN+ZK is enough)
> 2. On the UI, go 'Admin' --> 'Stacks and versions' --> Select the 'Versions'
> tab --> Click on the "show details" link --> click on the editor icon
> 3. Change one of the repo url's to a different but valid one
> 4. Press save
> 5. Nothing happens. If you uncheck the "skip validation" checkbox, then the
> repo is sometimes saved.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18545) Kerberos server actions should not timeout in minutes as specified in configuration
[
https://issues.apache.org/jira/browse/AMBARI-18545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-18545:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
{noformat}
commit 0a61db5666f3ee8b82cdab0d50a1c8450b177ae7
Author: Robert Levas
Date: Mon Oct 10 11:16:01 2016 -0400
{noformat}
Committed to branch-2.5
{noformat}
commit 367c2c95b260fc41fc6708549efe9cbcb0b3bd95
Author: Robert Levas
Date: Mon Oct 10 11:17:07 2016 -0400
{noformat}
> Kerberos server actions should not timeout in minutes as specified in
> configuration
> ---
>
> Key: AMBARI-18545
> URL: https://issues.apache.org/jira/browse/AMBARI-18545
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: kerberos
> Fix For: 2.5.0
>
> Attachments: AMBARI-18545_branch-2.4_01.patch,
> AMBARI-18545_branch-2.4_02.patch, AMBARI-18545_branch-2.5_01.patch,
> AMBARI-18545_branch-2.5_02.patch, AMBARI-18545_trunk_01.patch,
> AMBARI-18545_trunk_02.patch
>
>
> Kerberos related server-side actions should not time out in minutes as
> specified in configuration. Some Kerberos-related task can potentially take
> a much longer time based on number of hosts and components installed in the
> cluster.
> The {{Create Principals}} and {{Create Keytab Files}} stages need to be set
> to a rather large timeout value such that
> {noformat}
> if server.task.timeout < X
> timeout = X;
> else
> timeout = server.task.timeout
> Where X is set to something like 10 hours.
> {noformat}
> 10 hours seems to be a reasonable timeout value since it is not possible to
> specified an unlimited amount of time give Ambari's current task processing
> infrastructure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18563) Ambari startup script doesn't work on SUSE and potentially other OS's.
[ https://issues.apache.org/jira/browse/AMBARI-18563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18563: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.4 and branch-2.5 > Ambari startup script doesn't work on SUSE and potentially other OS's. > -- > > Key: AMBARI-18563 > URL: https://issues.apache.org/jira/browse/AMBARI-18563 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.2 > > Attachments: AMBARI-18563.patch > > > Since installing the new 2.4.0.1 on SLES 11 the ambari startup script doesn't > work on server boot or reboot. It seems to be the SED line called in the > ambari startup script that doesn't account for a directory structure of > /etc/init.d/rc3.d to populate $ROOT. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18563) Ambari startup script doesn't work on SUSE and potentially other OS's.
[
https://issues.apache.org/jira/browse/AMBARI-18563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562481#comment-15562481
]
Hadoop QA commented on AMBARI-18563:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12832483/AMBARI-18563.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8835//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8835//console
This message is automatically generated.
> Ambari startup script doesn't work on SUSE and potentially other OS's.
> --
>
> Key: AMBARI-18563
> URL: https://issues.apache.org/jira/browse/AMBARI-18563
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.2
>
> Attachments: AMBARI-18563.patch
>
>
> Since installing the new 2.4.0.1 on SLES 11 the ambari startup script doesn't
> work on server boot or reboot. It seems to be the SED line called in the
> ambari startup script that doesn't account for a directory structure of
> /etc/init.d/rc3.d to populate $ROOT.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18564) Ambari should be able to create arbitrary Kerberos identities for itself as declared in the Kerberos Descriptor
Robert Levas created AMBARI-18564:
-
Summary: Ambari should be able to create arbitrary Kerberos
identities for itself as declared in the Kerberos Descriptor
Key: AMBARI-18564
URL: https://issues.apache.org/jira/browse/AMBARI-18564
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.0
Reporter: Robert Levas
Assignee: Robert Levas
Priority: Critical
Fix For: 2.5.0
Ambari should be able to create arbitrary Kerberos identities for itself as
declared in the Kerberos Descriptor.
Currently, Ambari is hard-coded to create identities for itself and SPNEGO, but
that may not be good enough for all scenarios. Therefore, there needs to be an
{{AMBARI}} service block in the Kerberos descriptor to allow for arbitrary
identities to be defined for the Ambari server - similar to how any other
service is defined in the Kerberos descriptor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18563) Ambari startup script doesn't work on SUSE and potentially other OS's.
[ https://issues.apache.org/jira/browse/AMBARI-18563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18563: - Status: Patch Available (was: Open) > Ambari startup script doesn't work on SUSE and potentially other OS's. > -- > > Key: AMBARI-18563 > URL: https://issues.apache.org/jira/browse/AMBARI-18563 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.2 > > Attachments: AMBARI-18563.patch > > > Since installing the new 2.4.0.1 on SLES 11 the ambari startup script doesn't > work on server boot or reboot. It seems to be the SED line called in the > ambari startup script that doesn't account for a directory structure of > /etc/init.d/rc3.d to populate $ROOT. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18563) Ambari startup script doesn't work on SUSE and potentially other OS's.
Andrew Onischuk created AMBARI-18563: Summary: Ambari startup script doesn't work on SUSE and potentially other OS's. Key: AMBARI-18563 URL: https://issues.apache.org/jira/browse/AMBARI-18563 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.4.2 Attachments: AMBARI-18563.patch Since installing the new 2.4.0.1 on SLES 11 the ambari startup script doesn't work on server boot or reboot. It seems to be the SED line called in the ambari startup script that doesn't account for a directory structure of /etc/init.d/rc3.d to populate $ROOT. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18563) Ambari startup script doesn't work on SUSE and potentially other OS's.
[ https://issues.apache.org/jira/browse/AMBARI-18563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18563: - Attachment: AMBARI-18563.patch > Ambari startup script doesn't work on SUSE and potentially other OS's. > -- > > Key: AMBARI-18563 > URL: https://issues.apache.org/jira/browse/AMBARI-18563 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.2 > > Attachments: AMBARI-18563.patch > > > Since installing the new 2.4.0.1 on SLES 11 the ambari startup script doesn't > work on server boot or reboot. It seems to be the SED line called in the > ambari startup script that doesn't account for a directory structure of > /etc/init.d/rc3.d to populate $ROOT. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18562) Cannot update repository on the UI
[
https://issues.apache.org/jira/browse/AMBARI-18562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562411#comment-15562411
]
Hadoop QA commented on AMBARI-18562:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12832479/AMBARI-18562.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8834//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8834//console
This message is automatically generated.
> Cannot update repository on the UI
> --
>
> Key: AMBARI-18562
> URL: https://issues.apache.org/jira/browse/AMBARI-18562
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.5.0
>
> Attachments: AMBARI-18562.patch, save_repo_1.png, save_repo_2.png
>
>
> The problem described below occurs on trunk builds. It does not occur on
> branch-2.4 and branch-2.5 builds.
> 1. Install a simple cluster (HDFS+YARN+ZK is enough)
> 2. On the UI, go 'Admin' --> 'Stacks and versions' --> Select the 'Versions'
> tab --> Click on the "show details" link --> click on the editor icon
> 3. Change one of the repo url's to a different but valid one
> 4. Press save
> 5. Nothing happens. If you uncheck the "skip validation" checkbox, then the
> repo is sometimes saved.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18562) Cannot update repository on the UI
[ https://issues.apache.org/jira/browse/AMBARI-18562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562360#comment-15562360 ] Aleksandr Kovalenko commented on AMBARI-18562: -- +1 for the patch > Cannot update repository on the UI > -- > > Key: AMBARI-18562 > URL: https://issues.apache.org/jira/browse/AMBARI-18562 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.5.0 > > Attachments: AMBARI-18562.patch, save_repo_1.png, save_repo_2.png > > > The problem described below occurs on trunk builds. It does not occur on > branch-2.4 and branch-2.5 builds. > 1. Install a simple cluster (HDFS+YARN+ZK is enough) > 2. On the UI, go 'Admin' --> 'Stacks and versions' --> Select the 'Versions' > tab --> Click on the "show details" link --> click on the editor icon > 3. Change one of the repo url's to a different but valid one > 4. Press save > 5. Nothing happens. If you uncheck the "skip validation" checkbox, then the > repo is sometimes saved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18562) Cannot update repository on the UI
[ https://issues.apache.org/jira/browse/AMBARI-18562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-18562: -- Status: Patch Available (was: Open) > Cannot update repository on the UI > -- > > Key: AMBARI-18562 > URL: https://issues.apache.org/jira/browse/AMBARI-18562 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.5.0 > > Attachments: AMBARI-18562.patch, save_repo_1.png, save_repo_2.png > > > The problem described below occurs on trunk builds. It does not occur on > branch-2.4 and branch-2.5 builds. > 1. Install a simple cluster (HDFS+YARN+ZK is enough) > 2. On the UI, go 'Admin' --> 'Stacks and versions' --> Select the 'Versions' > tab --> Click on the "show details" link --> click on the editor icon > 3. Change one of the repo url's to a different but valid one > 4. Press save > 5. Nothing happens. If you uncheck the "skip validation" checkbox, then the > repo is sometimes saved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18562) Cannot update repository on the UI
[ https://issues.apache.org/jira/browse/AMBARI-18562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562354#comment-15562354 ] Andrii Tkach commented on AMBARI-18562: --- 30374 tests complete (29 seconds) 151 tests pending > Cannot update repository on the UI > -- > > Key: AMBARI-18562 > URL: https://issues.apache.org/jira/browse/AMBARI-18562 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.5.0 > > Attachments: AMBARI-18562.patch, save_repo_1.png, save_repo_2.png > > > The problem described below occurs on trunk builds. It does not occur on > branch-2.4 and branch-2.5 builds. > 1. Install a simple cluster (HDFS+YARN+ZK is enough) > 2. On the UI, go 'Admin' --> 'Stacks and versions' --> Select the 'Versions' > tab --> Click on the "show details" link --> click on the editor icon > 3. Change one of the repo url's to a different but valid one > 4. Press save > 5. Nothing happens. If you uncheck the "skip validation" checkbox, then the > repo is sometimes saved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18562) Cannot update repository on the UI
[ https://issues.apache.org/jira/browse/AMBARI-18562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-18562: -- Attachment: AMBARI-18562.patch > Cannot update repository on the UI > -- > > Key: AMBARI-18562 > URL: https://issues.apache.org/jira/browse/AMBARI-18562 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.5.0 > > Attachments: AMBARI-18562.patch, save_repo_1.png, save_repo_2.png > > > The problem described below occurs on trunk builds. It does not occur on > branch-2.4 and branch-2.5 builds. > 1. Install a simple cluster (HDFS+YARN+ZK is enough) > 2. On the UI, go 'Admin' --> 'Stacks and versions' --> Select the 'Versions' > tab --> Click on the "show details" link --> click on the editor icon > 3. Change one of the repo url's to a different but valid one > 4. Press save > 5. Nothing happens. If you uncheck the "skip validation" checkbox, then the > repo is sometimes saved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18553) Provision actions to happen based only on specified dependencies
[ https://issues.apache.org/jira/browse/AMBARI-18553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-18553: Attachment: AMBARI-18553.patch > Provision actions to happen based only on specified dependencies > > > Key: AMBARI-18553 > URL: https://issues.apache.org/jira/browse/AMBARI-18553 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 2.5.0 > > Attachments: AMBARI-18553.patch > > > Today, the START commands stored in role_command_orders table are bound to > multiple stages created based on dependencies between components - a > component in the second stage can only begin its START after the entire first > stage is done as opposed to just its dependencies in the first stage. This > eventually increases the overall blueprint deployment time. > This Jira tracks STARTing components just based on dependency order as > specified by the role_command_order as opposed to the current stage based > model. > The goal is to be able to configure a direct dependency based execution model > of commands, for now only for Blueprint based deployment commands. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18553) Provision actions to happen based only on specified dependencies
[ https://issues.apache.org/jira/browse/AMBARI-18553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-18553: Attachment: (was: AMBARI-18553.patch) > Provision actions to happen based only on specified dependencies > > > Key: AMBARI-18553 > URL: https://issues.apache.org/jira/browse/AMBARI-18553 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 2.5.0 > > > Today, the START commands stored in role_command_orders table are bound to > multiple stages created based on dependencies between components - a > component in the second stage can only begin its START after the entire first > stage is done as opposed to just its dependencies in the first stage. This > eventually increases the overall blueprint deployment time. > This Jira tracks STARTing components just based on dependency order as > specified by the role_command_order as opposed to the current stage based > model. > The goal is to be able to configure a direct dependency based execution model > of commands, for now only for Blueprint based deployment commands. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18562) Cannot update repository on the UI
[ https://issues.apache.org/jira/browse/AMBARI-18562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-18562: -- Attachment: save_repo_1.png > Cannot update repository on the UI > -- > > Key: AMBARI-18562 > URL: https://issues.apache.org/jira/browse/AMBARI-18562 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.5.0 > > Attachments: save_repo_1.png, save_repo_2.png > > > The problem described below occurs on trunk builds. It does not occur on > branch-2.4 and branch-2.5 builds. > 1. Install a simple cluster (HDFS+YARN+ZK is enough) > 2. On the UI, go 'Admin' --> 'Stacks and versions' --> Select the 'Versions' > tab --> Click on the "show details" link --> click on the editor icon > 3. Change one of the repo url's to a different but valid one > 4. Press save > 5. Nothing happens. If you uncheck the "skip validation" checkbox, then the > repo is sometimes saved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18562) Cannot update repository on the UI
[ https://issues.apache.org/jira/browse/AMBARI-18562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-18562: -- Attachment: save_repo_2.png > Cannot update repository on the UI > -- > > Key: AMBARI-18562 > URL: https://issues.apache.org/jira/browse/AMBARI-18562 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.5.0 > > Attachments: save_repo_1.png, save_repo_2.png > > > The problem described below occurs on trunk builds. It does not occur on > branch-2.4 and branch-2.5 builds. > 1. Install a simple cluster (HDFS+YARN+ZK is enough) > 2. On the UI, go 'Admin' --> 'Stacks and versions' --> Select the 'Versions' > tab --> Click on the "show details" link --> click on the editor icon > 3. Change one of the repo url's to a different but valid one > 4. Press save > 5. Nothing happens. If you uncheck the "skip validation" checkbox, then the > repo is sometimes saved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18562) Cannot update repository on the UI
Andrii Tkach created AMBARI-18562: - Summary: Cannot update repository on the UI Key: AMBARI-18562 URL: https://issues.apache.org/jira/browse/AMBARI-18562 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.5.0 Attachments: save_repo_1.png, save_repo_2.png The problem described below occurs on trunk builds. It does not occur on branch-2.4 and branch-2.5 builds. 1. Install a simple cluster (HDFS+YARN+ZK is enough) 2. On the UI, go 'Admin' --> 'Stacks and versions' --> Select the 'Versions' tab --> Click on the "show details" link --> click on the editor icon 3. Change one of the repo url's to a different but valid one 4. Press save 5. Nothing happens. If you uncheck the "skip validation" checkbox, then the repo is sometimes saved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18560) Add more logging to track what condition resulted in skipping agent commands
[
https://issues.apache.org/jira/browse/AMBARI-18560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562298#comment-15562298
]
Hadoop QA commented on AMBARI-18560:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12832456/AMBARI-18560.v1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8833//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8833//console
This message is automatically generated.
> Add more logging to track what condition resulted in skipping agent commands
>
>
> Key: AMBARI-18560
> URL: https://issues.apache.org/jira/browse/AMBARI-18560
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-18560.v1.patch
>
>
> Component START/STOP requests received through REST calls may not generate
> command to be executed by the agents. Currently it's hard track from the INFO
> level logs if commands were not sent to agents due to legitimate conditions
> what was the condition that resulted in skipping the creation of commands for
> agents.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18561) Capacity Scheduler View: Calculating absolute capacity for node labels and showing in sunburst chart
[ https://issues.apache.org/jira/browse/AMBARI-18561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated AMBARI-18561: -- Status: Patch Available (was: Open) > Capacity Scheduler View: Calculating absolute capacity for node labels and > showing in sunburst chart > > > Key: AMBARI-18561 > URL: https://issues.apache.org/jira/browse/AMBARI-18561 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Akhil PB >Assignee: Akhil PB > Fix For: 2.5.0 > > Attachments: AMBARI-18561.1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18561) Capacity Scheduler View: Calculating absolute capacity for node labels and showing in sunburst chart
[ https://issues.apache.org/jira/browse/AMBARI-18561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated AMBARI-18561: -- Attachment: AMBARI-18561.1.patch > Capacity Scheduler View: Calculating absolute capacity for node labels and > showing in sunburst chart > > > Key: AMBARI-18561 > URL: https://issues.apache.org/jira/browse/AMBARI-18561 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Akhil PB >Assignee: Akhil PB > Fix For: 2.5.0 > > Attachments: AMBARI-18561.1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18546) BP format does not generate property oozie.service.JPAService.jdbc.url
[
https://issues.apache.org/jira/browse/AMBARI-18546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562166#comment-15562166
]
Hudson commented on AMBARI-18546:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5778 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5778/])
AMBARI-18546. BP format does not generate property (vbrodetskyi:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=58afcf93d8445c3b1ffacdd33c1cb12a8e8414cb])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java
> BP format does not generate property oozie.service.JPAService.jdbc.url
> --
>
> Key: AMBARI-18546
> URL: https://issues.apache.org/jira/browse/AMBARI-18546
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18546.patch
>
>
> STR:
> * Install Ambari 2.4.0.1 with HDP 2.5 and Oozie (using existing MySQL DB).
> * Notice that oozie-site has config,
> {code}
> oozie.service.JPAService.jdbc.url=jdbc:mysql://$SERVER/$oozie.db.schema.name
> {code}
> E.g.,
> jdbc:mysql://c6401.ambari.apache.org/oozie
> * Export the BP,
> api/v1/clusters/c1?format=blueprint
> It doesn't generate the "oozie.service.JPAService.jdbc.url" property, so a
> user trying to use that blueprint will run into errors.
> Further, setting the value of that property to
> "jdbc:mysql://%HOSTGROUP::host_group_1%/oozie" does not actually replace it
> with the hostname, and it should also dynamically replace the Oozie DB name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18561) Capacity Scheduler View: Calculating absolute capacity for node labels and showing in sunburst chart
Akhil PB created AMBARI-18561: - Summary: Capacity Scheduler View: Calculating absolute capacity for node labels and showing in sunburst chart Key: AMBARI-18561 URL: https://issues.apache.org/jira/browse/AMBARI-18561 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.4.0 Reporter: Akhil PB Assignee: Akhil PB Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18546) BP format does not generate property oozie.service.JPAService.jdbc.url
[
https://issues.apache.org/jira/browse/AMBARI-18546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562078#comment-15562078
]
Hudson commented on AMBARI-18546:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #128 (See
[https://builds.apache.org/job/Ambari-branch-2.5/128/])
AMBARI-18546. BP format does not generate property (vbrodetskyi:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=46a528ffbb5e806c10815b7e1555b9a811326c86])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java
> BP format does not generate property oozie.service.JPAService.jdbc.url
> --
>
> Key: AMBARI-18546
> URL: https://issues.apache.org/jira/browse/AMBARI-18546
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18546.patch
>
>
> STR:
> * Install Ambari 2.4.0.1 with HDP 2.5 and Oozie (using existing MySQL DB).
> * Notice that oozie-site has config,
> {code}
> oozie.service.JPAService.jdbc.url=jdbc:mysql://$SERVER/$oozie.db.schema.name
> {code}
> E.g.,
> jdbc:mysql://c6401.ambari.apache.org/oozie
> * Export the BP,
> api/v1/clusters/c1?format=blueprint
> It doesn't generate the "oozie.service.JPAService.jdbc.url" property, so a
> user trying to use that blueprint will run into errors.
> Further, setting the value of that property to
> "jdbc:mysql://%HOSTGROUP::host_group_1%/oozie" does not actually replace it
> with the hostname, and it should also dynamically replace the Oozie DB name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18560) Add more logging to track what condition resulted in skipping agent commands
[ https://issues.apache.org/jira/browse/AMBARI-18560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-18560: -- Status: Patch Available (was: In Progress) > Add more logging to track what condition resulted in skipping agent commands > > > Key: AMBARI-18560 > URL: https://issues.apache.org/jira/browse/AMBARI-18560 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Sebastian Toader >Assignee: Sebastian Toader > Fix For: 2.5.0, 2.4.2 > > Attachments: AMBARI-18560.v1.patch > > > Component START/STOP requests received through REST calls may not generate > command to be executed by the agents. Currently it's hard track from the INFO > level logs if commands were not sent to agents due to legitimate conditions > what was the condition that resulted in skipping the creation of commands for > agents. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18560) Add more logging to track what condition resulted in skipping agent commands
[ https://issues.apache.org/jira/browse/AMBARI-18560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-18560: -- Attachment: AMBARI-18560.v1.patch > Add more logging to track what condition resulted in skipping agent commands > > > Key: AMBARI-18560 > URL: https://issues.apache.org/jira/browse/AMBARI-18560 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Sebastian Toader >Assignee: Sebastian Toader > Fix For: 2.5.0, 2.4.2 > > Attachments: AMBARI-18560.v1.patch > > > Component START/STOP requests received through REST calls may not generate > command to be executed by the agents. Currently it's hard track from the INFO > level logs if commands were not sent to agents due to legitimate conditions > what was the condition that resulted in skipping the creation of commands for > agents. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18546) BP format does not generate property oozie.service.JPAService.jdbc.url
[
https://issues.apache.org/jira/browse/AMBARI-18546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-18546:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.5
> BP format does not generate property oozie.service.JPAService.jdbc.url
> --
>
> Key: AMBARI-18546
> URL: https://issues.apache.org/jira/browse/AMBARI-18546
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18546.patch
>
>
> STR:
> * Install Ambari 2.4.0.1 with HDP 2.5 and Oozie (using existing MySQL DB).
> * Notice that oozie-site has config,
> {code}
> oozie.service.JPAService.jdbc.url=jdbc:mysql://$SERVER/$oozie.db.schema.name
> {code}
> E.g.,
> jdbc:mysql://c6401.ambari.apache.org/oozie
> * Export the BP,
> api/v1/clusters/c1?format=blueprint
> It doesn't generate the "oozie.service.JPAService.jdbc.url" property, so a
> user trying to use that blueprint will run into errors.
> Further, setting the value of that property to
> "jdbc:mysql://%HOSTGROUP::host_group_1%/oozie" does not actually replace it
> with the hostname, and it should also dynamically replace the Oozie DB name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18560) Add more logging to track what condition resulted in skipping agent commands
Sebastian Toader created AMBARI-18560: - Summary: Add more logging to track what condition resulted in skipping agent commands Key: AMBARI-18560 URL: https://issues.apache.org/jira/browse/AMBARI-18560 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Sebastian Toader Assignee: Sebastian Toader Fix For: 2.5.0, 2.4.2 Component START/STOP requests received through REST calls may not generate command to be executed by the agents. Currently it's hard track from the INFO level logs if commands were not sent to agents due to legitimate conditions what was the condition that resulted in skipping the creation of commands for agents. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
