Bug 1583851

Summary:	Ansible Job Times out at 300 seconds causing Automate State Machine to Fail
Product:	Red Hat CloudForms Management Engine	Reporter:	Satoe Imaishi <simaishi>
Component:	Automate	Assignee:	Bill Wei <bilwei>
Status:	CLOSED ERRATA	QA Contact:	Dmitry Misharov <dmisharo>
Severity:	high	Docs Contact:
Priority:	high
Version:	5.9.0	CC:	cpelland, mkanoor, myoder, obarenbo, tfitzger
Target Milestone:	GA	Keywords:	ZStream
Target Release:	5.9.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	5.9.3.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1581465	Environment:
Last Closed:	2018-07-12 13:15:30 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	Ansible	Target Upstream Version:
Embargoed:
Bug Depends On:	1581465
Bug Blocks:

Comment 2 CFME Bot 2018-05-29 22:06:53 UTC

New commit detected on ManageIQ/manageiq/gaprindashvili:

https://github.com/ManageIQ/manageiq/commit/0da130d89ed6644a6feca4ce1d33c8cba0b15f5d
commit 0da130d89ed6644a6feca4ce1d33c8cba0b15f5d
Author:     Madhu Kanoor <mkanoor>
AuthorDate: Tue May 29 14:50:21 2018 -0400
Commit:     Madhu Kanoor <mkanoor>
CommitDate: Tue May 29 14:50:21 2018 -0400

    Merge pull request #17476 from bzwei/playbook_runner_ttl

    Honor user provided execution_ttl option
    (cherry picked from commit 75cbaf4e1a9b5cf7bd9519c0f69b80dfa90740cb)

    Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1583851

 app/models/manageiq/providers/embedded_ansible/automation_manager/playbook_runner.rb | 7 +
 spec/models/manageiq/providers/embedded_ansible/automation_manager/playbook_runner_spec.rb | 18 +
 2 files changed, 25 insertions(+)

Comment 3 Dmitry Misharov 2018-06-13 08:07:43 UTC

Fixed and verified in 5.9.3.1.20180606184006_8d120c0. A state machine with log running ansible playbook works doesn't fail.

Comment 6 errata-xmlrpc 2018-07-12 13:15:30 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.

https://access.redhat.com/errata/RHSA-2018:2184