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

Bug 1792425

Summary:	Ansible consuming a lot of memory when running the update /etc/hosts task during config-download
Product:	Red Hat OpenStack	Reporter:	Sai Sindhur Malleni <smalleni>
Component:	tripleo-ansible	Assignee:	Luke Short <lshort>
Status:	CLOSED DUPLICATE	QA Contact:	Sasha Smolyak <ssmolyak>
Severity:	high	Docs Contact:
Priority:	high
Version:	16.0 (Train)	CC:	lshort
Target Milestone:	---	Keywords:	Triaged
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-28 17:14:54 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-17 16:14:08 UTC

Description of problem:

Profiling ansible memory consumption during config-download as documented in https://thesaitech.wordpress.com/2019/11/17/profiling-ansible-memory-usage-per-task/ we see that the update /etc/hosts task consumes a lot of memory. We should look at optimizing this.

https://gist.githubusercontent.com/smalleni/b14cac7674784fd3b84b42c99a7d5ee5/raw/3c785813e7dca988ac5c978fe3449dfb9c1ed32f/gistfile1.txt

tripleo-hosts-entries : Update /etc/hosts (0cc47afa-1a12-f1af-b1bb-00000002356e): 4058.31MB

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

How reproducible:
100%

Steps to Reproduce:
1. Deploy overcloud
2. Once the heat stack is created kill the deploy
3. Follow procedure in https://thesaitech.wordpress.com/2019/11/17/profiling-ansible-memory-usage-per-task/



Actual results:
/etc/hosts update consumes lot more memroy than other tasks

Expected results:
We should be able to optimize this

Additional info:

Comment 1 Sai Sindhur Malleni 2020-01-22 13:47:28 UTC

Another update, when scaling out to 250ish nodes from 200 nodes, we see ansible consume 50G+ of RSS memory.
https://snapshot.raintank.io/dashboard/snapshot/Xujs6L7FAsCM8Kpzc63khcOUi8RBRkbj?orgId=2

Comment 2 Luke Short 2020-01-28 17:14:54 UTC


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