[jira] [Resolved] (AMBARI-24724) Remove ambari-metrics dependency on ambari-commons
[ https://issues.apache.org/jira/browse/AMBARI-24724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle resolved AMBARI-24724. -- Resolution: Fixed > Remove ambari-metrics dependency on ambari-commons > -- > > Key: AMBARI-24724 > URL: https://issues.apache.org/jira/browse/AMBARI-24724 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.2.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > > The unnecessary dep was added to support OS defaults and test functions > around windows supportability added a few years back. Since then the windows > support has not been supported by any developers and is no longer of any use. > We recently separated the metrics repo and this dep creates a circular build > time dependency. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24724) Remove ambari-metrics dependency on ambari-commons
[ https://issues.apache.org/jira/browse/AMBARI-24724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636429#comment-16636429 ] ASF GitHub Bot commented on AMBARI-24724: - asfgit commented on issue #4: AMBARI-24724. Remove ambari-metrics dependency on ambari-commons. URL: https://github.com/apache/ambari-metrics/pull/4#issuecomment-426512496 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ambari-Metrics-Github-PR-Builder/11/ Test PASSed. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Remove ambari-metrics dependency on ambari-commons > -- > > Key: AMBARI-24724 > URL: https://issues.apache.org/jira/browse/AMBARI-24724 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.2.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > > The unnecessary dep was added to support OS defaults and test functions > around windows supportability added a few years back. Since then the windows > support has not been supported by any developers and is no longer of any use. > We recently separated the metrics repo and this dep creates a circular build > time dependency. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24723) Support wild cards in AppId and InstanceId fields in AMS GET API.
[ https://issues.apache.org/jira/browse/AMBARI-24723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-24723: --- Status: Patch Available (was: Open) > Support wild cards in AppId and InstanceId fields in AMS GET API. > - > > Key: AMBARI-24723 > URL: https://issues.apache.org/jira/browse/AMBARI-24723 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.8.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24724) Remove ambari-metrics dependency on ambari-commons
[ https://issues.apache.org/jira/browse/AMBARI-24724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636423#comment-16636423 ] ASF GitHub Bot commented on AMBARI-24724: - asfgit commented on issue #4: AMBARI-24724. Remove ambari-metrics dependency on ambari-commons. URL: https://github.com/apache/ambari-metrics/pull/4#issuecomment-426511102 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ambari-Metrics-Github-PR-Builder/10/ Test PASSed. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Remove ambari-metrics dependency on ambari-commons > -- > > Key: AMBARI-24724 > URL: https://issues.apache.org/jira/browse/AMBARI-24724 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.2.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > > The unnecessary dep was added to support OS defaults and test functions > around windows supportability added a few years back. Since then the windows > support has not been supported by any developers and is no longer of any use. > We recently separated the metrics repo and this dep creates a circular build > time dependency. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24723) Support wild cards in AppId and InstanceId fields in AMS GET API.
[ https://issues.apache.org/jira/browse/AMBARI-24723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636419#comment-16636419 ] ASF GitHub Bot commented on AMBARI-24723: - asfgit commented on issue #5: [AMBARI-24723] Support wild cards in AppId and InstanceId fields in AMS GET API. URL: https://github.com/apache/ambari-metrics/pull/5#issuecomment-426509390 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ambari-Metrics-Github-PR-Builder/9/ Test PASSed. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Support wild cards in AppId and InstanceId fields in AMS GET API. > - > > Key: AMBARI-24723 > URL: https://issues.apache.org/jira/browse/AMBARI-24723 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.8.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24723) Support wild cards in AppId and InstanceId fields in AMS GET API.
[ https://issues.apache.org/jira/browse/AMBARI-24723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636407#comment-16636407 ] ASF GitHub Bot commented on AMBARI-24723: - avijayanhwx opened a new pull request #5: [AMBARI-24723] Support wild cards in AppId and InstanceId fields in AMS GET API. URL: https://github.com/apache/ambari-metrics/pull/5 ## What changes were proposed in this pull request? Add support for wildcards in appId and instanceId ## How was this patch tested? Manually tested. Added unit test. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Support wild cards in AppId and InstanceId fields in AMS GET API. > - > > Key: AMBARI-24723 > URL: https://issues.apache.org/jira/browse/AMBARI-24723 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.8.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24723) Support wild cards in AppId and InstanceId fields in AMS GET API.
[ https://issues.apache.org/jira/browse/AMBARI-24723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24723: Labels: pull-request-available (was: ) > Support wild cards in AppId and InstanceId fields in AMS GET API. > - > > Key: AMBARI-24723 > URL: https://issues.apache.org/jira/browse/AMBARI-24723 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.8.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24724) Remove ambari-metrics dependency on ambari-commons
[ https://issues.apache.org/jira/browse/AMBARI-24724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636354#comment-16636354 ] ASF GitHub Bot commented on AMBARI-24724: - asfgit commented on issue #4: AMBARI-24724. Remove ambari-metrics dependency on ambari-commons. URL: https://github.com/apache/ambari-metrics/pull/4#issuecomment-426492265 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ambari-Metrics-Github-PR-Builder/8/ Test PASSed. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Remove ambari-metrics dependency on ambari-commons > -- > > Key: AMBARI-24724 > URL: https://issues.apache.org/jira/browse/AMBARI-24724 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.2.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > > The unnecessary dep was added to support OS defaults and test functions > around windows supportability added a few years back. Since then the windows > support has not been supported by any developers and is no longer of any use. > We recently separated the metrics repo and this dep creates a circular build > time dependency. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24724) Remove ambari-metrics dependency on ambari-commons
[ https://issues.apache.org/jira/browse/AMBARI-24724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636303#comment-16636303 ] ASF GitHub Bot commented on AMBARI-24724: - asfgit commented on issue #4: AMBARI-24724. Remove ambari-metrics dependency on ambari-commons. URL: https://github.com/apache/ambari-metrics/pull/4#issuecomment-426477435 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ambari-Metrics-Github-PR-Builder/7/ Test FAILed. Test FAILured. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Remove ambari-metrics dependency on ambari-commons > -- > > Key: AMBARI-24724 > URL: https://issues.apache.org/jira/browse/AMBARI-24724 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.2.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > > The unnecessary dep was added to support OS defaults and test functions > around windows supportability added a few years back. Since then the windows > support has not been supported by any developers and is no longer of any use. > We recently separated the metrics repo and this dep creates a circular build > time dependency. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24724) Remove ambari-metrics dependency on ambari-commons
[ https://issues.apache.org/jira/browse/AMBARI-24724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24724: Labels: pull-request-available (was: ) > Remove ambari-metrics dependency on ambari-commons > -- > > Key: AMBARI-24724 > URL: https://issues.apache.org/jira/browse/AMBARI-24724 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.2.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > > The unnecessary dep was added to support OS defaults and test functions > around windows supportability added a few years back. Since then the windows > support has not been supported by any developers and is no longer of any use. > We recently separated the metrics repo and this dep creates a circular build > time dependency. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24724) Remove ambari-metrics dependency on ambari-commons
[ https://issues.apache.org/jira/browse/AMBARI-24724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636283#comment-16636283 ] ASF GitHub Bot commented on AMBARI-24724: - swagle opened a new pull request #4: AMBARI-24724. Remove ambari-metrics dependency on ambari-commons. URL: https://github.com/apache/ambari-metrics/pull/4 ## What changes were proposed in this pull request? The unnecessary dep was added to support OS defaults and test functions around windows supportability added a few years back. Since then the windows support has not been supported by any developers and is no longer of any use. We recently separated the metrics repo and this dep creates a circular build time dependency. ## How was this patch tested? Ran unit tests. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Remove ambari-metrics dependency on ambari-commons > -- > > Key: AMBARI-24724 > URL: https://issues.apache.org/jira/browse/AMBARI-24724 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.2.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > > The unnecessary dep was added to support OS defaults and test functions > around windows supportability added a few years back. Since then the windows > support has not been supported by any developers and is no longer of any use. > We recently separated the metrics repo and this dep creates a circular build > time dependency. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24724) Remove ambari-metrics dependency on ambari-commons
Siddharth Wagle created AMBARI-24724: Summary: Remove ambari-metrics dependency on ambari-commons Key: AMBARI-24724 URL: https://issues.apache.org/jira/browse/AMBARI-24724 Project: Ambari Issue Type: Task Components: ambari-metrics Affects Versions: 2.2.0 Reporter: Siddharth Wagle Assignee: Siddharth Wagle Fix For: 2.8.0 The unnecessary dep was added to support OS defaults and test functions around windows supportability added a few years back. Since then the windows support has not been supported by any developers and is no longer of any use. We recently separated the metrics repo and this dep creates a circular build time dependency. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-7656) Add support for Hbase REST API
[ https://issues.apache.org/jira/browse/AMBARI-7656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636251#comment-16636251 ] Felix Frank commented on AMBARI-7656: - Hi, I'd like to pick this up, but it cannot apply to trunk because since AMBARI-24446 this code is no longer maintained here. Are patches for 2.x still welcome at all? Where are these services maintained now? > Add support for Hbase REST API > -- > > Key: AMBARI-7656 > URL: https://issues.apache.org/jira/browse/AMBARI-7656 > Project: Ambari > Issue Type: New Feature >Reporter: Marcus Young >Priority: Major > Attachments: AMBARI-7656.patch, AMBARI-7656.patch, AMBARI-7656.patch, > AMBARI-7656.patch, AMBARI-7656.patch, hbase_restgatewayserver.py > > > There is currently no first-class Hbase REST API support out of the box for > Ambari. It would be nice to have it install as part of the setup, so that it > can be managed via Ganglia, and propagate to every node in a cluster. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24723) Support wild cards in AppId and InstanceId fields in AMS GET API.
Aravindan Vijayan created AMBARI-24723: -- Summary: Support wild cards in AppId and InstanceId fields in AMS GET API. Key: AMBARI-24723 URL: https://issues.apache.org/jira/browse/AMBARI-24723 Project: Ambari Issue Type: Task Components: ambari-metrics Affects Versions: 2.8.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24688) Backend changes for the newer version of AMS Grafana.
[ https://issues.apache.org/jira/browse/AMBARI-24688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-24688. Resolution: Fixed > Backend changes for the newer version of AMS Grafana. > - > > Key: AMBARI-24688 > URL: https://issues.apache.org/jira/browse/AMBARI-24688 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.8.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24562) Protect the ClusterConfig resource so that only authorized users may have read-only access the data
[
https://issues.apache.org/jira/browse/AMBARI-24562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-24562:
--
Description:
Protect the ClientConfig resource so that only authorized users may have
read-only access the data.
Users with the following permission should have read-only access:
* {{CLUSTER.VIEW_CONFIGS}}
* {{SERVICE.VIEW_CONFIGS}}
* {{HOST.VIEW_CONFIGS}}
These permissions should be allow for the following roles:
* {{AMBARI.ADMINISTRATOR}}
* {{CLUSTER.ADMINISTRATOR}}
* {{CLUSTER.OPERATOR}}
* {{SERVICE.ADMINISTRATOR}}
* {{SERVICE.OPERATOR}}
* {{CLUSTER.USER}}
Users with no role related to the cluster may not view the data.
Example REST API entry point:
{noformat}
GET
/api/v1/clusters/cl1/services/HDFS/components/HDFS_CLIENT?format=client_config_tar
{noformat}
was:
Protect the ClientConfig resource so that only authorized users may have
read-only access the data.
Users with the following permission should have read-only access:
* {{CLUSTER.VIEW_CONFIGS}}
* {{SERVICE.VIEW_CONFIGS}}
* {{HOST.VIEW_CONFIGS}}
These permissions should be allow for the following roles:
* {{AMBARI.ADMINISTRATOR}}
* {{CLUSTER.ADMINISTRATOR}}
* {{CLUSTER.OPERATOR}}
* {{SERVICE.ADMINISTRATOR}}
* {{SERVICE.OPERATOR}}
* {{CLUSTER.USER}}
Users with no role related to the cluster may not view the data.
> Protect the ClusterConfig resource so that only authorized users may have
> read-only access the data
> ---
>
> Key: AMBARI-24562
> URL: https://issues.apache.org/jira/browse/AMBARI-24562
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Labels: pull-request-available, rbac
> Fix For: 2.7.2
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Protect the ClientConfig resource so that only authorized users may have
> read-only access the data.
> Users with the following permission should have read-only access:
> * {{CLUSTER.VIEW_CONFIGS}}
> * {{SERVICE.VIEW_CONFIGS}}
> * {{HOST.VIEW_CONFIGS}}
> These permissions should be allow for the following roles:
> * {{AMBARI.ADMINISTRATOR}}
> * {{CLUSTER.ADMINISTRATOR}}
> * {{CLUSTER.OPERATOR}}
> * {{SERVICE.ADMINISTRATOR}}
> * {{SERVICE.OPERATOR}}
> * {{CLUSTER.USER}}
> Users with no role related to the cluster may not view the data.
> Example REST API entry point:
> {noformat}
> GET
> /api/v1/clusters/cl1/services/HDFS/components/HDFS_CLIENT?format=client_config_tar
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23288) stateWatcherClient should be closed upon return from OutputSolr#createSolrStateWatcher
[
https://issues.apache.org/jira/browse/AMBARI-23288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated AMBARI-23288:
Description:
{code}
CloudSolrClient stateWatcherClient = createSolrClient();
{code}
stateWatcherClient should be closed upon return from the method.
was:
{code}
CloudSolrClient stateWatcherClient = createSolrClient();
{code}
stateWatcherClient should be closed upon return from the method.
> stateWatcherClient should be closed upon return from
> OutputSolr#createSolrStateWatcher
> --
>
> Key: AMBARI-23288
> URL: https://issues.apache.org/jira/browse/AMBARI-23288
> Project: Ambari
> Issue Type: Bug
>Reporter: Ted Yu
>Priority: Minor
>
> {code}
> CloudSolrClient stateWatcherClient = createSolrClient();
> {code}
> stateWatcherClient should be closed upon return from the method.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24032) Ambari should be selective about which HBase components that need to be restarted
[ https://issues.apache.org/jira/browse/AMBARI-24032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-24032: Description: For hbase config changes that only involve hbase master, Ambari should explicitly say so after the change. One example of such config change is for hbase.master.loadbalancer.class and hbase.coprocessor.master.classes was: For hbase config changes that only involve hbase master, Ambari should explicitly say so after the change. One example of such config change is for hbase.master.loadbalancer.class and hbase.coprocessor.master.classes > Ambari should be selective about which HBase components that need to be > restarted > - > > Key: AMBARI-24032 > URL: https://issues.apache.org/jira/browse/AMBARI-24032 > Project: Ambari > Issue Type: Bug >Reporter: Ted Yu >Priority: Major > > For hbase config changes that only involve hbase master, Ambari should > explicitly say so after the change. > One example of such config change is for hbase.master.loadbalancer.class and > hbase.coprocessor.master.classes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24720) UI: Configure Rolling Restart Advanced Options
[ https://issues.apache.org/jira/browse/AMBARI-24720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636002#comment-16636002 ] Hudson commented on AMBARI-24720: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10187 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10187/]) [AMBARI-24720] UI: Configure Rolling Restart Advanced Options. (ishanbhatt.1989: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=2c18ebe5b45910cadb76ab4f6eae75d7067f7eda]) * (edit) ambari-web/app/styles/application.less * (edit) ambari-web/app/templates/common/service_restart.hbs * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/views/common/service_restart_view.js > UI: Configure Rolling Restart Advanced Options > -- > > Key: AMBARI-24720 > URL: https://issues.apache.org/jira/browse/AMBARI-24720 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24720) UI: Configure Rolling Restart Advanced Options
[ https://issues.apache.org/jira/browse/AMBARI-24720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-24720. -- Resolution: Fixed > UI: Configure Rolling Restart Advanced Options > -- > > Key: AMBARI-24720 > URL: https://issues.apache.org/jira/browse/AMBARI-24720 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24714) User aborted task reported as FAILED in Bgoperations
[
https://issues.apache.org/jira/browse/AMBARI-24714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24714:
Labels: pull-request-available (was: )
> User aborted task reported as FAILED in Bgoperations
>
>
> Key: AMBARI-24714
> URL: https://issues.apache.org/jira/browse/AMBARI-24714
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Attachments: abort_bg_operations.py
>
>
> User aborted task reported as FAILED in Bgoperations.
> 1. Install cluster with all services ( Including Druid)
> 2. Click on Stop all services
> 3. When BGoperations window is loaded, click on the abort button for the same
> task
> 4. The operation should be aborted and marked as Aborted with "Aborted by
> user" message in the sub tasks logs
> 5. But instead the operation is marked as failure.
> Failed task is Druid Coordinator Stop
> {code:java}
> "href":
> "https://ctr-e138-1518143905142-466827-01-02.hwx.site:8443/api/v1/clusters/cl1/requests/59/stages/0/tasks/756;,
> "Tasks": {
> "attempt_cnt": 1,
> "cluster_name": "cl1",
> "command": "STOP",
> "command_detail": "DRUID_COORDINATOR STOP",
> "end_time": 1536363316602,
> "error_log": "/var/lib/ambari-agent/data/errors-756.txt",
> "exit_code": 0,
> "host_name": "ctr-e138-1518143905142-466827-01-05.hwx.site",
> "id": 756,
> "ops_display_name": null,
> "output_log": "/var/lib/ambari-agent/data/output-756.txt",
> "request_id": 59,
> "role": "DRUID_COORDINATOR",
> "stage_id": 0,
> "start_time": 1536363307548,
> "status": "FAILED",
> "stderr": "\nCommand aborted. Reason: 'Aborted by user'",
> "stdout": "\nCommand aborted. Reason: 'Aborted by user'\n\nCommand failed
> after 1 tries\n",
> "structured_out": {}
> }{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24721) Use maven docker plugin to build infra solr images
[ https://issues.apache.org/jira/browse/AMBARI-24721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-24721. --- Resolution: Fixed > Use maven docker plugin to build infra solr images > -- > > Key: AMBARI-24721 > URL: https://issues.apache.org/jira/browse/AMBARI-24721 > Project: Ambari > Issue Type: Task > Components: ambari-infra >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22618) User should be able to install Yarn DNS server using "+Add" utility from Host page
[ https://issues.apache.org/jira/browse/AMBARI-22618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16635570#comment-16635570 ] Hudson commented on AMBARI-22618: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10186 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10186/]) AMBARI-22618. New daemon is not shown on Ambari UI even though added in (aantonenko: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=5badc121ab128a536f0967e606259d0026ecc9af]) * (edit) ambari-web/app/models/stack_service_component.js * (edit) ambari-web/test/models/stack_service_component_test.js > User should be able to install Yarn DNS server using "+Add" utility from Host > page > -- > > Key: AMBARI-22618 > URL: https://issues.apache.org/jira/browse/AMBARI-22618 > Project: Ambari > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Yesha Vora >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Time Spent: 1h > Remaining Estimate: 0h > > Scenario: > Install Yarn component without selecting "Yarn DNS registry" > After installation, go to Host page and click on +ADD. > Yarn DNS registry service option should be present to allow the user to add > the service to host. > Currently, Yarn DNS registry service can not be ADDED to host directly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24702) Cover alert_instances_popup view
[ https://issues.apache.org/jira/browse/AMBARI-24702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16635536#comment-16635536 ] Hudson commented on AMBARI-24702: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10185 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10185/]) AMBARI-24702. Cover alert_instances_popup view (aantonenko: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=10de300e4c33a298f2aacee078ddbaabb83956e6]) * (edit) ambari-web/app/assets/test/tests.js * (add) ambari-web/test/views/main/alerts/alert_instances_popup_view_test.js > Cover alert_instances_popup view > > > Key: AMBARI-24702 > URL: https://issues.apache.org/jira/browse/AMBARI-24702 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-22618) User should be able to install Yarn DNS server using "+Add" utility from Host page
[ https://issues.apache.org/jira/browse/AMBARI-22618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander resolved AMBARI-22618. -- Resolution: Fixed Committed to trunk > User should be able to install Yarn DNS server using "+Add" utility from Host > page > -- > > Key: AMBARI-22618 > URL: https://issues.apache.org/jira/browse/AMBARI-22618 > Project: Ambari > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Yesha Vora >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Time Spent: 1h > Remaining Estimate: 0h > > Scenario: > Install Yarn component without selecting "Yarn DNS registry" > After installation, go to Host page and click on +ADD. > Yarn DNS registry service option should be present to allow the user to add > the service to host. > Currently, Yarn DNS registry service can not be ADDED to host directly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-22618) User should be able to install Yarn DNS server using "+Add" utility from Host page
[ https://issues.apache.org/jira/browse/AMBARI-22618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-22618: Assignee: Antonenko Alexander > User should be able to install Yarn DNS server using "+Add" utility from Host > page > -- > > Key: AMBARI-22618 > URL: https://issues.apache.org/jira/browse/AMBARI-22618 > Project: Ambari > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Yesha Vora >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Time Spent: 1h > Remaining Estimate: 0h > > Scenario: > Install Yarn component without selecting "Yarn DNS registry" > After installation, go to Host page and click on +ADD. > Yarn DNS registry service option should be present to allow the user to add > the service to host. > Currently, Yarn DNS registry service can not be ADDED to host directly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24702) Cover alert_instances_popup view
[ https://issues.apache.org/jira/browse/AMBARI-24702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-24702: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Cover alert_instances_popup view > > > Key: AMBARI-24702 > URL: https://issues.apache.org/jira/browse/AMBARI-24702 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22618) User should be able to install Yarn DNS server using "+Add" utility from Host page
[ https://issues.apache.org/jira/browse/AMBARI-22618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22618: Labels: pull-request-available (was: ) > User should be able to install Yarn DNS server using "+Add" utility from Host > page > -- > > Key: AMBARI-22618 > URL: https://issues.apache.org/jira/browse/AMBARI-22618 > Project: Ambari > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Yesha Vora >Priority: Critical > Labels: pull-request-available > > Scenario: > Install Yarn component without selecting "Yarn DNS registry" > After installation, go to Host page and click on +ADD. > Yarn DNS registry service option should be present to allow the user to add > the service to host. > Currently, Yarn DNS registry service can not be ADDED to host directly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24722) Failed to force_non_member_install a stack version on hosts
Myroslav Papirkovskyi created AMBARI-24722:
--
Summary: Failed to force_non_member_install a stack version on
hosts
Key: AMBARI-24722
URL: https://issues.apache.org/jira/browse/AMBARI-24722
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Myroslav Papirkovskyi
Assignee: Myroslav Papirkovskyi
Fix For: 2.8.0
The ability to pre-install packages on hosts (before being added to the
cluster) using the following API request is broken:
{noformat}
$ curl -X POST -d '\{ "HostStackVersions": { "repository_version":
, "stack": "HDP", "version": "2.6", "cluster_name": "TEST",
"force_non_member_install": true, "components": [ { "name" : "ZOOKEEPER_SERVER"
}, \{ "name": "ZOOKEEPER_CLIENT" } ] } }'
http://localhost:8080/api/v1/hosts/${hostname}/stack_versions
{noformat}
{noformat:title=ambari-agent.log}
ERROR 2018-06-19 08:54:08,222 CustomServiceOrchestrator.py:448 - Caught an
exception while executing custom service command: :
'Host_Level_Params for cluster_id=2 is missing. Check if server sent it.';
'Host_Level_Params for cluster_id=2 is missing. Check if server sent it.'
Traceback (most recent call last):
File "/usr/lib/ambari-agent/lib/ambari_agent/CustomServiceOrchestrator.py",
line 322, in runCommand
command = self.generate_command(command_header)
File "/usr/lib/ambari-agent/lib/ambari_agent/CustomServiceOrchestrator.py",
line 487, in generate_command
command_dict = self.configuration_builder.get_configuration(cluster_id,
service_name, component_name, required_config_timestamp)
File "/usr/lib/ambari-agent/lib/ambari_agent/ConfigurationBuilder.py", line
38, in get_configuration
host_level_params_cache = self.host_level_params_cache[cluster_id]
File "/usr/lib/ambari-agent/lib/ambari_agent/ClusterCache.py", line 155, in
__getitem__
raise KeyError("{0} for cluster_id={1} is missing. Check if server sent
it.".format(self.get_cache_name().title(), key))
KeyError: 'Host_Level_Params for cluster_id=2 is missing. Check if server sent
it.'
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24721) Use maven docker plugin to build infra solr images
[ https://issues.apache.org/jira/browse/AMBARI-24721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16635184#comment-16635184 ] Hudson commented on AMBARI-24721: - SUCCESS: Integrated in Jenkins build Ambari-Infra-master-Commit #4 (See [https://builds.apache.org/job/Ambari-Infra-master-Commit/4/]) AMBARI-24721. Use maven docker plugin to build infra solr images (#1) (github: [https://gitbox.apache.org/repos/asf?p=ambari-infra.git=commit=12bc5391d8cea0ceb02cde07f3b396d6ad29b59d]) * (edit) .gitignore * (add) Makefile * (edit) ambari-infra-manager-it/pom.xml * (add) jenkins/containers/docker-infra-solr/conf/solr.xml * (add) jenkins/containers/docker-infra-solr/bin/init.sh * (edit) ambari-infra-assembly/pom.xml * (add) jenkins/containers/docker-infra-solr/Dockerfile * (add) jenkins/containers/docker-infra-solr/bin/entrypoint.sh * (edit) pom.xml * (add) jenkins/containers/docker-infra-solr/conf/infra-solr.conf > Use maven docker plugin to build infra solr images > -- > > Key: AMBARI-24721 > URL: https://issues.apache.org/jira/browse/AMBARI-24721 > Project: Ambari > Issue Type: Task > Components: ambari-infra >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24721) Use maven docker plugin to build infra solr images
[ https://issues.apache.org/jira/browse/AMBARI-24721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16635182#comment-16635182 ] ASF GitHub Bot commented on AMBARI-24721: - oleewere closed pull request #1: AMBARI-24721. Use maven docker plugin to build infra solr images URL: https://github.com/apache/ambari-infra/pull/1 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Use maven docker plugin to build infra solr images > -- > > Key: AMBARI-24721 > URL: https://issues.apache.org/jira/browse/AMBARI-24721 > Project: Ambari > Issue Type: Task > Components: ambari-infra >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24721) Use maven docker plugin to build infra solr images
[ https://issues.apache.org/jira/browse/AMBARI-24721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16635166#comment-16635166 ] ASF GitHub Bot commented on AMBARI-24721: - asfgit commented on issue #1: AMBARI-24721. Use maven docker plugin to build infra solr images URL: https://github.com/apache/ambari-infra/pull/1#issuecomment-426197268 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ambari-Infra-Github-PR-Builder/1/ Test PASSed. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Use maven docker plugin to build infra solr images > -- > > Key: AMBARI-24721 > URL: https://issues.apache.org/jira/browse/AMBARI-24721 > Project: Ambari > Issue Type: Task > Components: ambari-infra >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24721) Use maven docker plugin to build infra solr images
[ https://issues.apache.org/jira/browse/AMBARI-24721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16635164#comment-16635164 ] ASF GitHub Bot commented on AMBARI-24721: - oleewere opened a new pull request #1: AMBARI-24721. Use maven docker plugin to build infra solr images URL: https://github.com/apache/ambari-infra/pull/1 ## What changes were proposed in this pull request? Use maven docker plugin to build and publish images. Add Makefile for builds Additional fix: use right metrics version for deb/rpm install ## How was this patch tested? Manually and on jenkins Please review @g-boros @kasakrisz This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Use maven docker plugin to build infra solr images > -- > > Key: AMBARI-24721 > URL: https://issues.apache.org/jira/browse/AMBARI-24721 > Project: Ambari > Issue Type: Task > Components: ambari-infra >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24721) Use maven docker plugin to build infra solr images
[ https://issues.apache.org/jira/browse/AMBARI-24721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24721: Labels: pull-request-available (was: ) > Use maven docker plugin to build infra solr images > -- > > Key: AMBARI-24721 > URL: https://issues.apache.org/jira/browse/AMBARI-24721 > Project: Ambari > Issue Type: Task > Components: ambari-infra >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24721) Use maven docker plugin to build infra solr images
Olivér Szabó created AMBARI-24721: - Summary: Use maven docker plugin to build infra solr images Key: AMBARI-24721 URL: https://issues.apache.org/jira/browse/AMBARI-24721 Project: Ambari Issue Type: Task Components: ambari-infra Affects Versions: 2.7.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
