Bug 1590267

Summary:	gluster network interface is not configured properly by vdsm to obtain IP from dhcp
Product:	[oVirt] vdsm	Reporter:	SATHEESARAN <sasundar>
Component:	General	Assignee:	Dan Kenigsberg <danken>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Meni Yakove <myakove>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.30.0	CC:	bugs, rhs-bugs, sabose, sankarshan, sasundar, ylavi
Target Milestone:	---	Keywords:	Reopened
Target Release:	---	Flags:	sasundar: ovirt-4.2? sasundar: planning_ack? sasundar: devel_ack? sasundar: testing_ack?
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1590264	Environment:
Last Closed:	2018-07-22 12:58: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:	1590264

Description SATHEESARAN 2018-06-12 10:32:35 UTC

+++ This bug was initially created as a clone of Bug #1590264 +++

Description of problem:
-----------------------
RHHI setup uses 2 network interface, one for ovirtmgmt and other for gluster. After gluster configuration and HE deployment is completed from cockpit, the gluster network interface configuration file is edited by vdsm and that doesn't adds 'BOOTPROTO=dhcp'

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

How reproducible:
-----------------
Few times

Steps to Reproduce:
--------------------
1. Complete RHHI deployment - Gluster configuration & HE deployment from cockpit
2. Check for the network configuration file for the interface allocated to the gluster network

Actual results:
---------------
Network configured via dhcp never comes up

Expected results:
-----------------
Network interface configured with dhcp should be up

Additional info:
----------------

Here is the network configuration file created by vdsm but missing BOOTPROTO
# Generated by VDSM version 4.20.30-1.el7ev
DEVICE=enp3s0f0
ONBOOT=yes
MTU=1500
NM_CONTROLLED=no

Comment 1 Yaniv Lavi 2018-06-24 07:36:19 UTC

Did you configure the gluster network using Cockpit?
Did you add the network via the engine as well during the HE deployment?
Can you add the supervdsm logs? Can you provide the ifcfg before the vdsm change?

Comment 2 SATHEESARAN 2018-07-04 10:07:29 UTC

Apologies for not answering this bug on time.

But this is a very recurring issue that we have seen in our setup and took long time for us to root cause the problem

(In reply to Yaniv Lavi from comment #1)
> Did you configure the gluster network using Cockpit?
No, I have configured network from RHV Manager UI

> Did you add the network via the engine as well during the HE deployment?
No, only via RHV Manager UI

> Can you add the supervdsm logs? Can you provide the ifcfg before the vdsm
> change?
I will provide the required info next time, and re-open this bug.

Comment 3 SATHEESARAN 2018-07-19 11:20:55 UTC

I could again hit this issue. The relevant details look the same as comment2

I have used DHCP to configure network interfaces, the network configuration file doesn't have 'BOOTPROTO=dhcp' and failed to obtain IP address on that network interface

Comment 4 Dan Kenigsberg 2018-07-22 12:58:00 UTC

But what about our requested data of comment 1? Please reopen when you have it.

When you attach supervdsm.log, make sure to walk us through it. Tell us when was the host added to the cluster, which network was configured for gluster and when. Make sure to include ifcfg files before and after the failure.