Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1624875

Summary: OSP13 with ODL - Build of instance failed: Binding failed for port
Product: Red Hat OpenStack Reporter: Noam Manos <nmanos>
Component: python-networking-odlAssignee: Mike Kolesnik <mkolesni>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Noam Manos <nmanos>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 13.0 (Queens)CC: nmanos, tfreger
Target Milestone: z4   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-04 14:22:24 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:
Attachments:
Description Flags
Build of instance failed: Binding failed for port.
none
controller-0 container logs none

Description Noam Manos 2018-09-03 13:20:58 UTC 
Created attachment 1480554 [details]
Build of instance failed: Binding failed for port.

Description of problem:

On OSP13 with ODL, trying to spawn a vm failed on:

Build of instance [uuid] was re-scheduled: Binding failed for port [uuid], please check neutron logs for more information.\n']: OSError: [Errno 2] No such file or directory: '/var/log/nova/nova-conductor.log'

Version-Release number of selected component (if applicable):
13.0-RHEL-7/2018-08-22.2

How reproducible:
Sometimes.

Steps to Reproduce:
1. Install OSP13 (GA) + ODL.
2. Upgrade to latest Z build.
3. Create a VM on the external flat network.

You can use this script for step 3:
https://code.engineering.redhat.com/gerrit/#/c/145740/2/Scripts/create_multi_topology.sh

For example:
./create_multi_topology.sh -t mvi -i cirros35 -n 1 -v 1 -e flat -c YES

Actual results:
(overcloud) [stack@undercloud-0 ~]$ openstack server list --all
+--------------------------------------+-------------------+--------+----------+
| ID                                   | Name              | Status | Networks | Image    | Flavor        |
+--------------------------------------+-------------------+--------+----------+
| 979c3254-fc83-449d-be01-dfe485ea5dbb | cirros35_vm1_net1 | ERROR  |          | cirros35 | cirros_flavor |
+--------------------------------------+-------------------+--------+----------+


Expected results:
VM should be ACTIVE.

Additional info:
See attachment for full consle output and log traces.
Comment 1 Noam Manos 2018-09-03 14:04:55 UTC 
Created attachment 1480571 [details]
controller-0 container logs
Comment 2 Mike Kolesnik 2018-09-04 07:59:55 UTC 
Was the deployment successful?

I see multiple problems here..

First, the error "OSError: [Errno 2] No such file or directory: '/var/log/nova/nova-conductor.log'" has nothing to do with Neutron or ODL and I'm not sure if it's related or just a red herring.

Second, the neutron log shows tons of these errors:
2018-09-03 14:52:52.669 1 WARNING networking_odl.common.odl_features [req-05834d0d-72eb-453a-896e-0f3ce3689b1e - - - - -] error fetching features: 503
2018-09-03 14:52:52.670 1 WARNING networking_odl.common.odl_features [req-05834d0d-72eb-453a-896e-0f3ce3689b1e - - - - -] Failed to retrieve ODL features, attempt 87338

Usually code 503 comes from load balancer servers though I'm not sure if in this case it came directly from the ODL or from HAProxy.

Third, both logs for karaf and the compute node are missing so it's impossible to further study the cause of the failure.

Please supply the missing information.
Comment 3 Mike Kolesnik 2018-09-04 14:22:24 UTC 
After talking with Noam it seems there's not enough info to investigate the bug properly at this point since the problem seems to have been in the environment not related to ODL.

Should the bug be reproduced we will reopen it.