Bug 1594778

Summary: [IPv6] - During host install, getCaps reports dhcpv6=true for iface although DHCPV6C=no in ifcfg-<iface>
Product: [oVirt] vdsm Reporter: eraviv
Component: GeneralAssignee: Petr Horáček <phoracek>
Status: CLOSED NOTABUG QA Contact: Meni Yakove <myakove>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.30.0CC: amusil, bugs, danken, dholler, eraviv, fkust
Target Milestone: ovirt-4.4.0Flags: rule-engine: ovirt-4.4+
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: 2019-02-12 12:35:01 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: 1080725    

Description eraviv 2018-06-25 12:13:03 UTC
Description of problem:

During host install, getCaps reports dhcpv6=true although it is set to no in the ifcfg of the iface on top of which vdsm is about to create ovirtmgmt bridge.

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


How reproducible:
100%

Steps to Reproduce:
1. in ifcfg-eth0 set IPV6_AUTOCONF=yes, DHCPV6C=no
2. ifdown eth0 && ifup eth0
3. vdsm-client Host getCapabilities | grep eth0

Actual results:
{
     ...
             "eth0": {
            "ipv6autoconf": true, 
            "dhcpv6": true
     ...
}

Expected results:
{
     ...
             "eth0": {
            "ipv6autoconf": true, 
            "dhcpv6": false
     ...
}

Additional info:
CentOS Linux release 7.4.1708 (Core)
vdsm-4.30.0-166.git9fe9abd.el7.centos.x86_64
NetworkManager-1.8.0-11.el7_4.x86_64

Comment 1 Dominik Holler 2019-02-11 14:24:45 UTC
Eitan, is the issue still reproducing? If not, please close the bug.

Comment 2 Ales Musil 2019-02-12 12:35:01 UTC
(In reply to Dominik Holler from comment #1)
> Eitan, is the issue still reproducing? If not, please close the bug.

We could not reproduce the issue. Closing the bug.

Comment 3 Franta Kust 2019-04-23 14:09:33 UTC
Update with no chances just to propagate proper Jira Resolution.