Closed lhoss closed 5 years ago
I know I've seen that but nothing I can do... this is a problem with Ambari and/or HDF mpack rather than an issue with these playbooks.
I know I've seen that but nothing I can do.
@alexandruanghel yeah I'm totally aware that it's not a bug in your/our playbooks 👍
I should have mentioned that, and ask if you could ask inside Cloudera about the status of that issue, and ideally post here a reference/link so we can track the progress (if it's not tracked internal only)
Also imagine any (new) user that now run the deployment with the bumped version (and HDF included), it will fail and they might look for help (hopefully checking the Issues
section here)
@alexandruanghel I just did another test run, with the hope that a newer build would have been released in the meantime, to fix this major issue , but it seems still not fixed! Would be great if you could ask inside Cloudera if this issue is known, and share the related AMBARI Jira issue if there's one?!
Don't think there will be a jira, probably non essential work on Ambari has stopped.
Looking at https://supportmatrix.hortonworks.com/ I can see it was updated to reflect the fact that Ambari 2.7.4 is not compatible with any HDF releases. So I guess that settles it, sorry.
Thanks for the update I also just found the related community post: https://community.cloudera.com/t5/Support-Questions/Latest-HDP-3-1-4-not-compatible-with-any-version-of-HDF-or/m-p/277721/highlight/false#M207654 .. and had posted a summary of my learnings, with a link back to the issue here
Hi @alexandruanghel , Not sure if you tested a cluster install with the latest Ambari (active since your latest version bump commit) and an HDF (mpack) deployment, but it seems those mpacks are not (yet) compatible with Ambari 2.7.4, because they are missing a file for only that version (
smartsense-ambari-view-2.7.4.jar
, details below):Here the full stacktrace (when I reproduced the mpack install issue, outside ansible, in the shell, as user
root
):I thought maybe I got bad timing, with the currently active HDF build (
4
), but the same issue when testing with HDF-3.4.0.0