Bug 1016457 - [oVirt][Neutron] Port deleted on VM stop, looses IP data
Summary: [oVirt][Neutron] Port deleted on VM stop, looses IP data
Keywords:
Status: CLOSED DUPLICATE of bug 1013491
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: 3.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.3.1
Assignee: Mike Kolesnik
QA Contact:
URL:
Whiteboard: network
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-08 08:27 UTC by Mike Kolesnik
Modified: 2013-10-09 05:37 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-10-09 05:37:24 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)

Description Mike Kolesnik 2013-10-08 08:27:24 UTC
Description of problem:
The port on the external network gets deleted when VM is stopped.
This causes the IP details (internal + floating IP, if associated) to be lost, and when VM will start again new IP will be assigned (not necessarily the one from before).


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


How reproducible:
Always


Steps to Reproduce:
1. Create VM with a vNIC attached to an external network provided by an 'OpenStack Network' provider
2. Run the VM
3. Stop the VM

Actual results:
The port is deleted from the external network


Expected results:
The port for the vNIC should remain on the external network


Additional info:
The new behavior is documented on the feature page:
http://www.ovirt.org/Features/Detailed_OSN_Integration#Integration_with_virtual_NIC_lifecycle

Extract:
"The port will be deleted in these cases:

    The virtual NIC is deleted from the VM.
    The virtual VNIC profile is changed, so that it is no longer connected to the external network.
    The VM is deleted.
    The data center containing the external networks is deleted forcefully.
    Snapshot operations (Preview, Undo) on the VM. "

Comment 1 Mike Kolesnik 2013-10-09 05:37:24 UTC

*** This bug has been marked as a duplicate of bug 1013491 ***


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