Bug 1079921 - [Neutron integration] Removing security group from VNIC doesn't update the Neutron Server
Summary: [Neutron integration] Removing security group from VNIC doesn't update the Ne...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.4.0
Hardware: x86_64
OS: Linux
high
unspecified
Target Milestone: ---
: 3.5.0
Assignee: Moti Asayag
QA Contact: GenadiC
URL:
Whiteboard: network
Depends On:
Blocks: 1063716
TreeView+ depends on / blocked
 
Reported: 2014-03-24 10:05 UTC by GenadiC
Modified: 2016-02-10 19:56 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-26 08:23:34 UTC
oVirt Team: Network
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description GenadiC 2014-03-24 10:05:07 UTC
Description of problem:
No update message is sent to Neutron Server when you remove preconfigured security group for the VNIC, attached to running VM

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


How reproducible:
Always

Steps to Reproduce:
1. Run VM with VNIC profile of External network
2. Add security group to that VNIC profile and check it is updated on Neutron Server
3. Update VNIC profile by removing security group

Actual results:
Security group is not updated on the Neutron Server - it is still the removed one

Expected results:
Update should be sent to Neutron Server and it should be updated correctly

Additional info:

Comment 1 Lior Vernia 2014-06-23 09:26:40 UTC
Do you mean that updating the security groups on the vnic profile triggered an update of the security profiles for the ports on neutron server for all of the vms which use that profile ?

Comment 2 GenadiC 2014-06-26 08:23:34 UTC
It's not a bug as update of the Network on Neutron is done today only when you unplug/plug the relevant vNIC with that network.
Will open RFE to be able to update the Neutron Network without unplug/plug


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