Bug 1528432

Summary: ceph-ansible does not properly check for running containers
Product: Red Hat Ceph Storage Reporter: Ken Dreyer (Red Hat) <kdreyer>
Component: Ceph-AnsibleAssignee: Guillaume Abrioux <gabrioux>
Status: CLOSED ERRATA QA Contact: subhash <vpoliset>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.0CC: adeza, aschoen, ceph-eng-bugs, ceph-qe-bugs, dmesser, edonnell, gabrioux, gmeno, hnallurv, kdreyer, nthomas, rperiyas, sankarshan, shan, tserlin, vashastr
Target Milestone: z1   
Target Release: 3.0   
Hardware: All   
OS: All   
Fixed In Version: RHEL: ceph-ansible-3.0.22-1.el7cp Ubuntu: ceph-ansible_3.0.22-2redhat1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1510555 Environment:
Last Closed: 2018-03-08 15:51:04 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:
Bug Depends On:    
Bug Blocks: 1494421, 1510555    

Comment 3 Vasishta 2018-01-25 09:42:31 UTC
Hi Ken, Hi Sebastien,

I just wanted to confirm the steps to verify this BZ.

As per my understanding, 

1) Make sure that on all probable nodes of a cluster docker is not running and only packages like docker-common is installed (Which provides CLI)

2) configure ceph-ansible to initialize containerized cluster, run playbook and and make sure that cluster gets deployed without trying to restart mgrs.

Can anyone please confirm these steps ?


Comment 5 Guillaume Abrioux 2018-01-26 09:45:32 UTC
Hi Vasishta,

What you described in c3 is correct.

Let me know if you need any support.


Comment 6 Ramakrishnan Periyasamy 2018-02-07 07:20:42 UTC
Hi Ken,

Can you please move this bug to ON_QA, so that QE can start verifying the bug.


Comment 8 subhash 2018-02-07 17:35:22 UTC
Following the steps from C31 of clone BZ 1510555 to verify, the playbook ran with no issues and cluster gets deployed without trying to restart mgrs. Moving to verfied state

Comment 11 errata-xmlrpc 2018-03-08 15:51:04 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.