As it turns out these force skips were due to the cloudera-manager.repo file being altered during initial installation of this cluster to make sure it didnt get updated.  After editing this file back to default everything started to work as normal. ... View more

Thank you very much for the reply.  I apologize but I havent had time to get through this until now.  When searching for available updates I am getting the following:   yum list available | grep -i cloudera-manager- Repo rhel-server-dts2-6-rpms forced skip_if_unavailable=True due to: /etc/rhsm/ca/redhat-uep.pem Repo rhel-server-dts2-6-rpms forced skip_if_unavailable=True due to: /etc/pki/entitlement/8878952237103311606-key.pem Repo rhel-server-dts-6-rpms forced skip_if_unavailable=True due to: /etc/rhsm/ca/redhat-uep.pem Repo rhel-server-dts-6-rpms forced skip_if_unavailable=True due to: /etc/pki/entitlement/8878952237103311606-key.pem Repo rhel-6-server-rpms forced skip_if_unavailable=True due to: /etc/rhsm/ca/redhat-uep.pem Repo rhel-6-server-rpms forced skip_if_unavailable=True due to: /etc/pki/entitlement/8878952237103311606-key.pem Repo rhel-6-server-eus-rpms forced skip_if_unavailable=True due to: /etc/rhsm/ca/redhat-uep.pem Repo rhel-6-server-eus-rpms forced skip_if_unavailable=True due to: /etc/pki/entitlement/8878952237103311606-key.pem   Not certain why the update would be unavailable across all repos.  I am running RHEL 6.5.  Everything seemed to work normally up until this point. ... View more

Thank you very much for your reply!  I do not have any data that is important in this environment.  In this cluster I am running RHEL 6.5.   I have also found, perhaps, a little more information:  There is a parcel available to move to 5.12.1-1.  I can distribute and activate this.  However, if I do, HDFS becomes unhappy and will not allow be to finalize.  After looking into the steps of updating HDFS it seems as or more complicated than where I am with updating CM.  The error that I am getting with HDFS is:   2014-03-13 23:38:15,488 FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in namenode join java.io.IOException: File system image contains an old layout version -40. An upgrade to version -47 is required. Please restart NameNode with -upgrade option. at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:221) at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:787) at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:568) at org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:443) at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:491) at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:684) at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:669) at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1254) at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1320) 2014-03-13 23:38:15,492 INFO org.apache.hadoop.util.ExitUtil: Exiting with status 1 2014-03-13 23:38:15,493 INFO org.apache.hadoop.hdfs.server.namenode.NameNode: SHUTDOWN_MSG: /************************************************************ SHUTDOWN_MSG: Shutting down NameNode at nn1/192.168.2.202 ************************************************************/ ~ This is arbitrary sample data as I have already rolled back and cleared these errors but where this says -40 mine said -59 and required -60. ... View more