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

Bug 1281318

Summary: gap between scheduler selection and claim causes spurious failures when the instance is the last one to fit
Product: Red Hat OpenStack Reporter: Jaison Raju <jraju>
Component: openstack-ironicAssignee: Lucas Alvares Gomes <lmartins>
Status: CLOSED DUPLICATE QA Contact: Toure Dunnon <tdunnon>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.0 (Kilo)CC: mburns, rhel-osp-director-maint, yeylon
Target Milestone: ---   
Target Release: 8.0 (Liberty)   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-12 13:40:13 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: 1339506    

Description Jaison Raju 2015-11-12 09:54:44 UTC
Description of problem:
There is a race between the scheduler in select_destinations, which selects a set of hosts, and the nova compute manager, which claims resources on those hosts when building the instance. The race is particularly noticable with Ironic, where every request will consume a full host, but can turn up on libvirt etc too. Multiple schedulers will likely exacerbate this too unless they are in a version of python with randomised dictionary ordering, in which case they will make it better .

Version-Release number of selected component (if applicable):
OSP7

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
https://bugs.launchpad.net/nova/+bug/1341420
https://review.openstack.org/#/c/226235/

Comment 3 Mike Burns 2015-11-12 13:02:43 UTC
How is this different from bug 1257950?  It looks like a duplicate to me.

Comment 4 Mike Burns 2015-11-12 13:40:13 UTC

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