All, It looks like our device "man in the middle" is the cause of our issue.  Curl and WGet are rejecting the internal cert that's being passed back.   Now, i need to figure out how to get the parcels to a create a local repo.   Thanks, DataCowboy ... View more

Consult, Test Command: curl https://archive.cloudera.com/cm5/redhat/7/x86_64/cm/5.5.1/repodata/repomd.xml   Here is the output from curl command: curl: (60) Peer's Certificate issuer is not recognized. More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. ... View more

That's correct, I'm doing a basic setup using Cloudera Manager.  Here are the steps I've taken so far.   1. Verified i can access the archive locations from the server.  - check 2. Executed yum clean all - check 3. Retry cluster install using CM 5.5.1 - no joy 4. Rebuilt centos 7 servers 5. Verified access to archive locations from server - check   Interestingly, when i tried to build a local repository using yum commands, i received the same "Peer's issuer certificate is not authorized" error.   ... View more