Bug 1226056 - Restarting VDSM with vdsm--4.16.13.1-1 removes changes to ifcfg- network scripts
Summary: Restarting VDSM with vdsm--4.16.13.1-1 removes changes to ifcfg- network scripts
Keywords:
Status: CLOSED DUPLICATE of bug 1203422
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 3.5.1
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: ---
: ---
Assignee: Ido Barkan
QA Contact: Aharon Canan
URL:
Whiteboard: network
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-28 21:14 UTC by Robert McSwain
Modified: 2019-07-16 11:58 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-08 10:08:20 UTC
oVirt Team: Network
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Robert McSwain 2015-05-28 21:14:21 UTC
Customer successfully updated 2 hosts to the 20150512 RHEV-H release via the "Upgrade" button in RHEV-M. Reading through the various bugs linked in https://access.redhat.com/solutions/1346443. He noted that it is now by design that ONBOOT=no for the various networks, and set the following ifcfg files to ONBOOT=yes and persisted them. Below is the console output prior to upgrade:

-----------------
[root@cl3-d14-p2c2n8 ~]# ll /config/etc/sysconfig/network-scripts/
total 4
-rw-r--r--. 1 root root 73 2015-05-12 20:52 ifcfg-eth0
-rw-r--r--. 1 root root 64 2015-05-12 20:52 ifcfg-lo
[root@cl3-d14-p2c2n8 ~]# cd /etc/sysconfig/network-scripts/
[root@cl3-d14-p2c2n8 network-scripts]# grep ONBOOT=no *
ifcfg-bond0.1100:ONBOOT=no
ifcfg-bond0.13:ONBOOT=no
ifcfg-bond0.1302:ONBOOT=no
ifcfg-bond0.20:ONBOOT=no
ifcfg-bond0.2000:ONBOOT=no
ifcfg-bond0.2001:ONBOOT=no
ifcfg-bond0.2002:ONBOOT=no
ifcfg-bond0.2003:ONBOOT=no
ifcfg-bond0.260:ONBOOT=no
ifcfg-bond0.29:ONBOOT=no
ifcfg-bond0.30:ONBOOT=no
ifcfg-bond0.320:ONBOOT=no
ifcfg-bond0.35:ONBOOT=no
ifcfg-bond0.9:ONBOOT=no
ifcfg-Cluster1:ONBOOT=no
ifcfg-Display:ONBOOT=no
ifcfg-Lambent:ONBOOT=no
ifcfg-Login:ONBOOT=no
ifcfg-MetroPrivate:ONBOOT=no
ifcfg-PMI:ONBOOT=no
ifcfg-Public:ONBOOT=no
ifcfg-vlan0020:ONBOOT=no
ifcfg-vlan0035:ONBOOT=no
ifcfg-vlan0320:ONBOOT=no
ifcfg-vlan1302:ONBOOT=no
ifcfg-vlan2000:ONBOOT=no
ifcfg-vlan2002:ONBOOT=no
ifcfg-vlan2003:ONBOOT=no
[root@cl3-d14-p2c2n8 network-scripts]# grep ONBOOT=yes *
ifcfg-bond0:ONBOOT=yes
ifcfg-bond0.258:ONBOOT=yes
ifcfg-eth0:ONBOOT=yes
ifcfg-eth1:ONBOOT=yes
ifcfg-rhevm:ONBOOT=yes
[root@cl3-d14-p2c2n8 network-scripts]# fils=`grep -l ONBOOT=no *`; for nn in $fils; do sed -i -e 's/ONBOOT=no/ONBOOT=yes/g' $nn; persist $nn; done
[root@cl3-d14-p2c2n8 network-scripts]# vi /etc/vdsm/vdsm.conf
[root@cl3-d14-p2c2n8 network-scripts]# cat /etc/vdsm/vdsm.conf
[addresses]
management_port = 54321

[vars]
ssl = true
net_persist = ifcfg
---------------

After the above console procedure and after clicking "Upgrade" in RHEV-M, the host rebooted as expected and the networks were up. On several hosts, he left the ONBOOT settings as VDSM configured them. The following ifcfg scripts as "yes":

[root@cl3-d14-p1c2n4 network-scripts]# grep ONBOOT=yes *
ifcfg-bond0:ONBOOT=yes
ifcfg-bond0.258:ONBOOT=yes
ifcfg-eth0:ONBOOT=yes
ifcfg-eth1:ONBOOT=yes
ifcfg-rhevm:ONBOOT=yes

All others were set to "no". he persisted all ifcfg scripts, edited vdsm.conf, then ran the upgrade procedure. The host upgraded and recovered as expected, with all networks present. However, the persisted files are no longer there:

