Bug 1740644

Summary: [nmstate] Add config option for Host deployment with nmstate
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: BLL.NetworkAssignee: Ales Musil <amusil>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: high Docs Contact:
Priority: high    
Version: futureCC: amusil, bugs, dholler, rdlugyhe
Target Milestone: ovirt-4.4.0Flags: pm-rhel: ovirt-4.4+
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
The current release adds a configuration option, VdsmUseNmstate, which you can use to enable nmstate on every new host with cluster compatibility level >= 4.4.
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-20 20:02:19 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: 1107803    

Description Michael Burman 2019-08-13 12:20:50 UTC
Description of problem:
[nmstate] Add config option for Host deployment with nmstate

Version-Release number of selected component (if applicable):
rhvm-4.4.0-0.1.master.el7.noarch

Add VdsmUseNmstate config option that helps with nmstate and vdsm deployment. This option only takes care about the vdsm.conf by adding 'net_nmstate_enabled=true' if enabled. nmstate package has to be installed before deployment.

How reproducible:
100%

Comment 1 Michael Burman 2019-10-23 13:53:43 UTC
Verified on - rhvm-4.4.0-0.4.master.el7.noarch

Comment 2 Dominik Holler 2020-01-20 13:19:00 UTC
This feature is removed by https://gerrit.ovirt.org/#/c/106307/

Comment 5 Sandro Bonazzola 2020-05-20 20:02:19 UTC
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

Since the problem described in this bug report should be
resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE.

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