python-eventlet package doesn't contain mos-specific patch

Bug #1469099 reported by Sergey Kolekonov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Fix Released
Critical
Mikhail Ivanov

Bug Description

python-eventlet package from MOS 7.0 mirror doesn't contain important patch
0001-MIRA-Don-t-treat-ENOTCONN-as-if-it-would-block.patch

It causes all *-api services to consume 100% of CPU

Changed in mos:
status: New → Confirmed
Mikhail Ivanov (mivanov)
Changed in mos:
assignee: MOS Packaging Team (mos-packaging) → Mikhail Ivanov (mivanov)
Mikhail Ivanov (mivanov)
Changed in mos:
status: Confirmed → In Progress
Revision history for this message
Fuel Devops McRobotson (fuel-devops-robot) wrote : Fix merged to packages/trusty/python-eventlet (7.0)

Reviewed: https://review.fuel-infra.org/8508
Submitter: Ivan Udovichenko <email address hidden>
Branch: 7.0

Commit: 4c5c4a61cbc1fb3192e23f0b51def0e422d237d5
Author: Mikhail Ivanov <email address hidden>
Date: Fri Jun 26 12:01:27 2015

Update package python-eventlet for MOS 7.0

Update package for MOS 7.0
Update subrevision, because wrong package in our repo has similar version
Sources from https://pypi.python.org/pypi/eventlet/0.16.1
Closes-Bug:#1469099

Change-Id: I71d6c76a9e471c770c731da920aeaef8afe0030b

Mikhail Ivanov (mivanov)
Changed in mos:
status: In Progress → Fix Committed
Revision history for this message
Thomas Goirand (thomas-goirand) wrote :

Hi,

It looks like to me that we should use the latest eventlet version, instead of using this patch. Indeed, version 0.17.4 has the fix included (though it's in a different file: eventlet/greenio/base.py instead of eventlet/greenio.py). I've been using that one version and ran tempest tests against OpenStack Kilo, and it just worked (tm). So let's upgrade...

Revision history for this message
Timur Nurlygayanov (tnurlygayanov) wrote :

Thomas, could you, please, create new bug where we will track the update for this package?
Looks like this issue were fixed for MOS 7.0, because API workers on my host takes ~20% of CPU (I have only one CPU on controller VM) status changed to Fix Released.

Changed in mos:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.