[root@cl3-d14-p1c2n4 network-scripts]# ll /config/etc/sysconfig/network-scripts/
total 2
-rw-r--r--. 1 root root 64 2015-04-30 23:54 ifcfg-lo


How Reproducible:
100%

How to Reproduce:
- After clicking "Save Network Configuration" no files are present in /config/etc/sysconfg/network-scripts
- After manually persisting the ifcfg files via CLI, a reboot (either manual, from the setup TUI, or via the upgrade the process) will wipe all the persisted files in /config/etc/sysconfg/network-scripts
- The end result is that after persisting the files and 2 reboots, the host is unreachable.

Expected Behavior: 
All ifcfg-* files are left as is rather than changing when vdsm is restarted either by a service restart or a full system reboot. 

Actual Behavior:
ifcfg-* files are reverted or emptied when vdsm is restarted.

Additional Information:
Pre- and post-upgrade log collections will be provided for a host where he

- did not edit the ONBOOT flags (i.e., they are as vdsm configured them)
- persisted the ifcfg files
- edited /etc/vdsm/vdsm.conf
- performed the upgrade via the "Upgrade" button in RHEV-M

The log collections were run with the following command from the RHEV-M controller:

Below is the console output from the host pre-upgrade:
----------------------------------

[root@cl3-d14-p2c1n1 ~]# cd /etc/sysconfig/network-scripts; grep ONBOOT=no *; echo --------;grep ONBOOT=yes *
ifcfg-bond0.1100:ONBOOT=no
ifcfg-bond0.13:ONBOOT=no
ifcfg-bond0.1302:ONBOOT=no
ifcfg-bond0.20:ONBOOT=no
ifcfg-bond0.2000:ONBOOT=no
ifcfg-bond0.2001:ONBOOT=no
ifcfg-bond0.2002:ONBOOT=no
ifcfg-bond0.2003:ONBOOT=no
ifcfg-bond0.260:ONBOOT=no
ifcfg-bond0.29:ONBOOT=no
ifcfg-bond0.30:ONBOOT=no
ifcfg-bond0.320:ONBOOT=no
ifcfg-bond0.35:ONBOOT=no
ifcfg-bond0.9:ONBOOT=no
ifcfg-Cluster1:ONBOOT=no
ifcfg-Display:ONBOOT=no
ifcfg-Lambent:ONBOOT=no
ifcfg-Login:ONBOOT=no
ifcfg-MetroPrivate:ONBOOT=no
ifcfg-PMI:ONBOOT=no
ifcfg-Public:ONBOOT=no
ifcfg-vlan0020:ONBOOT=no
ifcfg-vlan0035:ONBOOT=no
ifcfg-vlan0320:ONBOOT=no
ifcfg-vlan1302:ONBOOT=no
ifcfg-vlan2000:ONBOOT=no
ifcfg-vlan2002:ONBOOT=no
ifcfg-vlan2003:ONBOOT=no
--------
ifcfg-bond0:ONBOOT=yes
ifcfg-bond0.258:ONBOOT=yes
ifcfg-eth0:ONBOOT=yes
ifcfg-eth1:ONBOOT=yes
ifcfg-rhevm:ONBOOT=yes
[root@cl3-d14-p2c1n1 network-scripts]# persist /etc/sysconfig/network-scripts/ifcfg-*
[root@cl3-d14-p2c1n1 network-scripts]# ll /config/etc/sysconfig/network-scripts
total 68
-rw-rw-r--. 1 root root 140 2015-05-04 16:32 ifcfg-bond0
-rw-rw-r--. 1 root root 131 2015-05-04 16:33 ifcfg-bond0.1100
-rw-rw-r--. 1 root root 132 2015-05-04 16:32 ifcfg-bond0.13
-rw-rw-r--. 1 root root 136 2015-05-04 16:33 ifcfg-bond0.1302
-rw-rw-r--. 1 root root 134 2015-05-04 16:33 ifcfg-bond0.20
-rw-rw-r--. 1 root root 136 2015-05-04 16:33 ifcfg-bond0.2000
-rw-rw-r--. 1 root root 133 2015-05-04 16:33 ifcfg-bond0.2001
-rw-rw-r--. 1 root root 136 2015-05-04 16:33 ifcfg-bond0.2002
-rw-rw-r--. 1 root root 136 2015-05-20 11:28 ifcfg-bond0.2003
-rw-rw-r--. 1 root root 133 2015-05-04 16:32 ifcfg-bond0.258
-rw-rw-r--. 1 root root 134 2015-05-04 16:33 ifcfg-bond0.260
-rw-rw-r--. 1 root root 138 2015-05-04 16:33 ifcfg-bond0.29
-rw-rw-r--. 1 root root 133 2015-05-04 16:33 ifcfg-bond0.30
-rw-rw-r--. 1 root root 135 2015-05-04 16:32 ifcfg-bond0.320
-rw-rw-r--. 1 root root 134 2015-05-04 16:33 ifcfg-bond0.35
-rw-rw-r--. 1 root root 133 2015-05-04 16:32 ifcfg-bond0.9
-rw-rw-r--. 1 root root 149 2015-05-04 16:32 ifcfg-Cluster1
-rw-rw-r--. 1 root root 227 2015-05-04 16:33 ifcfg-Display
-rw-rw-r--. 1 root root 143 2015-05-04 16:32 ifcfg-eth0
-rw-rw-r--. 1 root root 143 2015-05-04 16:32 ifcfg-eth1
-rw-rw-r--. 1 root root 148 2015-05-04 16:33 ifcfg-Lambent
-rw-r--r--. 1 root root  64 2015-05-04 16:25 ifcfg-lo
-rw-rw-r--. 1 root root 146 2015-05-04 16:33 ifcfg-Login
-rw-rw-r--. 1 root root 153 2015-05-04 16:33 ifcfg-MetroPrivate
-rw-rw-r--. 1 root root 144 2015-05-04 16:33 ifcfg-PMI
-rw-rw-r--. 1 root root 147 2015-05-04 16:32 ifcfg-Public
-rw-rw-r--. 1 root root 227 2015-05-04 16:32 ifcfg-rhevm
-rw-rw-r--. 1 root root 149 2015-05-04 16:33 ifcfg-vlan0020
-rw-rw-r--. 1 root root 149 2015-05-04 16:33 ifcfg-vlan0035
-rw-rw-r--. 1 root root 149 2015-05-04 16:32 ifcfg-vlan0320
-rw-rw-r--. 1 root root 149 2015-05-04 16:33 ifcfg-vlan1302
-rw-rw-r--. 1 root root 149 2015-05-04 16:33 ifcfg-vlan2000
-rw-rw-r--. 1 root root 149 2015-05-04 16:33 ifcfg-vlan2002
-rw-rw-r--. 1 root root 149 2015-05-20 11:28 ifcfg-vlan2003
[root@cl3-d14-p2c1n1 network-scripts]# cat /etc/vdsm/vdsm.conf
[addresses]
management_port = 54321

