New Contributor
Posts: 1
Registered: ‎04-13-2018

Exception while reading parcel: CDH-5.10.2-1

I'm working to build a Virtualised 3 node test environment using:


Centos 7.3 Minimal build.

Anaconda 4.2.0

Spark2. 2.2.0

CDH 5.10.2-1

Java  jdk1.8.0_144

Plenty of Disk space

IP6 disabled

SELinux  Permissive

Using a local repository for parcel files


My build and deploy process fails when distributing/unpacking the CDH parcel. Anaconda and Spark distribute , install and activate with no problems. Checking the Agent log files I see the following.


[13/Apr/2018 12:52:23 +0000] 16047 Thread-13 parcel_cache INFO     Unpacking /opt/cloudera/parcels/.flood/CDH-5.10.2-1.cdh5.10.2.p0.5-el7.parcel/CDH-5.10.2-1.cdh5.10.2.p0.        5-el7.parcel into /opt/cloudera/parcels

[13/Apr/2018 12:52:56 +0000] 16047 MainThread parcel       INFO     Loading parcel manifest for: Anaconda-4.2.0

[13/Apr/2018 12:52:56 +0000] 16047 MainThread parcel       INFO     Loading parcel manifest for: SPARK2-2.2.0.cloudera1-1.cdh5.12.0.p0.142354

[13/Apr/2018 12:52:56 +0000] 16047 MainThread parcel       INFO     Loading parcel manifest for: CDH-5.10.2-1.cdh5.10.2.p0.5

[13/Apr/2018 12:52:56 +0000] 16047 MainThread parcel       ERROR    Exception while reading parcel: CDH-5.10.2-1.cdh5.10.2.p0.5

Traceback (most recent call last):

  File "/usr/lib64/cmf/agent/build/env/lib/python2.7/site-packages/cmf-5.10.2-py2.7.egg/cmf/", line 121, in refresh

    fd = open(manifest)

IOError: [Errno 2] No such file or directory: u'/opt/cloudera/parcels/CDH-5.10.2-1.cdh5.10.2.p0.5/meta/parcel.json'

[13/Apr/2018 12:53:31 +0000] 16047 Thread-13 parcel_cache INFO     Unpack of parcel /opt/cloudera/parcels/.flood/CDH-5.10.2-1.cdh5.10.2.p0.5-el7.parcel/CDH-5.10.2-1.cdh5.10.2.p0.5-el7.parcel successful




Telling me the the parcel.json file is missing/not accessible, but it is avail when I check:

[vagrant@node0 meta]$ ls -l /opt/cloudera/parcels/CDH-5.10.2-1.cdh5.10.2.p0.5/meta

total 7776

-rw-r--r--. 1 root root   11812 Jun 27  2017 alternatives.json

-rw-r--r--. 1 root root    1962 Jun 27  2017

-rw-r--r--. 1 root root 7598084 Jun 27  2017 filelist.json

-rw-r--r--. 1 root root  316053 Jun 27  2017 notices.txt

-rw-r--r--. 1 root root   17730 Jun 27  2017 parcel.json

-rw-r--r--. 1 root root    2815 Jun 27  2017 permissions.json


[vagrant@node0 meta]$ namei -m /opt/cloudera/parcels/CDH-5.10.2-1.cdh5.10.2.p0.5/meta/parcel.json

f: /opt/cloudera/parcels/CDH-5.10.2-1.cdh5.10.2.p0.5/meta/parcel.json

 dr-xr-xr-x /

 drwxr-xr-x opt

 drwxr-xr-x cloudera

 lrwxrwxrwx parcels -> /data/parcels

   dr-xr-xr-x /

   drwxrwxrwx data

   drwxr-xr-x parcels

 drwxr-xr-x CDH-5.10.2-1.cdh5.10.2.p0.5

 drwxr-xr-x meta

 -rw-r--r-- parcel.json



The last line of the agent log appears to say that the unpack of the parcel has completed after the check for the parcel.json file so of course it will fail.

If I then go and restart the cloudera-scm-agent the install process can see the parcel.json file and then completes.

How do I trigger the agent to recheck for the parcel file?