Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1111969

Summary: packstack ignores CONFIG_PROVISION_DEMO set to n
Product: Red Hat OpenStack Reporter: Nir Magnezi <nmagnezi>
Component: openstack-packstackAssignee: Gaël Chamoulaud <gchamoul>
Status: CLOSED ERRATA QA Contact: Ido Ovadia <iovadia>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 5.0 (RHEL 7)CC: aortega, breeler, derekh, gchamoul, gfidente, ichavero, mmagr, sgordon, yeylon
Target Milestone: rcKeywords: AutomationBlocker
Target Release: 5.0 (RHEL 7)   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: openstack-packstack-2014.1.1-0.27.dev1184.el7ost Doc Type: Bug Fix
Doc Text:
PackStack was provisioning Tempest with demo objects even if the flag CONFIG_PROVISION_DEMO was disabled. This fix makes these flags independent. Now you can install Tempest in a standalone mode or with the provisioning user of your choice. This fix adds two new config options: - CONFIG_PROVISION_TEMPEST_USER (blank by default) - CONFIG_PROVISION_TEMPEST_USER_PW 1) If CONFIG_PROVISION_TEMPEST is enabled and CONFIG_PROVISION_TEMPEST_USER stays blank, PackStack will provision Tempest in a standalone mode. 2) If CONFIG_PROVISION_TEMPEST_USER is set with a user, PackStack will provision tempest with this user. Note that you always will be able to use the demo user for provisioning tempest. In this case, if CONFIG_PROVISION_DEMO is enabled, PackStack will use the demo password from CONFIG_KEYSTONE_DEMO_PW. If CONFIG_PROVISION_DEMO is not enabled, it will use CONFIG_PROVISION_TEMPEST_USER_PW.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-24 17:25:01 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:
Attachments:
Description Flags
packstack answer file none

Description Nir Magnezi 2014-06-22 12:27:55 UTC 
Created attachment 911136 [details]
packstack answer file

Description of problem:
=======================
packstack ignores CONFIG_PROVISION_DEMO set to n.
Dispite the fact that CONFIG_PROVISION_DEMO=n, it creats the default public network: CONFIG_PROVISION_DEMO_FLOATRANGE=172.24.4.224/28
 
Version-Release number of selected component (if applicable):
=============================================================
openstack-packstack-2014.1.1-0.26.dev1157.el7ost.noarch
openstack-packstack-puppet-2014.1.1-0.26.dev1157.el7ost.noarch

How reproducible:
=================
Tested one time.

Steps to Reproduce:
===================
1. Use the attached answer file with packstack:

Actual results:
===============
192.168.160.29_provision.pp.log:Debug: Executing '/usr/bin/neutron subnet-create --format=shell --name=public_subnet --enable-dhcp=False --tenant_id=2ffbec4f8cc9427f8ba88062acdd0052 public 172.24.4.224/28'

Expected results:
=================
packstack should not create that network.
Comment 2 Nir Magnezi 2014-06-22 12:34:09 UTC 
In addition packstack created a DEMO tenant.
Comment 4 Gaël Chamoulaud 2014-06-24 09:26:45 UTC 
Patch proposed https://review.openstack.org/#/c/102122/
Comment 5 Gaël Chamoulaud 2014-06-24 09:27:54 UTC 
*** Bug 1111553 has been marked as a duplicate of this bug. ***
Comment 6 Martin Magr 2014-06-24 13:59:36 UTC 
This is not a regression. Packstack was provisioning demo together with tempest from the beginning.
Comment 11 Ido Ovadia 2014-07-21 14:09:20 UTC 
Verified
========
openstack-packstack-puppet-2014.1.1-0.35.dev1220.el6ost.noarch
openstack-packstack-2014.1.1-0.35.dev1220.el6ost.noarch
Comment 13 errata-xmlrpc 2014-07-24 17:25:01 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/RHBA-2014-0930.html