Bug 1680534

Summary: fail to deploy with ceph in containers with dmcrypt, ansible timeout
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Gal Amado <gamado>
Component: Ceph-AnsibleAssignee: Guillaume Abrioux <gabrioux>
Status: CLOSED ERRATA QA Contact: Persona non grata <nobody+410372>
Severity: high Docs Contact:
Priority: high    
Version: 3.2CC: aschoen, ceph-eng-bugs, gabrioux, gamado, gfidente, gmeno, nthomas, sankarshan, tchandra, tserlin
Target Milestone: z1   
Target Release: 3.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: ceph-ansible-3.2.8-1.el7cp Ubuntu: ceph-ansible_3.2.8-2redhat1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-03-07 15:51:42 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:
Bug Depends On:    
Bug Blocks: 1578730    
Attachments:
Description Flags
ceph_ansible_command.log none

Description Gal Amado 2019-02-25 09:57:38 UTC
Created attachment 1538386 [details]
ceph_ansible_command.log

Description of problem:
Versions :
puddle: 14   -p 2019-02-22.2
ceph-ansible-3.2.7-1.el7cp.noarch
ansible-2.6.11-1.el7ae.noarch

When trying to deploy with ceph, failed on Ansible timeout:

TASK [run ceph-ansible (immediate log at /var/lib/mistral/overcloud/ceph-ansible/ceph_ansible_command.log)] ***
Sunday 24 February 2019  12:08:32 -0500 (0:00:00.088)       0:21:43.063 ******* 

Ansible timed out at 4445 seconds.


/var/lib/mistral/overcloud/ceph-ansible/ceph_ansible_command.log is attached.

Comment 3 Sébastien Han 2019-02-26 09:23:50 UTC
This timeout looks familiar and was originally fixed in https://github.com/ceph/ceph-ansible/releases/tag/v3.2.6 as part of https://github.com/ceph/ceph-ansible/commit/303cc857540e62b09f14703dfe8f50e9e1666888.
As Giulio suggested, I'd be nice to have the env.

Comment 9 errata-xmlrpc 2019-03-07 15:51:42 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/RHBA-2019:0475