Bug 1100852
Summary: | [RFE] [RHEVM] [neutron integration] engine should monitor neutron-openvswitch-agent | ||
---|---|---|---|
Product: | [oVirt] ovirt-host-deploy | Reporter: | Martin Pavlik <mpavlik> |
Component: | Plugins.OpenStack | Assignee: | Yaniv Lavi <ylavi> |
Status: | CLOSED WONTFIX | QA Contact: | Shai Revivo <srevivo> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | --- | CC: | bazulay, bugs, danken, dougsland, gklein, iheim, nyechiel, rbalakri, Rhev-m-bugs, sbonazzo, srevivo, ylavi |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | Flags: | ylavi:
ovirt-future?
ylavi: planning_ack- mpavlik: devel_ack? rule-engine: testing_ack? |
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-07-20 10:02:21 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: |
Description
Martin Pavlik
2014-05-23 15:10:33 UTC
I am unsure I understand, moti, I am sure you will. I also do not like we are working in parallel on upstream bugs on downstream. downstream bugs should be specific to downstream or customers. As we would like to focus on Open vSwitch and remove the Linux bridge plugin, can you please retest this with Open vSwitch and change this RFE for the openvswitch-agent? Thanks, Nir neutron-openvswitch-agent is the same case [root@dell-r210ii-05 ~]# service neutron-openvswitch-agent status neutron-openvswitch-agent (pid 14496) is running... [root@dell-r210ii-05 ~]# kill -9 14496 [root@dell-r210ii-05 ~]# service neutron-openvswitch-agent status neutron-openvswitch-agent dead but pid file exists [root@dell-r210ii-05 ~]# service neutron-openvswitch-agent status neutron-openvswitch-agent dead but pid file exists (In reply to Martin Pavlik from comment #3) > neutron-openvswitch-agent is the same case > > [root@dell-r210ii-05 ~]# service neutron-openvswitch-agent status > neutron-openvswitch-agent (pid 14496) is running... > [root@dell-r210ii-05 ~]# kill -9 14496 > [root@dell-r210ii-05 ~]# service neutron-openvswitch-agent status > neutron-openvswitch-agent dead but pid file exists > [root@dell-r210ii-05 ~]# service neutron-openvswitch-agent status > neutron-openvswitch-agent dead but pid file exists Thanks Martin I believe that we should probably have a vdsm caps (or better, stats) hook that reports about the agents that are running in the Host. Then, the engine code that handles vdsStats can generate the appropriate event (probably refuse to schedule a VM with the external provider network to that faulty Host too). Dan, who's going to own this on network team? It makes sense to keep this on ydary until it receives a planning ack and in my opinion, tightening the neutron integration should not be high on our agenda right now. Planning has indicated this request is declined. You may appeal this decision by reopening this request. |