Bug 1483994 - Binding is not failing when ODL L2 is down
Summary: Binding is not failing when ODL L2 is down
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-networking-odl
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
Target Milestone: beta
: 12.0 (Pike)
Assignee: Mike Kolesnik
QA Contact: Itzik Brown
Depends On:
TreeView+ depends on / blocked
Reported: 2017-08-22 12:40 UTC by Itzik Brown
Modified: 2018-10-18 07:24 UTC (History)
1 user (show)

Fixed In Version: python-networking-odl-11.0.1-0.20170926211325.6ceec59.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-12-13 21:53:35 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Launchpad 1712334 0 None None None 2017-08-22 12:40:39 UTC
OpenDaylight gerrit 499200 0 None None None 2017-10-18 07:16:28 UTC
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

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):

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.


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