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

Bug 1452185

Summary:	After host reboot host doesn't have gateway
Product:	[oVirt] vdsm	Reporter:	Petr Matyáš <pmatyas>
Component:	General	Assignee:	Edward Haas <edwardh>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Raz Tamir <ratamir>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.20.0	CC:	bugs, danken, pmatyas
Target Milestone:	ovirt-4.2.0	Flags:	rule-engine: ovirt-4.2+
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:	2017-12-20 11:26:11 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:

Description Petr Matyáš 2017-05-18 13:40:41 UTC

Description of problem:
After rebooting a host there is no gateway specified, although just running dhclient manually workarounds the issue.
There is some dhclient usage message in journalctl, so maybe some vdsm scripts use dhclient incorrectly.
Without vdsm packages I can reboot the host and also get correct gateway.

Version-Release number of selected component (if applicable):
4.2 master
vdsm-4.20.0-859

How reproducible:
always on physical host in TLV, not on virtual host in BRQ though

Steps to Reproduce:
1. reboot the host

Actual results:
host is non responsive and doesn't have gateway specified

Expected results:
host is up after rebooting is done

Additional info:

Comment 2 Dan Kenigsberg 2017-05-21 11:22:01 UTC

Can you also attach supervdsm.log as well as the content of /var/lib/vdsm/

Comment 4 Edward Haas 2017-05-25 09:14:52 UTC

This is a good catch, we have a bug when deleting a sourceroute.
Instead of deleting a route from a specific table, we deleted the route from any table.

Comment 5 Edward Haas 2017-05-25 09:18:00 UTC

Petr, could you please try and apply the patch submitted to confirm it resolves the problem you saw? https://gerrit.ovirt.org/#/c/77321

Comment 6 Petr Matyáš 2017-05-29 11:22:04 UTC

Yes, it resolves the problem :)

Comment 7 Petr Matyáš 2017-06-07 08:03:05 UTC

Verified on vdsm-4.20.0-954.gita1adf06.el7.centos.x86_64

Comment 8 Sandro Bonazzola 2017-12-20 11:26:11 UTC

This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.