Created 08-29-2017 05:28 AM
I ran into an error while distributing a custom built parcel. It can be reproduced with an empty parcel as well. Steps to reproduce:
tar czvf Dummy-0.0.1-el7.parcel Dummy-0.0.1 sha1sum Dummy-0.0.1-el7.parcel | cut -d ' ' -f 1 > Dummy-0.0.1-el7.parcel.sha cp Dummy-0.0.1-el7.parcel* /opt/cloudera/parcel-repo/
An obvious workaround is to simply update the parcel version once more and deploy it without making the stupid mistake I've made, but it still seems like a bug to me. At least, the behaviour and the error message are not very intuitive.
Created 05-13-2020 09:33 PM
It is a bit of an old post however nothing has changed in the CDP 7.1. Still the same behavior. Is the parcel getting cached somewhere?
Created 05-14-2020 10:05 AM
@denys_tyshetsky , since this is an old topic, we recommend you create a new post with the CDP label added. There is a higher chance of your query being addressed by our experts when it is a new post and has relevant labels.
Created 09-15-2020 08:28 PM
This problem still exists. There has to be a copy of the old manifest.json stored somewhere.
Created 09-15-2020 09:31 PM
I found the following article (from SAP): https://help.sap.com/viewer/6437091bdb1145d9be06aeec79f06363/126.96.36.199/en-US/fe6cf78e25904e6b8167a1b16...
They did mention a hidden directory .flood under /opt/cloudera/parcels. However, following the steps in the article didn't help either. I still got the error:
"Ignoring parcel with inconsistent naming. Directory: ..., Manifest: ..."