question Custom Parcel will not display in the Add Service page in CM 5.13 in Archives of Support Questions (Read Only)

Custom Parcel will not display in the Add Service page in CM 5.13

IT.Services — Wed, 29 Nov 2017 01:14:08 GMT

I have a custom Parcel that works on CM 5.7. Using CM 5.7 I am able to add the service to my cluster without any problems. However, after I updated to CM 5.13, and activated the custom Parcel, the service does not display on the Add Service page. I have restarted the Cloudera Manager server, and I restarted the Cloudera Manager Services. The parcel.json file in the Parcel shows no errors on validation.

Do you have any recommendations? Do Parcels have to be recreated for each CM version?

Here is my parcel.json file, note that this works on CM 5.7, but not CM 5.13:

{
"schema_version": 1,
"name": "STORM",
"version": "1.0.1_0.0.4",
"setActiveSymlink": true,
"depends": "CDH",
"replaces": "STORM",
"conflicts": "",

"provides": [
"storm"
],

"scripts": {
"defines": "storm_env.sh"
},

"packages": [
{ "name" : "apache-storm",
"version": "apache-storm-1.0.1"
}
],

"components": [
{ "name" : "apache-storm",
"version" : "apache-storm-1.0.1",
"pkg_version": "1.0.1",
"pkg_release": "0.0.3"
}
],

"users": {
"storm": {
"longname" : "Apache Storm",
"home" : "/var/lib/storm",
"shell" : "/bin/bash",
"extra_groups": [ "storm" ]
}
},

"groups": [
"storm"
]
}

Re: Custom Parcel will not display in the Add Service page in CM 5.13

IT.Services — Thu, 30 Nov 2017 18:32:32 GMT

I realized that I was missing the CSD file that should accompany the custom Parcel. The CSD is what defines how the package in the Parcel will display on the Add Service menu in Cloudera Manager. After adding the CSD I restarted the CM server and the package is visible.

Re: Custom Parcel will not display in the Add Service page in CM 5.13

Suhas — Sat, 01 Jun 2019 03:44:31 GMT

I'm having same issue.

customized local parcels stored under /opt/cloudera/parcel-repo are not listing under CM- Parcels

I even tried below

1. copied exising parcel which is visible in CM

2. untar parcel to some temp location

3. rename dir (untar)

4. generate parcel/ tar by only replacing parcel name in parcel.json

5. generated sha file

6. Copied parcel and sha files under /opt/cloudera/parcel-repo

7. Restarted cloudera manager server.

But no luck

Any suggestion?