Description of problem: This is a subset of a major bug #1337661. This is specific for Ambari plugin version 2.3 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
The implementation is a bit different than what happens with the sahara-image-elements generation: we are going to use a unified Ambari 2.4 image to deploy HDP 2.4 and 2.3. The title of the feature is a bit confusing because it conflates together the version of Ambari and the version of the deployed HDP. Right now sahara-image-elements deploys Ambari 2.2.1.0 for HDP 2.4 and Ambari 2.2.0.0 for HDP 2.3, but there is no reason for it, because Ambari 2.4 can deploy both those older versions (and also HDP 2.5, but let's put that aside). This means that, code-wise, this feature is not different than the last version of https://bugzilla.redhat.com/show_bug.cgi?id=1502851, which includes https://review.openstack.org/#/c/544625/ . The same Ambari image will be used to deploy both versions of HDP.
The image generated with Ambari 2.4 can spawn HDP 2.3 clusters when the following bug is fixed: https://bugzilla.redhat.com/show_bug.cgi?id=1570556 Tested with openstack-sahara-8.0.1-0.20180328233736.36531cb Waiting for the other bug to be solved.
Thanks to rhbz#1570556, and with the help of a workaround for the TLS version used (see rhbz#1577372), the Ambari 2.4 image generated by sahara-image-pack can spawn an HDP 2.3 cluster (pre-tested also before the jdk issue hit). openstack-sahara-tests-0.6.0-2.el7ost openstack-sahara-8.0.1-0.20180328233739.36531cb.el7ost (with workaround)
Ok, we need a proper clean environment. Reopening for now with the blocker.
With the fixes for bug 1577372 and bug 1570556 in place, it is now possible to confirm that an Ambari 2.4 image generated by sahara-image-pack can spawn a working HDP 2.3 cluster. Verified with: openstack-sahara-8.0.1-0.20180328233740.36531cb.el7ost (name of the source package)
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:2086