@Alfa6 Excuse me for the delayed update. I am catching up to speed here: In the meantime we would like to be sure that we will have not any regression about our software developed on CDP 7.1.1. I hope you did get a chance to review the Component Versions page on the CDP 7.1.1 vs. 7.1.9. If not already, Please do: CDP 7.1.1 Components Version: https://docs.cloudera.com/runtime/7.1.1/release-notes/topics/rt-runtime-component-versions.html CDP 7.1.9 Components Version: https://docs.cloudera.com/cdp-private-cloud-base/7.1.9/runtime-release-notes/topics/rt-pvc-runtime-component-versions.html Additionally, Since you are concerned about the Backward compatibility, You may want to read the deprecation notices for 7.1.9 too: https://docs.cloudera.com/cdp-private-cloud-base/7.1.9/runtime-release-notes/topics/rt-pvc-deprecated.html Let us know how you plan your CDP upgrade. We are here to help for the hassle-upgrade experience on your CDP! Cheers V ... View more

@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. ... View more

Thanks ymprakash I did the procedure indicated and was the solution ... View more

Hi, we got those errors while doing the stack patching, likely but guessing here that link is placed due to the cloudera stack?  ... View more