[jira] [Created] (AMBARI-23229) Remove "Storm - Kafka-offset" Grafana dashboard if it is not supposed to work in Ambari 2.7
JaySenSharma created AMBARI-23229: - Summary: Remove "Storm - Kafka-offset" Grafana dashboard if it is not supposed to work in Ambari 2.7 Key: AMBARI-23229 URL: https://issues.apache.org/jira/browse/AMBARI-23229 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.6.1, 2.7.0 Reporter: JaySenSharma If "Storm - Kafka-offset" Grafana dashboard is not supposed to work in Ambari 2.7.0 then please remove it. We see that Kafka Spout metrics are available from Storm 2.0.0 and Storm 1.2.0 versions as per https://issues.apache.org/jira/browse/STORM-2867 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23228) "Storm - Kafka-offset" Grafana dashboard does not work and does not show proper error cause.
[
https://issues.apache.org/jira/browse/AMBARI-23228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
JaySenSharma updated AMBARI-23228:
--
Description:
In a fresh Ambari 2.6.1 setup when we try to access the "Storm -
Kafka-offset" Grafana dashboard then it shows errors.
{code:java}
Dashboard init failed
Template variables could not be initialized: Cannot read property 'then' of
undefined
{code}
- The "topic" dropdown menu does not show any topic name.
- When we check the browser "Developer Tools" --> "Console" output then we can
see the following error when accessing "Storm - Kafka-offset" Grafana dashboard:
{code:java}
TypeError: Cannot read property 'then' of undefined
at updateOptionsFromMetricFindQuery (app.ca0ab6f9.js:39)
at b (app.ca0ab6f9.js:16)
at i (app.ca0ab6f9.js:13)
at app.ca0ab6f9.js:13
at n.$eval (app.ca0ab6f9.js:13)
at n.$digest (app.ca0ab6f9.js:13)
at n.$apply (app.ca0ab6f9.js:13)
at f (app.ca0ab6f9.js:11)
at r (app.ca0ab6f9.js:11)
at XMLHttpRequest.v.onload (app.ca0ab6f9.js:11)
{code}
*Expectation:* Ambari should show meaningful messages in the Grafana UI
regarding the failure. Or if it is not able to find any particular metrics name.
.
was:
In a fresh Ambari 2.6.1 setup when we try to access the *"Storm -
Kafka-offset"* Grafana dashboard then it shows errors.
Dashboard init failed
Template variables could not be initialized: Cannot read property 'then' of
undefined
- The "topic" dropdown menu does not show any topic name.
- When we check the browser "Developer Tools" --> "Console" output then we can
see the following error when accessing "Storm - Kafka-offset" Grafana dashboard:
{code:java}
TypeError: Cannot read property 'then' of undefined
at updateOptionsFromMetricFindQuery (app.ca0ab6f9.js:39)
at b (app.ca0ab6f9.js:16)
at i (app.ca0ab6f9.js:13)
at app.ca0ab6f9.js:13
at n.$eval (app.ca0ab6f9.js:13)
at n.$digest (app.ca0ab6f9.js:13)
at n.$apply (app.ca0ab6f9.js:13)
at f (app.ca0ab6f9.js:11)
at r (app.ca0ab6f9.js:11)
at XMLHttpRequest.v.onload (app.ca0ab6f9.js:11)
{code}
> "Storm - Kafka-offset" Grafana dashboard does not work and does not show
> proper error cause.
>
>
> Key: AMBARI-23228
> URL: https://issues.apache.org/jira/browse/AMBARI-23228
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.6.1
>Reporter: JaySenSharma
>Priority: Blocker
>
> In a fresh Ambari 2.6.1 setup when we try to access the "Storm -
> Kafka-offset" Grafana dashboard then it shows errors.
> {code:java}
> Dashboard init failed
> Template variables could not be initialized: Cannot read property 'then' of
> undefined
> {code}
> - The "topic" dropdown menu does not show any topic name.
> - When we check the browser "Developer Tools" --> "Console" output then we
> can see the following error when accessing "Storm - Kafka-offset" Grafana
> dashboard:
> {code:java}
> TypeError: Cannot read property 'then' of undefined
> at updateOptionsFromMetricFindQuery (app.ca0ab6f9.js:39)
> at b (app.ca0ab6f9.js:16)
> at i (app.ca0ab6f9.js:13)
> at app.ca0ab6f9.js:13
> at n.$eval (app.ca0ab6f9.js:13)
> at n.$digest (app.ca0ab6f9.js:13)
> at n.$apply (app.ca0ab6f9.js:13)
> at f (app.ca0ab6f9.js:11)
> at r (app.ca0ab6f9.js:11)
> at XMLHttpRequest.v.onload (app.ca0ab6f9.js:11)
> {code}
> *Expectation:* Ambari should show meaningful messages in the Grafana UI
> regarding the failure. Or if it is not able to find any particular metrics
> name.
> .
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23228) "Storm - Kafka-offset" Grafana dashboard does not work and does not show proper error cause.
JaySenSharma created AMBARI-23228:
-
Summary: "Storm - Kafka-offset" Grafana dashboard does not work
and does not show proper error cause.
Key: AMBARI-23228
URL: https://issues.apache.org/jira/browse/AMBARI-23228
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: 2.6.1
Reporter: JaySenSharma
In a fresh Ambari 2.6.1 setup when we try to access the *"Storm -
Kafka-offset"* Grafana dashboard then it shows errors.
Dashboard init failed
Template variables could not be initialized: Cannot read property 'then' of
undefined
- The "topic" dropdown menu does not show any topic name.
- When we check the browser "Developer Tools" --> "Console" output then we can
see the following error when accessing "Storm - Kafka-offset" Grafana dashboard:
{code:java}
TypeError: Cannot read property 'then' of undefined
at updateOptionsFromMetricFindQuery (app.ca0ab6f9.js:39)
at b (app.ca0ab6f9.js:16)
at i (app.ca0ab6f9.js:13)
at app.ca0ab6f9.js:13
at n.$eval (app.ca0ab6f9.js:13)
at n.$digest (app.ca0ab6f9.js:13)
at n.$apply (app.ca0ab6f9.js:13)
at f (app.ca0ab6f9.js:11)
at r (app.ca0ab6f9.js:11)
at XMLHttpRequest.v.onload (app.ca0ab6f9.js:11)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23161) Invalid storage property value for zeppelin in stack HDP 2.6
[
https://issues.apache.org/jira/browse/AMBARI-23161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16397953#comment-16397953
]
Hudson commented on AMBARI-23161:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8855 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8855/])
[AMBARI-23161] Invalid storage property value for zeppelin in stack HDP
(github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=7a267d21eb1dd636be0e4563bba3046ca0d89dd3])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/services/stack_advisor.py
> Invalid storage property value for zeppelin in stack HDP 2.6
>
>
> Key: AMBARI-23161
> URL: https://issues.apache.org/jira/browse/AMBARI-23161
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.6.2
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> For stacks lower than HDP 2.6.3, property {{zeppelin.notebook.storage}}
> should have value {{org.apache.zeppelin.notebook.repo.VFSNotebookRepo}}. For
> stacks HDP 2.6.3 and higher this property should have value
> {{org.apache.zeppelin.notebook.repo.FileSystemNotebookRepo}}. As of now for
> all stacks HDP 2.6.x by default storage property will have value
> FileSystemNotebookRepo, it's not correct. So it should be fixed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23227) Pass service_group_name and service_name while creating Host Components.
[ https://issues.apache.org/jira/browse/AMBARI-23227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23227: Labels: pull-request-available (was: ) > Pass service_group_name and service_name while creating Host Components. > > > Key: AMBARI-23227 > URL: https://issues.apache.org/jira/browse/AMBARI-23227 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23227) Pass service_group_name and service_name while creating Host Components.
Ishan Bhatt created AMBARI-23227: Summary: Pass service_group_name and service_name while creating Host Components. Key: AMBARI-23227 URL: https://issues.apache.org/jira/browse/AMBARI-23227 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23226) Hide ambari-infra custom commands from the UI
[ https://issues.apache.org/jira/browse/AMBARI-23226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23226: Labels: pull-request-available (was: ) > Hide ambari-infra custom commands from the UI > - > > Key: AMBARI-23226 > URL: https://issues.apache.org/jira/browse/AMBARI-23226 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23200) Infra Solr - utility script to run infra-solr custom commands (migrate/backup/restore)
[ https://issues.apache.org/jira/browse/AMBARI-23200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23200: Labels: pull-request-available (was: ) > Infra Solr - utility script to run infra-solr custom commands > (migrate/backup/restore) > -- > > Key: AMBARI-23200 > URL: https://issues.apache.org/jira/browse/AMBARI-23200 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23226) Hide ambari-infra custom commands from the UI
Olivér Szabó created AMBARI-23226: - Summary: Hide ambari-infra custom commands from the UI Key: AMBARI-23226 URL: https://issues.apache.org/jira/browse/AMBARI-23226 Project: Ambari Issue Type: Bug Components: ambari-infra Affects Versions: 2.7.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23161) Invalid storage property value for zeppelin in stack HDP 2.6
[
https://issues.apache.org/jira/browse/AMBARI-23161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi resolved AMBARI-23161.
Resolution: Fixed
> Invalid storage property value for zeppelin in stack HDP 2.6
>
>
> Key: AMBARI-23161
> URL: https://issues.apache.org/jira/browse/AMBARI-23161
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.6.2
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> For stacks lower than HDP 2.6.3, property {{zeppelin.notebook.storage}}
> should have value {{org.apache.zeppelin.notebook.repo.VFSNotebookRepo}}. For
> stacks HDP 2.6.3 and higher this property should have value
> {{org.apache.zeppelin.notebook.repo.FileSystemNotebookRepo}}. As of now for
> all stacks HDP 2.6.x by default storage property will have value
> FileSystemNotebookRepo, it's not correct. So it should be fixed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23225) Ambari Server login fails due to TimelineMetricsCacheSizeOfEngine error in AMS perf branch.
[
https://issues.apache.org/jira/browse/AMBARI-23225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23225:
Labels: pull-request-available (was: )
> Ambari Server login fails due to TimelineMetricsCacheSizeOfEngine error in
> AMS perf branch.
> ---
>
> Key: AMBARI-23225
> URL: https://issues.apache.org/jira/browse/AMBARI-23225
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.7.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Labels: pull-request-available
>
> {code}
> java.lang.ClassCastException:
> org.apache.ambari.server.controller.metrics.timeline.cache.TimelineMetricsCacheSizeOfEngine
> cannot be cast to net.s
> f.ehcache.pool.SizeOfEngine
> at
> net.sf.ehcache.CacheManager.createSizeOfEngine(CacheManager.java:2068)
> at net.sf.ehcache.CacheManager.doInit(CacheManager.java:453)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-23216) Fix that Log Search for Ambari 2.6.2 should not require java8
[ https://issues.apache.org/jira/browse/AMBARI-23216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-23216. --- Resolution: Fixed > Fix that Log Search for Ambari 2.6.2 should not require java8 > - > > Key: AMBARI-23216 > URL: https://issues.apache.org/jira/browse/AMBARI-23216 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.6.2 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.6.2 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23218) Remove delete custom command from Ambari Infra Solr stack
[ https://issues.apache.org/jira/browse/AMBARI-23218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-23218. --- Resolution: Fixed > Remove delete custom command from Ambari Infra Solr stack > - > > Key: AMBARI-23218 > URL: https://issues.apache.org/jira/browse/AMBARI-23218 > Project: Ambari > Issue Type: Bug > Components: ambari-infra, ambari-server >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-23225) Ambari Server login fails due to TimelineMetricsCacheSizeOfEngine error in AMS perf branch.
[
https://issues.apache.org/jira/browse/AMBARI-23225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan reassigned AMBARI-23225:
--
Assignee: Aravindan Vijayan
> Ambari Server login fails due to TimelineMetricsCacheSizeOfEngine error in
> AMS perf branch.
> ---
>
> Key: AMBARI-23225
> URL: https://issues.apache.org/jira/browse/AMBARI-23225
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.7.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
>
> {code}
> java.lang.ClassCastException:
> org.apache.ambari.server.controller.metrics.timeline.cache.TimelineMetricsCacheSizeOfEngine
> cannot be cast to net.s
> f.ehcache.pool.SizeOfEngine
> at
> net.sf.ehcache.CacheManager.createSizeOfEngine(CacheManager.java:2068)
> at net.sf.ehcache.CacheManager.doInit(CacheManager.java:453)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23225) Ambari Server login fails due to TimelineMetricsCacheSizeOfEngine error in AMS perf branch.
Aravindan Vijayan created AMBARI-23225:
--
Summary: Ambari Server login fails due to
TimelineMetricsCacheSizeOfEngine error in AMS perf branch.
Key: AMBARI-23225
URL: https://issues.apache.org/jira/browse/AMBARI-23225
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: 2.7.0
Reporter: Aravindan Vijayan
{code}
java.lang.ClassCastException:
org.apache.ambari.server.controller.metrics.timeline.cache.TimelineMetricsCacheSizeOfEngine
cannot be cast to net.s
f.ehcache.pool.SizeOfEngine
at
net.sf.ehcache.CacheManager.createSizeOfEngine(CacheManager.java:2068)
at net.sf.ehcache.CacheManager.doInit(CacheManager.java:453)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23218) Remove delete custom command from Ambari Infra Solr stack
[ https://issues.apache.org/jira/browse/AMBARI-23218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16397588#comment-16397588 ] Hudson commented on AMBARI-23218: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8854 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8854/]) AMBARI-23218. ADDENDUM - Remove delete custom command from Ambari Infra (oleewere: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=8e6172a5281b739542e8bd94065c278ef2d6e9a2]) * (edit) ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/package/scripts/infra_solr.py AMBARI-23218. ADDENDUM2 - Remove delete custom command from Ambari Infra (oleewere: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=04b2b60cc34fb2214a254e932176feaeea47b102]) * (edit) ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/package/scripts/infra_solr.py > Remove delete custom command from Ambari Infra Solr stack > - > > Key: AMBARI-23218 > URL: https://issues.apache.org/jira/browse/AMBARI-23218 > Project: Ambari > Issue Type: Bug > Components: ambari-infra, ambari-server >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23224) Dependency check should ignore unknown services
[
https://issues.apache.org/jira/browse/AMBARI-23224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-23224:
---
Status: Patch Available (was: In Progress)
> Dependency check should ignore unknown services
> ---
>
> Key: AMBARI-23224
> URL: https://issues.apache.org/jira/browse/AMBARI-23224
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{BlueprintValidatorImpl}} throws NPE if encounters an unknown component.
> {noformat}
> at
> org.apache.ambari.server.topology.BlueprintValidatorImpl.validateHostGroup(BlueprintValidatorImpl.java:250)
> at
> org.apache.ambari.server.topology.BlueprintValidatorImpl.validateTopology(BlueprintValidatorImpl.java:70)
> at
> org.apache.ambari.server.topology.BlueprintImpl.validateTopology(BlueprintImpl.java:332)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23224) Dependency check should ignore unknown services
[
https://issues.apache.org/jira/browse/AMBARI-23224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23224:
Labels: pull-request-available (was: )
> Dependency check should ignore unknown services
> ---
>
> Key: AMBARI-23224
> URL: https://issues.apache.org/jira/browse/AMBARI-23224
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Labels: pull-request-available
> Fix For: 3.0.0
>
>
> {{BlueprintValidatorImpl}} throws NPE if encounters an unknown component.
> {noformat}
> at
> org.apache.ambari.server.topology.BlueprintValidatorImpl.validateHostGroup(BlueprintValidatorImpl.java:250)
> at
> org.apache.ambari.server.topology.BlueprintValidatorImpl.validateTopology(BlueprintValidatorImpl.java:70)
> at
> org.apache.ambari.server.topology.BlueprintImpl.validateTopology(BlueprintImpl.java:332)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23224) Dependency check should ignore unknown services
Doroszlai, Attila created AMBARI-23224:
--
Summary: Dependency check should ignore unknown services
Key: AMBARI-23224
URL: https://issues.apache.org/jira/browse/AMBARI-23224
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 3.0.0
Reporter: Doroszlai, Attila
Assignee: Doroszlai, Attila
Fix For: 3.0.0
{{BlueprintValidatorImpl}} throws NPE if encounters an unknown component.
{noformat}
at
org.apache.ambari.server.topology.BlueprintValidatorImpl.validateHostGroup(BlueprintValidatorImpl.java:250)
at
org.apache.ambari.server.topology.BlueprintValidatorImpl.validateTopology(BlueprintValidatorImpl.java:70)
at
org.apache.ambari.server.topology.BlueprintImpl.validateTopology(BlueprintImpl.java:332)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23223) Stack Mpack link broken in stacks api
Madhuvanthi Radhakrishnan created AMBARI-23223:
--
Summary: Stack Mpack link broken in stacks api
Key: AMBARI-23223
URL: https://issues.apache.org/jira/browse/AMBARI-23223
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 3.0.0
Reporter: Madhuvanthi Radhakrishnan
Assignee: Madhuvanthi Radhakrishnan
Fix For: 3.0.0
http://{{ambari_server}}:8080/api/v1/mpacks/3
version is empty
GET
[http://ambari_server:8080/api/v1/stacks//versions/1.0.0-b141|http://172.22.102.182:8080/api/v1/stacks/HDPCORE/versions/1.0.0-b141]
mpack is empty
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-22957) Stack Metainfo.xml should contain the osSpecifics tag. Add as part of metainfo generation.
[
https://issues.apache.org/jira/browse/AMBARI-22957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhuvanthi Radhakrishnan resolved AMBARI-22957.
Resolution: Fixed
> Stack Metainfo.xml should contain the osSpecifics tag. Add as part of
> metainfo generation.
> --
>
> Key: AMBARI-22957
> URL: https://issues.apache.org/jira/browse/AMBARI-22957
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> {noformat}
>
>
> any
>
>
>
hdpcore
>
>
false
>
>
>
>
> {noformat}
> This should be added to metainfo.xml for each stack during its generation.
> The only package that we now install is yum install which takes
> dependencies on all modules of the mpack.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-22997) cluster-settings.xml is not present in /var/lib/ambari-server/resources post ambari installation
[ https://issues.apache.org/jira/browse/AMBARI-22997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan resolved AMBARI-22997. Resolution: Fixed > cluster-settings.xml is not present in /var/lib/ambari-server/resources post > ambari installation > > > Key: AMBARI-22997 > URL: https://issues.apache.org/jira/browse/AMBARI-22997 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-21603) Deploy cluster with HDP-3.0.0.0 mpack in Core Service Group
[ https://issues.apache.org/jira/browse/AMBARI-21603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan resolved AMBARI-21603. Resolution: Fixed > Deploy cluster with HDP-3.0.0.0 mpack in Core Service Group > --- > > Key: AMBARI-21603 > URL: https://issues.apache.org/jira/browse/AMBARI-21603 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23187) Add custom actions for: format NN, format ZK and bootStrapStandBy
[ https://issues.apache.org/jira/browse/AMBARI-23187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16397521#comment-16397521 ] Hudson commented on AMBARI-23187: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8853 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8853/]) AMBARI-23187. Add custom actions for: format NN, format ZK and bootStrap (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=a55fbba2fc984ffbfec65c016ad2e6d215435fa9]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StackServiceComponentResourceProvider.java * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/zkfc_slave.py * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/metainfo.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/CustomCommandDefinition.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/StackServiceComponentResponse.java * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py > Add custom actions for: format NN, format ZK and bootStrapStandBy > - > > Key: AMBARI-23187 > URL: https://issues.apache.org/jira/browse/AMBARI-23187 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-23187.patch, AMBARI-23187.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Automate the actions needed for the wizard so UI can make a call to perform > the commands on the new NN hosts and setup federation. > Favoring automation here over manual steps like in the past NN HA wizard > forced user to do this instead of Ambari doing it for them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23187) Add custom actions for: format NN, format ZK and bootStrapStandBy
[ https://issues.apache.org/jira/browse/AMBARI-23187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23187: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Add custom actions for: format NN, format ZK and bootStrapStandBy > - > > Key: AMBARI-23187 > URL: https://issues.apache.org/jira/browse/AMBARI-23187 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-23187.patch, AMBARI-23187.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Automate the actions needed for the wizard so UI can make a call to perform > the commands on the new NN hosts and setup federation. > Favoring automation here over manual steps like in the past NN HA wizard > forced user to do this instead of Ambari doing it for them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23222) Ambari-agent fails to connect to server with two_way_auth enabled
[ https://issues.apache.org/jira/browse/AMBARI-23222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23222: Labels: pull-request-available (was: ) > Ambari-agent fails to connect to server with two_way_auth enabled > - > > Key: AMBARI-23222 > URL: https://issues.apache.org/jira/browse/AMBARI-23222 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-23222.patch > > > ERROR 2018-03-13 17:15:04,264 security.py:122 - Could not connect to > wss://ctr-e138-1518143905142-94896-01-02.hwx.site:8441/agent/stomp/v1 > Traceback (most recent call last): > File "/usr/lib/ambari-agent/lib/ambari_agent/security.py", line 113, in > establish_connection > conn.start() > File "/usr/lib/ambari-agent/lib/ambari_stomp/connect.py", line 46, in > start > self.transport.start() > File "/usr/lib/ambari-agent/lib/ambari_stomp/transport.py", line 109, > in start > self.attempt_connection() > File "/usr/lib/ambari-agent/lib/ambari_stomp/adapter/websocket.py", > line 89, in attempt_connection > self.ws.connect() > File "/usr/lib/ambari-agent/lib/ambari_ws4py/client/__init__.py", line > 216, in connect > self.sock.connect(self.bind_addr) > File "/usr/lib64/python2.7/ssl.py", line 869, in connect > self._real_connect(addr, False) > File "/usr/lib64/python2.7/ssl.py", line 860, in _real_connect > self.do_handshake() > File "/usr/lib64/python2.7/ssl.py", line 833, in do_handshake > self._sslobj.do_handshake() > SSLError: [SSL: SSLV3_ALERT_BAD_CERTIFICATE] sslv3 alert bad certificate > (_ssl.c:579) > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23222) Ambari-agent fails to connect to server with two_way_auth enabled
[ https://issues.apache.org/jira/browse/AMBARI-23222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23222: - Attachment: AMBARI-23222.patch > Ambari-agent fails to connect to server with two_way_auth enabled > - > > Key: AMBARI-23222 > URL: https://issues.apache.org/jira/browse/AMBARI-23222 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.0 > > Attachments: AMBARI-23222.patch > > > ERROR 2018-03-13 17:15:04,264 security.py:122 - Could not connect to > wss://ctr-e138-1518143905142-94896-01-02.hwx.site:8441/agent/stomp/v1 > Traceback (most recent call last): > File "/usr/lib/ambari-agent/lib/ambari_agent/security.py", line 113, in > establish_connection > conn.start() > File "/usr/lib/ambari-agent/lib/ambari_stomp/connect.py", line 46, in > start > self.transport.start() > File "/usr/lib/ambari-agent/lib/ambari_stomp/transport.py", line 109, > in start > self.attempt_connection() > File "/usr/lib/ambari-agent/lib/ambari_stomp/adapter/websocket.py", > line 89, in attempt_connection > self.ws.connect() > File "/usr/lib/ambari-agent/lib/ambari_ws4py/client/__init__.py", line > 216, in connect > self.sock.connect(self.bind_addr) > File "/usr/lib64/python2.7/ssl.py", line 869, in connect > self._real_connect(addr, False) > File "/usr/lib64/python2.7/ssl.py", line 860, in _real_connect > self.do_handshake() > File "/usr/lib64/python2.7/ssl.py", line 833, in do_handshake > self._sslobj.do_handshake() > SSLError: [SSL: SSLV3_ALERT_BAD_CERTIFICATE] sslv3 alert bad certificate > (_ssl.c:579) > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23222) Ambari-agent fails to connect to server with two_way_auth enabled
[ https://issues.apache.org/jira/browse/AMBARI-23222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23222: - Status: Patch Available (was: Open) > Ambari-agent fails to connect to server with two_way_auth enabled > - > > Key: AMBARI-23222 > URL: https://issues.apache.org/jira/browse/AMBARI-23222 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.0 > > Attachments: AMBARI-23222.patch > > > ERROR 2018-03-13 17:15:04,264 security.py:122 - Could not connect to > wss://ctr-e138-1518143905142-94896-01-02.hwx.site:8441/agent/stomp/v1 > Traceback (most recent call last): > File "/usr/lib/ambari-agent/lib/ambari_agent/security.py", line 113, in > establish_connection > conn.start() > File "/usr/lib/ambari-agent/lib/ambari_stomp/connect.py", line 46, in > start > self.transport.start() > File "/usr/lib/ambari-agent/lib/ambari_stomp/transport.py", line 109, > in start > self.attempt_connection() > File "/usr/lib/ambari-agent/lib/ambari_stomp/adapter/websocket.py", > line 89, in attempt_connection > self.ws.connect() > File "/usr/lib/ambari-agent/lib/ambari_ws4py/client/__init__.py", line > 216, in connect > self.sock.connect(self.bind_addr) > File "/usr/lib64/python2.7/ssl.py", line 869, in connect > self._real_connect(addr, False) > File "/usr/lib64/python2.7/ssl.py", line 860, in _real_connect > self.do_handshake() > File "/usr/lib64/python2.7/ssl.py", line 833, in do_handshake > self._sslobj.do_handshake() > SSLError: [SSL: SSLV3_ALERT_BAD_CERTIFICATE] sslv3 alert bad certificate > (_ssl.c:579) > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23222) Ambari-agent fails to connect to server with two_way_auth enabled
Andrew Onischuk created AMBARI-23222: Summary: Ambari-agent fails to connect to server with two_way_auth enabled Key: AMBARI-23222 URL: https://issues.apache.org/jira/browse/AMBARI-23222 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.7.0 Attachments: AMBARI-23222.patch ERROR 2018-03-13 17:15:04,264 security.py:122 - Could not connect to wss://ctr-e138-1518143905142-94896-01-02.hwx.site:8441/agent/stomp/v1 Traceback (most recent call last): File "/usr/lib/ambari-agent/lib/ambari_agent/security.py", line 113, in establish_connection conn.start() File "/usr/lib/ambari-agent/lib/ambari_stomp/connect.py", line 46, in start self.transport.start() File "/usr/lib/ambari-agent/lib/ambari_stomp/transport.py", line 109, in start self.attempt_connection() File "/usr/lib/ambari-agent/lib/ambari_stomp/adapter/websocket.py", line 89, in attempt_connection self.ws.connect() File "/usr/lib/ambari-agent/lib/ambari_ws4py/client/__init__.py", line 216, in connect self.sock.connect(self.bind_addr) File "/usr/lib64/python2.7/ssl.py", line 869, in connect self._real_connect(addr, False) File "/usr/lib64/python2.7/ssl.py", line 860, in _real_connect self.do_handshake() File "/usr/lib64/python2.7/ssl.py", line 833, in do_handshake self._sslobj.do_handshake() SSLError: [SSL: SSLV3_ALERT_BAD_CERTIFICATE] sslv3 alert bad certificate (_ssl.c:579) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22969) When host is registering while adding it, Remove Selected button shows up on selecting host
[ https://issues.apache.org/jira/browse/AMBARI-22969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16397263#comment-16397263 ] Hudson commented on AMBARI-22969: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8852 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8852/]) AMBARI-22969. When host is registering while adding it, Remove Selected (aantonenko: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=ccc5a662accae926f57581cb9842e310dd560d5a]) * (edit) ambari-web/test/views/wizard/step3_view_test.js * (edit) ambari-web/app/views/wizard/step3_view.js * (edit) ambari-web/app/templates/wizard/step3.hbs AMBARI-22969. When host is registering while adding it, Remove Selected (aantonenko: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=7b3d7a96cf838777475b870978d84197cefdc770]) * (edit) ambari-web/app/views/wizard/step3_view.js > When host is registering while adding it, Remove Selected button shows up on > selecting host > --- > > Key: AMBARI-22969 > URL: https://issues.apache.org/jira/browse/AMBARI-22969 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Vivek Rathod >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Time Spent: 40m > Remaining Estimate: 0h > > When host is registering(or installing agent) while adding it, Remove > Selected button shows up when you select a host > STR: > Try to add host to a cluster. When it is registering, the remove icon(on the > right side of the host name) is disabled, which is expected. But at that > time, if you select the host checkbox, then Remove Selected button is > available which allows user to delete the host while it is registering to the > server -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23220) Customise Services : Alignment not proper for Select Config group Pop up and overriden text box
[ https://issues.apache.org/jira/browse/AMBARI-23220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23220: Labels: pull-request-available (was: ) > Customise Services : Alignment not proper for Select Config group Pop up and > overriden text box > --- > > Key: AMBARI-23220 > URL: https://issues.apache.org/jira/browse/AMBARI-23220 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: Screen1.png, Screen2.png > > > There are two issues w.r.t alignment > *Issue#1* > 1) Go to All Configurations Tab under Customise Services Step of Install > Wizard. > 2) Select any property say under HDFS 'DataNode directories permission' . > Click '+' to override. > 3) Select a new config group > 4) The new text box which appears to provide overridden value is misaligned > with original one. > *Issue#2* > Following same steps as in Issue#1. Check the warning 'You are changing not > default group, please select config group to which you want to save dependent > configs from other services +Show Details+' at page top. > Click Show Details link. > A pop up opens. The text which appears on the pop up is not aligned properly. > Attaching screenshots for both issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23221) Before-start hook is failed when hdfs is not available in cluster
Eugene Chekanskiy created AMBARI-23221: -- Summary: Before-start hook is failed when hdfs is not available in cluster Key: AMBARI-23221 URL: https://issues.apache.org/jira/browse/AMBARI-23221 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0 Reporter: Eugene Chekanskiy Assignee: Eugene Chekanskiy Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-22819) Issues with storm jaas files and recursive ch_(mod/own) calls
[
https://issues.apache.org/jira/browse/AMBARI-22819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Chekanskiy resolved AMBARI-22819.
Resolution: Fixed
> Issues with storm jaas files and recursive ch_(mod/own) calls
> -
>
> Key: AMBARI-22819
> URL: https://issues.apache.org/jira/browse/AMBARI-22819
> Project: Ambari
> Issue Type: Bug
> Components: security
>Affects Versions: 2.5.1
>Reporter: Sandeep Nemuri
>Assignee: Eugene Chekanskiy
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Post disabling the kerberos Ambari is not deleting the storm_jaas.conf and
> client_jaas.conf files from storm conf directory.
> Offset lag section in Storm UI is not populating because of the jaas conf.
> {code}
> Unable to get offset lags for kafka. Reason:
> org.apache.zookeeper.KeeperException$AuthFailedException: KeeperErrorCode =
> AuthFailed for /brokers/topics/hortonworks/partitions at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:123) at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:51) at
> org.apache.zookeeper.ZooKeeper.getChildren(ZooKeeper.java:1590) at
> org.apache.curator.shaded.framework.imps.GetChildrenBuilderImpl$3.call(GetChildrenBuilderImpl.java:230)
> at
> org.apache.curator.shaded.framework.imps.GetChildrenBuilderImpl$3.call(GetChildrenBuilderImpl.java:219)
> at org.apache.curator.shaded.RetryLoop.callWithRetry(RetryLoop.java:109) at
> org.apache.curator.shaded.framework.imps.GetChildrenBuilderImpl.pathInForeground(GetChildrenBuilderImpl.java:216)
> at
> org.apache.curator.shaded.framework.imps.GetChildrenBuilderImpl.forPath(GetChildrenBuilderImpl.java:207)
> at
> org.apache.curator.shaded.framework.imps.GetChildrenBuilderImpl.forPath(GetChildrenBuilderImpl.java:40)
> at
> org.apache.storm.kafka.monitor.KafkaOffsetLagUtil.getLeadersAndTopicPartitions(KafkaOffsetLagUtil.java:323)
> at
> org.apache.storm.kafka.monitor.KafkaOffsetLagUtil.getOffsetLags(KafkaOffsetLagUtil.java:257)
> at
> org.apache.storm.kafka.monitor.KafkaOffsetLagUtil.main(KafkaOffsetLagUtil.java:126)
> {code}
> Storm's /usr/hdp/current/storm-client/bin/storm-kafka-monitor checks if the
> storm_jaas.conf exists in storm configuration directory and then uses it.
> {code:java}
> STORM_JAAS_CONF_PARAM=""
> JAAS_FILE="${STORM_CONF_DIR}/storm_jaas.conf"
> if [ -f $JAAS_FILE ]; then
> STORM_JAAS_CONF_PARAM="-Djava.security.auth.login.config=${JAAS_FILE}"
> fi
> {code}
> Issue will be resolved if we delete the storm_jaas.conf file manually.
> As well storm jaas configs must be readable by world to allow some mpacks
> work properly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22969) When host is registering while adding it, Remove Selected button shows up on selecting host
[ https://issues.apache.org/jira/browse/AMBARI-22969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22969: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > When host is registering while adding it, Remove Selected button shows up on > selecting host > --- > > Key: AMBARI-22969 > URL: https://issues.apache.org/jira/browse/AMBARI-22969 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Vivek Rathod >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Time Spent: 0.5h > Remaining Estimate: 0h > > When host is registering(or installing agent) while adding it, Remove > Selected button shows up when you select a host > STR: > Try to add host to a cluster. When it is registering, the remove icon(on the > right side of the host name) is disabled, which is expected. But at that > time, if you select the host checkbox, then Remove Selected button is > available which allows user to delete the host while it is registering to the > server -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23220) Customise Services : Alignment not proper for Select Config group Pop up and overriden text box
[ https://issues.apache.org/jira/browse/AMBARI-23220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-23220: -- Attachment: Screen2.png Screen1.png > Customise Services : Alignment not proper for Select Config group Pop up and > overriden text box > --- > > Key: AMBARI-23220 > URL: https://issues.apache.org/jira/browse/AMBARI-23220 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Fix For: 2.7.0 > > Attachments: Screen1.png, Screen2.png > > > There are two issues w.r.t alignment > *Issue#1* > 1) Go to All Configurations Tab under Customise Services Step of Install > Wizard. > 2) Select any property say under HDFS 'DataNode directories permission' . > Click '+' to override. > 3) Select a new config group > 4) The new text box which appears to provide overridden value is misaligned > with original one. > *Issue#2* > Following same steps as in Issue#1. Check the warning 'You are changing not > default group, please select config group to which you want to save dependent > configs from other services +Show Details+' at page top. > Click Show Details link. > A pop up opens. The text which appears on the pop up is not aligned properly. > Attaching screenshots for both issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23220) Customise Services : Alignment not proper for Select Config group Pop up and overriden text box
Andrii Tkach created AMBARI-23220: - Summary: Customise Services : Alignment not proper for Select Config group Pop up and overriden text box Key: AMBARI-23220 URL: https://issues.apache.org/jira/browse/AMBARI-23220 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.7.0 There are two issues w.r.t alignment *Issue#1* 1) Go to All Configurations Tab under Customise Services Step of Install Wizard. 2) Select any property say under HDFS 'DataNode directories permission' . Click '+' to override. 3) Select a new config group 4) The new text box which appears to provide overridden value is misaligned with original one. *Issue#2* Following same steps as in Issue#1. Check the warning 'You are changing not default group, please select config group to which you want to save dependent configs from other services +Show Details+' at page top. Click Show Details link. A pop up opens. The text which appears on the pop up is not aligned properly. Attaching screenshots for both issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23210) Customise Services: Alignment issue while adding new custom password property
[ https://issues.apache.org/jira/browse/AMBARI-23210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16397129#comment-16397129 ] Hudson commented on AMBARI-23210: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8851 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8851/]) AMBARI-23210 Customise Services: Alignment issue while adding new custom (1963907+atkach: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=508a609c064da59f037489f7e35980f3e315a293]) * (edit) ambari-web/app/views/common/controls_view.js * (edit) ambari-web/app/styles/service_configurations.less > Customise Services: Alignment issue while adding new custom password property > - > > Key: AMBARI-23210 > URL: https://issues.apache.org/jira/browse/AMBARI-23210 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: Screen Shot 2018-03-01 at 11.50.56 AM.png, Screen Shot > 2018-03-01 at 11.52.57 AM.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > When a new custom property is added whose Type is Password , the two > textboxes that appear are not properly aligned with Remove button. > The length of the text boxes should be reduced so that both > textboxes(password/confirm password) fit in the same line along with remove > button. > Attached screenshot from old and new UI. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-18952) Register BackupObserver and BackupHFileCleaner
[ https://issues.apache.org/jira/browse/AMBARI-18952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-18952: Description: Over in HBASE-14417, two new classes are added. org.apache.hadoop.hbase.backup.BackupHFileCleaner should be registered through hbase.master.hfilecleaner.plugins . It is responsible for keeping bulk loaded hfiles so that incremental backup can pick them up. org.apache.hadoop.hbase.backup.BackupObserver should be registered through hbase.coprocessor.region.classes It is notified when bulk load completes and writes records into hbase:backup table. was: Over in HBASE-14417, two new classes are added. org.apache.hadoop.hbase.backup.BackupHFileCleaner should be registered through hbase.master.hfilecleaner.plugins . It is responsible for keeping bulk loaded hfiles so that incremental backup can pick them up. org.apache.hadoop.hbase.backup.BackupObserver should be registered through hbase.coprocessor.region.classes It is notified when bulk load completes and writes records into hbase:backup table. > Register BackupObserver and BackupHFileCleaner > -- > > Key: AMBARI-18952 > URL: https://issues.apache.org/jira/browse/AMBARI-18952 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu >Priority: Major > > Over in HBASE-14417, two new classes are added. > org.apache.hadoop.hbase.backup.BackupHFileCleaner should be registered > through hbase.master.hfilecleaner.plugins . It is responsible for keeping > bulk loaded hfiles so that incremental backup can pick them up. > org.apache.hadoop.hbase.backup.BackupObserver should be registered through > hbase.coprocessor.region.classes > It is notified when bulk load completes and writes records into hbase:backup > table. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22342) Automate the addition of hbase backup related config entries
[
https://issues.apache.org/jira/browse/AMBARI-22342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated AMBARI-22342:
Description:
When user tries to run hbase backup without proper configuration:
{code}
Please make sure that backup is enabled on the cluster. To enable backup, in
hbase-site.xml, set:
hbase.backup.enable=true
hbase.master.logcleaner.plugins=YOUR_PLUGINS,org.apache.hadoop.hbase.backup.master.BackupLogCleaner
hbase.procedure.master.classes=YOUR_CLASSES,org.apache.hadoop.hbase.backup.master.LogRollMasterProcedureManager
hbase.procedure.regionserver.classes=YOUR_CLASSES,org.apache.hadoop.hbase.backup.regionserver.LogRollRegionServerProcedureManager
hbase.coprocessor.region.classes=YOUR_CLASSES,org.apache.hadoop.hbase.backup.BackupObserver
{code}
User needs to retrieve the current values for the configs, if any, and add
backup related entries.
Ambari should provide automation in putting the above in place.
was:
When user tries to run hbase backup without proper configuration:
{code}
Please make sure that backup is enabled on the cluster. To enable backup, in
hbase-site.xml, set:
hbase.backup.enable=true
hbase.master.logcleaner.plugins=YOUR_PLUGINS,org.apache.hadoop.hbase.backup.master.BackupLogCleaner
hbase.procedure.master.classes=YOUR_CLASSES,org.apache.hadoop.hbase.backup.master.LogRollMasterProcedureManager
hbase.procedure.regionserver.classes=YOUR_CLASSES,org.apache.hadoop.hbase.backup.regionserver.LogRollRegionServerProcedureManager
hbase.coprocessor.region.classes=YOUR_CLASSES,org.apache.hadoop.hbase.backup.BackupObserver
{code}
User needs to retrieve the current values for the configs, if any, and add
backup related entries.
Ambari should provide automation in putting the above in place.
> Automate the addition of hbase backup related config entries
>
>
> Key: AMBARI-22342
> URL: https://issues.apache.org/jira/browse/AMBARI-22342
> Project: Ambari
> Issue Type: Improvement
>Reporter: Ted Yu
>Priority: Major
>
> When user tries to run hbase backup without proper configuration:
> {code}
> Please make sure that backup is enabled on the cluster. To enable backup, in
> hbase-site.xml, set:
> hbase.backup.enable=true
> hbase.master.logcleaner.plugins=YOUR_PLUGINS,org.apache.hadoop.hbase.backup.master.BackupLogCleaner
> hbase.procedure.master.classes=YOUR_CLASSES,org.apache.hadoop.hbase.backup.master.LogRollMasterProcedureManager
> hbase.procedure.regionserver.classes=YOUR_CLASSES,org.apache.hadoop.hbase.backup.regionserver.LogRollRegionServerProcedureManager
> hbase.coprocessor.region.classes=YOUR_CLASSES,org.apache.hadoop.hbase.backup.BackupObserver
> {code}
> User needs to retrieve the current values for the configs, if any, and add
> backup related entries.
> Ambari should provide automation in putting the above in place.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23218) Remove delete custom command from Ambari Infra Solr stack
[ https://issues.apache.org/jira/browse/AMBARI-23218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16397070#comment-16397070 ] Hudson commented on AMBARI-23218: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8850 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8850/]) AMBARI-23218. Remove delete custom command from Ambari Infra Solr stack. (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=8eb901f8540fdfdf4dcd65b0039c3fae4afe75cc]) * (edit) ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/metainfo.xml * (edit) ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/package/scripts/collection.py > Remove delete custom command from Ambari Infra Solr stack > - > > Key: AMBARI-23218 > URL: https://issues.apache.org/jira/browse/AMBARI-23218 > Project: Ambari > Issue Type: Bug > Components: ambari-infra, ambari-server >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23210) Customise Services: Alignment issue while adding new custom password property
[ https://issues.apache.org/jira/browse/AMBARI-23210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16397006#comment-16397006 ] Andrii Tkach commented on AMBARI-23210: --- committed to trunk > Customise Services: Alignment issue while adding new custom password property > - > > Key: AMBARI-23210 > URL: https://issues.apache.org/jira/browse/AMBARI-23210 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: Screen Shot 2018-03-01 at 11.50.56 AM.png, Screen Shot > 2018-03-01 at 11.52.57 AM.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > When a new custom property is added whose Type is Password , the two > textboxes that appear are not properly aligned with Remove button. > The length of the text boxes should be reduced so that both > textboxes(password/confirm password) fit in the same line along with remove > button. > Attached screenshot from old and new UI. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23210) Customise Services: Alignment issue while adding new custom password property
[ https://issues.apache.org/jira/browse/AMBARI-23210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach resolved AMBARI-23210. --- Resolution: Fixed > Customise Services: Alignment issue while adding new custom password property > - > > Key: AMBARI-23210 > URL: https://issues.apache.org/jira/browse/AMBARI-23210 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: Screen Shot 2018-03-01 at 11.50.56 AM.png, Screen Shot > 2018-03-01 at 11.52.57 AM.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > When a new custom property is added whose Type is Password , the two > textboxes that appear are not properly aligned with Remove button. > The length of the text boxes should be reduced so that both > textboxes(password/confirm password) fit in the same line along with remove > button. > Attached screenshot from old and new UI. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23219) Set mariadb the default database for Hive on Amazon Linux 2 distribution
[ https://issues.apache.org/jira/browse/AMBARI-23219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23219: Labels: pull-request-available (was: ) > Set mariadb the default database for Hive on Amazon Linux 2 distribution > > > Key: AMBARI-23219 > URL: https://issues.apache.org/jira/browse/AMBARI-23219 > Project: Ambari > Issue Type: Task > Components: ambari-agent, ambari-server >Affects Versions: 2.7.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22969) When host is registering while adding it, Remove Selected button shows up on selecting host
[ https://issues.apache.org/jira/browse/AMBARI-22969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22969: Labels: pull-request-available (was: ) > When host is registering while adding it, Remove Selected button shows up on > selecting host > --- > > Key: AMBARI-22969 > URL: https://issues.apache.org/jira/browse/AMBARI-22969 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Vivek Rathod >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: trunk > > > When host is registering(or installing agent) while adding it, Remove > Selected button shows up when you select a host > STR: > Try to add host to a cluster. When it is registering, the remove icon(on the > right side of the host name) is disabled, which is expected. But at that > time, if you select the host checkbox, then Remove Selected button is > available which allows user to delete the host while it is registering to the > server -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-23214) StackAdvisor Error while enabling back security : invalid literal for int() with base 10
[
https://issues.apache.org/jira/browse/AMBARI-23214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas reassigned AMBARI-23214:
-
Assignee: Robert Levas
> StackAdvisor Error while enabling back security : invalid literal for int()
> with base 10
>
>
> Key: AMBARI-23214
> URL: https://issues.apache.org/jira/browse/AMBARI-23214
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: Vivek Rathod
>Assignee: Robert Levas
>Priority: Major
> Fix For: 2.6.2
>
>
> StackAdvisor Error while enabling back security : invalid literal for int()
> with base 10
>
> STR:
> 1) Install cluster with Ambari 2.6.1.0
> 2) Upgrade to Ambari 2.6.2.0
> 3) Regenerate keytabs for missing components and start all services
> 4) Disable security
> 5) Enable NN and RM HA
> 6) Enable Security. On enabling security. On configure identities page, there
> is a stackadvisor error
>
> {code}
> 12 Mar 2018 06:29:08,144 INFO [ambari-client-thread-67] StackAdvisorRunner:71
> - advisor script stderr: Traceback (most recent call last):
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 173,
> in
> main(sys.argv)
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 121,
> in main
> result = stackAdvisor.recommendConfigurations(services, hosts)
> File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
> line 776, in recommendConfigurations
> calculation(configurations, clusterSummary, services, hosts)
> File
> "/var/lib/ambari-server/resources/scripts/./../stacks/HDP/2.6/services/stack_advisor.py",
> line 125, in recommendZEPPELINConfigurations
> if compare_versions(full_stack_version, '2.6.3.0') >= 0:
> File
> "/usr/lib/ambari-server/lib/resource_management/libraries/functions/version.py",
> line 83, in compare_versions
> return cmp(_normalize(v1, desired_segments=max_segments), _normalize(v2,
> desired_segments=max_segments))
> File
> "/usr/lib/ambari-server/lib/resource_management/libraries/functions/version.py",
> line 34, in _normalize
> return [int(x) for x in v_list]
> ValueError: invalid literal for int() with base 10: ''
> 12 Mar 2018 06:29:08,145 WARN [ambari-client-thread-67]
> AbstractResourceProvider:97 - Error occured during recommendation
> org.apache.ambari.server.api.services.stackadvisor.StackAdvisorException:
> Stack Advisor reported an error: ValueError: invalid literal for int() with
> base 10: ''
> StdOut file: /var/run/ambari-server/stack-recommendations/4/stackadvisor.out
> StdErr file: /var/run/ambari-server/stack-recommendations/4/stackadvisor.err
> at
> org.apache.ambari.server.api.services.stackadvisor.StackAdvisorRunner.runScript(StackAdvisorRunner.java:96)
> at
> org.apache.ambari.server.api.services.stackadvisor.commands.StackAdvisorCommand.invoke(StackAdvisorCommand.java:297)
> at
> org.apache.ambari.server.api.services.stackadvisor.StackAdvisorHelper.recommend(StackAdvisorHelper.java:113)
> at
> org.apache.ambari.server.controller.internal.RecommendationResourceProvider.createResources(RecommendationResourceProvider.java:92)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298)
> at
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
> at
> org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37)
> at
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
> at
> org.apache.ambari.server.api.services.RecommendationService.getRecommendation(RecommendationService.java:59)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> 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
>
[jira] [Updated] (AMBARI-22969) When host is registering while adding it, Remove Selected button shows up on selecting host
[ https://issues.apache.org/jira/browse/AMBARI-22969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22969: - Status: Patch Available (was: Open) > When host is registering while adding it, Remove Selected button shows up on > selecting host > --- > > Key: AMBARI-22969 > URL: https://issues.apache.org/jira/browse/AMBARI-22969 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Vivek Rathod >Assignee: Antonenko Alexander >Priority: Major > Fix For: trunk > > > When host is registering(or installing agent) while adding it, Remove > Selected button shows up when you select a host > STR: > Try to add host to a cluster. When it is registering, the remove icon(on the > right side of the host name) is disabled, which is expected. But at that > time, if you select the host checkbox, then Remove Selected button is > available which allows user to delete the host while it is registering to the > server -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-22969) When host is registering while adding it, Remove Selected button shows up on selecting host
[ https://issues.apache.org/jira/browse/AMBARI-22969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-22969: Assignee: Antonenko Alexander > When host is registering while adding it, Remove Selected button shows up on > selecting host > --- > > Key: AMBARI-22969 > URL: https://issues.apache.org/jira/browse/AMBARI-22969 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Vivek Rathod >Assignee: Antonenko Alexander >Priority: Major > Fix For: trunk > > > When host is registering(or installing agent) while adding it, Remove > Selected button shows up when you select a host > STR: > Try to add host to a cluster. When it is registering, the remove icon(on the > right side of the host name) is disabled, which is expected. But at that > time, if you select the host checkbox, then Remove Selected button is > available which allows user to delete the host while it is registering to the > server -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23165) Install Wizard/Customise Services - Clear Filters is not working
[ https://issues.apache.org/jira/browse/AMBARI-23165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16396892#comment-16396892 ] Hudson commented on AMBARI-23165: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8849 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8849/]) AMBARI-23165. Install Wizard/Customise Services - Clear Filters is not (aantonenko: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=23c48c5c83549319bb33a99480fa7b70ff01270b]) * (edit) ambari-web/app/views/common/filter_combo_cleanable.js > Install Wizard/Customise Services - Clear Filters is not working > > > Key: AMBARI-23165 > URL: https://issues.apache.org/jira/browse/AMBARI-23165 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23165) Install Wizard/Customise Services - Clear Filters is not working
[ https://issues.apache.org/jira/browse/AMBARI-23165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16396861#comment-16396861 ] Antonenko Alexander commented on AMBARI-23165: -- Committed to trunk > Install Wizard/Customise Services - Clear Filters is not working > > > Key: AMBARI-23165 > URL: https://issues.apache.org/jira/browse/AMBARI-23165 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23165) Install Wizard/Customise Services - Clear Filters is not working
[ https://issues.apache.org/jira/browse/AMBARI-23165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-23165: - Resolution: Fixed Status: Resolved (was: Patch Available) > Install Wizard/Customise Services - Clear Filters is not working > > > Key: AMBARI-23165 > URL: https://issues.apache.org/jira/browse/AMBARI-23165 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23165) Install Wizard/Customise Services - Clear Filters is not working
[ https://issues.apache.org/jira/browse/AMBARI-23165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-23165: - Status: Patch Available (was: Open) > Install Wizard/Customise Services - Clear Filters is not working > > > Key: AMBARI-23165 > URL: https://issues.apache.org/jira/browse/AMBARI-23165 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23210) Customise Services: Alignment issue while adding new custom password property
[ https://issues.apache.org/jira/browse/AMBARI-23210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23210: Labels: pull-request-available (was: ) > Customise Services: Alignment issue while adding new custom password property > - > > Key: AMBARI-23210 > URL: https://issues.apache.org/jira/browse/AMBARI-23210 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: Screen Shot 2018-03-01 at 11.50.56 AM.png, Screen Shot > 2018-03-01 at 11.52.57 AM.png > > > When a new custom property is added whose Type is Password , the two > textboxes that appear are not properly aligned with Remove button. > The length of the text boxes should be reduced so that both > textboxes(password/confirm password) fit in the same line along with remove > button. > Attached screenshot from old and new UI. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23208) NN Federation Wizard: rename custom command
[ https://issues.apache.org/jira/browse/AMBARI-23208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16396820#comment-16396820 ] Hudson commented on AMBARI-23208: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8848 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8848/]) AMBARI-23208. NN Federation Wizard: rename custom command (akovalenko) (aleksandrkovalenko: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=eb2361376144e445e6fe461773b474f0bc30f8c0]) * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/utils/ajax/ajax.js * (edit) ambari-web/app/controllers/main/admin/federation/step3_controller.js * (edit) ambari-web/app/templates/main/admin/federation/step1.hbs * (edit) ambari-web/app/controllers/main/admin/federation/step1_controller.js > NN Federation Wizard: rename custom command > --- > > Key: AMBARI-23208 > URL: https://issues.apache.org/jira/browse/AMBARI-23208 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Rename BOOTSTRAP custom command to BOOTSTRAP_STANDBY. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23219) Set mariadb the default database for Hive on Amazon Linux 2 distribution
Krisztian Kasa created AMBARI-23219: --- Summary: Set mariadb the default database for Hive on Amazon Linux 2 distribution Key: AMBARI-23219 URL: https://issues.apache.org/jira/browse/AMBARI-23219 Project: Ambari Issue Type: Task Components: ambari-agent, ambari-server Affects Versions: 2.7.0 Reporter: Krisztian Kasa Assignee: Krisztian Kasa Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22897) Tez view button doesnt works in ambari hive views 1.5
[ https://issues.apache.org/jira/browse/AMBARI-22897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16396796#comment-16396796 ] Hudson commented on AMBARI-22897: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #657 (See [https://builds.apache.org/job/Ambari-branch-2.6/657/]) AMBARI-22897 - Tez view button doesnt works in ambari views 1.5(asnaik) (asnaik: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=1b0b7ae2f83cd40dd00cf8d58c7405b8595d4927]) * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/controllers/application.js * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/templates/index.hbs * (delete) contrib/views/hive-next/src/main/resources/ui/hive-web/app/controllers/settings.js * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/services/settings.js * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/styles/app.scss * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/tests/unit/routes/visual-explain-test.js * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/controllers/query-tabs.js * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/app/templates/components/query-settings.hbs * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/app/components/query-settings.js * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/controllers/open-queries.js * (delete) contrib/views/hive-next/src/main/resources/ui/hive-web/tests/unit/controllers/messages-test.js * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/app/routes/visual-explain.js * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/tests/unit/components/query-settings-test.js * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/tests/unit/routes/tez-ui-test.js * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/router.js * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/app/routes/messages.js * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/routes/application.js * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/app/routes/visualization-ui.js * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/controllers/index.js * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/templates/application.hbs * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/app/routes/tez-ui.js * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/styles/query-tabs.scss * (delete) contrib/views/hive-next/src/main/resources/ui/hive-web/tests/unit/views/visual-explain-test.js * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/tests/unit/routes/messages-test.js * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/templates/open-queries.hbs * (delete) contrib/views/hive-next/src/main/resources/ui/hive-web/tests/unit/controllers/settings-test.js * (delete) contrib/views/hive-next/src/main/resources/ui/hive-web/app/templates/settings.hbs > Tez view button doesnt works in ambari hive views 1.5 > - > > Key: AMBARI-22897 > URL: https://issues.apache.org/jira/browse/AMBARI-22897 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.1 > Environment: Ambari 2.6.1 >Reporter: Akhil S Naik >Assignee: Akhil S Naik >Priority: Major > Labels: ambari-views > Fix For: trunk, 3.0.0 > > Attachments: Screen Shot 2018-02-01 at 8.00.17 PM.png > > Time Spent: 40m > Remaining Estimate: 0h > > *Issue :* > Login to ambari version 2.6.1 navigate to hive view 1.5 > When click on tez button or visualization or visual explain or settings > button > the page throws a script error and it become a blank page > *Root Cause :* > when click on the tez button, visualization or any other side button , > the following error is thrown from ember : > Assertion Failed: You attempted to render into 'index' but it was not found > attached the image error -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22897) Tez view button doesnt works in ambari hive views 1.5
[ https://issues.apache.org/jira/browse/AMBARI-22897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil S Naik updated AMBARI-22897: -- Labels: ambari-views (was: ) > Tez view button doesnt works in ambari hive views 1.5 > - > > Key: AMBARI-22897 > URL: https://issues.apache.org/jira/browse/AMBARI-22897 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.1 > Environment: Ambari 2.6.1 >Reporter: Akhil S Naik >Assignee: Akhil S Naik >Priority: Major > Labels: ambari-views > Fix For: trunk, 3.0.0 > > Attachments: Screen Shot 2018-02-01 at 8.00.17 PM.png > > Time Spent: 40m > Remaining Estimate: 0h > > *Issue :* > Login to ambari version 2.6.1 navigate to hive view 1.5 > When click on tez button or visualization or visual explain or settings > button > the page throws a script error and it become a blank page > *Root Cause :* > when click on the tez button, visualization or any other side button , > the following error is thrown from ember : > Assertion Failed: You attempted to render into 'index' but it was not found > attached the image error -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22897) Tez view button doesnt works in ambari hive views 1.5
[ https://issues.apache.org/jira/browse/AMBARI-22897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil S Naik updated AMBARI-22897: -- Labels: (was: patch-available pull-request-available) > Tez view button doesnt works in ambari hive views 1.5 > - > > Key: AMBARI-22897 > URL: https://issues.apache.org/jira/browse/AMBARI-22897 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.1 > Environment: Ambari 2.6.1 >Reporter: Akhil S Naik >Assignee: Akhil S Naik >Priority: Major > Fix For: trunk, 3.0.0 > > Attachments: Screen Shot 2018-02-01 at 8.00.17 PM.png > > Time Spent: 40m > Remaining Estimate: 0h > > *Issue :* > Login to ambari version 2.6.1 navigate to hive view 1.5 > When click on tez button or visualization or visual explain or settings > button > the page throws a script error and it become a blank page > *Root Cause :* > when click on the tez button, visualization or any other side button , > the following error is thrown from ember : > Assertion Failed: You attempted to render into 'index' but it was not found > attached the image error -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22897) Tez view button doesnt works in ambari hive views 1.5
[ https://issues.apache.org/jira/browse/AMBARI-22897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil S Naik updated AMBARI-22897: -- Resolution: Fixed Fix Version/s: trunk Status: Resolved (was: Patch Available) > Tez view button doesnt works in ambari hive views 1.5 > - > > Key: AMBARI-22897 > URL: https://issues.apache.org/jira/browse/AMBARI-22897 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.1 > Environment: Ambari 2.6.1 >Reporter: Akhil S Naik >Assignee: Akhil S Naik >Priority: Major > Fix For: trunk, 3.0.0 > > Attachments: Screen Shot 2018-02-01 at 8.00.17 PM.png > > Time Spent: 40m > Remaining Estimate: 0h > > *Issue :* > Login to ambari version 2.6.1 navigate to hive view 1.5 > When click on tez button or visualization or visual explain or settings > button > the page throws a script error and it become a blank page > *Root Cause :* > when click on the tez button, visualization or any other side button , > the following error is thrown from ember : > Assertion Failed: You attempted to render into 'index' but it was not found > attached the image error -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23208) NN Federation Wizard: rename custom command
[ https://issues.apache.org/jira/browse/AMBARI-23208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-23208. -- Resolution: Fixed committed to trunk > NN Federation Wizard: rename custom command > --- > > Key: AMBARI-23208 > URL: https://issues.apache.org/jira/browse/AMBARI-23208 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Rename BOOTSTRAP custom command to BOOTSTRAP_STANDBY. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23218) Remove delete custom command from Ambari Infra Solr stack
[ https://issues.apache.org/jira/browse/AMBARI-23218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23218: Labels: pull-request-available (was: ) > Remove delete custom command from Ambari Infra Solr stack > - > > Key: AMBARI-23218 > URL: https://issues.apache.org/jira/browse/AMBARI-23218 > Project: Ambari > Issue Type: Bug > Components: ambari-infra, ambari-server >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23216) Fix that Log Search for Ambari 2.6.2 should not require java8
[ https://issues.apache.org/jira/browse/AMBARI-23216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16396742#comment-16396742 ] Hudson commented on AMBARI-23216: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #656 (See [https://builds.apache.org/job/Ambari-branch-2.6/656/]) AMBARI-23216. Fix that Log Search for Ambari 2.6.2 should not require (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=fe8545081e54e34461b645e8c3bd2fa327109358]) * (edit) ambari-logsearch/ambari-logsearch-logfeeder/pom.xml * (edit) ambari-logsearch/pom.xml > Fix that Log Search for Ambari 2.6.2 should not require java8 > - > > Key: AMBARI-23216 > URL: https://issues.apache.org/jira/browse/AMBARI-23216 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.6.2 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.6.2 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23218) Remove delete custom command from Ambari Infra Solr stack
Olivér Szabó created AMBARI-23218: - Summary: Remove delete custom command from Ambari Infra Solr stack Key: AMBARI-23218 URL: https://issues.apache.org/jira/browse/AMBARI-23218 Project: Ambari Issue Type: Bug Components: ambari-infra, ambari-server Affects Versions: 2.7.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23149) Installation of MySQL fails on CentOS 7.2, should install mariadb
[ https://issues.apache.org/jira/browse/AMBARI-23149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16396712#comment-16396712 ] Hudson commented on AMBARI-23149: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #655 (See [https://builds.apache.org/job/Ambari-branch-2.6/655/]) AMBARI-23149. Installation of MySQL fails on CentOS 7.2, should install (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=59ec1edde74b122f80d6a80854855a6ff0f46de6]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.1/services/HIVE/metainfo.xml * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/status_params.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/services/HIVE/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/metainfo.xml * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/mysql_service.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/services/HIVE/metainfo.xml * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/metainfo.xml > Installation of MySQL fails on CentOS 7.2, should install mariadb > - > > Key: AMBARI-23149 > URL: https://issues.apache.org/jira/browse/AMBARI-23149 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.6.2 > > Attachments: AMBARI-23149.patch, AMBARI-23149.patch > > Time Spent: 1h > Remaining Estimate: 0h > > I'm seeing the following error during HDP 3 beta installation. > > > > Traceback (most recent call last): > File > "/usr/lib/python2.6/site-packages/resource_management/core/providers/package/__init__.py", > line 268, in _call_with_retries > code, out = func(cmd, **kwargs) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 72, in inner > result = function(command, **kwargs) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 102, in checked_call > tries=tries, try_sleep=try_sleep, > timeout_kill_strategy=timeout_kill_strategy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 150, in _call_wrapper > result = _call(command, **kwargs_copy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 303, in _call > raise ExecutionFailed(err_msg, code, out, err) > ExecutionFailed: Execution of '/usr/bin/yum -d 0 -e 0 -y install > mysql-community-release' returned 1. Error: Nothing to do > > The above exception was the cause of the following exception: > > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/common-services/HIVE/3.0.0.3.0/package/scripts/mysql_server.py", > line 68, in > MysqlServer().execute() > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 376, in execute > method(env) > File > "/var/lib/ambari-agent/cache/common-services/HIVE/3.0.0.3.0/package/scripts/mysql_server.py", > line 37, in install > self.install_packages(env) > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 831, in install_packages > retry_count=agent_stack_retry_count) > File > "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line > 166, in __init__ > self.env.run() > File > "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", > line 160, in run > self.run_action(resource, action) > File > "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", > line 124, in run_action > provider_action() > File > "/usr/lib/python2.6/site-packages/resource_management/core/providers/package/__init__.py", > line 53, in action_install > self.install_package(package_name, self.resource.use_repos, > self.resource.skip_repos) > File > "/usr/lib/python2.6/site-packages/resource_management/core/providers/package/yumrpm.py", > line 251, in install_package > self.checked_call_with_retries(cmd, sudo=True, > logoutput=self.get_logoutput()) > File > "/usr/lib/python2.6/site-packages/resource_management/core/providers/package/__init__.py", > line 251, in checked_call_with_retries > return self._call_with_retries(cmd, is_checked=True, **kwargs) > File > "/usr/lib/python2.6/site-packages/resource_management/core/providers/package/__init__.py", > line 268, in _call_with_retries > code, out = func(cmd,
[jira] [Created] (AMBARI-23217) Spark and Spark2 SSL credentials in Ambari UI are in plain text rather than being hidden
Supreeth Sharma created AMBARI-23217: Summary: Spark and Spark2 SSL credentials in Ambari UI are in plain text rather than being hidden Key: AMBARI-23217 URL: https://issues.apache.org/jira/browse/AMBARI-23217 Project: Ambari Issue Type: Bug Components: ambari-sever Affects Versions: 2.6.2 Reporter: Supreeth Sharma Fix For: 2.6.2 Below properties which are part of Spark and Spark2 are in plaintext rather than being hidden in Ambari livy.key-password livy.keystore.password livy.ssl.trustStorePassword spark.ssl.keyPassword spark.ssl.keyStorePassword spark.ssl.trustStorePassword spark.ssl.keyPassword spark.ssl.keyStorePassword spark.ssl.trustStorePassword -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23149) Installation of MySQL fails on CentOS 7.2, should install mariadb
[ https://issues.apache.org/jira/browse/AMBARI-23149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23149: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.6 > Installation of MySQL fails on CentOS 7.2, should install mariadb > - > > Key: AMBARI-23149 > URL: https://issues.apache.org/jira/browse/AMBARI-23149 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.6.2 > > Attachments: AMBARI-23149.patch, AMBARI-23149.patch > > Time Spent: 1h > Remaining Estimate: 0h > > I'm seeing the following error during HDP 3 beta installation. > > > > Traceback (most recent call last): > File > "/usr/lib/python2.6/site-packages/resource_management/core/providers/package/__init__.py", > line 268, in _call_with_retries > code, out = func(cmd, **kwargs) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 72, in inner > result = function(command, **kwargs) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 102, in checked_call > tries=tries, try_sleep=try_sleep, > timeout_kill_strategy=timeout_kill_strategy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 150, in _call_wrapper > result = _call(command, **kwargs_copy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 303, in _call > raise ExecutionFailed(err_msg, code, out, err) > ExecutionFailed: Execution of '/usr/bin/yum -d 0 -e 0 -y install > mysql-community-release' returned 1. Error: Nothing to do > > The above exception was the cause of the following exception: > > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/common-services/HIVE/3.0.0.3.0/package/scripts/mysql_server.py", > line 68, in > MysqlServer().execute() > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 376, in execute > method(env) > File > "/var/lib/ambari-agent/cache/common-services/HIVE/3.0.0.3.0/package/scripts/mysql_server.py", > line 37, in install > self.install_packages(env) > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 831, in install_packages > retry_count=agent_stack_retry_count) > File > "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line > 166, in __init__ > self.env.run() > File > "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", > line 160, in run > self.run_action(resource, action) > File > "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", > line 124, in run_action > provider_action() > File > "/usr/lib/python2.6/site-packages/resource_management/core/providers/package/__init__.py", > line 53, in action_install > self.install_package(package_name, self.resource.use_repos, > self.resource.skip_repos) > File > "/usr/lib/python2.6/site-packages/resource_management/core/providers/package/yumrpm.py", > line 251, in install_package > self.checked_call_with_retries(cmd, sudo=True, > logoutput=self.get_logoutput()) > File > "/usr/lib/python2.6/site-packages/resource_management/core/providers/package/__init__.py", > line 251, in checked_call_with_retries > return self._call_with_retries(cmd, is_checked=True, **kwargs) > File > "/usr/lib/python2.6/site-packages/resource_management/core/providers/package/__init__.py", > line 268, in _call_with_retries > code, out = func(cmd, **kwargs) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 72, in inner > result = function(command, **kwargs) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 102, in checked_call > tries=tries, try_sleep=try_sleep, > timeout_kill_strategy=timeout_kill_strategy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 150, in _call_wrapper > result = _call(command, **kwargs_copy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 303, in _call > raise ExecutionFailed(err_msg, code, out, err) > resource_management.core.exceptions.ExecutionFailed: Execution of > '/usr/bin/yum -d 0 -e 0 -y install mysql-community-release' returned 1. > Error: Nothing to do >
[jira] [Commented] (AMBARI-23204) Ambari Upgrade : Schema Upgrade Fails with error "Foreign key constraint is incorrectly formed"
[
https://issues.apache.org/jira/browse/AMBARI-23204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16396684#comment-16396684
]
Hudson commented on AMBARI-23204:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8847 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8847/])
AMBARI-23204. Ambari Upgrade : Schema Upgrade Fails with error "Foreign
(m.magyar3:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=8bdef4281a818597cf75f9f8360748fef892b4b4])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog270.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog270Test.java
> Ambari Upgrade : Schema Upgrade Fails with error "Foreign key constraint is
> incorrectly formed"
> ---
>
> Key: AMBARI-23204
> URL: https://issues.apache.org/jira/browse/AMBARI-23204
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Jasmeen Kaur
>Assignee: Attila Magyar
>Priority: Blocker
> Labels: pull-request-available, upgrade
> Fix For: 2.7.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Ambari Schema Upgrade from 2.6.X to 2.7.0.0 fails with below exception .
> A blocker for Ambari Upgrades testing.
> {code:java}
> 12 Mar 2018 00:51:37,879 INFO [main] SchemaUpgradeHelper:424 - Upgrading
> schema to target version = 2.7.0.0
> 12 Mar 2018 00:51:37,883 INFO [main] SchemaUpgradeHelper:433 - Upgrading
> schema from source version = 2.6.1
> 12 Mar 2018 00:51:37,888 INFO [main] SchemaUpgradeHelper:163 - Upgrade path:
> [{ upgradeCatalog: sourceVersion = 2.6.1, targetVersion = 2.6.2 }, {
> upgradeCatalog: sourceVersion = 2.6.2, targetVersion = 2.7.0 }, {
> upgradeCatalog: sourceVersion = null, targetVersion = 2.7.0 }, {
> upgradeCatalog: sourceVersion = null, targetVersion = 2.7.0 }]
> 12 Mar 2018 00:51:37,889 INFO [main] SchemaUpgradeHelper:200 - Executing DDL
> upgrade...
> 12 Mar 2018 00:51:37,911 INFO [main] DBAccessorImpl:876 - Executing query:
> ALTER TABLE topology_host_request ADD status VARCHAR(255)
> 12 Mar 2018 00:51:37,948 INFO [main] DBAccessorImpl:876 - Executing query:
> ALTER TABLE topology_host_request ADD status_message VARCHAR(1024)
> 12 Mar 2018 00:51:37,982 INFO [main] DBAccessorImpl:876 - Executing query:
> ALTER TABLE stage ADD status VARCHAR(255) NOT NULL DEFAULT 'PENDING'
> 12 Mar 2018 00:51:38,017 INFO [main] DBAccessorImpl:876 - Executing query:
> ALTER TABLE stage ADD display_status VARCHAR(255) NOT NULL DEFAULT 'PENDING'
> 12 Mar 2018 00:51:38,055 INFO [main] DBAccessorImpl:876 - Executing query:
> ALTER TABLE request ADD display_status VARCHAR(255) NOT NULL DEFAULT 'PENDING'
> 12 Mar 2018 00:51:38,091 INFO [main] DBAccessorImpl:876 - Executing query:
> ALTER TABLE request ADD user_name VARCHAR(255)
> 12 Mar 2018 00:51:38,127 INFO [main] DBAccessorImpl:876 - Executing query:
> ALTER TABLE host_role_command ADD ops_display_name VARCHAR(255)
> 12 Mar 2018 00:51:38,314 INFO [main] DBAccessorImpl:876 - Executing query:
> ALTER TABLE hostcomponentdesiredstate DROP COLUMN security_state
> 12 Mar 2018 00:51:38,351 INFO [main] DBAccessorImpl:876 - Executing query:
> ALTER TABLE hostcomponentstate DROP COLUMN security_state
> 12 Mar 2018 00:51:38,387 INFO [main] DBAccessorImpl:876 - Executing query:
> ALTER TABLE servicedesiredstate DROP COLUMN security_state
> 12 Mar 2018 00:51:38,426 INFO [main] DBAccessorImpl:876 - Executing query:
> CREATE TABLE ambari_configuration (category_name VARCHAR(100) NOT NULL,
> property_name VARCHAR(100) NOT NULL, property_value VARCHAR(255))
> ENGINE=INNODB
> 12 Mar 2018 00:51:38,435 INFO [main] DBAccessorImpl:876 - Executing query:
> ALTER TABLE ambari_configuration ADD CONSTRAINT PK_ambari_configuration
> PRIMARY KEY (category_name,property_name)
> 12 Mar 2018 00:51:38,443 INFO [main] DBAccessorImpl:876 - Executing query:
> ALTER TABLE hostcomponentstate ADD last_live_state VARCHAR(255) DEFAULT
> 'UNKNOWN'
> 12 Mar 2018 00:51:38,476 WARN [main] DBAccessorImpl:965 -
> user_authentication_tmp table doesn't exists, skipping
> 12 Mar 2018 00:51:38,477 INFO [main] DBAccessorImpl:876 - Executing query:
> CREATE TABLE user_authentication_tmp (user_authentication_id BIGINT NOT NULL,
> user_id BIGINT NOT NULL, authentication_type VARCHAR(50) NOT NULL,
> authentication_key LONGTEXT, create_time DATETIME, update_time DATETIME)
> ENGINE=INNODB
> 12 Mar 2018 00:51:38,483 INFO [main] DBAccessorImpl:876 - Executing query:
> CREATE TABLE user_authentication (user_authentication_id BIGINT NOT NULL,
> user_id BIGINT NOT NULL, authentication_type VARCHAR(50) NOT NULL,
> authentication_key LONGTEXT, create_time
[jira] [Resolved] (AMBARI-23204) Ambari Upgrade : Schema Upgrade Fails with error "Foreign key constraint is incorrectly formed"
[
https://issues.apache.org/jira/browse/AMBARI-23204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Magyar resolved AMBARI-23204.
Resolution: Fixed
> Ambari Upgrade : Schema Upgrade Fails with error "Foreign key constraint is
> incorrectly formed"
> ---
>
> Key: AMBARI-23204
> URL: https://issues.apache.org/jira/browse/AMBARI-23204
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Jasmeen Kaur
>Assignee: Attila Magyar
>Priority: Blocker
> Labels: pull-request-available, upgrade
> Fix For: 2.7.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Ambari Schema Upgrade from 2.6.X to 2.7.0.0 fails with below exception .
> A blocker for Ambari Upgrades testing.
> {code:java}
> 12 Mar 2018 00:51:37,879 INFO [main] SchemaUpgradeHelper:424 - Upgrading
> schema to target version = 2.7.0.0
> 12 Mar 2018 00:51:37,883 INFO [main] SchemaUpgradeHelper:433 - Upgrading
> schema from source version = 2.6.1
> 12 Mar 2018 00:51:37,888 INFO [main] SchemaUpgradeHelper:163 - Upgrade path:
> [{ upgradeCatalog: sourceVersion = 2.6.1, targetVersion = 2.6.2 }, {
> upgradeCatalog: sourceVersion = 2.6.2, targetVersion = 2.7.0 }, {
> upgradeCatalog: sourceVersion = null, targetVersion = 2.7.0 }, {
> upgradeCatalog: sourceVersion = null, targetVersion = 2.7.0 }]
> 12 Mar 2018 00:51:37,889 INFO [main] SchemaUpgradeHelper:200 - Executing DDL
> upgrade...
> 12 Mar 2018 00:51:37,911 INFO [main] DBAccessorImpl:876 - Executing query:
> ALTER TABLE topology_host_request ADD status VARCHAR(255)
> 12 Mar 2018 00:51:37,948 INFO [main] DBAccessorImpl:876 - Executing query:
> ALTER TABLE topology_host_request ADD status_message VARCHAR(1024)
> 12 Mar 2018 00:51:37,982 INFO [main] DBAccessorImpl:876 - Executing query:
> ALTER TABLE stage ADD status VARCHAR(255) NOT NULL DEFAULT 'PENDING'
> 12 Mar 2018 00:51:38,017 INFO [main] DBAccessorImpl:876 - Executing query:
> ALTER TABLE stage ADD display_status VARCHAR(255) NOT NULL DEFAULT 'PENDING'
> 12 Mar 2018 00:51:38,055 INFO [main] DBAccessorImpl:876 - Executing query:
> ALTER TABLE request ADD display_status VARCHAR(255) NOT NULL DEFAULT 'PENDING'
> 12 Mar 2018 00:51:38,091 INFO [main] DBAccessorImpl:876 - Executing query:
> ALTER TABLE request ADD user_name VARCHAR(255)
> 12 Mar 2018 00:51:38,127 INFO [main] DBAccessorImpl:876 - Executing query:
> ALTER TABLE host_role_command ADD ops_display_name VARCHAR(255)
> 12 Mar 2018 00:51:38,314 INFO [main] DBAccessorImpl:876 - Executing query:
> ALTER TABLE hostcomponentdesiredstate DROP COLUMN security_state
> 12 Mar 2018 00:51:38,351 INFO [main] DBAccessorImpl:876 - Executing query:
> ALTER TABLE hostcomponentstate DROP COLUMN security_state
> 12 Mar 2018 00:51:38,387 INFO [main] DBAccessorImpl:876 - Executing query:
> ALTER TABLE servicedesiredstate DROP COLUMN security_state
> 12 Mar 2018 00:51:38,426 INFO [main] DBAccessorImpl:876 - Executing query:
> CREATE TABLE ambari_configuration (category_name VARCHAR(100) NOT NULL,
> property_name VARCHAR(100) NOT NULL, property_value VARCHAR(255))
> ENGINE=INNODB
> 12 Mar 2018 00:51:38,435 INFO [main] DBAccessorImpl:876 - Executing query:
> ALTER TABLE ambari_configuration ADD CONSTRAINT PK_ambari_configuration
> PRIMARY KEY (category_name,property_name)
> 12 Mar 2018 00:51:38,443 INFO [main] DBAccessorImpl:876 - Executing query:
> ALTER TABLE hostcomponentstate ADD last_live_state VARCHAR(255) DEFAULT
> 'UNKNOWN'
> 12 Mar 2018 00:51:38,476 WARN [main] DBAccessorImpl:965 -
> user_authentication_tmp table doesn't exists, skipping
> 12 Mar 2018 00:51:38,477 INFO [main] DBAccessorImpl:876 - Executing query:
> CREATE TABLE user_authentication_tmp (user_authentication_id BIGINT NOT NULL,
> user_id BIGINT NOT NULL, authentication_type VARCHAR(50) NOT NULL,
> authentication_key LONGTEXT, create_time DATETIME, update_time DATETIME)
> ENGINE=INNODB
> 12 Mar 2018 00:51:38,483 INFO [main] DBAccessorImpl:876 - Executing query:
> CREATE TABLE user_authentication (user_authentication_id BIGINT NOT NULL,
> user_id BIGINT NOT NULL, authentication_type VARCHAR(50) NOT NULL,
> authentication_key LONGTEXT, create_time DATETIME, update_time DATETIME)
> ENGINE=INNODB
> 12 Mar 2018 00:51:38,490 INFO [main] DBAccessorImpl:876 - Executing query:
> ALTER TABLE user_authentication ADD CONSTRAINT PK_user_authentication PRIMARY
> KEY (user_authentication_id)
> 12 Mar 2018 00:51:38,555 INFO [main] DBAccessorImpl:876 - Executing query:
> ALTER TABLE user_authentication ADD CONSTRAINT FK_user_authentication_users
> FOREIGN KEY (user_id) REFERENCES users (user_id)
> 12 Mar 2018 00:51:38,572 ERROR [main] DBAccessorImpl:882 - Error
[jira] [Resolved] (AMBARI-23215) Update logic to skip "*_CLIENT" services Service Checks (SC), as there is no SC defined for them.
[ https://issues.apache.org/jira/browse/AMBARI-23215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar resolved AMBARI-23215. -- Resolution: Fixed > Update logic to skip "*_CLIENT" services Service Checks (SC), as there is no > SC defined for them. > -- > > Key: AMBARI-23215 > URL: https://issues.apache.org/jira/browse/AMBARI-23215 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > - With advent of Mpacks, we have separated the *CLIENT* components from > *SERVER* counterparts and will be separate services itself. > -- For example: *ZOOKEEPER_CLIENT* will be a separate service having > category *CLIENT* and *ZOOKEEPER_SERVER* will be a separate service having > category *MASTER*. (Similarly, for others like HDFS_CLEINT and so on.) > - As there are no Service Checks explicitly defined for the CLIENT Services, > we need to update the code to skip running any SC calls for them. > [~dsen] Thanks for the pointers. > CC [~jluniya] | [~mradhakrishnan] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23215) Update logic to skip "*_CLIENT" services Service Checks (SC), as there is no SC defined for them.
[
https://issues.apache.org/jira/browse/AMBARI-23215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-23215:
-
Description:
- With advent of Mpacks, we have separated the *CLIENT* components from
*SERVER* counterparts and will be separate services itself.
-- For example: *ZOOKEEPER_CLIENT* will be a separate service having category
*CLIENT* and *ZOOKEEPER_SERVER* will be a separate service having category
*MASTER*. (Similarly, for others like HDFS_CLEINT and so on.)
- As there are no Service Checks explicitly defined for the CLIENT Services, we
need to update the code to skip running any SC calls for them.
[~dsen] Thanks for the pointers.
CC [~jluniya] | [~mradhakrishnan]
was:
{code}
POST /api/v1/clusters/c1/hosts/
{
"RequestInfo": {
"query": "Hosts/host_name.in(Host1,Host2)"
},
"Body": {
"host_components": [
"HostRoles": {
"component_name": "ZOOKEEPER_SERVER",
"component_type": "ZOOKEEPER_SERVER",
"service_group_name": "dev",
"service_name": "ZOOKEEPER_dev"
},
{
"HostRoles": {
"component_name": "ZOOKEEPER_CLIENT_dev",
"component_type": "ZOOKEEPER_CLIENT",
"service_group_name": "dev",
"service_name": "ZOOKEEPER_CLIENTS_dev"
}
}
]
}
}
{code}
- With advent of Mpacks, we have separated the *CLIENT* components from
*SERVER* counterparts and will be separate services itself.
-- For example: *ZOOKEEPER_CLIENT* will be a separate service having category
*CLIENT* and *ZOOKEEPER_SERVER* will be a separate service having category
*MASTER*. (Similarly, for others like HDFS_CLEINT and so on.)
- As there are no Service Checks explicitly defined for the CLIENT Services, we
need to update the code to skip running any SC calls for them.
[~dsen] Thanks for the pointers.
CC [~jluniya] | [~mradhakrishnan]
> Update logic to skip "*_CLIENT" services Service Checks (SC), as there is no
> SC defined for them.
> --
>
> Key: AMBARI-23215
> URL: https://issues.apache.org/jira/browse/AMBARI-23215
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> - With advent of Mpacks, we have separated the *CLIENT* components from
> *SERVER* counterparts and will be separate services itself.
> -- For example: *ZOOKEEPER_CLIENT* will be a separate service having
> category *CLIENT* and *ZOOKEEPER_SERVER* will be a separate service having
> category *MASTER*. (Similarly, for others like HDFS_CLEINT and so on.)
> - As there are no Service Checks explicitly defined for the CLIENT Services,
> we need to update the code to skip running any SC calls for them.
> [~dsen] Thanks for the pointers.
> CC [~jluniya] | [~mradhakrishnan]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23179) Hive view 2.0 does not parse the TAB delimited CSV files while using 'Upload Table'
[
https://issues.apache.org/jira/browse/AMBARI-23179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16396617#comment-16396617
]
Hudson commented on AMBARI-23179:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8846 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8846/])
AMBARI-23179 : Hive view 2.0 does not parse the TAB delimited CSV files
(github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=577bf7d08257300d96d6bc05178d6af065fa3afb])
* (edit)
contrib/views/hive20/src/main/resources/ui/app/routes/databases/database/tables/upload-table.js
> Hive view 2.0 does not parse the TAB delimited CSV files while using 'Upload
> Table'
> ---
>
> Key: AMBARI-23179
> URL: https://issues.apache.org/jira/browse/AMBARI-23179
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.6.0
> Environment: HDP 2.6.3
> Ambari 2.6.0
>Reporter: Sindhu Subhas
>Assignee: Nitiraj Singh Rathore
>Priority: Major
> Labels: pull-request-available
> Attachments: Screen Shot 2018-02-28 at 1.02.44 AM.png, Screen Shot
> 2018-02-28 at 5.05.55 PM.png, Screen Shot 2018-02-28 at 5.06.47 PM.png,
> Screen Shot 2018-02-28 at 5.07.30 PM.png, datatab.tsv
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Problem:
> When trying to Upload table from Hive view 2.0 from a TAB delimited file, the
> data is not parsed as expected.
> Same feature works as expected in Hive view 1.5.0.
> Attached output from Hive view 2.0 and output from Hive view 1.5.0.
> From the code, we do see difference in the code for
> src/main/java/org/apache/ambari/view/hive20/resources/uploads/UploadService.java.
> Debug from Hive view 2.0:
> {code:java}
> 27 Feb 2018 20:27:28,169 DEBUG
> [HiveViewActorSystem-akka.actor.default-dispatcher-4] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] OperationController:53 - } java.util.HashMap
> 27 Feb 2018 20:27:28,169 DEBUG
> [HiveViewActorSystem-akka.actor.default-dispatcher-4] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] HiveActor:41 - Message submitted:
> 927343c0-5ed6-435c-be60-37448ac1a8b0
> 27 Feb 2018 20:27:30,925 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] UploadService:484 - isFirstRowHeader : false,
> inputFileType : CSV
> 27 Feb 2018 20:27:30,934 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] OpenCSVParser:50 - setting delimiter as T
> 27 Feb 2018 20:27:30,934 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] OpenCSVParser:56 - setting Quote char : "
> 27 Feb 2018 20:27:30,934 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] OpenCSVParser:62 - setting escapeChar : \
> 27 Feb 2018 20:27:30,939 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] Parser:75 - generating preview for :
> ParseOptions{options={OPTIONS_CSV_QUOTE=", OPTIONS_CSV_DELIMITER=T,
> HEADER=NONE, FILE_TYPE=CSV, OPTIONS_CSV_ESCAPE_CHAR=\}}
> 27 Feb 2018 20:27:30,939 DEBUG [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] Parser:83 - Illegal number of preview columns supplied
> null
> 27 Feb 2018 20:27:30,943 DEBUG [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] ParseUtils:152 - error while parsing as timestamp
> string column1 column2 column3
> java.lang.IllegalArgumentException: Timestamp format must be -mm-dd
> hh:mm:ss[.f]
> at java.sql.Timestamp.valueOf(Timestamp.java:204)
> .
> 27 Feb 2018 20:27:30,948 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] Parser:149 - datatype detected for column 0 : STRING
> 27 Feb 2018 20:27:30,949 DEBUG [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] Parser:159 - return headers :
> [ColumnInfo{name='column1', type='STRING', precision=null, scale=null,
> comment='null'}]
> {code}
> Debug from Hive view 1.5.0:
> {code:java}
> 27 Feb 2018 20:13:15,881 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] UploadService:499 - isFirstRowHeader : true,
> inputFileType : CSV
> 27 Feb 2018 20:13:15,918 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] OpenCSVParser:50 - setting delimiter as
> 27 Feb 2018 20:13:15,919 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] OpenCSVParser:56 - setting Quote char : "
> 27 Feb 2018 20:13:15,919 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] OpenCSVParser:62 - setting escapeChar : \
> 27 Feb 2018 20:13:15,928 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] Parser:75 - generating preview for :
> ParseOptions{options={OPTIONS_CSV_QUOTE=", OPTIONS_CSV_DELIMITER= ,
> HEADER=FIRST_RECORD, FILE_TYPE=CSV, OPTIONS_CSV_ESCAPE_CHAR=\}}
> 27 Feb 2018 20:13:15,929 DEBUG
[jira] [Updated] (AMBARI-23215) Update logic to skip "*_CLIENT" services Service Checks (SC), as there is no SC defined for them.
[
https://issues.apache.org/jira/browse/AMBARI-23215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-23215:
-
Description:
{code}
POST /api/v1/clusters/c1/hosts/
{
"RequestInfo": {
"query": "Hosts/host_name.in(Host1,Host2)"
},
"Body": {
"host_components": [
"HostRoles": {
"component_name": "ZOOKEEPER_SERVER",
"component_type": "ZOOKEEPER_SERVER",
"service_group_name": "dev",
"service_name": "ZOOKEEPER_dev"
},
{
"HostRoles": {
"component_name": "ZOOKEEPER_CLIENT_dev",
"component_type": "ZOOKEEPER_CLIENT",
"service_group_name": "dev",
"service_name": "ZOOKEEPER_CLIENTS_dev"
}
}
]
}
}
{code}
- With advent of Mpacks, we have separated the *CLIENT* components from
*SERVER* counterparts and will be separate services itself.
-- For example: *ZOOKEEPER_CLIENT* will be a separate service having category
*CLIENT* and *ZOOKEEPER_SERVER* will be a separate service having category
*MASTER*. (Similarly, for others like HDFS_CLEINT and so on.)
- As there are no Service Checks explicitly defined for the CLIENT Services, we
need to update the code to skip running any SC calls for them.
[~dsen] Thanks for the pointers.
CC [~jluniya] | [~mradhakrishnan]
was:
{code}
POST /api/v1/clusters/c1/hosts/
{
"RequestInfo": {
"query": "Hosts/host_name.in(Host1,Host2)"
},
"Body": {
"host_components": ["HostRoles": {
"component_name": "ZOOKEEPER_SERVER",
"component_type": "ZOOKEEPER_SERVER",
"service_group_name": "dev",
"service_name": "ZOOKEEPER_dev"
},
{
"HostRoles": {
"component_name":
"ZOOKEEPER_CLIENT_dev",
"component_type": "ZOOKEEPER_CLIENT",
"service_group_name": "dev",
"service_name": "ZOOKEEPER_CLIENTS_dev"
}
}
]
}
}
{code}
- With advent of Mpacks, we have separated the *CLIENT* components from
*SERVER* counterparts and will be separate services itself.
-- For example: *ZOOKEEPER_CLIENT* will be a separate service having category
*CLIENT* and *ZOOKEEPER_SERVER* will be a separate service having category
*MASTER*. (Similarly, for others like HDFS_CLEINT and so on.)
- As there are no Service Checks explicitly defined for the CLIENT Services, we
need to update the code to skip running any SC calls for them.
[~dsen] Thanks for the pointers.
CC [~jluniya] | [~mradhakrishnan]
> Update logic to skip "*_CLIENT" services Service Checks (SC), as there is no
> SC defined for them.
> --
>
> Key: AMBARI-23215
> URL: https://issues.apache.org/jira/browse/AMBARI-23215
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {code}
> POST /api/v1/clusters/c1/hosts/
> {
> "RequestInfo": {
> "query": "Hosts/host_name.in(Host1,Host2)"
> },
> "Body": {
> "host_components": [
> "HostRoles": {
> "component_name": "ZOOKEEPER_SERVER",
> "component_type": "ZOOKEEPER_SERVER",
> "service_group_name": "dev",
> "service_name": "ZOOKEEPER_dev"
> },
> {
> "HostRoles": {
> "component_name": "ZOOKEEPER_CLIENT_dev",
> "component_type": "ZOOKEEPER_CLIENT",
> "service_group_name": "dev",
> "service_name": "ZOOKEEPER_CLIENTS_dev"
>}
>}
> ]
> }
> }
> {code}
> - With advent of Mpacks, we have separated the *CLIENT* components from
> *SERVER* counterparts and will be separate services itself.
> -- For example: *ZOOKEEPER_CLIENT* will be a separate service having
>
[jira] [Updated] (AMBARI-23215) Update logic to skip "*_CLIENT" services Service Checks (SC), as there is no SC defined for them.
[
https://issues.apache.org/jira/browse/AMBARI-23215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-23215:
-
Description:
POST /api/v1/clusters/c1/hosts/
{
"RequestInfo": {
"query": "Hosts/host_name.in(Host1,Host2)"
},
"Body": {
"host_components": ["HostRoles": {
"component_name": "ZOOKEEPER_SERVER",
"component_type": "ZOOKEEPER_SERVER",
"service_group_name": "dev",
"service_name": "ZOOKEEPER_dev"
},
{
"HostRoles": {
"component_name":
"ZOOKEEPER_CLIENT_dev",
"component_type": "ZOOKEEPER_CLIENT",
"service_group_name": "dev",
"service_name": "ZOOKEEPER_CLIENTS_dev"
}
}
]
}
}
- With advent of Mpacks, we have separated the *CLIENT* components from
*SERVER* counterparts and will be separate services itself.
-- For example: *ZOOKEEPER_CLIENT* will be a separate service having category
*CLIENT* and *ZOOKEEPER_SERVER* will be a separate service having category
*MASTER*. (Similarly, for others like HDFS_CLEINT and so on.)
- As there are no Service Checks explicitly defined for the CLIENT Services, we
need to update the code to skip running any SC calls for them.
[~dsen] Thanks for the pointers.
CC [~jluniya] | [~mradhakrishnan]
was:
- With advent of Mpacks, we have separated the *CLIENT* components from
*SERVER* counterparts and will be separate services itself.
-- For example: *ZOOKEEPER_CLIENT* will be a separate service having category
*CLIENT* and *ZOOKEEPER_SERVER* will be a separate service having category
*MASTER*. (Similarly, for others like HDFS_CLEINT and so on.)
- As there are no Service Checks explicitly defined for the CLIENT Services, we
need to update the code to skip running any SC calls for them.
[~dsen] Thanks for the pointers.
CC [~jluniya] | [~mradhakrishnan]
> Update logic to skip "*_CLIENT" services Service Checks (SC), as there is no
> SC defined for them.
> --
>
> Key: AMBARI-23215
> URL: https://issues.apache.org/jira/browse/AMBARI-23215
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> POST /api/v1/clusters/c1/hosts/
> {
> "RequestInfo": {
> "query": "Hosts/host_name.in(Host1,Host2)"
> },
> "Body": {
> "host_components": ["HostRoles": {
> "component_name": "ZOOKEEPER_SERVER",
> "component_type": "ZOOKEEPER_SERVER",
> "service_group_name": "dev",
> "service_name": "ZOOKEEPER_dev"
> },
> {
> "HostRoles": {
> "component_name":
> "ZOOKEEPER_CLIENT_dev",
> "component_type": "ZOOKEEPER_CLIENT",
> "service_group_name": "dev",
> "service_name": "ZOOKEEPER_CLIENTS_dev"
> }
> }
> ]
> }
> }
> - With advent of Mpacks, we have separated the *CLIENT* components from
> *SERVER* counterparts and will be separate services itself.
> -- For example: *ZOOKEEPER_CLIENT* will be a separate service having
> category *CLIENT* and *ZOOKEEPER_SERVER* will be a separate service having
> category *MASTER*. (Similarly, for others like HDFS_CLEINT and so on.)
> - As there are no Service Checks explicitly defined for the CLIENT Services,
> we need to update the code to skip running any SC calls for them.
> [~dsen] Thanks for the pointers.
> CC [~jluniya] | [~mradhakrishnan]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23215) Update logic to skip "*_CLIENT" services Service Checks (SC), as there is no SC defined for them.
[
https://issues.apache.org/jira/browse/AMBARI-23215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-23215:
-
Description:
{code}
POST /api/v1/clusters/c1/hosts/
{
"RequestInfo": {
"query": "Hosts/host_name.in(Host1,Host2)"
},
"Body": {
"host_components": ["HostRoles": {
"component_name": "ZOOKEEPER_SERVER",
"component_type": "ZOOKEEPER_SERVER",
"service_group_name": "dev",
"service_name": "ZOOKEEPER_dev"
},
{
"HostRoles": {
"component_name":
"ZOOKEEPER_CLIENT_dev",
"component_type": "ZOOKEEPER_CLIENT",
"service_group_name": "dev",
"service_name": "ZOOKEEPER_CLIENTS_dev"
}
}
]
}
}
{code}
- With advent of Mpacks, we have separated the *CLIENT* components from
*SERVER* counterparts and will be separate services itself.
-- For example: *ZOOKEEPER_CLIENT* will be a separate service having category
*CLIENT* and *ZOOKEEPER_SERVER* will be a separate service having category
*MASTER*. (Similarly, for others like HDFS_CLEINT and so on.)
- As there are no Service Checks explicitly defined for the CLIENT Services, we
need to update the code to skip running any SC calls for them.
[~dsen] Thanks for the pointers.
CC [~jluniya] | [~mradhakrishnan]
was:
POST /api/v1/clusters/c1/hosts/
{
"RequestInfo": {
"query": "Hosts/host_name.in(Host1,Host2)"
},
"Body": {
"host_components": ["HostRoles": {
"component_name": "ZOOKEEPER_SERVER",
"component_type": "ZOOKEEPER_SERVER",
"service_group_name": "dev",
"service_name": "ZOOKEEPER_dev"
},
{
"HostRoles": {
"component_name":
"ZOOKEEPER_CLIENT_dev",
"component_type": "ZOOKEEPER_CLIENT",
"service_group_name": "dev",
"service_name": "ZOOKEEPER_CLIENTS_dev"
}
}
]
}
}
- With advent of Mpacks, we have separated the *CLIENT* components from
*SERVER* counterparts and will be separate services itself.
-- For example: *ZOOKEEPER_CLIENT* will be a separate service having category
*CLIENT* and *ZOOKEEPER_SERVER* will be a separate service having category
*MASTER*. (Similarly, for others like HDFS_CLEINT and so on.)
- As there are no Service Checks explicitly defined for the CLIENT Services, we
need to update the code to skip running any SC calls for them.
[~dsen] Thanks for the pointers.
CC [~jluniya] | [~mradhakrishnan]
> Update logic to skip "*_CLIENT" services Service Checks (SC), as there is no
> SC defined for them.
> --
>
> Key: AMBARI-23215
> URL: https://issues.apache.org/jira/browse/AMBARI-23215
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {code}
> POST /api/v1/clusters/c1/hosts/
> {
> "RequestInfo": {
> "query": "Hosts/host_name.in(Host1,Host2)"
> },
> "Body": {
> "host_components": ["HostRoles": {
> "component_name": "ZOOKEEPER_SERVER",
> "component_type": "ZOOKEEPER_SERVER",
> "service_group_name": "dev",
> "service_name": "ZOOKEEPER_dev"
> },
> {
> "HostRoles": {
> "component_name":
> "ZOOKEEPER_CLIENT_dev",
> "component_type": "ZOOKEEPER_CLIENT",
> "service_group_name": "dev",
> "service_name": "ZOOKEEPER_CLIENTS_dev"
> }
>
[jira] [Updated] (AMBARI-23216) Fix that Log Search for Ambari 2.6.2 should not require java8
[ https://issues.apache.org/jira/browse/AMBARI-23216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23216: Labels: pull-request-available (was: ) > Fix that Log Search for Ambari 2.6.2 should not require java8 > - > > Key: AMBARI-23216 > URL: https://issues.apache.org/jira/browse/AMBARI-23216 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.6.2 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.6.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23216) Fix that Log Search for Ambari 2.6.2 should not require java8
Olivér Szabó created AMBARI-23216: - Summary: Fix that Log Search for Ambari 2.6.2 should not require java8 Key: AMBARI-23216 URL: https://issues.apache.org/jira/browse/AMBARI-23216 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.6.2 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.6.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
