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

Bug 1778615

Summary:	Ensure that NetworkManager is restarted if host-deploy via ansible is used
Product:	[oVirt] ovirt-host-deploy	Reporter:	Dominik Holler <dholler>
Component:	Core	Assignee:	Ales Musil <amusil>
Status:	CLOSED WONTFIX	QA Contact:	Michael Burman <mburman>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	master	CC:	bugs, mperina
Target Milestone:	---
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:	2020-03-17 13:44:09 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:	1765057
Bug Blocks:

Description Dominik Holler 2019-12-02 08:25:04 UTC

Ensure that NetworkManager is restarted if host-deploy via ansible is used

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


How reproducible:


Steps to Reproduce:
1. Add host to Engine
2. 
3.

Actual results:
With bug 1765057 fixed, NetworkManager is already restarted. This bug ensures that the behavior is kept, if the implementation if host-deploy uses ansible. 

Expected results:
Ensure that NetworkManager is restarted after packages on the host are updated/installed.

Additional info:
That the restart is required and has the desired effect, is not part of this bug.

Comment 3 Michael Burman 2020-01-20 13:24:06 UTC

Verified on - 4.4.0-0.14.master.el7

Comment 4 Sandro Bonazzola 2020-03-17 13:44:09 UTC

Closing won't fix. We are not shipping ovirt-host-deploy in 4.4