Description of problem: After rebooting a host there is no gateway specified, although just running dhclient manually workarounds the issue. There is some dhclient usage message in journalctl, so maybe some vdsm scripts use dhclient incorrectly. Without vdsm packages I can reboot the host and also get correct gateway. Version-Release number of selected component (if applicable): 4.2 master vdsm-4.20.0-859 How reproducible: always on physical host in TLV, not on virtual host in BRQ though Steps to Reproduce: 1. reboot the host Actual results: host is non responsive and doesn't have gateway specified Expected results: host is up after rebooting is done Additional info:
Can you also attach supervdsm.log as well as the content of /var/lib/vdsm/
This is a good catch, we have a bug when deleting a sourceroute. Instead of deleting a route from a specific table, we deleted the route from any table.
Petr, could you please try and apply the patch submitted to confirm it resolves the problem you saw? https://gerrit.ovirt.org/#/c/77321
Yes, it resolves the problem :)
Verified on vdsm-4.20.0-954.gita1adf06.el7.centos.x86_64
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.