Bug 1426788

Summary:	wrong CPU count in docker after hot plugging
Product:	Red Hat Enterprise Linux 7	Reporter:	Donald Berry <dberry>
Component:	docker	Assignee:	Antonio Murdaca <amurdaca>
Status:	CLOSED ERRATA	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	7.3	CC:	amurdaca, dornelas, dwalsh, jamills, lsm5, lsu
Target Milestone:	rc	Keywords:	Extras
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	When hot plugging a CPU into the system the docker daemon does not increment its count of CPUs. This package includes a back port of a fix that went into the upstream repos.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-26 14:37:52 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:	1186913, 1422984

Description Donald Berry 2017-02-24 20:59:09 UTC

Description of problem:
customer is using OCP 3.3/docker 1.10
customer added 2 vCPUs via VMware/ESX
OCP reports the additional CPUs but docker does not

Version-Release number of selected component (if applicable):
docker-1.10.3-57.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. add vCPUs with VMware/ESX

Additional info:
upstream patch in 1.13
https://github.com/docker/docker/issues/23768

Comment 2 Daniel Walsh 2017-02-24 21:28:05 UTC

Looks like this is fixed in docker-1.13.1.

Comment 3 Antonio Murdaca 2017-02-26 11:27:48 UTC

Backported https://github.com/projectatomic/docker/commit/9a509f913f752f75308a9eca40e55efbe5612fd3 to docker-1.12.6

Tested manually.

Comment 6 errata-xmlrpc 2017-05-26 14:37:52 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-2017:1325