Bug 1222323 - hosted engine deploy nukes resolve.conf and breaks DNS
Summary: hosted engine deploy nukes resolve.conf and breaks DNS
Keywords:
Status: CLOSED DUPLICATE of bug 1160423
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-hosted-engine-setup
Version: 3.5
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
: 3.6.0
Assignee: Sandro Bonazzola
QA Contact: meital avital
URL:
Whiteboard: integration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-17 15:47 UTC by rstory
Modified: 2015-05-21 10:07 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-05-21 10:07:02 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)

Description rstory 2015-05-17 15:47:42 UTC
Description of problem:

While doing a new install today (3.5.2 on CentOS 7), deploy failed because the system couldn't resolve the host name for my storage server. In bug #1160423 dns broken during creating of the mgmt bridge, but in this case mgmt was on eth1.79 vlan, and DNS config was on eth0.1. The deploy basically overwrote resolv.conf with a blank file.

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

# rpm -qa|grep ovirt
ovirt-release35-003-1.noarch
ovirt-engine-sdk-python-3.5.2.1-1.el7.centos.noarch
ovirt-hosted-engine-setup-1.2.3-1.el7.centos.noarch
ovirt-hosted-engine-ha-1.2.5-1.el7.centos.noarch
libgovirt-0.3.1-3.el7.x86_64
ovirt-host-deploy-1.3.1-1.el7.noarch

How reproducible:


Steps to Reproduce:
1. configure DNS on one interface, ovirt on another
2. run --deploy
3. check resolv.conf

Actual results:
empty file

Expected results:
unchanged contents

Additional info:
workaround is to run 'service network restart', which restores resolv.conf, and then redeploy.

Comment 1 Sandro Bonazzola 2015-05-21 10:07:02 UTC
thanks for reporting, but seems to me a duplicate of bug #1160423 also if this is on a tagged vlan. Marking as duplicate.

*** This bug has been marked as a duplicate of bug 1160423 ***


Note You need to log in before you can comment on or make changes to this bug.