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

Bug 1070393

Summary: foreman: default parameters related to specific host should be take from the host itself (controller installation)
Product: Red Hat OpenStack Reporter: Dafna Ron <dron>
Component: rubygem-staypuftAssignee: RHOS Maint <rhos-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Omri Hochman <ohochman>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.0CC: mburns, morazi, rhos-maint, yeylon
Target Milestone: ---   
Target Release: 5.0 (RHEL 7)   
Hardware: x86_64   
OS: Linux   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-05 19:51:42 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
screen shot none

Description Dafna Ron 2014-02-26 17:28:28 UTC
Created attachment 868117 [details]
screen shot

Description of problem:

My host is in the 10.35.XX.XX network and I am getting completely different values which I need to override creating new fields
If we do not use actual values from the host and only examples there is no need to override - simply create an empty field with example of how to fill it. 
the way it is done now I think it's a bit confusing to the users. 

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

foreman-1.3.0.2-1.el6sat.noarch
openstack-foreman-installer-1.0.4-1.el6ost.noarch
foreman-selinux-1.3.0-1.el6sat.noarch
rubygem-foreman_api-0.1.6-1.el6sat.noarch
foreman-mysql-1.3.0.2-1.el6sat.noarch
foreman-mysql2-1.3.0.2-1.el6sat.noarch
ruby193-rubygem-foreman_openstack_simplify-0.0.6-5.el6ost.noarch
foreman-installer-1.3.0-1.el6sat.noarch
foreman-proxy-1.3.0-3.el6sat.noarch

How reproducible:

100%

Steps to Reproduce:
1. add a host to the foreman
2. edit the host as a nova controller 
3.

Actual results:

we get unrelated values as default values 

Expected results:

we should be taking values from the host

Additional info:
screen shot

Comment 1 Mike Burns 2014-08-05 19:51:42 UTC
This bug was handled or obsoleted during the GA2 redesign work.  If you believe that this still applies to the current UI, please re-open this bug.