Bug 1778615 - Ensure that NetworkManager is restarted if host-deploy via ansible is used
Summary: Ensure that NetworkManager is restarted if host-deploy via ansible is used
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-host-deploy
Classification: oVirt
Component: Core
Version: master
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Ales Musil
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On: 1765057
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-02 08:25 UTC by Dominik Holler
Modified: 2022-02-23 14:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-17 13:44:09 UTC
oVirt Team: Network
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-44789 0 None None None 2022-02-23 14:24:29 UTC

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
Note You need to log in before you can comment on or make changes to this bug.