Bug 1383004 – quick install OCP3.3 failed for 'NoneType' object has no attribute 'strategy'

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1383004 - quick install OCP3.3 failed for 'NoneType' object has no attribute 'strategy'

Summary:	quick install OCP3.3 failed for 'NoneType' object has no attribute 'strategy'

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Installer (Show other bugs)
Sub Component:
Version:	3.3.1
Hardware:	Unspecified Unspecified

Priority	high Severity medium
Target Milestone:	---
Target Release:	3.3.1
Assigned To:	Tim Bielawa
QA Contact:	Johnny Liu
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2016-10-08 23:01 EDT by liujia
Modified:	2016-10-27 12:14 EDT (History)
CC List:	4 users (show)

See Also:
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 12:14:10 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2016:2122	normal	SHIPPED_LIVE	OpenShift Container Platform atomic-openshift-utils bug fix update	2016-10-27 16:11:30 EDT

Groups: None (edit)

Description liujia 2016-10-08 23:01:59 EDT

Description of problem:
Trigger an installation with quick installer,when it came to the playbook-Play 7/29 (Determine openshift_version to configure on first master), an error occured as folllows:
[WARNING]: Failure using method (v2_runner_on_failed) in callback plugin (<ansible.plugins.callback.openshift_quick_installer.CallbackModule object at 0x220e290>):
'NoneType' object has no attribute 'strategy'


Version-Release number of selected component (if applicable):
atomic-openshift-utils-3.3.30-1.git.0.b260e04.el7.noarch.rpm
openshift-ansible-playbooks-3.3.30-1.git.0.b260e04.el7.noarch.rpm
openshift-ansible-callback-plugins-3.3.30-1.git.0.b260e04.el7.noarch

How reproducible:
always

Steps to Reproduce:
1.yum install atomic-openshift-utils and then install rpm openshift-ansible-callback-plugins-3.3.30-1.git.0.b260e04.el7.noarch.rpm(work around bug 1382885)
2.run "atomic-openshift-installer install"

Actual results:
install failed with error:
Play 7/29 (Determine openshift_version to configure on first master)
............................................................ [WARNING]: Failure using method (v2_runner_on_failed) in callback plugin (<ansible.plugins.callback.openshift_quick_installer.CallbackModule object at 0x220e290>):
'NoneType' object has no attribute 'strategy'


Expected results:
quick install successfully.

Additional info:

Comment 1 liujia 2016-10-19 01:02:04 EDT

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?

Comment 3 liujia 2016-10-20 05:03:17 EDT

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.

Comment 5 errata-xmlrpc 2016-10-27 12:14:10 EDT

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

Note You need to log in before you can comment on or make changes to this bug.