Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1044920

Summary: PRD34 - [RFE][hosted engine] propose Default GW IP during installation
Product: Red Hat Enterprise Virtualization Manager Reporter: Pavel Stehlik <pstehlik>
Component: ovirt-hosted-engine-setupAssignee: Sandro Bonazzola <sbonazzo>
Status: CLOSED ERRATA QA Contact: movciari
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.3.0CC: aburden, acathrow, dfediuck, iheim
Target Milestone: ---Keywords: EasyFix, FutureFeature, ZStream
Target Release: 3.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: integration
Fixed In Version: ovirt-3.4.0-alpha1 Doc Type: Enhancement
Doc Text:
* The hosted-engine deployment script now proposes a default pingable gateway IP address.
Story Points: ---
Clone Of:
: 1046147 (view as bug list) Environment:
Last Closed: 2014-06-09 14:47:47 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:
Bug Depends On:    
Bug Blocks: 1046147, 1078909, 1142926    

Description Pavel Stehlik 2013-12-19 09:00:24 UTC
Description of problem:
...
--== NETWORK CONFIGURATION ==--
...
Please indicate a pingable gateway IP address:

Can we propose current Default GW IP ? eg: "Please indicate a pingable gateway IP address[192.168.1.1]:"

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

How reproducible:
100%

Steps to Reproduce:
1. hosted-engine --deploy
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Sandro Bonazzola 2013-12-23 07:38:08 UTC
Merged on upstream master branch for 3.4.0 rebase.

Comment 7 errata-xmlrpc 2014-06-09 14:47:47 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-0505.html