Bug 1356567

Summary:	Changing port admin_state_up is not enforced when using Opendaylight Mechanism driver
Product:	Red Hat OpenStack	Reporter:	Itzik Brown <itbrown>
Component:	opendaylight	Assignee:	Josh Hershberg <jhershbe>
Status:	CLOSED UPSTREAM	QA Contact:	Itzik Brown <itbrown>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	lpeer, mkolesni, nyechiel
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-15 09:36:05 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1337087

Description Itzik Brown 2016-07-14 11:57:31 UTC

Description of problem:
When using Opendaylight Mechanism driver and setting the port's admin_state_up attribute to False there is still connectivity to the instance.

Version-Release number of selected component (if applicable):
python-networking-odl-1.0.1-1.el7ost.noarch
opendaylight-1.0.0-4.el7ost.noarch
openvswitch-2.4.0-2.el7_2.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Launch an instance and associate a floating IP to the instance 
2. Check connectivity 
3. Identify the port of the instance using neutron port-list --device_id=<instance id>
4. Set the port_admin_state_up to False by running 
   # neutron port-update <port id> --admin_state_up=False 
5. Verify there is still connectivity to the instance

Actual results:


Expected results:


Additional info:

Comment 2 Josh Hershberg 2016-11-01 12:55:58 UTC

Upstream: https://bugs.opendaylight.org/show_bug.cgi?id=6718

Comment 3 Nir Yechiel 2017-01-15 09:36:05 UTC

I suggest to close this BZ and just leave it upstream at this point. If we will have a customer complaining about this we will reopen and prioritize.