Created attachment 779378 [details] vdsm log Description of problem: If you add network x with gateway configuration to Host that doesn't contain IP rules ( for example upgraded host from 3.2 to 3.3) then Host looses connectivity. Even after 2 minutes(default value), when the Host is supposed to come back after check connectivity failure it does not as the default gateway configuration is missing in the routing table Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Take the host without IP rules configured (for example host upgraded from 3.2) 2. Configure network red and attach it to Host with Static configuration: IP of 1.1.1.1, netmask of 255.255.255.0 and gateway of 1.1.1.254 using setupNetworks 3. Actual results: Host looses connectivity and never comes back Expected results: Host is not supposed to loose connectivity Additional info: After configuring IP rules on the Host everything worked as supposed to.
Created attachment 779379 [details] supervdsm log
A vdsm bug should never be filed without stating the relevant vdsm version. I believe that this is a dup of Bug 984028. Please reopen if it reproduces with vdsm that includes commit 8f4a060cc24901bb64490d8dd359799b1502bf60 Author: Assaf Muller <amuller> Date: Thu Aug 1 15:10:05 2013 +0300 Management network is now kept in main routing table *** This bug has been marked as a duplicate of bug 984028 ***