Bug 1636070

Summary: Build of instance aborted - Failed to allocate the network
Product: Red Hat OpenStack Reporter: Noam Manos <nmanos>
Component: openstack-neutronAssignee: Assaf Muller <amuller>
Status: CLOSED DUPLICATE QA Contact: Roee Agiman <ragiman>
Severity: high Docs Contact:
Priority: unspecified    
Version: 14.0 (Rocky)CC: amuller, chrisw, mkolesni, nmanos, nyechiel, wznoinsk
Target Milestone: ---   
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-10-28 14:43:25 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 aborted - Failed to allocate the network none

Description Noam Manos 2018-10-04 12:10:46 UTC 
Created attachment 1490487 [details]
Build of instance aborted - Failed to allocate the network

Description of problem:
Build of instance aborted: Failed to allocate the network(s), not rescheduling
Nova returned NotFound for event: 'network-vif-deleted'

Version-Release number of selected component (if applicable):
OSP14 2018-09-27.3


How reproducible:
Sometimes

Steps to Reproduce:
1. Deploy OSP14 + ODL
2. Spawn a VM

Please see attached console output.


Actual results:
Build of instance aborted: Failed to allocate the network(s), not rescheduling

neutron/server.log shows:
Nova returned NotFound for event: 'network-vif-deleted'

Expected results:
VM should be up and running.

Additional info:
Might be the same problem as in Bug 1636034 (Virtual Interface creation failed).
Comment 1 Noam Manos 2018-10-04 12:53:49 UTC 
SOS reports:
http://rhos-release.virt.bos.redhat.com/log/bz1636070/
Comment 2 Mike Kolesnik 2018-10-17 11:27:36 UTC 
Unfortunately there aren't any neutron/nova logs in the sosreports that you sent, please attach the logs so we can analyze the problem.
Comment 3 Waldemar Znoinski 2018-10-18 20:39:01 UTC 
@Noam it looks like it's very similar (or actully same) problem as https://bugzilla.redhat.com/show_bug.cgi?id=1636034 and that was is a dupe of https://bugzilla.redhat.com/show_bug.cgi?id=1631335

if ^ assumption is correct you should not see the issue from this very bz once you use puddle=2018-10-17.2 or newer
Comment 4 Noam Manos 2018-10-28 14:43:25 UTC 
(In reply to Waldemar Znoinski from comment #3)
> @Noam it looks like it's very similar (or actully same) problem as
> https://bugzilla.redhat.com/show_bug.cgi?id=1636034 and that was is a dupe
> of https://bugzilla.redhat.com/show_bug.cgi?id=1631335
> 
> if ^ assumption is correct you should not see the issue from this very bz
> once you use puddle=2018-10-17.2 or newer

Indeed, using puddle 2018-10-17.2 has solved the issue:
https://rhos-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DFG/view/opendaylight/view/odl-netvirt/job/DFG-opendaylight-odl-netvirt-14_director-rhel-virthost-3cont_2comp-ipv4-vxlan-ha-tempest/146
Comment 5 Noam Manos 2018-10-31 10:31:31 UTC 

*** This bug has been marked as a duplicate of bug 1631335 ***