Having trouble provisioning new nodes after you have moved you cloudera manager installation to a new host ?

Moving an existing Cloudera Manager installation to a new host is pretty straight forward and well documented here. After restarting the cluster everything might seem fine, but you might encounter problems when you want to add new hosts. Because if your cluster is using some (outdated) parcels, the provisioning will fail as the parcels are no longer available on your cloudera manager host and on the cloudera repo server.

The default directory of the Cloudera Manager to keep its parcels is

/opt/cloudera/parcel-repo

Example:

ls -la /opt/cloudera/parcel

-rw-r----- 1 cloudera-scm cloudera-scm 1531811730  6. Jan 22:11 CDH-5.2.1-1.cdh5.2.1.p0.12-el6.parcel
-rw-r----- 1 cloudera-scm cloudera-scm         42  6. Jan 22:11 CDH-5.2.1-1.cdh5.2.1.p0.12-el6.parcel.sha

Copy everything in here to the new host and make sure to transfer the ownership of the directory and files to cloudera-scm:cloudera-scm.

If your old Cloudera Manager host no longer available, you should take a look at /opt/cloudera/parcel-cache on one of your cluster nodes for the parcel files. In that case the *.sha files need to be generate manually (sha1sum {file} > {file}.sha1).