So, I try to manually start vdsm-network.service and see this,
suggesting I look in upgrade.log:
# systemctl status vdsm-network.service
● vdsm-network.service - Virtual Desktop Server Manager network restoration
Loaded: loaded (/usr/lib/systemd/system/vdsm-network.service;
enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2019-01-19 10:25:02
PST; 8s ago
Process: 6845 ExecStart=/usr/bin/vdsm-tool restore-nets (code=exited,
status=1/FAILURE)
Process: 6837 ExecStartPre=/usr/bin/vdsm-tool --vvverbose --append
--logfile=/var/log/vdsm/upgrade.log upgrade-unified-persistence
(code=exited, status=0/SUCCESS)
Main PID: 6845 (code=exited, status=1/FAILURE)
Jan 19 10:25:02 vmserver2 vdsm-tool[6845]: return
tool_command[cmd]["command"](*args)
Jan 19 10:25:02 vmserver2 vdsm-tool[6845]: File
"/usr/lib/python2.7/site-packages/vdsm/tool/restore_nets.py", line 41,
in restore_command
Jan 19 10:25:02 vmserver2 vdsm-tool[6845]: exec_restore(cmd)
Jan 19 10:25:02 vmserver2 vdsm-tool[6845]: File
"/usr/lib/python2.7/site-packages/vdsm/tool/restore_nets.py", line 54,
in exec_restore
Jan 19 10:25:02 vmserver2 vdsm-tool[6845]: raise
EnvironmentError('Failed to restore the persisted networks')
Jan 19 10:25:02 vmserver2 vdsm-tool[6845]: EnvironmentError: Failed to
restore the persisted networks
Jan 19 10:25:02 vmserver2 systemd[1]: vdsm-network.service: main process
exited, code=exited, status=1/FAILURE
Jan 19 10:25:02 vmserver2 systemd[1]: Failed to start Virtual Desktop
Server Manager network restoration.
Jan 19 10:25:02 vmserver2 systemd[1]: Unit vdsm-network.service entered
failed state.
Jan 19 10:25:02 vmserver2 systemd[1]: vdsm-network.service failed.
In upgrade.log I see this:
# cat upgrade.log
MainThread::DEBUG::2016-01-10
10:54:47,615::upgrade::90::upgrade::(apply_upgrade) Running upgrade
upgrade-unified-persistence
MainThread::DEBUG::2016-01-10
10:54:47,623::libvirtconnection::160::root::(get) trying to connect libvirt
MainThread::DEBUG::2016-01-10
10:54:47,639::netinfo::714::root::(_get_gateway) The gateway 192.168.1.1
is duplicated for the device em1
MainThread::DEBUG::2016-01-10 10:54:47,647::utils::669::root::(execCmd)
/sbin/ip route show to 0.0.0.0/0 table main (cwd None)
MainThread::DEBUG::2016-01-10 10:54:47,650::utils::687::root::(execCmd)
SUCCESS: <err> = ''; <rc> = 0
MainThread::DEBUG::2016-01-10
10:54:47,651::unified_persistence::46::root::(run)
upgrade-unified-persistence upgrade persisting networks {} and bondings {}
MainThread::INFO::2016-01-10
10:54:47,651::netconfpersistence::179::root::(_clearDisk) Clearing
/var/run/vdsm/netconf/nets/ and /var/run/vdsm/netconf/bonds/
MainThread::DEBUG::2016-01-10
10:54:47,651::netconfpersistence::187::root::(_clearDisk) No existent
config to clear.
MainThread::INFO::2016-01-10
10:54:47,652::netconfpersistence::179::root::(_clearDisk) Clearing
/var/run/vdsm/netconf/nets/ and /var/run/vdsm/netconf/bonds/
MainThread::DEBUG::2016-01-10
10:54:47,652::netconfpersistence::187::root::(_clearDisk) No existent
config to clear.
MainThread::INFO::2016-01-10
10:54:47,652::netconfpersistence::129::root::(save) Saved new config
RunningConfig({}, {}) to /var/run/vdsm/netconf/nets/ and
/var/run/vdsm/netconf/bonds/
MainThread::DEBUG::2016-01-10 10:54:47,652::utils::669::root::(execCmd)
/usr/share/vdsm/vdsm-store-net-config unified (cwd None)
MainThread::DEBUG::2016-01-10 10:54:47,672::utils::687::root::(execCmd)
SUCCESS: <err> = 'cp: cannot stat
\xe2\x80\x98/var/run/vdsm/netconf\xe2\x80\x99: No such file or
directory\n'; <rc> = 0
MainThread::DEBUG::2016-01-10
10:54:47,672::upgrade::51::upgrade::(_upgrade_seal) Upgrade
upgrade-unified-persistence successfully performed
I see some references to allowing duplicate gateways if identical on the
mailing list...