Failure to bootstrap cluster due to parcel error from CLI

velomcb — Fri, 16 Sep 2022 15:43:51 GMT

Attempting to bootstrap a Java8 cluster from the CLI. Everything seems to go well, and then this happens:

* Waiting for Cloudera Manager installation to complete .................. done
* Installing Cloudera Manager agents on all instances in parallel (20 at a time) .................................... done
* Creating CDH5 cluster using the new instances ... done
* Creating cluster: cdh-java8-test ........................................................... done
* java.lang.IllegalArgumentException: CDH=5.9.1-1.cdh5.9.1.p0.4 not found in list of all parcels. ...

The problem appears to be that for some reason the parcel name its looking for has an equal sign instead of a dash in it. I'm not sure how this is happening, here's the snippet of my conf file that tells it the version (based on aws-simple.conf from Github):

products {
CDH: 5 # includes Impala and Spark
}

I do not have any parcel repo definitions in the conf file.

EDIT - I'm running Director 2.2.

Re: Failure to bootstrap cluster due to parcel error from CLI

velomcb — Fri, 10 Mar 2017 23:33:57 GMT

I've found reference to a similar problem with other versions, and the naming is normal. I'm going to verify that the CM instance has access to the Internet the next time I run a deploy.

Re: Failure to bootstrap cluster due to parcel error from CLI

velomcb — Sun, 12 Mar 2017 03:03:33 GMT

My AMI appears to have had a bad parcel preload. Removed all parcels on the AMI and deployed without incident.

question Failure to bootstrap cluster due to parcel error from CLI in Archives of Support Questions (Read Only)

Failure to bootstrap cluster due to parcel error from CLI

Re: Failure to bootstrap cluster due to parcel error from CLI

Re: Failure to bootstrap cluster due to parcel error from CLI