Bug 843623

Summary:	ip address did not resolve to an ip address
Product:	[Retired] oVirt	Reporter:	Cybertimber2011 <cybertimber2000>
Component:	ovirt-engine-installer	Assignee:	Sandro Bonazzola <sbonazzo>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	3.1 RC	CC:	acathrow, alourie, iheim, jkt, sbonazzo
Target Milestone:	---
Target Release:	3.2
Hardware:	x86_64
OS:	Linux
Whiteboard:	integration
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	953770 (view as bug list)		Environment:
Last Closed:	2013-07-25 21:13: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:
Bug Depends On:
Bug Blocks:	953770

Description Cybertimber2011 2012-07-26 19:04:23 UTC

Component should be ovirt-engine-setup but it is not in the list

Description of problem:
When substituting an IP address for a fully qualified domain name in engine-setup, engine-setup reports that "<ip address here> did not resolve to an ip address. User input failed validation...". Not sure if there is a way to check for an IP address before checking for a FQDN, or if an ip address is unsupported.

Version-Release number of selected component (if applicable):
ovirt-engine 3.1.0-1.fc17
ovirt-engine-setup-3.1.0-1.fc17

How reproducible:
Always when using an IP address for a FQDN

Steps to Reproduce:
1. Install ovirt-engine
2. Run engine-setup
3. Enter the system IP address for "Host fully qualified domain name".
  
Actual results:
<ip address> did not resolve into an IP address
User input failed validation, do you still wish to use it (yes|no):

Expected results:
No lookup of an IP address as it is an IP address

Additional info:
3.0 also had this behavior, but I think it just said "user input failed validation, do you still wish to use it (yes|no)"

Comment 1 Cybertimber2011 2012-07-26 19:06:15 UTC

Additional comment, that line differs from others in how the options are presented. It should say ['yes'| 'no']: similar to the iptables question.

Comment 2 Alex Lourie 2013-01-23 21:36:23 UTC

Is it possible to test this with the latest master version upstream?

Basically, the behaviour of 3.1/3.2 should be the same as 3.0 in this regard.

Comment 3 Cybertimber2011 2013-01-24 17:23:20 UTC

Do you mean re-test with 3.2?

Comment 4 Alex Lourie 2013-01-24 17:55:46 UTC

(In reply to comment #3)
> Do you mean re-test with 3.2?

Yes, please :-)

Comment 5 Sandro Bonazzola 2013-02-01 13:07:55 UTC

Tested with 
ovirt-engine-setup-3.3.0-0.1.20130131130858.20130131.git6c8007c.fc18.noarch

still present as in comment #0 and comment #1

Comment 6 Sandro Bonazzola 2013-02-01 13:15:48 UTC

Additionally, it is present if the device with the given IP address is under NetworkManager and also if the device is confiugred with NM_CONTROLLED=no.

Comment 7 Sandro Bonazzola 2013-02-01 14:35:39 UTC

Patch sent upstream for comment #0. About comment #1, it requires a change in askYesNo function in common_utils, shared with other scripts and I'm not sure if it has to be changed or not.

Comment 8 Cybertimber2011 2013-02-03 20:12:30 UTC

Re: Comment #1 change, are the other questions not asked with the askYesNo function in common_utils?

I will finally have my 3.2 test system up shortly to do some testing. Sorry it's taken me a bit to respond, but thanks Sandro for testing and patching this.

Comment 9 Cybertimber2011 2013-02-04 17:16:42 UTC

Yes, I can confirm this is still present as well.
Tested with ovirt-engine-setup-3.2.0-2.fc18.noarch

Comment 10 Sandro Bonazzola 2013-02-05 12:37:30 UTC

It seems that a symbolic domain name is required for the engine to be able to generate certificates correctly. engine-setup will warn the user with a better message than <ip address here> did not resolve to an ip address. User input failed validation...

(In reply to comment #8)
> Re: Comment #1 change, are the other questions not asked with the askYesNo
> function in common_utils?

No, they're asked through _getInputFromUser with yes or no as options.

Comment 11 Sandro Bonazzola 2013-02-07 07:39:38 UTC

patch merged upstream master: http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=dca66499e55dfa421a732567ade00ed1c696c363

Comment 12 Cybertimber2011 2013-07-25 21:08:26 UTC

Itamar - I pretty sure this made it into 3.2.