Description of problem: There is a mismatch between the jdk version handled during provisioning of Ambari instances: - sahara-image-pack pre-loads java-1.7.0-openjdk-devel - sahara-image-create pre-loads java-1.8.0-openjdk-devel On the other side, sahara-engine (the service) uses the same code of sahara-image-pack and tries to ensure that java-1.7.0-openjdk-devel is installed. This means that, if the instance is generated using sahara-image-create has no repositories configured, the creation of the cluster will fail. This is not a total blocker because a workaround exists: an instance generated with sahara-image-create should be tuned to point to a repository with the packages, or the package java-1.7.0-openjdk-devel should be pre-loaded. Instead, all images should use java-1.8.0-openjdk{,-devel}. Nevertheless, it is a regression in the behavior of the images produced with sahara-image-create (the only way to produce images before 13) and it could be nice to have it fixed before the final release. Version-Release number of selected component (if applicable): Image generated with: sahara-image-elements-8.0.1-0.20180316135145.c235e1e.el7ost OpenStack deployment using: openstack-sahara-8.0.1-0.20180328233739.36531cb.el7ost
sahara-image-pack now injects java 1.8 and this is the version checked during the startup process. Verified with: openstack-sahara-image-8.0.1-0.20180328233740.36531cb.el7ost
Small typo (In reply to Luigi Toscano from comment #6) > Verified with (source package): > openstack-sahara-8.0.1-0.20180328233740.36531cb.el7ost
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