You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Ishan Bhatt (JIRA)" <ji...@apache.org> on 2017/11/07 01:44:00 UTC
[jira] [Updated] (AMBARI-22372) DLM install failed on an unsecure
upgraded cluster, due to missing configs
[ https://issues.apache.org/jira/browse/AMBARI-22372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ishan Bhatt updated AMBARI-22372:
---------------------------------
Description:
On an upgraded unsecure cluster, dlm install fails , this could be due to some of the dependent configs missing:
Screen Shot 2017-10-27 at 4.14.39 PM.png
The missing configs can be found in the screenshot below (This cluster is a fresh install of hdp2.6.3 where the dlm add service succeeded)
Screen Shot 2017-10-27 at 18.32.05 (1).png
Add service of DLM works fine on a secure upgraded cluster as well as fresh install (no-upgrade) unsecure cluster
This is a multi-cluster environment (2 clusters)
Setup details:
ambari version before upgrade :2.5.2.0-298
ambari version after upgrade: 2.6.0.0-264
hdp version after upgrade :2.6.3.0-232
DLM mpack version : http://s3.amazonaws.com/dev.hortonworks.com/DLM/centos7/1.x/BUILDS/1.0.0.0-155/tars/beacon/beacon-ambari-mpack-1.0.0.0-155.tar.gz
was:
On an upgraded unsecure cluster, dlm install fails , this could be due to some of the dependent configs missing:
Screen Shot 2017-10-27 at 4.14.39 PM.png
The missing configs can be found in the screenshot below (This cluster is a fresh install of hdp2.6.3 where the dlm add service succeeded)
Screen Shot 2017-10-27 at 18.32.05 (1).png
Add service of DLM works fine on a secure upgraded cluster as well as fresh install (no-upgrade) unsecure cluster
This is a multi-cluster environment (2 clusters)
Setup details:
ambari version before upgrade :2.5.2.0-298
HDP version before upgrade: 2.5.6.0-40
ambari version after upgrade: 2.6.0.0-264
hdp version after upgrade :2.6.3.0-232
DLM mpack version : http://s3.amazonaws.com/dev.hortonworks.com/DLM/centos7/1.x/BUILDS/1.0.0.0-155/tars/beacon/beacon-ambari-mpack-1.0.0.0-155.tar.gz
gateway 1: http://172.27.20.84:8080 (were DLM installed failed) (DLM version
gateway 2 : http://172.27.38.73:8080 (Does not have DLM installed yet, because of the test failed after the failure in 1st cluster)
gateway 2 has beacon m-pack version beacon-ambari-mpack-1.0.0.0-161.tar.gz installed. On trying to reproduce the issue, we found the configs were missing, dlm is not installed on this cluster yet.
unsecure fresh cluster where dlm install has passed : (not upgraded)
http://172.22.86.136:8080/#/main/dashboard/metrics
artifacts link:http://logserver.eng.hortonworks.com/?prefix=qelogs/nat/70322/amb-multicluster-upg-dlm/split-1/amb-multicluster-upg-dlm--abilgi/
jenkins job :http://linux-jenkins.qe.hortonworks.com:8080/job/Nightly-Start-EC2-Run-HDP/671087/
> DLM install failed on an unsecure upgraded cluster, due to missing configs
> --------------------------------------------------------------------------
>
> Key: AMBARI-22372
> URL: https://issues.apache.org/jira/browse/AMBARI-22372
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.6.0
> Reporter: Ishan Bhatt
> Assignee: Ishan Bhatt
> Fix For: trunk, 2.6.1
>
>
> On an upgraded unsecure cluster, dlm install fails , this could be due to some of the dependent configs missing:
> Screen Shot 2017-10-27 at 4.14.39 PM.png
> The missing configs can be found in the screenshot below (This cluster is a fresh install of hdp2.6.3 where the dlm add service succeeded)
> Screen Shot 2017-10-27 at 18.32.05 (1).png
> Add service of DLM works fine on a secure upgraded cluster as well as fresh install (no-upgrade) unsecure cluster
> This is a multi-cluster environment (2 clusters)
> Setup details:
> ambari version before upgrade :2.5.2.0-298
> ambari version after upgrade: 2.6.0.0-264
> hdp version after upgrade :2.6.3.0-232
> DLM mpack version : http://s3.amazonaws.com/dev.hortonworks.com/DLM/centos7/1.x/BUILDS/1.0.0.0-155/tars/beacon/beacon-ambari-mpack-1.0.0.0-155.tar.gz
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)