Bug 1734792

Summary: [Test-Only] Ensure that the extra_ipv4_addrs vdsm hook is still working on ovirt-4.4
Product: [oVirt] vdsm Reporter: Dominik Holler <dholler>
Component: GeneralAssignee: Bell Levin <blevin>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.40.0CC: bugs, mperina
Target Milestone: ovirt-4.4.0Flags: mperina: ovirt-4.4?
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-20 20:04:27 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: 1107803    
Bug Blocks:    

Description Dominik Holler 2019-07-31 13:08:04 UTC
Description of problem:
The extra_ipv4_addrs vdsm hook will not work anymore if VDSM will use the network manager based driver nmstate.

For this reason this hook has to be updated to work with nmstate or be removed from VDSM and the docs.

Comment 3 Michael Burman 2020-03-17 06:37:59 UTC
Verified on - 
vdsm-4.40.5-1.el8ev.x86_64
vdsm-hook-extra-ipv4-addrs-4.40.5-1.el8ev.x86_64
rhvm-4.4.0-0.25.master.el8ev.noarch

Comment 4 Michael Burman 2020-03-17 06:40:06 UTC
The hook works fine with nmstate and NM

IP4.ADDRESS[1]:                         5.5.5.5/24
IP4.ADDRESS[2]:                         5.5.5.8/24

ipv4:
    address:
    - ip: 5.5.5.5
      prefix-length: 24
    - ip: 5.5.5.8
      prefix-length: 24
    - ip: 5.5.5.6
      prefix-length: 24

nmstate-0.2.6-4.8.el8.noarch
NetworkManager-1.22.8-4.el8.x86_64

Comment 5 Sandro Bonazzola 2020-05-20 20:04:27 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.