Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1543741

Summary: [ceph-ansible] mgr daemons are not restarted if a new image is being pulled
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: subhash <vpoliset>
Component: Ceph-AnsibleAssignee: Sébastien Han <shan>
Status: CLOSED DUPLICATE QA Contact: subhash <vpoliset>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.0CC: adeza, aschoen, ceph-eng-bugs, gfidente, gmeno, hnallurv, nthomas, sankarshan
Target Milestone: z1   
Target Release: 3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-09 09:37:52 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:
Attachments:
Description Flags
FIle contains all.yml,osds.yml,hosts,ansible-playbook log
none
FIle contains ansible-playbook log ,all.yml,osds.yml,hosts content none

Description subhash 2018-02-09 07:38:30 UTC 
Created attachment 1393556 [details]
FIle contains all.yml,osds.yml,hosts,ansible-playbook log

Description of problem:
site-docker.yml does not restart the ceph-mgr daemon if a new image is pulled,it points to old image

Version-Release number of selected component (if applicable):
ceph-ansible-3.0.23-1.el7cp.noarch.rpm

How reproducible:
always

Steps to Reproduce:
1.Initialize ceph Containerized cluster by ceph-ansible with old image
2.update the new docker image tag in all.yml
3.Run the ansible playbook site-docker.yml

Actual results:
ceph-mgr daemon might not be restarting

Expected results:
ceph-mgr daemon should be restarted and point to new docker image.

Additional info:
I hit this issue while verifying BZ 1526513 for 3.0z1
Comment 4 subhash 2018-02-09 07:45:43 UTC 
Comment on attachment 1393556 [details]
FIle contains all.yml,osds.yml,hosts,ansible-playbook log

By mistake uploaded 2.5 log,sry abt that
Comment 5 subhash 2018-02-09 07:47:57 UTC 
Created attachment 1393557 [details]
FIle contains ansible-playbook log ,all.yml,osds.yml,hosts content

Here is the correct log for 3.0-z1
Comment 7 Sébastien Han 2018-02-09 09:37:52 UTC 

*** This bug has been marked as a duplicate of bug 1526513 ***