Bug 1383004
| Summary: | quick install OCP3.3 failed for 'NoneType' object has no attribute 'strategy' | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | liujia <jiajliu> |
| Component: | Installer | Assignee: | Tim Bielawa <tbielawa> |
| Status: | CLOSED ERRATA | QA Contact: | Johnny Liu <jialiu> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.3.1 | CC: | aos-bugs, jokerman, mmccomas, xtian |
| Target Milestone: | --- | ||
| Target Release: | 3.3.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: An AOI callback plugin method was not setting a variable to update the current play.
Consequence: When certain callback methods are called the required play object is not found. This causes the "'NoneType' object has no attribute 'strategy'" error.
Fix: Assign the play object in the play start callback method.
Result: Ansible can call all callback methods that require the playbook object. The 'no attribute' error is not raised.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-10-27 16:14:10 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
liujia
2016-10-09 03:01:59 UTC
With latest errata puddle(10-18.2), the problem is not existed. atomic-openshift-utils-3.3.37-1.git.0.10ff25b.el7.noarch @Jason If the bug is fixed, could u update the bug's status? Version: atomic-openshift-utils-3.3.38-1.git.0.2637ed5.el7.noarch Steps: trigger an installation against rhel env with qiick installer # atomic-openshift-installer install Result: It can install successfully. 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-2016:2122 |