[jira] [Created] (AMBARI-24622) Allow skipping package operations for LZO on sysprepped hosts
Doroszlai, Attila created AMBARI-24622: -- Summary: Allow skipping package operations for LZO on sysprepped hosts Key: AMBARI-24622 URL: https://issues.apache.org/jira/browse/AMBARI-24622 Project: Ambari Issue Type: Improvement Components: ambari-server Reporter: Doroszlai, Attila Assignee: Doroszlai, Attila Fix For: 2.7.2 LZO packages may be pre-installed in sysprepped environments, but Ambari still manages the repo and checks for existence of the packages, which takes time. The goal of this change is to allow users who pre-install packages to skip package manager operations for LZO packages, too. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-21503) Add JanusGraph Service
[ https://issues.apache.org/jira/browse/AMBARI-21503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16611621#comment-16611621 ] Chris Hupman commented on AMBARI-21503: --- I started working on adding JanusGraph as a service earlier in the year. The repo can be found [[here|https://github.com/chupman/janusgraph-ambari-service]|https://github.com/chupman/janusgraph-ambari-service]. I plan to start working on the plugin again heavily in October. I'm currently working on adding it as a repo under JanusGraph, but would be more than happy to help with an officially supported service. > Add JanusGraph Service > -- > > Key: AMBARI-21503 > URL: https://issues.apache.org/jira/browse/AMBARI-21503 > Project: Ambari > Issue Type: New Feature >Reporter: Christopher Jackson >Priority: Major > > Would be nice to have JanusGraph as a common-service in Ambari. > Information for JanusGraph can be found at: http://janusgraph.org/ > Required Services: HBASE, SOLR (create SOLR service as well, or leverage > AMBARI_INFRA?) > JanusGraph is a fork from Titan, IOP (IBM Open Platform) supported Titan > 1.0.0 as a service in the BigInsights 4.2.5.0 stack. This work can most > likely be used as a starting point for creating a janus service. Similarly > BigInsights 4.2.5.0 had a standalone SOLR (6.3.0) service. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24587) HDI Livy2 fails to restart
[
https://issues.apache.org/jira/browse/AMBARI-24587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Wagle updated AMBARI-24587:
-
Description:
Livy2 restart fails from Ambari due to Ambari could not fetch some Hadoop
configs?
StdErr:
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/livy2_server.py",
line 148, in
LivyServer().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 351, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/livy2_server.py",
line 62, in start
self.configure(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/livy2_server.py",
line 52, in configure
setup_livy(env, 'server', upgrade_type=upgrade_type, action = 'config')
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/setup_livy2.py",
line 53, in setup_livy
params.HdfsResource(None, action="execute")
File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line
166, in __init__
self.env.run()
File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
line 124, in run_action
provider_action()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
line 681, in action_execute
self.get_hdfs_resource_executor().action_execute(self)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
line 164, in action_execute
logoutput=logoutput,
File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line
166, in __init__
self.env.run()
File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
line 124, in run_action
provider_action()
File
"/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py", line
263, in action_run
returns=self.resource.returns)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
72, in inner
result = function(command, **kwargs)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
102, in checked_call
tries=tries, try_sleep=try_sleep,
timeout_kill_strategy=timeout_kill_strategy, returns=returns)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
150, in _call_wrapper
result = _call(command, **kwargs_copy)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
314, in _call
raise ExecutionFailed(err_msg, code, out, err)
resource_management.core.exceptions.ExecutionFailed: Execution of 'hadoop
--config /usr/hdp/3.0.1.0-175/hadoop/conf jar
/var/lib/ambari-agent/lib/fast-hdfs-resource.jar
/var/lib/ambari-agent/tmp/hdfs_resources_1535895647.58.json' returned 1.
Initializing filesystem uri: hdfs://mycluster
Creating: Resource [source=null,
target=wasb://spark2l-at30wu-livy2-121...@humbtesting5wua2.blob.core.windows.net/user/livy/recovery-69e01f25-3b7b-4af4-a787-37664ab45f0c,
type=directory, action=create, owner=livy, group=null, mode=700,
recursiveChown=false, recursiveChmod=false, changePermissionforParents=false,
manageIfExists=true] in hdfs://mycluster
Exception occurred, Reason: Wrong FS:
wasb://spark2l-at30wu-livy2-121...@humbtesting5wua2.blob.core.windows.net/user/livy/recovery-69e01f25-3b7b-4af4-a787-37664ab45f0c,
expected: hdfs://mycluster
java.lang.IllegalArgumentException: Wrong FS:
wasb://spark2l-at30wu-livy2-121...@humbtesting5wua2.blob.core.windows.net/user/livy/recovery-69e01f25-3b7b-4af4-a787-37664ab45f0c,
expected: hdfs://mycluster
at org.apache.hadoop.fs.FileSystem.checkPath(FileSystem.java:781)
at
org.apache.hadoop.hdfs.DistributedFileSystem.getPathName(DistributedFileSystem.java:240)
at
org.apache.hadoop.hdfs.DistributedFileSystem$29.doCall(DistributedFileSystem.java:1583)
at
org.apache.hadoop.hdfs.DistributedFileSystem$29.doCall(DistributedFileSystem.java:1580)
at
org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
at
org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:1595)
at org.apache.hadoop.fs.FileSystem.isFile(FileSystem.java:1768)
at
org.apache.ambari.fast_hdfs_resource.Resource.checkResourceParameters(Resource.java:193)
at
[jira] [Updated] (AMBARI-24587) HDI Livy2 fails to restart
[
https://issues.apache.org/jira/browse/AMBARI-24587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Wagle updated AMBARI-24587:
-
Description:
Livy2 restart fails from Ambari due to Ambari could not fetch some Hadoop
configs?
StdErr:
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/livy2_server.py",
line 148, in
LivyServer().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 351, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/livy2_server.py",
line 62, in start
self.configure(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/livy2_server.py",
line 52, in configure
setup_livy(env, 'server', upgrade_type=upgrade_type, action = 'config')
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/setup_livy2.py",
line 53, in setup_livy
params.HdfsResource(None, action="execute")
File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line
166, in __init__
self.env.run()
File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
line 124, in run_action
provider_action()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
line 681, in action_execute
self.get_hdfs_resource_executor().action_execute(self)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
line 164, in action_execute
logoutput=logoutput,
File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line
166, in __init__
self.env.run()
File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
line 124, in run_action
provider_action()
File
"/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py", line
263, in action_run
returns=self.resource.returns)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
72, in inner
result = function(command, **kwargs)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
102, in checked_call
tries=tries, try_sleep=try_sleep,
timeout_kill_strategy=timeout_kill_strategy, returns=returns)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
150, in _call_wrapper
result = _call(command, **kwargs_copy)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
314, in _call
raise ExecutionFailed(err_msg, code, out, err)
resource_management.core.exceptions.ExecutionFailed: Execution of 'hadoop
--config /usr/hdp/3.0.1.0-175/hadoop/conf jar
/var/lib/ambari-agent/lib/fast-hdfs-resource.jar
/var/lib/ambari-agent/tmp/hdfs_resources_1535895647.58.json' returned 1.
Initializing filesystem uri: hdfs://mycluster
Creating: Resource [source=null,
target=wasb://spark2l-at30wu-livy2-121...@humbtesting5wua2.blob.core.windows.net/user/livy/recovery-69e01f25-3b7b-4af4-a787-37664ab45f0c,
type=directory, action=create, owner=livy, group=null, mode=700,
recursiveChown=false, recursiveChmod=false, changePermissionforParents=false,
manageIfExists=true] in hdfs://mycluster
Exception occurred, Reason: Wrong FS:
wasb://spark2l-at30wu-livy2-121...@humbtesting5wua2.blob.core.windows.net/user/livy/recovery-69e01f25-3b7b-4af4-a787-37664ab45f0c,
expected: hdfs://mycluster
java.lang.IllegalArgumentException: Wrong FS:
wasb://spark2l-at30wu-livy2-121...@humbtesting5wua2.blob.core.windows.net/user/livy/recovery-69e01f25-3b7b-4af4-a787-37664ab45f0c,
expected: hdfs://mycluster
at org.apache.hadoop.fs.FileSystem.checkPath(FileSystem.java:781)
at
org.apache.hadoop.hdfs.DistributedFileSystem.getPathName(DistributedFileSystem.java:240)
at
org.apache.hadoop.hdfs.DistributedFileSystem$29.doCall(DistributedFileSystem.java:1583)
at
org.apache.hadoop.hdfs.DistributedFileSystem$29.doCall(DistributedFileSystem.java:1580)
at
org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
at
org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:1595)
at org.apache.hadoop.fs.FileSystem.isFile(FileSystem.java:1768)
at
org.apache.ambari.fast_hdfs_resource.Resource.checkResourceParameters(Resource.java:193)
at
[jira] [Updated] (AMBARI-24621) Badge with count of empty or invalid properties are missed ar the services panel during cluster installation
[ https://issues.apache.org/jira/browse/AMBARI-24621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24621: Labels: pull-request-available (was: ) > Badge with count of empty or invalid properties are missed ar the services > panel during cluster installation > > > Key: AMBARI-24621 > URL: https://issues.apache.org/jira/browse/AMBARI-24621 > 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: 3.0.0 > > > STR: > 1)Initiate cluster installation > 2)Navigate to customize all services page > 3)Navigate to service tab > 4)Clear some service required property > Expected > Count of errors near service name > Actual > Count of errors near service name is absent -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24621) Badge with count of empty or invalid properties are missed ar the services panel during cluster installation
Aleksandr Kovalenko created AMBARI-24621: Summary: Badge with count of empty or invalid properties are missed ar the services panel during cluster installation Key: AMBARI-24621 URL: https://issues.apache.org/jira/browse/AMBARI-24621 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 3.0.0 STR: 1)Initiate cluster installation 2)Navigate to customize all services page 3)Navigate to service tab 4)Clear some service required property Expected Count of errors near service name Actual Count of errors near service name is absent -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24586) User get stuck between steps if API returns empty version_definitions array
[ https://issues.apache.org/jira/browse/AMBARI-24586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24586. -- Resolution: Duplicate > User get stuck between steps if API returns empty version_definitions array > --- > > Key: AMBARI-24586 > URL: https://issues.apache.org/jira/browse/AMBARI-24586 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > In Install Wizard when user goes to step1 API request to load version > definitions is sent. Sometimes this request returns empty array and UI is not > showing any error and just shows empty page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24619) Horizontal scroll bar on assign slaves and clients page is not convenient for deploy with numerous hosts
[ https://issues.apache.org/jira/browse/AMBARI-24619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16610801#comment-16610801 ] Hudson commented on AMBARI-24619: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9936 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9936/]) AMBARI-24619 Horizontal scroll bar on assign slaves and clients page is (ababiichuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=6645b45e9bb680e41255671d3e742fe097018de6]) * (edit) ambari-web/app/templates/wizard/step6.hbs * (edit) ambari-web/test/views/wizard/step6_view_test.js * (edit) ambari-web/app/styles/common.less * (edit) ambari-web/app/styles/wizard.less * (edit) ambari-web/app/views/wizard/step6_view.js > Horizontal scroll bar on assign slaves and clients page is not convenient for > deploy with numerous hosts > > > Key: AMBARI-24619 > URL: https://issues.apache.org/jira/browse/AMBARI-24619 > 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: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > It is not convenient to configure slaves and clients for deploy with numerous > hosts because horizontal scroll bar is placed in the bottom of hosts list. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24619) Horizontal scroll bar on assign slaves and clients page is not convenient for deploy with numerous hosts
[ https://issues.apache.org/jira/browse/AMBARI-24619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-24619: -- Resolution: Fixed Status: Resolved (was: Patch Available) Merged to trunk > Horizontal scroll bar on assign slaves and clients page is not convenient for > deploy with numerous hosts > > > Key: AMBARI-24619 > URL: https://issues.apache.org/jira/browse/AMBARI-24619 > 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: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > It is not convenient to configure slaves and clients for deploy with numerous > hosts because horizontal scroll bar is placed in the bottom of hosts list. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24620) Duplicate view of configurations in Add Service wizard
[ https://issues.apache.org/jira/browse/AMBARI-24620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-24620: -- Attachment: duplicate-view.png > Duplicate view of configurations in Add Service wizard > -- > > Key: AMBARI-24620 > URL: https://issues.apache.org/jira/browse/AMBARI-24620 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.7.2 > > Attachments: duplicate-view.png > > > See screenshot -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24620) Duplicate view of configurations in Add Service wizard
Andrii Tkach created AMBARI-24620: - Summary: Duplicate view of configurations in Add Service wizard Key: AMBARI-24620 URL: https://issues.apache.org/jira/browse/AMBARI-24620 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.2 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.7.2 Attachments: duplicate-view.png See screenshot -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24619) Horizontal scroll bar on assign slaves and clients page is not convenient for deploy with numerous hosts
[ https://issues.apache.org/jira/browse/AMBARI-24619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-24619: -- Status: Patch Available (was: Open) > Horizontal scroll bar on assign slaves and clients page is not convenient for > deploy with numerous hosts > > > Key: AMBARI-24619 > URL: https://issues.apache.org/jira/browse/AMBARI-24619 > 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: 3.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > It is not convenient to configure slaves and clients for deploy with numerous > hosts because horizontal scroll bar is placed in the bottom of hosts list. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24619) Horizontal scroll bar on assign slaves and clients page is not convenient for deploy with numerous hosts
[ https://issues.apache.org/jira/browse/AMBARI-24619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24619: Labels: pull-request-available (was: ) > Horizontal scroll bar on assign slaves and clients page is not convenient for > deploy with numerous hosts > > > Key: AMBARI-24619 > URL: https://issues.apache.org/jira/browse/AMBARI-24619 > 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: 3.0.0 > > > It is not convenient to configure slaves and clients for deploy with numerous > hosts because horizontal scroll bar is placed in the bottom of hosts list. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24604) Stack advisor error popup with "500 status code" thrown during customize service page of install wizard
[ https://issues.apache.org/jira/browse/AMBARI-24604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen resolved AMBARI-24604. - Resolution: Fixed > Stack advisor error popup with "500 status code" thrown during customize > service page of install wizard > --- > > Key: AMBARI-24604 > URL: https://issues.apache.org/jira/browse/AMBARI-24604 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.2 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > ams-hbase hbase.rootdir property being set to "file://" leads to 500 server > error -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24619) Horizontal scroll bar on assign slaves and clients page is not convenient for deploy with numerous hosts
Andrii Babiichuk created AMBARI-24619: - Summary: Horizontal scroll bar on assign slaves and clients page is not convenient for deploy with numerous hosts Key: AMBARI-24619 URL: https://issues.apache.org/jira/browse/AMBARI-24619 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Fix For: 3.0.0 It is not convenient to configure slaves and clients for deploy with numerous hosts because horizontal scroll bar is placed in the bottom of hosts list. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24516) Default value for LDAP type
[ https://issues.apache.org/jira/browse/AMBARI-24516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16610527#comment-16610527 ] Hudson commented on AMBARI-24516: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #237 (See [https://builds.apache.org/job/Ambari-branch-2.7/237/]) AMBARI-24516 - Default value for LDAP type (#2276) (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=ca9851ea960d3f9b015c88017b3af9832b804091]) * (edit) ambari-server/src/main/python/ambari_server/setupSecurity.py * (edit) ambari-server/src/test/python/TestAmbariServer.py * (edit) ambari-server/src/main/python/ambari-server.py > Default value for LDAP type > --- > > Key: AMBARI-24516 > URL: https://issues.apache.org/jira/browse/AMBARI-24516 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Time Spent: 1.5h > Remaining Estimate: 0h > > 1. Set default value for ldap type 'Generic' > 2. command line option for disable asking ldap-type. Use Generic defaults for > if set and properties are not exists and not given. > 3. Ask for ldap type only if any of the properties which default value is > depending from ldap type is missing. > 4. Ask for the user credentials and queries Ambari for the existing values > first. Than offer these values as defaults. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24569) Cannot deploy Hive Metastore with Kerberos without HDFS
[
https://issues.apache.org/jira/browse/AMBARI-24569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila resolved AMBARI-24569.
Resolution: Invalid
> Cannot deploy Hive Metastore with Kerberos without HDFS
> ---
>
> Key: AMBARI-24569
> URL: https://issues.apache.org/jira/browse/AMBARI-24569
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Priority: Major
> Fix For: 2.7.2
>
>
> In order to enable Kerberos for Hive MetaStore we need a property in
> {{core-site}}, which is ignored by Ambari if HDFS is not present. Hive
> Metastore start fails due to empty {{core-site}} with:
> {noformat}
> KeeperException$InvalidACLException: KeeperErrorCode = InvalidACL for
> /hive/cluster/delegationMETASTORE/keys
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (AMBARI-24569) Cannot deploy Hive Metastore with Kerberos without HDFS
[
https://issues.apache.org/jira/browse/AMBARI-24569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila reassigned AMBARI-24569:
--
Assignee: (was: Doroszlai, Attila)
> Cannot deploy Hive Metastore with Kerberos without HDFS
> ---
>
> Key: AMBARI-24569
> URL: https://issues.apache.org/jira/browse/AMBARI-24569
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Priority: Major
> Fix For: 2.7.2
>
>
> In order to enable Kerberos for Hive MetaStore we need a property in
> {{core-site}}, which is ignored by Ambari if HDFS is not present. Hive
> Metastore start fails due to empty {{core-site}} with:
> {noformat}
> KeeperException$InvalidACLException: KeeperErrorCode = InvalidACL for
> /hive/cluster/delegationMETASTORE/keys
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-23018) Add more Solr alerts using Solr (< 6.4 version) metrics API
[ https://issues.apache.org/jira/browse/AMBARI-23018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krisztian Kasa resolved AMBARI-23018. - Resolution: Won't Fix > Add more Solr alerts using Solr (< 6.4 version) metrics API > --- > > Key: AMBARI-23018 > URL: https://issues.apache.org/jira/browse/AMBARI-23018 > Project: Ambari > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24618) Ambari generates wrong zookeeper connection string for KMS HA configuration
[ https://issues.apache.org/jira/browse/AMBARI-24618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24618: Labels: pull-request-available (was: ) > Ambari generates wrong zookeeper connection string for KMS HA configuration > --- > > Key: AMBARI-24618 > URL: https://issues.apache.org/jira/browse/AMBARI-24618 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > > * Zookeeper nodes are: node-1, node-2, node-3 > * KMS HA nodes: node-7, node-8. > Ambari generated value for the above property has node-7 and node-8 – see > picture attached – but should have node-1, node-2 and node-3. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-24618) Ambari generates wrong zookeeper connection string for KMS HA configuration
[ https://issues.apache.org/jira/browse/AMBARI-24618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-24618: Assignee: Antonenko Alexander > Ambari generates wrong zookeeper connection string for KMS HA configuration > --- > > Key: AMBARI-24618 > URL: https://issues.apache.org/jira/browse/AMBARI-24618 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > > * Zookeeper nodes are: node-1, node-2, node-3 > * KMS HA nodes: node-7, node-8. > Ambari generated value for the above property has node-7 and node-8 – see > picture attached – but should have node-1, node-2 and node-3. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24618) Ambari generates wrong zookeeper connection string for KMS HA configuration
Antonenko Alexander created AMBARI-24618: Summary: Ambari generates wrong zookeeper connection string for KMS HA configuration Key: AMBARI-24618 URL: https://issues.apache.org/jira/browse/AMBARI-24618 Project: Ambari Issue Type: Task Components: ambari-web Reporter: Antonenko Alexander * Zookeeper nodes are: node-1, node-2, node-3 * KMS HA nodes: node-7, node-8. Ambari generated value for the above property has node-7 and node-8 – see picture attached – but should have node-1, node-2 and node-3. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
