Bug 1102548 - [RFE] Neutron Integration: Ability to update vNIC profile from external provider network to engine-based network
Summary: [RFE] Neutron Integration: Ability to update vNIC profile from external provi...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RFEs
Version: 3.4.0
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
: ---
Assignee: Rob Young
QA Contact: Meni Yakove
URL:
Whiteboard:
Depends On:
Blocks: 1063716
TreeView+ depends on / blocked
 
Reported: 2014-05-29 07:47 UTC by GenadiC
Modified: 2019-04-24 14:41 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-06-06 07:29:47 UTC
oVirt Team: Network
Embargoed:
ylavi: ovirt-future?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)
engine log (1.99 MB, text/x-log)
2014-05-29 07:47 UTC, GenadiC
no flags Details

Description GenadiC 2014-05-29 07:47:52 UTC
Created attachment 900262 [details]
engine log

Description of problem:
Error while executing action Edit VM Interface properties: Failed to communicate with the external provider is received when trying to update the neutron network on VM with rhevm network and the connection to the Neutron Server is lost

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Import network from Neutron Server
2. Attach that network to running VM NIC
3. Disconnect Neutron Server
4. Try to edit the NIC on VM with another rhevm network


Actual results:
NIc with External provider network is not updated with rhevm network

Expected results:
It should be possible to update a VNIC with Neutron network on VM with rhevm network


Additional info:

Comment 2 Yaniv Lavi 2018-06-06 07:29:47 UTC
Closing old RFEs, please reopen if still needed.
Patches are always welcomed.


Note You need to log in before you can comment on or make changes to this bug.