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

Bug 1608584

Summary: Intermittent timeouts for sriov port creations
Product: Red Hat OpenStack Reporter: Matt Flusche <mflusche>
Component: openstack-neutronAssignee: Brian Haley <bhaley>
Status: CLOSED ERRATA QA Contact: Roee Agiman <ragiman>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 10.0 (Newton)CC: akaris, amuller, asoni, atelang, beagles, bhaley, cfields, chhudson, chrisw, jmelvin, jthomas, lhh, mflusche, nyechiel, ragiman, skaplons, srevivo, yrachman
Target Milestone: ---Keywords: Triaged, ZStream
Target Release: 10.0 (Newton)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: openstack-neutron-9.4.1-31.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-16 17:11:12 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: 1643761    

Description Matt Flusche 2018-07-25 21:23:35 UTC
Description of problem:

In this specific environment we are experiencing intermittent sriov port creation issues causing those instances to fail to launch.

Version-Release number of selected component (if applicable):
OSP 10
python-neutron-9.4.1-16.el7.noarch
openstack-neutron-sriov-nic-agent-9.4.1-16.el7.noarch

SR-IOV interface: 3b:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ [8086:1572] (rev 01)

How reproducible:
Intermittent in this environment


Steps to Reproduce:
1. Create sr-iov/direct port
2. Launch instance using direct port
3.

Additional info:

I'll follow up with additional detail and a link to the logs and sosreports.

Nova compute is failing with the following time out (after 300 seconds):

2018-07-24 10:13:58.285 4063 ERROR nova.compute.manager [req-55cb9666-dc1b-40c7-8c1b-016f70f20bb6 627bdd4c20d24969bea7854fd1a0686e 3d6afc405c204e6dac06fcd798710bea - - -] [instance: c8f468f2-3849-4202-aca3-8053a7390376] Build of instance c8f468f2-3849-4202-aca3-8053a7390376 aborted: Failed to allocate the network(s), not rescheduling.

Comment 50 errata-xmlrpc 2019-01-16 17:11:12 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/RHBA-2019:0080