[jira] [Created] (AMBARI-23444) Allow Custom Hooks on a Per-Role Basis
Dmytro Grinenko created AMBARI-23444:
Summary: Allow Custom Hooks on a Per-Role Basis
Key: AMBARI-23444
URL: https://issues.apache.org/jira/browse/AMBARI-23444
Project: Ambari
Issue Type: Task
Components: ambari-agent, ambari-server
Affects Versions: trunk
Reporter: Dmytro Grinenko
Assignee: Dmytro Grinenko
Fix For: trunk
Expand hooks with a service-specific hooks. In addition, we must use custom
command parameters to help with this. For examples:
{{before-KAFKA-INSTALL}}
{{after-STORM-START}}
{{after-KAFKA-RESTART}} <-- this is a custom command, not a "regular" command
The more-specific hooks should execute tightly to the command script. For
example:
{{before-INSTALL}}
{{before-KAFKA-INSTALL}}
install script for Kafka
{{after-KAFKA-INSTALL}}
{{after-INSTALL}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23438) Fix failing metrics unit tests on trunk.
[
https://issues.apache.org/jira/browse/AMBARI-23438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16424966#comment-16424966
]
Hudson commented on AMBARI-23438:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8971 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8971/])
AMBARI-23438 : Fix failing metrics unit tests on trunk. (avijayan:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=4a0a28d0efd458a6f5b6e060dc0f7b8466e0935a])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/StackDefinedPropertyProviderTest.java
* (edit)
ambari-server/src/test/python/common-services/AMBARI_METRICS/test_service_advisor.py
* (edit)
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-site.xml
* (edit)
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py
* (edit)
ambari-server/src/test/python/stacks/2.0.6/AMBARI_METRICS/test_metrics_monitor.py
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/AMSPropertyProviderTest.java
* (edit)
ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/source/RawMetricsSourceTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/AMSReportPropertyProviderTest.java
> Fix failing metrics unit tests on trunk.
>
>
> Key: AMBARI-23438
> URL: https://issues.apache.org/jira/browse/AMBARI-23438
> 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
> Fix For: 2.7.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> {code}
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.source.RawMetricsSourceTest.testRawMetricsSourcedAtFlushInterval
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.source.RawMetricsSourceTest.testRawMetricsCachedAndSourced
> org.apache.ambari.server.controller.internal.StackDefinedPropertyProviderTest.testStackDefinedPropertyProviderAsClusterAdministrator
> org.apache.ambari.server.controller.internal.StackDefinedPropertyProviderTest.testStackDefinedPropertyProviderAsAdministrator
> org.apache.ambari.server.controller.internal.StackDefinedPropertyProviderTest.testStackDefinedPropertyProviderAsServiceAdministrator
> org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testRbacForAMSPropertyProvider
> org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testPopulateResourcesForSingleHostMetric
> org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testPopulateResourcesForSingleHostMetricPointInTime
> org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testPopulateResourcesForMultipleHostMetricscPointInTime
> org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testPopulateResourcesForMultipleHostMetrics
> org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testPopulateResourcesForRegexpMetrics
> org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testPopulateResourcesForSingleComponentMetric
> org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testPopulateMetricsForEmbeddedHBase
> org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testAggregateFunctionForComponentMetrics
> org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testFilterOutOfBandMetricData
> org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testPopulateResourcesForHostComponentHostMetrics
> org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testPopulateResourcesForHostComponentMetricsForMultipleHosts
> org.apache.ambari.server.controller.metrics.timeline.AMSReportPropertyProviderTest.testPopulateResources
> org.apache.ambari.server.controller.metrics.timeline.AMSReportPropertyProviderTest.testPopulateResourceWithAggregateFunction
> org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23443) Stack registration fails on Debian9
Dhanya Balasundaran created AMBARI-23443: Summary: Stack registration fails on Debian9 Key: AMBARI-23443 URL: https://issues.apache.org/jira/browse/AMBARI-23443 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Dhanya Balasundaran Stack registration on Debian9 is failing [org.xml.sax.SAXParseException; lineNumber: 36; columnNumber: 26; cvc-enumeration-valid: Value 'debian9' is not facet-valid with respect to enumeration '[redhat6, redhat7, redhat-ppc6, redhat-ppc7, debian6, debian7, ubuntu12, ubuntu14, ubuntu16, suse11, suse12]'. It must be a value from the enumeration.] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23442) Load StackService mappings from registered mpacks
Jason Golieb created AMBARI-23442: - Summary: Load StackService mappings from registered mpacks Key: AMBARI-23442 URL: https://issues.apache.org/jira/browse/AMBARI-23442 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Jason Golieb Assignee: Jason Golieb Fix For: 3.0.0 Previously, StackService was being loaded with data from VDFs. Now that we are not using VDFs, we need to fill the StackService model from mpack data after the mpacks are registered. This will keep the data available where StackService is used. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23439) Overflowing list of frozen hosts in Assign Slaves and Clients page
[ https://issues.apache.org/jira/browse/AMBARI-23439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16424581#comment-16424581 ] Hudson commented on AMBARI-23439: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8970 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8970/]) [AMBARI-23439] Overflowing list of frozen hosts in Assign Slaves and (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=4291cb410680ee7c74174d54f9a2424091a9428b]) * (edit) ambari-web/app/styles/wizard.less > Overflowing list of frozen hosts in Assign Slaves and Clients page > -- > > Key: AMBARI-23439 > URL: https://issues.apache.org/jira/browse/AMBARI-23439 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Attachments: Screen Shot 2018-03-30 at 9.06.19 AM.png > > Time Spent: 40m > Remaining Estimate: 0h > > When more than 10 hosts are present in a deployed cluster, the frozen hosts > column in assign slaves and clients page overflows the boundary and is not > scrollable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23433) Remove unnecessary properties from the Ranger SSO configuration updates via the stack advisor
[
https://issues.apache.org/jira/browse/AMBARI-23433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-23433:
--
Status: Patch Available (was: Open)
> Remove unnecessary properties from the Ranger SSO configuration updates via
> the stack advisor
> -
>
> Key: AMBARI-23433
> URL: https://issues.apache.org/jira/browse/AMBARI-23433
> Project: Ambari
> Issue Type: Task
> Components: ambari-admin
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Remove unnecessary properties from the Ranger SSO configuration updates via
> the stack advisor
> * {{ranger.sso.cookiename}}
> * {{ranger.sso.query.param.originalurl}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23433) Remove unnecessary properties from the Ranger SSO configuration updates via the stack advisor
[
https://issues.apache.org/jira/browse/AMBARI-23433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23433:
Labels: pull-request-available (was: )
> Remove unnecessary properties from the Ranger SSO configuration updates via
> the stack advisor
> -
>
> Key: AMBARI-23433
> URL: https://issues.apache.org/jira/browse/AMBARI-23433
> Project: Ambari
> Issue Type: Task
> Components: ambari-admin
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
>
> Remove unnecessary properties from the Ranger SSO configuration updates via
> the stack advisor
> * {{ranger.sso.cookiename}}
> * {{ranger.sso.query.param.originalurl}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23440) 404 error while setting up SSO on a new cluster
[
https://issues.apache.org/jira/browse/AMBARI-23440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23440:
Labels: SSO pull-request-available security (was: SSO security)
> 404 error while setting up SSO on a new cluster
>
>
> Key: AMBARI-23440
> URL: https://issues.apache.org/jira/browse/AMBARI-23440
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Critical
> Labels: SSO, pull-request-available, security
> Fix For: 2.7.0
>
>
> When setting up SSO via the Ambari server CLI using a new Ambari server
> instance, the following error is encountered:
> {noformat}
> [root@c7401 ~]# ambari-server setup-sso
> Using python /usr/bin/python
> Setting up SSO authentication properties...
> Enter Ambari Admin login: admin
> Enter Ambari Admin password:
> Fetching SSO configuration from DB.ERROR: Exiting with exit code 1.
> REASON: Error while fetching SSO configuration. Error details: HTTP Error
> 404: Not Found
> {noformat}
> This is caused by the lack of the {{sso-configuration}} category in the
> Ambari configuration set - which will be a common scenario for new Ambari
> clusters.
> {noformat}
> GET
> /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/sso-configuration
> {noformat}
> {noformat}
> {
> "status" : 404,
> "message" : "The requested resource doesn't exist:
> RootServiceComponentConfiguration not found where
> Configuration/service_name=AMBARI AND
> Configuration/component_name=AMBARI_SERVER AND
> Configuration/category=sso-configuration."
> }
> {noformat}
> The CLI handle this response and assume the following default values:
> {noformat}
> ambari.sso.manage_services = false
> ambari.sso.enabled_services =
> {noformat}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-23426) Unable to parse task structured output when disabling Kerberos
[
https://issues.apache.org/jira/browse/AMBARI-23426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas resolved AMBARI-23426.
---
Resolution: Invalid
Closing this since the issue is inconsistent and larger than just Kerberos
related.
> Unable to parse task structured output when disabling Kerberos
> --
>
> Key: AMBARI-23426
> URL: https://issues.apache.org/jira/browse/AMBARI-23426
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The following error is seen in the log when disabling Kerberos:
> {noformat}
> Unable to parse task structured output:
> /var/lib/ambari-agent/data/structured-out-5.json
> {noformat}
> This appears to be caused by an empty value being returned from
> {{resource_management.libraries.script.script.Script#disable_security}}.
> Rather then returning an empty value ({{None}}), return {{"\{\}"}} instead.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23438) Fix failing metrics unit tests on trunk.
[
https://issues.apache.org/jira/browse/AMBARI-23438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23438:
Labels: pull-request-available (was: )
> Fix failing metrics unit tests on trunk.
>
>
> Key: AMBARI-23438
> URL: https://issues.apache.org/jira/browse/AMBARI-23438
> 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
> Fix For: 2.7.0
>
>
> {code}
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.source.RawMetricsSourceTest.testRawMetricsSourcedAtFlushInterval
> org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.source.RawMetricsSourceTest.testRawMetricsCachedAndSourced
> org.apache.ambari.server.controller.internal.StackDefinedPropertyProviderTest.testStackDefinedPropertyProviderAsClusterAdministrator
> org.apache.ambari.server.controller.internal.StackDefinedPropertyProviderTest.testStackDefinedPropertyProviderAsAdministrator
> org.apache.ambari.server.controller.internal.StackDefinedPropertyProviderTest.testStackDefinedPropertyProviderAsServiceAdministrator
> org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testRbacForAMSPropertyProvider
> org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testPopulateResourcesForSingleHostMetric
> org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testPopulateResourcesForSingleHostMetricPointInTime
> org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testPopulateResourcesForMultipleHostMetricscPointInTime
> org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testPopulateResourcesForMultipleHostMetrics
> org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testPopulateResourcesForRegexpMetrics
> org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testPopulateResourcesForSingleComponentMetric
> org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testPopulateMetricsForEmbeddedHBase
> org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testAggregateFunctionForComponentMetrics
> org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testFilterOutOfBandMetricData
> org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testPopulateResourcesForHostComponentHostMetrics
> org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testPopulateResourcesForHostComponentMetricsForMultipleHosts
> org.apache.ambari.server.controller.metrics.timeline.AMSReportPropertyProviderTest.testPopulateResources
> org.apache.ambari.server.controller.metrics.timeline.AMSReportPropertyProviderTest.testPopulateResourceWithAggregateFunction
> org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23441) API Addition for Upgrade Plan for Config Changes
[ https://issues.apache.org/jira/browse/AMBARI-23441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23441: Labels: pull-request-available (was: ) > API Addition for Upgrade Plan for Config Changes > > > Key: AMBARI-23441 > URL: https://issues.apache.org/jira/browse/AMBARI-23441 > Project: Ambari > Issue Type: Task >Reporter: Nate Cole >Priority: Major > Labels: pull-request-available > > Add config changes per service group detail -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23441) API Addition for Upgrade Plan for Config Changes
Nate Cole created AMBARI-23441: -- Summary: API Addition for Upgrade Plan for Config Changes Key: AMBARI-23441 URL: https://issues.apache.org/jira/browse/AMBARI-23441 Project: Ambari Issue Type: Task Reporter: Nate Cole -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23318) API Addition for Upgrade Plan
[ https://issues.apache.org/jira/browse/AMBARI-23318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-23318: --- Summary: API Addition for Upgrade Plan (was: API Addition for Upgrade Plan for Config Changes) > API Addition for Upgrade Plan > - > > Key: AMBARI-23318 > URL: https://issues.apache.org/jira/browse/AMBARI-23318 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 3.0.0 > > > Add an endpoint to create upgrade plans. An upgrade plan holds all the > "configuration" settings for an upgrade, as well as the service groups and > target mpacks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23441) API Addition for Upgrade Plan for Config Changes
[ https://issues.apache.org/jira/browse/AMBARI-23441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-23441: --- Description: Add config changes per service group detail > API Addition for Upgrade Plan for Config Changes > > > Key: AMBARI-23441 > URL: https://issues.apache.org/jira/browse/AMBARI-23441 > Project: Ambari > Issue Type: Task >Reporter: Nate Cole >Priority: Major > > Add config changes per service group detail -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23318) API Addition for Upgrade Plan for Config Changes
[ https://issues.apache.org/jira/browse/AMBARI-23318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole resolved AMBARI-23318. Resolution: Fixed > API Addition for Upgrade Plan for Config Changes > > > Key: AMBARI-23318 > URL: https://issues.apache.org/jira/browse/AMBARI-23318 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 3.0.0 > > > Add an endpoint to create upgrade plans. An upgrade plan holds all the > "configuration" settings for an upgrade, as well as the service groups and > target mpacks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23318) API Addition for Upgrade Plan for Config Changes
[ https://issues.apache.org/jira/browse/AMBARI-23318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-23318: --- Summary: API Addition for Upgrade Plan for Config Changes (was: API Addition for Upgrade Plan) > API Addition for Upgrade Plan for Config Changes > > > Key: AMBARI-23318 > URL: https://issues.apache.org/jira/browse/AMBARI-23318 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 3.0.0 > > > Add an endpoint to create upgrade plans. An upgrade plan holds all the > "configuration" settings for an upgrade, as well as the service groups and > target mpacks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23440) 404 error while setting up SSO on a new cluster
Sandor Molnar created AMBARI-23440:
--
Summary: 404 error while setting up SSO on a new cluster
Key: AMBARI-23440
URL: https://issues.apache.org/jira/browse/AMBARI-23440
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Sandor Molnar
Assignee: Sandor Molnar
Fix For: 2.7.0
When setting up SSO via the Ambari server CLI using a new Ambari server
instance, the following error is encountered:
{noformat}
[root@c7401 ~]# ambari-server setup-sso
Using python /usr/bin/python
Setting up SSO authentication properties...
Enter Ambari Admin login: admin
Enter Ambari Admin password:
Fetching SSO configuration from DB.ERROR: Exiting with exit code 1.
REASON: Error while fetching SSO configuration. Error details: HTTP Error 404:
Not Found
{noformat}
This is caused by the lack of the {{sso-configuration}} category in the Ambari
configuration set - which will be a common scenario for new Ambari clusters.
{noformat}
GET
/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/sso-configuration
{noformat}
{noformat}
{
"status" : 404,
"message" : "The requested resource doesn't exist:
RootServiceComponentConfiguration not found where
Configuration/service_name=AMBARI AND
Configuration/component_name=AMBARI_SERVER AND
Configuration/category=sso-configuration."
}
{noformat}
The CLI handle this response and assume the following default values:
{noformat}
ambari.sso.manage_services = false
ambari.sso.enabled_services =
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23439) Overflowing list of frozen hosts in Assign Slaves and Clients page
[ https://issues.apache.org/jira/browse/AMBARI-23439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23439: Labels: pull-request-available (was: ) > Overflowing list of frozen hosts in Assign Slaves and Clients page > -- > > Key: AMBARI-23439 > URL: https://issues.apache.org/jira/browse/AMBARI-23439 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Attachments: Screen Shot 2018-03-30 at 9.06.19 AM.png > > > When more than 10 hosts are present in a deployed cluster, the frozen hosts > column in assign slaves and clients page overflows the boundary and is not > scrollable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23439) Overflowing list of frozen hosts in Assign Slaves and Clients page
[ https://issues.apache.org/jira/browse/AMBARI-23439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23439: - Description: When more than 10 hosts are present in a deployed cluster, the frozen hosts column in assign slaves and clients page overflows the boundary and is not scrollable. (was: When more than 10 hosts are present in a deployed cluster, the frozen hosts column in assign slaves and clients page overflows the boundary and is not scrollable. !Screen Shot 2018-03-30 at 9.06.19 AM.png!) > Overflowing list of frozen hosts in Assign Slaves and Clients page > -- > > Key: AMBARI-23439 > URL: https://issues.apache.org/jira/browse/AMBARI-23439 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Fix For: trunk > > Attachments: Screen Shot 2018-03-30 at 9.06.19 AM.png > > > When more than 10 hosts are present in a deployed cluster, the frozen hosts > column in assign slaves and clients page overflows the boundary and is not > scrollable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23439) Overflowing list of frozen hosts in Assign Slaves and Clients page
Ishan Bhatt created AMBARI-23439: Summary: Overflowing list of frozen hosts in Assign Slaves and Clients page Key: AMBARI-23439 URL: https://issues.apache.org/jira/browse/AMBARI-23439 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: trunk Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: trunk Attachments: Screen Shot 2018-03-30 at 9.06.19 AM.png When more than 10 hosts are present in a deployed cluster, the frozen hosts column in assign slaves and clients page overflows the boundary and is not scrollable. !Screen Shot 2018-03-30 at 9.06.19 AM.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23112) Some libraries are not relocated in ambari-metrics-common jar
[ https://issues.apache.org/jira/browse/AMBARI-23112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16424251#comment-16424251 ] Hudson commented on AMBARI-23112: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8969 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8969/]) Revert "AMBARI-23112 : Some libraries are not relocated in (avijayan: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=7dcff39b83f208b75e01ef8948e08682281ba457]) * (edit) ambari-metrics/ambari-metrics-common/pom.xml > Some libraries are not relocated in ambari-metrics-common jar > - > > Key: AMBARI-23112 > URL: https://issues.apache.org/jira/browse/AMBARI-23112 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-23112.patch > > Time Spent: 2h > Remaining Estimate: 0h > > Some libraries are not relocated in ambari-metrics-common jar, that means > some classes are exists in the jar, and those can be on the classpath as well > (with different versions), which can cause issues. > Libaries which are not shaded: (not sure that conventional, but i think we > should not include those dependencies in the uberjar if those are not shaded): > * commons-lang > * commons-math3 > * commons-codec > * jackson-xc > * jackson-core-asl / jackson-mapper-asl -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23438) Fix failing metrics unit tests on trunk.
Aravindan Vijayan created AMBARI-23438:
--
Summary: Fix failing metrics unit tests on trunk.
Key: AMBARI-23438
URL: https://issues.apache.org/jira/browse/AMBARI-23438
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: 2.7.0
Reporter: Aravindan Vijayan
Assignee: Aravindan Vijayan
Fix For: 2.7.0
{code}
org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.source.RawMetricsSourceTest.testRawMetricsSourcedAtFlushInterval
org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.source.RawMetricsSourceTest.testRawMetricsCachedAndSourced
org.apache.ambari.server.controller.internal.StackDefinedPropertyProviderTest.testStackDefinedPropertyProviderAsClusterAdministrator
org.apache.ambari.server.controller.internal.StackDefinedPropertyProviderTest.testStackDefinedPropertyProviderAsAdministrator
org.apache.ambari.server.controller.internal.StackDefinedPropertyProviderTest.testStackDefinedPropertyProviderAsServiceAdministrator
org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testRbacForAMSPropertyProvider
org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testPopulateResourcesForSingleHostMetric
org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testPopulateResourcesForSingleHostMetricPointInTime
org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testPopulateResourcesForMultipleHostMetricscPointInTime
org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testPopulateResourcesForMultipleHostMetrics
org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testPopulateResourcesForRegexpMetrics
org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testPopulateResourcesForSingleComponentMetric
org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testPopulateMetricsForEmbeddedHBase
org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testAggregateFunctionForComponentMetrics
org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testFilterOutOfBandMetricData
org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testPopulateResourcesForHostComponentHostMetrics
org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest.testPopulateResourcesForHostComponentMetricsForMultipleHosts
org.apache.ambari.server.controller.metrics.timeline.AMSReportPropertyProviderTest.testPopulateResources
org.apache.ambari.server.controller.metrics.timeline.AMSReportPropertyProviderTest.testPopulateResourceWithAggregateFunction
org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23437) Remove config_helper.py from resource_management library
Scott Duan created AMBARI-23437: --- Summary: Remove config_helper.py from resource_management library Key: AMBARI-23437 URL: https://issues.apache.org/jira/browse/AMBARI-23437 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Scott Duan Assignee: Scott Duan Fix For: 3.0.0 Use execution_command instead -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (AMBARI-23112) Some libraries are not relocated in ambari-metrics-common jar
[ https://issues.apache.org/jira/browse/AMBARI-23112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan reopened AMBARI-23112: Reverting due to unit test failures. > Some libraries are not relocated in ambari-metrics-common jar > - > > Key: AMBARI-23112 > URL: https://issues.apache.org/jira/browse/AMBARI-23112 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-23112.patch > > Time Spent: 1.5h > Remaining Estimate: 0h > > Some libraries are not relocated in ambari-metrics-common jar, that means > some classes are exists in the jar, and those can be on the classpath as well > (with different versions), which can cause issues. > Libaries which are not shaded: (not sure that conventional, but i think we > should not include those dependencies in the uberjar if those are not shaded): > * commons-lang > * commons-math3 > * commons-codec > * jackson-xc > * jackson-core-asl / jackson-mapper-asl -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23436) Integrate ServiceConfigVersionService resource and it's subresources with swagger
Gabor Boros created AMBARI-23436: Summary: Integrate ServiceConfigVersionService resource and it's subresources with swagger Key: AMBARI-23436 URL: https://issues.apache.org/jira/browse/AMBARI-23436 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 3.0.0 Reporter: Gabor Boros Assignee: Gabor Boros Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23201) Integrate View resources and subresources with swagger
[ https://issues.apache.org/jira/browse/AMBARI-23201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Boros resolved AMBARI-23201. -- Resolution: Done > Integrate View resources and subresources with swagger > -- > > Key: AMBARI-23201 > URL: https://issues.apache.org/jira/browse/AMBARI-23201 > Project: Ambari > Issue Type: Task >Reporter: Gabor Boros >Assignee: Gabor Boros >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23361) Integrate RequestScheduleService resource and it's subresources with swagger
[ https://issues.apache.org/jira/browse/AMBARI-23361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23361: Labels: pull-request-available (was: ) > Integrate RequestScheduleService resource and it's subresources with swagger > > > Key: AMBARI-23361 > URL: https://issues.apache.org/jira/browse/AMBARI-23361 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Gabor Boros >Assignee: Gabor Boros >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23430) Interpreter configs are not retained after zeppelin restart
[
https://issues.apache.org/jira/browse/AMBARI-23430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-23430:
---
Attachment: AMBARI-23430.patch
> Interpreter configs are not retained after zeppelin restart
> ---
>
> Key: AMBARI-23430
> URL: https://issues.apache.org/jira/browse/AMBARI-23430
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.7.0
>
> Attachments: AMBARI-23430.patch
>
>
> Interpreter configs are not retained after zeppelin restart. This issue is
> seen for below interpreters :
> {code}
> jdbc
> md
> sh
> spark2
> {code}
> Steps to repro:
> 1) Add or edit new property to any of the above mentioned interpreters
> 2) Restart Zeppelin
> 3) See that the changes are not retained
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23430) Interpreter configs are not retained after zeppelin restart
[
https://issues.apache.org/jira/browse/AMBARI-23430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-23430:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Interpreter configs are not retained after zeppelin restart
> ---
>
> Key: AMBARI-23430
> URL: https://issues.apache.org/jira/browse/AMBARI-23430
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.7.0
>
> Attachments: AMBARI-23430.patch
>
>
> Interpreter configs are not retained after zeppelin restart. This issue is
> seen for below interpreters :
> {code}
> jdbc
> md
> sh
> spark2
> {code}
> Steps to repro:
> 1) Add or edit new property to any of the above mentioned interpreters
> 2) Restart Zeppelin
> 3) See that the changes are not retained
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23430) Interpreter configs are not retained after zeppelin restart
[
https://issues.apache.org/jira/browse/AMBARI-23430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-23430:
---
Status: Patch Available (was: Open)
> Interpreter configs are not retained after zeppelin restart
> ---
>
> Key: AMBARI-23430
> URL: https://issues.apache.org/jira/browse/AMBARI-23430
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.7.0
>
> Attachments: AMBARI-23430.patch
>
>
> Interpreter configs are not retained after zeppelin restart. This issue is
> seen for below interpreters :
> {code}
> jdbc
> md
> sh
> spark2
> {code}
> Steps to repro:
> 1) Add or edit new property to any of the above mentioned interpreters
> 2) Restart Zeppelin
> 3) See that the changes are not retained
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23080) Log Search: use comositeId instead of implicit routing by default for collections
[ https://issues.apache.org/jira/browse/AMBARI-23080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23080: Labels: pull-request-available (was: ) > Log Search: use comositeId instead of implicit routing by default for > collections > - > > Key: AMBARI-23080 > URL: https://issues.apache.org/jira/browse/AMBARI-23080 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >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-23435) Update install wizard to use service groups
Jason Golieb created AMBARI-23435:
-
Summary: Update install wizard to use service groups
Key: AMBARI-23435
URL: https://issues.apache.org/jira/browse/AMBARI-23435
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 3.0.0
Reporter: Jason Golieb
Assignee: Jason Golieb
Fix For: 3.0.0
There are a number of API calls used in the install wizard that currently have
a \{defaultServiceGroupName} placeholder. These API calls need to be updated to
be compatible with multiple service groups. Everywhere they are used, the code
that uses them must also be updated to be multiple service group compatible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23074) Change the default datadir for Infra Solr
[ https://issues.apache.org/jira/browse/AMBARI-23074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16424041#comment-16424041 ] Hudson commented on AMBARI-23074: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8968 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8968/]) AMBARI-23074. Change the default datadir for Infra Solr. (#863) (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=eef8f141d6111b5dbf2ea8ee445b2f7070a98fb3]) * (edit) ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/configuration/infra-solr-env.xml * (edit) ambari-server/src/test/python/stacks/2.4/AMBARI_INFRA/test_infra_solr.py * (edit) ambari-server/src/test/python/stacks/2.4/configs/default.json > Change the default datadir for Infra Solr > - > > Key: AMBARI-23074 > URL: https://issues.apache.org/jira/browse/AMBARI-23074 > Project: Ambari > Issue Type: Bug > Components: ambari-infra, ambari-server >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Minor > 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] [Resolved] (AMBARI-23074) Change the default datadir for Infra Solr
[ https://issues.apache.org/jira/browse/AMBARI-23074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-23074. --- Resolution: Fixed > Change the default datadir for Infra Solr > - > > Key: AMBARI-23074 > URL: https://issues.apache.org/jira/browse/AMBARI-23074 > Project: Ambari > Issue Type: Bug > Components: ambari-infra, ambari-server >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Minor > 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] [Commented] (AMBARI-23434) Fix stack issues in HDFS to support Namenode Federation setup
[
https://issues.apache.org/jira/browse/AMBARI-23434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16423989#comment-16423989
]
Hudson commented on AMBARI-23434:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8967 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8967/])
AMBARI-23434. Fix stack issues in HDFS to support Namenode Federation
(aonishuk:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=0824ed2c7b8699f561ff18ce0d5c4508cfe65791])
* (edit)
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py
* (edit)
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py
* (edit) ambari-common/src/main/python/resource_management/core/shell.py
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/namenode_ha_utils.py
* (edit)
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode.py
* (edit)
ambari-common/src/main/python/resource_management/libraries/providers/hdfs_resource.py
* (edit) ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py
* (edit)
ambari-common/src/main/python/resource_management/core/providers/system.py
* (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/package/scripts/hdfs_namenode.py
> Fix stack issues in HDFS to support Namenode Federation setup
> -
>
> Key: AMBARI-23434
> URL: https://issues.apache.org/jira/browse/AMBARI-23434
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-23434.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> For example, here are 2 things I found to be probably wrong.
> 1\. Journal node restart failed because we cannot find hdfs-site :
> dfs.journalnode.edits.dir. We delete that property in the wizard. We may have
> to change that to dfs.journalnode.edits.dir.nameservice
> 2\. The following snippet in params_linux.py on HDFS 3.0 stack seems wrong. It
> has been designed to work with only 1 nameservice.
>
>
>
> dfs_ha_enabled = False
> dfs_ha_nameservices =
> default('/configurations/hdfs-site/dfs.internal.nameservices', None)
> if dfs_ha_nameservices is None:
> dfs_ha_nameservices =
> default('/configurations/hdfs-site/dfs.nameservices', None)
> dfs_ha_namenode_ids =
> default(format("/configurations/hdfs-site/dfs.ha.namenodes.{dfs_ha_nameservices}"),
> None)
>
> 3\. After setting up NN Fed, when I restart namenodes, I see the following
> error.
>
>
>
> main_resource.resource.security_enabled,
> main_resource.resource.logoutput)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
> line 154, in __init__
> security_enabled, run_user)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/functions/namenode_ha_utils.py",
> line 204, in get_property_for_active_namenode
> if INADDR_ANY in value and rpc_key in hdfs_site:
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found
> in configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter
> 'dfs.namenode.https-address.ns2.nn1' was not found in configurations
> dictionary!
>
> This is probably because the namenode_ha_utils is not equipped to handle
> multiple nameservices.
> We may have to create to fix such stack errors when the wizard is done.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23434) Fix stack issues in HDFS to support Namenode Federation setup
[
https://issues.apache.org/jira/browse/AMBARI-23434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23434:
Labels: pull-request-available (was: )
> Fix stack issues in HDFS to support Namenode Federation setup
> -
>
> Key: AMBARI-23434
> URL: https://issues.apache.org/jira/browse/AMBARI-23434
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-23434.patch
>
>
> For example, here are 2 things I found to be probably wrong.
> 1\. Journal node restart failed because we cannot find hdfs-site :
> dfs.journalnode.edits.dir. We delete that property in the wizard. We may have
> to change that to dfs.journalnode.edits.dir.nameservice
> 2\. The following snippet in params_linux.py on HDFS 3.0 stack seems wrong. It
> has been designed to work with only 1 nameservice.
>
>
>
> dfs_ha_enabled = False
> dfs_ha_nameservices =
> default('/configurations/hdfs-site/dfs.internal.nameservices', None)
> if dfs_ha_nameservices is None:
> dfs_ha_nameservices =
> default('/configurations/hdfs-site/dfs.nameservices', None)
> dfs_ha_namenode_ids =
> default(format("/configurations/hdfs-site/dfs.ha.namenodes.{dfs_ha_nameservices}"),
> None)
>
> 3\. After setting up NN Fed, when I restart namenodes, I see the following
> error.
>
>
>
> main_resource.resource.security_enabled,
> main_resource.resource.logoutput)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
> line 154, in __init__
> security_enabled, run_user)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/functions/namenode_ha_utils.py",
> line 204, in get_property_for_active_namenode
> if INADDR_ANY in value and rpc_key in hdfs_site:
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found
> in configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter
> 'dfs.namenode.https-address.ns2.nn1' was not found in configurations
> dictionary!
>
> This is probably because the namenode_ha_utils is not equipped to handle
> multiple nameservices.
> We may have to create to fix such stack errors when the wizard is done.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23434) Fix stack issues in HDFS to support Namenode Federation setup
[
https://issues.apache.org/jira/browse/AMBARI-23434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-23434:
-
Status: Patch Available (was: Open)
> Fix stack issues in HDFS to support Namenode Federation setup
> -
>
> Key: AMBARI-23434
> URL: https://issues.apache.org/jira/browse/AMBARI-23434
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Fix For: 2.7.0
>
> Attachments: AMBARI-23434.patch
>
>
> For example, here are 2 things I found to be probably wrong.
> 1\. Journal node restart failed because we cannot find hdfs-site :
> dfs.journalnode.edits.dir. We delete that property in the wizard. We may have
> to change that to dfs.journalnode.edits.dir.nameservice
> 2\. The following snippet in params_linux.py on HDFS 3.0 stack seems wrong. It
> has been designed to work with only 1 nameservice.
>
>
>
> dfs_ha_enabled = False
> dfs_ha_nameservices =
> default('/configurations/hdfs-site/dfs.internal.nameservices', None)
> if dfs_ha_nameservices is None:
> dfs_ha_nameservices =
> default('/configurations/hdfs-site/dfs.nameservices', None)
> dfs_ha_namenode_ids =
> default(format("/configurations/hdfs-site/dfs.ha.namenodes.{dfs_ha_nameservices}"),
> None)
>
> 3\. After setting up NN Fed, when I restart namenodes, I see the following
> error.
>
>
>
> main_resource.resource.security_enabled,
> main_resource.resource.logoutput)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
> line 154, in __init__
> security_enabled, run_user)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/functions/namenode_ha_utils.py",
> line 204, in get_property_for_active_namenode
> if INADDR_ANY in value and rpc_key in hdfs_site:
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found
> in configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter
> 'dfs.namenode.https-address.ns2.nn1' was not found in configurations
> dictionary!
>
> This is probably because the namenode_ha_utils is not equipped to handle
> multiple nameservices.
> We may have to create to fix such stack errors when the wizard is done.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23434) Fix stack issues in HDFS to support Namenode Federation setup
[
https://issues.apache.org/jira/browse/AMBARI-23434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-23434:
-
Attachment: AMBARI-23434.patch
> Fix stack issues in HDFS to support Namenode Federation setup
> -
>
> Key: AMBARI-23434
> URL: https://issues.apache.org/jira/browse/AMBARI-23434
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Fix For: 2.7.0
>
> Attachments: AMBARI-23434.patch
>
>
> For example, here are 2 things I found to be probably wrong.
> 1\. Journal node restart failed because we cannot find hdfs-site :
> dfs.journalnode.edits.dir. We delete that property in the wizard. We may have
> to change that to dfs.journalnode.edits.dir.nameservice
> 2\. The following snippet in params_linux.py on HDFS 3.0 stack seems wrong. It
> has been designed to work with only 1 nameservice.
>
>
>
> dfs_ha_enabled = False
> dfs_ha_nameservices =
> default('/configurations/hdfs-site/dfs.internal.nameservices', None)
> if dfs_ha_nameservices is None:
> dfs_ha_nameservices =
> default('/configurations/hdfs-site/dfs.nameservices', None)
> dfs_ha_namenode_ids =
> default(format("/configurations/hdfs-site/dfs.ha.namenodes.{dfs_ha_nameservices}"),
> None)
>
> 3\. After setting up NN Fed, when I restart namenodes, I see the following
> error.
>
>
>
> main_resource.resource.security_enabled,
> main_resource.resource.logoutput)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
> line 154, in __init__
> security_enabled, run_user)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/functions/namenode_ha_utils.py",
> line 204, in get_property_for_active_namenode
> if INADDR_ANY in value and rpc_key in hdfs_site:
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found
> in configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter
> 'dfs.namenode.https-address.ns2.nn1' was not found in configurations
> dictionary!
>
> This is probably because the namenode_ha_utils is not equipped to handle
> multiple nameservices.
> We may have to create to fix such stack errors when the wizard is done.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23434) Fix stack issues in HDFS to support Namenode Federation setup
Andrew Onischuk created AMBARI-23434:
Summary: Fix stack issues in HDFS to support Namenode Federation
setup
Key: AMBARI-23434
URL: https://issues.apache.org/jira/browse/AMBARI-23434
Project: Ambari
Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
Fix For: 2.7.0
Attachments: AMBARI-23434.patch
For example, here are 2 things I found to be probably wrong.
1\. Journal node restart failed because we cannot find hdfs-site :
dfs.journalnode.edits.dir. We delete that property in the wizard. We may have
to change that to dfs.journalnode.edits.dir.nameservice
2\. The following snippet in params_linux.py on HDFS 3.0 stack seems wrong. It
has been designed to work with only 1 nameservice.
dfs_ha_enabled = False
dfs_ha_nameservices =
default('/configurations/hdfs-site/dfs.internal.nameservices', None)
if dfs_ha_nameservices is None:
dfs_ha_nameservices =
default('/configurations/hdfs-site/dfs.nameservices', None)
dfs_ha_namenode_ids =
default(format("/configurations/hdfs-site/dfs.ha.namenodes.{dfs_ha_nameservices}"),
None)
3\. After setting up NN Fed, when I restart namenodes, I see the following
error.
main_resource.resource.security_enabled,
main_resource.resource.logoutput)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
line 154, in __init__
security_enabled, run_user)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/functions/namenode_ha_utils.py",
line 204, in get_property_for_active_namenode
if INADDR_ANY in value and rpc_key in hdfs_site:
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/config_dictionary.py",
line 73, in __getattr__
raise Fail("Configuration parameter '" + self.name + "' was not found
in configurations dictionary!")
resource_management.core.exceptions.Fail: Configuration parameter
'dfs.namenode.https-address.ns2.nn1' was not found in configurations dictionary!
This is probably because the namenode_ha_utils is not equipped to handle
multiple nameservices.
We may have to create to fix such stack errors when the wizard is done.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23428) Log Search / Log Feeder: Set kerberos related solr properties through java opts
[ https://issues.apache.org/jira/browse/AMBARI-23428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16423917#comment-16423917 ] Hudson commented on AMBARI-23428: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8966 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8966/]) AMBARI-23428. Log Search / Log Feeder: Set kerberos related solr (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=c5596a8c2ab086faa4d970188531128fdff392d3]) * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/configurer/SolrCollectionConfigurer.java * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/properties/logsearch-env.sh.j2 * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/properties/logfeeder-env.sh.j2 * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/OutputSolr.java > Log Search / Log Feeder: Set kerberos related solr properties through java > opts > > > Key: AMBARI-23428 > URL: https://issues.apache.org/jira/browse/AMBARI-23428 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, 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: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23433) Remove unnecessary properties from the Ranger SSO configuration updates via the stack advisor
Robert Levas created AMBARI-23433:
-
Summary: Remove unnecessary properties from the Ranger SSO
configuration updates via the stack advisor
Key: AMBARI-23433
URL: https://issues.apache.org/jira/browse/AMBARI-23433
Project: Ambari
Issue Type: Task
Components: ambari-admin
Affects Versions: 2.7.0
Reporter: Robert Levas
Assignee: Robert Levas
Fix For: 2.7.0
Remove unnecessary properties from the Ranger SSO configuration updates via the
stack advisor
* {{ranger.sso.cookiename}}
* {{ranger.sso.query.param.originalurl}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23432) Cannot save edited repository urls in Ambari Version UI
[
https://issues.apache.org/jira/browse/AMBARI-23432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23432:
Labels: pull-request-available (was: )
> Cannot save edited repository urls in Ambari Version UI
> ---
>
> Key: AMBARI-23432
> URL: https://issues.apache.org/jira/browse/AMBARI-23432
> 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
>
>
> When attempting to Save an edited Repository URL the browser reports the
> following error (Chrome):
> {noformat}
> vendor.js:26942 TypeError: Cannot read property 'primaryClass' of undefined
> at new $modal.open.controller
> (http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/main.js:7972:41)
> at Object.instantiate
> (http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:17529:14)
> at $controller
> (http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:23350:28)
> at resolveSuccess
> (http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:52701:32)
> at processQueue
> (http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:29439:28)
> at
> http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:29455:27
> at Scope.$eval
> (http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:30737:28)
> at Scope.$digest
> (http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:30551:31)
> at Scope.$apply
> (http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:30845:24)
> at done
> (http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:24825:47)
> undefined
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23074) Change the default datadir for Infra Solr
[ https://issues.apache.org/jira/browse/AMBARI-23074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23074: Labels: pull-request-available (was: ) > Change the default datadir for Infra Solr > - > > Key: AMBARI-23074 > URL: https://issues.apache.org/jira/browse/AMBARI-23074 > Project: Ambari > Issue Type: Bug > Components: ambari-infra, ambari-server >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Minor > Labels: pull-request-available > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23428) Log Search / Log Feeder: Set kerberos related solr properties through java opts
[ https://issues.apache.org/jira/browse/AMBARI-23428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-23428. --- Resolution: Fixed > Log Search / Log Feeder: Set kerberos related solr properties through java > opts > > > Key: AMBARI-23428 > URL: https://issues.apache.org/jira/browse/AMBARI-23428 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, 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: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23432) Cannot save edited repository urls in Ambari Version UI
[
https://issues.apache.org/jira/browse/AMBARI-23432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-23432:
--
Description:
When attempting to Save an edited Repository URL the browser reports the
following error (Chrome):
{noformat}
vendor.js:26942 TypeError: Cannot read property 'primaryClass' of undefined
at new $modal.open.controller
(http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/main.js:7972:41)
at Object.instantiate
(http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:17529:14)
at $controller
(http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:23350:28)
at resolveSuccess
(http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:52701:32)
at processQueue
(http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:29439:28)
at
http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:29455:27
at Scope.$eval
(http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:30737:28)
at Scope.$digest
(http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:30551:31)
at Scope.$apply
(http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:30845:24)
at done
(http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:24825:47)
undefined
{noformat}
was:
When attempting to Save an edited Repository URL the browser reports the
following error (Chrome):
{noformat}
vendor.js:26942 TypeError: Cannot read property 'primaryClass' of undefined
at new $modal.open.controller
(http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/main.js:7972:41)
at Object.instantiate
(http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:17529:14)
at $controller
(http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:23350:28)
at resolveSuccess
(http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:52701:32)
at processQueue
(http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:29439:28)
at
http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:29455:27
at Scope.$eval
(http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:30737:28)
at Scope.$digest
(http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:30551:31)
at Scope.$apply
(http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:30845:24)
at done
(http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:24825:47)
undefined
{noformat}
See snapshot attached:
!image-2018-04-02-11-54-10-854.png|thumbnail!
> Cannot save edited repository urls in Ambari Version UI
> ---
>
> Key: AMBARI-23432
> URL: https://issues.apache.org/jira/browse/AMBARI-23432
> 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
>
>
> When attempting to Save an edited Repository URL the browser reports the
> following error (Chrome):
> {noformat}
> vendor.js:26942 TypeError: Cannot read property 'primaryClass' of undefined
> at new $modal.open.controller
> (http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/main.js:7972:41)
> at Object.instantiate
> (http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:17529:14)
> at $controller
> (http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:23350:28)
> at resolveSuccess
> (http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:52701:32)
> at processQueue
> (http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:29439:28)
> at
> http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:29455:27
> at Scope.$eval
>
[jira] [Created] (AMBARI-23432) Cannot save edited repository urls in Ambari Version UI
Andrii Tkach created AMBARI-23432:
-
Summary: Cannot save edited repository urls in Ambari Version UI
Key: AMBARI-23432
URL: https://issues.apache.org/jira/browse/AMBARI-23432
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.7.0
Reporter: Andrii Tkach
Assignee: Andrii Tkach
Fix For: 2.7.0
When attempting to Save an edited Repository URL the browser reports the
following error (Chrome):
{noformat}
vendor.js:26942 TypeError: Cannot read property 'primaryClass' of undefined
at new $modal.open.controller
(http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/main.js:7972:41)
at Object.instantiate
(http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:17529:14)
at $controller
(http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:23350:28)
at resolveSuccess
(http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:52701:32)
at processQueue
(http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:29439:28)
at
http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:29455:27
at Scope.$eval
(http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:30737:28)
at Scope.$digest
(http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:30551:31)
at Scope.$apply
(http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:30845:24)
at done
(http://ydavis-hdf-bug-94554-1.openstacklocal:8080/views/ADMIN_VIEW/2.7.0.0/INSTANCE/scripts/vendor.js:24825:47)
undefined
{noformat}
See snapshot attached:
!image-2018-04-02-11-54-10-854.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23401) Problems while selecting the property uniquely in Configurations screen while installation
[
https://issues.apache.org/jira/browse/AMBARI-23401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16423878#comment-16423878
]
Hudson commented on AMBARI-23401:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8965 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8965/])
AMBARI-23401 Problems while selecting the property uniquely in (1963907+atkach:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=f7a57625d0c448479a02f8e4f4674df626fed4b4])
* (edit) ambari-web/app/views/common/controls_view.js
> Problems while selecting the property uniquely in Configurations screen while
> installation
> --
>
> Key: AMBARI-23401
> URL: https://issues.apache.org/jira/browse/AMBARI-23401
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: screenshot-1[1].png, screenshot-2[1].png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> While scripting the automation code for the new UI installer, could not
> select some properties uniquely and some problems faced:
> # Unable to select some properties by their label in xpath:
> {panel}
> * In Advanced zeppelin-config panel under Zeppelin configurations, there are
> a bunch of configurations related to zeppelin.ssl. As seen in screenshot-1,
> all the labels have zeppelin.ssl in them and if one were to type textbox with
> label zeppelin.ssl using XPATH strict text match, i.e.
> //*[text()=’zeppelin.ssl’], it fails. This is because within the label there
> are some html elements (see screenshot-1) like which do not allow a
> strict match to the label.
> * A simple workaround would be to use xpath contains() operator, but it would
> return multiple fields for the same label, which is not good.
> {panel}
> # Try to select the property by ‘data-qa’ also has similar problems to above
> {panel}
> As per screenshot-2, the data-qa attribute has the value
> ‘service-config-zeppelin-ssl-zeppelin-config-xml-default’ which can only be
> covered by xpath //*[contains(@data-qa,’zeppelin-ssl’)]. But this would again
> lead to multiple matches in the UI.
> {panel}
> Two asks from a test automation point of view:
> # Remove any HTML entity from in between the label text
> {panel}
> Example: zeppelin.ssl to zeppelin.ssl
> {panel}
> # Set the data-qa attribute for the input fields to just the property name as
> specified in Blueprint. For example, if the Blueprint property is
> ‘zeppelin.ssl’, the data-qa attribute can be ‘zeppelin-ssl’.
>
> This would enable the automation code to uniquely identify the property
> fields.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23423) JS error while deploying new service
[
https://issues.apache.org/jira/browse/AMBARI-23423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23423:
Labels: pull-request-available (was: )
> JS error while deploying new service
>
>
> Key: AMBARI-23423
> URL: https://issues.apache.org/jira/browse/AMBARI-23423
> 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
>
>
> {noformat}
> " could not respond to event setProperty in state
> rootState.loading."
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23431) After enabling Kerberos, the Ambari JAAS file is not updated
Sandor Molnar created AMBARI-23431:
--
Summary: After enabling Kerberos, the Ambari JAAS file is not
updated
Key: AMBARI-23431
URL: https://issues.apache.org/jira/browse/AMBARI-23431
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Sandor Molnar
Assignee: Sandor Molnar
Fix For: 2.7.0
After enabling Kerberos, the Ambari JAAS file is not updated. This leads to
various errors like collecting JXM data from services:
{noformat}
28 Mar 2018 15:40:29,041 WARN [ambari-metrics-retrieval-service-thread-4]
RequestTargetAuthentication:88 - NEGOTIATE authentication error: No valid
credentials provided (Mechanism level: No valid credentials provided (Mechanism
level: Attempt to obtain new INITIATE credentials fai
led! (null)))
28 Mar 2018 15:40:29,042 ERROR [ambari-metrics-retrieval-service-thread-4]
AppCookieManager:122 - SPNego authentication failed, can not get hadoop.auth
cookie for URL: http://c7401.ambari.apache.org:50070/jmx
28 Mar 2018 15:40:29,042 ERROR [ambari-metrics-retrieval-service-thread-5]
AppCookieManager:122 - SPNego authentication failed, can not get hadoop.auth
cookie for URL:
http://c7401.ambari.apache.org:50070/jmx?get=Hadoop:service=NameNode,name=FSNamesystem::tag.HAState
2
{noformat}
The JAAS file as {{/etc/ambari-server/conf/krb5JAASLogin.conf}} is expected to
be updated to match the created Kerberos identity for the Ambari server, but is
not:
The default values of
{noformat}
...
keyTab="/etc/security/keytabs/ambari.keytab"
principal="amb...@example.com"
...
{noformat}
Should have been changed to
{noformat}
...
keyTab="/etc/security/keytabs/ambari.server.keytab"
principal="ambari-server...@example.com"
...
{noformat}
After manually fixing this and restarting Ambari, the JMX requests
authenticated properly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23407) Issues for no NN federation case appearing after federation support implementation
[
https://issues.apache.org/jira/browse/AMBARI-23407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16423842#comment-16423842
]
Hudson commented on AMBARI-23407:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8964 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8964/])
AMBARI-23407 Issues for no NN federation case appearing after federation
(github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=a7a34e40399d482edcc06fbb64e932519db0daeb])
* (edit) ambari-web/app/models/service/hdfs.js
* (edit) ambari-web/app/templates/main/service/services/hdfs.hbs
* (edit) ambari-web/app/views/main/dashboard/widgets/namenode_cpu.js
* (edit) ambari-web/app/controllers/global/update_controller.js
* (edit) ambari-web/app/views/main/service/info/summary/hdfs/widgets.js
* (edit) ambari-web/test/views/main/dashboard/widgets_test.js
* (edit) ambari-web/app/app.js
* (edit) ambari-web/app/views/main/dashboard/widgets.js
* (edit) ambari-web/app/templates/main/dashboard/widgets.hbs
* (edit) ambari-web/app/views/main/service/info/summary.js
> Issues for no NN federation case appearing after federation support
> implementation
> --
>
> Key: AMBARI-23407
> URL: https://issues.apache.org/jira/browse/AMBARI-23407
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> - HDFS links dropdown on dashboard isn't displayed with JS error thrown:
> {{Uncaught TypeError: Cannot read property 'hosts' of undefined}}
> - 'N/A' / 'Not Running' is displayed for NameNode Uptime instead of actual
> value
> - Incorrect values in Service metrics section of service summary page
> - Order of dashboard widgets is not restored
> - Incorrect value of NameNode RPC on host summary page
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-23407) Issues for no NN federation case appearing after federation support implementation
[
https://issues.apache.org/jira/browse/AMBARI-23407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Babiichuk resolved AMBARI-23407.
---
Resolution: Fixed
Merged to trunk
> Issues for no NN federation case appearing after federation support
> implementation
> --
>
> Key: AMBARI-23407
> URL: https://issues.apache.org/jira/browse/AMBARI-23407
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> - HDFS links dropdown on dashboard isn't displayed with JS error thrown:
> {{Uncaught TypeError: Cannot read property 'hosts' of undefined}}
> - 'N/A' / 'Not Running' is displayed for NameNode Uptime instead of actual
> value
> - Incorrect values in Service metrics section of service summary page
> - Order of dashboard widgets is not restored
> - Incorrect value of NameNode RPC on host summary page
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-23401) Problems while selecting the property uniquely in Configurations screen while installation
[
https://issues.apache.org/jira/browse/AMBARI-23401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach resolved AMBARI-23401.
---
Resolution: Fixed
> Problems while selecting the property uniquely in Configurations screen while
> installation
> --
>
> Key: AMBARI-23401
> URL: https://issues.apache.org/jira/browse/AMBARI-23401
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: screenshot-1[1].png, screenshot-2[1].png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> While scripting the automation code for the new UI installer, could not
> select some properties uniquely and some problems faced:
> # Unable to select some properties by their label in xpath:
> {panel}
> * In Advanced zeppelin-config panel under Zeppelin configurations, there are
> a bunch of configurations related to zeppelin.ssl. As seen in screenshot-1,
> all the labels have zeppelin.ssl in them and if one were to type textbox with
> label zeppelin.ssl using XPATH strict text match, i.e.
> //*[text()=’zeppelin.ssl’], it fails. This is because within the label there
> are some html elements (see screenshot-1) like which do not allow a
> strict match to the label.
> * A simple workaround would be to use xpath contains() operator, but it would
> return multiple fields for the same label, which is not good.
> {panel}
> # Try to select the property by ‘data-qa’ also has similar problems to above
> {panel}
> As per screenshot-2, the data-qa attribute has the value
> ‘service-config-zeppelin-ssl-zeppelin-config-xml-default’ which can only be
> covered by xpath //*[contains(@data-qa,’zeppelin-ssl’)]. But this would again
> lead to multiple matches in the UI.
> {panel}
> Two asks from a test automation point of view:
> # Remove any HTML entity from in between the label text
> {panel}
> Example: zeppelin.ssl to zeppelin.ssl
> {panel}
> # Set the data-qa attribute for the input fields to just the property name as
> specified in Blueprint. For example, if the Blueprint property is
> ‘zeppelin.ssl’, the data-qa attribute can be ‘zeppelin-ssl’.
>
> This would enable the automation code to uniquely identify the property
> fields.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23401) Problems while selecting the property uniquely in Configurations screen while installation
[
https://issues.apache.org/jira/browse/AMBARI-23401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16423830#comment-16423830
]
Andrii Tkach commented on AMBARI-23401:
---
committed to trunk
> Problems while selecting the property uniquely in Configurations screen while
> installation
> --
>
> Key: AMBARI-23401
> URL: https://issues.apache.org/jira/browse/AMBARI-23401
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: screenshot-1[1].png, screenshot-2[1].png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> While scripting the automation code for the new UI installer, could not
> select some properties uniquely and some problems faced:
> # Unable to select some properties by their label in xpath:
> {panel}
> * In Advanced zeppelin-config panel under Zeppelin configurations, there are
> a bunch of configurations related to zeppelin.ssl. As seen in screenshot-1,
> all the labels have zeppelin.ssl in them and if one were to type textbox with
> label zeppelin.ssl using XPATH strict text match, i.e.
> //*[text()=’zeppelin.ssl’], it fails. This is because within the label there
> are some html elements (see screenshot-1) like which do not allow a
> strict match to the label.
> * A simple workaround would be to use xpath contains() operator, but it would
> return multiple fields for the same label, which is not good.
> {panel}
> # Try to select the property by ‘data-qa’ also has similar problems to above
> {panel}
> As per screenshot-2, the data-qa attribute has the value
> ‘service-config-zeppelin-ssl-zeppelin-config-xml-default’ which can only be
> covered by xpath //*[contains(@data-qa,’zeppelin-ssl’)]. But this would again
> lead to multiple matches in the UI.
> {panel}
> Two asks from a test automation point of view:
> # Remove any HTML entity from in between the label text
> {panel}
> Example: zeppelin.ssl to zeppelin.ssl
> {panel}
> # Set the data-qa attribute for the input fields to just the property name as
> specified in Blueprint. For example, if the Blueprint property is
> ‘zeppelin.ssl’, the data-qa attribute can be ‘zeppelin-ssl’.
>
> This would enable the automation code to uniquely identify the property
> fields.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23401) Problems while selecting the property uniquely in Configurations screen while installation
[
https://issues.apache.org/jira/browse/AMBARI-23401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23401:
Labels: pull-request-available (was: )
> Problems while selecting the property uniquely in Configurations screen while
> installation
> --
>
> Key: AMBARI-23401
> URL: https://issues.apache.org/jira/browse/AMBARI-23401
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: screenshot-1[1].png, screenshot-2[1].png
>
>
> While scripting the automation code for the new UI installer, could not
> select some properties uniquely and some problems faced:
> # Unable to select some properties by their label in xpath:
> {panel}
> * In Advanced zeppelin-config panel under Zeppelin configurations, there are
> a bunch of configurations related to zeppelin.ssl. As seen in screenshot-1,
> all the labels have zeppelin.ssl in them and if one were to type textbox with
> label zeppelin.ssl using XPATH strict text match, i.e.
> //*[text()=’zeppelin.ssl’], it fails. This is because within the label there
> are some html elements (see screenshot-1) like which do not allow a
> strict match to the label.
> * A simple workaround would be to use xpath contains() operator, but it would
> return multiple fields for the same label, which is not good.
> {panel}
> # Try to select the property by ‘data-qa’ also has similar problems to above
> {panel}
> As per screenshot-2, the data-qa attribute has the value
> ‘service-config-zeppelin-ssl-zeppelin-config-xml-default’ which can only be
> covered by xpath //*[contains(@data-qa,’zeppelin-ssl’)]. But this would again
> lead to multiple matches in the UI.
> {panel}
> Two asks from a test automation point of view:
> # Remove any HTML entity from in between the label text
> {panel}
> Example: zeppelin.ssl to zeppelin.ssl
> {panel}
> # Set the data-qa attribute for the input fields to just the property name as
> specified in Blueprint. For example, if the Blueprint property is
> ‘zeppelin.ssl’, the data-qa attribute can be ‘zeppelin-ssl’.
>
> This would enable the automation code to uniquely identify the property
> fields.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23430) Interpreter configs are not retained after zeppelin restart
Vitaly Brodetskyi created AMBARI-23430:
--
Summary: Interpreter configs are not retained after zeppelin
restart
Key: AMBARI-23430
URL: https://issues.apache.org/jira/browse/AMBARI-23430
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
Fix For: 2.7.0
Interpreter configs are not retained after zeppelin restart. This issue is seen
for below interpreters :
{code}
jdbc
md
sh
spark2
{code}
Steps to repro:
1) Add or edit new property to any of the above mentioned interpreters
2) Restart Zeppelin
3) See that the changes are not retained
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23424) Need to add new property for Ranger-Tagsync when enabling federation for Namenode-HA via UI wizard
[
https://issues.apache.org/jira/browse/AMBARI-23424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16423754#comment-16423754
]
Hudson commented on AMBARI-23424:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8963 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8963/])
AMBARI-23424. Need to add new property for Ranger-Tagsync when enabling
(aleksandrkovalenko:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=95f9e81cd5f4d9882f8b63316336c31ed8896d6a])
* (edit) ambari-web/app/messages.js
* (edit) ambari-web/app/controllers/main/admin/federation/step3_controller.js
* (edit) ambari-web/app/controllers/main/admin/federation/step4_controller.js
* (edit) ambari-web/app/data/configs/wizards/federation_properties.js
> Need to add new property for Ranger-Tagsync when enabling federation for
> Namenode-HA via UI wizard
> --
>
> Key: AMBARI-23424
> URL: https://issues.apache.org/jira/browse/AMBARI-23424
> Project: Ambari
> Issue Type: Bug
> 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
>
> Need to dynamically add properties in config-type {{ranger-tagsync-site}}
> from UI for Federation wizard. This should be done when Atlas and
> Ranger-Tagsync service is installed.
> When federation is Enabled for HDFS, in this case for each name-service, we
> will need to add a property in config-type {{ranger-tagsync-site}} using
> below format:
> {noformat}ranger.tagsync.atlas.hdfs.instance..nameservice..ranger.service=
> {noformat}
> The Ranger service name can be derived from logic as below:
> If the value for property {{ranger.plugin.hdfs.service.name}} is default i.e.
> repo_name then the value for above property will be in the format:
> {noformat}_hadoop_{noformat}
> for e.g if the cluster-name is {{testcl1}} and the name-services are {{ns1}}
> , {{ns2}} and the {{ranger.plugin.hdfs.service.name}} has value
> repo_name then the property-value will be as below:
> ranger.tagsync.atlas.hdfs.instance.testcl1.nameservice.ns1.ranger.service=testcl1_hadoop_ns1
> ranger.tagsync.atlas.hdfs.instance.testcl1.nameservice.ns2.ranger.service=testcl1_hadoop_ns2
> If the user has a custom-value for the property
> {{ranger.plugin.hdfs.service.name}} i.e. not repo_name, then we will
> need to use the value provided in for property
> {{ranger.plugin.hdfs.service.name}} and use the format as
> _.
> for e.g if the cluster-name is {{testcl1}} and the name-services are {{ns1}}
> , {{ns2}} and the {{ranger.plugin.hdfs.service.name}} has value
> {{hadoop_service}} then the property-value will be as below:
> ranger.tagsync.atlas.hdfs.instance.testcl1.nameservice.ns1.ranger.service=hadoop_service_ns1
> ranger.tagsync.atlas.hdfs.instance.testcl1.nameservice.ns2.ranger.service=hadoop_service_ns2
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-23424) Need to add new property for Ranger-Tagsync when enabling federation for Namenode-HA via UI wizard
[
https://issues.apache.org/jira/browse/AMBARI-23424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko resolved AMBARI-23424.
--
Resolution: Fixed
> Need to add new property for Ranger-Tagsync when enabling federation for
> Namenode-HA via UI wizard
> --
>
> Key: AMBARI-23424
> URL: https://issues.apache.org/jira/browse/AMBARI-23424
> Project: Ambari
> Issue Type: Bug
> 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
>
> Need to dynamically add properties in config-type {{ranger-tagsync-site}}
> from UI for Federation wizard. This should be done when Atlas and
> Ranger-Tagsync service is installed.
> When federation is Enabled for HDFS, in this case for each name-service, we
> will need to add a property in config-type {{ranger-tagsync-site}} using
> below format:
> {noformat}ranger.tagsync.atlas.hdfs.instance..nameservice..ranger.service=
> {noformat}
> The Ranger service name can be derived from logic as below:
> If the value for property {{ranger.plugin.hdfs.service.name}} is default i.e.
> repo_name then the value for above property will be in the format:
> {noformat}_hadoop_{noformat}
> for e.g if the cluster-name is {{testcl1}} and the name-services are {{ns1}}
> , {{ns2}} and the {{ranger.plugin.hdfs.service.name}} has value
> repo_name then the property-value will be as below:
> ranger.tagsync.atlas.hdfs.instance.testcl1.nameservice.ns1.ranger.service=testcl1_hadoop_ns1
> ranger.tagsync.atlas.hdfs.instance.testcl1.nameservice.ns2.ranger.service=testcl1_hadoop_ns2
> If the user has a custom-value for the property
> {{ranger.plugin.hdfs.service.name}} i.e. not repo_name, then we will
> need to use the value provided in for property
> {{ranger.plugin.hdfs.service.name}} and use the format as
> _.
> for e.g if the cluster-name is {{testcl1}} and the name-services are {{ns1}}
> , {{ns2}} and the {{ranger.plugin.hdfs.service.name}} has value
> {{hadoop_service}} then the property-value will be as below:
> ranger.tagsync.atlas.hdfs.instance.testcl1.nameservice.ns1.ranger.service=hadoop_service_ns1
> ranger.tagsync.atlas.hdfs.instance.testcl1.nameservice.ns2.ranger.service=hadoop_service_ns2
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23428) Log Search / Log Feeder: Set kerberos related solr properties through java opts
[ https://issues.apache.org/jira/browse/AMBARI-23428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23428: Labels: pull-request-available (was: ) > Log Search / Log Feeder: Set kerberos related solr properties through java > opts > > > Key: AMBARI-23428 > URL: https://issues.apache.org/jira/browse/AMBARI-23428 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, 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] [Updated] (AMBARI-23429) Not able to install METRICS_MONITOR
[
https://issues.apache.org/jira/browse/AMBARI-23429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23429:
Labels: pull-request-available (was: )
> Not able to install METRICS_MONITOR
> ---
>
> Key: AMBARI-23429
> URL: https://issues.apache.org/jira/browse/AMBARI-23429
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Srikanth Janardhan
>Assignee: Srikanth Janardhan
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
>
> ambari version - 2.7.0.0-246
> metrics monitor installation failed due to below error
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
> line 72, in
> AmsMonitor().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
> line 28, in install
> import params
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/params.py",
> line 376, in
> if hbase_wal_dir and re.search("^file://|/", hbase_wal_dir): #If wal dir
> is on local file system, create it.
> NameError: name 're' is not defined
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
> line 72, in
> AmsMonitor().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
> line 28, in install
> import params
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/params.py",
> line 376, in
> if hbase_wal_dir and re.search("^file://|/", hbase_wal_dir): #If wal dir
> is on local file system, create it.
> NameError: name 're' is not defined
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23429) Not able to install METRICS_MONITOR
[
https://issues.apache.org/jira/browse/AMBARI-23429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Janardhan updated AMBARI-23429:
Component/s: (was: ambari-agent)
ambari-server
> Not able to install METRICS_MONITOR
> ---
>
> Key: AMBARI-23429
> URL: https://issues.apache.org/jira/browse/AMBARI-23429
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Srikanth Janardhan
>Assignee: Srikanth Janardhan
>Priority: Blocker
> Fix For: 2.7.0
>
>
> ambari version - 2.7.0.0-246
> metrics monitor installation failed due to below error
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
> line 72, in
> AmsMonitor().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
> line 28, in install
> import params
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/params.py",
> line 376, in
> if hbase_wal_dir and re.search("^file://|/", hbase_wal_dir): #If wal dir
> is on local file system, create it.
> NameError: name 're' is not defined
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
> line 72, in
> AmsMonitor().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
> line 28, in install
> import params
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/params.py",
> line 376, in
> if hbase_wal_dir and re.search("^file://|/", hbase_wal_dir): #If wal dir
> is on local file system, create it.
> NameError: name 're' is not defined
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23429) Not able to install METRICS_MONITOR
[
https://issues.apache.org/jira/browse/AMBARI-23429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Janardhan updated AMBARI-23429:
Description:
ambari version - 2.7.0.0-246
metrics monitor installation failed due to below error
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
line 72, in
AmsMonitor().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 353, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
line 28, in install
import params
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/params.py",
line 376, in
if hbase_wal_dir and re.search("^file://|/", hbase_wal_dir): #If wal dir is
on local file system, create it.
NameError: name 're' is not defined
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
line 72, in
AmsMonitor().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 353, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
line 28, in install
import params
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/params.py",
line 376, in
if hbase_wal_dir and re.search("^file://|/", hbase_wal_dir): #If wal dir is
on local file system, create it.
NameError: name 're' is not defined
{code}
was:
ambari version - 2.7.0.0-246
metrics monitor installation failed due to below error [^blueprint.json]
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
line 72, in
AmsMonitor().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 353, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
line 28, in install
import params
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/params.py",
line 376, in
if hbase_wal_dir and re.search("^file://|/", hbase_wal_dir): #If wal dir is
on local file system, create it.
NameError: name 're' is not defined
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
line 72, in
AmsMonitor().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 353, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
line 28, in install
import params
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/params.py",
line 376, in
if hbase_wal_dir and re.search("^file://|/", hbase_wal_dir): #If wal dir is
on local file system, create it.
NameError: name 're' is not defined
{code}
> Not able to install METRICS_MONITOR
> ---
>
> Key: AMBARI-23429
> URL: https://issues.apache.org/jira/browse/AMBARI-23429
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.7.0
>Reporter: Srikanth Janardhan
>Assignee: Srikanth Janardhan
>Priority: Blocker
> Fix For: 2.7.0
>
>
> ambari version - 2.7.0.0-246
> metrics monitor installation failed due to below error
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
> line 72, in
> AmsMonitor().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
> line 28, in install
> import params
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/params.py",
> line 376, in
> if hbase_wal_dir and re.search("^file://|/", hbase_wal_dir): #If wal dir
> is on local file system, create it.
> NameError: name 're' is not defined
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
> line 72, in
> AmsMonitor().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
[jira] [Created] (AMBARI-23429) Not able to install METRICS_MONITOR
Srikanth Janardhan created AMBARI-23429:
---
Summary: Not able to install METRICS_MONITOR
Key: AMBARI-23429
URL: https://issues.apache.org/jira/browse/AMBARI-23429
Project: Ambari
Issue Type: Bug
Components: ambari-agent
Affects Versions: 2.7.0
Reporter: Srikanth Janardhan
Assignee: Srikanth Janardhan
Fix For: 2.7.0
ambari version - 2.7.0.0-246
metrics monitor installation failed due to below error [^blueprint.json]
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
line 72, in
AmsMonitor().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 353, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
line 28, in install
import params
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/params.py",
line 376, in
if hbase_wal_dir and re.search("^file://|/", hbase_wal_dir): #If wal dir is
on local file system, create it.
NameError: name 're' is not defined
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
line 72, in
AmsMonitor().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 353, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
line 28, in install
import params
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/params.py",
line 376, in
if hbase_wal_dir and re.search("^file://|/", hbase_wal_dir): #If wal dir is
on local file system, create it.
NameError: name 're' is not defined
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
