Bug 1685583
| Summary: | [3.10] Slow Initialization During Upgrades | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Scott Dodson <sdodson> |
| Component: | Installer | Assignee: | Vadim Rutkovsky <vrutkovs> |
| Installer sub component: | openshift-ansible | QA Contact: | Weihua Meng <wmeng> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | high | ||
| Priority: | high | CC: | gpei, jialiu, mrobson, vrutkovs, wmeng |
| Version: | 3.10.0 | ||
| Target Milestone: | --- | ||
| Target Release: | 3.10.z | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: sanity checks were using inefficient code to validate hostvars
Consequence: sanity check time took several minutes on a large set of hosts
Fix: hostvars are stored in the class, so there are not being copied on every check
Result: sanity checks take less time to complete
|
Story Points: | --- |
| Clone Of: | 1682924 | Environment: | |
| Last Closed: | 2019-06-11 09:30:48 UTC | Type: | --- |
| 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: | 1682924 | ||
| Bug Blocks: | |||
|
Comment 1
Scott Dodson
2019-03-05 14:49:55 UTC
Fix is available in openshift-ansible-3.10.122-1 Fixed. openshift-ansible-3.10.127-1.git.0.131da09.el7 In my test, With 3.10.101, TASK [Run variable sanity checks] costs 1.88 seconds With 3.10.127, TASK [Run variable sanity checks] costs 0.35 second Kernel Version: 3.10.0-957.10.1.el7.x86_64 Operating System: Red Hat Enterprise Linux Server 7.6 (Maipo) 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-2019:0786 |