Bug 1332076 - [ipv6autoconf] - Vdsm reconfigure network with u'ipv6autoconf': False every reboot
Summary: [ipv6autoconf] - Vdsm reconfigure network with u'ipv6autoconf': False every r...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: Core
Version: 4.18.0
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: ovirt-4.0.0-rc
: 4.18.3
Assignee: Edward Haas
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks: RHEV_IPv6 1341260
TreeView+ depends on / blocked
 
Reported: 2016-05-02 06:23 UTC by Michael Burman
Modified: 2016-09-13 05:38 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1341260 (view as bug list)
Environment:
Last Closed: 2016-07-05 07:46:55 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-4.0.0+
ylavi: planning_ack+
danken: devel_ack+
rule-engine: testing_ack+


Attachments (Terms of Use)
vdsm logs (1.62 MB, application/x-gzip)
2016-05-02 06:23 UTC, Michael Burman
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 58971 0 master MERGED net: Canonicalize and 'translate' ipv6autoconf 2016-06-11 05:04:09 UTC
oVirt gerrit 59030 0 ovirt-4.0 MERGED net: Canonicalize and 'translate' ipv6autoconf 2016-06-13 09:00:03 UTC

Description Michael Burman 2016-05-02 06:23:46 UTC
Created attachment 1152860 [details]
vdsm logs

Description of problem:
[ipv6autoconf] - Vdsm reconfigure network with u'ipv6autoconf': False every reboot. 

As vdsm recognize a change on a network between the current and the persistent configuration for the ipv6autoconf property, it's touching and reconfigure the networks every reboot with:
persisted: {u'ipv6autoconf': False,

supervdsm.log --> 

restore-net::INFO::2016-05-02 08:52:40,410::vdsm-restore-net-config::283::root::(_find_changed_or_missing) ovirtmgmt is different or missing from persistent configuration. current: {'nic': 'enp4s0', 'dhcpv6': Fals
e, 'mtu': 1500, 'switch': 'legacy', 'bootproto': 'dhcp', 'stp': False, 'bridged': True, 'defaultRoute': True}, persisted: {u'ipv6autoconf': False, u'nic': u'enp4s0', u'mtu': 1500, u'switch': u'legacy', u'dhcpv6': 
False, u'stp': False, u'bridged': True, u'defaultRoute': True, u'bootproto': u'dhcp'}
restore-net::INFO::2016-05-02 08:52:40,410::vdsm-restore-net-config::283::root::(_find_changed_or_missing) n-3 is different or missing from persistent configuration. current: {'nic': 'ens1f0', 'ipaddr': '5.5.5.5',
 'netmask': '255.255.255.0', 'mtu': 1500, 'switch': 'legacy', 'dhcpv6': False, 'stp': False, 'bridged': True, 'defaultRoute': False, 'bootproto': 'none'}, persisted: {u'ipv6autoconf': False, u'nic': u'ens1f0', u'i
paddr': u'5.5.5.5', u'netmask': u'255.255.255.0', u'mtu': 1500, u'switch': u'legacy', u'dhcpv6': False, u'stp': False, u'bridged': True, 'defaultRoute': False, 'bootproto': 'none'}


Version-Release number of selected component (if applicable):
vdsm-4.17.999-1032.git4e6068b.el7.centos.noarch
vdsm-4.17.999-988.git74ab551.el7.centos.noarch
4.0.0-0.0.master.20160423161403.gite38df80.el7.centos

How reproducible:
100

Steps to Reproduce:
1. Add host(vdsm 4.0) to 4.0 engine 
2. Attach some networks to host via setup networks
3. Reboot server and check the supervdsm.log 

Actual results:
vdsm recognize a difference between what was persistent and the current configuration for networks on the ipv6autoconf property and reconfigure the networks every reboot

Expected results:
vdsm shouldn't reconfigure the networks every reboot with 
{u'ipv6autoconf': False

Comment 1 Michael Burman 2016-05-02 08:53:32 UTC
This is correct for u'ipv6autoconf': True as well

restore-net::INFO::2016-05-02 11:49:16,531::vdsm-restore-net-config::283::root::(_find_changed_or_missing) ovirtmgmt is different or missing from persistent configuration. current: {'nic': 'enp4s0', 'dhcpv6': Fals
e, 'mtu': 1500, 'switch': 'legacy', 'bootproto': 'dhcp', 'stp': False, 'bridged': True, 'defaultRoute': True}, persisted: {u'ipv6autoconf': True, u'nic': u'enp4s0', u'mtu': 1500, u'switch': u'legacy', u'dhcpv6': F
alse, u'stp': False, u'bridged': True, u'defaultRoute': True, u'bootproto': u'dhcp'}

Comment 2 Red Hat Bugzilla Rules Engine 2016-05-04 08:20:07 UTC
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 3 Michael Burman 2016-06-23 07:53:23 UTC
Verified on - vdsm-4.18.4-2.el7ev.x86_64

Comment 4 Sandro Bonazzola 2016-07-05 07:46:55 UTC
oVirt 4.0.0 has been released, closing current release.


Note You need to log in before you can comment on or make changes to this bug.