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

Bug 1780058

Summary: When using localhost as FQDN I'm getting warning 3 times
Product: [oVirt] ovirt-engine Reporter: Petr Matyáš <pmatyas>
Component: Setup.EngineAssignee: Sandro Bonazzola <sbonazzo>
Status: CLOSED WONTFIX QA Contact: Lucie Leistnerova <lleistne>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.4.0CC: arachman, bugs, didi
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-12-11 08:11:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1546838    
Bug Blocks:    
Attachments:
Description Flags
setup log none

Description Petr Matyáš 2019-12-05 10:29:20 UTC
Created attachment 1642320 [details]
setup log

Description of problem:
When using localhost.localdomain as FQDN for my engine, I'm getting a warning that not everything will be working which is fine, but then after confirming firewall configuration I get the same warning 3 additional times.

Version-Release number of selected component (if applicable):
ovirt-engine-setup-4.4.0-0.6.master.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. install engine on a server without dns resolution
2. confirm localhost.localdomain or localhost as FQDN for engine (or just set it to such)
3.

Actual results:
warning appears once and then 3 times

Expected results:
warning appears only once

Additional info:
          --== NETWORK CONFIGURATION ==--

          Host fully qualified DNS name of this server [localhost.localdomain]:
[WARNING] Failed to resolve localhost.localdomain using DNS, it can be resolved only locally
[WARNING] Using the name 'localhost' is not recommended, and may cause problems later on.
          Are you sure? (Yes, No) [No]: yes
          Setup can automatically configure the firewall on this system.
          Note: automatic configuration of the firewall may overwrite current settings.
          NOTICE: iptables is deprecated and will be removed in future releases
          Do you want Setup to configure the firewall? (Yes, No) [Yes]:
[ INFO  ] firewalld will be configured as firewall manager.
[WARNING] Using the name 'localhost' is not recommended, and may cause problems later on.
[WARNING] Using the name 'localhost' is not recommended, and may cause problems later on.
[WARNING] Using the name 'localhost' is not recommended, and may cause problems later on.

          --== DATABASE CONFIGURATION ==--

Comment 1 Yedidyah Bar David 2019-12-05 10:45:31 UTC
The reason that this warning appears 3 more times, is that we use the function that generates it 3 more times - for imageio-proxy, vmconsole-proxy, and websocket-proxy setup plugins. Each of them does its own (duplicate, in this case) tests for the fqdn, which emit this warning. I think it's fine to close, as this is a corner case, harmless, one might even claim desired. Thanks for the report!

Comment 2 Asaf Rachmani 2019-12-05 11:48:20 UTC
Didi, why is this a corner case?

Comment 3 Yedidyah Bar David 2019-12-08 06:27:50 UTC
(In reply to Asaf Rachmani from comment #2)
> Didi, why is this a corner case?

Because people are not supposed to use 'localhost' for the fqdn.

Comment 4 Sandro Bonazzola 2019-12-11 08:10:52 UTC
Closing wontfix. localhost shouldn't be used for fqdn on engine.