On 05-08-2017, exactly one month ago, I sent the change in the code to avoid the bug to @cjervis (Cloudera) by private message. With that change in the code I have the version 5.11 Express Edition working correctly.
According to my research the problem is related to the Express Edition, since the problem is linked to the roles REPORTSMANAGER, NAVIGATOR, NAVIGATORMETASERVER that in that version are not included.
While I already have all the process built to change the Java class with the problem every time I upgrade the Cloudera Manager, I think it is time for Cloudera to solve the problem, since it is so simple solution.
Absolutely; we thank you for all the help in this.
Addressing the NPE would have solved the immediate problem, but we were going for fixing whatever was broken to lead to the NPE. In doing so, it took much longer than we hoped to resolve. Of course that doesn't make the fact that it is broken for you and many other users...
At this point, we have a proposed fix that is slated for CM 5.12 and we will update you as soon as we discuss with engineering what we can do to get the fix into 5.10 and 5.11 branches, etc.
@GustavoVarisco, You ROCK!
I just installed CM 5.10.1 using the Cloudera Express license and BOOM!
Version: Cloudera Express 5.10.1 (#6 built by jenkins on 20170319-2001 git: f226435f6fa5f545543c00245900ae43bea7a29c)
Is there an estimations where 5.12 will be released?
Is there a manual a work around for this?
This issue will be resolved in the upcoming 5.10.2 and 5.11.2 maintenance releases, in addition to the 5.12 release.
C5.10.2 is supposed to be released this week. Release date for 5.11.2 is not defined yet, though.
C5.10.2 is supposed to be released this week.
C5.11.2 release date is not defined yet.
C5.12 release is planned for late July.