Bug 1040585

Summary:	CI tests failing due to improper handling of empty value
Product:	Red Hat OpenStack	Reporter:	Lon Hohberger <lhh>
Component:	openstack-packstack	Assignee:	Martin Magr <mmagr>
Status:	CLOSED ERRATA	QA Contact:	Nir Magnezi <nmagnezi>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	4.0	CC:	aortega, derekh, hateya, sclewis, yeylon
Target Milestone:	rc	Keywords:	OtherQA, TestBlocker, VerifiedOnDev
Target Release:	4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-packstack-2013.2.1-0.18.dev934.el6ost	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-12-20 00:44:13 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:

Description Lon Hohberger 2013-12-11 16:22:54 UTC

Description of problem:

After quite a bit of research, Martin and Terry discovered that if CONFIG_NEUTRON_LBAAS_HOST is set to an empty value in a packstack answers file, neutron-db-manage will break with the following exception:

Notice: /Stage[main]//Exec[neutron-db-manage upgrade]/returns: ImportError: Class  cannot be found (['Traceback (most recent call last):\n', '  File "/usr/lib/python2.6/site-packages/neutron/openstack/common/importutils.py", line 30, in import_class\n    __import__(mod_str)\n', 'ValueError: Empty module name\n'])
You will find full trace in log /var/tmp/packstack/20131211-103901-AMhl2O/manifests/192.168.129.50_neutron.pp.log[0m
Please check log file /var/tmp/packstack/20131211-103901-AMhl2O/openstack-setup.log for more information


Version-Release number of selected component (if applicable): 2013.2.1-0.17.dev930.el6ost


How reproducible: 100%

Steps to Reproduce:
1. Use packstack with an answers file that has CONFIG_NEUTRON_LBAAS_HOST empty

Actual results: Crash / failed installation

Expected results: No crash

Additional info: Fix in progress

Comment 5 errata-xmlrpc 2013-12-20 00:44:13 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.

http://rhn.redhat.com/errata/RHEA-2013-1859.html