Bug 989237
| Summary: | [VDSM]Adding new network to Host with gateway configuration causes disconnection to that Host | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | GenadiC <gcheresh> | ||||||
| Component: | vdsm | Assignee: | Assaf Muller <amuller> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | GenadiC <gcheresh> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 3.3.0 | CC: | abaron, bazulay, danken, hateya, iheim, lpeer, myakove, yeylon | ||||||
| Target Milestone: | --- | Keywords: | Triaged | ||||||
| Target Release: | 3.3.0 | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | network | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2013-08-22 22:27:20 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
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 *** |
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.