Problem when upgrading to CDH 5.4.1 (Parcels -

[#1]

 Cloudera Manager Version: Cloudera Express 5.4.1 (#197 built by jenkins on 20150509-0042 git: 003e06d761f80834d39c3a42431a266f0aaee736)

I have two Cloudera Cluster (A and B)

When I'm trying to get the latest 5.4.1 parcels, I can't see the 5.4.1 parcels on one of the servers (B).

Both have the same exact repo parcels and both have the same cloudera manager version.

Does anyone have the same experience?

[#2]

You just need to put the parcels into parcel-repo(in server node).

when you upgrade the cluster, server will auto distribute the parcels to all agents

[#3]

Ok Sartner, but did you had the same problem as me when trying to upgrade from 5.4 to 5.4.1?

I'm hoping if Cloudera Staff can verify if the solution provided by Sartner is acceptable for "production" cluster.

And I have concern why this particular cluster can't see the cdh 5.4.1 parcels from cloudera manager gui. (even though they have the exact same CM version)

[#4]

I can't understand what do you mean by "I can't see the 5.4.1 parcels on one of the servers (B)"

Can you give the sreenshots ?

[#5]

As you can see, on this particular cluster. There is no option to download CDH 5.4.1.

1. Yes I already updated to the latest cloudera manager that I stated on the first post.

2. The parcels repo url is on default config.

3. I have another cluster that can upgrade just fine from 5.4.0 to 5.4.1 (they are quite identical and using the same cm version)

[#6]

In my cluster (5.4.0) , there is no option to download CDH 5.4.1 too.......

[#7]

This is strange because on my other cloudera cluster, I have no problem upgrading CDH from 5.4.0 to 5.4.1 via CM.

So this is probably a bug? 

(ss on my other cloudera cluster)

[#8]

The following discussion covers the changes in the 5.4.x and our approach to the repos.  Most likely if you were on 5.3.x or older before you are seeing the change, whereas if you started on 5.4,  you are already following the new process automatically.

Please see: 

http://community.cloudera.com/t5/Cloudera-Manager-Installation/Why-is-CDH-5-4-not-set-as-the-latest-...

[#9]

@Tgrayson

I have upgraded the CM to the latest 5.4.1 on both cluster.

A cluster => didn't show cdh 5.4.1 parcels (cant upgrade)
B cluster => showed cdh 5.4.1 and successfully upgraded.

As you can see on my first post, the version of CM is 5.4.1 (#197 built by jenkins on 20150509-0042 git: 003e06d761f80834d39c3a42431a266f0aaee736)

and both have the same parcel repo urls

[#10 · Accepted solution]

Now the cluster that previously didn't see cdh 5.4.1 parcels got 5.4.2-1.cdh5.4.2.p0.2 parcel update available.

I believe this is probably the cause. (cloudera defer the 5.4.1 and waited for the 5.4.2 being pushed instead, because the release time is quite close)

Look: http://www.cloudera.com/content/cloudera/en/documentation/core/latest/topics/cdh_rn_new_in_542.html