Bug 1487759

Summary: [OSP12] tripleo-ansible-inventory is too slow: it takes more than 2 minutes to generate an inventory containing 1 undercloud + 1 controller + 1 compute
Product: Red Hat OpenStack Reporter: Marius Cornea <mcornea>
Component: openstack-tripleo-validationsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED ERRATA QA Contact: nlevinki <nlevinki>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 12.0 (Pike)CC: akaris, akrivoka, aschultz, beth.white, dbecker, jjoyce, jschluet, mburns, morazi, rhel-osp-director-maint, slinaber, tvignaud
Target Milestone: betaKeywords: Triaged
Target Release: 12.0 (Pike)   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: openstack-tripleo-validations-7.4.2-0.20171016115241.c2c9bf2.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-13 22:02:49 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:
Bug Depends On:    
Bug Blocks: 1513593    

Description Marius Cornea 2017-09-01 20:48:59 UTC
Description of problem:
tripleo-ansible-inventory takes more than 2 minutes to generate an inventory containing 1 undercloud + 1 controller + 1 compute.

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

How reproducible:

Steps to Reproduce:
1. Run tripleo-ansible-inventory --list

Actual results:
It takes almost 2 minutes to display the inventory for a minimal deployment.

Expected results:
It should be a matter of seconds to generate the inventory.

Additional info:

In upgrades we use use the inventory for upgrading non controller nodes and this step adds a pretty high delay per node upgrade.

Comment 3 Ana Krivokapic 2017-11-06 15:13:51 UTC
It now takes from 1s to 6s depending on the number of nodes in the setup.

Comment 5 Ana Krivokapic 2017-11-21 09:31:56 UTC
*** Bug 1450475 has been marked as a duplicate of this bug. ***

Comment 8 errata-xmlrpc 2017-12-13 22:02:49 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.