Description of problem:
restarting network service manually on server, causing to all network configuration to break. cause the onboot=no is set to no, on all NICs and networks ifcfg files, except the management network and the NIC it attached to.
- This is the case since we moved to unified
persistence - which has happened almost a year ago
http://gerrit.ovirt.org/25784
- vdsm will take care of that only when restarting the vdsmd service or rebooting the server.
Version-Release number of selected component (if applicable):
3.5.1-0.4.el6ev
as well on 3.6.0-0.0.master.20150412172306.git55ba764.el6
How reproducible:
100
Additional info:
service network restart; rm /var/run/vdsm/nets_restored; vdsm-tool restore-nets
is the intended workaround for it.
`service network restart` is equivalent to ifdown'ing all ifcfg files, and later ifup'ing them - but only these with ONBOOT=yes.
When using unified persistence, we have to set ONBOOT=no, to avoid wasting expensive boot time, particularly when DHCP is involved http://gerrit.ovirt.org/27541.
We could avoid this need once we manage to start vdsm-network before the network service is started.
Description of problem: restarting network service manually on server, causing to all network configuration to break. cause the onboot=no is set to no, on all NICs and networks ifcfg files, except the management network and the NIC it attached to. - This is the case since we moved to unified persistence - which has happened almost a year ago http://gerrit.ovirt.org/25784 - vdsm will take care of that only when restarting the vdsmd service or rebooting the server. Version-Release number of selected component (if applicable): 3.5.1-0.4.el6ev as well on 3.6.0-0.0.master.20150412172306.git55ba764.el6 How reproducible: 100 Additional info: service network restart; rm /var/run/vdsm/nets_restored; vdsm-tool restore-nets is the intended workaround for it.