Bug 1510492
| Summary: | OVN network status is constantly 'inactive' in CFME network provider UI | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-provider-ovn | Reporter: | Mor <mkalfon> | ||||
| Component: | provider | Assignee: | Marcin Mirecki <mmirecki> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Mor <mkalfon> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 1.0.4 | CC: | alkaplan, bugs, danken, gblomqui, hkataria, jfrey, jhardy, mburman, mmirecki, mpovolny, myakove, obarenbo, ylavi | ||||
| Target Milestone: | ovirt-4.2.0 | Flags: | rule-engine:
ovirt-4.2+
|
||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-12-20 10:49:52 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | Bug | |||||
| oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | RHEVM | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
It is an ovirt-provider-ovn bug. It has to report status. According to neuron v2 api (https://developer.openstack.org/api-ref/network/v2/index.html) the values are ACTIVE, DOWN, BUILD or ERROR. I am not sure the merged solution is nice enough because of """ The value is always set to 'ACTIVE' as there is no corresponding OVN property that could be used to model it. """ I suspected that Neutron's "active" attribute can be merged to weather the port is bound to a host, or whether it has an OpenFlow associated with it. Am I wrong? Marcin tells me that OVN networks are immediately active after being defined. Verified on: CFME 5.9.0.8.20171109215303_ed87902 ovirt-provider-ovn ovirt-provider-ovn-1.2-0.20171114103032.git5f4d32a.el7.centos.noarch 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. |
Created attachment 1349000 [details] evm log and screenshot Description of problem: OVN network gets reported as status 'inactive' when its active and being used in by oVirt VM. Version-Release number of selected component (if applicable): CFME 5.9.0.5.20171102023815_209f732 How reproducible: 100% Steps to Reproduce: 1. Create OVN network on oVirt UI. 2. Attach OVN network to VM vNIC. 3. Run the VM. 2. Sync the changes on the CFME oVirt provider. Actual results: Status appear as 'inactive' Expected results: Should be 'active' Additional info: