[jira] [Created] (AMBARI-25307) Ambari Configurable Password policy: user creation error popup is not expanded by default
Vivek Rathod created AMBARI-25307: - Summary: Ambari Configurable Password policy: user creation error popup is not expanded by default Key: AMBARI-25307 URL: https://issues.apache.org/jira/browse/AMBARI-25307 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.4 Reporter: Vivek Rathod Fix For: 2.7.4 Set a password policy and then try to set an invalid password. UI throws a popup error but the popup is not expanded. User has to manually expand it. It would be a good user experience if it was expanded in the first place -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25306) Ambari Configurable Password policy: Invalid regex must throw exception/error
Vivek Rathod created AMBARI-25306:
-
Summary: Ambari Configurable Password policy: Invalid regex must
throw exception/error
Key: AMBARI-25306
URL: https://issues.apache.org/jira/browse/AMBARI-25306
Project: Ambari
Issue Type: Bug
Components: ambari-sever
Affects Versions: 2.7.4
Reporter: Vivek Rathod
Ambari Configurable Password policy: Invalid regex must throw exception/error
Try to configure \{code}security.password.policy.regexp\{code} with invalid
regex like \{code}^(?=.*[A-Za-z])(?=.*\\d)[A-Za-z\\d]\{8, {code}
In this case ambari server restart is successful. Only when user tries to set a
password, UI shows an error
This can be handled in a better way, maybe ambari server restart should throw
exception?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24749) Stackadvisor error while enabling HSI
Vivek Rathod created AMBARI-24749:
-
Summary: Stackadvisor error while enabling HSI
Key: AMBARI-24749
URL: https://issues.apache.org/jira/browse/AMBARI-24749
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.3
Reporter: Vivek Rathod
Fix For: 2.7.3
Stackadvisor error while enabling HSI
STR:
On a deployed cluster, enable HSI from Hive Service Page. Stackadvisor throws
error
{code}
Traceback (most recent call last):
File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 184, in
main(sys.argv)
File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 138, in
main
result = stackAdvisor.validateConfigurations(services, hosts)
File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
line 1079, in validateConfigurations
validationItems = self.getConfigurationsValidationItems(services, hosts)
File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
line 1463, in getConfigurationsValidationItems
recommendations = self.recommendConfigurations(services, hosts)
File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
line 1639, in recommendConfigurations
serviceAdvisor.getServiceConfigurationRecommendations(configurations,
clusterSummary, services, hosts)
File
"/var/lib/ambari-server/resources/stacks/HDP/3.0/services/ZEPPELIN/service_advisor.py",
line 124, in getServiceConfigurationRecommendations
recommender.recommendZeppelinConfigurationsFromHDP25(configurations,
clusterData, services, hosts)
File
"/var/lib/ambari-server/resources/stacks/HDP/3.0/services/ZEPPELIN/service_advisor.py",
line 190, in recommendZeppelinConfigurationsFromHDP25
shiro_ini_content = zeppelin_shiro_ini['shiro_ini_content']
TypeError: 'NoneType' object has no attribute '__getitem__'
{code}
As a result HSI start fails because of misconfiguration
{code}
Failed: Cache size (0B) has to be smaller than the container sizing (0B)
java.lang.IllegalArgumentException: Cache size (0B) has to be smaller than the
container sizing (0B)
at com.google.common.base.Preconditions.checkArgument(Preconditions.java:122)
at
org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:248)
at
org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:120)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24498) Upgrade History page is blank after cluster is upgraded multiple times
Vivek Rathod created AMBARI-24498: - Summary: Upgrade History page is blank after cluster is upgraded multiple times Key: AMBARI-24498 URL: https://issues.apache.org/jira/browse/AMBARI-24498 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.1 Reporter: Vivek Rathod Fix For: 2.7.1 *STR* # Deployed cluster with Ambari version: 2.5.2.0-298 and HDP version: 2.6.2.14-5 # Upgrade Ambari to 2.6.2.0, HDP to 2.6.5.0 # Upgrade Ambari to 2.7.0, HDP to 3.0.1.0 # Go to Upgrade history page Upgrade history page shows empty (see attached for js error) Looks like an error while getting services info from older version -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24458) Start operation is disabled for HDFS after stopping components for one namespace
Vivek Rathod created AMBARI-24458: - Summary: Start operation is disabled for HDFS after stopping components for one namespace Key: AMBARI-24458 URL: https://issues.apache.org/jira/browse/AMBARI-24458 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.1 Environment: ambari-server version: ambari-server-2.7.1.0-70.x86_64 ambari-server --hash: f6d369619dc259e6ade537d6cdb3396f9e01c3dd Reporter: Vivek Rathod Fix For: 2.7.1 Attachments: Screen Shot 2018-08-10 at 10.16.46 AM.png, Screen Shot 2018-08-10 at 10.17.01 AM.png Start operation is disabled for HDFS after stopping components for one namespace STR: 1) On hdfs service page, stop components for one namespace (ns1) 2) Try to start them. Start button is disabled -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24399) Components start failing with 'Holder DFSClient_NONMAPREDUCE does not have any open files' while adding Namespace
[
https://issues.apache.org/jira/browse/AMBARI-24399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Rathod updated AMBARI-24399:
--
Summary: Components start failing with 'Holder DFSClient_NONMAPREDUCE does
not have any open files' while adding Namespace (was: Components start
failing with Holder DFSClient_NONMAPREDUCE does not have any open files)
> Components start failing with 'Holder DFSClient_NONMAPREDUCE does not have
> any open files' while adding Namespace
> --
>
> Key: AMBARI-24399
> URL: https://issues.apache.org/jira/browse/AMBARI-24399
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.1
>Reporter: Vivek Rathod
>Priority: Major
> Fix For: 2.7.1
>
>
> STR:
> Add a namespace from UI. In the last step restart required services,
> hiveserver2 restart fails. Although on retrying it comes back up
> {code}
> Traceback (most recent call last):
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 982, in restart
> self.status(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_server.py",
> line 79, in status
> check_process_status(status_params.hive_pid)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/functions/check_process_status.py",
> line 43, in check_process_status
> raise ComponentIsNotRunning()
> ComponentIsNotRunning
> The above exception was the cause of the following exception:
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_server.py",
> line 137, in
> HiveServer().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 993, in restart
> self.start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_server.py",
> line 50, in start
> self.configure(env) # FOR SECURITY
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_server.py",
> line 45, in configure
> hive(name='hiveserver2')
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive.py",
> line 119, in hive
> setup_hiveserver2()
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive.py",
> line 167, in setup_hiveserver2
> skip=params.sysprep_skip_copy_tarballs_hdfs)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/functions/copy_tarball.py",
> line 516, in copy_to_hdfs
> replace_existing_files=replace_existing_files,
> 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 654, in action_create_on_execute
> self.action_delayed("create")
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
> line 651, in action_delayed
> self.get_hdfs_resource_executor().action_delayed(action_name, self)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
> line 354, in action_delayed
> self.action_delayed_for_nameservice(nameservice, action_name, main_resource)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
> line 380, in action_delayed_for_nameservice
> self._create_resource()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
> line 396, in _create_resource
> self._create_file(self.main_resource.resource.target,
> source=self.main_resource.resource.source, mode=self.mode)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
> line 511, in _create_file
> self.util.run_command(target, 'CREATE', method='PUT', overwrite=True,
> assertable_result=False, file_to_put=source, **kwargs)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
> line 199, in run_command
> return self._run_command(*args, **kwargs)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
> line 272, in _run_command
> raise WebHDFSCallException(err_msg, result_dict)
>
[jira] [Created] (AMBARI-24399) Components start failing with Holder DFSClient_NONMAPREDUCE does not have any open files
Vivek Rathod created AMBARI-24399:
-
Summary: Components start failing with Holder
DFSClient_NONMAPREDUCE does not have any open files
Key: AMBARI-24399
URL: https://issues.apache.org/jira/browse/AMBARI-24399
Project: Ambari
Issue Type: Bug
Affects Versions: 2.7.1
Reporter: Vivek Rathod
Fix For: 2.7.1
STR:
Add a namespace from UI. In the last step restart required services,
hiveserver2 restart fails. Although on retrying it comes back up
{code}
Traceback (most recent call last):
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 982, in restart
self.status(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_server.py",
line 79, in status
check_process_status(status_params.hive_pid)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/functions/check_process_status.py",
line 43, in check_process_status
raise ComponentIsNotRunning()
ComponentIsNotRunning
The above exception was the cause of the following exception:
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_server.py",
line 137, in
HiveServer().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 353, in execute
method(env)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 993, in restart
self.start(env, upgrade_type=upgrade_type)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_server.py",
line 50, in start
self.configure(env) # FOR SECURITY
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_server.py",
line 45, in configure
hive(name='hiveserver2')
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive.py",
line 119, in hive
setup_hiveserver2()
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive.py",
line 167, in setup_hiveserver2
skip=params.sysprep_skip_copy_tarballs_hdfs)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/functions/copy_tarball.py",
line 516, in copy_to_hdfs
replace_existing_files=replace_existing_files,
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 654, in action_create_on_execute
self.action_delayed("create")
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
line 651, in action_delayed
self.get_hdfs_resource_executor().action_delayed(action_name, self)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
line 354, in action_delayed
self.action_delayed_for_nameservice(nameservice, action_name, main_resource)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
line 380, in action_delayed_for_nameservice
self._create_resource()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
line 396, in _create_resource
self._create_file(self.main_resource.resource.target,
source=self.main_resource.resource.source, mode=self.mode)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
line 511, in _create_file
self.util.run_command(target, 'CREATE', method='PUT', overwrite=True,
assertable_result=False, file_to_put=source, **kwargs)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
line 199, in run_command
return self._run_command(*args, **kwargs)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
line 272, in _run_command
raise WebHDFSCallException(err_msg, result_dict)
resource_management.libraries.providers.hdfs_resource.WebHDFSCallException:
Execution of 'curl -sS -L -w '%\{http_code}' -X PUT --data-binary
@/usr/hdp/3.0.1.0-30/hive/hive.tar.gz -H 'Content-Type:
application/octet-stream' --negotiate -u : -k
'https://:50470/webhdfs/v1/hdp/apps/3.0.1.0-30/hive/hive.tar.gz?op=CREATE=True=444''
returned status_code=404.
{
"RemoteException": {
"exception": "FileNotFoundException",
"javaClassName": "java.io.FileNotFoundException",
"message": "File does not exist: /hdp/apps/3.0.1.0-30/hive/hive.tar.gz (inode
16450) Holder DFSClient_NONMAPREDUCE_-1764810327_120 does not have any open
files.\n\tat
[jira] [Created] (AMBARI-24260) Ambari shows success when Decommission/Recommission operations fail
Vivek Rathod created AMBARI-24260: - Summary: Ambari shows success when Decommission/Recommission operations fail Key: AMBARI-24260 URL: https://issues.apache.org/jira/browse/AMBARI-24260 Project: Ambari Issue Type: Bug Affects Versions: 2.7.0 Reporter: Vivek Rathod Fix For: 2.7.0 Ambari shows success when Decommission/Recommission operations fail If Decommission/Recommission operation fails with non zero exit code, that component still gets decommissioned/recommissioned. We need to handle this failure and not transition the state to Decommissioned/Recommissioned when the respective operation fails -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24237) UI Install: Custom Yarn Capacity Scheduler property set is missing after deploy
Vivek Rathod created AMBARI-24237:
-
Summary: UI Install: Custom Yarn Capacity Scheduler property set
is missing after deploy
Key: AMBARI-24237
URL: https://issues.apache.org/jira/browse/AMBARI-24237
Project: Ambari
Issue Type: Bug
Affects Versions: 2.7.0
Reporter: Vivek Rathod
Fix For: 2.7.0
STR:
1) During UI install,add a custom property for \{code}capacity-scheduler\{code}
property: \{code}test.capacity.scheduler=test-value\{code}
After deployment this property goes missing
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24227) Add Namespace: Hive Metastore fails to start because NN is in safemode
Vivek Rathod created AMBARI-24227:
-
Summary: Add Namespace: Hive Metastore fails to start because NN
is in safemode
Key: AMBARI-24227
URL: https://issues.apache.org/jira/browse/AMBARI-24227
Project: Ambari
Issue Type: Bug
Affects Versions: 2.7.0
Reporter: Vivek Rathod
Fix For: 2.7.0
Add Namespace: Hive Metastore fails to start because NN is in safemode
{code}
18/06/29 10:43:41 INFO retry.RetryInvocationHandler:
org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.RetriableException):
org.apache.hadoop.hdfs.server.namenode.SafeModeException: Cannot modify ACL
entries on /warehouse/tablespace/external/hive. Name node is in safe mode.
The reported blocks 0 needs additional 1791 blocks to reach the threshold
1. of total blocks 1791.
The number of live datanodes 0 has reached the minimum number 0. Safe mode will
be turned off automatically once the thresholds have been reached.
NamenodeHostName:
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkNameNodeSafeMode(FSNamesystem.java:1441)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.modifyAclEntries(FSNamesystem.java:7112)
at
org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.modifyAclEntries(NameNodeRpcServer.java:2045)
at
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.modifyAclEntries(ClientNamenodeProtocolServerSideTranslatorPB.java:1442)
at
org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:523)
at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:991)
at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:872)
at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:818)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1688)
at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2678)
Caused by: org.apache.hadoop.hdfs.server.namenode.SafeModeException: Cannot
modify ACL entries on /warehouse/tablespace/external/hive. Name node is in safe
mode.
The reported blocks 0 needs additional 1791 blocks to reach the threshold
1. of total blocks 1791.
The number of live datanodes 0 has reached the minimum number 0. Safe mode will
be turned off automatically once the thresholds have been reached.
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24213) Enabling RM HA should not be allowed if YARN is stopped
Vivek Rathod created AMBARI-24213: - Summary: Enabling RM HA should not be allowed if YARN is stopped Key: AMBARI-24213 URL: https://issues.apache.org/jira/browse/AMBARI-24213 Project: Ambari Issue Type: Bug Affects Versions: 2.7.0 Reporter: Vivek Rathod Fix For: 2.7.0 Enabling RM HA should not be allowed if YARN is stopped. There should be a popup message saying RM should be up before enabling HA, similar to NN HA wizard warning -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24212) Restart Indicators for Hdfs, Yarn, MR2 present after adding Knox
Vivek Rathod created AMBARI-24212: - Summary: Restart Indicators for Hdfs, Yarn, MR2 present after adding Knox Key: AMBARI-24212 URL: https://issues.apache.org/jira/browse/AMBARI-24212 Project: Ambari Issue Type: Bug Affects Versions: 2.7.0 Reporter: Vivek Rathod Fix For: 2.7.0 STR: 1) Create hdfs and yarn Config Groups 2) Override some hdfs-site and yarn-site configs 3) Now add Knox After adding knox, Hdfs, Yarn and MR2 have restart indicators but they should not have them On deleting knox, this issue was not reproduced -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24211) UI Install: Stackadvisor does not show GPL Error
[
https://issues.apache.org/jira/browse/AMBARI-24211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Rathod updated AMBARI-24211:
--
Description:
STR:
1) Setup ambari server and deny gpl license
\{code}gpl.license.accepted=false\{code}
2) In customize services page, add the following properties
{code}io.compression.codecs=org.apache.hadoop.io.compress.GzipCodec,org.apache.hadoop.io.compress.DefaultCodec,org.apache.hadoop.io.compress.SnappyCodec,com.hadoop.compression.lzo.LzoCodec,com.hadoop.compression.lzo.LzopCodec\{code}
{code}io.compression.codec.lzo.class =
com.hadoop.compression.lzo.LzoCodec\{code} (custom)
3) On clicking next button, it proceeds to the next step
Expected Behavior : On clicking next button, show StackAdvisor error something
like \{code}Your Ambari Server has not been configured to download LZO and
install it\{ code} and stop user from navigating to next page
was:
STR:
1) Setup ambari server and deny gpl license
\{code}gpl.license.accepted=false\{code}
2) In customize services page, add the following properties
{code:java}
io.compression.codecs =
org.apache.hadoop.io.compress.GzipCodec,org.apache.hadoop.io.compress.DefaultCodec,org.apache.hadoop.io.compress.SnappyCodec,com.hadoop.compression.lzo.LzoCodec,com.hadoop.compression.lzo.LzopCodec\{code}
{code}
io.compression.codec.lzo.class = com.hadoop.compression.lzo.LzoCodec\{code}
(custom)
3) On clicking next button, it proceeds to the next step
Expected Behavior : On clicking next button, show StackAdvisor error something
like
{code:java}
{code}
{code} Your Ambari Server has not been configured to download LZO and install
it \{code} and stop user from navigating to next page
> UI Install: Stackadvisor does not show GPL Error
>
>
> Key: AMBARI-24211
> URL: https://issues.apache.org/jira/browse/AMBARI-24211
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Vivek Rathod
>Priority: Major
> Fix For: 2.7.0
>
>
> STR:
> 1) Setup ambari server and deny gpl license
> \{code}gpl.license.accepted=false\{code}
> 2) In customize services page, add the following properties
> {code}io.compression.codecs=org.apache.hadoop.io.compress.GzipCodec,org.apache.hadoop.io.compress.DefaultCodec,org.apache.hadoop.io.compress.SnappyCodec,com.hadoop.compression.lzo.LzoCodec,com.hadoop.compression.lzo.LzopCodec\{code}
>
> {code}io.compression.codec.lzo.class =
> com.hadoop.compression.lzo.LzoCodec\{code} (custom)
>
> 3) On clicking next button, it proceeds to the next step
> Expected Behavior : On clicking next button, show StackAdvisor error
> something like \{code}Your Ambari Server has not been configured to download
> LZO and install it\{ code} and stop user from navigating to next page
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24211) UI Install: Stackadvisor does not show GPL Error
[
https://issues.apache.org/jira/browse/AMBARI-24211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Rathod updated AMBARI-24211:
--
Description:
STR:
1) Setup ambari server and deny gpl license
\{code}gpl.license.accepted=false\{code}
2) In customize services page, add the following properties
{code:java}
io.compression.codecs=org.apache.hadoop.io.compress.GzipCodec,org.apache.hadoop.io.compress.DefaultCodec,org.apache.hadoop.io.compress.SnappyCodec,com.hadoop.compression.lzo.LzoCodec,com.hadoop.compression.lzo.LzopCodec\{code}
{code}
io.compression.codec.lzo.class = com.hadoop.compression.lzo.LzoCodec\{code}
(custom)
3) On clicking next button, it proceeds to the next step
Expected Behavior : On clicking next button, show StackAdvisor error something
like "Your Ambari Server has not been configured to download LZO and install
it" and stop user from navigating to next page
was:
STR:
1) Setup ambari server and deny gpl license
\{code}gpl.license.accepted=false\{code}
2) In customize services page, add the following properties
{code:java}
io.compression.codecs=org.apache.hadoop.io.compress.GzipCodec,org.apache.hadoop.io.compress.DefaultCodec,org.apache.hadoop.io.compress.SnappyCodec,com.hadoop.compression.lzo.LzoCodec,com.hadoop.compression.lzo.LzopCodec\{code}
{code}
io.compression.codec.lzo.class = com.hadoop.compression.lzo.LzoCodec\{code}
(custom)
3) On clicking next button, it proceeds to the next step
Expected Behavior : On clicking next button, show StackAdvisor error something
like \{code}Your Ambari Server has not been configured to download LZO and
install it \{code} and stop user from navigating to next page
> UI Install: Stackadvisor does not show GPL Error
>
>
> Key: AMBARI-24211
> URL: https://issues.apache.org/jira/browse/AMBARI-24211
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Vivek Rathod
>Priority: Major
> Fix For: 2.7.0
>
>
> STR:
> 1) Setup ambari server and deny gpl license
> \{code}gpl.license.accepted=false\{code}
> 2) In customize services page, add the following properties
> {code:java}
> io.compression.codecs=org.apache.hadoop.io.compress.GzipCodec,org.apache.hadoop.io.compress.DefaultCodec,org.apache.hadoop.io.compress.SnappyCodec,com.hadoop.compression.lzo.LzoCodec,com.hadoop.compression.lzo.LzopCodec\{code}
>
> {code}
> io.compression.codec.lzo.class = com.hadoop.compression.lzo.LzoCodec\{code}
> (custom)
>
> 3) On clicking next button, it proceeds to the next step
> Expected Behavior : On clicking next button, show StackAdvisor error
> something like "Your Ambari Server has not been configured to download LZO
> and install it" and stop user from navigating to next page
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24211) UI Install: Stackadvisor does not show GPL Error
[
https://issues.apache.org/jira/browse/AMBARI-24211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Rathod updated AMBARI-24211:
--
Description:
STR:
1) Setup ambari server and deny gpl license
\{code}gpl.license.accepted=false\{code}
2) In customize services page, add the following properties
{code:java}
io.compression.codecs=org.apache.hadoop.io.compress.GzipCodec,org.apache.hadoop.io.compress.DefaultCodec,org.apache.hadoop.io.compress.SnappyCodec,com.hadoop.compression.lzo.LzoCodec,com.hadoop.compression.lzo.LzopCodec\{code}
{code}
io.compression.codec.lzo.class = com.hadoop.compression.lzo.LzoCodec\{code}
(custom)
3) On clicking next button, it proceeds to the next step
Expected Behavior : On clicking next button, show StackAdvisor error something
like \{code}Your Ambari Server has not been configured to download LZO and
install it \{code} and stop user from navigating to next page
was:
STR:
1) Setup ambari server and deny gpl license
\{code}gpl.license.accepted=false\{code}
2) In customize services page, add the following properties
{code}io.compression.codecs=org.apache.hadoop.io.compress.GzipCodec,org.apache.hadoop.io.compress.DefaultCodec,org.apache.hadoop.io.compress.SnappyCodec,com.hadoop.compression.lzo.LzoCodec,com.hadoop.compression.lzo.LzopCodec\{code}
{code}io.compression.codec.lzo.class =
com.hadoop.compression.lzo.LzoCodec\{code} (custom)
3) On clicking next button, it proceeds to the next step
Expected Behavior : On clicking next button, show StackAdvisor error something
like \{code}Your Ambari Server has not been configured to download LZO and
install it\{ code} and stop user from navigating to next page
> UI Install: Stackadvisor does not show GPL Error
>
>
> Key: AMBARI-24211
> URL: https://issues.apache.org/jira/browse/AMBARI-24211
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Vivek Rathod
>Priority: Major
> Fix For: 2.7.0
>
>
> STR:
> 1) Setup ambari server and deny gpl license
> \{code}gpl.license.accepted=false\{code}
> 2) In customize services page, add the following properties
> {code:java}
> io.compression.codecs=org.apache.hadoop.io.compress.GzipCodec,org.apache.hadoop.io.compress.DefaultCodec,org.apache.hadoop.io.compress.SnappyCodec,com.hadoop.compression.lzo.LzoCodec,com.hadoop.compression.lzo.LzopCodec\{code}
>
> {code}
> io.compression.codec.lzo.class = com.hadoop.compression.lzo.LzoCodec\{code}
> (custom)
>
> 3) On clicking next button, it proceeds to the next step
> Expected Behavior : On clicking next button, show StackAdvisor error
> something like \{code}Your Ambari Server has not been configured to download
> LZO and install it \{code} and stop user from navigating to next page
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24211) UI Install: Stackadvisor does not show GPL Error
[
https://issues.apache.org/jira/browse/AMBARI-24211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Rathod updated AMBARI-24211:
--
Description:
STR:
1) Setup ambari server and deny gpl license
\{code}gpl.license.accepted=false\{code}
2) In customize services page, add the following properties
{code:java}
io.compression.codecs =
org.apache.hadoop.io.compress.GzipCodec,org.apache.hadoop.io.compress.DefaultCodec,org.apache.hadoop.io.compress.SnappyCodec,com.hadoop.compression.lzo.LzoCodec,com.hadoop.compression.lzo.LzopCodec\{code}
{code}
io.compression.codec.lzo.class = com.hadoop.compression.lzo.LzoCodec\{code}
(custom)
3) On clicking next button, it proceeds to the next step
Expected Behavior : On clicking next button, show StackAdvisor error something
like
{code:java}
{code}
{code} Your Ambari Server has not been configured to download LZO and install
it \{code} and stop user from navigating to next page
was:
STR:
1) Setup ambari server and deny gpl license
\{code}gpl.license.accepted=false\{code}
2) In customize services page, add the following properties
{code:java}
io.compression.codecs =
org.apache.hadoop.io.compress.GzipCodec,org.apache.hadoop.io.compress.DefaultCodec,org.apache.hadoop.io.compress.SnappyCodec,com.hadoop.compression.lzo.LzoCodec,com.hadoop.compression.lzo.LzopCodec\{code}
{code}
io.compression.codec.lzo.class = com.hadoop.compression.lzo.LzoCodec\{code}
(custom)
3) On clicking next button, it proceeds to the next step
Expected Behavior : On clicking next button, show StackAdvisor error something
like
{code}Your Ambari Server has not been configured to download LZO and install it
\{code} and stop user from navigating to next page
> UI Install: Stackadvisor does not show GPL Error
>
>
> Key: AMBARI-24211
> URL: https://issues.apache.org/jira/browse/AMBARI-24211
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Vivek Rathod
>Priority: Major
> Fix For: 2.7.0
>
>
> STR:
> 1) Setup ambari server and deny gpl license
> \{code}gpl.license.accepted=false\{code}
> 2) In customize services page, add the following properties
> {code:java}
> io.compression.codecs =
> org.apache.hadoop.io.compress.GzipCodec,org.apache.hadoop.io.compress.DefaultCodec,org.apache.hadoop.io.compress.SnappyCodec,com.hadoop.compression.lzo.LzoCodec,com.hadoop.compression.lzo.LzopCodec\{code}
> {code}
> io.compression.codec.lzo.class = com.hadoop.compression.lzo.LzoCodec\{code}
> (custom)
> 3) On clicking next button, it proceeds to the next step
> Expected Behavior : On clicking next button, show StackAdvisor error
> something like
> {code:java}
> {code}
> {code} Your Ambari Server has not been configured to download LZO and install
> it \{code} and stop user from navigating to next page
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24211) UI Install: Stackadvisor does not show GPL Error
Vivek Rathod created AMBARI-24211:
-
Summary: UI Install: Stackadvisor does not show GPL Error
Key: AMBARI-24211
URL: https://issues.apache.org/jira/browse/AMBARI-24211
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.7.0
Reporter: Vivek Rathod
Fix For: 2.7.0
STR:
1) Setup ambari server and deny gpl license
\{code}gpl.license.accepted=false\{code}
2) In customize services page, add the following properties
{code}io.compression.codecs =
org.apache.hadoop.io.compress.GzipCodec,org.apache.hadoop.io.compress.DefaultCodec,org.apache.hadoop.io.compress.SnappyCodec,com.hadoop.compression.lzo.LzoCodec,com.hadoop.compression.lzo.LzopCodec\{code}
{code}io.compression.codec.lzo.class =
com.hadoop.compression.lzo.LzoCodec\{code} (custom)
3) On clicking next button, it proceeds to the next step
Expected Behavior : On clicking next button, show StackAdvisor error something
like \{code}Your Ambari Server has not been configured to download LZO and
install it\{code} and stop user from navigating to next page
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24211) UI Install: Stackadvisor does not show GPL Error
[
https://issues.apache.org/jira/browse/AMBARI-24211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Rathod updated AMBARI-24211:
--
Description:
STR:
1) Setup ambari server and deny gpl license
\{code}gpl.license.accepted=false\{code}
2) In customize services page, add the following properties
{code:java}
io.compression.codecs =
org.apache.hadoop.io.compress.GzipCodec,org.apache.hadoop.io.compress.DefaultCodec,org.apache.hadoop.io.compress.SnappyCodec,com.hadoop.compression.lzo.LzoCodec,com.hadoop.compression.lzo.LzopCodec\{code}
{code}
io.compression.codec.lzo.class = com.hadoop.compression.lzo.LzoCodec\{code}
(custom)
3) On clicking next button, it proceeds to the next step
Expected Behavior : On clicking next button, show StackAdvisor error something
like
{code}Your Ambari Server has not been configured to download LZO and install it
\{code} and stop user from navigating to next page
was:
STR:
1) Setup ambari server and deny gpl license
\{code}gpl.license.accepted=false\{code}
2) In customize services page, add the following properties
{code}io.compression.codecs =
org.apache.hadoop.io.compress.GzipCodec,org.apache.hadoop.io.compress.DefaultCodec,org.apache.hadoop.io.compress.SnappyCodec,com.hadoop.compression.lzo.LzoCodec,com.hadoop.compression.lzo.LzopCodec\{code}
{code}io.compression.codec.lzo.class =
com.hadoop.compression.lzo.LzoCodec\{code} (custom)
3) On clicking next button, it proceeds to the next step
Expected Behavior : On clicking next button, show StackAdvisor error something
like \{code}Your Ambari Server has not been configured to download LZO and
install it\{code} and stop user from navigating to next page
> UI Install: Stackadvisor does not show GPL Error
>
>
> Key: AMBARI-24211
> URL: https://issues.apache.org/jira/browse/AMBARI-24211
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Vivek Rathod
>Priority: Major
> Fix For: 2.7.0
>
>
> STR:
> 1) Setup ambari server and deny gpl license
> \{code}gpl.license.accepted=false\{code}
> 2) In customize services page, add the following properties
> {code:java}
> io.compression.codecs =
> org.apache.hadoop.io.compress.GzipCodec,org.apache.hadoop.io.compress.DefaultCodec,org.apache.hadoop.io.compress.SnappyCodec,com.hadoop.compression.lzo.LzoCodec,com.hadoop.compression.lzo.LzopCodec\{code}
> {code}
> io.compression.codec.lzo.class = com.hadoop.compression.lzo.LzoCodec\{code}
> (custom)
> 3) On clicking next button, it proceeds to the next step
> Expected Behavior : On clicking next button, show StackAdvisor error
> something like
> {code}Your Ambari Server has not been configured to download LZO and install
> it \{code} and stop user from navigating to next page
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24173) UI Deploy: Cannot deploy cluster with Config Groups
Vivek Rathod created AMBARI-24173:
-
Summary: UI Deploy: Cannot deploy cluster with Config Groups
Key: AMBARI-24173
URL: https://issues.apache.org/jira/browse/AMBARI-24173
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Vivek Rathod
Fix For: 2.7.0
UI Deploy: Cannot deploy cluster with Config Groups
STR:
1) Install cluster via UI
2) On Customize services page, create a Config Group and add some hosts to it
3) Click Deploy
{code}
2018-06-22 23:46:28,174 ERROR [ambari-client-thread-505]
AbstractResourceProvider:353 - Caught AmbariException when modifying a resource
org.apache.ambari.server.AmbariException: Config group not found, clusterName =
cl1, groupId = 1529709098419
at
org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.updateConfigGroups(ConfigGroupResourceProvider.java:683)
at
org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.access$300(ConfigGroupResourceProvider.java:76)
at
org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider$4.invoke(ConfigGroupResourceProvider.java:351)
at
org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider$4.invoke(ConfigGroupResourceProvider.java:348)
at
org.apache.ambari.server.controller.internal.AbstractResourceProvider.invokeWithRetry(AbstractResourceProvider.java:465)
at
org.apache.ambari.server.controller.internal.AbstractResourceProvider.modifyResources(AbstractResourceProvider.java:346)
at
org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.updateResources(ConfigGroupResourceProvider.java:348)
at
org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.updateResourcesAuthorized(ConfigGroupResourceProvider.java:251)
at
org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.updateResources(AbstractAuthorizedResourceProvider.java:312)
at
org.apache.ambari.server.controller.internal.ClusterControllerImpl.updateResources(ClusterControllerImpl.java:317)
at
org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.update(PersistenceManagerImpl.java:125)
at
org.apache.ambari.server.api.handlers.UpdateHandler.persist(UpdateHandler.java:46)
at
org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:68)
at
org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
at
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:163)
at
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:127)
at
org.apache.ambari.server.api.services.ConfigGroupService.updateConfigGroup(ConfigGroupService.java:186)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
at
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
at
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
at
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
[jira] [Created] (AMBARI-23970) Broken RCO in Add Namespace Wizards Restart Required Services, Hiveserver fails to start because DN's are not up
Vivek Rathod created AMBARI-23970:
-
Summary: Broken RCO in Add Namespace Wizards Restart Required
Services, Hiveserver fails to start because DN's are not up
Key: AMBARI-23970
URL: https://issues.apache.org/jira/browse/AMBARI-23970
Project: Ambari
Issue Type: Bug
Affects Versions: 2.7.0
Reporter: Vivek Rathod
Fix For: 2.7.0
Broken RCO in Add Namespace Wizards Restart Required Services, Hiveserver fails
to start because DN's are not up
{code}
{ "RemoteException": {"exception": "IOException", "javaClassName":
"java.io.IOException", "message": "Failed to find datanode, suggest to
check cluster health. excludeDatanodes=null" }
}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23815) NN Federation wizard: Restart Required Services should not restart JN and ZKFC
Vivek Rathod created AMBARI-23815:
-
Summary: NN Federation wizard: Restart Required Services should
not restart JN and ZKFC
Key: AMBARI-23815
URL: https://issues.apache.org/jira/browse/AMBARI-23815
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.7.0
Reporter: Vivek Rathod
Fix For: 2.7.0
STR:
Add namespace from UI. In the Restart All Services operation RM fails to start
{code}
Traceback (most recent call last):
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/functions/decorator.py",
line 54, in wrapper
return function(*args, **kwargs)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/resourcemanager.py",
line 244, in wait_for_dfs_directory_created
raise Fail("DFS directory '" + dir_path + "' does not exist !")
Fail: DFS directory '/ats/done/' does not exist !
The above exception was the cause of the following exception:
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/resourcemanager.py",
line 261, in
Resourcemanager().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 353, in execute
method(env)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 982, in restart
self.start(env, upgrade_type=upgrade_type)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/resourcemanager.py",
line 142, in start
self.wait_for_dfs_directories_created(params.entity_groupfs_store_dir,
params.entity_groupfs_active_dir)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/resourcemanager.py",
line 211, in wait_for_dfs_directories_created
self.wait_for_dfs_directory_created(dir_path, ignored_dfs_dirs)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/functions/decorator.py",
line 62, in wrapper
return function(*args, **kwargs)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/resourcemanager.py",
line 244, in wait_for_dfs_directory_created
raise Fail("DFS directory '" + dir_path + "' does not exist !")
resource_management.core.exceptions.Fail: DFS directory '/ats/done/' does not
exist !
{code}
But after closing the wizard and starting all the services it started.
Also restarting history server failed on another host
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/historyserver.py",
line 134, in
HistoryServer().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 353, in execute
method(env)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 982, in restart
self.start(env, upgrade_type=upgrade_type)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/historyserver.py",
line 95, in start
skip=params.sysprep_skip_copy_tarballs_hdfs)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/functions/copy_tarball.py",
line 502, in copy_to_hdfs
replace_existing_files=replace_existing_files,
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 627, in action_create_on_execute
self.action_delayed("create")
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
line 624, in action_delayed
self.get_hdfs_resource_executor().action_delayed(action_name, self)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
line 333, in action_delayed
self.action_delayed_for_nameservice(nameservice, action_name, main_resource)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
line 359, in action_delayed_for_nameservice
self._create_resource()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
line 375, in _create_resource
self._create_file(self.main_resource.resource.target,
source=self.main_resource.resource.source, mode=self.mode)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
line 490, in _create_file
self.util.run_command(target, 'CREATE', method='PUT', overwrite=True,
assertable_result=False, file_to_put=source, **kwargs)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
line 178, in run_command
return
[jira] [Updated] (AMBARI-23754) UI Issues for HDFS Metrics when having multiple namespaces
[ https://issues.apache.org/jira/browse/AMBARI-23754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod updated AMBARI-23754: -- Summary: UI Issues for HDFS Metrics when having multiple namespaces (was: New Widgets are displayed twice on HDFS summary page) > UI Issues for HDFS Metrics when having multiple namespaces > -- > > Key: AMBARI-23754 > URL: https://issues.apache.org/jira/browse/AMBARI-23754 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Priority: Major > Fix For: 2.7.0 > > Attachments: Issue #1.png, Issue #2 Create custom widget for > Namespace.png, Issue #2.png, Issue #3 -1.png, Issue #3 -2.png, Screen Shot > 2018-05-02 at 4.10.46 PM.png, Screen Shot 2018-05-02 at 4.20.20 PM.png, > Screen Shot 2018-05-02 at 4.21.31 PM.png, image-2018-05-07-11-08-12-178.png, > image-2018-05-07-11-08-25-003.png, image-2018-05-07-11-08-25-040.png, > image-2018-05-07-11-08-35-838.png, image-2018-05-07-11-08-35-880.png > > > Issue #1) > On Hdfs metrics page, add a widget. That is displayed in the top panel for > the default namespace and then at the bottom for the namespace selected > (ns1,ns2 or All) > Should the widget on the top show the aggregate metrics instead of metrics > for just default namespace? > OR > Should they not appear in the top section and be displayed only for the > namespace selected at the bottom? > !image-2018-05-07-11-08-12-178.png! > Issue #2) > Create custom widget for a namespace > No Namespace name next to the custom widget > !image-2018-05-07-11-08-25-040.png!!image-2018-05-07-11-08-25-003.png! > > Issue #3) > Duplicate widgets in the Browse Widgets window where there are multiple > namespaces > !image-2018-05-07-11-08-35-880.png!!image-2018-05-07-11-08-35-838.png! > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23754) New Widgets are displayed twice on HDFS summary page
[ https://issues.apache.org/jira/browse/AMBARI-23754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod updated AMBARI-23754: -- Attachment: image-2018-05-07-11-08-12-178.png > New Widgets are displayed twice on HDFS summary page > > > Key: AMBARI-23754 > URL: https://issues.apache.org/jira/browse/AMBARI-23754 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Priority: Major > Fix For: 2.7.0 > > Attachments: Issue #1.png, Issue #2 Create custom widget for > Namespace.png, Issue #2.png, Issue #3 -1.png, Issue #3 -2.png, Screen Shot > 2018-05-02 at 4.10.46 PM.png, Screen Shot 2018-05-02 at 4.20.20 PM.png, > Screen Shot 2018-05-02 at 4.21.31 PM.png, image-2018-05-07-11-08-12-178.png, > image-2018-05-07-11-08-25-003.png, image-2018-05-07-11-08-25-040.png, > image-2018-05-07-11-08-35-838.png, image-2018-05-07-11-08-35-880.png > > > Issue #1) > On Hdfs metrics page, add a widget. That is displayed in the top panel for > the default namespace and then at the bottom for the namespace selected > (ns1,ns2 or All) > Should the widget on the top show the aggregate metrics instead of metrics > for just default namespace? > OR > Should they not appear in the top section and be displayed only for the > namespace selected at the bottom? > [!Issue > #1.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155237/155237_Issue+%231.png] > Issue #2) > Create custom widget for a namespace > No Namespace name next to the custom widget > [!Issue > #2.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155239/155239_Issue+%232.png] > [!Issue #2 Create custom widget for > Namespace.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155238/155238_Issue+%232+Create+custom+widget+for+Namespace.png] > Issue #3) > Duplicate widgets in the Browse Widgets window where there are multiple > namespaces > [!Issue #3 > -2.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155240/155240_Issue+%233+-2.png] > [!Issue #3 > -1.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155241/155241_Issue+%233+-1.png] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23754) New Widgets are displayed twice on HDFS summary page
[ https://issues.apache.org/jira/browse/AMBARI-23754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod updated AMBARI-23754: -- Attachment: image-2018-05-07-11-08-35-838.png > New Widgets are displayed twice on HDFS summary page > > > Key: AMBARI-23754 > URL: https://issues.apache.org/jira/browse/AMBARI-23754 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Priority: Major > Fix For: 2.7.0 > > Attachments: Issue #1.png, Issue #2 Create custom widget for > Namespace.png, Issue #2.png, Issue #3 -1.png, Issue #3 -2.png, Screen Shot > 2018-05-02 at 4.10.46 PM.png, Screen Shot 2018-05-02 at 4.20.20 PM.png, > Screen Shot 2018-05-02 at 4.21.31 PM.png, image-2018-05-07-11-08-12-178.png, > image-2018-05-07-11-08-25-003.png, image-2018-05-07-11-08-25-040.png, > image-2018-05-07-11-08-35-838.png, image-2018-05-07-11-08-35-880.png > > > Issue #1) > On Hdfs metrics page, add a widget. That is displayed in the top panel for > the default namespace and then at the bottom for the namespace selected > (ns1,ns2 or All) > Should the widget on the top show the aggregate metrics instead of metrics > for just default namespace? > OR > Should they not appear in the top section and be displayed only for the > namespace selected at the bottom? > [!Issue > #1.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155237/155237_Issue+%231.png] > Issue #2) > Create custom widget for a namespace > No Namespace name next to the custom widget > [!Issue > #2.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155239/155239_Issue+%232.png] > [!Issue #2 Create custom widget for > Namespace.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155238/155238_Issue+%232+Create+custom+widget+for+Namespace.png] > Issue #3) > Duplicate widgets in the Browse Widgets window where there are multiple > namespaces > [!Issue #3 > -2.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155240/155240_Issue+%233+-2.png] > [!Issue #3 > -1.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155241/155241_Issue+%233+-1.png] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23754) New Widgets are displayed twice on HDFS summary page
[ https://issues.apache.org/jira/browse/AMBARI-23754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod updated AMBARI-23754: -- Description: Issue #1) On Hdfs metrics page, add a widget. That is displayed in the top panel for the default namespace and then at the bottom for the namespace selected (ns1,ns2 or All) Should the widget on the top show the aggregate metrics instead of metrics for just default namespace? OR Should they not appear in the top section and be displayed only for the namespace selected at the bottom? !image-2018-05-07-11-08-12-178.png! Issue #2) Create custom widget for a namespace No Namespace name next to the custom widget !image-2018-05-07-11-08-25-040.png!!image-2018-05-07-11-08-25-003.png! Issue #3) Duplicate widgets in the Browse Widgets window where there are multiple namespaces !image-2018-05-07-11-08-35-880.png!!image-2018-05-07-11-08-35-838.png! was: Issue #1) On Hdfs metrics page, add a widget. That is displayed in the top panel for the default namespace and then at the bottom for the namespace selected (ns1,ns2 or All) Should the widget on the top show the aggregate metrics instead of metrics for just default namespace? OR Should they not appear in the top section and be displayed only for the namespace selected at the bottom? [!Issue #1.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155237/155237_Issue+%231.png] Issue #2) Create custom widget for a namespace No Namespace name next to the custom widget [!Issue #2.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155239/155239_Issue+%232.png] [!Issue #2 Create custom widget for Namespace.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155238/155238_Issue+%232+Create+custom+widget+for+Namespace.png] Issue #3) Duplicate widgets in the Browse Widgets window where there are multiple namespaces [!Issue #3 -2.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155240/155240_Issue+%233+-2.png] [!Issue #3 -1.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155241/155241_Issue+%233+-1.png] > New Widgets are displayed twice on HDFS summary page > > > Key: AMBARI-23754 > URL: https://issues.apache.org/jira/browse/AMBARI-23754 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Priority: Major > Fix For: 2.7.0 > > Attachments: Issue #1.png, Issue #2 Create custom widget for > Namespace.png, Issue #2.png, Issue #3 -1.png, Issue #3 -2.png, Screen Shot > 2018-05-02 at 4.10.46 PM.png, Screen Shot 2018-05-02 at 4.20.20 PM.png, > Screen Shot 2018-05-02 at 4.21.31 PM.png, image-2018-05-07-11-08-12-178.png, > image-2018-05-07-11-08-25-003.png, image-2018-05-07-11-08-25-040.png, > image-2018-05-07-11-08-35-838.png, image-2018-05-07-11-08-35-880.png > > > Issue #1) > On Hdfs metrics page, add a widget. That is displayed in the top panel for > the default namespace and then at the bottom for the namespace selected > (ns1,ns2 or All) > Should the widget on the top show the aggregate metrics instead of metrics > for just default namespace? > OR > Should they not appear in the top section and be displayed only for the > namespace selected at the bottom? > !image-2018-05-07-11-08-12-178.png! > Issue #2) > Create custom widget for a namespace > No Namespace name next to the custom widget > !image-2018-05-07-11-08-25-040.png!!image-2018-05-07-11-08-25-003.png! > > Issue #3) > Duplicate widgets in the Browse Widgets window where there are multiple > namespaces > !image-2018-05-07-11-08-35-880.png!!image-2018-05-07-11-08-35-838.png! > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23754) New Widgets are displayed twice on HDFS summary page
[ https://issues.apache.org/jira/browse/AMBARI-23754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod updated AMBARI-23754: -- Attachment: image-2018-05-07-11-08-25-040.png > New Widgets are displayed twice on HDFS summary page > > > Key: AMBARI-23754 > URL: https://issues.apache.org/jira/browse/AMBARI-23754 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Priority: Major > Fix For: 2.7.0 > > Attachments: Issue #1.png, Issue #2 Create custom widget for > Namespace.png, Issue #2.png, Issue #3 -1.png, Issue #3 -2.png, Screen Shot > 2018-05-02 at 4.10.46 PM.png, Screen Shot 2018-05-02 at 4.20.20 PM.png, > Screen Shot 2018-05-02 at 4.21.31 PM.png, image-2018-05-07-11-08-12-178.png, > image-2018-05-07-11-08-25-003.png, image-2018-05-07-11-08-25-040.png, > image-2018-05-07-11-08-35-838.png, image-2018-05-07-11-08-35-880.png > > > Issue #1) > On Hdfs metrics page, add a widget. That is displayed in the top panel for > the default namespace and then at the bottom for the namespace selected > (ns1,ns2 or All) > Should the widget on the top show the aggregate metrics instead of metrics > for just default namespace? > OR > Should they not appear in the top section and be displayed only for the > namespace selected at the bottom? > [!Issue > #1.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155237/155237_Issue+%231.png] > Issue #2) > Create custom widget for a namespace > No Namespace name next to the custom widget > [!Issue > #2.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155239/155239_Issue+%232.png] > [!Issue #2 Create custom widget for > Namespace.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155238/155238_Issue+%232+Create+custom+widget+for+Namespace.png] > Issue #3) > Duplicate widgets in the Browse Widgets window where there are multiple > namespaces > [!Issue #3 > -2.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155240/155240_Issue+%233+-2.png] > [!Issue #3 > -1.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155241/155241_Issue+%233+-1.png] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23754) New Widgets are displayed twice on HDFS summary page
[ https://issues.apache.org/jira/browse/AMBARI-23754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod updated AMBARI-23754: -- Attachment: image-2018-05-07-11-08-25-003.png > New Widgets are displayed twice on HDFS summary page > > > Key: AMBARI-23754 > URL: https://issues.apache.org/jira/browse/AMBARI-23754 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Priority: Major > Fix For: 2.7.0 > > Attachments: Issue #1.png, Issue #2 Create custom widget for > Namespace.png, Issue #2.png, Issue #3 -1.png, Issue #3 -2.png, Screen Shot > 2018-05-02 at 4.10.46 PM.png, Screen Shot 2018-05-02 at 4.20.20 PM.png, > Screen Shot 2018-05-02 at 4.21.31 PM.png, image-2018-05-07-11-08-12-178.png, > image-2018-05-07-11-08-25-003.png, image-2018-05-07-11-08-25-040.png, > image-2018-05-07-11-08-35-838.png, image-2018-05-07-11-08-35-880.png > > > Issue #1) > On Hdfs metrics page, add a widget. That is displayed in the top panel for > the default namespace and then at the bottom for the namespace selected > (ns1,ns2 or All) > Should the widget on the top show the aggregate metrics instead of metrics > for just default namespace? > OR > Should they not appear in the top section and be displayed only for the > namespace selected at the bottom? > [!Issue > #1.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155237/155237_Issue+%231.png] > Issue #2) > Create custom widget for a namespace > No Namespace name next to the custom widget > [!Issue > #2.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155239/155239_Issue+%232.png] > [!Issue #2 Create custom widget for > Namespace.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155238/155238_Issue+%232+Create+custom+widget+for+Namespace.png] > Issue #3) > Duplicate widgets in the Browse Widgets window where there are multiple > namespaces > [!Issue #3 > -2.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155240/155240_Issue+%233+-2.png] > [!Issue #3 > -1.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155241/155241_Issue+%233+-1.png] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23754) New Widgets are displayed twice on HDFS summary page
[ https://issues.apache.org/jira/browse/AMBARI-23754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod updated AMBARI-23754: -- Attachment: image-2018-05-07-11-08-35-880.png > New Widgets are displayed twice on HDFS summary page > > > Key: AMBARI-23754 > URL: https://issues.apache.org/jira/browse/AMBARI-23754 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Priority: Major > Fix For: 2.7.0 > > Attachments: Issue #1.png, Issue #2 Create custom widget for > Namespace.png, Issue #2.png, Issue #3 -1.png, Issue #3 -2.png, Screen Shot > 2018-05-02 at 4.10.46 PM.png, Screen Shot 2018-05-02 at 4.20.20 PM.png, > Screen Shot 2018-05-02 at 4.21.31 PM.png, image-2018-05-07-11-08-12-178.png, > image-2018-05-07-11-08-25-003.png, image-2018-05-07-11-08-25-040.png, > image-2018-05-07-11-08-35-838.png, image-2018-05-07-11-08-35-880.png > > > Issue #1) > On Hdfs metrics page, add a widget. That is displayed in the top panel for > the default namespace and then at the bottom for the namespace selected > (ns1,ns2 or All) > Should the widget on the top show the aggregate metrics instead of metrics > for just default namespace? > OR > Should they not appear in the top section and be displayed only for the > namespace selected at the bottom? > [!Issue > #1.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155237/155237_Issue+%231.png] > Issue #2) > Create custom widget for a namespace > No Namespace name next to the custom widget > [!Issue > #2.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155239/155239_Issue+%232.png] > [!Issue #2 Create custom widget for > Namespace.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155238/155238_Issue+%232+Create+custom+widget+for+Namespace.png] > Issue #3) > Duplicate widgets in the Browse Widgets window where there are multiple > namespaces > [!Issue #3 > -2.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155240/155240_Issue+%233+-2.png] > [!Issue #3 > -1.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155241/155241_Issue+%233+-1.png] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23754) New Widgets are displayed twice on HDFS summary page
[ https://issues.apache.org/jira/browse/AMBARI-23754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod updated AMBARI-23754: -- Description: Issue #1) On Hdfs metrics page, add a widget. That is displayed in the top panel for the default namespace and then at the bottom for the namespace selected (ns1,ns2 or All) Should the widget on the top show the aggregate metrics instead of metrics for just default namespace? OR Should they not appear in the top section and be displayed only for the namespace selected at the bottom? [!Issue #1.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155237/155237_Issue+%231.png] Issue #2) Create custom widget for a namespace No Namespace name next to the custom widget [!Issue #2.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155239/155239_Issue+%232.png] [!Issue #2 Create custom widget for Namespace.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155238/155238_Issue+%232+Create+custom+widget+for+Namespace.png] Issue #3) Duplicate widgets in the Browse Widgets window where there are multiple namespaces [!Issue #3 -2.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155240/155240_Issue+%233+-2.png] [!Issue #3 -1.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155241/155241_Issue+%233+-1.png] was: New Widgets are displayed twice on HDFS summary page STR: On Hdfs metrics page, add a widget. That is displayed in the top panel for the default namespace and then at the bottom for the namespace selected (ns1,ns2 or All) Should the widget on the top show the aggregate metrics instead of metrics for just default namespace? OR Should they not appear in the top section and be displayed only for the namespace selected at the bottom? Another issue: Found one more issue. On creating a new Widget for a namespace, it does not have the namespace tag next to it. It is also not filtered by the namespace filter. In the screenshots below, I created a widget "test" > New Widgets are displayed twice on HDFS summary page > > > Key: AMBARI-23754 > URL: https://issues.apache.org/jira/browse/AMBARI-23754 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Priority: Major > Fix For: 2.7.0 > > Attachments: Issue #1.png, Issue #2 Create custom widget for > Namespace.png, Issue #2.png, Issue #3 -1.png, Issue #3 -2.png, Screen Shot > 2018-05-02 at 4.10.46 PM.png, Screen Shot 2018-05-02 at 4.20.20 PM.png, > Screen Shot 2018-05-02 at 4.21.31 PM.png > > > Issue #1) > On Hdfs metrics page, add a widget. That is displayed in the top panel for > the default namespace and then at the bottom for the namespace selected > (ns1,ns2 or All) > Should the widget on the top show the aggregate metrics instead of metrics > for just default namespace? > OR > Should they not appear in the top section and be displayed only for the > namespace selected at the bottom? > [!Issue > #1.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155237/155237_Issue+%231.png] > Issue #2) > Create custom widget for a namespace > No Namespace name next to the custom widget > [!Issue > #2.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155239/155239_Issue+%232.png] > [!Issue #2 Create custom widget for > Namespace.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155238/155238_Issue+%232+Create+custom+widget+for+Namespace.png] > Issue #3) > Duplicate widgets in the Browse Widgets window where there are multiple > namespaces > [!Issue #3 > -2.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155240/155240_Issue+%233+-2.png] > [!Issue #3 > -1.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155241/155241_Issue+%233+-1.png] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23754) New Widgets are displayed twice on HDFS summary page
[ https://issues.apache.org/jira/browse/AMBARI-23754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod updated AMBARI-23754: -- Attachment: Issue #3 -2.png Issue #3 -1.png Issue #2 Create custom widget for Namespace.png Issue #2.png Issue #1.png > New Widgets are displayed twice on HDFS summary page > > > Key: AMBARI-23754 > URL: https://issues.apache.org/jira/browse/AMBARI-23754 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Priority: Major > Fix For: 2.7.0 > > Attachments: Issue #1.png, Issue #2 Create custom widget for > Namespace.png, Issue #2.png, Issue #3 -1.png, Issue #3 -2.png, Screen Shot > 2018-05-02 at 4.10.46 PM.png, Screen Shot 2018-05-02 at 4.20.20 PM.png, > Screen Shot 2018-05-02 at 4.21.31 PM.png > > > Issue #1) > On Hdfs metrics page, add a widget. That is displayed in the top panel for > the default namespace and then at the bottom for the namespace selected > (ns1,ns2 or All) > Should the widget on the top show the aggregate metrics instead of metrics > for just default namespace? > OR > Should they not appear in the top section and be displayed only for the > namespace selected at the bottom? > [!Issue > #1.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155237/155237_Issue+%231.png] > Issue #2) > Create custom widget for a namespace > No Namespace name next to the custom widget > [!Issue > #2.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155239/155239_Issue+%232.png] > [!Issue #2 Create custom widget for > Namespace.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155238/155238_Issue+%232+Create+custom+widget+for+Namespace.png] > Issue #3) > Duplicate widgets in the Browse Widgets window where there are multiple > namespaces > [!Issue #3 > -2.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155240/155240_Issue+%233+-2.png] > [!Issue #3 > -1.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/155241/155241_Issue+%233+-1.png] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23754) New Widgets are displayed twice on HDFS summary page
[ https://issues.apache.org/jira/browse/AMBARI-23754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod updated AMBARI-23754: -- Description: New Widgets are displayed twice on HDFS summary page STR: On Hdfs metrics page, add a widget. That is displayed in the top panel for the default namespace and then at the bottom for the namespace selected (ns1,ns2 or All) Should the widget on the top show the aggregate metrics instead of metrics for just default namespace? OR Should they not appear in the top section and be displayed only for the namespace selected at the bottom? Another issue: Found one more issue. On creating a new Widget for a namespace, it does not have the namespace tag next to it. It is also not filtered by the namespace filter. In the screenshots below, I created a widget "test" > New Widgets are displayed twice on HDFS summary page > > > Key: AMBARI-23754 > URL: https://issues.apache.org/jira/browse/AMBARI-23754 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Priority: Major > Fix For: 2.7.0 > > Attachments: Screen Shot 2018-05-02 at 4.10.46 PM.png, Screen Shot > 2018-05-02 at 4.20.20 PM.png, Screen Shot 2018-05-02 at 4.21.31 PM.png > > > New Widgets are displayed twice on HDFS summary page > STR: On Hdfs metrics page, add a widget. That is displayed in the top panel > for the default namespace and then at the bottom for the namespace selected > (ns1,ns2 or All) > Should the widget on the top show the aggregate metrics instead of metrics > for just default namespace? > OR > Should they not appear in the top section and be displayed only for the > namespace selected at the bottom? > > > > Another issue: > Found one more issue. On creating a new Widget for a namespace, it does not > have the namespace tag next to it. It is also not filtered by the namespace > filter. In the screenshots below, I created a widget "test" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23754) New Widgets are displayed twice on HDFS summary page
Vivek Rathod created AMBARI-23754: - Summary: New Widgets are displayed twice on HDFS summary page Key: AMBARI-23754 URL: https://issues.apache.org/jira/browse/AMBARI-23754 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Environment: New Widgets are displayed twice on HDFS summary page STR: On Hdfs metrics page, add a widget. That is displayed in the top panel for the default namespace and then at the bottom for the namespace selected (ns1,ns2 or All) Should the widget on the top show the aggregate metrics instead of metrics for just default namespace? OR Should they not appear in the top section and be displayed only for the namespace selected at the bottom? Another issue: Found one more issue. On creating a new Widget for a namespace, it does not have the namespace tag next to it. It is also not filtered by the namespace filter. In the screenshots below, I created a widget "test" Reporter: Vivek Rathod Fix For: 2.7.0 Attachments: Screen Shot 2018-05-02 at 4.10.46 PM.png, Screen Shot 2018-05-02 at 4.20.20 PM.png, Screen Shot 2018-05-02 at 4.21.31 PM.png -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23754) New Widgets are displayed twice on HDFS summary page
[ https://issues.apache.org/jira/browse/AMBARI-23754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod updated AMBARI-23754: -- Environment: (was: New Widgets are displayed twice on HDFS summary page STR: On Hdfs metrics page, add a widget. That is displayed in the top panel for the default namespace and then at the bottom for the namespace selected (ns1,ns2 or All) Should the widget on the top show the aggregate metrics instead of metrics for just default namespace? OR Should they not appear in the top section and be displayed only for the namespace selected at the bottom? Another issue: Found one more issue. On creating a new Widget for a namespace, it does not have the namespace tag next to it. It is also not filtered by the namespace filter. In the screenshots below, I created a widget "test") > New Widgets are displayed twice on HDFS summary page > > > Key: AMBARI-23754 > URL: https://issues.apache.org/jira/browse/AMBARI-23754 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Priority: Major > Fix For: 2.7.0 > > Attachments: Screen Shot 2018-05-02 at 4.10.46 PM.png, Screen Shot > 2018-05-02 at 4.20.20 PM.png, Screen Shot 2018-05-02 at 4.21.31 PM.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23708) Sometimes Active and StandBy status is not displayed for default namespace
[ https://issues.apache.org/jira/browse/AMBARI-23708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod updated AMBARI-23708: -- Environment: (was: Active and StandBy status is not displayed for default namespace . On a cluster with namespaces, go to hdfs summary page. For the default namespace, Active and StandBy status for namenodes is missing. It appears for a short duration and again disappears) > Sometimes Active and StandBy status is not displayed for default namespace > -- > > Key: AMBARI-23708 > URL: https://issues.apache.org/jira/browse/AMBARI-23708 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Priority: Major > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23708) Sometimes Active and StandBy status is not displayed for default namespace
Vivek Rathod created AMBARI-23708: - Summary: Sometimes Active and StandBy status is not displayed for default namespace Key: AMBARI-23708 URL: https://issues.apache.org/jira/browse/AMBARI-23708 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Environment: Active and StandBy status is not displayed for default namespace . On a cluster with namespaces, go to hdfs summary page. For the default namespace, Active and StandBy status for namenodes is missing. It appears for a short duration and again disappears Reporter: Vivek Rathod Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23708) Sometimes Active and StandBy status is not displayed for default namespace
[ https://issues.apache.org/jira/browse/AMBARI-23708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod updated AMBARI-23708: -- Description: Active and StandBy status is not displayed for default namespace . On a cluster with namespaces, go to hdfs summary page. For the default namespace, Active and StandBy status for namenodes is missing. It appears for a short duration and again disappears > Sometimes Active and StandBy status is not displayed for default namespace > -- > > Key: AMBARI-23708 > URL: https://issues.apache.org/jira/browse/AMBARI-23708 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Priority: Major > Fix For: 2.7.0 > > > Active and StandBy status is not displayed for default namespace . > On a cluster with namespaces, go to hdfs summary page. For the default > namespace, Active and StandBy status for namenodes is missing. It appears for > a short duration and again disappears -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23655) While adding HDFS Namespace from UI, Timeline service fails to start
Vivek Rathod created AMBARI-23655:
-
Summary: While adding HDFS Namespace from UI, Timeline service
fails to start
Key: AMBARI-23655
URL: https://issues.apache.org/jira/browse/AMBARI-23655
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Vivek Rathod
Fix For: 2.7.0
While adding HDFS Namespace from UI, Timeline service fails to start in the
last step ("Restart All Services") because the active Namenode(from older
namespace) is in Safe Mode
It seems for restart all service operation we do not wait for namenode to leave
safemode
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23615) Header missing in Step2 Select hosts page in NN Federation Wizard
Vivek Rathod created AMBARI-23615: - Summary: Header missing in Step2 Select hosts page in NN Federation Wizard Key: AMBARI-23615 URL: https://issues.apache.org/jira/browse/AMBARI-23615 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Environment: ambari-server --hash 22cf9683c7c6d5dc0f84a2fd312ef14326ec9d35 Reporter: Vivek Rathod Fix For: 2.7.0 Attachments: Screen Shot 2018-04-18 at 1.50.43 PM.png Header missing in Step2 Select hosts page in NN Federation Wizard. All other pages have proper headers -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23612) Wizards do not load correctly when opening from different browser
[ https://issues.apache.org/jira/browse/AMBARI-23612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod updated AMBARI-23612: -- Attachment: Screen Shot 2018-04-17 at 2.14.29 PM.png Screen Shot 2018-04-13 at 4.39.52 PM.png > Wizards do not load correctly when opening from different browser > - > > Key: AMBARI-23612 > URL: https://issues.apache.org/jira/browse/AMBARI-23612 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 > Environment: ambari-server --hash > 5507ee62ae19676fbf35b889b602648a54185289 >Reporter: Vivek Rathod >Priority: Major > Fix For: 2.7.0 > > Attachments: Screen Shot 2018-04-17 at 2.14.29 PM.png, Screen Shot > 2018-04-17 at 2.17.56 PM.png > > > Wizards do not load when opening from different browser > STR: Launch any wizard like Add New HDFS Namespace or Move master wizard. > While in the middle of the wizard, try to open it in another browser > Verified the Move master wizard with ambari 262 build and it works fine there -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23612) Wizards do not load correctly when opening from different browser
[ https://issues.apache.org/jira/browse/AMBARI-23612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod updated AMBARI-23612: -- Attachment: (was: Screen Shot 2018-04-13 at 4.39.52 PM.png) > Wizards do not load correctly when opening from different browser > - > > Key: AMBARI-23612 > URL: https://issues.apache.org/jira/browse/AMBARI-23612 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 > Environment: ambari-server --hash > 5507ee62ae19676fbf35b889b602648a54185289 >Reporter: Vivek Rathod >Priority: Major > Fix For: 2.7.0 > > Attachments: Screen Shot 2018-04-17 at 2.14.29 PM.png, Screen Shot > 2018-04-17 at 2.17.56 PM.png > > > Wizards do not load when opening from different browser > STR: Launch any wizard like Add New HDFS Namespace or Move master wizard. > While in the middle of the wizard, try to open it in another browser > Verified the Move master wizard with ambari 262 build and it works fine there -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23612) Wizards do not load correctly when opening from different browser
[ https://issues.apache.org/jira/browse/AMBARI-23612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod updated AMBARI-23612: -- Attachment: Screen Shot 2018-04-17 at 2.17.56 PM.png > Wizards do not load correctly when opening from different browser > - > > Key: AMBARI-23612 > URL: https://issues.apache.org/jira/browse/AMBARI-23612 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 > Environment: ambari-server --hash > 5507ee62ae19676fbf35b889b602648a54185289 >Reporter: Vivek Rathod >Priority: Major > Fix For: 2.7.0 > > Attachments: Screen Shot 2018-04-17 at 2.14.29 PM.png, Screen Shot > 2018-04-17 at 2.17.56 PM.png > > > Wizards do not load when opening from different browser > STR: Launch any wizard like Add New HDFS Namespace or Move master wizard. > While in the middle of the wizard, try to open it in another browser > Verified the Move master wizard with ambari 262 build and it works fine there -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23612) Wizards do not load correctly when opening from different browser
Vivek Rathod created AMBARI-23612: - Summary: Wizards do not load correctly when opening from different browser Key: AMBARI-23612 URL: https://issues.apache.org/jira/browse/AMBARI-23612 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Environment: ambari-server --hash 5507ee62ae19676fbf35b889b602648a54185289 Reporter: Vivek Rathod Fix For: 2.7.0 Wizards do not load when opening from different browser STR: Launch any wizard like Add New HDFS Namespace or Move master wizard. While in the middle of the wizard, try to open it in another browser Verified the Move master wizard with ambari 262 build and it works fine there -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23468) UI does not render all the configs on selecting non default config group
Vivek Rathod created AMBARI-23468: - Summary: UI does not render all the configs on selecting non default config group Key: AMBARI-23468 URL: https://issues.apache.org/jira/browse/AMBARI-23468 Project: Ambari Issue Type: Bug Affects Versions: 2.7.0 Reporter: Vivek Rathod Fix For: 2.7.0 UI does not render all the configs on selecting non default config group STR: 1) Create a Config Group 2) On services page -> Config tab and all the configs are rendered properly 2) Now select the config group and all the configs do not load properly UI is not making the call to get all the config groups when we select non default CG [http://:8080/api/v1/clusters/cl1/config_groups?ConfigGroup/tag.in(HDFS,RANGER_KMS,AMBARI_METRICS,RANGER,YARN,ZOOKEEPER,HIVE,KAFKA,ATLAS,DRUID,TEZ,AMBARI_INFRA_SOLR,HBASE,SQOOP,STORM,KNOX,MAPREDUCE2,SPARK2)=*|http://172.27.16.212:8080/api/v1/clusters/cl1/config_groups?ConfigGroup/tag.in(HDFS,RANGER_KMS,AMBARI_METRICS,RANGER,YARN,ZOOKEEPER,HIVE,KAFKA,ATLAS,DRUID,TEZ,AMBARI_INFRA_SOLR,HBASE,SQOOP,STORM,KNOX,MAPREDUCE2,SPARK2)=*] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23273) Hosts page does not unselect hosts on navigating away from the page
Vivek Rathod created AMBARI-23273: - Summary: Hosts page does not unselect hosts on navigating away from the page Key: AMBARI-23273 URL: https://issues.apache.org/jira/browse/AMBARI-23273 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Vivek Rathod Fix For: 2.7.0 Hosts page does not unselect hosts when navigating away from the page STR: -> Go to hosts page and select some hosts -> Now navigate away and come back to hosts page. Previously selected hosts are still selected This causes Selected Hosts in the drop down to be disabled. Refreshing the page works and it clears the selection -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23272) Server Error while Bulk Deleting Hosts
Vivek Rathod created AMBARI-23272:
-
Summary: Server Error while Bulk Deleting Hosts
Key: AMBARI-23272
URL: https://issues.apache.org/jira/browse/AMBARI-23272
Project: Ambari
Issue Type: Bug
Components: ambari-server, ambari-web
Affects Versions: 2.7.0
Reporter: Vivek Rathod
Fix For: 2.7.0
Server Error while Bulk Deleting Hosts
STR:
1) Create a config group and override a property
2) Bulk delete some hosts from UI that are in the config group. Deletion of
Host fails with.
UI does not handle this failure and the wizard is stuck
{code}
16 Mar 2018 20:26:03,339 WARN [pool-4-thread-1] AlertDefinitionHash:538 -
Unable to add configurations to alert definition command
org.apache.ambari.server.HostNotFoundException: Host not found,
hostname=
16 Mar 2018 20:26:03,317 WARN [pool-4-thread-1] AlertDefinitionHash:538 -
Unable to add configurations to alert definition command
org.apache.ambari.server.HostNotFoundException: Host not found,
hostname=
at
org.apache.ambari.server.state.cluster.ClustersImpl.getHost(ClustersImpl.java:438)
at
org.apache.ambari.server.state.ConfigHelper.getEffectiveDesiredTags(ConfigHelper.java:188)
at
org.apache.ambari.server.state.ConfigHelper.getEffectiveDesiredTags(ConfigHelper.java:172)
at
org.apache.ambari.server.agent.AlertDefinitionCommand.addConfigs(AlertDefinitionCommand.java:141)
at
org.apache.ambari.server.state.alert.AlertDefinitionHash.enqueueAgentCommands(AlertDefinitionHash.java:536)
at
org.apache.ambari.server.state.alert.AlertDefinitionHash.enqueueAgentCommands(AlertDefinitionHash.java:495)
at
org.apache.ambari.server.events.listeners.alerts.AlertHashInvalidationListener.onEvent(AlertHashInvalidationListener.java:127)
at sun.reflect.GeneratedMethodAccessor593.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
com.google.common.eventbus.EventSubscriber.handleEvent(EventSubscriber.java:74)
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:322)
at
com.google.common.eventbus.AsyncEventBus.access$001(AsyncEventBus.java:34)
at
com.google.common.eventbus.AsyncEventBus$1.run(AsyncEventBus.java:117)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
16 Mar 2018 20:26:03,464 ERROR [ambari-client-thread-8491]
ContainerResponse:419 - The RuntimeException could not be mapped to a response,
re-throwing to the HTTP container
javax.persistence.RollbackException: Transaction "rolled back" because
transaction was set to RollbackOnly.
at
org.eclipse.persistence.internal.jpa.transaction.EntityTransactionImpl.commit(EntityTransactionImpl.java:143)
at
org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:153)
at
org.apache.ambari.server.controller.internal.HostResourceProvider$4.invoke(HostResourceProvider.java:386)
at
org.apache.ambari.server.controller.internal.HostResourceProvider$4.invoke(HostResourceProvider.java:383)
at
org.apache.ambari.server.controller.internal.AbstractResourceProvider.invokeWithRetry(AbstractResourceProvider.java:465)
at
org.apache.ambari.server.controller.internal.AbstractResourceProvider.modifyResources(AbstractResourceProvider.java:346)
at
org.apache.ambari.server.controller.internal.HostResourceProvider.deleteResourcesAuthorized(HostResourceProvider.java:383)
at
org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.deleteResources(AbstractAuthorizedResourceProvider.java:346)
at
org.apache.ambari.server.controller.internal.ClusterControllerImpl.deleteResources(ClusterControllerImpl.java:337)
at
org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.delete(PersistenceManagerImpl.java:132)
at
org.apache.ambari.server.api.handlers.DeleteHandler.persist(DeleteHandler.java:48)
at
org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:68)
at
org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
at
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:163)
at
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:127)
at
org.apache.ambari.server.api.services.HostService.deleteHosts(HostService.java:314)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
[jira] [Created] (AMBARI-23214) StackAdvisor Error while enabling back security : invalid literal for int() with base 10
Vivek Rathod created AMBARI-23214:
-
Summary: StackAdvisor Error while enabling back security : invalid
literal for int() with base 10
Key: AMBARI-23214
URL: https://issues.apache.org/jira/browse/AMBARI-23214
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.6.2
Reporter: Vivek Rathod
Fix For: 2.6.2
StackAdvisor Error while enabling back security : invalid literal for int()
with base 10
STR:
1) Install cluster with Ambari 2.6.1.0
2) Upgrade to Ambari 2.6.2.0
3) Regenerate keytabs for missing components and start all services
4) Disable security
5) Enable NN and RM HA
6) Enable Security. On enabling security. On configure identities page, there
is a stackadvisor error
{code}
12 Mar 2018 06:29:08,144 INFO [ambari-client-thread-67] StackAdvisorRunner:71 -
advisor script stderr: Traceback (most recent call last):
File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 173, in
main(sys.argv)
File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 121, in
main
result = stackAdvisor.recommendConfigurations(services, hosts)
File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
line 776, in recommendConfigurations
calculation(configurations, clusterSummary, services, hosts)
File
"/var/lib/ambari-server/resources/scripts/./../stacks/HDP/2.6/services/stack_advisor.py",
line 125, in recommendZEPPELINConfigurations
if compare_versions(full_stack_version, '2.6.3.0') >= 0:
File
"/usr/lib/ambari-server/lib/resource_management/libraries/functions/version.py",
line 83, in compare_versions
return cmp(_normalize(v1, desired_segments=max_segments), _normalize(v2,
desired_segments=max_segments))
File
"/usr/lib/ambari-server/lib/resource_management/libraries/functions/version.py",
line 34, in _normalize
return [int(x) for x in v_list]
ValueError: invalid literal for int() with base 10: ''
12 Mar 2018 06:29:08,145 WARN [ambari-client-thread-67]
AbstractResourceProvider:97 - Error occured during recommendation
org.apache.ambari.server.api.services.stackadvisor.StackAdvisorException: Stack
Advisor reported an error: ValueError: invalid literal for int() with base 10:
''
StdOut file: /var/run/ambari-server/stack-recommendations/4/stackadvisor.out
StdErr file: /var/run/ambari-server/stack-recommendations/4/stackadvisor.err
at
org.apache.ambari.server.api.services.stackadvisor.StackAdvisorRunner.runScript(StackAdvisorRunner.java:96)
at
org.apache.ambari.server.api.services.stackadvisor.commands.StackAdvisorCommand.invoke(StackAdvisorCommand.java:297)
at
org.apache.ambari.server.api.services.stackadvisor.StackAdvisorHelper.recommend(StackAdvisorHelper.java:113)
at
org.apache.ambari.server.controller.internal.RecommendationResourceProvider.createResources(RecommendationResourceProvider.java:92)
at
org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298)
at
org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
at
org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37)
at
org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73)
at
org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
at
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
at
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
at
org.apache.ambari.server.api.services.RecommendationService.getRecommendation(RecommendationService.java:59)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at
[jira] [Created] (AMBARI-22970) Back button is missing on Host Page
Vivek Rathod created AMBARI-22970: - Summary: Back button is missing on Host Page Key: AMBARI-22970 URL: https://issues.apache.org/jira/browse/AMBARI-22970 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: trunk Reporter: Vivek Rathod Fix For: trunk Back button is missing on Host Page. Go to any host page and and to navigate back to all hosts, there is not back button. Clicking on Hosts works but it is not intuitive -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22969) When host is registering while adding it, Remove Selected button shows up on selecting host
Vivek Rathod created AMBARI-22969: - Summary: When host is registering while adding it, Remove Selected button shows up on selecting host Key: AMBARI-22969 URL: https://issues.apache.org/jira/browse/AMBARI-22969 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: trunk Reporter: Vivek Rathod Fix For: trunk When host is registering(or installing agent) while adding it, Remove Selected button shows up when you select a host STR: Try to add host to a cluster. When it is registering, the remove icon(on the right side of the host name) is disabled, which is expected. But at that time, if you select the host checkbox, then Remove Selected button is available which allows user to delete the host while it is registering to the server -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22042) Final Properties filter does not work for Config Groups
[ https://issues.apache.org/jira/browse/AMBARI-22042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod updated AMBARI-22042: -- Attachment: (was: screenshot-2.png) > Final Properties filter does not work for Config Groups > --- > > Key: AMBARI-22042 > URL: https://issues.apache.org/jira/browse/AMBARI-22042 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Vivek Rathod > Fix For: 2.6.0 > > > Final property filter does not work for Config Groups > STR: > 1) Create a config group and override a property and set it to final > 2) On configs page, select the config group and filter by final > The filter works with Default group but does not work with custom config group -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22042) Final Properties filter does not work for Config Groups
[ https://issues.apache.org/jira/browse/AMBARI-22042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod updated AMBARI-22042: -- Attachment: (was: screenshot-1.png) > Final Properties filter does not work for Config Groups > --- > > Key: AMBARI-22042 > URL: https://issues.apache.org/jira/browse/AMBARI-22042 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Vivek Rathod > Fix For: 2.6.0 > > > Final property filter does not work for Config Groups > STR: > 1) Create a config group and override a property and set it to final > 2) On configs page, select the config group and filter by final > The filter works with Default group but does not work with custom config group -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22042) Final Properties filter does not work for Config Groups
[ https://issues.apache.org/jira/browse/AMBARI-22042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod updated AMBARI-22042: -- Attachment: screenshot-1.png > Final Properties filter does not work for Config Groups > --- > > Key: AMBARI-22042 > URL: https://issues.apache.org/jira/browse/AMBARI-22042 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Vivek Rathod > Fix For: 2.6.0 > > Attachments: screenshot-1.png, screenshot-2.png > > > Final property filter does not work for Config Groups > STR: > 1) Create a config group and override a property and set it to final > 2) On configs page, select the config group and filter by final > The filter works with Default group but does not work with custom config group -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22042) Final Properties filter does not work for Config Groups
[ https://issues.apache.org/jira/browse/AMBARI-22042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod updated AMBARI-22042: -- Attachment: screenshot-2.png > Final Properties filter does not work for Config Groups > --- > > Key: AMBARI-22042 > URL: https://issues.apache.org/jira/browse/AMBARI-22042 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Vivek Rathod > Fix For: 2.6.0 > > Attachments: screenshot-1.png, screenshot-2.png > > > Final property filter does not work for Config Groups > STR: > 1) Create a config group and override a property and set it to final > 2) On configs page, select the config group and filter by final > The filter works with Default group but does not work with custom config group -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22042) Final Properties filter does not work for Config Groups
Vivek Rathod created AMBARI-22042: - Summary: Final Properties filter does not work for Config Groups Key: AMBARI-22042 URL: https://issues.apache.org/jira/browse/AMBARI-22042 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.6.0 Reporter: Vivek Rathod Fix For: 2.6.0 Final property filter does not work for Config Groups STR: 1) Create a config group and override a property and set it to final 2) On configs page, select the config group and filter by final The filter works with Default group but does not work with custom config group -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22035) Stack and Versions page is stuck while trying to install a new stack
Vivek Rathod created AMBARI-22035: - Summary: Stack and Versions page is stuck while trying to install a new stack Key: AMBARI-22035 URL: https://issues.apache.org/jira/browse/AMBARI-22035 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.6.0 Reporter: Vivek Rathod Fix For: 2.6.0 STR: Install Ambari 2.5.2 with HDP 2.5 Upgrade to Ambari 2.6.0 Register a new stack HDP 2.6.* Click Install On button -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21932) Some clients are shown as installed for a hosts page even when they have not been installed through ambari
Vivek Rathod created AMBARI-21932: - Summary: Some clients are shown as installed for a hosts page even when they have not been installed through ambari Key: AMBARI-21932 URL: https://issues.apache.org/jira/browse/AMBARI-21932 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.2 Reporter: Vivek Rathod Fix For: 2.6.0 Some clients are shown as installed for a hosts page even when they have not been installed through ambari On an installed cluster: 1) Add a host with no clients 2) Now add a service with clients on all hosts (including the newely added host) 3) On the newely added host, only one client is expected(from the newely added service) to be shown but actually other clients are also present as well -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-18094) Oozie server failed to start with NoClassDefFoundError: org/apache/oozie/cli/CLIParser
[
https://issues.apache.org/jira/browse/AMBARI-18094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Rathod updated AMBARI-18094:
--
Description:
Install cluster with HDFS, Yarn, MR and ZK, and then add
{hive,tez,piz}
and then
{oozie,hbase,sqoop}
Oozie server fails to start on adding oozie.
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
line 215, in
OozieServer().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 280, in execute
method(env)
File
"/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
line 95, in start
oozie_service(action='start', upgrade_type=upgrade_type)
File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
line 89, in thunk
return fn(*args, **kwargs)
File
"/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
line 131, in oozie_service
path = params.execute_path
File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
line 155, in __init__
self.env.run()
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 124, in run_action
provider_action()
File
"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
line 273, in action_run
tries=self.resource.tries, try_sleep=self.resource.try_sleep)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 71, in inner
result = function(command, **kwargs)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 93, in checked_call
tries=tries, try_sleep=try_sleep)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 141, in _call_wrapper
result = _call(command, **kwargs_copy)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 294, in _call
raise Fail(err_msg)
resource_management.core.exceptions.Fail: Execution of
'/usr/hdp/current/oozie-server/bin/oozie-setup.sh sharelib create -fs
hdfs://:8020 -locallib /usr/hdp/current/oozie-server/share'
returned 1. Hortonworks #
This is MOTD message, added for testing in qe infra
setting OOZIE_CONFIG=${OOZIE_CONFIG:-/usr/hdp/current/oozie-server/conf}
setting
CATALINA_BASE=${CATALINA_BASE:-/usr/hdp/current/oozie-server/oozie-server}
setting CATALINA_TMPDIR=${CATALINA_TMPDIR:-/var/tmp/oozie}
setting OOZIE_CATALINA_HOME=/usr/lib/bigtop-tomcat
setting JAVA_HOME=/usr/jdk64/jdk1.8.0_60
setting JRE_HOME=${JAVA_HOME}
setting CATALINA_OPTS="$CATALINA_OPTS -Xmx2048m"
setting OOZIE_LOG=/grid/0/log/oozie
setting CATALINA_PID=/var/run/oozie/oozie.pid
setting OOZIE_DATA=/grid/0/hadoop/oozie/data
setting OOZIE_HTTP_PORT=11000
setting OOZIE_ADMIN_PORT=11001
setting
JAVA_LIBRARY_PATH=/usr/hdp/current/hadoop-client/lib/native/Linux-amd64-64
setting OOZIE_CLIENT_OPTS="${OOZIE_CLIENT_OPTS}
-Doozie.connection.retry.count=5 "
setting OOZIE_CONFIG=${OOZIE_CONFIG:-/usr/hdp/current/oozie-server/conf}
setting
CATALINA_BASE=${CATALINA_BASE:-/usr/hdp/current/oozie-server/oozie-server}
setting CATALINA_TMPDIR=${CATALINA_TMPDIR:-/var/tmp/oozie}
setting OOZIE_CATALINA_HOME=/usr/lib/bigtop-tomcat
setting JAVA_HOME=/usr/jdk64/jdk1.8.0_60
setting JRE_HOME=${JAVA_HOME}
setting CATALINA_OPTS="$CATALINA_OPTS -Xmx2048m"
setting OOZIE_LOG=/grid/0/log/oozie
setting CATALINA_PID=/var/run/oozie/oozie.pid
setting OOZIE_DATA=/grid/0/hadoop/oozie/data
setting OOZIE_HTTP_PORT=11000
setting OOZIE_ADMIN_PORT=11001
setting
JAVA_LIBRARY_PATH=/usr/hdp/current/hadoop-client/lib/native/Linux-amd64-64
setting OOZIE_CLIENT_OPTS="${OOZIE_CLIENT_OPTS}
-Doozie.connection.retry.count=5 "
Exception in thread "main" java.lang.NoClassDefFoundError:
org/apache/oozie/cli/CLIParser
at org.apache.oozie.tools.OozieSharelibCLI.run(OozieSharelibCLI.java:92)
at
org.apache.oozie.tools.OozieSharelibCLI.main(OozieSharelibCLI.java:67)
Caused by: java.lang.ClassNotFoundException: org.apache.oozie.cli.CLIParser
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 2 more
{code}
was:
Install cluster with HDFS, Yarn, MR and ZK, and then add
{hive,tez,piz}
and then
{oozie,hbase,sqoop}
Oozie server fails to start on adding oozie.
{code}
Traceback (most recent call last):
File
[jira] [Resolved] (AMBARI-19245) Smartsense Install fails while installing cluster with Blueprint with Customized Service Users
[
https://issues.apache.org/jira/browse/AMBARI-19245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Rathod resolved AMBARI-19245.
---
Resolution: Invalid
> Smartsense Install fails while installing cluster with Blueprint with
> Customized Service Users
> --
>
> Key: AMBARI-19245
> URL: https://issues.apache.org/jira/browse/AMBARI-19245
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
> Fix For: 2.5.0
>
>
> Smartsense Install fails while installing cluster with Blueprint with
> Customized Service User
> {code}
> Execution of 'useradd -m -G cstm-hdfs -g hadoop activity_analyzer' returned
> 6. useradd: group 'cstm-hdfs' does not exist
> {code}
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_agent.py",
> line 22, in
> HSTScript('agent').execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 282, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_script.py",
> line 48, in install
> self.deploy_component_specific_config(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_script.py",
> line 360, in deploy_component_specific_config
> self.create_activity_user()
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_script.py",
> line 516, in create_activity_user
> groups = params.config['configurations']['hadoop-env']['hdfs_user']
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/accounts.py",
> line 82, in action_create
> shell.checked_call(command, sudo=True)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 'useradd -m
> -G cstm-hdfs -g hadoop activity_analyzer' returned 6. useradd: group
> 'cstm-hdfs' does not exist
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_agent.py",
> line 22, in
> HSTScript('agent').execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 282, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_script.py",
> line 48, in install
> self.deploy_component_specific_config(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_script.py",
> line 360, in deploy_component_specific_config
> self.create_activity_user()
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_script.py",
> line 516, in create_activity_user
> groups = params.config['configurations']['hadoop-env']['hdfs_user']
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/accounts.py",
> line 82, in action_create
> shell.checked_call(command, sudo=True)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
[jira] [Resolved] (AMBARI-19731) Stack Advisor error while adding services in Add Service Wizard
[
https://issues.apache.org/jira/browse/AMBARI-19731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Rathod resolved AMBARI-19731.
---
Resolution: Invalid
> Stack Advisor error while adding services in Add Service Wizard
> ---
>
> Key: AMBARI-19731
> URL: https://issues.apache.org/jira/browse/AMBARI-19731
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
> Fix For: 2.5.0
>
> Attachments: screenshot-1.png
>
>
> Stack Advisor error while adding services in Add Service Wizard
> This was observed after deleting some services and while adding them back to
> the cluster, stack advisor throws:
> {code}
> 500 status code received on POST method for API:
> /api/v1/stacks/HDP/versions/2.6/recommendations
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20146) HiveView2.0: Visual Explain graph zooms out on scrolling down
[ https://issues.apache.org/jira/browse/AMBARI-20146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod updated AMBARI-20146: -- Attachment: screenshot-1.png > HiveView2.0: Visual Explain graph zooms out on scrolling down > - > > Key: AMBARI-20146 > URL: https://issues.apache.org/jira/browse/AMBARI-20146 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Vivek Rathod > Fix For: 2.5.0 > > Attachments: screenshot-1.png > > > HiveView2.0: Visual Explain graph zooms out on scrolling down. > Noticed this on hive view, when after typing a query, click visual explain. > On scrolling down, the graph zooms out every time, which affects the user > experience while trying to use the visual explain feature -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20146) HiveView2.0: Visual Explain graph zooms out on scrolling down
Vivek Rathod created AMBARI-20146: - Summary: HiveView2.0: Visual Explain graph zooms out on scrolling down Key: AMBARI-20146 URL: https://issues.apache.org/jira/browse/AMBARI-20146 Project: Ambari Issue Type: Bug Affects Versions: 2.5.0 Reporter: Vivek Rathod Fix For: 2.5.0 HiveView2.0: Visual Explain graph zooms out on scrolling down. Noticed this on hive view, when after typing a query, click visual explain. On scrolling down, the graph zooms out every time, which affects the user experience while trying to use the visual explain feature -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-18867) Field spark.history.kerberos.principal is not present on Configure Identities page
[ https://issues.apache.org/jira/browse/AMBARI-18867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod resolved AMBARI-18867. --- Resolution: Not A Problem This is not a bug, but a change introduced as part of AMBARI-18148 > Field spark.history.kerberos.principal is not present on Configure Identities > page > -- > > Key: AMBARI-18867 > URL: https://issues.apache.org/jira/browse/AMBARI-18867 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Rathod > Fix For: 2.5.0 > > > Field spark.history.kerberos.principal is not present on Configure Identities > page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20032) HDFS service check fails after Stopping one Namenode in HA cluster
Vivek Rathod created AMBARI-20032: - Summary: HDFS service check fails after Stopping one Namenode in HA cluster Key: AMBARI-20032 URL: https://issues.apache.org/jira/browse/AMBARI-20032 Project: Ambari Issue Type: Bug Affects Versions: 2.5.0 Reporter: Vivek Rathod Fix For: 2.5.0 HDFS service check fails after Stopping one Namenode in HA cluster. Stop the active Namenode and run HDFS service check, it fails. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19730) Namenodes fail to come up after removing some Journalnodes
[
https://issues.apache.org/jira/browse/AMBARI-19730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15852226#comment-15852226
]
Vivek Rathod commented on AMBARI-19730:
---
Thanks [~stoader] for the analysis
> Namenodes fail to come up after removing some Journalnodes
> --
>
> Key: AMBARI-19730
> URL: https://issues.apache.org/jira/browse/AMBARI-19730
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
> Fix For: 2.5.0
>
>
> Namenodes fail to come up after removing some Journalnodes
> STR:
> Deploy a 6 node HA cluster using Blueprints, with 6 Journalnodes.
> Remove 2 Journalnodes using Manage JN Wizard
> In the Start All Services in Manage JN Wizard, Both the Namenodes fail to
> come up.
> {code}
> 17/01/26 03:39:56 INFO ipc.Client: Retrying connect to server:
> /:8020. Already tried 0 time(s);
> retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=1,
> sleepTime=1000 MILLISECONDS)
> 17/01/26 03:39:56 WARN ipc.Client: Failed to connect to server:
> /:8020: retries get failed due to
> exceeded maximum allowed retries number: 1
> java.net.ConnectException: Connection refused
> at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
> at
> sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
> at
> org.apache.hadoop.net.SocketIOWithTimeout.connect(SocketIOWithTimeout.java:206)
> at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:531)
> at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:495)
> at
> org.apache.hadoop.ipc.Client$Connection.setupConnection(Client.java:650)
> at
> org.apache.hadoop.ipc.Client$Connection.setupIOstreams(Client.java:745)
> at org.apache.hadoop.ipc.Client$Connection.access$3200(Client.java:397)
> at org.apache.hadoop.ipc.Client.getConnection(Client.java:1618)
> at org.apache.hadoop.ipc.Client.call(Client.java:1449)
> at org.apache.hadoop.ipc.Client.call(Client.java:1396)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:233)
> at com.sun.proxy.$Proxy8.getServiceStatus(Unknown Source)
> at
> org.apache.hadoop.ha.protocolPB.HAServiceProtocolClientSideTranslatorPB.getServiceStatus(HAServiceProtocolClientSideTranslatorPB.java:122)
> at org.apache.hadoop.ha.HAAdmin.getServiceState(HAAdmin.java:359)
> at org.apache.hadoop.ha.HAAdmin.runCmd(HAAdmin.java:457)
> at org.apache.hadoop.hdfs.tools.DFSHAAdmin.runCmd(DFSHAAdmin.java:120)
> at org.apache.hadoop.ha.HAAdmin.run(HAAdmin.java:384)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:90)
> at org.apache.hadoop.hdfs.tools.DFSHAAdmin.main(DFSHAAdmin.java:132)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (AMBARI-19730) Namenodes fail to come up after removing some Journalnodes
[
https://issues.apache.org/jira/browse/AMBARI-19730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Rathod resolved AMBARI-19730.
---
Resolution: Invalid
> Namenodes fail to come up after removing some Journalnodes
> --
>
> Key: AMBARI-19730
> URL: https://issues.apache.org/jira/browse/AMBARI-19730
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
> Fix For: 2.5.0
>
>
> Namenodes fail to come up after removing some Journalnodes
> STR:
> Deploy a 6 node HA cluster using Blueprints, with 6 Journalnodes.
> Remove 2 Journalnodes using Manage JN Wizard
> In the Start All Services in Manage JN Wizard, Both the Namenodes fail to
> come up.
> {code}
> 17/01/26 03:39:56 INFO ipc.Client: Retrying connect to server:
> /:8020. Already tried 0 time(s);
> retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=1,
> sleepTime=1000 MILLISECONDS)
> 17/01/26 03:39:56 WARN ipc.Client: Failed to connect to server:
> /:8020: retries get failed due to
> exceeded maximum allowed retries number: 1
> java.net.ConnectException: Connection refused
> at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
> at
> sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
> at
> org.apache.hadoop.net.SocketIOWithTimeout.connect(SocketIOWithTimeout.java:206)
> at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:531)
> at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:495)
> at
> org.apache.hadoop.ipc.Client$Connection.setupConnection(Client.java:650)
> at
> org.apache.hadoop.ipc.Client$Connection.setupIOstreams(Client.java:745)
> at org.apache.hadoop.ipc.Client$Connection.access$3200(Client.java:397)
> at org.apache.hadoop.ipc.Client.getConnection(Client.java:1618)
> at org.apache.hadoop.ipc.Client.call(Client.java:1449)
> at org.apache.hadoop.ipc.Client.call(Client.java:1396)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:233)
> at com.sun.proxy.$Proxy8.getServiceStatus(Unknown Source)
> at
> org.apache.hadoop.ha.protocolPB.HAServiceProtocolClientSideTranslatorPB.getServiceStatus(HAServiceProtocolClientSideTranslatorPB.java:122)
> at org.apache.hadoop.ha.HAAdmin.getServiceState(HAAdmin.java:359)
> at org.apache.hadoop.ha.HAAdmin.runCmd(HAAdmin.java:457)
> at org.apache.hadoop.hdfs.tools.DFSHAAdmin.runCmd(DFSHAAdmin.java:120)
> at org.apache.hadoop.ha.HAAdmin.run(HAAdmin.java:384)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:90)
> at org.apache.hadoop.hdfs.tools.DFSHAAdmin.main(DFSHAAdmin.java:132)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19730) Namenodes fail to come up after removing some Journalnodes
[
https://issues.apache.org/jira/browse/AMBARI-19730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15852225#comment-15852225
]
Vivek Rathod commented on AMBARI-19730:
---
Closing this as invalid issue because format Journalnodes did not execute
correctly as dfs.namenode.shared.edits.dir pointed to only 3 JournalNodes
instead of all 6.
Setting the value of dfs.namenode.shared.edits.dir to
qjournal://localhost:8485/mycluster worked because by specifying localhost in
the value, Blueprint processor recognises "localhost" and replaces with the
necessary real host names
> Namenodes fail to come up after removing some Journalnodes
> --
>
> Key: AMBARI-19730
> URL: https://issues.apache.org/jira/browse/AMBARI-19730
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
> Fix For: 2.5.0
>
>
> Namenodes fail to come up after removing some Journalnodes
> STR:
> Deploy a 6 node HA cluster using Blueprints, with 6 Journalnodes.
> Remove 2 Journalnodes using Manage JN Wizard
> In the Start All Services in Manage JN Wizard, Both the Namenodes fail to
> come up.
> {code}
> 17/01/26 03:39:56 INFO ipc.Client: Retrying connect to server:
> /:8020. Already tried 0 time(s);
> retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=1,
> sleepTime=1000 MILLISECONDS)
> 17/01/26 03:39:56 WARN ipc.Client: Failed to connect to server:
> /:8020: retries get failed due to
> exceeded maximum allowed retries number: 1
> java.net.ConnectException: Connection refused
> at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
> at
> sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
> at
> org.apache.hadoop.net.SocketIOWithTimeout.connect(SocketIOWithTimeout.java:206)
> at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:531)
> at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:495)
> at
> org.apache.hadoop.ipc.Client$Connection.setupConnection(Client.java:650)
> at
> org.apache.hadoop.ipc.Client$Connection.setupIOstreams(Client.java:745)
> at org.apache.hadoop.ipc.Client$Connection.access$3200(Client.java:397)
> at org.apache.hadoop.ipc.Client.getConnection(Client.java:1618)
> at org.apache.hadoop.ipc.Client.call(Client.java:1449)
> at org.apache.hadoop.ipc.Client.call(Client.java:1396)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:233)
> at com.sun.proxy.$Proxy8.getServiceStatus(Unknown Source)
> at
> org.apache.hadoop.ha.protocolPB.HAServiceProtocolClientSideTranslatorPB.getServiceStatus(HAServiceProtocolClientSideTranslatorPB.java:122)
> at org.apache.hadoop.ha.HAAdmin.getServiceState(HAAdmin.java:359)
> at org.apache.hadoop.ha.HAAdmin.runCmd(HAAdmin.java:457)
> at org.apache.hadoop.hdfs.tools.DFSHAAdmin.runCmd(DFSHAAdmin.java:120)
> at org.apache.hadoop.ha.HAAdmin.run(HAAdmin.java:384)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:90)
> at org.apache.hadoop.hdfs.tools.DFSHAAdmin.main(DFSHAAdmin.java:132)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (AMBARI-19787) Service Checks not being executed after Wire Encryption
[ https://issues.apache.org/jira/browse/AMBARI-19787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod resolved AMBARI-19787. --- Resolution: Duplicate > Service Checks not being executed after Wire Encryption > --- > > Key: AMBARI-19787 > URL: https://issues.apache.org/jira/browse/AMBARI-19787 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Vivek Rathod > Fix For: 2.5.0 > > Attachments: screenshot-1.png > > > Service Checks not being executed after Wire Encryption. Deploy failed > because some service checks were queued but were never executed after Wire > Encryption. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19787) Service Checks not being executed after Wire Encryption
[ https://issues.apache.org/jira/browse/AMBARI-19787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15852220#comment-15852220 ] Vivek Rathod commented on AMBARI-19787: --- This was fixed as part of AMBARI-19775 > Service Checks not being executed after Wire Encryption > --- > > Key: AMBARI-19787 > URL: https://issues.apache.org/jira/browse/AMBARI-19787 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Vivek Rathod > Fix For: 2.5.0 > > Attachments: screenshot-1.png > > > Service Checks not being executed after Wire Encryption. Deploy failed > because some service checks were queued but were never executed after Wire > Encryption. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-19840) Atlas Metadata Server Fails to start
[
https://issues.apache.org/jira/browse/AMBARI-19840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Rathod resolved AMBARI-19840.
---
Resolution: Invalid
> Atlas Metadata Server Fails to start
>
>
> Key: AMBARI-19840
> URL: https://issues.apache.org/jira/browse/AMBARI-19840
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
> Fix For: 2.5.0
>
>
> Atlas Metadata Server Fails to start after deleting and adding back atlas.
> STR:
> 1) Delete the following services from the cluster: Smartsense, Atlas, Hbase,
> Sqoop, Storm, Knox, Flume and AMS
> 2) Add back the deleted services using Add service Wizard
> Atlas Metadata Server fails with
> {code}
> ERROR Java::OrgApacheHadoopHbaseIpc::RemoteWithExtrasException:
> org.apache.hadoop.hbase.coprocessor.CoprocessorException: SSLContext must not
> be null
> at
> org.apache.ranger.authorization.hbase.RangerAuthorizationCoprocessor.grant(RangerAuthorizationCoprocessor.java:1180)
> at
> org.apache.hadoop.hbase.protobuf.generated.AccessControlProtos$AccessControlService$1.grant(AccessControlProtos.java:9933)
> at
> org.apache.hadoop.hbase.protobuf.generated.AccessControlProtos$AccessControlService.callMethod(AccessControlProtos.java:10097)
> at
> org.apache.hadoop.hbase.regionserver.HRegion.execService(HRegion.java:7832)
> at
> org.apache.hadoop.hbase.regionserver.RSRpcServices.execServiceOnRegion(RSRpcServices.java:1961)
> at
> org.apache.hadoop.hbase.regionserver.RSRpcServices.execService(RSRpcServices.java:1943)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:32389)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2141)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:112)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:187)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:167)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19840) Atlas Metadata Server Fails to start
[
https://issues.apache.org/jira/browse/AMBARI-19840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15852215#comment-15852215
]
Vivek Rathod commented on AMBARI-19840:
---
The issue was that the cluster was wire encrypted and on deleting some services
and adding them back, those services were no longer configured to work with
SSL. But Ranger still tried to communicate to them using SSL.
The solution is either to un-wire encrypt ranger, or the enable wire encryption
back for the newly added services. Resolving this as invalid buy
> Atlas Metadata Server Fails to start
>
>
> Key: AMBARI-19840
> URL: https://issues.apache.org/jira/browse/AMBARI-19840
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
> Fix For: 2.5.0
>
>
> Atlas Metadata Server Fails to start after deleting and adding back atlas.
> STR:
> 1) Delete the following services from the cluster: Smartsense, Atlas, Hbase,
> Sqoop, Storm, Knox, Flume and AMS
> 2) Add back the deleted services using Add service Wizard
> Atlas Metadata Server fails with
> {code}
> ERROR Java::OrgApacheHadoopHbaseIpc::RemoteWithExtrasException:
> org.apache.hadoop.hbase.coprocessor.CoprocessorException: SSLContext must not
> be null
> at
> org.apache.ranger.authorization.hbase.RangerAuthorizationCoprocessor.grant(RangerAuthorizationCoprocessor.java:1180)
> at
> org.apache.hadoop.hbase.protobuf.generated.AccessControlProtos$AccessControlService$1.grant(AccessControlProtos.java:9933)
> at
> org.apache.hadoop.hbase.protobuf.generated.AccessControlProtos$AccessControlService.callMethod(AccessControlProtos.java:10097)
> at
> org.apache.hadoop.hbase.regionserver.HRegion.execService(HRegion.java:7832)
> at
> org.apache.hadoop.hbase.regionserver.RSRpcServices.execServiceOnRegion(RSRpcServices.java:1961)
> at
> org.apache.hadoop.hbase.regionserver.RSRpcServices.execService(RSRpcServices.java:1943)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:32389)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2141)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:112)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:187)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:167)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-19840) Atlas Metadata Server Fails to start
Vivek Rathod created AMBARI-19840:
-
Summary: Atlas Metadata Server Fails to start
Key: AMBARI-19840
URL: https://issues.apache.org/jira/browse/AMBARI-19840
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.5.0
Reporter: Vivek Rathod
Fix For: 2.5.0
Atlas Metadata Server Fails to start after deleting and adding back atlas.
STR:
1) Delete the following services from the cluster: Smartsense, Atlas, Hbase,
Sqoop, Storm, Knox, Flume and AMS
2) Add back the deleted services using Add service Wizard
Atlas Metadata Server fails with
{code}
ERROR Java::OrgApacheHadoopHbaseIpc::RemoteWithExtrasException:
org.apache.hadoop.hbase.coprocessor.CoprocessorException: SSLContext must not
be null
at
org.apache.ranger.authorization.hbase.RangerAuthorizationCoprocessor.grant(RangerAuthorizationCoprocessor.java:1180)
at
org.apache.hadoop.hbase.protobuf.generated.AccessControlProtos$AccessControlService$1.grant(AccessControlProtos.java:9933)
at
org.apache.hadoop.hbase.protobuf.generated.AccessControlProtos$AccessControlService.callMethod(AccessControlProtos.java:10097)
at
org.apache.hadoop.hbase.regionserver.HRegion.execService(HRegion.java:7832)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.execServiceOnRegion(RSRpcServices.java:1961)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.execService(RSRpcServices.java:1943)
at
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:32389)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2141)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:112)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:187)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:167)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] (AMBARI-19787) Service Checks not being executed after Wire Encryption
Title: Message Title Vivek Rathod updated an issue Ambari / AMBARI-19787 Service Checks not being executed after Wire Encryption Change By: Vivek Rathod Service Checks not being executed after Wire Encryption. Deploy failed because some service checks were queued but were never executed after Wire Encryption. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
[jira] (AMBARI-19787) Service Checks not being executed after Wire Encryption
Title: Message Title Vivek Rathod updated an issue Ambari / AMBARI-19787 Service Checks not being executed after Wire Encryption Change By: Vivek Rathod Attachment: screenshot-1.png Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
[jira] (AMBARI-19787) Service Checks not being executed after Wire Encryption
Title: Message Title Vivek Rathod created an issue Ambari / AMBARI-19787 Service Checks not being executed after Wire Encryption Issue Type: Bug Affects Versions: 2.5.0 Assignee: Unassigned Created: 30/Jan/17 22:03 Fix Versions: 2.5.0 Priority: Major Reporter: Vivek Rathod Service Checks not being executed after Wire Encryption. Deploy failed because some service checks were queued but never executed after Wire Encryption. Add Comment
[jira] [Created] (AMBARI-19736) Format ZKFC commands failing while enabling NameNode HA
Vivek Rathod created AMBARI-19736:
-
Summary: Format ZKFC commands failing while enabling NameNode HA
Key: AMBARI-19736
URL: https://issues.apache.org/jira/browse/AMBARI-19736
Project: Ambari
Issue Type: Bug
Affects Versions: 2.5.0
Reporter: Vivek Rathod
Fix For: 2.5.0
Format ZKFC commands failing while enabling NameNode HA at Initializa Metadata
step
{code}
17/01/26 00:45:51 INFO ha.ActiveStandbyElector: Terminating ZK connection for
elector id=124323713 appData=null cb=Elector callbacks for NameNode at
/:8020
17/01/26 00:45:51 INFO zookeeper.ZooKeeper: Session: 0x359d8394c030006 closed
17/01/26 00:45:51 INFO zookeeper.ClientCnxn: EventThread shut down
17/01/26 00:45:51 FATAL tools.DFSZKFailoverController: Got a fatal error,
exiting now
java.io.IOException: Couldn't create /hadoop-ha/nameservice
at
org.apache.hadoop.ha.ActiveStandbyElector.ensureParentZNode(ActiveStandbyElector.java:350)
at
org.apache.hadoop.ha.ZKFailoverController.formatZK(ZKFailoverController.java:274)
at
org.apache.hadoop.ha.ZKFailoverController.doRun(ZKFailoverController.java:212)
at
org.apache.hadoop.ha.ZKFailoverController.access$000(ZKFailoverController.java:61)
at
org.apache.hadoop.ha.ZKFailoverController$1.run(ZKFailoverController.java:172)
at
org.apache.hadoop.ha.ZKFailoverController$1.run(ZKFailoverController.java:168)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:360)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1704)
at
org.apache.hadoop.security.SecurityUtil.doAsLoginUserOrFatal(SecurityUtil.java:474)
at
org.apache.hadoop.ha.ZKFailoverController.run(ZKFailoverController.java:168)
at
org.apache.hadoop.hdfs.tools.DFSZKFailoverController.main(DFSZKFailoverController.java:183)
Caused by: org.apache.zookeeper.KeeperException$NoAuthException:
KeeperErrorCode = NoAuth for /hadoop-ha/nameservice
at org.apache.zookeeper.KeeperException.create(KeeperException.java:113)
at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:783)
at
org.apache.hadoop.ha.ActiveStandbyElector$3.run(ActiveStandbyElector.java:1000)
at
org.apache.hadoop.ha.ActiveStandbyElector$3.run(ActiveStandbyElector.java:997)
at
org.apache.hadoop.ha.ActiveStandbyElector.zkDoWithRetries(ActiveStandbyElector.java:1041)
at
org.apache.hadoop.ha.ActiveStandbyElector.createWithRetries(ActiveStandbyElector.java:997)
at
org.apache.hadoop.ha.ActiveStandbyElector.ensureParentZNode(ActiveStandbyElector.java:344)
... 11 more
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19731) Stack Advisor error while adding services in Add Service Wizard
[
https://issues.apache.org/jira/browse/AMBARI-19731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Rathod updated AMBARI-19731:
--
Attachment: screenshot-1.png
> Stack Advisor error while adding services in Add Service Wizard
> ---
>
> Key: AMBARI-19731
> URL: https://issues.apache.org/jira/browse/AMBARI-19731
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
> Fix For: 2.5.0
>
> Attachments: screenshot-1.png
>
>
> Stack Advisor error while adding services in Add Service Wizard
> This was observed after deleting some services and while adding them back to
> the cluster, stack advisor throws:
> {code}
> 500 status code received on POST method for API:
> /api/v1/stacks/HDP/versions/2.6/recommendations
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19731) Stack Advisor error while adding services in Add Service Wizard
Vivek Rathod created AMBARI-19731:
-
Summary: Stack Advisor error while adding services in Add Service
Wizard
Key: AMBARI-19731
URL: https://issues.apache.org/jira/browse/AMBARI-19731
Project: Ambari
Issue Type: Bug
Affects Versions: 2.5.0
Reporter: Vivek Rathod
Fix For: 2.5.0
Stack Advisor error while adding services in Add Service Wizard
This was observed after deleting some services and while adding them back to
the cluster, stack advisor throws:
{code}
500 status code received on POST method for API:
/api/v1/stacks/HDP/versions/2.6/recommendations
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19730) Namenodes fail to come up after removing some Journalnodes
Vivek Rathod created AMBARI-19730:
-
Summary: Namenodes fail to come up after removing some Journalnodes
Key: AMBARI-19730
URL: https://issues.apache.org/jira/browse/AMBARI-19730
Project: Ambari
Issue Type: Bug
Affects Versions: 2.5.0
Reporter: Vivek Rathod
Fix For: 2.5.0
Namenodes fail to come up after removing some Journalnodes
STR:
Deploy a 6 node HA cluster using Blueprints, with 6 Journalnodes.
Remove 2 Journalnodes using Manage JN Wizard
In the Start All Services in Manage JN Wizard, Both the Namenodes fail to come
up.
{code}
17/01/26 03:39:56 INFO ipc.Client: Retrying connect to server:
/:8020. Already tried 0 time(s); retry
policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=1, sleepTime=1000
MILLISECONDS)
17/01/26 03:39:56 WARN ipc.Client: Failed to connect to server:
/:8020: retries get failed due to
exceeded maximum allowed retries number: 1
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
at
org.apache.hadoop.net.SocketIOWithTimeout.connect(SocketIOWithTimeout.java:206)
at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:531)
at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:495)
at
org.apache.hadoop.ipc.Client$Connection.setupConnection(Client.java:650)
at
org.apache.hadoop.ipc.Client$Connection.setupIOstreams(Client.java:745)
at org.apache.hadoop.ipc.Client$Connection.access$3200(Client.java:397)
at org.apache.hadoop.ipc.Client.getConnection(Client.java:1618)
at org.apache.hadoop.ipc.Client.call(Client.java:1449)
at org.apache.hadoop.ipc.Client.call(Client.java:1396)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:233)
at com.sun.proxy.$Proxy8.getServiceStatus(Unknown Source)
at
org.apache.hadoop.ha.protocolPB.HAServiceProtocolClientSideTranslatorPB.getServiceStatus(HAServiceProtocolClientSideTranslatorPB.java:122)
at org.apache.hadoop.ha.HAAdmin.getServiceState(HAAdmin.java:359)
at org.apache.hadoop.ha.HAAdmin.runCmd(HAAdmin.java:457)
at org.apache.hadoop.hdfs.tools.DFSHAAdmin.runCmd(DFSHAAdmin.java:120)
at org.apache.hadoop.ha.HAAdmin.run(HAAdmin.java:384)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:90)
at org.apache.hadoop.hdfs.tools.DFSHAAdmin.main(DFSHAAdmin.java:132)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19661) Kafka Brokers go down after Wire Encryption
Vivek Rathod created AMBARI-19661: - Summary: Kafka Brokers go down after Wire Encryption Key: AMBARI-19661 URL: https://issues.apache.org/jira/browse/AMBARI-19661 Project: Ambari Issue Type: Bug Affects Versions: 2.5.0 Environment: Centos7, Wire Encryption =yes, Customized service users = yes Reporter: Vivek Rathod Fix For: 2.5.0 Kafka Brokers go down after Wire Encryption. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19472) Service Checks getting timed out after Wire Encryption
[
https://issues.apache.org/jira/browse/AMBARI-19472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Rathod updated AMBARI-19472:
--
Description:
Service Checks getting timed out after Wire Encryption. Seeing some deployments
failing because of this. It is intermittent
{code}
Python script has been killed due to timeout after waiting 300 secs
{code}
was:
Service Checks getting timed out after Wire Encryption. Seeing some deployments
in ambari system tests failing because of this issue
{code}
Python script has been killed due to timeout after waiting 300 secs
{code}
> Service Checks getting timed out after Wire Encryption
> --
>
> Key: AMBARI-19472
> URL: https://issues.apache.org/jira/browse/AMBARI-19472
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
> Fix For: 2.5.0
>
>
> Service Checks getting timed out after Wire Encryption. Seeing some
> deployments failing because of this. It is intermittent
> {code}
> Python script has been killed due to timeout after waiting 300 secs
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19472) Service Checks getting timed out after Wire Encryption
Vivek Rathod created AMBARI-19472:
-
Summary: Service Checks getting timed out after Wire Encryption
Key: AMBARI-19472
URL: https://issues.apache.org/jira/browse/AMBARI-19472
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.5.0
Reporter: Vivek Rathod
Fix For: 2.5.0
Service Checks getting timed out after Wire Encryption. Seeing some deployments
in ambari system tests failing because of this issue
{code}
Python script has been killed due to timeout after waiting 300 secs
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19390) AMS Collector works in HTTP mode after setting ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY
Vivek Rathod created AMBARI-19390: - Summary: AMS Collector works in HTTP mode after setting ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY Key: AMBARI-19390 URL: https://issues.apache.org/jira/browse/AMBARI-19390 Project: Ambari Issue Type: Bug Affects Versions: 2.5.0 Reporter: Vivek Rathod Fix For: 2.5.0 AMS Collector works in HTTP mode after setting ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19245) Smartsense Install fails while installing cluster with Blueprint with Customized Service Users
Vivek Rathod created AMBARI-19245:
-
Summary: Smartsense Install fails while installing cluster with
Blueprint with Customized Service Users
Key: AMBARI-19245
URL: https://issues.apache.org/jira/browse/AMBARI-19245
Project: Ambari
Issue Type: Bug
Affects Versions: 2.5.0
Reporter: Vivek Rathod
Fix For: 2.5.0
Smartsense Install fails while installing cluster with Blueprint with
Customized Service User
{code}
Execution of 'useradd -m -G cstm-hdfs -g hadoop activity_analyzer' returned 6.
useradd: group 'cstm-hdfs' does not exist
{code}
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_agent.py",
line 22, in
HSTScript('agent').execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 282, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_script.py",
line 48, in install
self.deploy_component_specific_config(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_script.py",
line 360, in deploy_component_specific_config
self.create_activity_user()
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_script.py",
line 516, in create_activity_user
groups = params.config['configurations']['hadoop-env']['hdfs_user']
File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
line 155, in __init__
self.env.run()
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 124, in run_action
provider_action()
File
"/usr/lib/python2.6/site-packages/resource_management/core/providers/accounts.py",
line 82, in action_create
shell.checked_call(command, sudo=True)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 72, in inner
result = function(command, **kwargs)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 102, in checked_call
tries=tries, try_sleep=try_sleep,
timeout_kill_strategy=timeout_kill_strategy)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 150, in _call_wrapper
result = _call(command, **kwargs_copy)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 303, in _call
raise ExecutionFailed(err_msg, code, out, err)
resource_management.core.exceptions.ExecutionFailed: Execution of 'useradd -m
-G cstm-hdfs -g hadoop activity_analyzer' returned 6. useradd: group
'cstm-hdfs' does not exist
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_agent.py",
line 22, in
HSTScript('agent').execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 282, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_script.py",
line 48, in install
self.deploy_component_specific_config(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_script.py",
line 360, in deploy_component_specific_config
self.create_activity_user()
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_script.py",
line 516, in create_activity_user
groups = params.config['configurations']['hadoop-env']['hdfs_user']
File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
line 155, in __init__
self.env.run()
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 124, in run_action
provider_action()
File
"/usr/lib/python2.6/site-packages/resource_management/core/providers/accounts.py",
line 82, in action_create
shell.checked_call(command, sudo=True)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 72, in inner
result = function(command, **kwargs)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 102, in checked_call
tries=tries, try_sleep=try_sleep,
timeout_kill_strategy=timeout_kill_strategy)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 150, in _call_wrapper
result = _call(command, **kwargs_copy)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 303, in _call
raise ExecutionFailed(err_msg, code, out, err)
[jira] [Created] (AMBARI-19182) Config Groups: Save button not enabled while trying to overwrite configs
Vivek Rathod created AMBARI-19182: - Summary: Config Groups: Save button not enabled while trying to overwrite configs Key: AMBARI-19182 URL: https://issues.apache.org/jira/browse/AMBARI-19182 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Vivek Rathod Fix For: 2.5.0 STR: -> For a service, create a config group -> Go to configs page, select the config group. Now try to overwrite a config, Save button is not enabled here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19180) Service Flume failed to start with "cannot open /grid/0/log/flume/a1.out for reading: Permission denied"
Vivek Rathod created AMBARI-19180:
-
Summary: Service Flume failed to start with "cannot open
/grid/0/log/flume/a1.out for reading: Permission denied"
Key: AMBARI-19180
URL: https://issues.apache.org/jira/browse/AMBARI-19180
Project: Ambari
Issue Type: Bug
Affects Versions: 2.5.0
Reporter: Vivek Rathod
Fix For: 2.5.0
STR:
-> Delete the following services on the cluster : Flume, Atlas, Hbase, Sqoop,
Storm, Knox, AMS
-> Add them back using add service wizard
Flume fails to start with
{noformat}
2016-12-12 03:47:12,623 - Execute['ambari-sudo.sh su cstm-flume -l -s /bin/bash
-c 'export
PATH='"'"'/usr/sbin:/sbin:/usr/lib/ambari-server/*:/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/agentslava/bin:/var/lib/ambari-agent'"'"'
JAVA_HOME=/usr/jdk64/jdk1.8.0_77 ; /usr/hdp/current/flume-server/bin/flume-ng
agent --name a1 --conf /usr/hdp/current/flume-server/conf/a1 --conf-file
/usr/hdp/current/flume-server/conf/a1/flume.conf
-Dflume.monitoring.type=org.apache.hadoop.metrics2.sink.flume.FlumeTimelineMetricsSink
-Dflume.monitoring.node=ctr-e64-1480733150053-10989-01-02.hwx.site:6188 >
/grid/0/log/flume/a1.out 2>&1' &'] {'environment': {'JAVA_HOME':
'/usr/jdk64/jdk1.8.0_77'}, 'wait_for_finish': False}
2016-12-12 03:47:12,640 - Execute['ambari-sudo.sh -H -E pgrep -o -u cstm-flume
-f '^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
/var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0'] {'logoutput': True,
'tries': 20, 'try_sleep': 10}
2016-12-12 03:47:12,667 - Retrying after 10 seconds. Reason: Execution of
'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
'^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
/var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
2016-12-12 03:47:22,706 - Retrying after 10 seconds. Reason: Execution of
'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
'^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
/var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
2016-12-12 03:47:32,748 - Retrying after 10 seconds. Reason: Execution of
'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
'^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
/var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
2016-12-12 03:47:42,791 - Retrying after 10 seconds. Reason: Execution of
'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
'^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
/var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
2016-12-12 03:47:52,835 - Retrying after 10 seconds. Reason: Execution of
'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
'^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
/var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
2016-12-12 03:48:02,880 - Retrying after 10 seconds. Reason: Execution of
'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
'^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
/var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
2016-12-12 03:48:12,926 - Retrying after 10 seconds. Reason: Execution of
'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
'^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
/var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
2016-12-12 03:48:22,974 - Retrying after 10 seconds. Reason: Execution of
'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
'^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
/var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
2016-12-12 03:48:33,021 - Retrying after 10 seconds. Reason: Execution of
'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
'^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
/var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
2016-12-12 03:48:43,063 - Retrying after 10 seconds. Reason: Execution of
'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
'^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
/var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
2016-12-12 03:48:53,104 - Retrying after 10 seconds. Reason: Execution of
'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
'^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
/var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
2016-12-12 03:49:03,153 - Retrying after 10 seconds. Reason: Execution of
'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
'^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
/var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
2016-12-12 03:49:13,191 - Retrying after 10 seconds. Reason: Execution of
'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
'^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
/var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
2016-12-12 03:49:23,237 - Retrying
[jira] [Created] (AMBARI-19159) Namenode went down after enabling NNHA
Vivek Rathod created AMBARI-19159: - Summary: Namenode went down after enabling NNHA Key: AMBARI-19159 URL: https://issues.apache.org/jira/browse/AMBARI-19159 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Vivek Rathod Fix For: 2.5.0 After enabling NNHA, One of the Namenodes went down STR: 1) Enable NNHA with 4 Journalnodes 2) Stop All/Start all services After that one of the namenodes went down one host -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19145) Namenodes failed to start while adding a Jouralnode
Vivek Rathod created AMBARI-19145:
-
Summary: Namenodes failed to start while adding a Jouralnode
Key: AMBARI-19145
URL: https://issues.apache.org/jira/browse/AMBARI-19145
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.5.0
Reporter: Vivek Rathod
Fix For: 2.5.0
STR:
1) Install cluster and Enable HA with 3 Journalnodes
2) Add a Journal node using manage JN wizard (This goes through fine)
3) Add another Journal node
This time go to hosts page, and click add component-> JN and use the manage JN
wizard
Namenodes fail to start in the final step.
Both the namenodes fail to connect to each other
{noformat}
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
at
org.apache.hadoop.net.SocketIOWithTimeout.connect(SocketIOWithTimeout.java:206)
at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:531)
at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:495)
at
org.apache.hadoop.ipc.Client$Connection.setupConnection(Client.java:650)
at
org.apache.hadoop.ipc.Client$Connection.setupIOstreams(Client.java:745)
at org.apache.hadoop.ipc.Client$Connection.access$3200(Client.java:397)
at org.apache.hadoop.ipc.Client.getConnection(Client.java:1618)
at org.apache.hadoop.ipc.Client.call(Client.java:1449)
at org.apache.hadoop.ipc.Client.call(Client.java:1396)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:233)
at com.sun.proxy.$Proxy8.getServiceStatus(Unknown Source)
at
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19115) Metrics Monitor start failed: ERROR: Cannot write pid /grid/0/pid/metric_monitor/ambari-metrics-monitor.pid
Vivek Rathod created AMBARI-19115:
-
Summary: Metrics Monitor start failed: ERROR: Cannot write pid
/grid/0/pid/metric_monitor/ambari-metrics-monitor.pid
Key: AMBARI-19115
URL: https://issues.apache.org/jira/browse/AMBARI-19115
Project: Ambari
Issue Type: Bug
Affects Versions: 2.5.0
Reporter: Vivek Rathod
Fix For: 2.5.0
STR: Install cluster with 4 services: HDFS, Flume, AMS and Smartsense, with
custom PID's
Metrics Monitor start fails while starting services
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_monitor.py",
line 68, in
AmsMonitor().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 282, in execute
method(env)
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_monitor.py",
line 42, in start
action = 'start'
File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
line 89, in thunk
return fn(*args, **kwargs)
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams_service.py",
line 103, in ams_service
user=params.ams_user
File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
line 155, in __init__
self.env.run()
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 124, in run_action
provider_action()
File
"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
line 262, in action_run
tries=self.resource.tries, try_sleep=self.resource.try_sleep)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 72, in inner
result = function(command, **kwargs)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 102, in checked_call
tries=tries, try_sleep=try_sleep,
timeout_kill_strategy=timeout_kill_strategy)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 150, in _call_wrapper
result = _call(command, **kwargs_copy)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 303, in _call
raise ExecutionFailed(err_msg, code, out, err)
resource_management.core.exceptions.ExecutionFailed: Execution of
'/usr/sbin/ambari-metrics-monitor --config /etc/ambari-metrics-monitor/conf
start' returned 1. Hortonworks #
This is MOTD message, added for testing in qe infra
Building psutil...
running build
running build_py
creating build/lib.linux-x86_64-2.6
creating build/lib.linux-x86_64-2.6/psutil
copying psutil/__init__.py -> build/lib.linux-x86_64-2.6/psutil
copying psutil/_common.py -> build/lib.linux-x86_64-2.6/psutil
copying psutil/_compat.py -> build/lib.linux-x86_64-2.6/psutil
copying psutil/_psbsd.py -> build/lib.linux-x86_64-2.6/psutil
copying psutil/_pslinux.py -> build/lib.linux-x86_64-2.6/psutil
copying psutil/_psosx.py -> build/lib.linux-x86_64-2.6/psutil
copying psutil/_psposix.py -> build/lib.linux-x86_64-2.6/psutil
copying psutil/_pssunos.py -> build/lib.linux-x86_64-2.6/psutil
copying psutil/_pswindows.py -> build/lib.linux-x86_64-2.6/psutil
running build_ext
building '_psutil_linux' extension
creating build/temp.linux-x86_64-2.6
creating build/temp.linux-x86_64-2.6/psutil
gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic
-D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic
-D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/usr/include/python2.6 -c
psutil/_psutil_linux.c -o build/temp.linux-x86_64-2.6/psutil/_psutil_linux.o
psutil/_psutil_linux.c: In function ‘psutil_proc_cpu_affinity_set’:
psutil/_psutil_linux.c:327: warning: suggest explicit braces to avoid ambiguous
‘else’
gcc -pthread -shared build/temp.linux-x86_64-2.6/psutil/_psutil_linux.o
-L/usr/lib64 -lpython2.6 -o build/lib.linux-x86_64-2.6/_psutil_linux.so
building '_psutil_posix' extension
gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic
-D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic
-D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/usr/include/python2.6 -c
psutil/_psutil_posix.c -o build/temp.linux-x86_64-2.6/psutil/_psutil_posix.o
gcc -pthread -shared build/temp.linux-x86_64-2.6/psutil/_psutil_posix.o
-L/usr/lib64 -lpython2.6 -o
[jira] [Updated] (AMBARI-19089) Manage Journalnode Wizard is stuck at Add/Remove JournalNodes 2 of 310 Return to search
[ https://issues.apache.org/jira/browse/AMBARI-19089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod updated AMBARI-19089: -- Attachment: Screen Shot 2016-12-05 at 1.47.33 PM.png > Manage Journalnode Wizard is stuck at Add/Remove JournalNodes 2 of 310 > Return to search > > > Key: AMBARI-19089 > URL: https://issues.apache.org/jira/browse/AMBARI-19089 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Rathod > Fix For: 2.5.0 > > Attachments: Screen Shot 2016-12-05 at 1.47.33 PM.png > > > Manage Journalnode Wizard is stuck at Add/Remove JournalNodes. > This occured while running the test on firefox (version 29.0) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19089) Manage Journalnode Wizard is stuck at Add/Remove JournalNodes 2 of 310 Return to search
Vivek Rathod created AMBARI-19089: - Summary: Manage Journalnode Wizard is stuck at Add/Remove JournalNodes 2 of 310 Return to search Key: AMBARI-19089 URL: https://issues.apache.org/jira/browse/AMBARI-19089 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Vivek Rathod Fix For: 2.5.0 Manage Journalnode Wizard is stuck at Add/Remove JournalNodes. This occured while running the test on firefox (version 29.0) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19059) Falcon quicklinks combobox is absent
[ https://issues.apache.org/jira/browse/AMBARI-19059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod updated AMBARI-19059: -- Attachment: screenshot-1.png > Falcon quicklinks combobox is absent > > > Key: AMBARI-19059 > URL: https://issues.apache.org/jira/browse/AMBARI-19059 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Rathod > Fix For: 2.5.0 > > Attachments: screenshot-1.png > > > Falcon quicklinks combobox is absent -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19059) Falcon quicklinks combobox is absent
[ https://issues.apache.org/jira/browse/AMBARI-19059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod updated AMBARI-19059: -- Description: Falcon quicklinks combobox is absent was:Falcon quicklinks combobox is absent > Falcon quicklinks combobox is absent > > > Key: AMBARI-19059 > URL: https://issues.apache.org/jira/browse/AMBARI-19059 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Rathod > Fix For: 2.5.0 > > > Falcon quicklinks combobox is absent -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19059) Falcon quicklinks combobox is absent
Vivek Rathod created AMBARI-19059: - Summary: Falcon quicklinks combobox is absent Key: AMBARI-19059 URL: https://issues.apache.org/jira/browse/AMBARI-19059 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Vivek Rathod Fix For: 2.5.0 Falcon quicklinks combobox is absent -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19041) Choose services page select/deselect all services not working while adding smartsense to the cluster
[ https://issues.apache.org/jira/browse/AMBARI-19041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod updated AMBARI-19041: -- Description: Smartsense is mandatory install. But UI and API allows user to delete it. After deleting smartsense, on adding smartsense, on choose services page, select/deselect all button does not work as expected. was: User should not be able to delete Smartsense from UI or API because it is mandatory in ambari 250. Also, after deleting Smartsense, Choose services page on add service wizard is broken(Select/Deselect All button does not work as designed). > Choose services page select/deselect all services not working while adding > smartsense to the cluster > > > Key: AMBARI-19041 > URL: https://issues.apache.org/jira/browse/AMBARI-19041 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Rathod > Fix For: 2.5.0 > > > Smartsense is mandatory install. But UI and API allows user to delete it. > After deleting smartsense, on adding smartsense, on choose services page, > select/deselect all button does not work as expected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19041) Choose services page select/deselect all services not working while adding smartsense to the cluster
[ https://issues.apache.org/jira/browse/AMBARI-19041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod updated AMBARI-19041: -- Summary: Choose services page select/deselect all services not working while adding smartsense to the cluster (was: User should not be able to delete Smartsense(from UI or API) as it is mandatory) > Choose services page select/deselect all services not working while adding > smartsense to the cluster > > > Key: AMBARI-19041 > URL: https://issues.apache.org/jira/browse/AMBARI-19041 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Rathod > Fix For: 2.5.0 > > > User should not be able to delete Smartsense from UI or API because it is > mandatory in ambari 250. > Also, after deleting Smartsense, Choose services page on add service wizard > is broken(Select/Deselect All button does not work as designed). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19041) User should not be able to delete Smartsense(from UI or API) as it is mandatory
Vivek Rathod created AMBARI-19041: - Summary: User should not be able to delete Smartsense(from UI or API) as it is mandatory Key: AMBARI-19041 URL: https://issues.apache.org/jira/browse/AMBARI-19041 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Vivek Rathod Fix For: 2.5.0 User should not be able to delete Smartsense from UI or API because it is mandatory in ambari 250. Also, after deleting Smartsense, Choose services page on add service wizard is broken(Select/Deselect All button does not work as designed). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19021) Ambari server java process died with exit code 134 after setting up Ambari kerberos JAAS configuration
Vivek Rathod created AMBARI-19021:
-
Summary: Ambari server java process died with exit code 134 after
setting up Ambari kerberos JAAS configuration
Key: AMBARI-19021
URL: https://issues.apache.org/jira/browse/AMBARI-19021
Project: Ambari
Issue Type: Bug
Affects Versions: 2.5.0
Reporter: Vivek Rathod
Fix For: 2.5.0
Ambari server java process died with exit code 134 after setting up Ambari
kerberos JAAS configuration. While enabling SPNEGO Authentication, after
setting up JAAS configuration, ambari server restart failed with exitcode 134.
On performing the ambari server setup and start manually on the same cluster,
everything went through fine and the ambari server is now running on the
cluster. This may be an intermittent issue.
{noformat}
2016-11-29 06:12:51,092 DEBUG
com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
Sending commands to host :
2016-11-29 06:12:51,092 DEBUG
com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
Sending command [ambari-server setup-security]
2016-11-29 06:12:51,093 DEBUG
com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
Sending command [3]
2016-11-29 06:12:51,093 DEBUG
com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
Sending command [ambari-qa-...@example.com]
2016-11-29 06:12:51,093 DEBUG
com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
Sending command [/etc/security/keytabs/smokeuser.headless.keytab]
2016-11-29 06:12:51,795 DEBUG
com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
[OUTPUT STREAM]
Using python /usr/bin/python
Security setup options...
===
Choose one of the following options:
[1] Enable HTTPS for Ambari server.
[2] Encrypt passwords stored in ambari.properties file.
[3] Setup Ambari kerberos JAAS configuration.
[4] Setup truststore.
[5] Import certificate to truststore.
===
Enter choice, (1-5): Setting up Ambari kerberos JAAS configuration to access
secured Hadoop daemons...
Enter ambari server's kerberos principal name (amb...@example.com): Enter
keytab path for ambari server's kerberos principal: Ambari Server
'setup-security' completed successfully.
[ERROR STREAM]
[EXIT CODE]
0
2016-11-29 06:12:51,796 INFO
com.hw.ambari.ui.tests.console.TestConfigureHTTPSpnegoAuthentication.changeKRB5_JAASLOGIN_CONF():
[Finished]
2016-11-29 06:12:51,797 INFO
com.hw.ambari.ui.util.cluster_managers.AmbariManager.getStartAmbariServerCommand():
Trying to restart Ambari server ...
2016-11-29 06:12:51,798 DEBUG
com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
Sending commands to host :
2016-11-29 06:12:51,798 DEBUG
com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
Sending command [ambari-server restart --debug]
2016-11-29 06:12:52,700 DEBUG
com.hw.ambari.ui.util.cluster_managers.ProcessData.buildOutputAndErrorStreamData():
sh: line 1: 419471 Aborted /usr/jdk64/jdk1.8.0_77/bin/java
-server -XX:NewRatio=2 -XX:+UseConcMarkSweepGC -Xms512m -Xmx2048m
-XX:MaxPermSize=128m
-Djava.security.auth.login.config=$ROOT/etc/ambari-server/conf/krb5JAASLogin.conf
-Djava.security.krb5.conf=/etc/krb5.conf -Djavax.securit
2016-11-29 06:12:52,701 DEBUG
com.hw.ambari.ui.util.cluster_managers.ProcessData.buildOutputAndErrorStreamData():
y.auth.useSubjectCredsOnly=false -Xdebug
-Xrunjdwp:transport=dt_socket,address=5005,server=y,suspend=n -cp
/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/mysql-connector-java.jar
org.apache.ambari.server.controller.AmbariServer >
/var/log/ambari-server/ambari-server.out 2>&1
2016-11-29 06:13:03,521 DEBUG
com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
[OUTPUT STREAM]
Using python /usr/bin/python
Restarting ambari-server
Ambari Server stopped
Ambari Server running with administrator privileges.
Organizing resource files at /var/lib/ambari-server/resources...
Ambari database consistency check started...
Server PID at: /var/run/ambari-server/ambari-server.pid
Server out at: /var/log/ambari-server/ambari-server.out
Server log at: /var/log/ambari-server/ambari-server.log
Waiting for server start.
DB configs consistency check: no errors and warnings were found.
ERROR: Exiting with exit code -1.
REASON: Ambari Server java process died with exitcode 134. Check
/var/log/ambari-server/ambari-server.out for more information.
[ERROR STREAM]
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18867) Field spark.history.kerberos.principal is not present on Configure Identities page
Vivek Rathod created AMBARI-18867: - Summary: Field spark.history.kerberos.principal is not present on Configure Identities page Key: AMBARI-18867 URL: https://issues.apache.org/jira/browse/AMBARI-18867 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Vivek Rathod Fix For: 2.5.0 Field spark.history.kerberos.principal is not present on Configure Identities page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18856) Manage JournalNode Wizard: If nothing changes in step 1, next button should not be enabled
Vivek Rathod created AMBARI-18856: - Summary: Manage JournalNode Wizard: If nothing changes in step 1, next button should not be enabled Key: AMBARI-18856 URL: https://issues.apache.org/jira/browse/AMBARI-18856 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Vivek Rathod Fix For: 2.5.0 In Manage JournalNode Wizard, If nothing changes in step 1, next button should not be enabled -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18855) Manage JournalNode Wizard: While assigning new JournalNodes, Current JournalNode selection value changes
Vivek Rathod created AMBARI-18855: - Summary: Manage JournalNode Wizard: While assigning new JournalNodes, Current JournalNode selection value changes Key: AMBARI-18855 URL: https://issues.apache.org/jira/browse/AMBARI-18855 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Vivek Rathod Fix For: 2.5.0 STR: While in Manage journalNode wizard, step 1 -> Click on add journal nodes button 2-3 times. The values in current journalnode selection changes, but the it should not change. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18775) Host Page filter not working properly
[ https://issues.apache.org/jira/browse/AMBARI-18775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Rathod updated AMBARI-18775: -- Description: STR: Go to hosts page and filter by Resourcemanager. The hosts filtered does not contain resourcemanager. was: STR: Go to hosts page and filter by Resourcemanager. The hosts filtered does not contain resourcemanager. Please find attached screenshots. > Host Page filter not working properly > - > > Key: AMBARI-18775 > URL: https://issues.apache.org/jira/browse/AMBARI-18775 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Vivek Rathod > Fix For: 2.4.2 > > > STR: > Go to hosts page and filter by Resourcemanager. The hosts filtered does not > contain resourcemanager. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
