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

Bug 1047127

Summary: Installing Foreman should not ask for PRIVATE/PUBLIC info since it is not used by Neutron
Product: Red Hat OpenStack Reporter: Ofer Blaut <oblaut>
Component: openstack-foreman-installerAssignee: Jason Guiditta <jguiditt>
Status: CLOSED DUPLICATE QA Contact: Ami Jeain <ajeain>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.0CC: hateya, morazi, oblaut, ohochman, rhos-maint, yeylon
Target Milestone: ---Keywords: ZStream
Target Release: 4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-10 14:45: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 Ofer Blaut 2013-12-29 09:57:11 UTC 
Description of problem:

User must use several parameters [1] when installing foreman, which are not needed.

using /usr/share/openstack-foreman-installer/bin/foreman_server.sh
The default should be installing foreman without them, since they are not needed for neutron ( even for nova network they can be added later )

[1] 
#PRIVATE_CONTROLLER_IP=10.0.0.0
#PRIVATE_INTERFACE=eth
#PRIVATE_NETMASK=10.0.0.0
#PUBLIC_CONTROLLER_IP=10.0.0.0
#PUBLIC_INTERFACE=eth
#PUBLIC_NETMASK=10.3.3.0
#FOREMAN_GATEWAY=false



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.run foreman_server.sh  will require parameters [1]
2.This is not needed in installation phase of course not to neutron.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Jason Guiditta 2014-01-10 14:45:36 UTC 
Closing this as a Duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1049688 (see comment 4 for detailed list of changes). If you believe that does not cover this adequately, feel free to reopen

*** This bug has been marked as a duplicate of bug 1049688 ***