Ignoring non-compliant parcel manifest:

@Deepak_Unravel Welcome to the Cloudera Community!

To help you get the best possible solution, I have tagged our Cloudera Manager experts @snm1523 @soychago  who may be able to assist you further.

Please keep us updated on your post, and we hope you find a satisfactory solution to your query.

Thanks , Looking for an response ASAP as its blocking us to deploy the parcels on CDP 719 .
just FYI . Cloudera manager version is : 7.11.3

@Deepak_Unravel is the unravel parcel deployed via CSD? It might not be compatible with the CM version you're using and the parcel.json or the manifest.json might not be working as expected.

Can you check if you have a "conflicts" entry in your parcel.json file? If so, can you try:

1.) Stopping a CM agent in the cdpvm1.unraveldata.com host

2.) In the same node where you stopped the CM agent, edit the parcel.json file and remove the "conflicts"

3.) Start the agent and check if the parcel is deployed.

@Deepak_Unravel 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.

@Deepak_Unravel 
This is a regression on the python3 upgrade or more specifically something that worked by mistake in the past. Before py3 avro used to be more flexible with it's schema's and used to ignore any extra fields. If a value didn't exist in the schema it could have any value without invalidating the parcel.

Now it expects data to be in exact format to the schema which is more accurate. During the py3 migration most fields were added but looks like we missed the conflicts field. A workaround for now can be to remove the conflicts field from the parcel since it doesn't have any conflicts right now.

Please remove the conflicts entry in /opt/cloudera/parcels/UNRAVEL_SENSOR-1.0.4791002_cdh7.1_h3.1_s2.4/meta/parcel.json file on all the agents.

Post conflicts entry removal you will able to distribute the parcel.