Bug 1199047

Summary:	The value of use_neutron is set to false (instead of true) when neutron is used.
Product:	Red Hat OpenStack	Reporter:	Lukas Bezdicka <lbezdick>
Component:	openstack-packstack	Assignee:	Lukas Bezdicka <lbezdick>
Status:	CLOSED ERRATA	QA Contact:	Luigi Toscano <ltoscano>
Severity:	high	Docs Contact:
Priority:	medium
Version:	6.0 (Juno)	CC:	aortega, dnavale, lbezdick, nlevinki, nyechiel, tfreger, yeylon
Target Milestone:	z2	Keywords:	ZStream
Target Release:	6.0 (Juno)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-packstack-2014.2-0.17.dev1462.gbb05296.el7ost	Doc Type:	Bug Fix
Doc Text:	A typo in the code caused Sahara option that uses OpenStack Networking to be always false. With this update, the error has been addresses. As a result, Sahara now uses OpenStack Networking if the parameter 'CONFIG_NEUTRON_INSTALL is set to 'y'.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-04-07 15:10:36 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Lukas Bezdicka 2015-03-05 11:50:01 UTC

The value of use_neutron is set to false (instead of true) when neutron is used.

The fix is quite straightforward, the wrong line is:
use_neutron => ($sahara_cfg_controller_host == 'y')

into packstack/puppet/templates/sahara.pp

Found on RDO package:
openstack-packstack-2014.2-0.13.dev1395.gaabe0a2.fc22.noarch
and of course current git master (713b745e0efbaaba5695055f6125464f72afcee1).

Comment 6 Luigi Toscano 2015-03-18 17:51:39 UTC

The value of use_neutron is now correctly set according the availability of Neutron (True if requested and installed from packstack, False otherwise).

openstack-packstack-2014.2-0.17.dev1462.gbb05296.el7ost.noarch
openstack-packstack-puppet-2014.2-0.17.dev1462.gbb05296.el7ost.noarch

Comment 9 errata-xmlrpc 2015-04-07 15:10:36 UTC

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://rhn.redhat.com/errata/RHSA-2015-0789.html