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

Bug 1794013

Summary:	Ansible consumes around 50 cores of CPU when running the update /etc/hosts task on a scale deployment
Product:	Red Hat OpenStack	Reporter:	Sai Sindhur Malleni <smalleni>
Component:	tripleo-ansible	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Sasha Smolyak <ssmolyak>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16.0 (Train)
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:	2020-01-22 14:54:39 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:

Description Sai Sindhur Malleni 2020-01-22 13:56:34 UTC

Description of problem:
When scaling from 200 nodes to 250 nodes in OSP 16, we see ansible-playbook process consume around 50 cores on the undercloud during the update /etc/hosts task which runs for around 22 minutes

Version-Release number of selected component (if applicable):
RHOS_TRUNK-16.0-RHEL-8-20200113.n.0

How reproducible:
100% at scale

Steps to Reproduce:
1. Run a scale out on a large deployment
2. Monitor CPU usage of ansible
3.

Actual results:
Ansible consumes around 50 cores on the undercloud

Expected results:
Consuming 50 cores isn't acceptable

Additional info:
https://snapshot.raintank.io/dashboard/snapshot/Xujs6L7FAsCM8Kpzc63khcOUi8RBRkbj?orgId=2

Comment 1 Sai Sindhur Malleni 2020-01-22 14:54:39 UTC


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