[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=15627862#comment-15627862 ] Hudson commented on AMBARI-18561: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #240 (See [https://builds.apache.org/job/Ambari-branch-2.5/240/]) AMBARI-18561. Capacity Scheduler View: Calculating absolute capacity for (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a05d99969fdabc022e1ec7bf544e6effc2fbdd4e]) * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/controllers/queuesconf.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/models/queue.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/controllers/advanced.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/router.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/capsched/advanced.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/components/queueMapping.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/controllers/capsched.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/components/editLabelCapacity.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/components/labelCapacityBar.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/capsched/partials/preemption.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/components/queueMapping.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/controllers/scheduler.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/components/sunburstChart.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/controllers/editqueue.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/app.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/styles/application.less > 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, AMBARI-18561.2.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18770) Service check and Ambari Alerting for RM fails against Yarn with HA and SPNEGO
[
https://issues.apache.org/jira/browse/AMBARI-18770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15627848#comment-15627848
]
Hadoop QA commented on AMBARI-18770:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836503/AMBARI-18770.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/9089//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9089//console
This message is automatically generated.
> Service check and Ambari Alerting for RM fails against Yarn with HA and
> SPNEGO
> ---
>
> Key: AMBARI-18770
> URL: https://issues.apache.org/jira/browse/AMBARI-18770
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: 2.4.0, 2.4.1, 2.4.2
> Environment: Hortonworks HDP 2.5 and HDP 2.4
>Reporter: Greg Senia
>Priority: Minor
> Fix For: 2.4.2
>
> Attachments: AMBARI-18770.patch
>
>
> If both HA and SPNEGO is configured for the cluster, the service check and
> ambari Alerting for RM fails for Yarn.
--
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 ] Pallav Kulshreshtha updated AMBARI-18561: - Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and branch-2.5 > 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, AMBARI-18561.2.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18770) Service check and Ambari Alerting for RM fails against Yarn with HA and SPNEGO
[ https://issues.apache.org/jira/browse/AMBARI-18770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15627769#comment-15627769 ] Greg Senia commented on AMBARI-18770: - Curl Manpage: -L, --location (HTTP/HTTPS) If the server reports that the requested page has moved to a different location (indicated with a Location: header and a 3XX response code), this option will make curl redo the request on the new place. If used together with -i, --include or -I, --head, headers from all requested pages will be shown. When authentication is used, curl only sends its credentials to the initial host. If a redirect takes curl to a different host, it won't be able to intercept the user+password. See also --location-trusted on how to change this. You can limit the amount of redirects to follow by using the --max-redirs option. When curl follows a redirect and the request is not a plain GET (for example POST or PUT), it will do the following request with a GET if the HTTP response was 301, 302, or 303. If the response code was any other 3xx code, curl will re-send the following request using the same unmodified method. You can tell curl to not change the non-GET request method to GET after a 30x response by using the dedicated options for that: --post301, --post302 and -post303. --location-trusted (HTTP/HTTPS) Like -L, --location, but will allow sending the name + password to all hosts that the site may redirect to. This may or may not introduce a secu- rity breach if the site redirects you to a site to which you'll send your authentication info (which is plaintext in the case of HTTP Basic authentication). > Service check and Ambari Alerting for RM fails against Yarn with HA and > SPNEGO > --- > > Key: AMBARI-18770 > URL: https://issues.apache.org/jira/browse/AMBARI-18770 > Project: Ambari > Issue Type: Bug > Components: ambari-agent, ambari-server >Affects Versions: 2.4.0, 2.4.1, 2.4.2 > Environment: Hortonworks HDP 2.5 and HDP 2.4 >Reporter: Greg Senia >Priority: Minor > Fix For: 2.4.2 > > Attachments: AMBARI-18770.patch > > > If both HA and SPNEGO is configured for the cluster, the service check and > ambari Alerting for RM fails for Yarn. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18770) Service check and Ambari Alerting for RM fails against Yarn with HA and SPNEGO
[ https://issues.apache.org/jira/browse/AMBARI-18770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Senia updated AMBARI-18770: Fix Version/s: 2.4.2 Status: Patch Available (was: Open) > Service check and Ambari Alerting for RM fails against Yarn with HA and > SPNEGO > --- > > Key: AMBARI-18770 > URL: https://issues.apache.org/jira/browse/AMBARI-18770 > Project: Ambari > Issue Type: Bug > Components: ambari-agent, ambari-server >Affects Versions: 2.4.0, 2.4.1, 2.4.2 > Environment: Hortonworks HDP 2.5 and HDP 2.4 >Reporter: Greg Senia >Priority: Minor > Fix For: 2.4.2 > > Attachments: AMBARI-18770.patch > > > If both HA and SPNEGO is configured for the cluster, the service check and > ambari Alerting for RM fails for Yarn. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18770) Service check and Ambari Alerting for RM fails against Yarn with HA and SPNEGO
[ https://issues.apache.org/jira/browse/AMBARI-18770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Senia updated AMBARI-18770: Affects Version/s: 2.4.2 2.4.1 > Service check and Ambari Alerting for RM fails against Yarn with HA and > SPNEGO > --- > > Key: AMBARI-18770 > URL: https://issues.apache.org/jira/browse/AMBARI-18770 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.4.0, 2.4.1, 2.4.2 > Environment: Hortonworks HDP 2.5 >Reporter: Greg Senia >Priority: Minor > > If both HA and SPNEGO is configured for the cluster, the service check and > ambari Alerting for RM fails for Yarn. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18770) Service check and Ambari Alerting for RM fails against Yarn with HA and SPNEGO
[ https://issues.apache.org/jira/browse/AMBARI-18770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Senia updated AMBARI-18770: Description: If both HA and SPNEGO is configured for the cluster, the service check and ambari Alerting for RM fails for Yarn. was: If both HA and SPNEGO is configured for the cluster, the service check fails on Yarn. The problem is because we are using curl to fetch the http pages, we also enters –L to follow the location information in the header. But –L don’t forward authentication information to redirected hosts. Changing –L to --location-trusted solves the problem. --- /tmp/service_check.py 2016-09-28 13:08:06.468192028 +0200 +++ /var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py 2016-09-28 13:17:36.810100884 +0200 @@ -129,7 +129,7 @@ for rm_webapp_address in params.rm_webapp_addresses_list: info_app_url = params.scheme + "://" + rm_webapp_address + "/ws/v1/cluster/apps/" + application_name - get_app_info_cmd = "curl --negotiate -u : -ksL --connect-timeout " + CURL_CONNECTION_TIMEOUT + " " + info_app_url + get_app_info_cmd = "curl --negotiate -u : -ks --location-trusted --connect-timeout " + CURL_CONNECTION_TIMEOUT + " " + info_app_url return_code, stdout, _ = get_user_call_output(get_app_info_cmd, user=params.smokeuser, > Service check and Ambari Alerting for RM fails against Yarn with HA and > SPNEGO > --- > > Key: AMBARI-18770 > URL: https://issues.apache.org/jira/browse/AMBARI-18770 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.4.0 > Environment: Hortonworks HDP 2.5 >Reporter: Greg Senia >Priority: Minor > > If both HA and SPNEGO is configured for the cluster, the service check and > ambari Alerting for RM fails for Yarn. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18770) Service check and Ambari Alerting for RM fails against Yarn with HA and SPNEGO
Greg Senia created AMBARI-18770: --- Summary: Service check and Ambari Alerting for RM fails against Yarn with HA and SPNEGO Key: AMBARI-18770 URL: https://issues.apache.org/jira/browse/AMBARI-18770 Project: Ambari Issue Type: Bug Components: ambari-agent Affects Versions: 2.4.0 Environment: Hortonworks HDP 2.5 Reporter: Greg Senia Priority: Minor If both HA and SPNEGO is configured for the cluster, the service check fails on Yarn. The problem is because we are using curl to fetch the http pages, we also enters –L to follow the location information in the header. But –L don’t forward authentication information to redirected hosts. Changing –L to --location-trusted solves the problem. --- /tmp/service_check.py 2016-09-28 13:08:06.468192028 +0200 +++ /var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py 2016-09-28 13:17:36.810100884 +0200 @@ -129,7 +129,7 @@ for rm_webapp_address in params.rm_webapp_addresses_list: info_app_url = params.scheme + "://" + rm_webapp_address + "/ws/v1/cluster/apps/" + application_name - get_app_info_cmd = "curl --negotiate -u : -ksL --connect-timeout " + CURL_CONNECTION_TIMEOUT + " " + info_app_url + get_app_info_cmd = "curl --negotiate -u : -ks --location-trusted --connect-timeout " + CURL_CONNECTION_TIMEOUT + " " + info_app_url return_code, stdout, _ = get_user_call_output(get_app_info_cmd, user=params.smokeuser, -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18769) Proxy user fixes for Hive view 2.0
[ https://issues.apache.org/jira/browse/AMBARI-18769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Rajeev updated AMBARI-18769: --- Summary: Proxy user fixes for Hive view 2.0 (was: Proxy user fixes for Ambari Hive view 2.0) > Proxy user fixes for Hive view 2.0 > -- > > Key: AMBARI-18769 > URL: https://issues.apache.org/jira/browse/AMBARI-18769 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.4.1 > > Attachments: AMBARI-18769.trunk.patch > > > Hive view must allow user proxying -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18769) Proxy user fixes for Ambari Hive view 2.0
[ https://issues.apache.org/jira/browse/AMBARI-18769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Rajeev updated AMBARI-18769: --- Summary: Proxy user fixes for Ambari Hive view 2.0 (was: Proxy user fixes for Ambari) > Proxy user fixes for Ambari Hive view 2.0 > - > > Key: AMBARI-18769 > URL: https://issues.apache.org/jira/browse/AMBARI-18769 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.4.1 > > Attachments: AMBARI-18769.trunk.patch > > > Hive view must allow user proxying -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18769) Proxy user fixes for Ambari
[ https://issues.apache.org/jira/browse/AMBARI-18769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Rajeev updated AMBARI-18769: --- Status: Patch Available (was: Open) > Proxy user fixes for Ambari > --- > > Key: AMBARI-18769 > URL: https://issues.apache.org/jira/browse/AMBARI-18769 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.4.1 > > Attachments: AMBARI-18769.trunk.patch > > > Hive view must allow user proxying -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18769) Proxy user fixes for Ambari
[ https://issues.apache.org/jira/browse/AMBARI-18769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Rajeev updated AMBARI-18769: --- Attachment: AMBARI-18769.trunk.patch > Proxy user fixes for Ambari > --- > > Key: AMBARI-18769 > URL: https://issues.apache.org/jira/browse/AMBARI-18769 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.4.1 > > Attachments: AMBARI-18769.trunk.patch > > > Hive view must allow user proxying -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18769) Proxy user fixes for Ambari
[ https://issues.apache.org/jira/browse/AMBARI-18769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Rajeev updated AMBARI-18769: --- Fix Version/s: (was: 2.4.0) 2.4.1 > Proxy user fixes for Ambari > --- > > Key: AMBARI-18769 > URL: https://issues.apache.org/jira/browse/AMBARI-18769 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.4.1 > > > Hive view must allow user proxying -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18769) Proxy user fixes for Ambari
Ashwin Rajeev created AMBARI-18769: -- Summary: Proxy user fixes for Ambari Key: AMBARI-18769 URL: https://issues.apache.org/jira/browse/AMBARI-18769 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.4.0 Reporter: Ashwin Rajeev Assignee: Ashwin Rajeev Fix For: 2.4.0 Hive view must allow user proxying -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18768) Session invalidation for hive view
[ https://issues.apache.org/jira/browse/AMBARI-18768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Rajeev updated AMBARI-18768: --- Attachment: AMBARI-18786.trunk.patch > Session invalidation for hive view > -- > > Key: AMBARI-18768 > URL: https://issues.apache.org/jira/browse/AMBARI-18768 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.4.0 > > Attachments: AMBARI-18786.trunk.patch > > > In some cases , HS2 may restart/be restarted when the hive view is in use, > This usually manifests as a session expired/broken pipe exception > Change the error shown to a connection error and indicate that user must > retry the query -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18768) Session invalidation for hive view
[ https://issues.apache.org/jira/browse/AMBARI-18768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Rajeev updated AMBARI-18768: --- Status: Patch Available (was: Open) > Session invalidation for hive view > -- > > Key: AMBARI-18768 > URL: https://issues.apache.org/jira/browse/AMBARI-18768 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.4.0 > > > In some cases , HS2 may restart/be restarted when the hive view is in use, > This usually manifests as a session expired/broken pipe exception > Change the error shown to a connection error and indicate that user must > retry the query -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18768) Session invalidation for hive view
[ https://issues.apache.org/jira/browse/AMBARI-18768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Rajeev updated AMBARI-18768: --- Description: In some cases , HS2 may restart/be restarted when the hive view is in use, This usually manifests as a session expired/broken pipe exception Change the error shown to a connection error and indicate that user must retry the query > Session invalidation for hive view > -- > > Key: AMBARI-18768 > URL: https://issues.apache.org/jira/browse/AMBARI-18768 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.4.0 > > > In some cases , HS2 may restart/be restarted when the hive view is in use, > This usually manifests as a session expired/broken pipe exception > Change the error shown to a connection error and indicate that user must > retry the query -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18768) Session invalidation for hive view
Ashwin Rajeev created AMBARI-18768: -- Summary: Session invalidation for hive view Key: AMBARI-18768 URL: https://issues.apache.org/jira/browse/AMBARI-18768 Project: Ambari Issue Type: Bug Affects Versions: 2.4.0 Reporter: Ashwin Rajeev Assignee: Ashwin Rajeev Fix For: 2.4.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18474) Kerberos wizard loses request id on server restart
[ https://issues.apache.org/jira/browse/AMBARI-18474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15627603#comment-15627603 ] Jaimin Jetly commented on AMBARI-18474: --- Patch backported to branch-2.4 > Kerberos wizard loses request id on server restart > -- > > Key: AMBARI-18474 > URL: https://issues.apache.org/jira/browse/AMBARI-18474 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18474.patch, Screen Shot 2016-09-20 at 6.37.29 > PM.png > > > *Problem* > - Kerberos wizard create principals action timed out > - To increase task timeout we had to restart the server > - On restart wizard comes up wit ha spinner, no error no indication of what > is happening > - had to post a last request id through js console for work to resume. > - Quitting a wizard means users has to start from the very beginning, on a > 1300 node cluster that is not feasible. > *Expected behavior*: > - If the last request id was not perisisted by UI, on restart the last > request id needs to be retrieved and check for context info to resume from > where the user left the wizard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18474) Kerberos wizard loses request id on server restart
[ https://issues.apache.org/jira/browse/AMBARI-18474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-18474: -- Fix Version/s: (was: 2.5.0) 2.4.2 > Kerberos wizard loses request id on server restart > -- > > Key: AMBARI-18474 > URL: https://issues.apache.org/jira/browse/AMBARI-18474 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18474.patch, Screen Shot 2016-09-20 at 6.37.29 > PM.png > > > *Problem* > - Kerberos wizard create principals action timed out > - To increase task timeout we had to restart the server > - On restart wizard comes up wit ha spinner, no error no indication of what > is happening > - had to post a last request id through js console for work to resume. > - Quitting a wizard means users has to start from the very beginning, on a > 1300 node cluster that is not feasible. > *Expected behavior*: > - If the last request id was not perisisted by UI, on restart the last > request id needs to be retrieved and check for context info to resume from > where the user left the wizard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18744) Ambari-server: REST API changes to GET and PUT credential store information
[
https://issues.apache.org/jira/browse/AMBARI-18744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-18744:
---
Attachment: rb53283.patch
> Ambari-server: REST API changes to GET and PUT credential store information
> ---
>
> Key: AMBARI-18744
> URL: https://issues.apache.org/jira/browse/AMBARI-18744
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53283.patch
>
>
> *Support stack definition for credential store information*
> To support backward compatibility, services must be tagged to indicate
> whether they support credential store backed passwords. This requires changes
> in the stack definition object model.
> {code}
>
> SERVICE_NAME
> :
>
> true
> false
>
> :
> :
>
> {code}
> *REST API support is required to GET _credential_store_supported_ and
> _credential_store_enabled_ values for a service:*
> {quote}api/v1/clusters//services?fields=ServiceInfo/service_name,ServiceInfo/credential_store_supported,ServiceInfo/credential_store_enabled{quote}
> *REST API support is required to PUT _credential_store_enabled_ value for a
> service:*
> {quote}api/v1/clusters//services?ServiceInfo/service_name.in(RANGER,HIVE)
> {
> ServiceInfo: {
> credential_store_enabled: “true”
> }
> }{quote}
> {quote}api/v1/clusters/testcluster/services/RANGER -X PUT -d '{"ServiceInfo"
> : {"credential_store_enabled":"true"}}'
> {quote}
> {quote}api/v1/clusters/testcluster/services?ServiceInfo/service_name=ZOOKEEPER
> -X PUT -d '{"ServiceInfo" : {"credential_store_enabled":"false"}}'{quote}
> *REST API to get Stack definition*
> {quote}
> curl -u admin:admin -H "X-Requested-By: ambari" -X GET
> http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services
> {quote}
> {quote}
> {
> "href" : "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/;,
> {
> "href" :
> "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/YARN;,
> "StackServices" : {
> "service_name" : "YARN",
> "stack_name" : "HDP",
> "stack_version" : "2.0",
> "credential_store_supported" : "false",
> "credential_store_enabled" : "false"
> }
> },
> {
> "href" :
> "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/ZOOKEEPER;,
> "StackServices" : {
> "service_name" : "ZOOKEEPER",
> "stack_name" : "HDP",
> "stack_version" : "2.0",
> "credential_store_supported" : "false",
> "credential_store_enabled" : "false"
> }
> }
> ]
> }
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18744) Ambari-server: REST API changes to GET and PUT credential store information
[
https://issues.apache.org/jira/browse/AMBARI-18744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-18744:
---
Status: Open (was: Patch Available)
> Ambari-server: REST API changes to GET and PUT credential store information
> ---
>
> Key: AMBARI-18744
> URL: https://issues.apache.org/jira/browse/AMBARI-18744
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53283.patch
>
>
> *Support stack definition for credential store information*
> To support backward compatibility, services must be tagged to indicate
> whether they support credential store backed passwords. This requires changes
> in the stack definition object model.
> {code}
>
> SERVICE_NAME
> :
>
> true
> false
>
> :
> :
>
> {code}
> *REST API support is required to GET _credential_store_supported_ and
> _credential_store_enabled_ values for a service:*
> {quote}api/v1/clusters//services?fields=ServiceInfo/service_name,ServiceInfo/credential_store_supported,ServiceInfo/credential_store_enabled{quote}
> *REST API support is required to PUT _credential_store_enabled_ value for a
> service:*
> {quote}api/v1/clusters//services?ServiceInfo/service_name.in(RANGER,HIVE)
> {
> ServiceInfo: {
> credential_store_enabled: “true”
> }
> }{quote}
> {quote}api/v1/clusters/testcluster/services/RANGER -X PUT -d '{"ServiceInfo"
> : {"credential_store_enabled":"true"}}'
> {quote}
> {quote}api/v1/clusters/testcluster/services?ServiceInfo/service_name=ZOOKEEPER
> -X PUT -d '{"ServiceInfo" : {"credential_store_enabled":"false"}}'{quote}
> *REST API to get Stack definition*
> {quote}
> curl -u admin:admin -H "X-Requested-By: ambari" -X GET
> http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services
> {quote}
> {quote}
> {
> "href" : "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/;,
> {
> "href" :
> "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/YARN;,
> "StackServices" : {
> "service_name" : "YARN",
> "stack_name" : "HDP",
> "stack_version" : "2.0",
> "credential_store_supported" : "false",
> "credential_store_enabled" : "false"
> }
> },
> {
> "href" :
> "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/ZOOKEEPER;,
> "StackServices" : {
> "service_name" : "ZOOKEEPER",
> "stack_name" : "HDP",
> "stack_version" : "2.0",
> "credential_store_supported" : "false",
> "credential_store_enabled" : "false"
> }
> }
> ]
> }
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18744) Ambari-server: REST API changes to GET and PUT credential store information
[
https://issues.apache.org/jira/browse/AMBARI-18744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-18744:
---
Status: Patch Available (was: Open)
> Ambari-server: REST API changes to GET and PUT credential store information
> ---
>
> Key: AMBARI-18744
> URL: https://issues.apache.org/jira/browse/AMBARI-18744
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53283.patch
>
>
> *Support stack definition for credential store information*
> To support backward compatibility, services must be tagged to indicate
> whether they support credential store backed passwords. This requires changes
> in the stack definition object model.
> {code}
>
> SERVICE_NAME
> :
>
> true
> false
>
> :
> :
>
> {code}
> *REST API support is required to GET _credential_store_supported_ and
> _credential_store_enabled_ values for a service:*
> {quote}api/v1/clusters//services?fields=ServiceInfo/service_name,ServiceInfo/credential_store_supported,ServiceInfo/credential_store_enabled{quote}
> *REST API support is required to PUT _credential_store_enabled_ value for a
> service:*
> {quote}api/v1/clusters//services?ServiceInfo/service_name.in(RANGER,HIVE)
> {
> ServiceInfo: {
> credential_store_enabled: “true”
> }
> }{quote}
> {quote}api/v1/clusters/testcluster/services/RANGER -X PUT -d '{"ServiceInfo"
> : {"credential_store_enabled":"true"}}'
> {quote}
> {quote}api/v1/clusters/testcluster/services?ServiceInfo/service_name=ZOOKEEPER
> -X PUT -d '{"ServiceInfo" : {"credential_store_enabled":"false"}}'{quote}
> *REST API to get Stack definition*
> {quote}
> curl -u admin:admin -H "X-Requested-By: ambari" -X GET
> http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services
> {quote}
> {quote}
> {
> "href" : "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/;,
> {
> "href" :
> "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/YARN;,
> "StackServices" : {
> "service_name" : "YARN",
> "stack_name" : "HDP",
> "stack_version" : "2.0",
> "credential_store_supported" : "false",
> "credential_store_enabled" : "false"
> }
> },
> {
> "href" :
> "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/ZOOKEEPER;,
> "StackServices" : {
> "service_name" : "ZOOKEEPER",
> "stack_name" : "HDP",
> "stack_version" : "2.0",
> "credential_store_supported" : "false",
> "credential_store_enabled" : "false"
> }
> }
> ]
> }
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18744) Ambari-server: REST API changes to GET and PUT credential store information
[
https://issues.apache.org/jira/browse/AMBARI-18744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-18744:
---
Attachment: (was: rb53283.patch)
> Ambari-server: REST API changes to GET and PUT credential store information
> ---
>
> Key: AMBARI-18744
> URL: https://issues.apache.org/jira/browse/AMBARI-18744
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53283.patch
>
>
> *Support stack definition for credential store information*
> To support backward compatibility, services must be tagged to indicate
> whether they support credential store backed passwords. This requires changes
> in the stack definition object model.
> {code}
>
> SERVICE_NAME
> :
>
> true
> false
>
> :
> :
>
> {code}
> *REST API support is required to GET _credential_store_supported_ and
> _credential_store_enabled_ values for a service:*
> {quote}api/v1/clusters//services?fields=ServiceInfo/service_name,ServiceInfo/credential_store_supported,ServiceInfo/credential_store_enabled{quote}
> *REST API support is required to PUT _credential_store_enabled_ value for a
> service:*
> {quote}api/v1/clusters//services?ServiceInfo/service_name.in(RANGER,HIVE)
> {
> ServiceInfo: {
> credential_store_enabled: “true”
> }
> }{quote}
> {quote}api/v1/clusters/testcluster/services/RANGER -X PUT -d '{"ServiceInfo"
> : {"credential_store_enabled":"true"}}'
> {quote}
> {quote}api/v1/clusters/testcluster/services?ServiceInfo/service_name=ZOOKEEPER
> -X PUT -d '{"ServiceInfo" : {"credential_store_enabled":"false"}}'{quote}
> *REST API to get Stack definition*
> {quote}
> curl -u admin:admin -H "X-Requested-By: ambari" -X GET
> http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services
> {quote}
> {quote}
> {
> "href" : "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/;,
> {
> "href" :
> "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/YARN;,
> "StackServices" : {
> "service_name" : "YARN",
> "stack_name" : "HDP",
> "stack_version" : "2.0",
> "credential_store_supported" : "false",
> "credential_store_enabled" : "false"
> }
> },
> {
> "href" :
> "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/ZOOKEEPER;,
> "StackServices" : {
> "service_name" : "ZOOKEEPER",
> "stack_name" : "HDP",
> "stack_version" : "2.0",
> "credential_store_supported" : "false",
> "credential_store_enabled" : "false"
> }
> }
> ]
> }
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18733) Perf: Allow running multiple Ambari Agents on the same host
[
https://issues.apache.org/jira/browse/AMBARI-18733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15627483#comment-15627483
]
Hadoop QA commented on AMBARI-18733:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836457/AMBARI-18733.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 3 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 .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9088//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9088//console
This message is automatically generated.
> Perf: Allow running multiple Ambari Agents on the same host
> ---
>
> Key: AMBARI-18733
> URL: https://issues.apache.org/jira/browse/AMBARI-18733
> Project: Ambari
> Issue Type: Story
> Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-18733.patch
>
>
> Currently there are limitations to running multiple Ambari Agents on the same
> host because it uses a single path for
> /etc/ambari-agent/conf/ambari-agent.ini
> /var/run/ambari-agent/ambari-agent.pid
> /var/lib/ambari-agent/data
> /var/log/ambari-agent/
> Ambari Agent already has a way to change the port, log dir, and pid dir
> through its config file, so we also need it to support its own unique home
> directory with its own unique config file.
> Furthermore, the agent will have to override its hostname.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18346) SmartSense Mandatory Install
[
https://issues.apache.org/jira/browse/AMBARI-18346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15627449#comment-15627449
]
Hadoop QA commented on AMBARI-18346:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836471/AMBARI-18346.v1.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/9087//console
This message is automatically generated.
> SmartSense Mandatory Install
>
>
> Key: AMBARI-18346
> URL: https://issues.apache.org/jira/browse/AMBARI-18346
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-18346.v0.patch, AMBARI-18346.v1.patch
>
>
> Perform a UI hack to force selection of SmartSense for HDP stacks (the user
> cannot deselect).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18767) E2E Integration for Manage JournalNode Wizard
[
https://issues.apache.org/jira/browse/AMBARI-18767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15627445#comment-15627445
]
Hadoop QA commented on AMBARI-18767:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836488/AMBARI-18767.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:red}-1 core tests{color}. The test build failed in ambari-web
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9086//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9086//console
This message is automatically generated.
> E2E Integration for Manage JournalNode Wizard
> -
>
> Key: AMBARI-18767
> URL: https://issues.apache.org/jira/browse/AMBARI-18767
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.5.0
>
> Attachments: AMBARI-18767.patch, AMBARI-18767_branch-2.5.patch
>
>
> E2E Integration for Manage JournalNode Wizard
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18767) E2E Integration for Manage JournalNode Wizard
[ https://issues.apache.org/jira/browse/AMBARI-18767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-18767: -- Status: Patch Available (was: Open) > E2E Integration for Manage JournalNode Wizard > - > > Key: AMBARI-18767 > URL: https://issues.apache.org/jira/browse/AMBARI-18767 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-18767.patch, AMBARI-18767_branch-2.5.patch > > > E2E Integration for Manage JournalNode Wizard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18767) E2E Integration for Manage JournalNode Wizard
[ https://issues.apache.org/jira/browse/AMBARI-18767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-18767: -- Attachment: AMBARI-18767.patch > E2E Integration for Manage JournalNode Wizard > - > > Key: AMBARI-18767 > URL: https://issues.apache.org/jira/browse/AMBARI-18767 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-18767.patch, AMBARI-18767_branch-2.5.patch > > > E2E Integration for Manage JournalNode Wizard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18752) Popover dialog displays raw html instead of rendering it
[ https://issues.apache.org/jira/browse/AMBARI-18752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15627283#comment-15627283 ] Hudson commented on AMBARI-18752: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5908 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5908/]) AMBARI-18752 Popover dialog displays raw html instead of rendering it (zhewang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=43d4857155f59e30c967b96dcd91b0224c2f214b]) * (edit) ambari-web/app/utils/helper.js > Popover dialog displays raw html instead of rendering it > > > Key: AMBARI-18752 > URL: https://issues.apache.org/jira/browse/AMBARI-18752 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 3.0.0 > > Attachments: AMBARI-18752.v0.patch, Screen Shot 2016-10-31 at > 12.16.47 PM.png > > > Popover dialog displays raw html instead of rendering it as shown in the > screen-shot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18767) E2E Integration for Manage JournalNode Wizard
[ https://issues.apache.org/jira/browse/AMBARI-18767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-18767: -- Attachment: AMBARI-18767_branch-2.5.patch AMBARI-18767.patch > E2E Integration for Manage JournalNode Wizard > - > > Key: AMBARI-18767 > URL: https://issues.apache.org/jira/browse/AMBARI-18767 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-18767_branch-2.5.patch > > > E2E Integration for Manage JournalNode Wizard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18767) E2E Integration for Manage JournalNode Wizard
[ https://issues.apache.org/jira/browse/AMBARI-18767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-18767: -- Attachment: (was: AMBARI-18767.patch) > E2E Integration for Manage JournalNode Wizard > - > > Key: AMBARI-18767 > URL: https://issues.apache.org/jira/browse/AMBARI-18767 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-18767_branch-2.5.patch > > > E2E Integration for Manage JournalNode Wizard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18767) E2E Integration for Manage JournalNode Wizard
Richard Zang created AMBARI-18767: - Summary: E2E Integration for Manage JournalNode Wizard Key: AMBARI-18767 URL: https://issues.apache.org/jira/browse/AMBARI-18767 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Richard Zang Assignee: Richard Zang Fix For: 2.5.0 E2E Integration for Manage JournalNode Wizard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18346) SmartSense Mandatory Install
[ https://issues.apache.org/jira/browse/AMBARI-18346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-18346: Attachment: AMBARI-18346.v1.patch > SmartSense Mandatory Install > > > Key: AMBARI-18346 > URL: https://issues.apache.org/jira/browse/AMBARI-18346 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18346.v0.patch, AMBARI-18346.v1.patch > > > Perform a UI hack to force selection of SmartSense for HDP stacks (the user > cannot deselect). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18346) SmartSense Mandatory Install
[ https://issues.apache.org/jira/browse/AMBARI-18346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-18346: Status: Patch Available (was: Open) > SmartSense Mandatory Install > > > Key: AMBARI-18346 > URL: https://issues.apache.org/jira/browse/AMBARI-18346 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18346.v0.patch, AMBARI-18346.v1.patch > > > Perform a UI hack to force selection of SmartSense for HDP stacks (the user > cannot deselect). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18346) SmartSense Mandatory Install
[ https://issues.apache.org/jira/browse/AMBARI-18346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-18346: Status: Open (was: Patch Available) > SmartSense Mandatory Install > > > Key: AMBARI-18346 > URL: https://issues.apache.org/jira/browse/AMBARI-18346 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18346.v0.patch > > > Perform a UI hack to force selection of SmartSense for HDP stacks (the user > cannot deselect). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18766) Add Service failed when none of the host components report version
[
https://issues.apache.org/jira/browse/AMBARI-18766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-18766:
---
Assignee: Jaimin Jetly (was: Sumit Mohanty)
> Add Service failed when none of the host components report version
> --
>
> Key: AMBARI-18766
> URL: https://issues.apache.org/jira/browse/AMBARI-18766
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Jaimin Jetly
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18766.patch
>
>
> When the underlying packages do not support versioned layout or do not report
> version (basically distro-select is not supported) then the stack version
> associated with the cluster is not changed to CURRENT from INIT.
> This blocks the UI from discovering the stack version associated with the
> cluster. UI instead should simply rely on the stack version that is specified
> in the cluster resource.
> *Cluster resource* ("version": "ODPi-1.0")
> {code}
> {
> "href": "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1;,
> "Clusters": {
> "cluster_id": 2,
> "cluster_name": "c1",
> "health_report": {
> "Host/stale_config": 1,
> "Host/maintenance_state": 0,
> "Host/host_status/ALERT": 0
> },
> "provisioning_state": "INSTALLED",
> "security_type": "NONE",
> "total_hosts": 1,
> "version": "ODPi-1.0",
> {code}
> *stack_version resource* ("state": "INIT")
> {code}
> {
> "href":
> "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1/stack_versions/1;,
> "ClusterStackVersions": {
> "cluster_name": "c1",
> "id": 1,
> "repository_version": 1,
> "stack": "ODPi",
> "state": "INIT",
> "version": "1.0",
> "host_states": {
> "CURRENT": [],
> "INIT": [],
> "INSTALLED": [],
> "INSTALLING": [],
> "INSTALL_FAILED": [],
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18679) Create HOST_ORDERED Upgrade Pack
[ https://issues.apache.org/jira/browse/AMBARI-18679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15626994#comment-15626994 ] Hudson commented on AMBARI-18679: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #239 (See [https://builds.apache.org/job/Ambari-branch-2.5/239/]) AMBARI-18679. Create HOST_ORDERED Upgrade Pack (ncole) (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3e906f848a41813466c27da81119a1313a1290a5]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/stack/UpgradePackTest.java * (add) ambari-server/src/test/resources/stacks/HDP/2.2.0/upgrades/upgrade_test_host_ordered.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/Grouping.java * (add) ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/HostOrderGrouping.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/UpgradeType.java * (edit) ambari-server/src/main/resources/upgrade-pack.xsd * (add) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/host-upgrade-2.5.xml > Create HOST_ORDERED Upgrade Pack > > > Key: AMBARI-18679 > URL: https://issues.apache.org/jira/browse/AMBARI-18679 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18679.patch > > > Create a new type of upgrade pack that allows an upgrade by Host Order. This > JIRA is only creating the skeleton. The classes for HOST_ORDERED will be > added as the feature progresses. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18766) Add Service failed when none of the host components report version
[
https://issues.apache.org/jira/browse/AMBARI-18766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15626950#comment-15626950
]
Hadoop QA commented on AMBARI-18766:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836448/AMBARI-18766.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:red}-1 core tests{color}. The test build failed in ambari-web
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9085//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9085//console
This message is automatically generated.
> Add Service failed when none of the host components report version
> --
>
> Key: AMBARI-18766
> URL: https://issues.apache.org/jira/browse/AMBARI-18766
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18766.patch
>
>
> When the underlying packages do not support versioned layout or do not report
> version (basically distro-select is not supported) then the stack version
> associated with the cluster is not changed to CURRENT from INIT.
> This blocks the UI from discovering the stack version associated with the
> cluster. UI instead should simply rely on the stack version that is specified
> in the cluster resource.
> *Cluster resource* ("version": "ODPi-1.0")
> {code}
> {
> "href": "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1;,
> "Clusters": {
> "cluster_id": 2,
> "cluster_name": "c1",
> "health_report": {
> "Host/stale_config": 1,
> "Host/maintenance_state": 0,
> "Host/host_status/ALERT": 0
> },
> "provisioning_state": "INSTALLED",
> "security_type": "NONE",
> "total_hosts": 1,
> "version": "ODPi-1.0",
> {code}
> *stack_version resource* ("state": "INIT")
> {code}
> {
> "href":
> "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1/stack_versions/1;,
> "ClusterStackVersions": {
> "cluster_name": "c1",
> "id": 1,
> "repository_version": 1,
> "stack": "ODPi",
> "state": "INIT",
> "version": "1.0",
> "host_states": {
> "CURRENT": [],
> "INIT": [],
> "INSTALLED": [],
> "INSTALLING": [],
> "INSTALL_FAILED": [],
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18766) Add Service failed when none of the host components report version
[
https://issues.apache.org/jira/browse/AMBARI-18766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaimin Jetly updated AMBARI-18766:
--
Component/s: (was: ambari-server)
ambari-web
> Add Service failed when none of the host components report version
> --
>
> Key: AMBARI-18766
> URL: https://issues.apache.org/jira/browse/AMBARI-18766
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18766.patch
>
>
> When the underlying packages do not support versioned layout or do not report
> version (basically distro-select is not supported) then the stack version
> associated with the cluster is not changed to CURRENT from INIT.
> This blocks the UI from discovering the stack version associated with the
> cluster. UI instead should simply rely on the stack version that is specified
> in the cluster resource.
> *Cluster resource* ("version": "ODPi-1.0")
> {code}
> {
> "href": "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1;,
> "Clusters": {
> "cluster_id": 2,
> "cluster_name": "c1",
> "health_report": {
> "Host/stale_config": 1,
> "Host/maintenance_state": 0,
> "Host/host_status/ALERT": 0
> },
> "provisioning_state": "INSTALLED",
> "security_type": "NONE",
> "total_hosts": 1,
> "version": "ODPi-1.0",
> {code}
> *stack_version resource* ("state": "INIT")
> {code}
> {
> "href":
> "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1/stack_versions/1;,
> "ClusterStackVersions": {
> "cluster_name": "c1",
> "id": 1,
> "repository_version": 1,
> "stack": "ODPi",
> "state": "INIT",
> "version": "1.0",
> "host_states": {
> "CURRENT": [],
> "INIT": [],
> "INSTALLED": [],
> "INSTALLING": [],
> "INSTALL_FAILED": [],
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18766) Add Service failed when none of the host components report version
[
https://issues.apache.org/jira/browse/AMBARI-18766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15626940#comment-15626940
]
Jaimin Jetly commented on AMBARI-18766:
---
+1 for the patch.
> Add Service failed when none of the host components report version
> --
>
> Key: AMBARI-18766
> URL: https://issues.apache.org/jira/browse/AMBARI-18766
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18766.patch
>
>
> When the underlying packages do not support versioned layout or do not report
> version (basically distro-select is not supported) then the stack version
> associated with the cluster is not changed to CURRENT from INIT.
> This blocks the UI from discovering the stack version associated with the
> cluster. UI instead should simply rely on the stack version that is specified
> in the cluster resource.
> *Cluster resource* ("version": "ODPi-1.0")
> {code}
> {
> "href": "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1;,
> "Clusters": {
> "cluster_id": 2,
> "cluster_name": "c1",
> "health_report": {
> "Host/stale_config": 1,
> "Host/maintenance_state": 0,
> "Host/host_status/ALERT": 0
> },
> "provisioning_state": "INSTALLED",
> "security_type": "NONE",
> "total_hosts": 1,
> "version": "ODPi-1.0",
> {code}
> *stack_version resource* ("state": "INIT")
> {code}
> {
> "href":
> "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1/stack_versions/1;,
> "ClusterStackVersions": {
> "cluster_name": "c1",
> "id": 1,
> "repository_version": 1,
> "stack": "ODPi",
> "state": "INIT",
> "version": "1.0",
> "host_states": {
> "CURRENT": [],
> "INIT": [],
> "INSTALLED": [],
> "INSTALLING": [],
> "INSTALL_FAILED": [],
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18733) Perf: Allow running multiple Ambari Agents on the same host
[ https://issues.apache.org/jira/browse/AMBARI-18733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18733: - Status: Patch Available (was: Open) > Perf: Allow running multiple Ambari Agents on the same host > --- > > Key: AMBARI-18733 > URL: https://issues.apache.org/jira/browse/AMBARI-18733 > Project: Ambari > Issue Type: Story > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-18733.patch > > > Currently there are limitations to running multiple Ambari Agents on the same > host because it uses a single path for > /etc/ambari-agent/conf/ambari-agent.ini > /var/run/ambari-agent/ambari-agent.pid > /var/lib/ambari-agent/data > /var/log/ambari-agent/ > Ambari Agent already has a way to change the port, log dir, and pid dir > through its config file, so we also need it to support its own unique home > directory with its own unique config file. > Furthermore, the agent will have to override its hostname. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18733) Perf: Allow running multiple Ambari Agents on the same host
[ https://issues.apache.org/jira/browse/AMBARI-18733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18733: - Attachment: AMBARI-18733.patch > Perf: Allow running multiple Ambari Agents on the same host > --- > > Key: AMBARI-18733 > URL: https://issues.apache.org/jira/browse/AMBARI-18733 > Project: Ambari > Issue Type: Story > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-18733.patch > > > Currently there are limitations to running multiple Ambari Agents on the same > host because it uses a single path for > /etc/ambari-agent/conf/ambari-agent.ini > /var/run/ambari-agent/ambari-agent.pid > /var/lib/ambari-agent/data > /var/log/ambari-agent/ > Ambari Agent already has a way to change the port, log dir, and pid dir > through its config file, so we also need it to support its own unique home > directory with its own unique config file. > Furthermore, the agent will have to override its hostname. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18734) Perf: Fix TODO comments added by AMBARI-18733 to allow multiple agents to use distinct config files on the same host
[ https://issues.apache.org/jira/browse/AMBARI-18734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18734: - Summary: Perf: Fix TODO comments added by AMBARI-18733 to allow multiple agents to use distinct config files on the same host (was: Perf: Allow registration of multiple Ambari Agents running on the same host) > Perf: Fix TODO comments added by AMBARI-18733 to allow multiple agents to use > distinct config files on the same host > > > Key: AMBARI-18734 > URL: https://issues.apache.org/jira/browse/AMBARI-18734 > Project: Ambari > Issue Type: Story > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > > Once each agent has its own unique hostname and port, they will need to > register with Ambari Server. Most likely we will choose manual registration > since the server should not have knowledge about multiple agents running on > the same host. > This means we may need to modify /etc/hosts file and other things to get > registration working. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18766) Add Service failed when none of the host components report version
[
https://issues.apache.org/jira/browse/AMBARI-18766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-18766:
---
Status: Patch Available (was: Open)
> Add Service failed when none of the host components report version
> --
>
> Key: AMBARI-18766
> URL: https://issues.apache.org/jira/browse/AMBARI-18766
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18766.patch
>
>
> When the underlying packages do not support versioned layout or do not report
> version (basically distro-select is not supported) then the stack version
> associated with the cluster is not changed to CURRENT from INIT.
> This blocks the UI from discovering the stack version associated with the
> cluster. UI instead should simply rely on the stack version that is specified
> in the cluster resource.
> *Cluster resource* ("version": "ODPi-1.0")
> {code}
> {
> "href": "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1;,
> "Clusters": {
> "cluster_id": 2,
> "cluster_name": "c1",
> "health_report": {
> "Host/stale_config": 1,
> "Host/maintenance_state": 0,
> "Host/host_status/ALERT": 0
> },
> "provisioning_state": "INSTALLED",
> "security_type": "NONE",
> "total_hosts": 1,
> "version": "ODPi-1.0",
> {code}
> *stack_version resource* ("state": "INIT")
> {code}
> {
> "href":
> "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1/stack_versions/1;,
> "ClusterStackVersions": {
> "cluster_name": "c1",
> "id": 1,
> "repository_version": 1,
> "stack": "ODPi",
> "state": "INIT",
> "version": "1.0",
> "host_states": {
> "CURRENT": [],
> "INIT": [],
> "INSTALLED": [],
> "INSTALLING": [],
> "INSTALL_FAILED": [],
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18766) Add Service failed when none of the host components report version
[
https://issues.apache.org/jira/browse/AMBARI-18766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-18766:
---
Attachment: AMBARI-18766.patch
> Add Service failed when none of the host components report version
> --
>
> Key: AMBARI-18766
> URL: https://issues.apache.org/jira/browse/AMBARI-18766
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18766.patch
>
>
> When the underlying packages do not support versioned layout or do not report
> version (basically distro-select is not supported) then the stack version
> associated with the cluster is not changed to CURRENT from INIT.
> This blocks the UI from discovering the stack version associated with the
> cluster. UI instead should simply rely on the stack version that is specified
> in the cluster resource.
> *Cluster resource* ("version": "ODPi-1.0")
> {code}
> {
> "href": "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1;,
> "Clusters": {
> "cluster_id": 2,
> "cluster_name": "c1",
> "health_report": {
> "Host/stale_config": 1,
> "Host/maintenance_state": 0,
> "Host/host_status/ALERT": 0
> },
> "provisioning_state": "INSTALLED",
> "security_type": "NONE",
> "total_hosts": 1,
> "version": "ODPi-1.0",
> {code}
> *stack_version resource* ("state": "INIT")
> {code}
> {
> "href":
> "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1/stack_versions/1;,
> "ClusterStackVersions": {
> "cluster_name": "c1",
> "id": 1,
> "repository_version": 1,
> "stack": "ODPi",
> "state": "INIT",
> "version": "1.0",
> "host_states": {
> "CURRENT": [],
> "INIT": [],
> "INSTALLED": [],
> "INSTALLING": [],
> "INSTALL_FAILED": [],
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18766) Add Service failed when none of the host components report version
Sumit Mohanty created AMBARI-18766:
--
Summary: Add Service failed when none of the host components
report version
Key: AMBARI-18766
URL: https://issues.apache.org/jira/browse/AMBARI-18766
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.0
Reporter: Sumit Mohanty
Assignee: Sumit Mohanty
Priority: Critical
Fix For: 2.4.2
When the underlying packages do not support versioned layout or do not report
version (basically distro-select is not supported) then the stack version
associated with the cluster is not changed to CURRENT from INIT.
This blocks the UI from discovering the stack version associated with the
cluster. UI instead should simply rely on the stack version that is specified
in the cluster resource.
*Cluster resource* ("version": "ODPi-1.0")
{code}
{
"href": "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1;,
"Clusters": {
"cluster_id": 2,
"cluster_name": "c1",
"health_report": {
"Host/stale_config": 1,
"Host/maintenance_state": 0,
"Host/host_status/ALERT": 0
},
"provisioning_state": "INSTALLED",
"security_type": "NONE",
"total_hosts": 1,
"version": "ODPi-1.0",
{code}
*stack_version resource* ("state": "INIT")
{code}
{
"href":
"http://c6402.ambari.apache.org:8080/api/v1/clusters/c1/stack_versions/1;,
"ClusterStackVersions": {
"cluster_name": "c1",
"id": 1,
"repository_version": 1,
"stack": "ODPi",
"state": "INIT",
"version": "1.0",
"host_states": {
"CURRENT": [],
"INIT": [],
"INSTALLED": [],
"INSTALLING": [],
"INSTALL_FAILED": [],
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18764) Fix missing checkboxes and radiobuttons
[ https://issues.apache.org/jira/browse/AMBARI-18764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-18764: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Fix missing checkboxes and radiobuttons > --- > > Key: AMBARI-18764 > URL: https://issues.apache.org/jira/browse/AMBARI-18764 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-18764.patch > > > Restore checkboxes and radiobuttons in the following places: > - Metric Actions dropdown > - Manual items in Upgrade wizard > - Create/select config group popup > - Start TLS option in Create Alert Notification popup > - Ignore Errors checkbox on step 3 of Kerberos wizard > - Regenerate keytabs popup -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18679) Create HOST_ORDERED Upgrade Pack
[ https://issues.apache.org/jira/browse/AMBARI-18679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15626748#comment-15626748 ] Hudson commented on AMBARI-18679: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5906 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5906/]) AMBARI-18679. Create HOST_ORDERED Upgrade Pack. part 2 (ncole) (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2a983d4e9da2472d47a6e52f391471c55bcf43d6]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/host-ordered-upgrade.xml > Create HOST_ORDERED Upgrade Pack > > > Key: AMBARI-18679 > URL: https://issues.apache.org/jira/browse/AMBARI-18679 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18679.patch > > > Create a new type of upgrade pack that allows an upgrade by Host Order. This > JIRA is only creating the skeleton. The classes for HOST_ORDERED will be > added as the feature progresses. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18744) Ambari-server: REST API changes to GET and PUT credential store information
[
https://issues.apache.org/jira/browse/AMBARI-18744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15626658#comment-15626658
]
Hadoop QA commented on AMBARI-18744:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836435/rb53283.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 2 new
or modified test files.
{color:red}-1 javac{color:red}. The patch appears to cause the build to
fail.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9084//console
This message is automatically generated.
> Ambari-server: REST API changes to GET and PUT credential store information
> ---
>
> Key: AMBARI-18744
> URL: https://issues.apache.org/jira/browse/AMBARI-18744
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53283.patch
>
>
> *Support stack definition for credential store information*
> To support backward compatibility, services must be tagged to indicate
> whether they support credential store backed passwords. This requires changes
> in the stack definition object model.
> {code}
>
> SERVICE_NAME
> :
>
> true
> false
>
> :
> :
>
> {code}
> *REST API support is required to GET _credential_store_supported_ and
> _credential_store_enabled_ values for a service:*
> {quote}api/v1/clusters//services?fields=ServiceInfo/service_name,ServiceInfo/credential_store_supported,ServiceInfo/credential_store_enabled{quote}
> *REST API support is required to PUT _credential_store_enabled_ value for a
> service:*
> {quote}api/v1/clusters//services?ServiceInfo/service_name.in(RANGER,HIVE)
> {
> ServiceInfo: {
> credential_store_enabled: “true”
> }
> }{quote}
> {quote}api/v1/clusters/testcluster/services/RANGER -X PUT -d '{"ServiceInfo"
> : {"credential_store_enabled":"true"}}'
> {quote}
> {quote}api/v1/clusters/testcluster/services?ServiceInfo/service_name=ZOOKEEPER
> -X PUT -d '{"ServiceInfo" : {"credential_store_enabled":"false"}}'{quote}
> *REST API to get Stack definition*
> {quote}
> curl -u admin:admin -H "X-Requested-By: ambari" -X GET
> http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services
> {quote}
> {quote}
> {
> "href" : "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/;,
> {
> "href" :
> "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/YARN;,
> "StackServices" : {
> "service_name" : "YARN",
> "stack_name" : "HDP",
> "stack_version" : "2.0",
> "credential_store_supported" : "false",
> "credential_store_enabled" : "false"
> }
> },
> {
> "href" :
> "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/ZOOKEEPER;,
> "StackServices" : {
> "service_name" : "ZOOKEEPER",
> "stack_name" : "HDP",
> "stack_version" : "2.0",
> "credential_store_supported" : "false",
> "credential_store_enabled" : "false"
> }
> }
> ]
> }
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18679) Create HOST_ORDERED Upgrade Pack
[ https://issues.apache.org/jira/browse/AMBARI-18679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15626629#comment-15626629 ] Hudson commented on AMBARI-18679: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5905 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5905/]) AMBARI-18679. Create HOST_ORDERED Upgrade Pack (ncole) (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ba526d9a2cfbb84ce03787fde5e3cf740950dc18]) * (add) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/host-ordered-upgrade.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/Grouping.java * (add) ambari-server/src/test/resources/stacks/HDP/2.2.0/upgrades/upgrade_test_host_ordered.xml * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/stack/UpgradePackTest.java * (add) ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/HostOrderGrouping.java * (edit) ambari-server/src/main/resources/upgrade-pack.xsd * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/UpgradeType.java > Create HOST_ORDERED Upgrade Pack > > > Key: AMBARI-18679 > URL: https://issues.apache.org/jira/browse/AMBARI-18679 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18679.patch > > > Create a new type of upgrade pack that allows an upgrade by Host Order. This > JIRA is only creating the skeleton. The classes for HOST_ORDERED will be > added as the feature progresses. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18744) Ambari-server: REST API changes to GET and PUT credential store information
[
https://issues.apache.org/jira/browse/AMBARI-18744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-18744:
---
Status: Patch Available (was: Open)
> Ambari-server: REST API changes to GET and PUT credential store information
> ---
>
> Key: AMBARI-18744
> URL: https://issues.apache.org/jira/browse/AMBARI-18744
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53283.patch
>
>
> *Support stack definition for credential store information*
> To support backward compatibility, services must be tagged to indicate
> whether they support credential store backed passwords. This requires changes
> in the stack definition object model.
> {code}
>
> SERVICE_NAME
> :
>
> true
> false
>
> :
> :
>
> {code}
> *REST API support is required to GET _credential_store_supported_ and
> _credential_store_enabled_ values for a service:*
> {quote}api/v1/clusters//services?fields=ServiceInfo/service_name,ServiceInfo/credential_store_supported,ServiceInfo/credential_store_enabled{quote}
> *REST API support is required to PUT _credential_store_enabled_ value for a
> service:*
> {quote}api/v1/clusters//services?ServiceInfo/service_name.in(RANGER,HIVE)
> {
> ServiceInfo: {
> credential_store_enabled: “true”
> }
> }{quote}
> {quote}api/v1/clusters/testcluster/services/RANGER -X PUT -d '{"ServiceInfo"
> : {"credential_store_enabled":"true"}}'
> {quote}
> {quote}api/v1/clusters/testcluster/services?ServiceInfo/service_name=ZOOKEEPER
> -X PUT -d '{"ServiceInfo" : {"credential_store_enabled":"false"}}'{quote}
> *REST API to get Stack definition*
> {quote}
> curl -u admin:admin -H "X-Requested-By: ambari" -X GET
> http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services
> {quote}
> {quote}
> {
> "href" : "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/;,
> {
> "href" :
> "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/YARN;,
> "StackServices" : {
> "service_name" : "YARN",
> "stack_name" : "HDP",
> "stack_version" : "2.0",
> "credential_store_supported" : "false",
> "credential_store_enabled" : "false"
> }
> },
> {
> "href" :
> "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/ZOOKEEPER;,
> "StackServices" : {
> "service_name" : "ZOOKEEPER",
> "stack_name" : "HDP",
> "stack_version" : "2.0",
> "credential_store_supported" : "false",
> "credential_store_enabled" : "false"
> }
> }
> ]
> }
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18744) Ambari-server: REST API changes to GET and PUT credential store information
[
https://issues.apache.org/jira/browse/AMBARI-18744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-18744:
---
Attachment: rb53283.patch
> Ambari-server: REST API changes to GET and PUT credential store information
> ---
>
> Key: AMBARI-18744
> URL: https://issues.apache.org/jira/browse/AMBARI-18744
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53283.patch
>
>
> *Support stack definition for credential store information*
> To support backward compatibility, services must be tagged to indicate
> whether they support credential store backed passwords. This requires changes
> in the stack definition object model.
> {code}
>
> SERVICE_NAME
> :
>
> true
> false
>
> :
> :
>
> {code}
> *REST API support is required to GET _credential_store_supported_ and
> _credential_store_enabled_ values for a service:*
> {quote}api/v1/clusters//services?fields=ServiceInfo/service_name,ServiceInfo/credential_store_supported,ServiceInfo/credential_store_enabled{quote}
> *REST API support is required to PUT _credential_store_enabled_ value for a
> service:*
> {quote}api/v1/clusters//services?ServiceInfo/service_name.in(RANGER,HIVE)
> {
> ServiceInfo: {
> credential_store_enabled: “true”
> }
> }{quote}
> {quote}api/v1/clusters/testcluster/services/RANGER -X PUT -d '{"ServiceInfo"
> : {"credential_store_enabled":"true"}}'
> {quote}
> {quote}api/v1/clusters/testcluster/services?ServiceInfo/service_name=ZOOKEEPER
> -X PUT -d '{"ServiceInfo" : {"credential_store_enabled":"false"}}'{quote}
> *REST API to get Stack definition*
> {quote}
> curl -u admin:admin -H "X-Requested-By: ambari" -X GET
> http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services
> {quote}
> {quote}
> {
> "href" : "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/;,
> {
> "href" :
> "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/YARN;,
> "StackServices" : {
> "service_name" : "YARN",
> "stack_name" : "HDP",
> "stack_version" : "2.0",
> "credential_store_supported" : "false",
> "credential_store_enabled" : "false"
> }
> },
> {
> "href" :
> "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/ZOOKEEPER;,
> "StackServices" : {
> "service_name" : "ZOOKEEPER",
> "stack_name" : "HDP",
> "stack_version" : "2.0",
> "credential_store_supported" : "false",
> "credential_store_enabled" : "false"
> }
> }
> ]
> }
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18744) Ambari-server: REST API changes to GET and PUT credential store information
[
https://issues.apache.org/jira/browse/AMBARI-18744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-18744:
---
Attachment: (was: rb53283.patch)
> Ambari-server: REST API changes to GET and PUT credential store information
> ---
>
> Key: AMBARI-18744
> URL: https://issues.apache.org/jira/browse/AMBARI-18744
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53283.patch
>
>
> *Support stack definition for credential store information*
> To support backward compatibility, services must be tagged to indicate
> whether they support credential store backed passwords. This requires changes
> in the stack definition object model.
> {code}
>
> SERVICE_NAME
> :
>
> true
> false
>
> :
> :
>
> {code}
> *REST API support is required to GET _credential_store_supported_ and
> _credential_store_enabled_ values for a service:*
> {quote}api/v1/clusters//services?fields=ServiceInfo/service_name,ServiceInfo/credential_store_supported,ServiceInfo/credential_store_enabled{quote}
> *REST API support is required to PUT _credential_store_enabled_ value for a
> service:*
> {quote}api/v1/clusters//services?ServiceInfo/service_name.in(RANGER,HIVE)
> {
> ServiceInfo: {
> credential_store_enabled: “true”
> }
> }{quote}
> {quote}api/v1/clusters/testcluster/services/RANGER -X PUT -d '{"ServiceInfo"
> : {"credential_store_enabled":"true"}}'
> {quote}
> {quote}api/v1/clusters/testcluster/services?ServiceInfo/service_name=ZOOKEEPER
> -X PUT -d '{"ServiceInfo" : {"credential_store_enabled":"false"}}'{quote}
> *REST API to get Stack definition*
> {quote}
> curl -u admin:admin -H "X-Requested-By: ambari" -X GET
> http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services
> {quote}
> {quote}
> {
> "href" : "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/;,
> {
> "href" :
> "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/YARN;,
> "StackServices" : {
> "service_name" : "YARN",
> "stack_name" : "HDP",
> "stack_version" : "2.0",
> "credential_store_supported" : "false",
> "credential_store_enabled" : "false"
> }
> },
> {
> "href" :
> "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/ZOOKEEPER;,
> "StackServices" : {
> "service_name" : "ZOOKEEPER",
> "stack_name" : "HDP",
> "stack_version" : "2.0",
> "credential_store_supported" : "false",
> "credential_store_enabled" : "false"
> }
> }
> ]
> }
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18744) Ambari-server: REST API changes to GET and PUT credential store information
[
https://issues.apache.org/jira/browse/AMBARI-18744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-18744:
---
Status: Open (was: Patch Available)
> Ambari-server: REST API changes to GET and PUT credential store information
> ---
>
> Key: AMBARI-18744
> URL: https://issues.apache.org/jira/browse/AMBARI-18744
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53283.patch
>
>
> *Support stack definition for credential store information*
> To support backward compatibility, services must be tagged to indicate
> whether they support credential store backed passwords. This requires changes
> in the stack definition object model.
> {code}
>
> SERVICE_NAME
> :
>
> true
> false
>
> :
> :
>
> {code}
> *REST API support is required to GET _credential_store_supported_ and
> _credential_store_enabled_ values for a service:*
> {quote}api/v1/clusters//services?fields=ServiceInfo/service_name,ServiceInfo/credential_store_supported,ServiceInfo/credential_store_enabled{quote}
> *REST API support is required to PUT _credential_store_enabled_ value for a
> service:*
> {quote}api/v1/clusters//services?ServiceInfo/service_name.in(RANGER,HIVE)
> {
> ServiceInfo: {
> credential_store_enabled: “true”
> }
> }{quote}
> {quote}api/v1/clusters/testcluster/services/RANGER -X PUT -d '{"ServiceInfo"
> : {"credential_store_enabled":"true"}}'
> {quote}
> {quote}api/v1/clusters/testcluster/services?ServiceInfo/service_name=ZOOKEEPER
> -X PUT -d '{"ServiceInfo" : {"credential_store_enabled":"false"}}'{quote}
> *REST API to get Stack definition*
> {quote}
> curl -u admin:admin -H "X-Requested-By: ambari" -X GET
> http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services
> {quote}
> {quote}
> {
> "href" : "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/;,
> {
> "href" :
> "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/YARN;,
> "StackServices" : {
> "service_name" : "YARN",
> "stack_name" : "HDP",
> "stack_version" : "2.0",
> "credential_store_supported" : "false",
> "credential_store_enabled" : "false"
> }
> },
> {
> "href" :
> "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/ZOOKEEPER;,
> "StackServices" : {
> "service_name" : "ZOOKEEPER",
> "stack_name" : "HDP",
> "stack_version" : "2.0",
> "credential_store_supported" : "false",
> "credential_store_enabled" : "false"
> }
> }
> ]
> }
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18765) Services with invalid themes hang the UI when you attempt to add them
[
https://issues.apache.org/jira/browse/AMBARI-18765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15626486#comment-15626486
]
Hadoop QA commented on AMBARI-18765:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836419/AMBARI-18765.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 5 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:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.state.cluster.ClusterDeadlockTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9083//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9083//console
This message is automatically generated.
> Services with invalid themes hang the UI when you attempt to add them
> -
>
> Key: AMBARI-18765
> URL: https://issues.apache.org/jira/browse/AMBARI-18765
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.4.0, 2.5.0
>Reporter: Tim Thorpe
>Assignee: Tim Thorpe
> Fix For: trunk, 2.5.0, 2.4.2
>
> Attachments: AMBARI-18765.patch
>
>
> For a given service if the theme.json file is not properly formatted, Ambari
> server will still start 'successfully' but attempts to add that service to
> the cluster will fail.
> The Ambari server start will log the theme error. Although it neglects to
> mention which theme file and service are in error.
> When you attempt to add the service, it will query for the service's themes:
> api/v1/stacks//versions//services?StackServices/service_name.in(HDFS,YARN,MAPREDUCE2,ZOOKEEPER,RANGER,RANGER_KMS,SLIDER)/ThemeInfo/default=true=themes/*
> This will return something like the following for the invalid theme:
> "ThemeInfo" : {
>"default" : true,
>"file_name" : "theme_version_2.json",
>"service_name" : "RANGER_KMS",
>"stack_name" : "BigInsights",
>"stack_version" : "4.3",
>"theme_data" : null
> }
> where the theme_data is null.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18764) Fix missing checkboxes and radiobuttons
[
https://issues.apache.org/jira/browse/AMBARI-18764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15626385#comment-15626385
]
Hadoop QA commented on AMBARI-18764:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836407/AMBARI-18764.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:red}-1 core tests{color}. The test build failed in ambari-web
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9082//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9082//console
This message is automatically generated.
> Fix missing checkboxes and radiobuttons
> ---
>
> Key: AMBARI-18764
> URL: https://issues.apache.org/jira/browse/AMBARI-18764
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-18764.patch
>
>
> Restore checkboxes and radiobuttons in the following places:
> - Metric Actions dropdown
> - Manual items in Upgrade wizard
> - Create/select config group popup
> - Start TLS option in Create Alert Notification popup
> - Ignore Errors checkbox on step 3 of Kerberos wizard
> - Regenerate keytabs popup
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18763) Ambari upgrade fails when add-on mpack is installed
[ https://issues.apache.org/jira/browse/AMBARI-18763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15626383#comment-15626383 ] Hudson commented on AMBARI-18763: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5904 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5904/]) AMBARI-18763: Ambari upgrade fails when add-on mpack is installed (jluniya: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=cc14719c774097af24faa559000fb3b714266802]) * (edit) ambari-server/src/main/python/ambari_server/serverUpgrade.py > Ambari upgrade fails when add-on mpack is installed > --- > > Key: AMBARI-18763 > URL: https://issues.apache.org/jira/browse/AMBARI-18763 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Jayush Luniya >Assignee: Jayush Luniya >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18763.patch > > > Install Ambari 2.4.0 > Install an add-on mpack > Upgrade Ambari from 2.4.0 to 2.4.1 > Ambari upgrade fails > ambari-server upgrade > Using python /usr/bin/python > Upgrading ambari-server > Updating properties in ambari.properties ... > WARNING: Original file ambari-env.sh kept > ERROR: Unexpected OSError: Errno 17 File exists > For more info run ambari-server with -v or --verbose option > Note; Attached the ambari server upgrade in verbose output -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18763) Ambari upgrade fails when add-on mpack is installed
[ https://issues.apache.org/jira/browse/AMBARI-18763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15626361#comment-15626361 ] Hudson commented on AMBARI-18763: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #238 (See [https://builds.apache.org/job/Ambari-branch-2.5/238/]) AMBARI-18763: Ambari upgrade fails when add-on mpack is installed (jluniya: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=45538aa50f68c83660a317e41462e2b3ba8b3698]) * (edit) ambari-server/src/main/python/ambari_server/serverUpgrade.py > Ambari upgrade fails when add-on mpack is installed > --- > > Key: AMBARI-18763 > URL: https://issues.apache.org/jira/browse/AMBARI-18763 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Jayush Luniya >Assignee: Jayush Luniya >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18763.patch > > > Install Ambari 2.4.0 > Install an add-on mpack > Upgrade Ambari from 2.4.0 to 2.4.1 > Ambari upgrade fails > ambari-server upgrade > Using python /usr/bin/python > Upgrading ambari-server > Updating properties in ambari.properties ... > WARNING: Original file ambari-env.sh kept > ERROR: Unexpected OSError: Errno 17 File exists > For more info run ambari-server with -v or --verbose option > Note; Attached the ambari server upgrade in verbose output -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18713) use exclude list of mount device types on docker containers
[
https://issues.apache.org/jira/browse/AMBARI-18713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15626319#comment-15626319
]
Hadoop QA commented on AMBARI-18713:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836352/AMBARI-18713.patch.1
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 6 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 ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9081//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9081//console
This message is automatically generated.
> use exclude list of mount device types on docker containers
> ---
>
> Key: AMBARI-18713
> URL: https://issues.apache.org/jira/browse/AMBARI-18713
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18713.patch, AMBARI-18713.patch.1
>
>
> * Remove logic from UI that picks a single host to represent the entire
> cluster
> * Have each host report their mount devices and how much space is available
> in each one, so Ambari can store this in the DB (this will affect new
> installs only or newly registered hosts)
> * Move logic to Stack Advisor
> * Use exclude list
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanel=15626341#comment-15626341 ] Amruta Borkar commented on AMBARI-18355: The test case doesn't seem to be failing due to this 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_v6.patch, > AMBARI-18355_v7.patch, AMBARI-18355_v8.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-18708) Add a cluster version directly as INSTALLED
[
https://issues.apache.org/jira/browse/AMBARI-18708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole updated AMBARI-18708:
---
Assignee: Jonathan Hurley (was: Nate Cole)
> Add a cluster version directly as INSTALLED
> ---
>
> Key: AMBARI-18708
> URL: https://issues.apache.org/jira/browse/AMBARI-18708
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
>
> When creating a repository for a cluster, allow the API to set directly to
> INSTALLED. This is the case where bits are known to be preinstalled.
> This API call will set direct values for {{cluster_version}} and
> {{host_version}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18765) Services with invalid themes hang the UI when you attempt to add them
[
https://issues.apache.org/jira/browse/AMBARI-18765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Thorpe updated AMBARI-18765:
Attachment: AMBARI-18765.patch
> Services with invalid themes hang the UI when you attempt to add them
> -
>
> Key: AMBARI-18765
> URL: https://issues.apache.org/jira/browse/AMBARI-18765
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.4.0, 2.5.0
>Reporter: Tim Thorpe
>Assignee: Tim Thorpe
> Fix For: trunk, 2.5.0, 2.4.2
>
> Attachments: AMBARI-18765.patch
>
>
> For a given service if the theme.json file is not properly formatted, Ambari
> server will still start 'successfully' but attempts to add that service to
> the cluster will fail.
> The Ambari server start will log the theme error. Although it neglects to
> mention which theme file and service are in error.
> When you attempt to add the service, it will query for the service's themes:
> api/v1/stacks//versions//services?StackServices/service_name.in(HDFS,YARN,MAPREDUCE2,ZOOKEEPER,RANGER,RANGER_KMS,SLIDER)/ThemeInfo/default=true=themes/*
> This will return something like the following for the invalid theme:
> "ThemeInfo" : {
>"default" : true,
>"file_name" : "theme_version_2.json",
>"service_name" : "RANGER_KMS",
>"stack_name" : "BigInsights",
>"stack_version" : "4.3",
>"theme_data" : null
> }
> where the theme_data is null.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18765) Services with invalid themes hang the UI when you attempt to add them
[
https://issues.apache.org/jira/browse/AMBARI-18765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Thorpe updated AMBARI-18765:
Status: Patch Available (was: Open)
> Services with invalid themes hang the UI when you attempt to add them
> -
>
> Key: AMBARI-18765
> URL: https://issues.apache.org/jira/browse/AMBARI-18765
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.4.0, 2.5.0
>Reporter: Tim Thorpe
>Assignee: Tim Thorpe
> Fix For: trunk, 2.5.0, 2.4.2
>
> Attachments: AMBARI-18765.patch
>
>
> For a given service if the theme.json file is not properly formatted, Ambari
> server will still start 'successfully' but attempts to add that service to
> the cluster will fail.
> The Ambari server start will log the theme error. Although it neglects to
> mention which theme file and service are in error.
> When you attempt to add the service, it will query for the service's themes:
> api/v1/stacks//versions//services?StackServices/service_name.in(HDFS,YARN,MAPREDUCE2,ZOOKEEPER,RANGER,RANGER_KMS,SLIDER)/ThemeInfo/default=true=themes/*
> This will return something like the following for the invalid theme:
> "ThemeInfo" : {
>"default" : true,
>"file_name" : "theme_version_2.json",
>"service_name" : "RANGER_KMS",
>"stack_name" : "BigInsights",
>"stack_version" : "4.3",
>"theme_data" : null
> }
> where the theme_data is null.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18764) Fix missing checkboxes and radiobuttons
[ https://issues.apache.org/jira/browse/AMBARI-18764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15626220#comment-15626220 ] Aleksandr Kovalenko commented on AMBARI-18764: -- +1 for the patch > Fix missing checkboxes and radiobuttons > --- > > Key: AMBARI-18764 > URL: https://issues.apache.org/jira/browse/AMBARI-18764 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-18764.patch > > > Restore checkboxes and radiobuttons in the following places: > - Metric Actions dropdown > - Manual items in Upgrade wizard > - Create/select config group popup > - Start TLS option in Create Alert Notification popup > - Ignore Errors checkbox on step 3 of Kerberos wizard > - Regenerate keytabs popup -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18764) Fix missing checkboxes and radiobuttons
[ https://issues.apache.org/jira/browse/AMBARI-18764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-18764: -- Description: Restore checkboxes and radiobuttons in the following places: - Metric Actions dropdown - Manual items in Upgrade wizard - Create/select config group popup - Start TLS option in Create Alert Notification popup - Ignore Errors checkbox on step 3 of Kerberos wizard - Regenerate keytabs popup was: Restore checkboxes and radiobuttons in the following places: - Metric Actions dropdown - Manual items in Upgrade wizard - Create/select config group popup - Start TLS option in Create Alert Notification popup - Ignore Errors checkbox on step 3 of Kerberos wizard > Fix missing checkboxes and radiobuttons > --- > > Key: AMBARI-18764 > URL: https://issues.apache.org/jira/browse/AMBARI-18764 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-18764.patch > > > Restore checkboxes and radiobuttons in the following places: > - Metric Actions dropdown > - Manual items in Upgrade wizard > - Create/select config group popup > - Start TLS option in Create Alert Notification popup > - Ignore Errors checkbox on step 3 of Kerberos wizard > - Regenerate keytabs popup -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18764) Fix missing checkboxes and radiobuttons
[ https://issues.apache.org/jira/browse/AMBARI-18764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-18764: -- Attachment: AMBARI-18764.patch > Fix missing checkboxes and radiobuttons > --- > > Key: AMBARI-18764 > URL: https://issues.apache.org/jira/browse/AMBARI-18764 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-18764.patch > > > Restore checkboxes and radiobuttons in the following places: > - Metric Actions dropdown > - Manual items in Upgrade wizard > - Create/select config group popup > - Start TLS option in Create Alert Notification popup > - Ignore Errors checkbox on step 3 of Kerberos wizard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18764) Fix missing checkboxes and radiobuttons
[ https://issues.apache.org/jira/browse/AMBARI-18764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-18764: -- Status: Patch Available (was: Open) > Fix missing checkboxes and radiobuttons > --- > > Key: AMBARI-18764 > URL: https://issues.apache.org/jira/browse/AMBARI-18764 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-18764.patch > > > Restore checkboxes and radiobuttons in the following places: > - Metric Actions dropdown > - Manual items in Upgrade wizard > - Create/select config group popup > - Start TLS option in Create Alert Notification popup > - Ignore Errors checkbox on step 3 of Kerberos wizard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18765) Services with invalid themes hang the UI when you attempt to add them
Tim Thorpe created AMBARI-18765:
---
Summary: Services with invalid themes hang the UI when you attempt
to add them
Key: AMBARI-18765
URL: https://issues.apache.org/jira/browse/AMBARI-18765
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: trunk, 2.4.0, 2.5.0
Reporter: Tim Thorpe
Assignee: Tim Thorpe
Fix For: trunk, 2.5.0, 2.4.2
For a given service if the theme.json file is not properly formatted, Ambari
server will still start 'successfully' but attempts to add that service to the
cluster will fail.
The Ambari server start will log the theme error. Although it neglects to
mention which theme file and service are in error.
When you attempt to add the service, it will query for the service's themes:
api/v1/stacks//versions//services?StackServices/service_name.in(HDFS,YARN,MAPREDUCE2,ZOOKEEPER,RANGER,RANGER_KMS,SLIDER)/ThemeInfo/default=true=themes/*
This will return something like the following for the invalid theme:
"ThemeInfo" : {
"default" : true,
"file_name" : "theme_version_2.json",
"service_name" : "RANGER_KMS",
"stack_name" : "BigInsights",
"stack_version" : "4.3",
"theme_data" : null
}
where the theme_data is null.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18764) Fix missing checkboxes and radiobuttons
Andrii Babiichuk created AMBARI-18764: - Summary: Fix missing checkboxes and radiobuttons Key: AMBARI-18764 URL: https://issues.apache.org/jira/browse/AMBARI-18764 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Fix For: 3.0.0 Restore checkboxes and radiobuttons in the following places: - Metric Actions dropdown - Manual items in Upgrade wizard - Create/select config group popup - Start TLS option in Create Alert Notification popup - Ignore Errors checkbox on step 3 of Kerberos wizard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18760) ambari-server.pid might not be created
[ https://issues.apache.org/jira/browse/AMBARI-18760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15626185#comment-15626185 ] Hudson commented on AMBARI-18760: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5903 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5903/]) AMBARI-18760 ambari-server.pid might not be created (dsen) (dsen: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c143be331f670da3aef2451ed6d3fe1b41c6d8c4]) * (edit) ambari-server/src/main/python/ambari_server/utils.py > ambari-server.pid might not be created > -- > > Key: AMBARI-18760 > URL: https://issues.apache.org/jira/browse/AMBARI-18760 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 2.4.2 > > Attachments: AMBARI-18760.patch > > > /var/run/ambari-server/ambari-server.pid might not be created, but IOError > not logged -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18760) ambari-server.pid might not be created
[ https://issues.apache.org/jira/browse/AMBARI-18760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-18760: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk, branch-2.5, branch-2.4 > ambari-server.pid might not be created > -- > > Key: AMBARI-18760 > URL: https://issues.apache.org/jira/browse/AMBARI-18760 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 2.4.2 > > Attachments: AMBARI-18760.patch > > > /var/run/ambari-server/ambari-server.pid might not be created, but IOError > not logged -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18725) Ambari Database Check failed to Complete Error
[
https://issues.apache.org/jira/browse/AMBARI-18725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15626082#comment-15626082
]
Hudson commented on AMBARI-18725:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #236 (See
[https://builds.apache.org/job/Ambari-branch-2.5/236/])
AMBARI-18725. Ambari Database Check failed to Complete Error (rlevas) (rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=93cbf671423b36292fa4c230e76bc1ca26fe5a15])
* (edit) ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql
> Ambari Database Check failed to Complete Error
> --
>
> Key: AMBARI-18725
> URL: https://issues.apache.org/jira/browse/AMBARI-18725
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0, 2.4.2
>Reporter: Matt
>Assignee: Robert Levas
>Priority: Blocker
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-18725_branch-2.4_01.patch,
> AMBARI-18725_branch-2.5_01.patch, AMBARI-18725_trunk_01.patch
>
>
> Built Ambari from branch-2.4, branch-2.5 and trunk. All the builds have the
> same issue when the start command is run.
> {code}> ambari-server start
> Using python /usr/bin/python
> Starting ambari-server
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> No errors were found.
> ERROR: Exiting with exit code 1.
> REASON: Database check failed to complete. Please check
> /var/log/ambari-server/ambari-server.log and
> /var/log/ambari-server/ambari-server-check-database.log for more
> information.{code}
> The database.log says {code}Error preallocating sequence numbers{code}
> Nothing suspicious on ambari-server.log.
> Log file ambari-server-check-database.log attached with this JIRA for
> reference.
> *Update*
> Reverting
> https://github.com/apache/ambari/commit/b632b33bc35afc5a01354e8916fdcdf698e49e19
> on a local copy of branch-2.4 fixed the issue on branch-2.4 build
> Reverting
> https://github.com/apache/ambari/commit/49f58e8402b543875c61f8d74a052bd6cd45a788
> on a local copy of branch-2.5 fixed the issue on branch-2.5 build
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18757) DB configs consistency check failed after upgrade from 2.1.1 to 2.4.2 (stack 2.3)
[
https://issues.apache.org/jira/browse/AMBARI-18757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15626079#comment-15626079
]
Hudson commented on AMBARI-18757:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #236 (See
[https://builds.apache.org/job/Ambari-branch-2.5/236/])
AMBARI-18757. DB configs consistency check failed after upgrade from
(vbrodetskyi:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6f5d214147a23eaa5e183877d9f5c3f1108e00ab])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog242.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog242Test.java
> DB configs consistency check failed after upgrade from 2.1.1 to 2.4.2 (stack
> 2.3)
> -
>
> Key: AMBARI-18757
> URL: https://issues.apache.org/jira/browse/AMBARI-18757
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.4.2
>
> Attachments: AMBARI-18757.patch
>
>
> 1)Install old version regarding env. (enable AD security)
> 2)Make ambari only upgrade
> Actual result:
> DB configs consistency check failed after upgrade from 2.1.1 to 2.4.2 (stack
> 2.3)
> {code}
> 2016-10-28 02:43:15,878 ERROR - Required config(s):
> storm-cluster-log4j,storm-worker-log4j is(are) not available for service
> STORM with service config version 4 in cluster cl1
> 2016-10-28 02:43:15,917 INFO - *** Check
> database completed ***
> 2016-10-28 02:47:01,109 INFO - *** Check
> database started ***
> 2016-10-28 02:47:12,523 INFO - Checking for configs not mapped to any cluster
> 2016-10-28 02:47:12,538 INFO - Checking for configs selected more than once
> 2016-10-28 02:47:12,541 INFO - Checking for hosts without state
> 2016-10-28 02:47:12,544 INFO - Checking host component states count equals
> host component desired states count
> 2016-10-28 02:47:12,548 INFO - Checking services and their configs
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / PIG
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / SPARK
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / MAPREDUCE2
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / YARN
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / FALCON
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / SLIDER
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / HIVE
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / TEZ
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / ZOOKEEPER
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / STORM
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / SQOOP
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / HBASE
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / OOZIE
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / FLUME
> 2016-10-28 02:47:17,675 INFO - Processing HDP-2.3 / KNOX
> 2016-10-28 02:47:17,675 INFO - Processing HDP-2.3 / KERBEROS
> 2016-10-28 02:47:17,675 INFO - Processing HDP-2.3 / HDFS
> 2016-10-28 02:47:17,675 INFO - Processing HDP-2.3 / AMBARI_METRICS
> 2016-10-28 02:47:17,682 ERROR - Required config(s): sqoop-site is(are) not
> available for service SQOOP with service config version 1 in cluster cl1
> 2016-10-28 02:47:17,682 ERROR - Required config(s):
> falcon-client.properties,falcon-log4j is(are) not available for service
> FALCON with service config version 3 in cluster cl1
> 2016-10-28 02:47:17,682 ERROR - Required config(s):
> spark-thrift-sparkconf,spark-hive-site-override is(are) not available for
> service SPARK with service config version 3 in cluster cl1
> 2016-10-28 02:47:17,682 ERROR - Required config(s):
> knoxsso-topology,admin-topology is(are) not available for service KNOX with
> service config version 3 in cluster cl1
> 2016-10-28 02:47:17,682 ERROR - Required config(s):
> ams-ssl-client,ams-ssl-server,ams-grafana-env,ams-grafana-ini is(are) not
> available for service AMBARI_METRICS with service config version 3 in cluster
> cl1
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18725) Ambari Database Check failed to Complete Error
[
https://issues.apache.org/jira/browse/AMBARI-18725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15626075#comment-15626075
]
Hudson commented on AMBARI-18725:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5902 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5902/])
AMBARI-18725. Ambari Database Check failed to Complete Error (rlevas) (rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=38cbda8826c126ca50aff6928c437d59b0168c7d])
* (edit) ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql
> Ambari Database Check failed to Complete Error
> --
>
> Key: AMBARI-18725
> URL: https://issues.apache.org/jira/browse/AMBARI-18725
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0, 2.4.2
>Reporter: Matt
>Assignee: Robert Levas
>Priority: Blocker
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-18725_branch-2.4_01.patch,
> AMBARI-18725_branch-2.5_01.patch, AMBARI-18725_trunk_01.patch
>
>
> Built Ambari from branch-2.4, branch-2.5 and trunk. All the builds have the
> same issue when the start command is run.
> {code}> ambari-server start
> Using python /usr/bin/python
> Starting ambari-server
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> No errors were found.
> ERROR: Exiting with exit code 1.
> REASON: Database check failed to complete. Please check
> /var/log/ambari-server/ambari-server.log and
> /var/log/ambari-server/ambari-server-check-database.log for more
> information.{code}
> The database.log says {code}Error preallocating sequence numbers{code}
> Nothing suspicious on ambari-server.log.
> Log file ambari-server-check-database.log attached with this JIRA for
> reference.
> *Update*
> Reverting
> https://github.com/apache/ambari/commit/b632b33bc35afc5a01354e8916fdcdf698e49e19
> on a local copy of branch-2.4 fixed the issue on branch-2.4 build
> Reverting
> https://github.com/apache/ambari/commit/49f58e8402b543875c61f8d74a052bd6cd45a788
> on a local copy of branch-2.5 fixed the issue on branch-2.5 build
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18763) Ambari upgrade fails when add-on mpack is installed
[ https://issues.apache.org/jira/browse/AMBARI-18763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15626069#comment-15626069 ] Jayush Luniya commented on AMBARI-18763: [~sumitmohanty] Can you review the attached patch? Its a one-line change. > Ambari upgrade fails when add-on mpack is installed > --- > > Key: AMBARI-18763 > URL: https://issues.apache.org/jira/browse/AMBARI-18763 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Jayush Luniya >Assignee: Jayush Luniya >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18763.patch > > > Install Ambari 2.4.0 > Install an add-on mpack > Upgrade Ambari from 2.4.0 to 2.4.1 > Ambari upgrade fails > ambari-server upgrade > Using python /usr/bin/python > Upgrading ambari-server > Updating properties in ambari.properties ... > WARNING: Original file ambari-env.sh kept > ERROR: Unexpected OSError: Errno 17 File exists > For more info run ambari-server with -v or --verbose option > Note; Attached the ambari server upgrade in verbose output -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18763) Ambari upgrade fails when add-on mpack is installed
[ https://issues.apache.org/jira/browse/AMBARI-18763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18763: --- Status: Patch Available (was: In Progress) > Ambari upgrade fails when add-on mpack is installed > --- > > Key: AMBARI-18763 > URL: https://issues.apache.org/jira/browse/AMBARI-18763 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Jayush Luniya >Assignee: Jayush Luniya >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18763.patch > > > Install Ambari 2.4.0 > Install an add-on mpack > Upgrade Ambari from 2.4.0 to 2.4.1 > Ambari upgrade fails > ambari-server upgrade > Using python /usr/bin/python > Upgrading ambari-server > Updating properties in ambari.properties ... > WARNING: Original file ambari-env.sh kept > ERROR: Unexpected OSError: Errno 17 File exists > For more info run ambari-server with -v or --verbose option > Note; Attached the ambari server upgrade in verbose output -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18763) Ambari upgrade fails when add-on mpack is installed
[ https://issues.apache.org/jira/browse/AMBARI-18763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18763: --- Attachment: AMBARI-18763.patch > Ambari upgrade fails when add-on mpack is installed > --- > > Key: AMBARI-18763 > URL: https://issues.apache.org/jira/browse/AMBARI-18763 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Jayush Luniya >Assignee: Jayush Luniya >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18763.patch > > > Install Ambari 2.4.0 > Install an add-on mpack > Upgrade Ambari from 2.4.0 to 2.4.1 > Ambari upgrade fails > ambari-server upgrade > Using python /usr/bin/python > Upgrading ambari-server > Updating properties in ambari.properties ... > WARNING: Original file ambari-env.sh kept > ERROR: Unexpected OSError: Errno 17 File exists > For more info run ambari-server with -v or --verbose option > Note; Attached the ambari server upgrade in verbose output -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18711) Ambari-server: DB changes to enable/disable credential store support
[ https://issues.apache.org/jira/browse/AMBARI-18711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15626006#comment-15626006 ] Hudson commented on AMBARI-18711: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5901 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5901/]) AMBARI-18711: Ambari-server: DB changes to enable/disable credential (nsomasundaram: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c0c02d05ff184f89df8e152a63689318160efb18]) * (edit) ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ServiceDesiredStateEntity.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/ServiceImpl.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/Service.java * (edit) ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java * (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql * (edit) ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql * (edit) ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql * (edit) ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql > Ambari-server: DB changes to enable/disable credential store support > > > Key: AMBARI-18711 > URL: https://issues.apache.org/jira/browse/AMBARI-18711 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 2.5.0 > > Attachments: rb53216.patch > > > To enable or disable a component to use credential store, changes are > required in the DB to keep track of this information. The > _servicedesiredstate_ table can keep track of this information using a new > *credential_store_enabled* column. > If a service supports reading passwords from the configuration's JCEKS file, > then it will specify this information in its stack definition. Services that > support using the credential store can be enabled or disabled to use it. > Services that do not, will always be disabled from using the credential store. > The option to enable or disable the components of a service that has > credential store support is provided via the UI and blueprint. This > information will then be captured in the _servicedesiredstate_ table in the > *credential_store_enabled* column. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-14160) Ambari Slider View should pick up multiple versions of the same app package
[ https://issues.apache.org/jira/browse/AMBARI-14160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-14160: Description: I was validating some fix for Slider hbase with Gour. A new Slider hbase app package was built and moved to under: /var/lib/ambari-server/resources/apps We tried naming the new app package ending with -ted.zip -999.zip After 'ambari-server restart', the new app package was not picked up by Ambari. Ambari Slider View should be able to accommodate more than one version of app package. was: I was validating some fix for Slider hbase with Gour. A new Slider hbase app package was built and moved to under: /var/lib/ambari-server/resources/apps We tried naming the new app package ending with -ted.zip -999.zip After 'ambari-server restart', the new app package was not picked up by Ambari. Ambari Slider View should be able to accommodate more than one version of app package. > Ambari Slider View should pick up multiple versions of the same app package > --- > > Key: AMBARI-14160 > URL: https://issues.apache.org/jira/browse/AMBARI-14160 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu > > I was validating some fix for Slider hbase with Gour. > A new Slider hbase app package was built and moved to under: > /var/lib/ambari-server/resources/apps > We tried naming the new app package ending with -ted.zip -999.zip > After 'ambari-server restart', the new app package was not picked up by > Ambari. > Ambari Slider View should be able to accommodate more than one version of app > package. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18725) Ambari Database Check failed to Complete Error
[
https://issues.apache.org/jira/browse/AMBARI-18725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-18725:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
{noformat}
commit 38cbda8826c126ca50aff6928c437d59b0168c7d
Author: Robert Levas
Date: Tue Nov 1 12:36:02 2016 -0400
{noformat}
Committed to branch-2.5
{noformat}
commit 93cbf671423b36292fa4c230e76bc1ca26fe5a15
Author: Robert Levas
Date: Tue Nov 1 12:37:09 2016 -0400
{noformat}
Committed to branch-2.4
{noformat}
commit db618b29c10c3f6384e5ed410e2c37fc89078d47
Author: Robert Levas
Date: Tue Nov 1 12:37:53 2016 -0400
{noformat}
> Ambari Database Check failed to Complete Error
> --
>
> Key: AMBARI-18725
> URL: https://issues.apache.org/jira/browse/AMBARI-18725
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0, 2.4.2
>Reporter: Matt
>Assignee: Robert Levas
>Priority: Blocker
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-18725_branch-2.4_01.patch,
> AMBARI-18725_branch-2.5_01.patch, AMBARI-18725_trunk_01.patch
>
>
> Built Ambari from branch-2.4, branch-2.5 and trunk. All the builds have the
> same issue when the start command is run.
> {code}> ambari-server start
> Using python /usr/bin/python
> Starting ambari-server
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> No errors were found.
> ERROR: Exiting with exit code 1.
> REASON: Database check failed to complete. Please check
> /var/log/ambari-server/ambari-server.log and
> /var/log/ambari-server/ambari-server-check-database.log for more
> information.{code}
> The database.log says {code}Error preallocating sequence numbers{code}
> Nothing suspicious on ambari-server.log.
> Log file ambari-server-check-database.log attached with this JIRA for
> reference.
> *Update*
> Reverting
> https://github.com/apache/ambari/commit/b632b33bc35afc5a01354e8916fdcdf698e49e19
> on a local copy of branch-2.4 fixed the issue on branch-2.4 build
> Reverting
> https://github.com/apache/ambari/commit/49f58e8402b543875c61f8d74a052bd6cd45a788
> on a local copy of branch-2.5 fixed the issue on branch-2.5 build
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18711) Ambari-server: DB changes to enable/disable credential store support
[ https://issues.apache.org/jira/browse/AMBARI-18711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18711: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari-server: DB changes to enable/disable credential store support > > > Key: AMBARI-18711 > URL: https://issues.apache.org/jira/browse/AMBARI-18711 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 2.5.0 > > Attachments: rb53216.patch > > > To enable or disable a component to use credential store, changes are > required in the DB to keep track of this information. The > _servicedesiredstate_ table can keep track of this information using a new > *credential_store_enabled* column. > If a service supports reading passwords from the configuration's JCEKS file, > then it will specify this information in its stack definition. Services that > support using the credential store can be enabled or disabled to use it. > Services that do not, will always be disabled from using the credential store. > The option to enable or disable the components of a service that has > credential store support is provided via the UI and blueprint. This > information will then be captured in the _servicedesiredstate_ table in the > *credential_store_enabled* column. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-18742) Ambari-server: Stack definition Object Model changes to support tag changes
[ https://issues.apache.org/jira/browse/AMBARI-18742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram resolved AMBARI-18742. Resolution: Duplicate > Ambari-server: Stack definition Object Model changes to support tag changes > --- > > Key: AMBARI-18742 > URL: https://issues.apache.org/jira/browse/AMBARI-18742 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 2.5.0 > > Attachments: rb53276.patch > > > Changes required in Stack object model to support the following stack > definition changes: > To support backward compatibility, services must be tagged to indicate > whether they support credential store backed passwords. > If services support credential store, they will also be able to read clear > text passwords. Services that do not support credential store will not be > able to decrypt the passwords in the configurations. > The server will send this information to the agent so that it can determine > whether it should store clear text passwords in the configuration files or > use JCEKS files. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18742) Ambari-server: Stack definition Object Model changes to support tag changes
[ https://issues.apache.org/jira/browse/AMBARI-18742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18742: --- Status: Open (was: Patch Available) > Ambari-server: Stack definition Object Model changes to support tag changes > --- > > Key: AMBARI-18742 > URL: https://issues.apache.org/jira/browse/AMBARI-18742 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 2.5.0 > > Attachments: rb53276.patch > > > Changes required in Stack object model to support the following stack > definition changes: > To support backward compatibility, services must be tagged to indicate > whether they support credential store backed passwords. > If services support credential store, they will also be able to read clear > text passwords. Services that do not support credential store will not be > able to decrypt the passwords in the configurations. > The server will send this information to the agent so that it can determine > whether it should store clear text passwords in the configuration files or > use JCEKS files. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18725) Ambari Database Check failed to Complete Error
[
https://issues.apache.org/jira/browse/AMBARI-18725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-18725:
--
Attachment: AMBARI-18725_trunk_01.patch
AMBARI-18725_branch-2.5_01.patch
AMBARI-18725_branch-2.4_01.patch
> Ambari Database Check failed to Complete Error
> --
>
> Key: AMBARI-18725
> URL: https://issues.apache.org/jira/browse/AMBARI-18725
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0, 2.4.2
>Reporter: Matt
>Assignee: Robert Levas
>Priority: Blocker
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-18725_branch-2.4_01.patch,
> AMBARI-18725_branch-2.5_01.patch, AMBARI-18725_trunk_01.patch
>
>
> Built Ambari from branch-2.4, branch-2.5 and trunk. All the builds have the
> same issue when the start command is run.
> {code}> ambari-server start
> Using python /usr/bin/python
> Starting ambari-server
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> No errors were found.
> ERROR: Exiting with exit code 1.
> REASON: Database check failed to complete. Please check
> /var/log/ambari-server/ambari-server.log and
> /var/log/ambari-server/ambari-server-check-database.log for more
> information.{code}
> The database.log says {code}Error preallocating sequence numbers{code}
> Nothing suspicious on ambari-server.log.
> Log file ambari-server-check-database.log attached with this JIRA for
> reference.
> *Update*
> Reverting
> https://github.com/apache/ambari/commit/b632b33bc35afc5a01354e8916fdcdf698e49e19
> on a local copy of branch-2.4 fixed the issue on branch-2.4 build
> Reverting
> https://github.com/apache/ambari/commit/49f58e8402b543875c61f8d74a052bd6cd45a788
> on a local copy of branch-2.5 fixed the issue on branch-2.5 build
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18751) Upgrade Fails From 2.4.2 to 2.5 Due To Existing Role Authorizations
[
https://issues.apache.org/jira/browse/AMBARI-18751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15625552#comment-15625552
]
Hadoop QA commented on AMBARI-18751:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836350/AMBARI-18751_trunk_01.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 2 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:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.controller.metrics.JMXPropertyProviderTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9079//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9079//console
This message is automatically generated.
> Upgrade Fails From 2.4.2 to 2.5 Due To Existing Role Authorizations
> ---
>
> Key: AMBARI-18751
> URL: https://issues.apache.org/jira/browse/AMBARI-18751
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Blocker
> Fix For: 2.4.2
>
> Attachments: AMBARI-18751_branch-2.4_01.patch,
> AMBARI-18751_branch-2.5_01.patch, AMBARI-18751_trunk_01.patch
>
>
> STR:
> - Install Ambari 2.4.2 (from branch-2.4)
> - Upgrade to Ambari 2.5.0
> The following exception fails the upgrade. It appears as though this is from
> [a recent
> commit|https://github.com/apache/ambari/commit/57116b774c62e5ff6ce22de70458e7c01cccdb07]
> into {{branch-2.4}}: AMBARI-18433
> When the upgrade runs, it assumes that the role authorizations need to be
> added. In existing 2.4.0 and 2.4.1 installations, this is true. But since
> this code is now in the 2.4 branch, 2.4.2+ installations will already have
> the required data seeded.
> {code}
> 2016-10-31 11:12:01,193 WARN [main] (Slf4jMLog.java:220) log() - [c3p0] A
> PooledConnection that has already signalled a Connection error is still in
> use!
> 2016-10-31 11:12:01,193 WARN [main] (Slf4jMLog.java:223) log() - [c3p0]
> Another error has occurred [ org.postgresql.util.PSQLException: ERROR:
> current transaction is aborted, commands ignored until end of transaction
> block ] which will not be reported to listeners!
> org.postgresql.util.PSQLException: ERROR: current transaction is aborted,
> commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2161)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1890)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:559)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:417)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:302)
> at
> com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeQuery(NewProxyPreparedStatement.java:353)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabasePlatform.wasFailureCommunicationBased(DatabasePlatform.java:2914)
> at
> org.eclipse.persistence.platform.server.ServerPlatformBase.wasFailureCommunicationBased(ServerPlatformBase.java:546)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.processExceptionForCommError(DatabaseAccessor.java:1616)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:900)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:964)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:633)
> at
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatch(ParameterizedSQLBatchWritingMechanism.java:149)
> at
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatchedStatements(ParameterizedSQLBatchWritingMechanism.java:134)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.writesCompleted(DatabaseAccessor.java:1845)
>
[jira] [Commented] (AMBARI-18762) Fix Karma test runner
[ https://issues.apache.org/jira/browse/AMBARI-18762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15625478#comment-15625478 ] Hudson commented on AMBARI-18762: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5900 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5900/]) AMBARI-18762 Fix Karma test runner (atkach) (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4697e4709bab87e5631e1d5db65720cec01e455f]) * (edit) ambari-web/karma.conf.js * (edit) ambari-web/package.json * (edit) ambari-web/test/views/common/quick_link_view_test.js > Fix Karma test runner > - > > Key: AMBARI-18762 > URL: https://issues.apache.org/jira/browse/AMBARI-18762 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-18762.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18757) DB configs consistency check failed after upgrade from 2.1.1 to 2.4.2 (stack 2.3)
[
https://issues.apache.org/jira/browse/AMBARI-18757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15625481#comment-15625481
]
Hudson commented on AMBARI-18757:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5900 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5900/])
AMBARI-18757. DB configs consistency check failed after upgrade from
(vbrodetskyi:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b89b9e1540b0ec539f62ee00d8bf82f1184f8af4])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog242.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog242Test.java
> DB configs consistency check failed after upgrade from 2.1.1 to 2.4.2 (stack
> 2.3)
> -
>
> Key: AMBARI-18757
> URL: https://issues.apache.org/jira/browse/AMBARI-18757
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.4.2
>
> Attachments: AMBARI-18757.patch
>
>
> 1)Install old version regarding env. (enable AD security)
> 2)Make ambari only upgrade
> Actual result:
> DB configs consistency check failed after upgrade from 2.1.1 to 2.4.2 (stack
> 2.3)
> {code}
> 2016-10-28 02:43:15,878 ERROR - Required config(s):
> storm-cluster-log4j,storm-worker-log4j is(are) not available for service
> STORM with service config version 4 in cluster cl1
> 2016-10-28 02:43:15,917 INFO - *** Check
> database completed ***
> 2016-10-28 02:47:01,109 INFO - *** Check
> database started ***
> 2016-10-28 02:47:12,523 INFO - Checking for configs not mapped to any cluster
> 2016-10-28 02:47:12,538 INFO - Checking for configs selected more than once
> 2016-10-28 02:47:12,541 INFO - Checking for hosts without state
> 2016-10-28 02:47:12,544 INFO - Checking host component states count equals
> host component desired states count
> 2016-10-28 02:47:12,548 INFO - Checking services and their configs
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / PIG
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / SPARK
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / MAPREDUCE2
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / YARN
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / FALCON
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / SLIDER
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / HIVE
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / TEZ
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / ZOOKEEPER
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / STORM
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / SQOOP
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / HBASE
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / OOZIE
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / FLUME
> 2016-10-28 02:47:17,675 INFO - Processing HDP-2.3 / KNOX
> 2016-10-28 02:47:17,675 INFO - Processing HDP-2.3 / KERBEROS
> 2016-10-28 02:47:17,675 INFO - Processing HDP-2.3 / HDFS
> 2016-10-28 02:47:17,675 INFO - Processing HDP-2.3 / AMBARI_METRICS
> 2016-10-28 02:47:17,682 ERROR - Required config(s): sqoop-site is(are) not
> available for service SQOOP with service config version 1 in cluster cl1
> 2016-10-28 02:47:17,682 ERROR - Required config(s):
> falcon-client.properties,falcon-log4j is(are) not available for service
> FALCON with service config version 3 in cluster cl1
> 2016-10-28 02:47:17,682 ERROR - Required config(s):
> spark-thrift-sparkconf,spark-hive-site-override is(are) not available for
> service SPARK with service config version 3 in cluster cl1
> 2016-10-28 02:47:17,682 ERROR - Required config(s):
> knoxsso-topology,admin-topology is(are) not available for service KNOX with
> service config version 3 in cluster cl1
> 2016-10-28 02:47:17,682 ERROR - Required config(s):
> ams-ssl-client,ams-ssl-server,ams-grafana-env,ams-grafana-ini is(are) not
> available for service AMBARI_METRICS with service config version 3 in cluster
> cl1
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18713) use exclude list of mount device types on docker containers
[ https://issues.apache.org/jira/browse/AMBARI-18713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-18713: - Attachment: AMBARI-18713.patch.1 > use exclude list of mount device types on docker containers > --- > > Key: AMBARI-18713 > URL: https://issues.apache.org/jira/browse/AMBARI-18713 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Dmytro Grinenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18713.patch, AMBARI-18713.patch.1 > > > * Remove logic from UI that picks a single host to represent the entire > cluster > * Have each host report their mount devices and how much space is available > in each one, so Ambari can store this in the DB (this will affect new > installs only or newly registered hosts) > * Move logic to Stack Advisor > * Use exclude list -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18751) Upgrade Fails From 2.4.2 to 2.5 Due To Existing Role Authorizations
[
https://issues.apache.org/jira/browse/AMBARI-18751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-18751:
--
Attachment: AMBARI-18751_trunk_01.patch
AMBARI-18751_branch-2.5_01.patch
AMBARI-18751_branch-2.4_01.patch
> Upgrade Fails From 2.4.2 to 2.5 Due To Existing Role Authorizations
> ---
>
> Key: AMBARI-18751
> URL: https://issues.apache.org/jira/browse/AMBARI-18751
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Blocker
> Fix For: 2.4.2
>
> Attachments: AMBARI-18751_branch-2.4_01.patch,
> AMBARI-18751_branch-2.5_01.patch, AMBARI-18751_trunk_01.patch
>
>
> STR:
> - Install Ambari 2.4.2 (from branch-2.4)
> - Upgrade to Ambari 2.5.0
> The following exception fails the upgrade. It appears as though this is from
> [a recent
> commit|https://github.com/apache/ambari/commit/57116b774c62e5ff6ce22de70458e7c01cccdb07]
> into {{branch-2.4}}: AMBARI-18433
> When the upgrade runs, it assumes that the role authorizations need to be
> added. In existing 2.4.0 and 2.4.1 installations, this is true. But since
> this code is now in the 2.4 branch, 2.4.2+ installations will already have
> the required data seeded.
> {code}
> 2016-10-31 11:12:01,193 WARN [main] (Slf4jMLog.java:220) log() - [c3p0] A
> PooledConnection that has already signalled a Connection error is still in
> use!
> 2016-10-31 11:12:01,193 WARN [main] (Slf4jMLog.java:223) log() - [c3p0]
> Another error has occurred [ org.postgresql.util.PSQLException: ERROR:
> current transaction is aborted, commands ignored until end of transaction
> block ] which will not be reported to listeners!
> org.postgresql.util.PSQLException: ERROR: current transaction is aborted,
> commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2161)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1890)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:559)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:417)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:302)
> at
> com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeQuery(NewProxyPreparedStatement.java:353)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabasePlatform.wasFailureCommunicationBased(DatabasePlatform.java:2914)
> at
> org.eclipse.persistence.platform.server.ServerPlatformBase.wasFailureCommunicationBased(ServerPlatformBase.java:546)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.processExceptionForCommError(DatabaseAccessor.java:1616)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:900)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:964)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:633)
> at
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatch(ParameterizedSQLBatchWritingMechanism.java:149)
> at
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatchedStatements(ParameterizedSQLBatchWritingMechanism.java:134)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.writesCompleted(DatabaseAccessor.java:1845)
> at
> org.eclipse.persistence.internal.sessions.AbstractSession.writesCompleted(AbstractSession.java:4300)
> at
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.writesCompleted(UnitOfWorkImpl.java:5592)
> at
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.acquireWriteLocks(UnitOfWorkImpl.java:1646)
> at
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitTransactionAfterWriteChanges(UnitOfWorkImpl.java:1614)
> at
> org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.commitRootUnitOfWork(RepeatableWriteUnitOfWork.java:285)
> at
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitAndResume(UnitOfWorkImpl.java:1169)
> at
> org.eclipse.persistence.internal.jpa.transaction.EntityTransactionImpl.commit(EntityTransactionImpl.java:134)
> at
>
[jira] [Updated] (AMBARI-18751) Upgrade Fails From 2.4.2 to 2.5 Due To Existing Role Authorizations
[
https://issues.apache.org/jira/browse/AMBARI-18751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-18751:
--
Status: Patch Available (was: In Progress)
> Upgrade Fails From 2.4.2 to 2.5 Due To Existing Role Authorizations
> ---
>
> Key: AMBARI-18751
> URL: https://issues.apache.org/jira/browse/AMBARI-18751
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Blocker
> Fix For: 2.4.2
>
> Attachments: AMBARI-18751_branch-2.4_01.patch,
> AMBARI-18751_branch-2.5_01.patch, AMBARI-18751_trunk_01.patch
>
>
> STR:
> - Install Ambari 2.4.2 (from branch-2.4)
> - Upgrade to Ambari 2.5.0
> The following exception fails the upgrade. It appears as though this is from
> [a recent
> commit|https://github.com/apache/ambari/commit/57116b774c62e5ff6ce22de70458e7c01cccdb07]
> into {{branch-2.4}}: AMBARI-18433
> When the upgrade runs, it assumes that the role authorizations need to be
> added. In existing 2.4.0 and 2.4.1 installations, this is true. But since
> this code is now in the 2.4 branch, 2.4.2+ installations will already have
> the required data seeded.
> {code}
> 2016-10-31 11:12:01,193 WARN [main] (Slf4jMLog.java:220) log() - [c3p0] A
> PooledConnection that has already signalled a Connection error is still in
> use!
> 2016-10-31 11:12:01,193 WARN [main] (Slf4jMLog.java:223) log() - [c3p0]
> Another error has occurred [ org.postgresql.util.PSQLException: ERROR:
> current transaction is aborted, commands ignored until end of transaction
> block ] which will not be reported to listeners!
> org.postgresql.util.PSQLException: ERROR: current transaction is aborted,
> commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2161)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1890)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:559)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:417)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:302)
> at
> com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeQuery(NewProxyPreparedStatement.java:353)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabasePlatform.wasFailureCommunicationBased(DatabasePlatform.java:2914)
> at
> org.eclipse.persistence.platform.server.ServerPlatformBase.wasFailureCommunicationBased(ServerPlatformBase.java:546)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.processExceptionForCommError(DatabaseAccessor.java:1616)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:900)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:964)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:633)
> at
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatch(ParameterizedSQLBatchWritingMechanism.java:149)
> at
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatchedStatements(ParameterizedSQLBatchWritingMechanism.java:134)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.writesCompleted(DatabaseAccessor.java:1845)
> at
> org.eclipse.persistence.internal.sessions.AbstractSession.writesCompleted(AbstractSession.java:4300)
> at
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.writesCompleted(UnitOfWorkImpl.java:5592)
> at
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.acquireWriteLocks(UnitOfWorkImpl.java:1646)
> at
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitTransactionAfterWriteChanges(UnitOfWorkImpl.java:1614)
> at
> org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.commitRootUnitOfWork(RepeatableWriteUnitOfWork.java:285)
> at
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitAndResume(UnitOfWorkImpl.java:1169)
> at
> org.eclipse.persistence.internal.jpa.transaction.EntityTransactionImpl.commit(EntityTransactionImpl.java:134)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:153)
> at
>
[jira] [Commented] (AMBARI-18748) ambari-server upgrade fail (from 2.2.2.0/2.4.0.0/2.4.0.1/2.4.1.0 to 2.4.2.0 )
[
https://issues.apache.org/jira/browse/AMBARI-18748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15625418#comment-15625418
]
Hudson commented on AMBARI-18748:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5899 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5899/])
AMBARI-18748. ambari-server upgrade fail (from (vbrodetskyi:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=917e4b8456f7c849914d0412457be0c86d031841])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog242.java
> ambari-server upgrade fail (from 2.2.2.0/2.4.0.0/2.4.0.1/2.4.1.0 to 2.4.2.0 )
> -
>
> Key: AMBARI-18748
> URL: https://issues.apache.org/jira/browse/AMBARI-18748
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.4.2
>
> Attachments: AMBARI-18748.patch
>
>
> 1)Install old version regarding env.
> 2)Make ambari only upgrade
> Actual result:
> ambari-server upgrade fell
> {code}
> 2016-10-28 01:20:19,601 ERROR
> com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
> *Command '[ambari-server upgrade --verbose, ]'
> failed with exitcode 11 ***
> 2016-10-28 01:20:19,603 INFO
> com.hw.ambari.ui.util.cluster_managers.UpgradeClusterManager.upgrade_schema():
> Result of ambari-server upgrade command:
> 2016-10-28 01:20:19,603 INFO
> com.hw.ambari.ui.util.cluster_managers.UpgradeClusterManager.upgrade_schema():
> [OUTPUT STREAM]
> Using python /usr/bin/python
> Upgrading ambari-server
> Updating properties in ambari.properties ...
> WARNING: Original file ambari-env.sh kept
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: No mpack replay logs found. Skipping replaying mpack commands
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Fixing database objects owner
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Ambari Server configured for MySQL. Confirm you have made a backup of the
> Ambari Server database [y/n] (y)? INFO: Loading properties from
> /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Upgrading database schema
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: AMBARI_SERVER_LIB is not set, using default /usr/lib/ambari-server
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: about to run command: /usr/lib/jvm/java-7-openjdk-amd64/bin/java -cp
> '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/mysql-connector-java.jar'
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper >
> /var/log/ambari-server/ambari-server.out 2>&1
> INFO: Return code from schema upgrade command, retcode = 1
> Error output from schema upgrade command:
> Exception in thread "main" org.apache.ambari.server.AmbariException: Entity
> must be managed to call remove:
> org.apache.ambari.server.orm.entities.PrincipalEntity@5e81dbde, try merging
> the detached and try the remove again.
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:240)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:356)
> Caused by: java.lang.IllegalArgumentException: Entity must be managed to call
> remove: org.apache.ambari.server.orm.entities.PrincipalEntity@5e81dbde, try
> merging the detached and try the remove again.
> at
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.performRemove(UnitOfWorkImpl.java:3578)
> at
> org.eclipse.persistence.internal.jpa.EntityManagerImpl.remove(EntityManagerImpl.java:574)
> at
> org.apache.ambari.server.orm.dao.PrincipalDAO.remove(PrincipalDAO.java:132)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:128)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog242.convertRolePrincipals(UpgradeCatalog242.java:213)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog242.executeDMLUpdates(UpgradeCatalog242.java:122)
> at
>
[jira] [Commented] (AMBARI-18729) Add PDF version of stack, extension and service definitions
[ https://issues.apache.org/jira/browse/AMBARI-18729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15625420#comment-15625420 ] Hudson commented on AMBARI-18729: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5899 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5899/]) AMBARI-18729 - Add PDF version of stack, extension and service (tthorpe: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2f57937ab43c564c5f1e0cc68fcb0373982f702f]) * (add) contrib/docs/Apache_Ambari_Stack_Definition.pdf > Add PDF version of stack, extension and service definitions > --- > > Key: AMBARI-18729 > URL: https://issues.apache.org/jira/browse/AMBARI-18729 > Project: Ambari > Issue Type: Documentation > Components: contrib >Affects Versions: 2.4.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe >Priority: Minor > Fix For: trunk, 2.5.0, 2.4.2 > > Attachments: Apache_Ambari_Stack_Definition.pdf > > > The document will consolidate all the stack related information from the > wiki. It will describe to users how to create a stack, extension or service > definition. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18760) ambari-server.pid might not be created
[
https://issues.apache.org/jira/browse/AMBARI-18760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15625419#comment-15625419
]
Hadoop QA commented on AMBARI-18760:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836330/AMBARI-18760.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/9076//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9076//console
This message is automatically generated.
> ambari-server.pid might not be created
> --
>
> Key: AMBARI-18760
> URL: https://issues.apache.org/jira/browse/AMBARI-18760
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.4.2
>
> Attachments: AMBARI-18760.patch
>
>
> /var/run/ambari-server/ambari-server.pid might not be created, but IOError
> not logged
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18757) DB configs consistency check failed after upgrade from 2.1.1 to 2.4.2 (stack 2.3)
[
https://issues.apache.org/jira/browse/AMBARI-18757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-18757:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk, branch-2.4, branch-2.5
> DB configs consistency check failed after upgrade from 2.1.1 to 2.4.2 (stack
> 2.3)
> -
>
> Key: AMBARI-18757
> URL: https://issues.apache.org/jira/browse/AMBARI-18757
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.4.2
>
> Attachments: AMBARI-18757.patch
>
>
> 1)Install old version regarding env. (enable AD security)
> 2)Make ambari only upgrade
> Actual result:
> DB configs consistency check failed after upgrade from 2.1.1 to 2.4.2 (stack
> 2.3)
> {code}
> 2016-10-28 02:43:15,878 ERROR - Required config(s):
> storm-cluster-log4j,storm-worker-log4j is(are) not available for service
> STORM with service config version 4 in cluster cl1
> 2016-10-28 02:43:15,917 INFO - *** Check
> database completed ***
> 2016-10-28 02:47:01,109 INFO - *** Check
> database started ***
> 2016-10-28 02:47:12,523 INFO - Checking for configs not mapped to any cluster
> 2016-10-28 02:47:12,538 INFO - Checking for configs selected more than once
> 2016-10-28 02:47:12,541 INFO - Checking for hosts without state
> 2016-10-28 02:47:12,544 INFO - Checking host component states count equals
> host component desired states count
> 2016-10-28 02:47:12,548 INFO - Checking services and their configs
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / PIG
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / SPARK
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / MAPREDUCE2
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / YARN
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / FALCON
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / SLIDER
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / HIVE
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / TEZ
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / ZOOKEEPER
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / STORM
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / SQOOP
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / HBASE
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / OOZIE
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / FLUME
> 2016-10-28 02:47:17,675 INFO - Processing HDP-2.3 / KNOX
> 2016-10-28 02:47:17,675 INFO - Processing HDP-2.3 / KERBEROS
> 2016-10-28 02:47:17,675 INFO - Processing HDP-2.3 / HDFS
> 2016-10-28 02:47:17,675 INFO - Processing HDP-2.3 / AMBARI_METRICS
> 2016-10-28 02:47:17,682 ERROR - Required config(s): sqoop-site is(are) not
> available for service SQOOP with service config version 1 in cluster cl1
> 2016-10-28 02:47:17,682 ERROR - Required config(s):
> falcon-client.properties,falcon-log4j is(are) not available for service
> FALCON with service config version 3 in cluster cl1
> 2016-10-28 02:47:17,682 ERROR - Required config(s):
> spark-thrift-sparkconf,spark-hive-site-override is(are) not available for
> service SPARK with service config version 3 in cluster cl1
> 2016-10-28 02:47:17,682 ERROR - Required config(s):
> knoxsso-topology,admin-topology is(are) not available for service KNOX with
> service config version 3 in cluster cl1
> 2016-10-28 02:47:17,682 ERROR - Required config(s):
> ams-ssl-client,ams-ssl-server,ams-grafana-env,ams-grafana-ini is(are) not
> available for service AMBARI_METRICS with service config version 3 in cluster
> cl1
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18762) Fix Karma test runner
[ https://issues.apache.org/jira/browse/AMBARI-18762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-18762: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Fix Karma test runner > - > > Key: AMBARI-18762 > URL: https://issues.apache.org/jira/browse/AMBARI-18762 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-18762.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18762) Fix Karma test runner
[ https://issues.apache.org/jira/browse/AMBARI-18762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15625379#comment-15625379 ] Andrii Tkach commented on AMBARI-18762: --- committed to trunk > Fix Karma test runner > - > > Key: AMBARI-18762 > URL: https://issues.apache.org/jira/browse/AMBARI-18762 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-18762.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18729) Add PDF version of stack, extension and service definitions
[ https://issues.apache.org/jira/browse/AMBARI-18729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15625375#comment-15625375 ] Hudson commented on AMBARI-18729: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #234 (See [https://builds.apache.org/job/Ambari-branch-2.5/234/]) AMBARI-18729 - Add PDF version of stack, extension and service (tthorpe: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0520416ed2bf798f36a710964d7511a7752dacb3]) * (add) contrib/docs/Apache_Ambari_Stack_Definition.pdf > Add PDF version of stack, extension and service definitions > --- > > Key: AMBARI-18729 > URL: https://issues.apache.org/jira/browse/AMBARI-18729 > Project: Ambari > Issue Type: Documentation > Components: contrib >Affects Versions: 2.4.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe >Priority: Minor > Fix For: trunk, 2.5.0, 2.4.2 > > Attachments: Apache_Ambari_Stack_Definition.pdf > > > The document will consolidate all the stack related information from the > wiki. It will describe to users how to create a stack, extension or service > definition. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18762) Fix Karma test runner
[
https://issues.apache.org/jira/browse/AMBARI-18762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15625361#comment-15625361
]
Hadoop QA commented on AMBARI-18762:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836332/AMBARI-18762.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:red}-1 core tests{color}. The test build failed in ambari-web
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9075//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9075//console
This message is automatically generated.
> Fix Karma test runner
> -
>
> Key: AMBARI-18762
> URL: https://issues.apache.org/jira/browse/AMBARI-18762
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-18762.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18748) ambari-server upgrade fail (from 2.2.2.0/2.4.0.0/2.4.0.1/2.4.1.0 to 2.4.2.0 )
[
https://issues.apache.org/jira/browse/AMBARI-18748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-18748:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk, branch-2.4, branch-2.5
> ambari-server upgrade fail (from 2.2.2.0/2.4.0.0/2.4.0.1/2.4.1.0 to 2.4.2.0 )
> -
>
> Key: AMBARI-18748
> URL: https://issues.apache.org/jira/browse/AMBARI-18748
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.4.2
>
> Attachments: AMBARI-18748.patch
>
>
> 1)Install old version regarding env.
> 2)Make ambari only upgrade
> Actual result:
> ambari-server upgrade fell
> {code}
> 2016-10-28 01:20:19,601 ERROR
> com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
> *Command '[ambari-server upgrade --verbose, ]'
> failed with exitcode 11 ***
> 2016-10-28 01:20:19,603 INFO
> com.hw.ambari.ui.util.cluster_managers.UpgradeClusterManager.upgrade_schema():
> Result of ambari-server upgrade command:
> 2016-10-28 01:20:19,603 INFO
> com.hw.ambari.ui.util.cluster_managers.UpgradeClusterManager.upgrade_schema():
> [OUTPUT STREAM]
> Using python /usr/bin/python
> Upgrading ambari-server
> Updating properties in ambari.properties ...
> WARNING: Original file ambari-env.sh kept
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: No mpack replay logs found. Skipping replaying mpack commands
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Fixing database objects owner
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Ambari Server configured for MySQL. Confirm you have made a backup of the
> Ambari Server database [y/n] (y)? INFO: Loading properties from
> /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Upgrading database schema
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: AMBARI_SERVER_LIB is not set, using default /usr/lib/ambari-server
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: about to run command: /usr/lib/jvm/java-7-openjdk-amd64/bin/java -cp
> '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/mysql-connector-java.jar'
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper >
> /var/log/ambari-server/ambari-server.out 2>&1
> INFO: Return code from schema upgrade command, retcode = 1
> Error output from schema upgrade command:
> Exception in thread "main" org.apache.ambari.server.AmbariException: Entity
> must be managed to call remove:
> org.apache.ambari.server.orm.entities.PrincipalEntity@5e81dbde, try merging
> the detached and try the remove again.
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:240)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:356)
> Caused by: java.lang.IllegalArgumentException: Entity must be managed to call
> remove: org.apache.ambari.server.orm.entities.PrincipalEntity@5e81dbde, try
> merging the detached and try the remove again.
> at
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.performRemove(UnitOfWorkImpl.java:3578)
> at
> org.eclipse.persistence.internal.jpa.EntityManagerImpl.remove(EntityManagerImpl.java:574)
> at
> org.apache.ambari.server.orm.dao.PrincipalDAO.remove(PrincipalDAO.java:132)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:128)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog242.convertRolePrincipals(UpgradeCatalog242.java:213)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog242.executeDMLUpdates(UpgradeCatalog242.java:122)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:908)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
> ... 1 more
> ERROR: Error executing schema upgrade, please check the server logs.
> ERROR: Ambari server upgrade failed. Please look at
>
