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

Bug 1144084

Summary:	Installing of ovirt-engine-setup-plugin-allinone caused network to drop when NetworkManager is up
Product:	[Retired] oVirt	Reporter:	Aaron Ogle <aaron>
Component:	vdsm	Assignee:	Dan Kenigsberg <danken>
Status:	CLOSED DUPLICATE	QA Contact:	Gil Klein <gklein>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.5	CC:	bazulay, bugs, danken, ecohen, gklein, lsurette, mgoldboi, rbalakri, yeylon, ylavi
Target Milestone:	---
Target Release:	3.6.0
Hardware:	x86_64
OS:	Linux
Whiteboard:	network
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-09-08 09:47:14 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Network	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Aaron Ogle 2014-09-18 15:25:02 UTC

User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.120 Safari/537.36
Build Identifier:

I installed ovirt-engine-setup-plugin-allinone package. Then ran the engine-setup.
Selected Host as VDSM and used default answers on the others.

Installer times out waiting on the VDSM to come up. Checking the admin web interface you can see that host is there but flagged as Non-Operational. In the event log it said it failed to setup network. If you attempted to add ovirt to em1 through the interface it would fail.

Reproducible: Always

Steps to Reproduce:
1.Download Fedora 20 iso and install on host.
2.Add release 35 rpm. `yum localinstall http://plain.resources.ovirt.org/pub/yum-repo/ovirt-release34.rpm`
3. Install ovirt-engine-setup-plugin-allinone.
4. Run engine-setup choosing Yes for VDSM on host, other options default.
Actual Results:
It never successfully finishes setting up.

I worked this through with apuimedo(asegurap) in irc.

After going through this process several times and not having any luck, I did a re-install.

After being advised that the NetworkManager service was potentially problematic, I disabled the service.

I followed the original steps and it seemed to succeed, but then the network connection dropped. I would restart it, go for maybe a minute and the connection would drop again.

After some digging I discovered this task running:

```
root 18875 0.0 0.0 113380 3240 ? S< 16:30 0:00 /bin/bash /etc/sysconfig/network-scripts/ifdown-eth ifcfg-ovirtmgmt
root 18974 0.0 0.0 113380 3204 ? S< 16:30 0:00 /bin/sh /etc/sysconfig/network-scripts/ifdown-post ifcfg-ovirtmgmt
root 18989 0.8 0.1 247168 22008 ? S< 16:30 0:00 /usr/bin/python -Es /usr/bin/firewall-cmd --remove-interface=ovirtmgmt
```

Seems like the firewall was taking down the ovirtmgmt interface.

Disabling firewalld and installing/enabling iptables/ip6tables service. I then did a engine-cleanup proceeded by engine-setup.

This time it worked.

Comment 1 Dan Kenigsberg 2014-09-25 16:35:42 UTC

Note that http://gerrit.ovirt.org/33171 only conflicts with firewalld and NetworkManager; it does not solve (nor aims to solve, nor understands) the real problem. Hence, we should keep this bug open and researched.

Comment 2 Aaron Ogle 2014-09-26 14:20:02 UTC

Also after installed, firewalld being up seems to cause the ovirtmgmt interface to loose its ip.  Seemingly its removing the ip.

Comment 3 Antoni Segura Puimedon 2014-09-26 21:13:11 UTC

For now, it is better to run vdsm with iptables and without firewalld nor NetworkManager due to the problem that Aaron mentions and others that are being sorted out.

Comment 5 Dan Kenigsberg 2015-09-08 09:47:14 UTC


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