[vars]
ssl = true
net_persist = ifcfg

[root@cl3-d14-p2c1n1 network-scripts]#

----------------------------------
Below is the console output from the host post-upgrade:
----------------------------------

[root@cl3-d14-p2c1n1 ~]# cd /etc/sysconfig/network-scripts; grep ONBOOT=no *; echo --------;grep ONBOOT=yes *
ifcfg-bond0.1100:ONBOOT=no
ifcfg-bond0.13:ONBOOT=no
ifcfg-bond0.1302:ONBOOT=no
ifcfg-bond0.20:ONBOOT=no
ifcfg-bond0.2000:ONBOOT=no
ifcfg-bond0.2001:ONBOOT=no
ifcfg-bond0.2002:ONBOOT=no
ifcfg-bond0.2003:ONBOOT=no
ifcfg-bond0.260:ONBOOT=no
ifcfg-bond0.29:ONBOOT=no
ifcfg-bond0.30:ONBOOT=no
ifcfg-bond0.320:ONBOOT=no
ifcfg-bond0.35:ONBOOT=no
ifcfg-bond0.9:ONBOOT=no
ifcfg-Cluster1:ONBOOT=no
ifcfg-Display:ONBOOT=no
ifcfg-Lambent:ONBOOT=no
ifcfg-Login:ONBOOT=no
ifcfg-MetroPrivate:ONBOOT=no
ifcfg-PMI:ONBOOT=no
ifcfg-Public:ONBOOT=no
ifcfg-vlan0020:ONBOOT=no
ifcfg-vlan0035:ONBOOT=no
ifcfg-vlan0320:ONBOOT=no
ifcfg-vlan1302:ONBOOT=no
ifcfg-vlan2000:ONBOOT=no
ifcfg-vlan2002:ONBOOT=no
ifcfg-vlan2003:ONBOOT=no
--------
ifcfg-bond0:ONBOOT=yes
ifcfg-bond0.258:ONBOOT=yes
ifcfg-eth0:ONBOOT=yes
ifcfg-eth1:ONBOOT=yes
ifcfg-rhevm:ONBOOT=yes
[root@cl3-d14-p2c1n1 network-scripts]# ll /config/etc/sysconfig/network-scripts
total 2
-rw-r--r--. 1 root root 64 2015-05-04 16:25 ifcfg-lo

Comment 2 Barak 2015-05-31 12:07:42 UTC
I see only upgrade to version.

What version was it upgraded from ? was it a clean install than ?

Comment 4 Dan Kenigsberg 2015-06-08 10:08:20 UTC

*** This bug has been marked as a duplicate of bug 1203422 ***


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