Rolling upgrade failing for a clean cluster from HDP 2.2.8 to HDP 2.3.2

[#1]

Installed a fresh HDP 2.2.8 cluster, and then went through all the steps to perform a rolling upgrade to the new HDP 2.3.2 release, the service checks for MapReduce2, Tez and Pig all fail.

Can't see anything in the known issues of the release notes for this.

Once the upgrade runs all the way through I'll take a look for some debug logs, but for now just wanted to see if anyone else had seen this?

[#2]

Right, setup 2 new identical 2.2.8 clusters, and this is the result...

2.2.8 --> 2.3.0 = Works!

2.2.8 --> 2.3.2 = Works!

Wait? What?

So a bit more digging around and I discover the Ambari release increment too. The cluster I installed this morning, is Ambari 2.1.1, where as the two I installed this afternoon picked up Ambari 2.1.2...

Sooo I guess Ambari 2.1.1 won't perform a rolling upgrade between HDP 2.2.8 and HDP 2.3.2.

There's no mention of such dependancies in our release notes.

[#3]

I try to monitor http://public-repo-1.hortonworks.com/ once in a while for new bits. Always go with the latest .x release that is not .0 release.

[#4 · Accepted solution]

It's a known issue with Ambari 2.1.1. When performing this rolling upgrade for HDP, ensure you're using Ambari 2.1.2.

[#5]

Should be mentioned in our release notes in that case imho.