(Cloudera manager) : Issues while adding hosts to cluster in production env. CDH Cloudera Manager Version 5.13.1

[#1]

Hi All,

We are facing an issue while adding new host to Cloudera manger.

During host installation, Cloudera manager is replacing the /etc/yum.repos.d/cloudera-manager.repo file.

The original repo file on server has the required Cloudera credentials to downlaod packages from Cloudera archive. --------

$ cat cloudera-manager.repo [cloudera-manager] name = Cloudera Manager, Version 5.13.1 #baseurl = https://archive.cloudera.com/cm5/redhat/7/x86_64/cm/5.13.1/ #gpgkey = https://archive.cloudera.com/redhat/cdh/RPM-GPG-KEY-cloudera baseurl = https://7bf0xxxx-xxxx-xxxxxxb236:15xxxxxxxxxc9@archive.cloudera.com/cm5/redhat/7/x86_64/cm/5.13.1/ gpgkey = https://7bf0xxxx-xxxx-xxxxxxb236:15xxxxxxxxxc9@archive.cloudera.com/redhat/cdh/RPM-GPG-KEY-cloudera gpgcheck = 1 --------

Now when we try to add this host in Cloudera manager, during installation phase the file Cloudera-manager.repo is replaced.

Due to this we are observing authentication failures.

[#2]

@Satyajit Do you have same repo with credentials on CM server host as well or not? I am guessing the CM server have the repo file without credentials. 

Also follow the doc to add new host : https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/cm_mc_adding_hosts.html#cmug_topic_7...

[#3]

@GangWar  Thank you for reply, checking with the customer on this, will update , if i will still require any info on this.

[#4]

@Satyajit 

Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.

Thanks in advance

[#5]

Hello, The issue is still pending. We are still now able to add the host via CM.

CM version is 5.13.1. We tried modifying the repo files as well but did not help either. It is getting modified again back to the previous one. 

[#6]

During host installation, cloudera manager is replacing the /etc/yum.repos.d/cloudera-manager.repo file.

The original repo file on server has the required cloudera credentials to download the packages from cloudera archive.

--------
$ cat cloudera-manager.repo
[cloudera-manager]
name = Cloudera Manager, Version 5.13.1
#baseurl = https://archive.cloudera.com/cm5/redhat/7/x86_64/cm/5.13.1/
#gpgkey = https://archive.cloudera.com/redhat/cdh/RPM-GPG-KEY-cloudera
baseurl = https://7bf0xxxx-xxxx-xxxxxxb236:15xxxxxxxxxc9@archive.cloudera.com/cm5/redhat/7/x86_64/cm/5.13.1/
gpgkey = https://7bf0xxxx-xxxx-xxxxxxb236:15xxxxxxxxxc9@archive.cloudera.com/redhat/cdh/RPM-GPG-KEY-cloudera
gpgcheck = 1

--------

Now when we try to add this host in cloudera manager, during installation phase the file cloudera-manager.repo is replaced. Due to this we are observing authentication failures.

We think /tmp/scm_prepare_node.uERRAndo/scm_prepare_node.sh script replaces the repo as per the logs.

Updated contents
---------------
$cat cloudera-manager.repo
[cloudera-manager]
name = Cloudera Manager, Version 5.13.1
baseurl = https://archive.cloudera.com/cm5/redhat/7/x86_64/cm/5.13.1/
gpgkey = https://archive.cloudera.com/redhat/cdh/RPM-GPG-KEY-cloudera
gpgcheck = 1

-------------

This would be an issue as it prevents us from adding new hosts in case of failures in existing cluster.

[#7]

@PritamToshniwal An obvious discrepancy I noticed that "/p" is missing from URL. The url should be something like this. 

baseurl = https://7bf0xxxx-xxxx-xxxxxxb236:15xxxxxxxxxc9@archive.cloudera.com/p/cm5/redhat/7/x86_64/cm/5.13.1/

Try to modify this and restart CM server. Let us how it goes.