Description of problem: Sahara can use heat as internal engine to provision and control the Hadoop cluster. The default engine was by default the Sahara-specific one until Kilo. From Liberty, the default engine is the heat one. The sahara.conf file does not acknowledge this and it still shows the comment # infrastructure_engine = direct But this is not the problem. The issue is that, if CONFIG_SAHARA_INSTALL=y and CONFIG_HEAT_INSTALL=n, Heat is not installed but Sahara expects it to be working, and cluster provisioning fails. So, while the default comment in the generated sahara.conf should show heat, that value should change based on the Heat availability. Version-Release number of selected component (if applicable): openstack-packstack-2015.2-dev1636.g3015bff.el7.centos.noarch openstack-packstack-puppet-2015.2-dev1636.g3015bff.el7.centos.noarch openstack-puppet-modules-2015.2-dev.1150d0da14ad00e6151d11443ab96d6d3e9649b2_8eef2746.el7.centos.noarch
When CONFIG_SAHARA_INSTALL is y, packstack automatically sets CONFIG_HEAT_INSTALL to y regardless of its original value. Verified on an up-to-date CentOS 7, with: RDO Liberty: openstack-packstack-7.0.0-0.10.dev1682.g42b3426.el7.noarch openstack-packstack-puppet-7.0.0-0.10.dev1682.g42b3426.el7.noarch openstack-puppet-modules-7.0.1-1.el7.noarch RDO Mitaka (DLRN snapshot): openstack-packstack-8.0.0-0.20160303124552.0476b9b.el7.centos.noarch openstack-packstack-puppet-8.0.0-0.20160303124552.0476b9b.el7.centos.noarch openstack-puppet-modules-8.0.0a0-0.20160304203011.7dc7e93.el7.centos.noarch