Bug 1794900

Summary: [ceph-ansible] : rolling_update of containerized cluster failed searching inappropriate container name while trying to get keyrings from monitor
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Vasishta <vashastr>
Component: Ceph-AnsibleAssignee: Guillaume Abrioux <gabrioux>
Status: CLOSED ERRATA QA Contact: Vasishta <vashastr>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 4.0CC: aschoen, ceph-eng-bugs, ceph-qe-bugs, dsavinea, gmeno, nthomas, tserlin, ykaul
Target Milestone: rcKeywords: Regression
Target Release: 4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-ansible-4.0.13-1.el8cp, ceph-ansible-4.0.13-1.el7cp Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-31 12:48: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:
Bug Depends On:    
Bug Blocks: 1792122    

Description Vasishta 2020-01-25 08:10:42 UTC
Description of problem:
rolling update is failing at task ceph-osd : get keys from monitors trying to get keys

Version-Release number of selected component (if applicable):
$ rpm -qa|grep ceph-ansible
ceph-ansible-4.0.12-1.el7cp.noarch


How reproducible:
Always (1/1)

Steps to Reproduce:
1. Configure 3.x cluster
2. Run rolling update to upgrade cluster to 4.x


Actual results:
stderr: 'Error response from daemon: No such container: ceph-mon-magna034'

Expected results:
rolling update should not fail

Additional info:

Comment 9 Vasishta 2020-01-28 05:12:33 UTC
Working fine with ceph-ansible-4.0.13-1
Moving to verified state

Comment 11 errata-xmlrpc 2020-01-31 12:48:52 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-2020:0312