Bug 1483994

Summary:	Binding is not failing when ODL L2 is down
Product:	Red Hat OpenStack	Reporter:	Itzik Brown <itbrown>
Component:	python-networking-odl	Assignee:	Mike Kolesnik <mkolesni>
Status:	CLOSED ERRATA	QA Contact:	Itzik Brown <itbrown>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	12.0 (Pike)	CC:	trozet
Target Milestone:	beta	Keywords:	Triaged
Target Release:	12.0 (Pike)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-networking-odl-11.0.1-0.20170926211325.6ceec59.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:	N/A
Last Closed:	2017-12-13 21:53:35 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:

Description Itzik Brown 2017-08-22 12:40:39 UTC

Description of problem:
When the ODL L2 agent is down and an instance is scheduled to run on the node with this agent the instance is in 'spawning' state for a long time until it fails.

The expected behavior is in the case the agent is down that the binding will fail and the instance will be rescheduled to run on a different compute node.

Version-Release number of selected component (if applicable):
python-networking-odl-11.0.0-0.20170804111351.a27bd55.el7ost.noarch
opendaylight-6.1.0-2.el7ost.noarch

How reproducible:


Steps to Reproduce:
1. Block the outgoing port 6640 on the Compute node
2. Wait for the agent to be down (openstack network agent list)
3. Launch an instance and verify it's scheduled to be on the above node
4. Verify that the instance is in 'spawning' state and not rescheduled to another node

Actual results:


Expected results:


Additional info:

Comment 2 Itzik Brown 2017-11-05 11:43:31 UTC

Checked with python-networking-odl-11.0.1-0.20170926211325.6ceec59.el7ost.noarch.

Blocked outgoing port 6640 on the compute node and waited for the agent status to be down.

Then tried to launch an instance on this node and it failed as expected:
{"message": "Binding failed for port c53a7d09-ef59-4298-8a73-b55f5bfa145d, please check neutron logs for more information.", "code": 500, "details": "  File \"/usr/lib/python2.7/site-packages/nova/compute/manager.py\", line 1829, in _do_build_and_run_instance

Comment 5 errata-xmlrpc 2017-12-13 21:53:35 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:3462