Bug 1576310
| Summary: | [OVN] - [HE] - ovn tunnel is not created if central hostname resolved as 127.0.0.1 in hosts file | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-hosted-engine-setup | Reporter: | Michael Burman <mburman> |
| Component: | Network | Assignee: | Simone Tiraboschi <stirabos> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Michael Burman <mburman> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 2.2.19 | CC: | bugs, dholler, lveyde, mmirecki, stirabos |
| Target Milestone: | ovirt-4.2.4 | Keywords: | Automation |
| Target Release: | 2.2.22 | Flags: | rule-engine:
ovirt-4.2+
|
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-hosted-engine-setup-2.2.22 | Doc Type: | Bug Fix |
| Doc Text: |
OVN central is installed on the hosted-engine VM; the hosts should point to it using its IP address which is available just at the end of the setup so the setup will temporary use the bootstrap address at setup time fixing it with the target address just at the end.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-06-26 08:42:00 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1581783 | ||
Verified on - ovirt-hosted-engine-setup-2.2.22-1.el7ev.noarch This bugzilla is included in oVirt 4.2.4 release, published on June 26th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.4 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |
Description of problem: [OVN] - [HE] - ovn tunnel doesn't created if central hostname resolved as 127.0.0.1 in hosts file When running hosted engine deploy, user is asked if he want to add the VM's FQDN to /etc/hosts file and resolved as 127.0.01, if choosing 'yes' then the ovn deploy using 127.0.0.1 as central and then no ovn tunnel is created on the host/s. 2018-05-09 10:05:42,563 p=61921 u=ovirt | TASK [ovirt-provider-ovn-driver : Configure OVN for oVirt] ********************* 2018-05-09 10:05:50,118 p=61921 u=ovirt | changed: [lynx03.lab.eng.tlv2.redhat.com] => { "changed": true, "cmd": [ "vdsm-tool", "ovn-config", "127.0.0.1", "10.46.16.22" ], "delta": "0:00:06.741161", "end": "2018-05-09 10:05:50.029649", "rc": 0, "start": "2018-05-09 10:05:43.288488" } Version-Release number of selected component (if applicable): 4.2.3.5-0.1.el7 How reproducible: 100% Steps to Reproduce: 1. Run hosted-engine deploy and choose yes to add the VM's FQDN to hosts file Actual results: Try to use ovn in this engine after deploy is done NO tunnel created on the host/s Expected results: We should handle such use case for users that choose to add their FQDNs to hosts file and resolved as 127.0.01