[jira] [Commented] (AMBARI-21843) Database consistency check fails after upgrade to ambari 2.6.0
[ https://issues.apache.org/jira/browse/AMBARI-21843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16146376#comment-16146376 ] Hudson commented on AMBARI-21843: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7959 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7959/]) AMBARI-21843. Database consistency check fails after upgrade to ambari (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1c506ff7da1dc1763bc24a7665077cf920b4a2bc]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelper.java > Database consistency check fails after upgrade to ambari 2.6.0 > -- > > Key: AMBARI-21843 > URL: https://issues.apache.org/jira/browse/AMBARI-21843 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21843.patch > > > Here we need to fix two issues: > 1) Table "clusterconfigmapping" was removed in ambari-2.6.0 (dropping it > during upgrade). But db consistency check still using this table to get some > data. After upgrade it fails because "clusterconfigmapping" doesn't exist. > Need to reimplement checks which are using this table. > 2) Db consistency check doesn't show any information for user about errors, > in casse when table doesn't exist. You can check that with > "clusterconfigmapping" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21847) Refactor stack version column view
[
https://issues.apache.org/jira/browse/AMBARI-21847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16146368#comment-16146368
]
Hadoop QA commented on AMBARI-21847:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12884319/AMBARI-21847_trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12100//console
This message is automatically generated.
> Refactor stack version column view
> --
>
> Key: AMBARI-21847
> URL: https://issues.apache.org/jira/browse/AMBARI-21847
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.6.0
>
> Attachments: AMBARI-21847.patch, AMBARI-21847_trunk.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-13901) CLONE - The definition and hadling of hadoop-env should not be restrictive to HDFS
[ https://issues.apache.org/jira/browse/AMBARI-13901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty reassigned AMBARI-13901: -- Assignee: (was: Sumit Mohanty) > CLONE - The definition and hadling of hadoop-env should not be restrictive to > HDFS > -- > > Key: AMBARI-13901 > URL: https://issues.apache.org/jira/browse/AMBARI-13901 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.1.0 >Reporter: Nathan Falk > Fix For: trunk > > > This defect is cloned from AMBARI-12851. Here is the original description: > Hadoop Env configuration defined at the stack level is managed only if HDFS > service is slected as part of the deployment. If HDFS is disabled and any > alternate FS includes hadoop-env in the stack, the configuration should be > understood by the Ambari code and corresponding hadoop-env.sh should be > created properly on the hadoop/ambari agent machines. > I do not believe that the issue has been fully addressed by AMBARI-12837. > If a filesystem service is replacing HDFS, then it has to manage the > core-site and hadoop-env configurations, and possibly hdfs-site as well. Many > of these properties are defined in site_properties.js, but are defined as > having a 'serviceName' of 'HDFS'. When it comes time for Ambari to display > these properties in the UI, they get left out. This is true both on the > customize services page of the installation wizard and on the Configs tab for > the HCFS service. > On installation, anything that the HCFS service has defined in the stack in > core-site.xml, hdfs-site.xml or hadoop-env.xml does get saved to the > database, even if some of the properties do not appear on the Customize > Services page. > However, if the admin tries to change any properties later (for example, the > hadoop-env.sh content), then only those properties which are displayed by the > UI, which are those properties that are NOT defined in site_properties.js, > are saved. > The issue seems to be in these areas of the code, all in > ambari-web/app/utils/config.js: > mergePredefinedWithSaved > mergePredefinedWithLoaded > serviceConfigUiAttributes > All 3 of these functions will set 'serviceName' in the serviceConfigObj to > the serviceName from the pre-defined config properties in configsPropertyDef. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-13163) check_fs_root for HIVE service should also support HCFS type
[ https://issues.apache.org/jira/browse/AMBARI-13163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty reassigned AMBARI-13163: -- Assignee: (was: Sumit Mohanty) > check_fs_root for HIVE service should also support HCFS type > > > Key: AMBARI-13163 > URL: https://issues.apache.org/jira/browse/AMBARI-13163 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Vijay Srinivasaraghavan > Fix For: 2.3.0 > > > check_fs_root includes the logic to modify the FS path when it changes. The > current implementation only supports it for hdfs. Instead of filtering the FS > root by "hdfs", the value should be read from cluster-env for any HCFS type > to identify the FS namespace or it could simple tokenize DefaultFS and find > string before "://". -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-12293) Allow auto execution of command/task at specific life cycle stages of a cluster
[ https://issues.apache.org/jira/browse/AMBARI-12293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved AMBARI-12293. Resolution: Won't Fix > Allow auto execution of command/task at specific life cycle stages of a > cluster > --- > > Key: AMBARI-12293 > URL: https://issues.apache.org/jira/browse/AMBARI-12293 > Project: Ambari > Issue Type: Task > Components: ambari-server, stacks >Affects Versions: 2.1.0 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty >Priority: Critical > Fix For: 2.3.0 > > > During cluster creation (or add hosts), especially in the hosted clusters in > cloud environment, it is a requirement to execute tasks/commands at specific > life-cycle stages. > Samples of such stages are: > * pre-install - before any components are installed > * post-install - after all components are installed > * pre-start - before starting any components > * post-start - after all starts are complete > These tasks are generally expected to be executed for each host and at least > once. It is expected that these tasks be auto-executed. In addition if these > tasks fail it may result in fast fail - aborting any other tasks following > these. > Samples of such tasks are - > * perform host level setup (create local users, files, and folders) > * perform custom health checks > To support auto-execution, it is also necessary to allow saved configuration > for the tasks being auto-executed. > While it may not be necessary, it will be good to allow execution of the > above tasks at any other time through explicit API calls. > Ambari today has support for custom command/action. Custom actions can be > defined as stand alone tasks that can be invoked anytime through APIs. Custom > commands are commands associated with specific services. The design of this > feature should take into account the existing capabilities. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21793) Add support for variables used by Knox topology template
[ https://issues.apache.org/jira/browse/AMBARI-21793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-21793: --- Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to branch-2.5 as well. > Add support for variables used by Knox topology template > > > Key: AMBARI-21793 > URL: https://issues.apache.org/jira/browse/AMBARI-21793 > Project: Ambari > Issue Type: Bug >Reporter: Sandeep More >Assignee: Sandeep More > Fix For: 2.5.3, 2.6.0 > > Attachments: AMBARI-21793.001.patch > > > Currently Knox template within Ambari uses some hardcoded values such as http > schemes, this bug is to add variables which would would make Knox template > within Ambari more dynamic. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21793) Add support for variables used by Knox topology template
[ https://issues.apache.org/jira/browse/AMBARI-21793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-21793: --- Fix Version/s: 2.5.3 > Add support for variables used by Knox topology template > > > Key: AMBARI-21793 > URL: https://issues.apache.org/jira/browse/AMBARI-21793 > Project: Ambari > Issue Type: Bug >Reporter: Sandeep More >Assignee: Sandeep More > Fix For: 2.5.3, 2.6.0 > > Attachments: AMBARI-21793.001.patch > > > Currently Knox template within Ambari uses some hardcoded values such as http > schemes, this bug is to add variables which would would make Knox template > within Ambari more dynamic. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21821) Update Ambari Metrics service check to support HTTP SPNEGO authentication
[
https://issues.apache.org/jira/browse/AMBARI-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16146329#comment-16146329
]
Hadoop QA commented on AMBARI-21821:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12884327/AMBARI-21821.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12099//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12099//console
This message is automatically generated.
> Update Ambari Metrics service check to support HTTP SPNEGO authentication
> -
>
> Key: AMBARI-21821
> URL: https://issues.apache.org/jira/browse/AMBARI-21821
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: trunk
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: trunk
>
> Attachments: AMBARI-21821.patch
>
>
> This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to
> authenticate".
> In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari
> Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But
> Ambari Metrics service check currently does not support Kerberos HTTP SPNEGO
> authentication.
> 2017-08-24 16:13:44,078 - Ambari Metrics service check was started.
> 2017-08-24 16:13:44,109 - Generated metrics for host amshost.example.com :
> {
> "metrics": [
> {
> "metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
> "appid": "amssmoketestfake",
> "hostname": "host.example.com",
> "timestamp": 1503616424000,
> "starttime": 1503616424000,
> "metrics": {
> "1503616424000": 0.164134766408,
> "1503616425000": 1503616424000
> }
> }
> ]
> }
> 2017-08-24 16:13:44,114 - Connecting (POST) to
> amshost.example.com:6188/ws/v1/timeline/metrics/
> 2017-08-24 16:13:44,117 - Http response for host amshost.example.com: 401
> Authentication required
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21843) Database consistency check fails after upgrade to ambari 2.6.0
[ https://issues.apache.org/jira/browse/AMBARI-21843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-21843: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.6 > Database consistency check fails after upgrade to ambari 2.6.0 > -- > > Key: AMBARI-21843 > URL: https://issues.apache.org/jira/browse/AMBARI-21843 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21843.patch > > > Here we need to fix two issues: > 1) Table "clusterconfigmapping" was removed in ambari-2.6.0 (dropping it > during upgrade). But db consistency check still using this table to get some > data. After upgrade it fails because "clusterconfigmapping" doesn't exist. > Need to reimplement checks which are using this table. > 2) Db consistency check doesn't show any information for user about errors, > in casse when table doesn't exist. You can check that with > "clusterconfigmapping" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21569) Users randomly getting "HDFS020 Could not write file" exceptions while running query from Hive View
[
https://issues.apache.org/jira/browse/AMBARI-21569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16146325#comment-16146325
]
Hudson commented on AMBARI-21569:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7958 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7958/])
Revert "AMBARI-21569.Users randomly getting "HDFS020 Could not write (smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6848c8f4f1a162cbc99b632a4285fc5b579bab40])
* (edit)
contrib/views/utils/src/main/java/org/apache/ambari/view/utils/hdfs/HdfsUtil.java
* (edit)
contrib/views/utils/src/main/java/org/apache/ambari/view/utils/hdfs/HdfsApi.java
* (edit) contrib/views/hive20/src/main/resources/ui/yarn.lock
> Users randomly getting "HDFS020 Could not write file" exceptions while
> running query from Hive View
> ---
>
> Key: AMBARI-21569
> URL: https://issues.apache.org/jira/browse/AMBARI-21569
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Gaurav Nagar
>Assignee: venkat
> Fix For: 2.6.0
>
> Attachments: AMBARI-21569.branch-2.5.patch, AMBARI-21569-trunk.patch
>
>
> Running queries from Hive View are reporting intermittent issues with the
> Hive view. They get the exceptions as reported below
> {code:java}
> ServiceFormattedException:100 -
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS020 Could not write
> file /user/user/hive/jobs/hive-job-5290-2017-03-22_02-35/logs
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS020 Could not write
> file /user/user/hive/jobs/hive-job-5290-2017-03-22_02-35/logs
> at
> org.apache.ambari.view.utils.hdfs.HdfsUtil.putStringToFile(HdfsUtil.java:51)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobControllerImpl.updateOperationLogs(JobControllerImpl.java:202)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobControllerImpl.update(JobControllerImpl.java:160)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobResourceManager.read(JobResourceManager.java:79)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobResourceManager.readController(JobResourceManager.java:95)
> at
> org.apache.ambari.view.hive.resources.jobs.JobService.getOne(JobService.java:133)
> at sun.reflect.GeneratedMethodAccessor191.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at
>
[jira] [Commented] (AMBARI-21843) Database consistency check fails after upgrade to ambari 2.6.0
[ https://issues.apache.org/jira/browse/AMBARI-21843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16146309#comment-16146309 ] Hudson commented on AMBARI-21843: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #81 (See [https://builds.apache.org/job/Ambari-branch-2.6/81/]) AMBARI-21843. Database consistency check fails after upgrade to ambari (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=43432ae30355765fbf982553d7360aa00d7534e1]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelperTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelper.java > Database consistency check fails after upgrade to ambari 2.6.0 > -- > > Key: AMBARI-21843 > URL: https://issues.apache.org/jira/browse/AMBARI-21843 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21843.patch > > > Here we need to fix two issues: > 1) Table "clusterconfigmapping" was removed in ambari-2.6.0 (dropping it > during upgrade). But db consistency check still using this table to get some > data. After upgrade it fails because "clusterconfigmapping" doesn't exist. > Need to reimplement checks which are using this table. > 2) Db consistency check doesn't show any information for user about errors, > in casse when table doesn't exist. You can check that with > "clusterconfigmapping" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21849) Clean up repo_version table during mpack delete, add create validation for mpacks
Madhuvanthi Radhakrishnan created AMBARI-21849: -- Summary: Clean up repo_version table during mpack delete, add create validation for mpacks Key: AMBARI-21849 URL: https://issues.apache.org/jira/browse/AMBARI-21849 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Madhuvanthi Radhakrishnan Assignee: Madhuvanthi Radhakrishnan Fix For: 3.0.0 *Register Mpack API throws NPE when mpack defined in the registry is unavailable in mpack-repo.* 1. Register mpack registry with an invalid mpackUrl (which does not point to a Mpack) 2. Try to create a Mpack using register Mpack API 3. API should fail with valid error message stating invalid/unreachable mpackUrl, but fails with 500 server error. *Delete Mpack API failing with 500 server error (foreign key constraint violation error) on a failed deploy cluster* Scenario Cluster is deployed but "Install, Test, Start" step fails. User issues DELETE /cluster using API Root Cause Since we are far ahead in the deployment process, entries are made to number of tables that references the stack namely -extensionlink -clusters -clusterconfig -serviceconfig -clusterstate -repo_version -blueprint Of these, the DELETE /cluster clears up entries from all the tables referencing stacks except for repo_version. When user issues DELETE /mpacks after this, a call is made to remove the entry from the stack table but it still has a reference in the repo_version table due to which we get referential integrity error. Fix Before we delete an mpack we have the following checks - -Whether any clusters are deployed (To be relaxed in future) -If there is a stack entry that has current_mpack_id = mpack_id (delete candidate) Based on this, we will delete the repo_version entry for the above stack_id safely. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-21231) Mpack Processing Engine
[ https://issues.apache.org/jira/browse/AMBARI-21231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan resolved AMBARI-21231. Resolution: Fixed > Mpack Processing Engine > --- > > Key: AMBARI-21231 > URL: https://issues.apache.org/jira/browse/AMBARI-21231 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 3.0.0 > > > Download and extract mpack > Power the stacks apis -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21737) Ambari should expose whether a service is able to rolling-restart instead of hard coding service name
[ https://issues.apache.org/jira/browse/AMBARI-21737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan updated AMBARI-21737: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari should expose whether a service is able to rolling-restart instead of > hard coding service name > - > > Key: AMBARI-21737 > URL: https://issues.apache.org/jira/browse/AMBARI-21737 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Attachments: AMBARI-21737.patch > > > Add a new property rollingRestartSupported to component in the metainfo.xml > file. This property can be used to decide whether the component supports > rolling restart. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21569) Users randomly getting "HDFS020 Could not write file" exceptions while running query from Hive View
[
https://issues.apache.org/jira/browse/AMBARI-21569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16146201#comment-16146201
]
Hudson commented on AMBARI-21569:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #80 (See
[https://builds.apache.org/job/Ambari-branch-2.6/80/])
Revert "AMBARI-21569.Users randomly getting "HDFS020 Could not write (smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=63989a2d635e9bcfcf5034d8dbbaaa644b42032a])
* (edit) contrib/views/hive20/src/main/resources/ui/yarn.lock
* (edit)
contrib/views/utils/src/main/java/org/apache/ambari/view/utils/hdfs/HdfsApi.java
* (edit)
contrib/views/utils/src/main/java/org/apache/ambari/view/utils/hdfs/HdfsUtil.java
> Users randomly getting "HDFS020 Could not write file" exceptions while
> running query from Hive View
> ---
>
> Key: AMBARI-21569
> URL: https://issues.apache.org/jira/browse/AMBARI-21569
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Gaurav Nagar
>Assignee: venkat
> Fix For: 2.6.0
>
> Attachments: AMBARI-21569.branch-2.5.patch, AMBARI-21569-trunk.patch
>
>
> Running queries from Hive View are reporting intermittent issues with the
> Hive view. They get the exceptions as reported below
> {code:java}
> ServiceFormattedException:100 -
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS020 Could not write
> file /user/user/hive/jobs/hive-job-5290-2017-03-22_02-35/logs
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS020 Could not write
> file /user/user/hive/jobs/hive-job-5290-2017-03-22_02-35/logs
> at
> org.apache.ambari.view.utils.hdfs.HdfsUtil.putStringToFile(HdfsUtil.java:51)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobControllerImpl.updateOperationLogs(JobControllerImpl.java:202)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobControllerImpl.update(JobControllerImpl.java:160)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobResourceManager.read(JobResourceManager.java:79)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobResourceManager.readController(JobResourceManager.java:95)
> at
> org.apache.ambari.view.hive.resources.jobs.JobService.getOne(JobService.java:133)
> at sun.reflect.GeneratedMethodAccessor191.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at
>
[jira] [Updated] (AMBARI-21824) Make services as sub-resource of ServiceGroups and use Servicegroup while doing Creation, Update and retrieval of HostComponents and ServiceComponents.
[
https://issues.apache.org/jira/browse/AMBARI-21824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-21824:
-
Attachment: AMBARI-21824.1.patch
> Make services as sub-resource of ServiceGroups and use Servicegroup while
> doing Creation, Update and retrieval of HostComponents and ServiceComponents.
> ---
>
> Key: AMBARI-21824
> URL: https://issues.apache.org/jira/browse/AMBARI-21824
> Project: Ambari
> Issue Type: Task
> Components: ambari-server, ambari-web
>Affects Versions: 2.5.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 3.0.0
>
> Attachments: AMBARI-21824.1.patch
>
>
> ServiceGroup was a new sub-resource added for cluster in AMBARI-21594.
> This Task involves :
> - moving *Services* which was earlier a sub-resource of *Cluster* under
> *ServiceGroup* now, and
> - using *Servicegroup* while doing Creation, Update and retrieval of
> *HostComponents* and *ServiceComponents*.
> - UI changes which includes creating a *default ServiceGroup named 'core'*,
> and all services created goes under it. Further, making UI calls SG aware,
> while making a call.
> The new API calls will be the following:
> ---
> *==*
> *Service:*
> *==*
> New API calls:
> http://:/api/v1/clusters//*servicegroups/*/services
> http://:/api/v1/clusters//*servicegroups/*/services/
> *POST*
> Eg:
> http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services
> Request
> {code}
> {
> "ServiceInfo" : {
> "cluster_name": "c1",
> "service_group_name": "core",
> "service_name": "RANGER",
> "service_display_name": "RANGER"
> }
> }
> {code}
> Response
> {code}
> {
> "resources" : [
> {
> "href" :
> "http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER;,
> "ServiceInfo" : {
> "cluster_id" : 2,
> "cluster_name" : "c1",
> "credential_store_enabled" : false,
> "credential_store_supported" : false,
> "desired_repository_version_id" : "2.6.1.0-129",
> "desired_stack" : "HDP-2.6",
> "maintenance_state" : "OFF",
> "repository_state" : "NOT_REQUIRED",
> "service_display_name" : "RANGER",
> "service_group_id" : 2,
> "service_group_name" : "core",
> "service_id" : 4,
> "service_name" : "RANGER",
> "state" : "INIT"
> }
> }
> ]
> }
> {code}
> *GET*
> Eg:
> http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services
> Request
> {code}
> --
> {code}
> Response
> {code}
> {
> "href" :
> "http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services;,
> "items" : [
> {
> "href" :
> "http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER;,
> "ServiceInfo" : {
> "cluster_name" : "c1",
> "service_display_name" : "RANGER",
> "service_group_name" : "core"
> }
> }
> ]
> }
> {code}
> Eg:
> http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER
> Request
> {code}
> --
> {code}
> Response
> {code}
> {
> "href" :
> "http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER;,
> "ServiceInfo" : {
> "cluster_id" : 2,
> "cluster_name" : "c1",
> "credential_store_enabled" : "false",
> "credential_store_supported" : "false",
> "desired_repository_version_id" : 1,
> "desired_stack" : {
> "stackName" : "HDP",
> "stackVersion" : "2.6",
> "stackId" : "HDP-2.6"
> },
> "maintenance_state" : "OFF",
> "repository_state" : "NOT_REQUIRED",
> "service_display_name" : "RANGER",
> "service_group_id" : 2,
> "service_group_name" : "core",
> "service_id" : 4,
> "service_name" : "RANGER",
> "state" : "UNKNOWN"
> },
> "alerts_summary" : {
> "CRITICAL" : 0,
> "MAINTENANCE" : 0,
> "OK" : 0,
> "UNKNOWN" : 0,
> "WARNING" : 0
> },
> "alerts" : [ ],
> "components" : [ ],
> "artifacts" : [ ]
> }
> {code}
> *DELETE*
> Eg:
> http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER
> Request
> {code}
> --
> {code}
> Response
> {code}
> {
> "deleteResult" : [
> {
> "deleted" : {
> "key" : "service_name: RANGER"
> }
> }
> ]
> }
> {code}
>
[jira] [Commented] (AMBARI-21824) Make services as sub-resource of ServiceGroups and use Servicegroup while doing Creation, Update and retrieval of HostComponents and ServiceComponents.
[
https://issues.apache.org/jira/browse/AMBARI-21824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16146156#comment-16146156
]
Swapan Shridhar commented on AMBARI-21824:
--
Commit done to branch : *branch-feature-AMBARI-14714*
{code}
commit f3520c09e0dfb1f3f82d881d1a9c0df23fe549d8
Author: Swapan Shridhar
Date: Mon Aug 28 19:49:11 2017 -0700
AMBARI-21824. MultiEverything : Make services as sub-resource of
ServiceGroups and use Servicegroup while doing Creation, Update and retrieval
of HostComponents and ServiceComponents.
{code}
> Make services as sub-resource of ServiceGroups and use Servicegroup while
> doing Creation, Update and retrieval of HostComponents and ServiceComponents.
> ---
>
> Key: AMBARI-21824
> URL: https://issues.apache.org/jira/browse/AMBARI-21824
> Project: Ambari
> Issue Type: Task
> Components: ambari-server, ambari-web
>Affects Versions: 2.5.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 3.0.0
>
>
> ServiceGroup was a new sub-resource added for cluster in AMBARI-21594.
> This Task involves :
> - moving *Services* which was earlier a sub-resource of *Cluster* under
> *ServiceGroup* now, and
> - using *Servicegroup* while doing Creation, Update and retrieval of
> *HostComponents* and *ServiceComponents*.
> - UI changes which includes creating a *default ServiceGroup named 'core'*,
> and all services created goes under it. Further, making UI calls SG aware,
> while making a call.
> The new API calls will be the following:
> ---
> *==*
> *Service:*
> *==*
> New API calls:
> http://:/api/v1/clusters//*servicegroups/*/services
> http://:/api/v1/clusters//*servicegroups/*/services/
> *POST*
> Eg:
> http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services
> Request
> {code}
> {
> "ServiceInfo" : {
> "cluster_name": "c1",
> "service_group_name": "core",
> "service_name": "RANGER",
> "service_display_name": "RANGER"
> }
> }
> {code}
> Response
> {code}
> {
> "resources" : [
> {
> "href" :
> "http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER;,
> "ServiceInfo" : {
> "cluster_id" : 2,
> "cluster_name" : "c1",
> "credential_store_enabled" : false,
> "credential_store_supported" : false,
> "desired_repository_version_id" : "2.6.1.0-129",
> "desired_stack" : "HDP-2.6",
> "maintenance_state" : "OFF",
> "repository_state" : "NOT_REQUIRED",
> "service_display_name" : "RANGER",
> "service_group_id" : 2,
> "service_group_name" : "core",
> "service_id" : 4,
> "service_name" : "RANGER",
> "state" : "INIT"
> }
> }
> ]
> }
> {code}
> *GET*
> Eg:
> http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services
> Request
> {code}
> --
> {code}
> Response
> {code}
> {
> "href" :
> "http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services;,
> "items" : [
> {
> "href" :
> "http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER;,
> "ServiceInfo" : {
> "cluster_name" : "c1",
> "service_display_name" : "RANGER",
> "service_group_name" : "core"
> }
> }
> ]
> }
> {code}
> Eg:
> http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER
> Request
> {code}
> --
> {code}
> Response
> {code}
> {
> "href" :
> "http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER;,
> "ServiceInfo" : {
> "cluster_id" : 2,
> "cluster_name" : "c1",
> "credential_store_enabled" : "false",
> "credential_store_supported" : "false",
> "desired_repository_version_id" : 1,
> "desired_stack" : {
> "stackName" : "HDP",
> "stackVersion" : "2.6",
> "stackId" : "HDP-2.6"
> },
> "maintenance_state" : "OFF",
> "repository_state" : "NOT_REQUIRED",
> "service_display_name" : "RANGER",
> "service_group_id" : 2,
> "service_group_name" : "core",
> "service_id" : 4,
> "service_name" : "RANGER",
> "state" : "UNKNOWN"
> },
> "alerts_summary" : {
> "CRITICAL" : 0,
> "MAINTENANCE" : 0,
> "OK" : 0,
> "UNKNOWN" : 0,
> "WARNING" : 0
> },
> "alerts" : [ ],
> "components" : [ ],
> "artifacts" : [ ]
> }
> {code}
> *DELETE*
> Eg:
>
[jira] [Comment Edited] (AMBARI-21824) Make services as sub-resource of ServiceGroups and use Servicegroup while doing Creation, Update and retrieval of HostComponents and ServiceComponents.
[
https://issues.apache.org/jira/browse/AMBARI-21824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16146156#comment-16146156
]
Swapan Shridhar edited comment on AMBARI-21824 at 8/29/17 9:23 PM:
---
Commit done to branch : *"branch-feature-AMBARI-14714"*
{code}
commit f3520c09e0dfb1f3f82d881d1a9c0df23fe549d8
Author: Swapan Shridhar
Date: Mon Aug 28 19:49:11 2017 -0700
AMBARI-21824. MultiEverything : Make services as sub-resource of
ServiceGroups and use Servicegroup while doing Creation, Update and retrieval
of HostComponents and ServiceComponents.
{code}
was (Author: swapanshridhar):
Commit done to branch : *branch-feature-AMBARI-14714*
{code}
commit f3520c09e0dfb1f3f82d881d1a9c0df23fe549d8
Author: Swapan Shridhar
Date: Mon Aug 28 19:49:11 2017 -0700
AMBARI-21824. MultiEverything : Make services as sub-resource of
ServiceGroups and use Servicegroup while doing Creation, Update and retrieval
of HostComponents and ServiceComponents.
{code}
> Make services as sub-resource of ServiceGroups and use Servicegroup while
> doing Creation, Update and retrieval of HostComponents and ServiceComponents.
> ---
>
> Key: AMBARI-21824
> URL: https://issues.apache.org/jira/browse/AMBARI-21824
> Project: Ambari
> Issue Type: Task
> Components: ambari-server, ambari-web
>Affects Versions: 2.5.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 3.0.0
>
>
> ServiceGroup was a new sub-resource added for cluster in AMBARI-21594.
> This Task involves :
> - moving *Services* which was earlier a sub-resource of *Cluster* under
> *ServiceGroup* now, and
> - using *Servicegroup* while doing Creation, Update and retrieval of
> *HostComponents* and *ServiceComponents*.
> - UI changes which includes creating a *default ServiceGroup named 'core'*,
> and all services created goes under it. Further, making UI calls SG aware,
> while making a call.
> The new API calls will be the following:
> ---
> *==*
> *Service:*
> *==*
> New API calls:
> http://:/api/v1/clusters//*servicegroups/*/services
> http://:/api/v1/clusters//*servicegroups/*/services/
> *POST*
> Eg:
> http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services
> Request
> {code}
> {
> "ServiceInfo" : {
> "cluster_name": "c1",
> "service_group_name": "core",
> "service_name": "RANGER",
> "service_display_name": "RANGER"
> }
> }
> {code}
> Response
> {code}
> {
> "resources" : [
> {
> "href" :
> "http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER;,
> "ServiceInfo" : {
> "cluster_id" : 2,
> "cluster_name" : "c1",
> "credential_store_enabled" : false,
> "credential_store_supported" : false,
> "desired_repository_version_id" : "2.6.1.0-129",
> "desired_stack" : "HDP-2.6",
> "maintenance_state" : "OFF",
> "repository_state" : "NOT_REQUIRED",
> "service_display_name" : "RANGER",
> "service_group_id" : 2,
> "service_group_name" : "core",
> "service_id" : 4,
> "service_name" : "RANGER",
> "state" : "INIT"
> }
> }
> ]
> }
> {code}
> *GET*
> Eg:
> http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services
> Request
> {code}
> --
> {code}
> Response
> {code}
> {
> "href" :
> "http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services;,
> "items" : [
> {
> "href" :
> "http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER;,
> "ServiceInfo" : {
> "cluster_name" : "c1",
> "service_display_name" : "RANGER",
> "service_group_name" : "core"
> }
> }
> ]
> }
> {code}
> Eg:
> http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER
> Request
> {code}
> --
> {code}
> Response
> {code}
> {
> "href" :
> "http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER;,
> "ServiceInfo" : {
> "cluster_id" : 2,
> "cluster_name" : "c1",
> "credential_store_enabled" : "false",
> "credential_store_supported" : "false",
> "desired_repository_version_id" : 1,
> "desired_stack" : {
> "stackName" : "HDP",
> "stackVersion" : "2.6",
> "stackId" : "HDP-2.6"
> },
> "maintenance_state" : "OFF",
> "repository_state" :
[jira] [Updated] (AMBARI-21821) Update Ambari Metrics service check to support HTTP SPNEGO authentication
[
https://issues.apache.org/jira/browse/AMBARI-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qin Liu updated AMBARI-21821:
-
Status: Patch Available (was: Open)
> Update Ambari Metrics service check to support HTTP SPNEGO authentication
> -
>
> Key: AMBARI-21821
> URL: https://issues.apache.org/jira/browse/AMBARI-21821
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: trunk
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: trunk
>
> Attachments: AMBARI-21821.patch
>
>
> This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to
> authenticate".
> In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari
> Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But
> Ambari Metrics service check currently does not support Kerberos HTTP SPNEGO
> authentication.
> 2017-08-24 16:13:44,078 - Ambari Metrics service check was started.
> 2017-08-24 16:13:44,109 - Generated metrics for host amshost.example.com :
> {
> "metrics": [
> {
> "metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
> "appid": "amssmoketestfake",
> "hostname": "host.example.com",
> "timestamp": 1503616424000,
> "starttime": 1503616424000,
> "metrics": {
> "1503616424000": 0.164134766408,
> "1503616425000": 1503616424000
> }
> }
> ]
> }
> 2017-08-24 16:13:44,114 - Connecting (POST) to
> amshost.example.com:6188/ws/v1/timeline/metrics/
> 2017-08-24 16:13:44,117 - Http response for host amshost.example.com: 401
> Authentication required
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21821) Update Ambari Metrics service check to support HTTP SPNEGO authentication
[
https://issues.apache.org/jira/browse/AMBARI-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qin Liu updated AMBARI-21821:
-
Attachment: AMBARI-21821.patch
> Update Ambari Metrics service check to support HTTP SPNEGO authentication
> -
>
> Key: AMBARI-21821
> URL: https://issues.apache.org/jira/browse/AMBARI-21821
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: trunk
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: trunk
>
> Attachments: AMBARI-21821.patch
>
>
> This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to
> authenticate".
> In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari
> Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But
> Ambari Metrics service check currently does not support Kerberos HTTP SPNEGO
> authentication.
> 2017-08-24 16:13:44,078 - Ambari Metrics service check was started.
> 2017-08-24 16:13:44,109 - Generated metrics for host amshost.example.com :
> {
> "metrics": [
> {
> "metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
> "appid": "amssmoketestfake",
> "hostname": "host.example.com",
> "timestamp": 1503616424000,
> "starttime": 1503616424000,
> "metrics": {
> "1503616424000": 0.164134766408,
> "1503616425000": 1503616424000
> }
> }
> ]
> }
> 2017-08-24 16:13:44,114 - Connecting (POST) to
> amshost.example.com:6188/ws/v1/timeline/metrics/
> 2017-08-24 16:13:44,117 - Http response for host amshost.example.com: 401
> Authentication required
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21824) Make services as sub-resource of ServiceGroups and use Servicegroup while doing Creation, Update and retrieval of HostComponents and ServiceComponents.
[
https://issues.apache.org/jira/browse/AMBARI-21824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-21824:
-
Description:
ServiceGroup was a new sub-resource added for cluster in AMBARI-21594.
This Task involves :
- moving *Services* which was earlier a sub-resource of *Cluster* under
*ServiceGroup* now, and
- using *Servicegroup* while doing Creation, Update and retrieval of
*HostComponents* and *ServiceComponents*.
- UI changes which includes creating a *default ServiceGroup named 'core'*,
and all services created goes under it. Further, making UI calls SG aware,
while making a call.
The new API calls will be the following:
---
*==*
*Service:*
*==*
New API calls:
http://:/api/v1/clusters//*servicegroups/*/services
http://:/api/v1/clusters//*servicegroups/*/services/
*POST*
Eg:
http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services
Request
{code}
{
"ServiceInfo" : {
"cluster_name": "c1",
"service_group_name": "core",
"service_name": "RANGER",
"service_display_name": "RANGER"
}
}
{code}
Response
{code}
{
"resources" : [
{
"href" :
"http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER;,
"ServiceInfo" : {
"cluster_id" : 2,
"cluster_name" : "c1",
"credential_store_enabled" : false,
"credential_store_supported" : false,
"desired_repository_version_id" : "2.6.1.0-129",
"desired_stack" : "HDP-2.6",
"maintenance_state" : "OFF",
"repository_state" : "NOT_REQUIRED",
"service_display_name" : "RANGER",
"service_group_id" : 2,
"service_group_name" : "core",
"service_id" : 4,
"service_name" : "RANGER",
"state" : "INIT"
}
}
]
}
{code}
*GET*
Eg:
http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services
Request
{code}
--
{code}
Response
{code}
{
"href" :
"http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services;,
"items" : [
{
"href" :
"http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER;,
"ServiceInfo" : {
"cluster_name" : "c1",
"service_display_name" : "RANGER",
"service_group_name" : "core"
}
}
]
}
{code}
Eg:
http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER
Request
{code}
--
{code}
Response
{code}
{
"href" :
"http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER;,
"ServiceInfo" : {
"cluster_id" : 2,
"cluster_name" : "c1",
"credential_store_enabled" : "false",
"credential_store_supported" : "false",
"desired_repository_version_id" : 1,
"desired_stack" : {
"stackName" : "HDP",
"stackVersion" : "2.6",
"stackId" : "HDP-2.6"
},
"maintenance_state" : "OFF",
"repository_state" : "NOT_REQUIRED",
"service_display_name" : "RANGER",
"service_group_id" : 2,
"service_group_name" : "core",
"service_id" : 4,
"service_name" : "RANGER",
"state" : "UNKNOWN"
},
"alerts_summary" : {
"CRITICAL" : 0,
"MAINTENANCE" : 0,
"OK" : 0,
"UNKNOWN" : 0,
"WARNING" : 0
},
"alerts" : [ ],
"components" : [ ],
"artifacts" : [ ]
}
{code}
*DELETE*
Eg:
http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER
Request
{code}
--
{code}
Response
{code}
{
"deleteResult" : [
{
"deleted" : {
"key" : "service_name: RANGER"
}
}
]
}
{code}
**
*Service Component*
**
New API calls:
http://:/api/v1/clusters//*servicegroups/*/services//components/
http://:/api/v1/clusters//*servicegroups/*/services//components/ZOOKEEPER_SERVER
*POST*
Eg:
http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER/components/
Request
{code}
{
"ServiceComponentInfo" : {
"component_name" : "RANGER_USERSYNC"
}
}
{code}
Response
{code}
{
"resources" : [
{
"href" :
"http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER/components/RANGER_USERSYNC/;,
"ServiceComponentInfo" : {
"category" : null,
"cluster_id" : 2,
"cluster_name" : "c1",
"component_name" : "RANGER_USERSYNC",
"desired_stack" : "HDP-2.6",
"desired_version" : "NOT_REQUIRED",
"display_name" : "Ranger Usersync",
"recovery_enabled" : false,
"service_display_name" : "RANGER",
"service_group_id" : 2,
"service_group_name" : "core",
"service_id" : 4,
[jira] [Updated] (AMBARI-21824) Make services as sub-resource of ServiceGroups and use Servicegroup while doing Creation, Update and retrieval of HostComponents and ServiceComponents.
[
https://issues.apache.org/jira/browse/AMBARI-21824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-21824:
-
Description:
ServiceGroup was a new sub-resource added for cluster in AMBARI-21594.
This Task involves :
- moving *Services* which was earlier a sub-resource of *Cluster* under
*ServiceGroup* now, and
- using *Servicegroup* while doing Creation, Update and retrieval of
*HostComponents* and *ServiceComponents*.
- UI changes which includes creating a *default ServiceGroup named 'core'*,
and all services created goes under it. Further, making UI calls SG aware,
while making a call.
The new API calls will be the following:
---
*==*
*Service:*
*==*
New API calls:
http://:/api/v1/clusters//*servicegroups/*/services
http://:/api/v1/clusters//*servicegroups/*/services/
*POST*
Eg:
http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services
Request
{code}
{
"ServiceInfo" : {
"cluster_name": "c1",
"service_group_name": "core",
"service_name": "RANGER",
"service_display_name": "RANGER"
}
}
{code}
Response
{code}
{
"resources" : [
{
"href" :
"http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER;,
"ServiceInfo" : {
"cluster_id" : 2,
"cluster_name" : "c1",
"credential_store_enabled" : false,
"credential_store_supported" : false,
"desired_repository_version_id" : "2.6.1.0-129",
"desired_stack" : "HDP-2.6",
"maintenance_state" : "OFF",
"repository_state" : "NOT_REQUIRED",
"service_display_name" : "RANGER",
"service_group_id" : 2,
"service_group_name" : "core",
"service_id" : 4,
"service_name" : "RANGER",
"state" : "INIT"
}
}
]
}
{code}
*GET*
Eg:
http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services
Request
{code}
--
{code}
Response
{code}
{
"href" :
"http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services;,
"items" : [
{
"href" :
"http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER;,
"ServiceInfo" : {
"cluster_name" : "c1",
"service_display_name" : "RANGER",
"service_group_name" : "core"
}
}
]
}
{code}
Eg:
http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER
Request
{code}
--
{code}
Response
{code}
{
"href" :
"http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER;,
"ServiceInfo" : {
"cluster_id" : 2,
"cluster_name" : "c1",
"credential_store_enabled" : "false",
"credential_store_supported" : "false",
"desired_repository_version_id" : 1,
"desired_stack" : {
"stackName" : "HDP",
"stackVersion" : "2.6",
"stackId" : "HDP-2.6"
},
"maintenance_state" : "OFF",
"repository_state" : "NOT_REQUIRED",
"service_display_name" : "RANGER",
"service_group_id" : 2,
"service_group_name" : "core",
"service_id" : 4,
"service_name" : "RANGER",
"state" : "UNKNOWN"
},
"alerts_summary" : {
"CRITICAL" : 0,
"MAINTENANCE" : 0,
"OK" : 0,
"UNKNOWN" : 0,
"WARNING" : 0
},
"alerts" : [ ],
"components" : [ ],
"artifacts" : [ ]
}
{code}
*DELETE*
Eg:
http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER
Request
{code}
--
{code}
Response
{code}
{
"deleteResult" : [
{
"deleted" : {
"key" : "service_name: RANGER"
}
}
]
}
{code}
-
**
*Service Component*
**
New API calls:
http://:/api/v1/clusters//*servicegroups/*/services//components/
http://:/api/v1/clusters//*servicegroups/*/services//components/ZOOKEEPER_SERVER
*POST*
Eg:
http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER/components/
Request
{code}
{
"ServiceComponentInfo" : {
"component_name" : "RANGER_USERSYNC"
}
}
{code}
Response
{code}
{
"resources" : [
{
"href" :
"http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER/components/RANGER_USERSYNC/;,
"ServiceComponentInfo" : {
"category" : null,
"cluster_id" : 2,
"cluster_name" : "c1",
"component_name" : "RANGER_USERSYNC",
"desired_stack" : "HDP-2.6",
"desired_version" : "NOT_REQUIRED",
"display_name" : "Ranger Usersync",
"recovery_enabled" : false,
[jira] [Updated] (AMBARI-21824) Make services as sub-resource of ServiceGroups and use Servicegroup while doing Creation, Update and retrieval of HostComponents and ServiceComponents.
[
https://issues.apache.org/jira/browse/AMBARI-21824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-21824:
-
Description:
ServiceGroup was a new sub-resource added for cluster in AMBARI-21594.
This Task involves :
- moving *Services* which was earlier a sub-resource of *Cluster* under
*ServiceGroup* now, and
- using *Servicegroup* while doing Creation, Update and retrieval of
*HostComponents* and *ServiceComponents*.
- UI changes which includes creating a *default ServiceGroup named 'core'*,
and all services created goes under it. Further, making UI calls SG aware,
while making a call.
The new API calls will be the following:
---
*==*
*Service:*
*==*
http://:/api/v1/clusters//*servicegroups/*/services
http://:/api/v1/clusters//*servicegroups/*/services/
*POST*
Eg:
http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services
Request
{code}
{
"ServiceInfo" : {
"cluster_name": "c1",
"service_group_name": "core",
"service_name": "RANGER",
"service_display_name": "RANGER"
}
}
{code}
Response
{code}
{
"resources" : [
{
"href" :
"http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER;,
"ServiceInfo" : {
"cluster_id" : 2,
"cluster_name" : "c1",
"credential_store_enabled" : false,
"credential_store_supported" : false,
"desired_repository_version_id" : "2.6.1.0-129",
"desired_stack" : "HDP-2.6",
"maintenance_state" : "OFF",
"repository_state" : "NOT_REQUIRED",
"service_display_name" : "RANGER",
"service_group_id" : 2,
"service_group_name" : "core",
"service_id" : 4,
"service_name" : "RANGER",
"state" : "INIT"
}
}
]
}
{code}
*GET*
Eg:
http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services
Request
{code}
--
{code}
Response
{code}
{
"href" :
"http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services;,
"items" : [
{
"href" :
"http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER;,
"ServiceInfo" : {
"cluster_name" : "c1",
"service_display_name" : "RANGER",
"service_group_name" : "core"
}
}
]
}
{code}
Eg:
http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER
Request
{code}
--
{code}
Response
{code}
{
"href" :
"http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER;,
"ServiceInfo" : {
"cluster_id" : 2,
"cluster_name" : "c1",
"credential_store_enabled" : "false",
"credential_store_supported" : "false",
"desired_repository_version_id" : 1,
"desired_stack" : {
"stackName" : "HDP",
"stackVersion" : "2.6",
"stackId" : "HDP-2.6"
},
"maintenance_state" : "OFF",
"repository_state" : "NOT_REQUIRED",
"service_display_name" : "RANGER",
"service_group_id" : 2,
"service_group_name" : "core",
"service_id" : 4,
"service_name" : "RANGER",
"state" : "UNKNOWN"
},
"alerts_summary" : {
"CRITICAL" : 0,
"MAINTENANCE" : 0,
"OK" : 0,
"UNKNOWN" : 0,
"WARNING" : 0
},
"alerts" : [ ],
"components" : [ ],
"artifacts" : [ ]
}
{code}
*DELETE*
Eg:
http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER
Request
{code}
--
{code}
Response
{code}
{
"deleteResult" : [
{
"deleted" : {
"key" : "service_name: RANGER"
}
}
]
}
{code}
*===*
*Service Component*
*===*
*POST*
Eg:
http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER/components/
Request
{code}
{
"ServiceComponentInfo" : {
"component_name" : "RANGER_USERSYNC"
}
}
{code}
Response
{code}
{
"resources" : [
{
"href" :
"http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER/components/RANGER_USERSYNC/;,
"ServiceComponentInfo" : {
"category" : null,
"cluster_id" : 2,
"cluster_name" : "c1",
"component_name" : "RANGER_USERSYNC",
"desired_stack" : "HDP-2.6",
"desired_version" : "NOT_REQUIRED",
"display_name" : "Ranger Usersync",
"recovery_enabled" : false,
"service_display_name" : "RANGER",
"service_group_id" : 2,
"service_group_name" : "core",
"service_id" : 4,
"service_name" : "RANGER",
"state" : "INIT",
"total_count" : {
"installFailedCount" : 0,
"unknownCount" : 0,
"installedCount" : 0,
[jira] [Updated] (AMBARI-21824) Make services as sub-resource of ServiceGroups and use Servicegroup while doing Creation, Update and retrieval of HostComponents and ServiceComponents.
[
https://issues.apache.org/jira/browse/AMBARI-21824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-21824:
-
Description:
ServiceGroup was a new sub-resource added for cluster in AMBARI-21594.
This Task involves :
- moving *Services* which was earlier a sub-resource of *Cluster* under
*ServiceGroup* now, and
- using *Servicegroup* while doing Creation, Update and retrieval of
*HostComponents* and *ServiceComponents*.
- UI changes which includes creating a *default ServiceGroup named 'core'*,
and all services created goes under it. Further, making UI calls SG aware,
while making a call.
The new API calls will be the following:
---
*==*
*Service:*
*==*
http://:/api/v1/clusters//*servicegroups/*/services
http://:/api/v1/clusters//*servicegroups/*/services/
*POST*
Eg:
http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services
Request
{code}
{
"ServiceInfo" : {
"cluster_name": "c1",
"service_group_name": "core",
"service_name": "RANGER",
"service_display_name": "RANGER"
}
}
{code}
Response:
{code}
{
"resources" : [
{
"href" :
"http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER;,
"ServiceInfo" : {
"cluster_id" : 2,
"cluster_name" : "c1",
"credential_store_enabled" : false,
"credential_store_supported" : false,
"desired_repository_version_id" : "2.6.1.0-129",
"desired_stack" : "HDP-2.6",
"maintenance_state" : "OFF",
"repository_state" : "NOT_REQUIRED",
"service_display_name" : "RANGER",
"service_group_id" : 2,
"service_group_name" : "core",
"service_id" : 4,
"service_name" : "RANGER",
"state" : "INIT"
}
}
]
}
{code}
*GET*
Eg:
http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services
Request
{code}
--
{code}
Response:
{code}
{
"href" :
"http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services;,
"items" : [
{
"href" :
"http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER;,
"ServiceInfo" : {
"cluster_name" : "c1",
"service_display_name" : "RANGER",
"service_group_name" : "core"
}
}
]
}
{code}
Eg:
http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER
Request
{code}
--
{code}
Response:
{code}
{
"href" :
"http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER;,
"ServiceInfo" : {
"cluster_id" : 2,
"cluster_name" : "c1",
"credential_store_enabled" : "false",
"credential_store_supported" : "false",
"desired_repository_version_id" : 1,
"desired_stack" : {
"stackName" : "HDP",
"stackVersion" : "2.6",
"stackId" : "HDP-2.6"
},
"maintenance_state" : "OFF",
"repository_state" : "NOT_REQUIRED",
"service_display_name" : "RANGER",
"service_group_id" : 2,
"service_group_name" : "core",
"service_id" : 4,
"service_name" : "RANGER",
"state" : "UNKNOWN"
},
"alerts_summary" : {
"CRITICAL" : 0,
"MAINTENANCE" : 0,
"OK" : 0,
"UNKNOWN" : 0,
"WARNING" : 0
},
"alerts" : [ ],
"components" : [ ],
"artifacts" : [ ]
}
{code}
*DELETE*
Eg:
http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER
Request
{code}
{code}
Response:
{code}
{
"deleteResult" : [
{
"deleted" : {
"key" : "service_name: RANGER"
}
}
]
}
{code}
*===*
*Service Component*
*===*
*POST*
Eg:
http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER/components/
Request
{code}
{
"ServiceComponentInfo" : {
"component_name" : "RANGER_USERSYNC"
}
}
{code}
Response:
{code}
{
"resources" : [
{
"href" :
"http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER/components/RANGER_USERSYNC/;,
"ServiceComponentInfo" : {
"category" : null,
"cluster_id" : 2,
"cluster_name" : "c1",
"component_name" : "RANGER_USERSYNC",
"desired_stack" : "HDP-2.6",
"desired_version" : "NOT_REQUIRED",
"display_name" : "Ranger Usersync",
"recovery_enabled" : false,
"service_display_name" : "RANGER",
"service_group_id" : 2,
"service_group_name" : "core",
"service_id" : 4,
"service_name" : "RANGER",
"state" : "INIT",
"total_count" : {
"installFailedCount" : 0,
"unknownCount" : 0,
"installedCount" : 0,
[jira] [Updated] (AMBARI-21824) Make services as sub-resource of ServiceGroups and use Servicegroup while doing Creation, Update and retrieval of HostComponents and ServiceComponents.
[
https://issues.apache.org/jira/browse/AMBARI-21824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-21824:
-
Description:
ServiceGroup was a new sub-resource added for cluster in AMBARI-21594.
This Task involves :
- moving *Services* which was earlier a sub-resource of *Cluster* under
*ServiceGroup* now, and
- using *Servicegroup* while doing Creation, Update and retrieval of
*HostComponents* and *ServiceComponents*.
The new API calls will be the following:
---
*==*
*Service:*
*==*
http://:/api/v1/clusters//*servicegroups/*/services
http://:/api/v1/clusters//*servicegroups/*/services/
*POST*
Eg:
http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services
Request
{code}
{
"ServiceInfo" : {
"cluster_name": "c1",
"service_group_name": "core",
"service_name": "RANGER",
"service_display_name": "RANGER"
}
}
{code}
Response:
{code}
{
"resources" : [
{
"href" :
"http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER;,
"ServiceInfo" : {
"cluster_id" : 2,
"cluster_name" : "c1",
"credential_store_enabled" : false,
"credential_store_supported" : false,
"desired_repository_version_id" : "2.6.1.0-129",
"desired_stack" : "HDP-2.6",
"maintenance_state" : "OFF",
"repository_state" : "NOT_REQUIRED",
"service_display_name" : "RANGER",
"service_group_id" : 2,
"service_group_name" : "core",
"service_id" : 4,
"service_name" : "RANGER",
"state" : "INIT"
}
}
]
}
{code}
*GET*
Eg:
http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services
Request
{code}
--
{code}
Response:
{code}
{
"href" :
"http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services;,
"items" : [
{
"href" :
"http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER;,
"ServiceInfo" : {
"cluster_name" : "c1",
"service_display_name" : "RANGER",
"service_group_name" : "core"
}
}
]
}
{code}
Eg:
http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER
Request
{code}
--
{code}
Response:
{code}
{
"href" :
"http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER;,
"ServiceInfo" : {
"cluster_id" : 2,
"cluster_name" : "c1",
"credential_store_enabled" : "false",
"credential_store_supported" : "false",
"desired_repository_version_id" : 1,
"desired_stack" : {
"stackName" : "HDP",
"stackVersion" : "2.6",
"stackId" : "HDP-2.6"
},
"maintenance_state" : "OFF",
"repository_state" : "NOT_REQUIRED",
"service_display_name" : "RANGER",
"service_group_id" : 2,
"service_group_name" : "core",
"service_id" : 4,
"service_name" : "RANGER",
"state" : "UNKNOWN"
},
"alerts_summary" : {
"CRITICAL" : 0,
"MAINTENANCE" : 0,
"OK" : 0,
"UNKNOWN" : 0,
"WARNING" : 0
},
"alerts" : [ ],
"components" : [ ],
"artifacts" : [ ]
}
{code}
*DELETE*
Eg:
http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER
Request
{code}
{code}
Response:
{code}
{
"deleteResult" : [
{
"deleted" : {
"key" : "service_name: RANGER"
}
}
]
}
{code}
*===*
*Service Component*
*===*
*POST*
Eg:
http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER/components/
Request
{code}
{
"ServiceComponentInfo" : {
"component_name" : "RANGER_USERSYNC"
}
}
{code}
Response:
{code}
{
"resources" : [
{
"href" :
"http://c6404.ambari.apache.org:8080/api/v1/clusters/c1/servicegroups/core/services/RANGER/components/RANGER_USERSYNC/;,
"ServiceComponentInfo" : {
"category" : null,
"cluster_id" : 2,
"cluster_name" : "c1",
"component_name" : "RANGER_USERSYNC",
"desired_stack" : "HDP-2.6",
"desired_version" : "NOT_REQUIRED",
"display_name" : "Ranger Usersync",
"recovery_enabled" : false,
"service_display_name" : "RANGER",
"service_group_id" : 2,
"service_group_name" : "core",
"service_id" : 4,
"service_name" : "RANGER",
"state" : "INIT",
"total_count" : {
"installFailedCount" : 0,
"unknownCount" : 0,
"installedCount" : 0,
"initCount" : 0,
"startedCount" : 0,
"totalCount" : 0
}
}
}
]
}
{code}
*GET*
Eg:
[jira] [Updated] (AMBARI-21847) Refactor stack version column view
[ https://issues.apache.org/jira/browse/AMBARI-21847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21847: -- Status: Patch Available (was: In Progress) > Refactor stack version column view > -- > > Key: AMBARI-21847 > URL: https://issues.apache.org/jira/browse/AMBARI-21847 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.6.0 > > Attachments: AMBARI-21847.patch, AMBARI-21847_trunk.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (AMBARI-21847) Refactor stack version column view
[ https://issues.apache.org/jira/browse/AMBARI-21847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145888#comment-16145888 ] Andrii Tkach edited comment on AMBARI-21847 at 8/29/17 7:06 PM: branch-2.6: 30479 passing (25s) 157 pending trunk: 21306 passing (25s) 128 pending was (Author: atkach): branch-2.6: 30479 passing (25s) 157 pending > Refactor stack version column view > -- > > Key: AMBARI-21847 > URL: https://issues.apache.org/jira/browse/AMBARI-21847 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.6.0 > > Attachments: AMBARI-21847.patch, AMBARI-21847_trunk.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21847) Refactor stack version column view
[ https://issues.apache.org/jira/browse/AMBARI-21847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21847: -- Attachment: AMBARI-21847_trunk.patch > Refactor stack version column view > -- > > Key: AMBARI-21847 > URL: https://issues.apache.org/jira/browse/AMBARI-21847 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.6.0 > > Attachments: AMBARI-21847.patch, AMBARI-21847_trunk.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21848) Ambari Replaces the Value of Undefined Service Configuration Properties with "Undefined" in Default Config Group If the Same Property is Defined in Different Config Gro
Aleksandr Kovalenko created AMBARI-21848: Summary: Ambari Replaces the Value of Undefined Service Configuration Properties with "Undefined" in Default Config Group If the Same Property is Defined in Different Config Group Key: AMBARI-21848 URL: https://issues.apache.org/jira/browse/AMBARI-21848 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.1 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Priority: Blocker Fix For: 2.6.0 _PROBLEM:_ If Custom *-site properties are added to a non-default config group in Ambari 2.5.0 or 2.5.1, these same properties will be set to "Undefined" in the default config group when a different default configuration group property for the same service is modified. _BUSINESS IMPACT:_ This can result in services failing to restart for certain properties (e.g. hive.server2.thrift.bind.host) _STEPS TO REPRODUCE:_ 1. Install Ambari-2.5 2. Create config group for any service. 3. Add override for this new group in some custom *-site. 4. Make change in default config group for the same service. _EXPECTED RESULT:_ Property overriden in step 3 will not exist in default config group _ACTUAL RESULT:_ Property overriden in step 3 has value "Undefined" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21847) Refactor stack version column view
[ https://issues.apache.org/jira/browse/AMBARI-21847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145888#comment-16145888 ] Andrii Tkach commented on AMBARI-21847: --- branch-2.6: 30479 passing (25s) 157 pending > Refactor stack version column view > -- > > Key: AMBARI-21847 > URL: https://issues.apache.org/jira/browse/AMBARI-21847 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.6.0 > > Attachments: AMBARI-21847.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21847) Refactor stack version column view
[ https://issues.apache.org/jira/browse/AMBARI-21847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21847: -- Attachment: AMBARI-21847.patch > Refactor stack version column view > -- > > Key: AMBARI-21847 > URL: https://issues.apache.org/jira/browse/AMBARI-21847 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.6.0 > > Attachments: AMBARI-21847.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21847) Refactor stack version column view
Andrii Tkach created AMBARI-21847: - Summary: Refactor stack version column view Key: AMBARI-21847 URL: https://issues.apache.org/jira/browse/AMBARI-21847 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.6.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.6.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21634) Make sure Ambari also considers NIS users
[ https://issues.apache.org/jira/browse/AMBARI-21634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145867#comment-16145867 ] Aman Poonia commented on AMBARI-21634: -- Can we get this committed? > Make sure Ambari also considers NIS users > -- > > Key: AMBARI-21634 > URL: https://issues.apache.org/jira/browse/AMBARI-21634 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.5.1 >Reporter: Aman Poonia >Assignee: Aman Poonia > Fix For: trunk > > Attachments: AMBARI-21634.patch > > > Make sure Ambari also considers NIS users while reporting for the users if > they are present or not. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21308) Log Search UI GA
[
https://issues.apache.org/jira/browse/AMBARI-21308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145833#comment-16145833
]
Hadoop QA commented on AMBARI-21308:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12884296/AMBARI-21308_merge.patch
against trunk revision .
{color:red}-1 @author{color}. The patch appears to contain 1 @author tags
which the Hadoop community has agreed to not allow in code contributions.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 javac{color}. The patch appears to cause the [build to
fail|https://builds.apache.org/job/Ambari-trunk-test-patch/12098//artifact/patch-work/patchJavacWarnings.txt].
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12098//console
This message is automatically generated.
> Log Search UI GA
>
>
> Key: AMBARI-21308
> URL: https://issues.apache.org/jira/browse/AMBARI-21308
> Project: Ambari
> Issue Type: Epic
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-21308_merge.patch
>
>
> This Epic tracks the implementation of the new Log Search UI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21846) Transparent Huge Pages check using wrong file for CentOS 7
[
https://issues.apache.org/jira/browse/AMBARI-21846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Lavoie updated AMBARI-21846:
--
Summary: Transparent Huge Pages check using wrong file for CentOS 7 (was:
Transparent Huge Pages check using wrong file CentOS 7)
> Transparent Huge Pages check using wrong file for CentOS 7
> --
>
> Key: AMBARI-21846
> URL: https://issues.apache.org/jira/browse/AMBARI-21846
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
> Environment: CentOS 7.x
> Ambari 2.5.1 - Hortonworks
>Reporter: Bruno Lavoie
>Priority: Minor
>
> In ambari_agent/HostInfo.py, the file used to check Transparent Huge Pages
> for RedHat family is: /sys/kernel/mm/redhat_transparent_hugepage/enabled
> But it appears to be /sys/kernel/mm/transparent_hugepage/enabled for CentOS 7.
> {code}
> # cat /etc/redhat-release
> CentOS Linux release 7.3.1611 (Core)
> # cat /sys/kernel/mm/redhat_transparent_hugepage/enabled
> cat: /sys/kernel/mm/redhat_transparent_hugepage/enabled: No such file or
> directory
> # cat /sys/kernel/mm/transparent_hugepage/enabled
> [always] madvise never
> {code}
> No warnings when configuring hosts for a fresh cluster while I didn't
> disabled THP. Found it suspect and stumbled into this issue.
> Maybe the code must be more tailored for managing CentOS vs RedHat.
> I don't have any RHEL to check if it changed there too.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21846) Transparent Huge Pages check using wrong file CentOS 7
Bruno Lavoie created AMBARI-21846:
-
Summary: Transparent Huge Pages check using wrong file CentOS 7
Key: AMBARI-21846
URL: https://issues.apache.org/jira/browse/AMBARI-21846
Project: Ambari
Issue Type: Bug
Components: ambari-agent
Environment: CentOS 7.x
Ambari 2.5.1 - Hortonworks
Reporter: Bruno Lavoie
Priority: Minor
In ambari_agent/HostInfo.py, the file used to check Transparent Huge Pages for
RedHat family is: /sys/kernel/mm/redhat_transparent_hugepage/enabled
But it appears to be /sys/kernel/mm/transparent_hugepage/enabled for CentOS 7.
{code}
# cat /etc/redhat-release
CentOS Linux release 7.3.1611 (Core)
# cat /sys/kernel/mm/redhat_transparent_hugepage/enabled
cat: /sys/kernel/mm/redhat_transparent_hugepage/enabled: No such file or
directory
# cat /sys/kernel/mm/transparent_hugepage/enabled
[always] madvise never
{code}
No warnings when configuring hosts for a fresh cluster while I didn't disabled
THP. Found it suspect and stumbled into this issue.
Maybe the code must be more tailored for managing CentOS vs RedHat.
I don't have any RHEL to check if it changed there too.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21841) Green Version Bubbles Are Selected Multiple Times For Patched Services
[
https://issues.apache.org/jira/browse/AMBARI-21841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145810#comment-16145810
]
Hadoop QA commented on AMBARI-21841:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12884304/AMBARI-21841_trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12097//console
This message is automatically generated.
> Green Version Bubbles Are Selected Multiple Times For Patched Services
> --
>
> Key: AMBARI-21841
> URL: https://issues.apache.org/jira/browse/AMBARI-21841
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.6.0
>
> Attachments: AMBARI-21841.patch, AMBARI-21841_trunk.patch
>
>
> STR:
> Install HDP 2.6.0.0 with ZK and Storm
> Patch Storm to HDP 2.6.0.1
> Install a MAINT VDF for 2.6.1.0 where:
> ZK's version is 2.6.1.0
> Storm's version is 2.6.0.1
> Because the VDF declares that Storm's version is 2.6.0.1, we won't upgrade
> it. However, the Stacks and Versions page shows both the version numbers for
> Storm for 2.6.0.1 and 2.6.1.0 as being green. This is incorrect - a service
> should only ever have the version it's on be highlighted.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21841) Green Version Bubbles Are Selected Multiple Times For Patched Services
[ https://issues.apache.org/jira/browse/AMBARI-21841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145776#comment-16145776 ] Andrii Tkach commented on AMBARI-21841: --- +1 for the patch > Green Version Bubbles Are Selected Multiple Times For Patched Services > -- > > Key: AMBARI-21841 > URL: https://issues.apache.org/jira/browse/AMBARI-21841 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21841.patch, AMBARI-21841_trunk.patch > > > STR: > Install HDP 2.6.0.0 with ZK and Storm > Patch Storm to HDP 2.6.0.1 > Install a MAINT VDF for 2.6.1.0 where: > ZK's version is 2.6.1.0 > Storm's version is 2.6.0.1 > Because the VDF declares that Storm's version is 2.6.0.1, we won't upgrade > it. However, the Stacks and Versions page shows both the version numbers for > Storm for 2.6.0.1 and 2.6.1.0 as being green. This is incorrect - a service > should only ever have the version it's on be highlighted. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21844) JN Wizard fails if there is an issue with Datanode start.
[ https://issues.apache.org/jira/browse/AMBARI-21844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-21844: - Resolution: Fixed Status: Resolved (was: Patch Available) > JN Wizard fails if there is an issue with Datanode start. > - > > Key: AMBARI-21844 > URL: https://issues.apache.org/jira/browse/AMBARI-21844 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21844_branch-2.6.patch, AMBARI-21844.patch > > > *PROBLEM* > JN wizard fails if there is an issue with the datanode start at the final > step of the wizard when its suppose to bring up the services > *DESCRIPTION* > We had bad disks on a couple of DN and at the final state where the JN wizard > was suppose to bring up all the services it failed with errors. After this > the only option was to go ahead and cancel the wizard to proceed as the next > tab was greyed out. This is a bad user experience. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21844) JN Wizard fails if there is an issue with Datanode start.
[ https://issues.apache.org/jira/browse/AMBARI-21844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145774#comment-16145774 ] Aleksandr Kovalenko commented on AMBARI-21844: -- committed to trunk and branch-2.6 > JN Wizard fails if there is an issue with Datanode start. > - > > Key: AMBARI-21844 > URL: https://issues.apache.org/jira/browse/AMBARI-21844 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21844_branch-2.6.patch, AMBARI-21844.patch > > > *PROBLEM* > JN wizard fails if there is an issue with the datanode start at the final > step of the wizard when its suppose to bring up the services > *DESCRIPTION* > We had bad disks on a couple of DN and at the final state where the JN wizard > was suppose to bring up all the services it failed with errors. After this > the only option was to go ahead and cancel the wizard to proceed as the next > tab was greyed out. This is a bad user experience. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21842) PATCH and MAINT Orchestrations Should Only Invoke stack-select On Specific Packages
[
https://issues.apache.org/jira/browse/AMBARI-21842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145764#comment-16145764
]
Hudson commented on AMBARI-21842:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7957 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7957/])
AMBARI-21842 - PATCH and MAINT Orchestrations Should Only Invoke (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b300f504c4e39b5eff1df85255b238517f1d6f49])
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/stack_select.py
* (add) ambari-server/src/test/python/TestStackSelect.py
> PATCH and MAINT Orchestrations Should Only Invoke stack-select On Specific
> Packages
> ---
>
> Key: AMBARI-21842
> URL: https://issues.apache.org/jira/browse/AMBARI-21842
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21842.patch
>
>
> During a {{PATCH}} or {{MAINT}} upgrade, the agents are invoking
> {{stack_select}} as if it was a {{STANDARD}} upgrade.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21308) Log Search UI GA
[
https://issues.apache.org/jira/browse/AMBARI-21308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145758#comment-16145758
]
Hadoop QA commented on AMBARI-21308:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12884296/AMBARI-21308_merge.patch
against trunk revision .
{color:red}-1 @author{color}. The patch appears to contain 1 @author tags
which the Hadoop community has agreed to not allow in code contributions.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 javac{color}. The patch appears to cause the [build to
fail|https://builds.apache.org/job/Ambari-trunk-test-patch/12096//artifact/patch-work/patchJavacWarnings.txt].
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12096//console
This message is automatically generated.
> Log Search UI GA
>
>
> Key: AMBARI-21308
> URL: https://issues.apache.org/jira/browse/AMBARI-21308
> Project: Ambari
> Issue Type: Epic
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-21308_merge.patch
>
>
> This Epic tracks the implementation of the new Log Search UI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21841) Green Version Bubbles Are Selected Multiple Times For Patched Services
[ https://issues.apache.org/jira/browse/AMBARI-21841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21841: - Assignee: Antonenko Alexander Status: Patch Available (was: Open) > Green Version Bubbles Are Selected Multiple Times For Patched Services > -- > > Key: AMBARI-21841 > URL: https://issues.apache.org/jira/browse/AMBARI-21841 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21841.patch, AMBARI-21841_trunk.patch > > > STR: > Install HDP 2.6.0.0 with ZK and Storm > Patch Storm to HDP 2.6.0.1 > Install a MAINT VDF for 2.6.1.0 where: > ZK's version is 2.6.1.0 > Storm's version is 2.6.0.1 > Because the VDF declares that Storm's version is 2.6.0.1, we won't upgrade > it. However, the Stacks and Versions page shows both the version numbers for > Storm for 2.6.0.1 and 2.6.1.0 as being green. This is incorrect - a service > should only ever have the version it's on be highlighted. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21841) Green Version Bubbles Are Selected Multiple Times For Patched Services
[ https://issues.apache.org/jira/browse/AMBARI-21841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21841: - Attachment: AMBARI-21841_trunk.patch > Green Version Bubbles Are Selected Multiple Times For Patched Services > -- > > Key: AMBARI-21841 > URL: https://issues.apache.org/jira/browse/AMBARI-21841 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21841.patch, AMBARI-21841_trunk.patch > > > STR: > Install HDP 2.6.0.0 with ZK and Storm > Patch Storm to HDP 2.6.0.1 > Install a MAINT VDF for 2.6.1.0 where: > ZK's version is 2.6.1.0 > Storm's version is 2.6.0.1 > Because the VDF declares that Storm's version is 2.6.0.1, we won't upgrade > it. However, the Stacks and Versions page shows both the version numbers for > Storm for 2.6.0.1 and 2.6.1.0 as being green. This is incorrect - a service > should only ever have the version it's on be highlighted. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21842) PATCH and MAINT Orchestrations Should Only Invoke stack-select On Specific Packages
[
https://issues.apache.org/jira/browse/AMBARI-21842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145744#comment-16145744
]
Hudson commented on AMBARI-21842:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #79 (See
[https://builds.apache.org/job/Ambari-branch-2.6/79/])
AMBARI-21842 - PATCH and MAINT Orchestrations Should Only Invoke (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=22fe5ffaec5b4450262e83565031cdbbbf8b9a61])
* (edit)
ambari-server/src/main/resources/stacks/BigInsights/4.2.5/services/HDFS/package/scripts/journalnode.py
* (edit)
ambari-server/src/main/resources/stacks/BigInsights/4.2.5/services/HDFS/package/scripts/namenode.py
* (add) ambari-server/src/test/python/TestStackSelect.py
* (edit)
ambari-server/src/main/resources/stacks/BigInsights/4.2.5/services/HDFS/package/scripts/hdfs_client.py
* (edit)
ambari-server/src/main/resources/stacks/BigInsights/4.2.5/services/HDFS/package/scripts/snamenode.py
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/stack_select.py
* (edit)
ambari-server/src/main/resources/stacks/BigInsights/4.2.5/services/HDFS/package/scripts/nfsgateway.py
* (edit)
ambari-server/src/main/resources/stacks/BigInsights/4.2.5/services/OOZIE/package/scripts/oozie_client.py
* (edit)
ambari-server/src/main/resources/stacks/BigInsights/4.2.5/services/HDFS/package/scripts/datanode.py
* (edit)
ambari-server/src/main/resources/stacks/BigInsights/4.2.5/services/OOZIE/package/scripts/oozie_server.py
> PATCH and MAINT Orchestrations Should Only Invoke stack-select On Specific
> Packages
> ---
>
> Key: AMBARI-21842
> URL: https://issues.apache.org/jira/browse/AMBARI-21842
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21842.patch
>
>
> During a {{PATCH}} or {{MAINT}} upgrade, the agents are invoking
> {{stack_select}} as if it was a {{STANDARD}} upgrade.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21308) Log Search UI GA
[ https://issues.apache.org/jira/browse/AMBARI-21308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-21308: -- Attachment: (was: AMBARI-21308_merge.patch) > Log Search UI GA > > > Key: AMBARI-21308 > URL: https://issues.apache.org/jira/browse/AMBARI-21308 > Project: Ambari > Issue Type: Epic > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-21308_merge.patch > > > This Epic tracks the implementation of the new Log Search UI. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21308) Log Search UI GA
[ https://issues.apache.org/jira/browse/AMBARI-21308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-21308: -- Attachment: AMBARI-21308_merge.patch > Log Search UI GA > > > Key: AMBARI-21308 > URL: https://issues.apache.org/jira/browse/AMBARI-21308 > Project: Ambari > Issue Type: Epic > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-21308_merge.patch > > > This Epic tracks the implementation of the new Log Search UI. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21308) Log Search UI GA
[
https://issues.apache.org/jira/browse/AMBARI-21308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145676#comment-16145676
]
Hadoop QA commented on AMBARI-21308:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12884289/AMBARI-21308_merge.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/12095//console
This message is automatically generated.
> Log Search UI GA
>
>
> Key: AMBARI-21308
> URL: https://issues.apache.org/jira/browse/AMBARI-21308
> Project: Ambari
> Issue Type: Epic
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-21308_merge.patch
>
>
> This Epic tracks the implementation of the new Log Search UI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21842) PATCH and MAINT Orchestrations Should Only Invoke stack-select On Specific Packages
[
https://issues.apache.org/jira/browse/AMBARI-21842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21842:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> PATCH and MAINT Orchestrations Should Only Invoke stack-select On Specific
> Packages
> ---
>
> Key: AMBARI-21842
> URL: https://issues.apache.org/jira/browse/AMBARI-21842
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21842.patch
>
>
> During a {{PATCH}} or {{MAINT}} upgrade, the agents are invoking
> {{stack_select}} as if it was a {{STANDARD}} upgrade.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21843) Database consistency check fails after upgrade to ambari 2.6.0
[
https://issues.apache.org/jira/browse/AMBARI-21843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145664#comment-16145664
]
Hadoop QA commented on AMBARI-21843:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12884266/AMBARI-21843.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/12093//console
This message is automatically generated.
> Database consistency check fails after upgrade to ambari 2.6.0
> --
>
> Key: AMBARI-21843
> URL: https://issues.apache.org/jira/browse/AMBARI-21843
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21843.patch
>
>
> Here we need to fix two issues:
> 1) Table "clusterconfigmapping" was removed in ambari-2.6.0 (dropping it
> during upgrade). But db consistency check still using this table to get some
> data. After upgrade it fails because "clusterconfigmapping" doesn't exist.
> Need to reimplement checks which are using this table.
> 2) Db consistency check doesn't show any information for user about errors,
> in casse when table doesn't exist. You can check that with
> "clusterconfigmapping"
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21844) JN Wizard fails if there is an issue with Datanode start.
[ https://issues.apache.org/jira/browse/AMBARI-21844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145646#comment-16145646 ] Hudson commented on AMBARI-21844: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #78 (See [https://builds.apache.org/job/Ambari-branch-2.6/78/]) AMBARI-21844. JN Wizard fails if there is an issue with Datanode start (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=44ab107560ec0dca8f54b5fe79644a6a36551cba]) * (edit) ambari-web/app/controllers/main/admin/highAvailability/journalNode/step8_controller.js > JN Wizard fails if there is an issue with Datanode start. > - > > Key: AMBARI-21844 > URL: https://issues.apache.org/jira/browse/AMBARI-21844 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21844_branch-2.6.patch, AMBARI-21844.patch > > > *PROBLEM* > JN wizard fails if there is an issue with the datanode start at the final > step of the wizard when its suppose to bring up the services > *DESCRIPTION* > We had bad disks on a couple of DN and at the final state where the JN wizard > was suppose to bring up all the services it failed with errors. After this > the only option was to go ahead and cancel the wizard to proceed as the next > tab was greyed out. This is a bad user experience. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21844) JN Wizard fails if there is an issue with Datanode start.
[ https://issues.apache.org/jira/browse/AMBARI-21844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145635#comment-16145635 ] Hudson commented on AMBARI-21844: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7956 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7956/]) AMBARI-21844. JN Wizard fails if there is an issue with Datanode start (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=00479043de7cacd82aae571ff89e1364fcc13623]) * (edit) ambari-web/app/controllers/main/admin/highAvailability/journalNode/step8_controller.js > JN Wizard fails if there is an issue with Datanode start. > - > > Key: AMBARI-21844 > URL: https://issues.apache.org/jira/browse/AMBARI-21844 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21844_branch-2.6.patch, AMBARI-21844.patch > > > *PROBLEM* > JN wizard fails if there is an issue with the datanode start at the final > step of the wizard when its suppose to bring up the services > *DESCRIPTION* > We had bad disks on a couple of DN and at the final state where the JN wizard > was suppose to bring up all the services it failed with errors. After this > the only option was to go ahead and cancel the wizard to proceed as the next > tab was greyed out. This is a bad user experience. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21308) Log Search UI GA
[ https://issues.apache.org/jira/browse/AMBARI-21308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-21308: -- Status: Patch Available (was: Open) > Log Search UI GA > > > Key: AMBARI-21308 > URL: https://issues.apache.org/jira/browse/AMBARI-21308 > Project: Ambari > Issue Type: Epic > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-21308_merge.patch > > > This Epic tracks the implementation of the new Log Search UI. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21308) Log Search UI GA
[ https://issues.apache.org/jira/browse/AMBARI-21308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-21308: -- Attachment: AMBARI-21308_merge.patch > Log Search UI GA > > > Key: AMBARI-21308 > URL: https://issues.apache.org/jira/browse/AMBARI-21308 > Project: Ambari > Issue Type: Epic > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-21308_merge.patch > > > This Epic tracks the implementation of the new Log Search UI. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21841) Green Version Bubbles Are Selected Multiple Times For Patched Services
[ https://issues.apache.org/jira/browse/AMBARI-21841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21841: - Attachment: AMBARI-21841.patch > Green Version Bubbles Are Selected Multiple Times For Patched Services > -- > > Key: AMBARI-21841 > URL: https://issues.apache.org/jira/browse/AMBARI-21841 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21841.patch > > > STR: > Install HDP 2.6.0.0 with ZK and Storm > Patch Storm to HDP 2.6.0.1 > Install a MAINT VDF for 2.6.1.0 where: > ZK's version is 2.6.1.0 > Storm's version is 2.6.0.1 > Because the VDF declares that Storm's version is 2.6.0.1, we won't upgrade > it. However, the Stacks and Versions page shows both the version numbers for > Storm for 2.6.0.1 and 2.6.1.0 as being green. This is incorrect - a service > should only ever have the version it's on be highlighted. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-21845) Log Search UI: add filter by hostname for service logs
[ https://issues.apache.org/jira/browse/AMBARI-21845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk resolved AMBARI-21845. --- Resolution: Fixed Committed to branch-feature-logsearch-ui > Log Search UI: add filter by hostname for service logs > -- > > Key: AMBARI-21845 > URL: https://issues.apache.org/jira/browse/AMBARI-21845 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-21845.patch > > > Service logs should be filtered by hostname. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21845) Log Search UI: add filter by hostname for service logs
[ https://issues.apache.org/jira/browse/AMBARI-21845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-21845: -- Attachment: AMBARI-21845.patch > Log Search UI: add filter by hostname for service logs > -- > > Key: AMBARI-21845 > URL: https://issues.apache.org/jira/browse/AMBARI-21845 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-21845.patch > > > Service logs should be filtered by hostname. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21844) JN Wizard fails if there is an issue with Datanode start.
[
https://issues.apache.org/jira/browse/AMBARI-21844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145554#comment-16145554
]
Hadoop QA commented on AMBARI-21844:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12884269/AMBARI-21844.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/12092//console
This message is automatically generated.
> JN Wizard fails if there is an issue with Datanode start.
> -
>
> Key: AMBARI-21844
> URL: https://issues.apache.org/jira/browse/AMBARI-21844
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.1
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21844_branch-2.6.patch, AMBARI-21844.patch
>
>
> *PROBLEM*
> JN wizard fails if there is an issue with the datanode start at the final
> step of the wizard when its suppose to bring up the services
> *DESCRIPTION*
> We had bad disks on a couple of DN and at the final state where the JN wizard
> was suppose to bring up all the services it failed with errors. After this
> the only option was to go ahead and cancel the wizard to proceed as the next
> tab was greyed out. This is a bad user experience.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21845) Log Search UI: add filter by hostname for service logs
Andrii Babiichuk created AMBARI-21845: - Summary: Log Search UI: add filter by hostname for service logs Key: AMBARI-21845 URL: https://issues.apache.org/jira/browse/AMBARI-21845 Project: Ambari Issue Type: Task Components: ambari-logsearch Affects Versions: 3.0.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Fix For: 3.0.0 Service logs should be filtered by hostname. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21844) JN Wizard fails if there is an issue with Datanode start.
[
https://issues.apache.org/jira/browse/AMBARI-21844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145511#comment-16145511
]
Hadoop QA commented on AMBARI-21844:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12884269/AMBARI-21844.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12091//console
This message is automatically generated.
> JN Wizard fails if there is an issue with Datanode start.
> -
>
> Key: AMBARI-21844
> URL: https://issues.apache.org/jira/browse/AMBARI-21844
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.1
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21844_branch-2.6.patch, AMBARI-21844.patch
>
>
> *PROBLEM*
> JN wizard fails if there is an issue with the datanode start at the final
> step of the wizard when its suppose to bring up the services
> *DESCRIPTION*
> We had bad disks on a couple of DN and at the final state where the JN wizard
> was suppose to bring up all the services it failed with errors. After this
> the only option was to go ahead and cancel the wizard to proceed as the next
> tab was greyed out. This is a bad user experience.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21837) Admin Versions page is missing repository URL
[ https://issues.apache.org/jira/browse/AMBARI-21837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145495#comment-16145495 ] Hudson commented on AMBARI-21837: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7955 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7955/]) AMBARI-21837 Admin Versions page is missing repository URL. (atkach) (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ff3a095bc98c7abff4b706e780c9b31d7519fa8e]) * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/Stack.js > Admin Versions page is missing repository URL > - > > Key: AMBARI-21837 > URL: https://issues.apache.org/jira/browse/AMBARI-21837 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.6.0 > > Attachments: AMBARI-21837.patch, AMBARI-21837_trunk.patch, Screen > Shot 2017-08-28 at 12.33.22 PM.png > > > The Admin Stacks page is missing URL. See screenshot. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21840) Upgrade pre-checks failing to run on trunk
[ https://issues.apache.org/jira/browse/AMBARI-21840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145496#comment-16145496 ] Hudson commented on AMBARI-21840: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7955 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7955/]) AMBARI-21840 Upgrade pre-checks failing to run on trunk (dgrinenko) (hapylestat: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6f713da58b2ddf4c9a988648503df99293dde477]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/UpgradeContext.java > Upgrade pre-checks failing to run on trunk > -- > > Key: AMBARI-21840 > URL: https://issues.apache.org/jira/browse/AMBARI-21840 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: trunk >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-21840.patch > > > UpgradeChecks\repository_version_id is not being passed to as part of > predicate to UpgradeChecks resource at UpgradeContext -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21844) JN Wizard fails if there is an issue with Datanode start.
[ https://issues.apache.org/jira/browse/AMBARI-21844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145429#comment-16145429 ] Andrii Babiichuk commented on AMBARI-21844: --- +1 for the patch > JN Wizard fails if there is an issue with Datanode start. > - > > Key: AMBARI-21844 > URL: https://issues.apache.org/jira/browse/AMBARI-21844 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21844_branch-2.6.patch, AMBARI-21844.patch > > > *PROBLEM* > JN wizard fails if there is an issue with the datanode start at the final > step of the wizard when its suppose to bring up the services > *DESCRIPTION* > We had bad disks on a couple of DN and at the final state where the JN wizard > was suppose to bring up all the services it failed with errors. After this > the only option was to go ahead and cancel the wizard to proceed as the next > tab was greyed out. This is a bad user experience. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21844) JN Wizard fails if there is an issue with Datanode start.
[ https://issues.apache.org/jira/browse/AMBARI-21844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-21844: - Attachment: AMBARI-21844_branch-2.6.patch > JN Wizard fails if there is an issue with Datanode start. > - > > Key: AMBARI-21844 > URL: https://issues.apache.org/jira/browse/AMBARI-21844 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21844_branch-2.6.patch, AMBARI-21844.patch > > > *PROBLEM* > JN wizard fails if there is an issue with the datanode start at the final > step of the wizard when its suppose to bring up the services > *DESCRIPTION* > We had bad disks on a couple of DN and at the final state where the JN wizard > was suppose to bring up all the services it failed with errors. After this > the only option was to go ahead and cancel the wizard to proceed as the next > tab was greyed out. This is a bad user experience. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21844) JN Wizard fails if there is an issue with Datanode start.
[ https://issues.apache.org/jira/browse/AMBARI-21844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-21844: - Attachment: AMBARI-21844.patch > JN Wizard fails if there is an issue with Datanode start. > - > > Key: AMBARI-21844 > URL: https://issues.apache.org/jira/browse/AMBARI-21844 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21844_branch-2.6.patch, AMBARI-21844.patch > > > *PROBLEM* > JN wizard fails if there is an issue with the datanode start at the final > step of the wizard when its suppose to bring up the services > *DESCRIPTION* > We had bad disks on a couple of DN and at the final state where the JN wizard > was suppose to bring up all the services it failed with errors. After this > the only option was to go ahead and cancel the wizard to proceed as the next > tab was greyed out. This is a bad user experience. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21844) JN Wizard fails if there is an issue with Datanode start.
[ https://issues.apache.org/jira/browse/AMBARI-21844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-21844: - Status: Patch Available (was: Open) > JN Wizard fails if there is an issue with Datanode start. > - > > Key: AMBARI-21844 > URL: https://issues.apache.org/jira/browse/AMBARI-21844 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21844_branch-2.6.patch, AMBARI-21844.patch > > > *PROBLEM* > JN wizard fails if there is an issue with the datanode start at the final > step of the wizard when its suppose to bring up the services > *DESCRIPTION* > We had bad disks on a couple of DN and at the final state where the JN wizard > was suppose to bring up all the services it failed with errors. After this > the only option was to go ahead and cancel the wizard to proceed as the next > tab was greyed out. This is a bad user experience. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21837) Admin Versions page is missing repository URL
[ https://issues.apache.org/jira/browse/AMBARI-21837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145420#comment-16145420 ] Hudson commented on AMBARI-21837: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #77 (See [https://builds.apache.org/job/Ambari-branch-2.6/77/]) AMBARI-21837 Admin Versions page is missing repository URL. (atkach) (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=45241712076f059f4d7bf36d231572a2ea4084cb]) * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/Stack.js > Admin Versions page is missing repository URL > - > > Key: AMBARI-21837 > URL: https://issues.apache.org/jira/browse/AMBARI-21837 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.6.0 > > Attachments: AMBARI-21837.patch, AMBARI-21837_trunk.patch, Screen > Shot 2017-08-28 at 12.33.22 PM.png > > > The Admin Stacks page is missing URL. See screenshot. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21828) Backend should sort repo_version by version string
[ https://issues.apache.org/jira/browse/AMBARI-21828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145415#comment-16145415 ] Hudson commented on AMBARI-21828: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7954 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7954/]) AMBARI-21828. The BE should be providing repository versions in the (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e16da830042e1fea011733da45b24fe6648ee7c2]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProviderTest.java > Backend should sort repo_version by version string > -- > > Key: AMBARI-21828 > URL: https://issues.apache.org/jira/browse/AMBARI-21828 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21828.patch > > > The BE should be providing repository versions in the order of version string. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21844) JN Wizard fails if there is an issue with Datanode start.
Aleksandr Kovalenko created AMBARI-21844: Summary: JN Wizard fails if there is an issue with Datanode start. Key: AMBARI-21844 URL: https://issues.apache.org/jira/browse/AMBARI-21844 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.1 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Priority: Critical Fix For: 2.6.0 *PROBLEM* JN wizard fails if there is an issue with the datanode start at the final step of the wizard when its suppose to bring up the services *DESCRIPTION* We had bad disks on a couple of DN and at the final state where the JN wizard was suppose to bring up all the services it failed with errors. After this the only option was to go ahead and cancel the wizard to proceed as the next tab was greyed out. This is a bad user experience. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21843) Database consistency check fails after upgrade to ambari 2.6.0
[ https://issues.apache.org/jira/browse/AMBARI-21843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-21843: --- Attachment: AMBARI-21843.patch > Database consistency check fails after upgrade to ambari 2.6.0 > -- > > Key: AMBARI-21843 > URL: https://issues.apache.org/jira/browse/AMBARI-21843 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21843.patch > > > Here we need to fix two issues: > 1) Table "clusterconfigmapping" was removed in ambari-2.6.0 (dropping it > during upgrade). But db consistency check still using this table to get some > data. After upgrade it fails because "clusterconfigmapping" doesn't exist. > Need to reimplement checks which are using this table. > 2) Db consistency check doesn't show any information for user about errors, > in casse when table doesn't exist. You can check that with > "clusterconfigmapping" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21843) Database consistency check fails after upgrade to ambari 2.6.0
[ https://issues.apache.org/jira/browse/AMBARI-21843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-21843: --- Status: Patch Available (was: Open) > Database consistency check fails after upgrade to ambari 2.6.0 > -- > > Key: AMBARI-21843 > URL: https://issues.apache.org/jira/browse/AMBARI-21843 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21843.patch > > > Here we need to fix two issues: > 1) Table "clusterconfigmapping" was removed in ambari-2.6.0 (dropping it > during upgrade). But db consistency check still using this table to get some > data. After upgrade it fails because "clusterconfigmapping" doesn't exist. > Need to reimplement checks which are using this table. > 2) Db consistency check doesn't show any information for user about errors, > in casse when table doesn't exist. You can check that with > "clusterconfigmapping" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21843) Database consistency check fails after upgrade to ambari 2.6.0
Vitaly Brodetskyi created AMBARI-21843: -- Summary: Database consistency check fails after upgrade to ambari 2.6.0 Key: AMBARI-21843 URL: https://issues.apache.org/jira/browse/AMBARI-21843 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.6.0 Reporter: Vitaly Brodetskyi Assignee: Vitaly Brodetskyi Priority: Critical Fix For: 2.6.0 Here we need to fix two issues: 1) Table "clusterconfigmapping" was removed in ambari-2.6.0 (dropping it during upgrade). But db consistency check still using this table to get some data. After upgrade it fails because "clusterconfigmapping" doesn't exist. Need to reimplement checks which are using this table. 2) Db consistency check doesn't show any information for user about errors, in casse when table doesn't exist. You can check that with "clusterconfigmapping" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21842) PATCH and MAINT Orchestrations Should Only Invoke stack-select On Specific Packages
[
https://issues.apache.org/jira/browse/AMBARI-21842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21842:
-
Status: Patch Available (was: Open)
> PATCH and MAINT Orchestrations Should Only Invoke stack-select On Specific
> Packages
> ---
>
> Key: AMBARI-21842
> URL: https://issues.apache.org/jira/browse/AMBARI-21842
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21842.patch
>
>
> During a {{PATCH}} or {{MAINT}} upgrade, the agents are invoking
> {{stack_select}} as if it was a {{STANDARD}} upgrade.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21842) PATCH and MAINT Orchestrations Should Only Invoke stack-select On Specific Packages
[
https://issues.apache.org/jira/browse/AMBARI-21842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21842:
-
Attachment: AMBARI-21842.patch
> PATCH and MAINT Orchestrations Should Only Invoke stack-select On Specific
> Packages
> ---
>
> Key: AMBARI-21842
> URL: https://issues.apache.org/jira/browse/AMBARI-21842
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21842.patch
>
>
> During a {{PATCH}} or {{MAINT}} upgrade, the agents are invoking
> {{stack_select}} as if it was a {{STANDARD}} upgrade.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21842) PATCH and MAINT Orchestrations Should Only Invoke stack-select On Specific Packages
Jonathan Hurley created AMBARI-21842:
Summary: PATCH and MAINT Orchestrations Should Only Invoke
stack-select On Specific Packages
Key: AMBARI-21842
URL: https://issues.apache.org/jira/browse/AMBARI-21842
Project: Ambari
Issue Type: Bug
Affects Versions: 2.6.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Critical
Fix For: 2.6.0
During a {{PATCH}} or {{MAINT}} upgrade, the agents are invoking
{{stack_select}} as if it was a {{STANDARD}} upgrade.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21839) METRICS_MONITOR start is failing due to "ImportError: cannot import name _common"
[
https://issues.apache.org/jira/browse/AMBARI-21839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145381#comment-16145381
]
Hadoop QA commented on AMBARI-21839:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12884247/AMBARI-21839.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12090//console
This message is automatically generated.
> METRICS_MONITOR start is failing due to "ImportError: cannot import name
> _common"
> -
>
> Key: AMBARI-21839
> URL: https://issues.apache.org/jira/browse/AMBARI-21839
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21839.patch
>
>
> METRICS_MONITOR start is failing on one of the nodes of a cluster due to
> "ImportError: cannot import name _common".
> Ambari server version is 2.4.0.4.100. Seeing this error in 2.5.0.4.1 also.
> Redirecting psutils build output to log file to investigate the issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21840) Upgrade pre-checks failing to run on trunk
[ https://issues.apache.org/jira/browse/AMBARI-21840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-21840: - Status: Patch Available (was: In Progress) > Upgrade pre-checks failing to run on trunk > -- > > Key: AMBARI-21840 > URL: https://issues.apache.org/jira/browse/AMBARI-21840 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: trunk >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-21840.patch > > > UpgradeChecks\repository_version_id is not being passed to as part of > predicate to UpgradeChecks resource at UpgradeContext -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21840) Upgrade pre-checks failing to run on trunk
[ https://issues.apache.org/jira/browse/AMBARI-21840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145376#comment-16145376 ] Dmytro Grinenko commented on AMBARI-21840: -- Committed: ff3a095bc9..6f713da58b trunk -> trunk > Upgrade pre-checks failing to run on trunk > -- > > Key: AMBARI-21840 > URL: https://issues.apache.org/jira/browse/AMBARI-21840 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: trunk >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-21840.patch > > > UpgradeChecks\repository_version_id is not being passed to as part of > predicate to UpgradeChecks resource at UpgradeContext -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21840) Upgrade pre-checks failing to run on trunk
[ https://issues.apache.org/jira/browse/AMBARI-21840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-21840: - Resolution: Fixed Status: Resolved (was: Patch Available) > Upgrade pre-checks failing to run on trunk > -- > > Key: AMBARI-21840 > URL: https://issues.apache.org/jira/browse/AMBARI-21840 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: trunk >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-21840.patch > > > UpgradeChecks\repository_version_id is not being passed to as part of > predicate to UpgradeChecks resource at UpgradeContext -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21840) Upgrade pre-checks failing to run on trunk
[ https://issues.apache.org/jira/browse/AMBARI-21840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-21840: - Attachment: AMBARI-21840.patch > Upgrade pre-checks failing to run on trunk > -- > > Key: AMBARI-21840 > URL: https://issues.apache.org/jira/browse/AMBARI-21840 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: trunk >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-21840.patch > > > UpgradeChecks\repository_version_id is not being passed to as part of > predicate to UpgradeChecks resource at UpgradeContext -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21837) Admin Versions page is missing repository URL
[ https://issues.apache.org/jira/browse/AMBARI-21837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21837: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Admin Versions page is missing repository URL > - > > Key: AMBARI-21837 > URL: https://issues.apache.org/jira/browse/AMBARI-21837 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.6.0 > > Attachments: AMBARI-21837.patch, AMBARI-21837_trunk.patch, Screen > Shot 2017-08-28 at 12.33.22 PM.png > > > The Admin Stacks page is missing URL. See screenshot. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21837) Admin Versions page is missing repository URL
[ https://issues.apache.org/jira/browse/AMBARI-21837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145361#comment-16145361 ] Andrii Tkach commented on AMBARI-21837: --- committed to trunk and branch-2.6 > Admin Versions page is missing repository URL > - > > Key: AMBARI-21837 > URL: https://issues.apache.org/jira/browse/AMBARI-21837 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.6.0 > > Attachments: AMBARI-21837.patch, AMBARI-21837_trunk.patch, Screen > Shot 2017-08-28 at 12.33.22 PM.png > > > The Admin Stacks page is missing URL. See screenshot. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21839) METRICS_MONITOR start is failing due to "ImportError: cannot import name _common"
[
https://issues.apache.org/jira/browse/AMBARI-21839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145354#comment-16145354
]
Hadoop QA commented on AMBARI-21839:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12884247/AMBARI-21839.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12089//console
This message is automatically generated.
> METRICS_MONITOR start is failing due to "ImportError: cannot import name
> _common"
> -
>
> Key: AMBARI-21839
> URL: https://issues.apache.org/jira/browse/AMBARI-21839
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21839.patch
>
>
> METRICS_MONITOR start is failing on one of the nodes of a cluster due to
> "ImportError: cannot import name _common".
> Ambari server version is 2.4.0.4.100. Seeing this error in 2.5.0.4.1 also.
> Redirecting psutils build output to log file to investigate the issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-21828) Backend should sort repo_version by version string
[ https://issues.apache.org/jira/browse/AMBARI-21828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole resolved AMBARI-21828. Resolution: Fixed > Backend should sort repo_version by version string > -- > > Key: AMBARI-21828 > URL: https://issues.apache.org/jira/browse/AMBARI-21828 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21828.patch > > > The BE should be providing repository versions in the order of version string. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21828) Backend should sort repo_version by version string
[ https://issues.apache.org/jira/browse/AMBARI-21828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-21828: --- Attachment: AMBARI-21828.patch > Backend should sort repo_version by version string > -- > > Key: AMBARI-21828 > URL: https://issues.apache.org/jira/browse/AMBARI-21828 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21828.patch > > > The BE should be providing repository versions in the order of version string. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21841) Green Version Bubbles Are Selected Multiple Times For Patched Services
Antonenko Alexander created AMBARI-21841: Summary: Green Version Bubbles Are Selected Multiple Times For Patched Services Key: AMBARI-21841 URL: https://issues.apache.org/jira/browse/AMBARI-21841 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.6.0 Reporter: Antonenko Alexander Fix For: 2.6.0 STR: Install HDP 2.6.0.0 with ZK and Storm Patch Storm to HDP 2.6.0.1 Install a MAINT VDF for 2.6.1.0 where: ZK's version is 2.6.1.0 Storm's version is 2.6.0.1 Because the VDF declares that Storm's version is 2.6.0.1, we won't upgrade it. However, the Stacks and Versions page shows both the version numbers for Storm for 2.6.0.1 and 2.6.1.0 as being green. This is incorrect - a service should only ever have the version it's on be highlighted. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21828) Backend should sort repo_version by version string
[ https://issues.apache.org/jira/browse/AMBARI-21828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145322#comment-16145322 ] Hudson commented on AMBARI-21828: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #76 (See [https://builds.apache.org/job/Ambari-branch-2.6/76/]) AMBARI-21828. The BE should be providing repository versions in the (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7ca3a4d630eca9a2f06896b27c4ab4595e49af5e]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java > Backend should sort repo_version by version string > -- > > Key: AMBARI-21828 > URL: https://issues.apache.org/jira/browse/AMBARI-21828 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.0 > > > The BE should be providing repository versions in the order of version string. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21839) METRICS_MONITOR start is failing due to "ImportError: cannot import name _common"
[ https://issues.apache.org/jira/browse/AMBARI-21839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-21839: Status: Patch Available (was: In Progress) > METRICS_MONITOR start is failing due to "ImportError: cannot import name > _common" > - > > Key: AMBARI-21839 > URL: https://issues.apache.org/jira/browse/AMBARI-21839 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21839.patch > > > METRICS_MONITOR start is failing on one of the nodes of a cluster due to > "ImportError: cannot import name _common". > Ambari server version is 2.4.0.4.100. Seeing this error in 2.5.0.4.1 also. > Redirecting psutils build output to log file to investigate the issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21839) METRICS_MONITOR start is failing due to "ImportError: cannot import name _common"
[ https://issues.apache.org/jira/browse/AMBARI-21839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-21839: Attachment: AMBARI-21839.patch > METRICS_MONITOR start is failing due to "ImportError: cannot import name > _common" > - > > Key: AMBARI-21839 > URL: https://issues.apache.org/jira/browse/AMBARI-21839 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21839.patch > > > METRICS_MONITOR start is failing on one of the nodes of a cluster due to > "ImportError: cannot import name _common". > Ambari server version is 2.4.0.4.100. Seeing this error in 2.5.0.4.1 also. > Redirecting psutils build output to log file to investigate the issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21840) Upgrade pre-checks failing to run on trunk
Dmytro Grinenko created AMBARI-21840: Summary: Upgrade pre-checks failing to run on trunk Key: AMBARI-21840 URL: https://issues.apache.org/jira/browse/AMBARI-21840 Project: Ambari Issue Type: Bug Components: ambari-sever Affects Versions: trunk Reporter: Dmytro Grinenko Assignee: Dmytro Grinenko Priority: Critical Fix For: trunk UpgradeChecks\repository_version_id is not being passed to as part of predicate to UpgradeChecks resource at UpgradeContext -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21833) Add keberos service for 3.0.0 stack
[ https://issues.apache.org/jira/browse/AMBARI-21833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145277#comment-16145277 ] Hudson commented on AMBARI-21833: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7953 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7953/]) AMBARI-21833. Add keberos service for 3.0.0 stack (echekanskiy) (echekanskiy: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=41656481b231244b9bfe86ba24a6a3f258b9d17d]) * (add) ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-30/package/scripts/kerberos_client.py * (add) ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-30/package/scripts/kerberos_common.py * (add) ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-30/configuration/krb5-conf.xml * (add) ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-30/metainfo.xml * (add) ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-30/package/scripts/utils.py * (add) ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-30/package/scripts/params.py * (add) ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-30/configuration/kerberos-env.xml * (add) ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-30/package/scripts/service_check.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/KERBEROS/metainfo.xml * (add) ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-30/kerberos.json * (add) ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-30/properties/krb5_conf.j2 * (add) ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-30/package/scripts/status_params.py > Add keberos service for 3.0.0 stack > --- > > Key: AMBARI-21833 > URL: https://issues.apache.org/jira/browse/AMBARI-21833 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 3.0.0 > > Attachments: AMBARI-21833.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21837) Admin Versions page is missing repository URL
[
https://issues.apache.org/jira/browse/AMBARI-21837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145250#comment-16145250
]
Hadoop QA commented on AMBARI-21837:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12884234/AMBARI-21837_trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-admin.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12088//console
This message is automatically generated.
> Admin Versions page is missing repository URL
> -
>
> Key: AMBARI-21837
> URL: https://issues.apache.org/jira/browse/AMBARI-21837
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-21837.patch, AMBARI-21837_trunk.patch, Screen
> Shot 2017-08-28 at 12.33.22 PM.png
>
>
> The Admin Stacks page is missing URL. See screenshot.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21833) Add keberos service for 3.0.0 stack
[ https://issues.apache.org/jira/browse/AMBARI-21833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145224#comment-16145224 ] Eugene Chekanskiy commented on AMBARI-21833: 5388ae6..4165648 trunk -> trunk > Add keberos service for 3.0.0 stack > --- > > Key: AMBARI-21833 > URL: https://issues.apache.org/jira/browse/AMBARI-21833 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 3.0.0 > > Attachments: AMBARI-21833.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21833) Add keberos service for 3.0.0 stack
[ https://issues.apache.org/jira/browse/AMBARI-21833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Chekanskiy updated AMBARI-21833: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Add keberos service for 3.0.0 stack > --- > > Key: AMBARI-21833 > URL: https://issues.apache.org/jira/browse/AMBARI-21833 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 3.0.0 > > Attachments: AMBARI-21833.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21837) Admin Versions page is missing repository URL
[ https://issues.apache.org/jira/browse/AMBARI-21837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145210#comment-16145210 ] Aleksandr Kovalenko commented on AMBARI-21837: -- +1 for the patch > Admin Versions page is missing repository URL > - > > Key: AMBARI-21837 > URL: https://issues.apache.org/jira/browse/AMBARI-21837 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.6.0 > > Attachments: AMBARI-21837.patch, AMBARI-21837_trunk.patch, Screen > Shot 2017-08-28 at 12.33.22 PM.png > > > The Admin Stacks page is missing URL. See screenshot. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21838) Revert Icon Is Cutoff On Stacks and Versions Page
[ https://issues.apache.org/jira/browse/AMBARI-21838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145174#comment-16145174 ] Hudson commented on AMBARI-21838: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #75 (See [https://builds.apache.org/job/Ambari-branch-2.6/75/]) AMBARI-21838. Revert Icon Is Cutoff On Stacks and Versions Page (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=61d223a530a18c27d3c6aaf7dbf91eeed6ad2892]) * (edit) ambari-web/app/styles/stack_versions.less > Revert Icon Is Cutoff On Stacks and Versions Page > - > > Key: AMBARI-21838 > URL: https://issues.apache.org/jira/browse/AMBARI-21838 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21838.patch, Screen Shot 2017-08-28 at 1.51.53 > PM.png > > > Register a PATCH VDF with a longer name. You'll notice that the revert icon > is cutoff. Also, it doesn't seem to be utilizing an alpha channel as it > appears white in the background instead of grey. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21837) Admin Versions page is missing repository URL
[
https://issues.apache.org/jira/browse/AMBARI-21837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145170#comment-16145170
]
Hadoop QA commented on AMBARI-21837:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12884234/AMBARI-21837_trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-admin.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12087//console
This message is automatically generated.
> Admin Versions page is missing repository URL
> -
>
> Key: AMBARI-21837
> URL: https://issues.apache.org/jira/browse/AMBARI-21837
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-21837.patch, AMBARI-21837_trunk.patch, Screen
> Shot 2017-08-28 at 12.33.22 PM.png
>
>
> The Admin Stacks page is missing URL. See screenshot.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21839) METRICS_MONITOR start is failing due to "ImportError: cannot import name _common"
Dmytro Sen created AMBARI-21839: --- Summary: METRICS_MONITOR start is failing due to "ImportError: cannot import name _common" Key: AMBARI-21839 URL: https://issues.apache.org/jira/browse/AMBARI-21839 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.4.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Priority: Critical Fix For: 2.6.0 METRICS_MONITOR start is failing on one of the nodes of a cluster due to "ImportError: cannot import name _common". Ambari server version is 2.4.0.4.100. Seeing this error in 2.5.0.4.1 also. Redirecting psutils build output to log file to investigate the issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21837) Admin Versions page is missing repository URL
[ https://issues.apache.org/jira/browse/AMBARI-21837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21837: -- Attachment: AMBARI-21837_trunk.patch > Admin Versions page is missing repository URL > - > > Key: AMBARI-21837 > URL: https://issues.apache.org/jira/browse/AMBARI-21837 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.6.0 > > Attachments: AMBARI-21837.patch, AMBARI-21837_trunk.patch, Screen > Shot 2017-08-28 at 12.33.22 PM.png > > > The Admin Stacks page is missing URL. See screenshot. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21838) Revert Icon Is Cutoff On Stacks and Versions Page
[ https://issues.apache.org/jira/browse/AMBARI-21838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145125#comment-16145125 ] Antonenko Alexander commented on AMBARI-21838: -- Commited to branch-2.6 > Revert Icon Is Cutoff On Stacks and Versions Page > - > > Key: AMBARI-21838 > URL: https://issues.apache.org/jira/browse/AMBARI-21838 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21838.patch, Screen Shot 2017-08-28 at 1.51.53 > PM.png > > > Register a PATCH VDF with a longer name. You'll notice that the revert icon > is cutoff. Also, it doesn't seem to be utilizing an alpha channel as it > appears white in the background instead of grey. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
