Bug 867478
Summary: | [RHEVM] [backend] [Host Networking] host does not go non-operationl if required VLAN goes down | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Martin Pavlik <mpavlik> | ||||
Component: | ovirt-engine | Assignee: | lpeer <lpeer> | ||||
Status: | CLOSED WONTFIX | QA Contact: | Martin Pavlik <mpavlik> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 3.1.0 | CC: | dyasny, gklein, iheim, lpeer, Rhev-m-bugs, sgrinber, yeylon, ykaul | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | All | ||||||
Whiteboard: | network | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2012-10-21 16:36:59 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: |
|
This is not a real life case, so I would prefer to refrain placing resources to support it. The interesting use case is if the Interfaces where the network is attached to is set is down due to loss of connectivity. In your case - if em2 is down, will it cause status to go into non-operational? (In reply to comment #1) > This is not a real life case, so I would prefer to refrain placing resources > to support it. > > The interesting use case is if the Interfaces where the network is attached > to is set is down due to loss of connectivity. > > In your case - if em2 is down, will it cause status to go into > non-operational? Yes, host will be set as non-oprerational Closing this, Not because it's not a bug, but since there is no trivial real life scenario I can think of that leads to this scenario. If anyone encounters this in non synthetic test please reopen. |
Created attachment 628881 [details] vdsm.log + engine.log Description of problem: host does not go non-operationl if required VLAN goes down Version-Release number of selected component (if applicable): Red Hat Enterprise Virtualization Manager Version: '3.1.0-20.el6ev' vdsm-4.9.6-37.0.el6_3.x86_64 How reproducible: 100% Steps to Reproduce: 1. create required network with VLAN tag (e.g. VLAN2222, with tag 2222) 2. ssh to the host and run ifdown VLAN2222 && ifdown em2.2222 Actual results: host stays operational despite required network is down Expected results: host should go non-operational Additional info: