Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1197668 - After failure to setupNetworks: restore-nets with unified persistence does not restore pre-vdsm ifcfg
After failure to setupNetworks: restore-nets with unified persistence does no...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm (Show other bugs)
3.5.0
x86_64 Linux
urgent Severity urgent
: ---
: 3.5.0-2
Assigned To: Petr Horáček
Martin Pavlik
network
: ZStream
Depends On: 1188251 1199012
Blocks: 1197443
  Show dependency treegraph
 
Reported: 2015-03-02 06:20 EST by rhev-integ
Modified: 2017-03-07 06:50 EST (History)
34 users (show)

See Also:
Fixed In Version: vt13.12
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1188251
Environment:
Last Closed: 2015-03-06 15:24:46 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Network
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 1346443 None None None Never
oVirt gerrit 37453 master MERGED network: store non-Vdsm ifcfgs with unified persistence Never
oVirt gerrit 38240 ovirt-3.5 MERGED network: store non-Vdsm ifcfgs with unified persistence Never
Red Hat Product Errata RHBA-2015:0649 normal SHIPPED_LIVE vdsm 3.5.0-2 ASYNC - bug fix and enhancement update 2015-03-06 20:24:29 EST

  None (edit)
Comment 1 Eyal Edri 2015-03-03 03:56:33 EST
danken, this patch is merged (15892), any other patch is pending or this is ready to move to MODIFIED?
Comment 3 Martin Pavlik 2015-03-05 05:21:40 EST
verification blocked by bug 1199012
Comment 4 Martin Pavlik 2015-03-05 07:28:56 EST
verifed @ vdsm-4.16.8.1-7.el6ev.x86_64

Steps:
1) manually configure bond0 on host
2) change MTU on rhevm network to 8000000
3) add the host from step 1 to setup
4) installation of the host succeeds, but the network configuration fails
5) pre-vdsm ifcfg files are rolled back


snippets of log

MainProcess|Thread-17::DEBUG::2015-03-05 12:07:42,418::ifcfg::450::root::(_persistentBackup) backing up ifcfg-eth0: #pre-vdsm
DEVICE=eth0
USERCTL=no
ONBOOT=yes
MASTER=bond0
SLAVE=yes
BOOTPROTO=none

MainProcess|Thread-17::DEBUG::2015-03-05 12:07:42,419::ifcfg::313::root::(writeBackupFile) Persistently backed up /var/lib/vdsm/netconfback/ifcfg-eth0 (until next 'set safe config')
MainProcess|Thread-17::DEBUG::2015-03-05 12:07:42,419::ifcfg::550::root::(writeConfFile) Writing to file /etc/sysconfig/network-scripts/ifcfg-eth0 configuration:
# Generated by VDSM version 4.16.8.1-7.el6ev
DEVICE=eth0
HWADDR=00:1a:4a:16:01:51
MASTER=bond0
SLAVE=yes
ONBOOT=yes
MTU=80000000
NM_CONTROLLED=no

MainProcess|Thread-17::DEBUG::2015-03-05 12:07:42,419::utils::739::root::(execCmd) /sbin/ip route show to 0.0.0.0/0 table all (cwd None)
MainProcess|Thread-17::DEBUG::2015-03-05 12:07:42,421::utils::759::root::(execCmd) SUCCESS: <err> = ''; <rc> = 0
MainProcess|Thread-17::DEBUG::2015-03-05 12:07:42,426::ifcfg::374::root::(_atomicBackup) Backed up /etc/sysconfig/network-scripts/ifcfg-eth1
MainProcess|Thread-17::DEBUG::2015-03-05 12:07:42,426::ifcfg::450::root::(_persistentBackup) backing up ifcfg-eth1: #pre-vdsm
DEVICE=eth1
USERCTL=no
ONBOOT=yes
MASTER=bond0
SLAVE=yes
BOOTPROTO=none
.
.
.
.
MainProcess|Thread-17::DEBUG::2015-03-05 12:07:42,426::ifcfg::313::root::(writeBackupFile) Persistently backed up /var/lib/vdsm/netconfback/ifcfg-eth1 (until next 'set safe config')
MainProcess|Thread-17::DEBUG::2015-03-05 12:07:42,426::ifcfg::550::root::(writeConfFile) Writing to file /etc/sysconfig/network-scripts/ifcfg-eth1 configuration:
# Generated by VDSM version 4.16.8.1-7.el6ev
DEVICE=eth1
HWADDR=00:1a:4a:16:01:53
MASTER=bond0
SLAVE=yes
ONBOOT=yes
MTU=80000000
NM_CONTROLLED=no
.
.
.
MainProcess|Thread-17::INFO::2015-03-05 12:09:43,716::api::687::setupNetworks::(setupNetworks) Connectivity check failed, rolling back
.
.
.
.
ainProcess|Thread-17::INFO::2015-03-05 12:09:44,019::ifcfg::391::root::(restoreAtomicBackup) Restored /etc/sysconfig/network-scripts/ifcfg-rhevm
MainProcess|Thread-17::INFO::2015-03-05 12:09:44,020::ifcfg::391::root::(restoreAtomicBackup) Restored /etc/sysconfig/network-scripts/ifcfg-eth1
MainProcess|Thread-17::INFO::2015-03-05 12:09:44,020::ifcfg::391::root::(restoreAtomicBackup) Restored /etc/sysconfig/network-scripts/ifcfg-eth0
MainProcess|Thread-17::INFO::2015-03-05 12:09:44,020::ifcfg::391::root::(restoreAtomicBackup) Restored /etc/sysconfig/network-scripts/ifcfg-bond0
Comment 6 errata-xmlrpc 2015-03-06 15:24:46 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0649.html
Comment 13 Dan Kenigsberg 2015-03-13 05:58:29 EDT
Ulhas, Pavel: please note that this bug is NOT the same issue of the "vanishing bond" bug 1154399.

The our bug 1197668 is about rolling back to manually-configured ifcfg files in case of failure in setupNetworks. In 99% of the cases it is unrelated to rhev-h (where users do not edit ifcfg files manually), and as such, it is not planned to be released in a node image.

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