Bug 1740644 - [nmstate] Add config option for Host deployment with nmstate
Summary: [nmstate] Add config option for Host deployment with nmstate
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: future
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ovirt-4.4.0
: ---
Assignee: Ales Musil
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks: VDSM_use_NetworkManager
TreeView+ depends on / blocked
 
Reported: 2019-08-13 12:20 UTC by Michael Burman
Modified: 2020-05-20 20:02 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-05-20 20:02:19 UTC
oVirt Team: Network
Embargoed:
pm-rhel: ovirt-4.4+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 102602 0 master MERGED core: Add config option for Host deployment with nmstate 2020-10-22 05:18:44 UTC
oVirt gerrit 106307 0 None MERGED core: Remove VdsmUseNmstate config option 2020-10-22 05:18:44 UTC

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