[jira] [Commented] (AMBARI-24563) global name 'VERIFY_DEPENDENCY_CMD' is not defined'
[
https://issues.apache.org/jira/browse/AMBARI-24563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16661155#comment-16661155
]
Hudson commented on AMBARI-24563:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #379 (See
[https://builds.apache.org/job/Ambari-branch-2.7/379/])
AMBARI-24563. global name 'VERIFY_DEPENDENCY_CMD' is not defined' (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=09a1ef80047c99b2c59926530a0d78237c552061])
* (edit)
ambari-common/src/main/python/ambari_commons/repo_manager/apt_manager.py
> global name 'VERIFY_DEPENDENCY_CMD' is not defined'
> ---
>
> Key: AMBARI-24563
> URL: https://issues.apache.org/jira/browse/AMBARI-24563
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.7.1
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> STR:-
> 1. deploy the cluster with HDP-3.0.1.0-164 + ambari_version : 2.7.1.0-147
> 2. added a patch targetVDF-29-08-2018-00-53-55.xml
> 3. install version
> {code}
> 2018-08-29 16:47:27,225 - Package Manager failed to install packages: Failed
> to execute command '/usr/bin/apt-get -o Dpkg::Options::=--force-confdef
> --allow-unauthenticated --assume-yes install -o
> Dir::Etc::SourceList=/dev/null -o Dir::Etc::SourceParts= hdp-select', exited
> with code '100', message: 'E: dpkg was interrupted, you must manually run
> 'dpkg --configure -a' to correct the problem.
> '
> 2018-08-29 16:47:27,250 - Could not install packages. Error: global name
> 'VERIFY_DEPENDENCY_CMD' is not defined
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 136, in actionexecute
> ret_code = self.install_packages(package_list)
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 447, in install_packages
> if not self.repo_mgr.verify_dependencies():
> File
> "/usr/lib/ambari-agent/lib/ambari_commons/repo_manager/apt_manager.py", line
> 218, in verify_dependencies
> err_msg = Logger.filter_text("Failed to verify package dependencies.
> Execution of '%s' returned %s. %s" % (VERIFY_DEPENDENCY_CMD, code, out))
> NameError: global name 'VERIFY_DEPENDENCY_CMD' is not defined
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 136, in actionexecute
> ret_code = self.install_packages(package_list)
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 447, in install_packages
> if not self.repo_mgr.verify_dependencies():
> File
> "/usr/lib/ambari-agent/lib/ambari_commons/repo_manager/apt_manager.py", line
> 218, in verify_dependencies
> err_msg = Logger.filter_text("Failed to verify package dependencies.
> Execution of '%s' returned %s. %s" % (VERIFY_DEPENDENCY_CMD, code, out))
> NameError: global name 'VERIFY_DEPENDENCY_CMD' is not defined
> The above exception was the cause of the following exception:
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 486, in
> InstallPackages().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/custom_actions/scripts/install_packages.py",
> line 149, in actionexecute
> raise Fail("Failed to distribute repositories/install packages")
> resource_management.core.exceptions.Fail: Failed to distribute
> repositories/install packages
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24812) Implement New Upgrade Check Which Warns About Missing Plugin Checks
[
https://issues.apache.org/jira/browse/AMBARI-24812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16661125#comment-16661125
]
Hudson commented on AMBARI-24812:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10244 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/10244/])
[AMBARI-24812] - Implement New Upgrade Check Which Warns About Missing (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=cd397373e6d7a0d976ee50e61466cfe184cfb6a7])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/checks/UpgradeCheckRegistry.java
* (add)
ambari-server/src/test/java/org/apache/ambari/server/checks/PluginChecksLoadedCheckTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/PreUpgradeCheckResourceProviderTest.java
* (add)
ambari-server/src/main/java/org/apache/ambari/server/checks/PluginChecksLoadedCheck.java
> Implement New Upgrade Check Which Warns About Missing Plugin Checks
> ---
>
> Key: AMBARI-24812
> URL: https://issues.apache.org/jira/browse/AMBARI-24812
> Project: Ambari
> Issue Type: Task
>Affects Versions: 2.8.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> AMBARI-24737 removed stack upgrade checks from being shipped with Ambari and
> instead expects the stacks to deliver their own implementations. In the event
> that an upgrade check is defined in an upgrade pack but cannot be found or
> instantiated, there should be a warning displayed before allowing the upgrade
> to proceed.
> For example:
> {code}
> {
> "href" :
> "http://localhost:8080/api/v1/clusters/c1/rolling_upgrades_check/PLUGIN_CHECK_LOAD_FAILURE;,
> "UpgradeChecks" : {
> "check" : "Plugin Upgrade Checks",
> "check_type" : "CLUSTER",
> "cluster_name" : "c1",
> "failed_detail" : [
> {
> "package_name" : "org.apache.ambari.server.checks",
> "class_name" : "ServicesYarnWorkPreservingCheck"
> },
> {
> "package_name" : "org.apache.ambari.server.checks",
> "class_name" : "DruidHighAvailabilityCheck"
> },
> {
> "package_name" : "org.apache.ambari.server.checks",
> "class_name" : "ServicesNamenodeHighAvailabilityCheck"
> },
> {
> "package_name" : "org.apache.ambari.server.checks",
> "class_name" : "MapReduce2JobHistoryStatePreservingCheck"
> },
> {
> "package_name" : "org.apache.ambari.server.checks",
> "class_name" : "YarnRMHighAvailabilityCheck"
> },
> {
> "package_name" : "org.apache.ambari.server.checks",
> "class_name" : "ServicesMapReduceDistributedCacheCheck"
> },
> {
> "package_name" : "org.apache.ambari.server.checks",
> "class_name" : "ServicesTezDistributedCacheCheck"
> },
> {
> "package_name" : "org.apache.ambari.server.checks",
> "class_name" : "YarnTimelineServerStatePreservingCheck"
> },
> {
> "package_name" : "org.apache.ambari.server.checks",
> "class_name" : "HiveMultipleMetastoreCheck"
> },
> {
> "package_name" : "org.apache.ambari.server.checks",
> "class_name" : "SecondaryNamenodeDeletedCheck"
> }
> ],
> "failed_on" : [
> "ServicesMapReduceDistributedCacheCheck",
> "ServicesTezDistributedCacheCheck",
> "SecondaryNamenodeDeletedCheck",
> "YarnTimelineServerStatePreservingCheck",
> "YarnRMHighAvailabilityCheck",
> "DruidHighAvailabilityCheck",
> "ServicesNamenodeHighAvailabilityCheck",
> "HiveMultipleMetastoreCheck",
> "MapReduce2JobHistoryStatePreservingCheck",
> "ServicesYarnWorkPreservingCheck"
> ],
> "id" : "PLUGIN_CHECK_LOAD_FAILURE",
> "reason" : "The following upgrade checks could not be loaded and were
> not run. Although this will not stop your upgrade, it is advised that these
> checks be corrected to ensure a successful upgrade.",
> "repository_version_id" : 2,
> "status" : "FAIL",
> "upgrade_type" : "NON_ROLLING"
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24563) global name 'VERIFY_DEPENDENCY_CMD' is not defined'
[
https://issues.apache.org/jira/browse/AMBARI-24563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Magyar resolved AMBARI-24563.
Resolution: Fixed
> global name 'VERIFY_DEPENDENCY_CMD' is not defined'
> ---
>
> Key: AMBARI-24563
> URL: https://issues.apache.org/jira/browse/AMBARI-24563
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.7.1
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> STR:-
> 1. deploy the cluster with HDP-3.0.1.0-164 + ambari_version : 2.7.1.0-147
> 2. added a patch targetVDF-29-08-2018-00-53-55.xml
> 3. install version
> {code}
> 2018-08-29 16:47:27,225 - Package Manager failed to install packages: Failed
> to execute command '/usr/bin/apt-get -o Dpkg::Options::=--force-confdef
> --allow-unauthenticated --assume-yes install -o
> Dir::Etc::SourceList=/dev/null -o Dir::Etc::SourceParts= hdp-select', exited
> with code '100', message: 'E: dpkg was interrupted, you must manually run
> 'dpkg --configure -a' to correct the problem.
> '
> 2018-08-29 16:47:27,250 - Could not install packages. Error: global name
> 'VERIFY_DEPENDENCY_CMD' is not defined
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 136, in actionexecute
> ret_code = self.install_packages(package_list)
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 447, in install_packages
> if not self.repo_mgr.verify_dependencies():
> File
> "/usr/lib/ambari-agent/lib/ambari_commons/repo_manager/apt_manager.py", line
> 218, in verify_dependencies
> err_msg = Logger.filter_text("Failed to verify package dependencies.
> Execution of '%s' returned %s. %s" % (VERIFY_DEPENDENCY_CMD, code, out))
> NameError: global name 'VERIFY_DEPENDENCY_CMD' is not defined
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 136, in actionexecute
> ret_code = self.install_packages(package_list)
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 447, in install_packages
> if not self.repo_mgr.verify_dependencies():
> File
> "/usr/lib/ambari-agent/lib/ambari_commons/repo_manager/apt_manager.py", line
> 218, in verify_dependencies
> err_msg = Logger.filter_text("Failed to verify package dependencies.
> Execution of '%s' returned %s. %s" % (VERIFY_DEPENDENCY_CMD, code, out))
> NameError: global name 'VERIFY_DEPENDENCY_CMD' is not defined
> The above exception was the cause of the following exception:
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 486, in
> InstallPackages().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/custom_actions/scripts/install_packages.py",
> line 149, in actionexecute
> raise Fail("Failed to distribute repositories/install packages")
> resource_management.core.exceptions.Fail: Failed to distribute
> repositories/install packages
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24812) Implement New Upgrade Check Which Warns About Missing Plugin Checks
[
https://issues.apache.org/jira/browse/AMBARI-24812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley resolved AMBARI-24812.
--
Resolution: Fixed
> Implement New Upgrade Check Which Warns About Missing Plugin Checks
> ---
>
> Key: AMBARI-24812
> URL: https://issues.apache.org/jira/browse/AMBARI-24812
> Project: Ambari
> Issue Type: Task
>Affects Versions: 2.8.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> AMBARI-24737 removed stack upgrade checks from being shipped with Ambari and
> instead expects the stacks to deliver their own implementations. In the event
> that an upgrade check is defined in an upgrade pack but cannot be found or
> instantiated, there should be a warning displayed before allowing the upgrade
> to proceed.
> For example:
> {code}
> {
> "href" :
> "http://localhost:8080/api/v1/clusters/c1/rolling_upgrades_check/PLUGIN_CHECK_LOAD_FAILURE;,
> "UpgradeChecks" : {
> "check" : "Plugin Upgrade Checks",
> "check_type" : "CLUSTER",
> "cluster_name" : "c1",
> "failed_detail" : [
> {
> "package_name" : "org.apache.ambari.server.checks",
> "class_name" : "ServicesYarnWorkPreservingCheck"
> },
> {
> "package_name" : "org.apache.ambari.server.checks",
> "class_name" : "DruidHighAvailabilityCheck"
> },
> {
> "package_name" : "org.apache.ambari.server.checks",
> "class_name" : "ServicesNamenodeHighAvailabilityCheck"
> },
> {
> "package_name" : "org.apache.ambari.server.checks",
> "class_name" : "MapReduce2JobHistoryStatePreservingCheck"
> },
> {
> "package_name" : "org.apache.ambari.server.checks",
> "class_name" : "YarnRMHighAvailabilityCheck"
> },
> {
> "package_name" : "org.apache.ambari.server.checks",
> "class_name" : "ServicesMapReduceDistributedCacheCheck"
> },
> {
> "package_name" : "org.apache.ambari.server.checks",
> "class_name" : "ServicesTezDistributedCacheCheck"
> },
> {
> "package_name" : "org.apache.ambari.server.checks",
> "class_name" : "YarnTimelineServerStatePreservingCheck"
> },
> {
> "package_name" : "org.apache.ambari.server.checks",
> "class_name" : "HiveMultipleMetastoreCheck"
> },
> {
> "package_name" : "org.apache.ambari.server.checks",
> "class_name" : "SecondaryNamenodeDeletedCheck"
> }
> ],
> "failed_on" : [
> "ServicesMapReduceDistributedCacheCheck",
> "ServicesTezDistributedCacheCheck",
> "SecondaryNamenodeDeletedCheck",
> "YarnTimelineServerStatePreservingCheck",
> "YarnRMHighAvailabilityCheck",
> "DruidHighAvailabilityCheck",
> "ServicesNamenodeHighAvailabilityCheck",
> "HiveMultipleMetastoreCheck",
> "MapReduce2JobHistoryStatePreservingCheck",
> "ServicesYarnWorkPreservingCheck"
> ],
> "id" : "PLUGIN_CHECK_LOAD_FAILURE",
> "reason" : "The following upgrade checks could not be loaded and were
> not run. Although this will not stop your upgrade, it is advised that these
> checks be corrected to ensure a successful upgrade.",
> "repository_version_id" : 2,
> "status" : "FAIL",
> "upgrade_type" : "NON_ROLLING"
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24819) do not allow creation of new hive actions in WFM
[ https://issues.apache.org/jira/browse/AMBARI-24819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24819: Labels: pull-request-available (was: ) > do not allow creation of new hive actions in WFM > - > > Key: AMBARI-24819 > URL: https://issues.apache.org/jira/browse/AMBARI-24819 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: venkat >Assignee: venkat >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-24818) Knox topology files installed via Ambari are world readable
[ https://issues.apache.org/jira/browse/AMBARI-24818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24818: Labels: pull-request-available (was: ) > Knox topology files installed via Ambari are world readable > --- > > Key: AMBARI-24818 > URL: https://issues.apache.org/jira/browse/AMBARI-24818 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Sandeep More >Assignee: Sandeep More >Priority: Major > Labels: pull-request-available > Attachments: ambari.patch > > > The Knox topologies should only be accessible to the knox user. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24296) [Yarn Queue Manager] Yarn Queue manager is allowing to Create a Child Queue for queue-mappings enabled Queue and Save it
[
https://issues.apache.org/jira/browse/AMBARI-24296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16661013#comment-16661013
]
Hudson commented on AMBARI-24296:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #378 (See
[https://builds.apache.org/job/Ambari-branch-2.7/378/])
[AMBARI-24296] Yarn Queue manager is allowing to Create a Child Queue
(jonathanhurley:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=56c8ccf77506ddc1268ee1925f3ca0f73bdfb9da])
* (edit)
contrib/views/capacity-scheduler/src/main/resources/ui/app/controllers/queues.js
> [Yarn Queue Manager] Yarn Queue manager is allowing to Create a Child Queue
> for queue-mappings enabled Queue and Save it
>
>
> Key: AMBARI-24296
> URL: https://issues.apache.org/jira/browse/AMBARI-24296
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.7.0
>Reporter: Akhil S Naik
>Assignee: Akhil S Naik
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Yarn Queue manager is allowing to Create a Child Queue for queue-mappings
> enabled Queue and Save the changes
> But the Operating is Failing as Yarn is having a check that Queue-mappings
> should only be allowed for Leaf queue
> Code which validates whether queue-mappings are enabled only for leaf-queue (
> YARN CODE)
> {code:java}
> private static QueueMapping validateAndGetQueueMapping(
> CapacitySchedulerQueueManager queueManager, CSQueue queue,
> QueueMapping mapping, QueuePath queuePath) throws IOException {
> if (!(queue instanceof LeafQueue)) {
> throw new IOException(
> "mapping contains invalid or non-leaf queue : " +
> mapping.getQueue());
> }
> {code}
> The buggy code in [Ambari Yarn Queue Manager which needs rework]:
> https://github.com/apache/ambari/blob/79cca1c7184f1661236971dac70d85a83fab6c11/contrib/views/capacity-scheduler/src/main/resources/ui/app/controllers/queues.js#L410
> {code:java}
> hasInvalidMapping = queues.filter(function(queue){
> return !queue.get("queues"); //get all leaf queues
> }).map(function(queue){
> return queue.get("name");
> }).indexOf(mapping[2]) == -1;
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24819) do not allow creation of new hive actions in WFM
venkat created AMBARI-24819: --- Summary: do not allow creation of new hive actions in WFM Key: AMBARI-24819 URL: https://issues.apache.org/jira/browse/AMBARI-24819 Project: Ambari Issue Type: Bug Components: ambari-views Reporter: venkat Assignee: venkat Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24563) global name 'VERIFY_DEPENDENCY_CMD' is not defined'
[
https://issues.apache.org/jira/browse/AMBARI-24563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-24563:
---
Fix Version/s: (was: 2.7.1)
2.7.3
> global name 'VERIFY_DEPENDENCY_CMD' is not defined'
> ---
>
> Key: AMBARI-24563
> URL: https://issues.apache.org/jira/browse/AMBARI-24563
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.7.1
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> STR:-
> 1. deploy the cluster with HDP-3.0.1.0-164 + ambari_version : 2.7.1.0-147
> 2. added a patch targetVDF-29-08-2018-00-53-55.xml
> 3. install version
> {code}
> 2018-08-29 16:47:27,225 - Package Manager failed to install packages: Failed
> to execute command '/usr/bin/apt-get -o Dpkg::Options::=--force-confdef
> --allow-unauthenticated --assume-yes install -o
> Dir::Etc::SourceList=/dev/null -o Dir::Etc::SourceParts= hdp-select', exited
> with code '100', message: 'E: dpkg was interrupted, you must manually run
> 'dpkg --configure -a' to correct the problem.
> '
> 2018-08-29 16:47:27,250 - Could not install packages. Error: global name
> 'VERIFY_DEPENDENCY_CMD' is not defined
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 136, in actionexecute
> ret_code = self.install_packages(package_list)
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 447, in install_packages
> if not self.repo_mgr.verify_dependencies():
> File
> "/usr/lib/ambari-agent/lib/ambari_commons/repo_manager/apt_manager.py", line
> 218, in verify_dependencies
> err_msg = Logger.filter_text("Failed to verify package dependencies.
> Execution of '%s' returned %s. %s" % (VERIFY_DEPENDENCY_CMD, code, out))
> NameError: global name 'VERIFY_DEPENDENCY_CMD' is not defined
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 136, in actionexecute
> ret_code = self.install_packages(package_list)
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 447, in install_packages
> if not self.repo_mgr.verify_dependencies():
> File
> "/usr/lib/ambari-agent/lib/ambari_commons/repo_manager/apt_manager.py", line
> 218, in verify_dependencies
> err_msg = Logger.filter_text("Failed to verify package dependencies.
> Execution of '%s' returned %s. %s" % (VERIFY_DEPENDENCY_CMD, code, out))
> NameError: global name 'VERIFY_DEPENDENCY_CMD' is not defined
> The above exception was the cause of the following exception:
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 486, in
> InstallPackages().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/custom_actions/scripts/install_packages.py",
> line 149, in actionexecute
> raise Fail("Failed to distribute repositories/install packages")
> resource_management.core.exceptions.Fail: Failed to distribute
> repositories/install packages
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (AMBARI-24563) global name 'VERIFY_DEPENDENCY_CMD' is not defined'
[
https://issues.apache.org/jira/browse/AMBARI-24563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan reopened AMBARI-24563:
This patch has not been committed into branch-2.7. Please commit this to
branch-2.7.
> global name 'VERIFY_DEPENDENCY_CMD' is not defined'
> ---
>
> Key: AMBARI-24563
> URL: https://issues.apache.org/jira/browse/AMBARI-24563
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.7.1
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> STR:-
> 1. deploy the cluster with HDP-3.0.1.0-164 + ambari_version : 2.7.1.0-147
> 2. added a patch targetVDF-29-08-2018-00-53-55.xml
> 3. install version
> {code}
> 2018-08-29 16:47:27,225 - Package Manager failed to install packages: Failed
> to execute command '/usr/bin/apt-get -o Dpkg::Options::=--force-confdef
> --allow-unauthenticated --assume-yes install -o
> Dir::Etc::SourceList=/dev/null -o Dir::Etc::SourceParts= hdp-select', exited
> with code '100', message: 'E: dpkg was interrupted, you must manually run
> 'dpkg --configure -a' to correct the problem.
> '
> 2018-08-29 16:47:27,250 - Could not install packages. Error: global name
> 'VERIFY_DEPENDENCY_CMD' is not defined
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 136, in actionexecute
> ret_code = self.install_packages(package_list)
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 447, in install_packages
> if not self.repo_mgr.verify_dependencies():
> File
> "/usr/lib/ambari-agent/lib/ambari_commons/repo_manager/apt_manager.py", line
> 218, in verify_dependencies
> err_msg = Logger.filter_text("Failed to verify package dependencies.
> Execution of '%s' returned %s. %s" % (VERIFY_DEPENDENCY_CMD, code, out))
> NameError: global name 'VERIFY_DEPENDENCY_CMD' is not defined
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 136, in actionexecute
> ret_code = self.install_packages(package_list)
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 447, in install_packages
> if not self.repo_mgr.verify_dependencies():
> File
> "/usr/lib/ambari-agent/lib/ambari_commons/repo_manager/apt_manager.py", line
> 218, in verify_dependencies
> err_msg = Logger.filter_text("Failed to verify package dependencies.
> Execution of '%s' returned %s. %s" % (VERIFY_DEPENDENCY_CMD, code, out))
> NameError: global name 'VERIFY_DEPENDENCY_CMD' is not defined
> The above exception was the cause of the following exception:
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 486, in
> InstallPackages().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/custom_actions/scripts/install_packages.py",
> line 149, in actionexecute
> raise Fail("Failed to distribute repositories/install packages")
> resource_management.core.exceptions.Fail: Failed to distribute
> repositories/install packages
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-20390) Inappropriate kafka log4j configuration results in too much kafka logs
[ https://issues.apache.org/jira/browse/AMBARI-20390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-20390: --- Resolution: Not A Problem Status: Resolved (was: Patch Available) > Inappropriate kafka log4j configuration results in too much kafka logs > --- > > Key: AMBARI-20390 > URL: https://issues.apache.org/jira/browse/AMBARI-20390 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.7.0, 2.7.1, 2.7.2 >Reporter: WangJie >Assignee: Jayush Luniya >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Attachments: AMBARI-20390.patch, screenshot-1.png > > Time Spent: 1h > Remaining Estimate: 0h > > Inappropriate kafka log4j configuration results in too much kafka logs which > are constantly increasing and never be removed. > Besides,DailyRollingFileAppender does not support property:maxBackupIndex and > maxFileSize, Only RollingFileAppender supports it. > Suggestion: > Change kafka log4j appender mode from DailyRollingFileAppender to > RollingFileAppender. > In this way, it will automatically remove the useless kafka log file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-20390) Inappropriate kafka log4j configuration results in too much kafka logs
[ https://issues.apache.org/jira/browse/AMBARI-20390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya reassigned AMBARI-20390: -- Assignee: Jayush Luniya > Inappropriate kafka log4j configuration results in too much kafka logs > --- > > Key: AMBARI-20390 > URL: https://issues.apache.org/jira/browse/AMBARI-20390 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.7.0, 2.7.1, 2.7.2 >Reporter: WangJie >Assignee: Jayush Luniya >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Attachments: AMBARI-20390.patch, screenshot-1.png > > Time Spent: 1h > Remaining Estimate: 0h > > Inappropriate kafka log4j configuration results in too much kafka logs which > are constantly increasing and never be removed. > Besides,DailyRollingFileAppender does not support property:maxBackupIndex and > maxFileSize, Only RollingFileAppender supports it. > Suggestion: > Change kafka log4j appender mode from DailyRollingFileAppender to > RollingFileAppender. > In this way, it will automatically remove the useless kafka log file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-20390) Inappropriate kafka log4j configuration results in too much kafka logs
[ https://issues.apache.org/jira/browse/AMBARI-20390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16661001#comment-16661001 ] Jayush Luniya commented on AMBARI-20390: The configs defined in the stack definitions are only the default values and can be changed by the end user when deploying the cluster. You can change the log4j properties from the UI without having to change the default. > Inappropriate kafka log4j configuration results in too much kafka logs > --- > > Key: AMBARI-20390 > URL: https://issues.apache.org/jira/browse/AMBARI-20390 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.7.0, 2.7.1, 2.7.2 >Reporter: WangJie >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Attachments: AMBARI-20390.patch, screenshot-1.png > > Time Spent: 1h > Remaining Estimate: 0h > > Inappropriate kafka log4j configuration results in too much kafka logs which > are constantly increasing and never be removed. > Besides,DailyRollingFileAppender does not support property:maxBackupIndex and > maxFileSize, Only RollingFileAppender supports it. > Suggestion: > Change kafka log4j appender mode from DailyRollingFileAppender to > RollingFileAppender. > In this way, it will automatically remove the useless kafka log file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24817) Update incorrect instructions for updating alert groups with API
[
https://issues.apache.org/jira/browse/AMBARI-24817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16660981#comment-16660981
]
Hudson commented on AMBARI-24817:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10243 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/10243/])
[AMBARI-24817] Update incorrect instructions for updating alert groups
(jonathanhurley:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=aac386e6b42cd75b3d15ed42c47c5595d80916a4])
* (edit) ambari-server/docs/api/v1/alert-dispatching.md
> Update incorrect instructions for updating alert groups with API
>
>
> Key: AMBARI-24817
> URL: https://issues.apache.org/jira/browse/AMBARI-24817
> Project: Ambari
> Issue Type: Task
>Reporter: Jonathan Hurley
>Priority: Major
> Fix For: 2.8.0
>
>
> Submitting a POST request to
> {{api/v1/clusters/CLUSTER/alert_groups/GROUP-ID}} to update an alert returns
> a method not allowed error:
> {code}
> Status Code: 405 Method Not Allowed
> Allow: HEAD,DELETE,GET,OPTIONS,PUT
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24296) [Yarn Queue Manager] Yarn Queue manager is allowing to Create a Child Queue for queue-mappings enabled Queue and Save it
[
https://issues.apache.org/jira/browse/AMBARI-24296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16660982#comment-16660982
]
Hudson commented on AMBARI-24296:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10243 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/10243/])
[AMBARI-24296] Yarn Queue manager is allowing to Create a Child Queue
(jonathanhurley:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=c540bb2d0ccca61f1ae689e189e7b3d5c0caece5])
* (edit)
contrib/views/capacity-scheduler/src/main/resources/ui/app/controllers/queues.js
> [Yarn Queue Manager] Yarn Queue manager is allowing to Create a Child Queue
> for queue-mappings enabled Queue and Save it
>
>
> Key: AMBARI-24296
> URL: https://issues.apache.org/jira/browse/AMBARI-24296
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.7.0
>Reporter: Akhil S Naik
>Assignee: Akhil S Naik
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Yarn Queue manager is allowing to Create a Child Queue for queue-mappings
> enabled Queue and Save the changes
> But the Operating is Failing as Yarn is having a check that Queue-mappings
> should only be allowed for Leaf queue
> Code which validates whether queue-mappings are enabled only for leaf-queue (
> YARN CODE)
> {code:java}
> private static QueueMapping validateAndGetQueueMapping(
> CapacitySchedulerQueueManager queueManager, CSQueue queue,
> QueueMapping mapping, QueuePath queuePath) throws IOException {
> if (!(queue instanceof LeafQueue)) {
> throw new IOException(
> "mapping contains invalid or non-leaf queue : " +
> mapping.getQueue());
> }
> {code}
> The buggy code in [Ambari Yarn Queue Manager which needs rework]:
> https://github.com/apache/ambari/blob/79cca1c7184f1661236971dac70d85a83fab6c11/contrib/views/capacity-scheduler/src/main/resources/ui/app/controllers/queues.js#L410
> {code:java}
> hasInvalidMapping = queues.filter(function(queue){
> return !queue.get("queues"); //get all leaf queues
> }).map(function(queue){
> return queue.get("name");
> }).indexOf(mapping[2]) == -1;
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23355) Add Hive Service wizard shows incorrect path for mysql driver in ambari-server setup command
[
https://issues.apache.org/jira/browse/AMBARI-23355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16660980#comment-16660980
]
Hudson commented on AMBARI-23355:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10243 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/10243/])
[AMBARI-23355] Add Hive Service wizard shows incorrect path for mysql
(jonathanhurley:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=464a5e887397232195536ed8fb180ad5a86a9ab5])
* (edit) ambari-web/app/views/common/configs/widgets/combo_config_widget_view.js
> Add Hive Service wizard shows incorrect path for mysql driver in
> ambari-server setup command
>
>
> Key: AMBARI-23355
> URL: https://issues.apache.org/jira/browse/AMBARI-23355
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: trunk
>Reporter: JaySenSharma
>Assignee: JaySenSharma
>Priority: Major
> Labels: ambari-web, pull-request-available
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> While installing Hive on Ambari it shows the message for installing driver
> with incorrect Driver JAR name in the setup command.
> {code}
> To use MySQL with Hive, you must download the
> https://dev.mysql.com/downloads/connector/j/ from MySQL. Once downloaded to
> the Ambari Server host, run:
> ambari-server setup --jdbc-db=mysql
> --jdbc-driver=/path/to/mysql/com.mysql.jdbc.Driver
> {code}
> Notice the path is *"/path/to/mysql/com.mysql.jdbc.Driver"*, which is
> supposed to be *"/path/to/mysql/mysql-connector-java.jar"*
> So if the users will follow the instruction as it is, then it will cause the
> following error:
> {code}
> # ambari-server setup --jdbc-db=mysql
> --jdbc-driver=/path/to/mysql/com.mysql.jdbc.Driver
> Using python /usr/bin/python
> Setup ambari-server
> ERROR: Exiting with exit code 1.
> REASON: File /path/to/mysql/com.mysql.jdbc.Driver does not exist!
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24818) Knox topology files installed via Ambari are world readable
[ https://issues.apache.org/jira/browse/AMBARI-24818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep More updated AMBARI-24818: -- Attachment: ambari.patch > Knox topology files installed via Ambari are world readable > --- > > Key: AMBARI-24818 > URL: https://issues.apache.org/jira/browse/AMBARI-24818 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Sandeep More >Assignee: Sandeep More >Priority: Major > Attachments: ambari.patch > > > The Knox topologies should only be accessible to the knox user. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24818) Knox topology files installed via Ambari are world readable
[ https://issues.apache.org/jira/browse/AMBARI-24818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep More updated AMBARI-24818: -- Status: Patch Available (was: Open) > Knox topology files installed via Ambari are world readable > --- > > Key: AMBARI-24818 > URL: https://issues.apache.org/jira/browse/AMBARI-24818 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Sandeep More >Assignee: Sandeep More >Priority: Major > Attachments: ambari.patch > > > The Knox topologies should only be accessible to the knox user. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24818) Knox topology files installed via Ambari are world readable
Sandeep More created AMBARI-24818: - Summary: Knox topology files installed via Ambari are world readable Key: AMBARI-24818 URL: https://issues.apache.org/jira/browse/AMBARI-24818 Project: Ambari Issue Type: Bug Affects Versions: 2.7.0 Reporter: Sandeep More Assignee: Sandeep More The Knox topologies should only be accessible to the knox user. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24817) Update incorrect instructions for updating alert groups with API
[
https://issues.apache.org/jira/browse/AMBARI-24817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley resolved AMBARI-24817.
--
Resolution: Fixed
> Update incorrect instructions for updating alert groups with API
>
>
> Key: AMBARI-24817
> URL: https://issues.apache.org/jira/browse/AMBARI-24817
> Project: Ambari
> Issue Type: Task
>Reporter: Jonathan Hurley
>Priority: Major
> Fix For: 2.8.0
>
>
> Submitting a POST request to
> {{api/v1/clusters/CLUSTER/alert_groups/GROUP-ID}} to update an alert returns
> a method not allowed error:
> {code}
> Status Code: 405 Method Not Allowed
> Allow: HEAD,DELETE,GET,OPTIONS,PUT
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24817) Update incorrect instructions for updating alert groups with API
Jonathan Hurley created AMBARI-24817:
Summary: Update incorrect instructions for updating alert groups
with API
Key: AMBARI-24817
URL: https://issues.apache.org/jira/browse/AMBARI-24817
Project: Ambari
Issue Type: Task
Reporter: Jonathan Hurley
Fix For: 2.8.0
Submitting a POST request to {{api/v1/clusters/CLUSTER/alert_groups/GROUP-ID}}
to update an alert returns a method not allowed error:
{code}
Status Code: 405 Method Not Allowed
Allow: HEAD,DELETE,GET,OPTIONS,PUT
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23925) Zeppelin is not respecting the absolute hdfs path for notebooks
[ https://issues.apache.org/jira/browse/AMBARI-23925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23925: Labels: pull-request-available (was: ) > Zeppelin is not respecting the absolute hdfs path for notebooks > --- > > Key: AMBARI-23925 > URL: https://issues.apache.org/jira/browse/AMBARI-23925 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.7.0 >Reporter: Supreeth Sharma >Assignee: Supreeth Sharma >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.3 > > > Zeppelin is not respecting the absolute hdfs path and picking up the > incorrect path for notebooks. > Even when user is setting 'zeppelin.notebook.dir' as > 'hdfs://ns2/zeppelin/tmp/tmp1/notebook', ambari is picking up the path as > /user/zeppelin/hdfs://ns2/zeppelin/tmp/tmp1/notebook > and due to this zeppelin service start is failing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24550) Yarn Timeline Service V2 Reader goes down after Ambari Upgrade from 2.7.0.0 to 2.7.1.0
[ https://issues.apache.org/jira/browse/AMBARI-24550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar resolved AMBARI-24550. Resolution: Fixed > Yarn Timeline Service V2 Reader goes down after Ambari Upgrade from 2.7.0.0 > to 2.7.1.0 > -- > > Key: AMBARI-24550 > URL: https://issues.apache.org/jira/browse/AMBARI-24550 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > STR: > 1) Install cluster with Ambari2.7.0.0 + HDP-3.0.0.0 > 2) Upgrade Ambari to 2.7.1.0 > Yarn Timeline Service V2 Reader goes down after some time. > Reason: the placeholders in yarn.timeline-service.reader.webapp.address and > yarn.timeline-service.reader.webapp.https.address are no longer replaced by > the stack code so these values become empty. In this case the timeline reader > will use the default ports which may conflict with other ports used by > other components. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24550) Yarn Timeline Service V2 Reader goes down after Ambari Upgrade from 2.7.0.0 to 2.7.1.0
[ https://issues.apache.org/jira/browse/AMBARI-24550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16660869#comment-16660869 ] Hudson commented on AMBARI-24550: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #377 (See [https://builds.apache.org/job/Ambari-branch-2.7/377/]) AMBARI-24550. Yarn Timeline Service V2 Reader goes down after Ambari (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=fb97376408ecefb19d13ddc505934e33cc03184d]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog271Test.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog271.java > Yarn Timeline Service V2 Reader goes down after Ambari Upgrade from 2.7.0.0 > to 2.7.1.0 > -- > > Key: AMBARI-24550 > URL: https://issues.apache.org/jira/browse/AMBARI-24550 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > STR: > 1) Install cluster with Ambari2.7.0.0 + HDP-3.0.0.0 > 2) Upgrade Ambari to 2.7.1.0 > Yarn Timeline Service V2 Reader goes down after some time. > Reason: the placeholders in yarn.timeline-service.reader.webapp.address and > yarn.timeline-service.reader.webapp.https.address are no longer replaced by > the stack code so these values become empty. In this case the timeline reader > will use the default ports which may conflict with other ports used by > other components. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22829) Services depending on HDFS do not start up properly (behind a proxy)
[ https://issues.apache.org/jira/browse/AMBARI-22829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22829: Labels: pull-request-available (was: ) > Services depending on HDFS do not start up properly (behind a proxy) > > > Key: AMBARI-22829 > URL: https://issues.apache.org/jira/browse/AMBARI-22829 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.6.1 >Reporter: Alberto >Priority: Minor > Labels: pull-request-available > > Services that depend on HDFS (HBase, Hive...) fail to start when the calls to > the HDFS API (http://:50070/webhdfs...> are redirected > through a corporate proxy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22280) falcon quicklinks.json added in AMBARI-19059 has typos
[
https://issues.apache.org/jira/browse/AMBARI-22280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-22280:
Labels: pull-request-available (was: )
> falcon quicklinks.json added in AMBARI-19059 has typos
> --
>
> Key: AMBARI-22280
> URL: https://issues.apache.org/jira/browse/AMBARI-22280
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.1
>Reporter: Rahul Pathak
>Assignee: Yusaku Sako
>Priority: Major
> Labels: pull-request-available
> Fix For: trunk
>
>
> ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/quicklinks/quicklinks.json
> added in AMBARI-19059 has below typos.
> {code}
> "property":"falcon.enableTLS" should be "property":"*.falcon.enableTLS",
> "site":"falcon-startup-properties" should be
> "site":"falcon-startup.properties"
> {code}
> Due to this quicklink for falcon is not working after enabling ssl for falcon.
> I have verified that making above changes on ambari server solve the problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22184) Add a default port for binary mode for Spark/Spark2 Thriftserver
[
https://issues.apache.org/jira/browse/AMBARI-22184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-22184:
Labels: pull-request-available (was: )
> Add a default port for binary mode for Spark/Spark2 Thriftserver
>
>
> Key: AMBARI-22184
> URL: https://issues.apache.org/jira/browse/AMBARI-22184
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Marco Gaido
>Priority: Minor
> Labels: pull-request-available
>
> Ambari sets a default for {{hive.server2.thrift.port}}, but it doesn't for
> {{hive.server2.thrift.http.port}}. So if you switch from binary to http mode
> there is a conflict with HiveServer2, since the default port in the code is
> the same.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-19850) Default value for storm.messaging.netty.max_retries is incorrect
[
https://issues.apache.org/jira/browse/AMBARI-19850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-19850:
Labels: pull-request-available (was: )
> Default value for storm.messaging.netty.max_retries is incorrect
>
>
> Key: AMBARI-19850
> URL: https://issues.apache.org/jira/browse/AMBARI-19850
> Project: Ambari
> Issue Type: Bug
>Reporter: Tibor Kiss
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
>
> Apache Storm's default value for {{storm.messaging.netty.max_retries}}
> parameter is set to 300:
> https://github.com/apache/storm/blob/v1.0.1/conf/defaults.yaml#L202
> In Ambari this is set to 30 by default which could cause messaging problems
> in overloaded clusters.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24779) Move Namenode operation fails as it tries to install and start ZKFailoverController on non-HA cluster
[
https://issues.apache.org/jira/browse/AMBARI-24779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-24779:
--
Reporter: Vivek Sharma (was: Ishan Bhatt)
> Move Namenode operation fails as it tries to install and start
> ZKFailoverController on non-HA cluster
> --
>
> Key: AMBARI-24779
> URL: https://issues.apache.org/jira/browse/AMBARI-24779
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Reporter: Vivek Sharma
>Assignee: Ishan Bhatt
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Error at final screen during Service start for ZKFailoverController. This is
> unexpected as the cluster is non-HA and ZKFailoverController component should
> not be attempted for a start at all on the new NN host
> {code:java}
> 2018-10-11 14:22:52,136 - Execute['ambari-sudo.sh su cstm-hdfs -l -s
> /bin/bash -c 'ulimit -c unlimited ; /usr/hdp/3.0.3.0-74/hadoop/bin/hdfs
> --config /usr/hdp/3.0.3.0-74/hadoop/conf --daemon start zkfc'']
> {'environment': {'HADOOP_LIBEXEC_DIR': '/usr/hdp/3.0.3.0-74/hadoop/libexec'},
> 'not_if': 'ambari-sudo.sh -H -E test -f
> /var/run/hadoop/cstm-hdfs/hadoop-cstm-hdfs-zkfc.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop/cstm-hdfs/hadoop-cstm-hdfs-zkfc.pid'}
> 2018-10-11 14:22:54,336 - Execute['find /grid/0/log/hdfs/cstm-hdfs -maxdepth
> 1 -type f -name '*' -exec echo '==> {} <==' \; -exec tail -n 40 {} \;']
> {'logoutput': True, 'ignore_failures': True, 'user': 'cstm-hdfs'}
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> ==>
> /grid/0/log/hdfs/cstm-hdfs/hadoop-cstm-hdfs-zkfc-ctr-e138-1518143905142-517699-01-03.hwx.site.out
> <==
> Exception in thread "main" org.apache.hadoop.HadoopIllegalArgumentException:
> HA is not enabled for this namenode.
> at
> org.apache.hadoop.hdfs.tools.DFSZKFailoverController.create(DFSZKFailoverController.java:134)
> at
> org.apache.hadoop.hdfs.tools.DFSZKFailoverController.main(DFSZKFailoverController.java:192)
> core file size (blocks, -c) unlimited
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24767) Error while starting Timeline v2 Reader during Move operation
[
https://issues.apache.org/jira/browse/AMBARI-24767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-24767:
--
Reporter: Vivek Sharma (was: Attila Magyar)
> Error while starting Timeline v2 Reader during Move operation
> -
>
> Key: AMBARI-24767
> URL: https://issues.apache.org/jira/browse/AMBARI-24767
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Vivek Sharma
>Assignee: Attila Magyar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> # Deployed HDP-3.0.3 HA cluster with Ambari-2.7.3 (Active RM and Timeline v2
> Reader are on the same host)
> # Under Yarn --> Service Actions - choose to Move Timeline Service V2.0
> Reader. Pick a new host and let the move operation complete
> {code}
> 2018-10-11 13:04:33,887 ERROR reader.TimelineReaderServer
> (TimelineReaderServer.java:startTimelineReaderServer(236)) - Error starting
> TimelineReaderWebServer
> org.apache.hadoop.yarn.exceptions.YarnRuntimeException: Failed to login from
> keytab
> at
> org.apache.hadoop.yarn.server.timelineservice.reader.TimelineReaderServer.serviceInit(TimelineReaderServer.java:88)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:164)
> at
> org.apache.hadoop.yarn.server.timelineservice.reader.TimelineReaderServer.startTimelineReaderServer(TimelineReaderServer.java:233)
> at
> org.apache.hadoop.yarn.server.timelineservice.reader.TimelineReaderServer.main(TimelineReaderServer.java:246)
> Caused by: org.apache.hadoop.security.KerberosAuthException: failure to
> login: for principal:
> yarn/ctr-e138-1518143905142-517945-01-06.hwx.s...@example.com from keytab
> /etc/security/keytabs/yarn.service.keytab
> javax.security.auth.login.LoginException: Unable to obtain password from user
> at
> org.apache.hadoop.security.UserGroupInformation.doSubjectLogin(UserGroupInformation.java:1847)
> at
> org.apache.hadoop.security.UserGroupInformation.loginUserFromKeytabAndReturnUGI(UserGroupInformation.java:1215)
> at
> org.apache.hadoop.security.UserGroupInformation.loginUserFromKeytab(UserGroupInformation.java:1008)
> at org.apache.hadoop.security.SecurityUtil.login(SecurityUtil.java:313)
> at
> org.apache.hadoop.yarn.server.timelineservice.reader.TimelineReaderServer.serviceInit(TimelineReaderServer.java:85)
> ... 3 more
> Caused by: javax.security.auth.login.LoginException: Unable to obtain
> password from user
> at
> com.sun.security.auth.module.Krb5LoginModule.promptForPass(Krb5LoginModule.java:897)
> at
> com.sun.security.auth.module.Krb5LoginModule.attemptAuthentication(Krb5LoginModule.java:760)
> at
> com.sun.security.auth.module.Krb5LoginModule.login(Krb5LoginModule.java:617)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at javax.security.auth.login.LoginContext.invoke(LoginContext.java:755)
> at
> javax.security.auth.login.LoginContext.access$000(LoginContext.java:195)
> at javax.security.auth.login.LoginContext$4.run(LoginContext.java:682)
> at javax.security.auth.login.LoginContext$4.run(LoginContext.java:680)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
> at javax.security.auth.login.LoginContext.login(LoginContext.java:587)
> at
> org.apache.hadoop.security.UserGroupInformation$HadoopLoginContext.login(UserGroupInformation.java:1926)
> at
> org.apache.hadoop.security.UserGroupInformation.doSubjectLogin(UserGroupInformation.java:1837)
> ... 7 more
> 2018-10-11 13:04:33,890 INFO util.ExitUtil (ExitUtil.java:terminate(210)) -
> Exiting with status -1: Error starting TimelineReaderWebServer
> 2018-10-11 13:04:33,894 INFO reader.TimelineReaderServer
> (LogAdapter.java:info(51)) - SHUTDOWN_MSG:
> /
> SHUTDOWN_MSG: Shutting down TimelineReaderServer at
> ctr-e138-1518143905142-517945-01-02.hwx.site/172.27.74.4
> /
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24791) Node Managers fail to start after RM is moved to a different host as 'resource-tracker.address' config is not updated
[ https://issues.apache.org/jira/browse/AMBARI-24791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-24791: -- Reporter: Vivek Sharma (was: Ishan Bhatt) > Node Managers fail to start after RM is moved to a different host as > 'resource-tracker.address' config is not updated > - > > Key: AMBARI-24791 > URL: https://issues.apache.org/jira/browse/AMBARI-24791 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Vivek Sharma >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h > Remaining Estimate: 0h > > # Under Yarn --> Service Actions - choose to Move Resource Manager. Pick a > new host for the active RM node and let the move operation complete > # Observe the state of Node Managers in Ambari UI > *Result* > All Node Managers show as down. > Observed that one of the configs - > 'yarn.resourcemanager.resource-tracker.address.rm2' still points to older RM > node[!Screen Shot 2018-10-11 at 6.20.51 > PM.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/165347/165347_Screen+Shot+2018-10-11+at+6.20.51+PM.png] > , which may be causing this issue -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (AMBARI-24809) API Call to change the repository configuration doesn't work
[ https://issues.apache.org/jira/browse/AMBARI-24809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16660764#comment-16660764 ] Paulo Moraes Moura edited comment on AMBARI-24809 at 10/23/18 2:51 PM: --- Just discovered that the repo customization should be done throught the version definition since Ambari 2.6. https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.0.0/bk_ambari-release-notes/content/ambari_relnotes-2.6.0.0-behavioral-changes.html Maybe displaying a deprecated warning to any calls made to the old api would be helpful. was (Author: pmoraesm): Just discovered that the repo customization should be done throught the version definition since Ambari 2.6. Maybe displaying a deprecated warning to any calls made to the old api would be helpful. > API Call to change the repository configuration doesn't work > > > Key: AMBARI-24809 > URL: https://issues.apache.org/jira/browse/AMBARI-24809 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.7.1 >Reporter: Paulo Moraes Moura >Priority: Major > Attachments: ambari-audit.log, curl_get_new_repo.txt, > curl_put_new_repo.txt, hdp-3.0-repo.json > > > Updating the repository configuration through the API call isn't working. > After submitting the request, a status 200 is received and an update repo > configuration line is printed in the ambari-audit.log, but the public repo > still is used in the installation. > > Attached: > * curl PUT request to update repo configuration > * json file containing desired configuration > * ambari-audit.log showing the update > * curl GET request to retrieve the values after performing the PUT > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24809) API Call to change the repository configuration doesn't work
[ https://issues.apache.org/jira/browse/AMBARI-24809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16660764#comment-16660764 ] Paulo Moraes Moura commented on AMBARI-24809: - Just discovered that the repo customization should be done throught the version definition since Ambari 2.6. Maybe displaying a deprecated warning to any calls made to the old api would be helpful. > API Call to change the repository configuration doesn't work > > > Key: AMBARI-24809 > URL: https://issues.apache.org/jira/browse/AMBARI-24809 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.7.1 >Reporter: Paulo Moraes Moura >Priority: Major > Attachments: ambari-audit.log, curl_get_new_repo.txt, > curl_put_new_repo.txt, hdp-3.0-repo.json > > > Updating the repository configuration through the API call isn't working. > After submitting the request, a status 200 is received and an update repo > configuration line is printed in the ambari-audit.log, but the public repo > still is used in the installation. > > Attached: > * curl PUT request to update repo configuration > * json file containing desired configuration > * ambari-audit.log showing the update > * curl GET request to retrieve the values after performing the PUT > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24816) Cover dashboard widgets views
[ https://issues.apache.org/jira/browse/AMBARI-24816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24816: Labels: pull-request-available (was: ) > Cover dashboard widgets views > - > > Key: AMBARI-24816 > URL: https://issues.apache.org/jira/browse/AMBARI-24816 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24816) Cover dashboard widgets views
Antonenko Alexander created AMBARI-24816: Summary: Cover dashboard widgets views Key: AMBARI-24816 URL: https://issues.apache.org/jira/browse/AMBARI-24816 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Antonenko Alexander -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-24816) Cover dashboard widgets views
[ https://issues.apache.org/jira/browse/AMBARI-24816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-24816: Assignee: Antonenko Alexander > Cover dashboard widgets views > - > > Key: AMBARI-24816 > URL: https://issues.apache.org/jira/browse/AMBARI-24816 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24813) Merge missing agent commits to branch-2.7
[ https://issues.apache.org/jira/browse/AMBARI-24813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16660621#comment-16660621 ] Hudson commented on AMBARI-24813: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #376 (See [https://builds.apache.org/job/Ambari-branch-2.7/376/]) AMBARI-24813. Merge missing agent commits to branch-2.7 (aonishuk) (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=232e3ba25d5a809acf84cdb7d15f0b0984a27ac1]) * (edit) ambari-server/src/test/python/custom_actions/TestInstallPackages.py * (edit) ambari-common/src/main/python/resource_management/libraries/providers/__init__.py * (edit) ambari-common/src/main/python/resource_management/libraries/providers/repository.py * (edit) ambari-server/src/test/python/stacks/2.0.6/hooks/before-INSTALL/test_before_install.py * (edit) ambari-agent/src/test/python/resource_management/TestRepositoryResource.py * (edit) ambari-server/src/test/python/custom_actions/TestUpdateRepo.py * (edit) ambari-server/src/main/resources/stack-hooks/before-INSTALL/scripts/repo_initialization.py * (edit) ambari-common/src/main/python/resource_management/libraries/functions/repository_util.py * (edit) ambari-common/src/main/python/resource_management/libraries/resources/repository.py * (edit) ambari-server/src/main/resources/custom_actions/scripts/update_repo.py * (edit) ambari-server/src/test/python/stacks/2.0.6/OOZIE/test_oozie_server.py > Merge missing agent commits to branch-2.7 > - > > Key: AMBARI-24813 > URL: https://issues.apache.org/jira/browse/AMBARI-24813 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: AMBARI-24813.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24815) Add column to show which service recommended changes during upgrade refer to
[ https://issues.apache.org/jira/browse/AMBARI-24815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16660575#comment-16660575 ] Hudson commented on AMBARI-24815: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10242 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10242/]) AMBARI-24815 Add column to show which service recommended changes during (1963907+atkach: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=22f6a504dee9d98eca3c5eb9fcc90bbe1d12f716]) * (edit) ambari-web/test/controllers/main/admin/stack_and_upgrade_controller_test.js * (edit) ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js * (edit) ambari-web/app/messages.js > Add column to show which service recommended changes during upgrade refer to > > > Key: AMBARI-24815 > URL: https://issues.apache.org/jira/browse/AMBARI-24815 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: open_recommended_config_changes.png > > Time Spent: 50m > Remaining Estimate: 0h > > During the stack upgrade from HDP 2.6 -> HDP 3.x, the list of changes Ambari > wants to make to each service is very difficult to interpret. Below is an > example of the config changes Ambari recommends when attempting to upgrade > fresh-install HDP2.6.2 cluster. > Here's an example of how these configs look like when the user presses the > "Open" button: > open_recommended_config_changes.png > Note the highlighting is not intentional - it is automatically done by the > browser (chrome) due to the special characters in the configs. > A small step to improve the user experience would be to add a column that > shows which service each config applies. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24815) Add column to show which service recommended changes during upgrade refer to
[ https://issues.apache.org/jira/browse/AMBARI-24815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16660529#comment-16660529 ] Andrii Tkach commented on AMBARI-24815: --- committed to trunk > Add column to show which service recommended changes during upgrade refer to > > > Key: AMBARI-24815 > URL: https://issues.apache.org/jira/browse/AMBARI-24815 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: open_recommended_config_changes.png > > Time Spent: 50m > Remaining Estimate: 0h > > During the stack upgrade from HDP 2.6 -> HDP 3.x, the list of changes Ambari > wants to make to each service is very difficult to interpret. Below is an > example of the config changes Ambari recommends when attempting to upgrade > fresh-install HDP2.6.2 cluster. > Here's an example of how these configs look like when the user presses the > "Open" button: > open_recommended_config_changes.png > Note the highlighting is not intentional - it is automatically done by the > browser (chrome) due to the special characters in the configs. > A small step to improve the user experience would be to add a column that > shows which service each config applies. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24815) Add column to show which service recommended changes during upgrade refer to
[ https://issues.apache.org/jira/browse/AMBARI-24815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach resolved AMBARI-24815. --- Resolution: Fixed > Add column to show which service recommended changes during upgrade refer to > > > Key: AMBARI-24815 > URL: https://issues.apache.org/jira/browse/AMBARI-24815 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: open_recommended_config_changes.png > > Time Spent: 50m > Remaining Estimate: 0h > > During the stack upgrade from HDP 2.6 -> HDP 3.x, the list of changes Ambari > wants to make to each service is very difficult to interpret. Below is an > example of the config changes Ambari recommends when attempting to upgrade > fresh-install HDP2.6.2 cluster. > Here's an example of how these configs look like when the user presses the > "Open" button: > open_recommended_config_changes.png > Note the highlighting is not intentional - it is automatically done by the > browser (chrome) due to the special characters in the configs. > A small step to improve the user experience would be to add a column that > shows which service each config applies. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24786) Cover common configs views
[ https://issues.apache.org/jira/browse/AMBARI-24786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16660442#comment-16660442 ] Hudson commented on AMBARI-24786: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10241 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10241/]) AMBARI-24786. Cover common configs views (aantonenko: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=c6f36e1240f8f7d81b925c14114a75e8af941e73]) * (add) ambari-web/test/views/common/configs/service_config_layout_tab_compare_view_test.js * (add) ambari-web/test/views/common/configs/service_config_layout_tab_view_test.js * (add) ambari-web/test/views/common/configs/config_category_container_view_test.js * (edit) ambari-web/app/assets/test/tests.js > Cover common configs views > -- > > Key: AMBARI-24786 > URL: https://issues.apache.org/jira/browse/AMBARI-24786 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24801) Cover alert definition views
[ https://issues.apache.org/jira/browse/AMBARI-24801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16660417#comment-16660417 ] Hudson commented on AMBARI-24801: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10240 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10240/]) AMBARI-24801. Cover alert definition views (aantonenko: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=72a6079f23d330de07f3c5a044c686dd9a7a8366]) * (edit) ambari-web/app/assets/test/tests.js * (add) ambari-web/test/views/main/alerts/alert_definition/alert_definition_summary_test.js > Cover alert definition views > > > Key: AMBARI-24801 > URL: https://issues.apache.org/jira/browse/AMBARI-24801 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24794) Adding Ranger Password configs in Admin Settings section under Advanced config
[ https://issues.apache.org/jira/browse/AMBARI-24794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16660386#comment-16660386 ] Hudson commented on AMBARI-24794: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #374 (See [https://builds.apache.org/job/Ambari-branch-2.7/374/]) AMBARI-24794 Adding Ranger Password configs in Admin Settings section (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=499bdc0aeadbc4b5a1223e8c9ae9bc4f38edc447]) * (edit) ambari-web/app/data/configs/services/ranger_properties.js > Adding Ranger Password configs in Admin Settings section under Advanced config > -- > > Key: AMBARI-24794 > URL: https://issues.apache.org/jira/browse/AMBARI-24794 > Project: Ambari > Issue Type: Bug >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > Fix For: trunk, 2.7.3 > > Attachments: AMBARI-24794.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > > This jira is fixing the below password configs to be shown in 'Admin > Settings' section under Advanced Config section for Ranger service. > * rangerusersync_user_password > * rangertagsync_user_password > * keyadmin_user_password -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24801) Cover alert definition views
[ https://issues.apache.org/jira/browse/AMBARI-24801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander resolved AMBARI-24801. -- Resolution: Fixed Committed to trunk > Cover alert definition views > > > Key: AMBARI-24801 > URL: https://issues.apache.org/jira/browse/AMBARI-24801 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24786) Cover common configs views
[ https://issues.apache.org/jira/browse/AMBARI-24786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-24786: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Cover common configs views > -- > > Key: AMBARI-24786 > URL: https://issues.apache.org/jira/browse/AMBARI-24786 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-24801) Cover alert definition views
[ https://issues.apache.org/jira/browse/AMBARI-24801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-24801: Assignee: Antonenko Alexander > Cover alert definition views > > > Key: AMBARI-24801 > URL: https://issues.apache.org/jira/browse/AMBARI-24801 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24815) Add column to show which service recommended changes during upgrade refer to
[ https://issues.apache.org/jira/browse/AMBARI-24815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24815: Labels: pull-request-available (was: ) > Add column to show which service recommended changes during upgrade refer to > > > Key: AMBARI-24815 > URL: https://issues.apache.org/jira/browse/AMBARI-24815 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: open_recommended_config_changes.png > > > During the stack upgrade from HDP 2.6 -> HDP 3.x, the list of changes Ambari > wants to make to each service is very difficult to interpret. Below is an > example of the config changes Ambari recommends when attempting to upgrade > fresh-install HDP2.6.2 cluster. > Here's an example of how these configs look like when the user presses the > "Open" button: > open_recommended_config_changes.png > Note the highlighting is not intentional - it is automatically done by the > browser (chrome) due to the special characters in the configs. > A small step to improve the user experience would be to add a column that > shows which service each config applies. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24794) Adding Ranger Password configs in Admin Settings section under Advanced config
[ https://issues.apache.org/jira/browse/AMBARI-24794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-24794: - Resolution: Fixed Status: Resolved (was: Patch Available) > Adding Ranger Password configs in Admin Settings section under Advanced config > -- > > Key: AMBARI-24794 > URL: https://issues.apache.org/jira/browse/AMBARI-24794 > Project: Ambari > Issue Type: Bug >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > Fix For: trunk, 2.7.3 > > Attachments: AMBARI-24794.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > > This jira is fixing the below password configs to be shown in 'Admin > Settings' section under Advanced Config section for Ranger service. > * rangerusersync_user_password > * rangertagsync_user_password > * keyadmin_user_password -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24815) Add column to show which service recommended changes during upgrade refer to
[ https://issues.apache.org/jira/browse/AMBARI-24815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-24815: -- Attachment: open_recommended_config_changes.png > Add column to show which service recommended changes during upgrade refer to > > > Key: AMBARI-24815 > URL: https://issues.apache.org/jira/browse/AMBARI-24815 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Fix For: 2.7.3 > > Attachments: open_recommended_config_changes.png > > > During the stack upgrade from HDP 2.6 -> HDP 3.x, the list of changes Ambari > wants to make to each service is very difficult to interpret. Below is an > example of the config changes Ambari recommends when attempting to upgrade > fresh-install HDP2.6.2 cluster. > Here's an example of how these configs look like when the user presses the > "Open" button: > open_recommended_config_changes.png > Note the highlighting is not intentional - it is automatically done by the > browser (chrome) due to the special characters in the configs. > A small step to improve the user experience would be to add a column that > shows which service each config applies. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24815) Add column to show which service recommended changes during upgrade refer to
Andrii Tkach created AMBARI-24815: - Summary: Add column to show which service recommended changes during upgrade refer to Key: AMBARI-24815 URL: https://issues.apache.org/jira/browse/AMBARI-24815 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.1 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.7.3 During the stack upgrade from HDP 2.6 -> HDP 3.x, the list of changes Ambari wants to make to each service is very difficult to interpret. Below is an example of the config changes Ambari recommends when attempting to upgrade fresh-install HDP2.6.2 cluster. Here's an example of how these configs look like when the user presses the "Open" button: open_recommended_config_changes.png Note the highlighting is not intentional - it is automatically done by the browser (chrome) due to the special characters in the configs. A small step to improve the user experience would be to add a column that shows which service each config applies. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24814) Add a rolling_restart_supported flag at the stack service endpoint
[ https://issues.apache.org/jira/browse/AMBARI-24814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24814: Labels: pull-request-available (was: ) > Add a rolling_restart_supported flag at the stack service endpoint > -- > > Key: AMBARI-24814 > URL: https://issues.apache.org/jira/browse/AMBARI-24814 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.8.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > Similar to the one at stack service component level we need a flag for HDFS, > YARN and Zookeeper > at api/v1/stacks/HDP/versions//services/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24814) Add a rolling_restart_supported flag at the stack service endpoint
Dmytro Sen created AMBARI-24814: --- Summary: Add a rolling_restart_supported flag at the stack service endpoint Key: AMBARI-24814 URL: https://issues.apache.org/jira/browse/AMBARI-24814 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 2.8.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 2.8.0 Similar to the one at stack service component level we need a flag for HDFS, YARN and Zookeeper at api/v1/stacks/HDP/versions//services/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24813) Merge missing agent commits to branch-2.7
[ https://issues.apache.org/jira/browse/AMBARI-24813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24813: Labels: pull-request-available (was: ) > Merge missing agent commits to branch-2.7 > - > > Key: AMBARI-24813 > URL: https://issues.apache.org/jira/browse/AMBARI-24813 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: AMBARI-24813.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24813) Merge missing agent commits to branch-2.7
[ https://issues.apache.org/jira/browse/AMBARI-24813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24813: - Status: Patch Available (was: Open) > Merge missing agent commits to branch-2.7 > - > > Key: AMBARI-24813 > URL: https://issues.apache.org/jira/browse/AMBARI-24813 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.3 > > Attachments: AMBARI-24813.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24813) Merge missing agent commits to branch-2.7
[ https://issues.apache.org/jira/browse/AMBARI-24813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24813: - Attachment: AMBARI-24813.patch > Merge missing agent commits to branch-2.7 > - > > Key: AMBARI-24813 > URL: https://issues.apache.org/jira/browse/AMBARI-24813 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.3 > > Attachments: AMBARI-24813.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24813) Merge missing agent commits to branch-2.7
Andrew Onischuk created AMBARI-24813: Summary: Merge missing agent commits to branch-2.7 Key: AMBARI-24813 URL: https://issues.apache.org/jira/browse/AMBARI-24813 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.7.3 Attachments: AMBARI-24813.patch -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24709) Implement support for Minimal Blueprint Export
[ https://issues.apache.org/jira/browse/AMBARI-24709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-24709: --- Status: Patch Available (was: In Progress) > Implement support for Minimal Blueprint Export > -- > > Key: AMBARI-24709 > URL: https://issues.apache.org/jira/browse/AMBARI-24709 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 2.5h > Remaining Estimate: 0h > > Implement a new mode for Blueprint exports, a "minimal" mode in which only > modified configuration is included in the exported Blueprint. The original > "full" Blueprint export should still be possible, in order to maintain > backwards compatibility. -- 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: Won't Fix
> 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
>Assignee: Doroszlai, Attila
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> 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] [Commented] (AMBARI-21157) Code cleanup
[ https://issues.apache.org/jira/browse/AMBARI-21157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16660229#comment-16660229 ] Hudson commented on AMBARI-21157: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10239 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10239/]) AMBARI-21157. Fix unintended newline in license (#2496) (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=88af062a0a3d0b1c98f3fafbc9c1144f296c8cff]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ExportBlueprintRequest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/topology/ClusterTopologyImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/topology/SecurityConfiguration.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/topology/BlueprintValidator.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/topology/NoSuchHostGroupException.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/topology/TopologyRequestFactoryImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ConfigurationTopologyException.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/topology/SecurityConfigurationFactory.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/topology/ConfigurationFactory.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/topology/NoSuchBlueprintException.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/topology/tasks/TopologyTask.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/topology/BlueprintFactory.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/topology/HostOfferResponse.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/topology/BlueprintImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/topology/Configuration.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/topology/HostGroupImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/topology/TopologyRequestFactory.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/topology/Credential.java > Code cleanup > > > Key: AMBARI-21157 > URL: https://issues.apache.org/jira/browse/AMBARI-21157 > Project: Ambari > Issue Type: Epic > Components: ambari-server >Affects Versions: trunk >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Time Spent: 40m > Remaining Estimate: 0h > > Clean up Ambari Server source code warnings. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24794) Adding Ranger Password configs in Admin Settings section under Advanced config
[ https://issues.apache.org/jira/browse/AMBARI-24794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-24794: - Status: Patch Available (was: In Progress) > Adding Ranger Password configs in Admin Settings section under Advanced config > -- > > Key: AMBARI-24794 > URL: https://issues.apache.org/jira/browse/AMBARI-24794 > Project: Ambari > Issue Type: Bug >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > Fix For: trunk, 2.7.3 > > Attachments: AMBARI-24794.patch > > Time Spent: 40m > Remaining Estimate: 0h > > This jira is fixing the below password configs to be shown in 'Admin > Settings' section under Advanced Config section for Ranger service. > * rangerusersync_user_password > * rangertagsync_user_password > * keyadmin_user_password -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24794) Adding Ranger Password configs in Admin Settings section under Advanced config
[ https://issues.apache.org/jira/browse/AMBARI-24794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-24794: - Fix Version/s: 2.7.3 > Adding Ranger Password configs in Admin Settings section under Advanced config > -- > > Key: AMBARI-24794 > URL: https://issues.apache.org/jira/browse/AMBARI-24794 > Project: Ambari > Issue Type: Bug >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > Fix For: trunk, 2.7.3 > > Attachments: AMBARI-24794.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > This jira is fixing the below password configs to be shown in 'Admin > Settings' section under Advanced Config section for Ranger service. > * rangerusersync_user_password > * rangertagsync_user_password > * keyadmin_user_password -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24794) Adding Ranger Password configs in Admin Settings section under Advanced config
[ https://issues.apache.org/jira/browse/AMBARI-24794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-24794: - Fix Version/s: trunk > Adding Ranger Password configs in Admin Settings section under Advanced config > -- > > Key: AMBARI-24794 > URL: https://issues.apache.org/jira/browse/AMBARI-24794 > Project: Ambari > Issue Type: Bug >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Attachments: AMBARI-24794.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > This jira is fixing the below password configs to be shown in 'Admin > Settings' section under Advanced Config section for Ranger service. > * rangerusersync_user_password > * rangertagsync_user_password > * keyadmin_user_password -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (AMBARI-24794) Adding Ranger Password configs in Admin Settings section under Advanced config
[ https://issues.apache.org/jira/browse/AMBARI-24794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar reopened AMBARI-24794: -- > Adding Ranger Password configs in Admin Settings section under Advanced config > -- > > Key: AMBARI-24794 > URL: https://issues.apache.org/jira/browse/AMBARI-24794 > Project: Ambari > Issue Type: Bug >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Attachments: AMBARI-24794.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > This jira is fixing the below password configs to be shown in 'Admin > Settings' section under Advanced Config section for Ranger service. > * rangerusersync_user_password > * rangertagsync_user_password > * keyadmin_user_password -- This message was sent by Atlassian JIRA (v7.6.3#76005)
