Bug 1761457

Summary: ceph-mds get keys from monitor - gets them from non-existent mds
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Giulio Fidente <gfidente>
Component: Ceph-AnsibleAssignee: Guillaume Abrioux <gabrioux>
Status: CLOSED ERRATA QA Contact: Yogev Rabl <yrabl>
Severity: medium Docs Contact:
Priority: high    
Version: 4.0CC: aschoen, ceph-eng-bugs, ceph-qe-bugs, dsavinea, gmeno, hyelloji, nthomas, tchandra, tserlin, vashastr, ykaul
Target Milestone: rc   
Target Release: 4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-ansible-4.0.2-1.el8cp Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-31 12:47:33 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: 1594251    

Comment 1 RHEL Program Management 2019-10-14 12:57:55 UTC
Please specify the severity of this bug. Severity is defined here:
https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity.

Comment 6 Hemanth Kumar 2020-01-07 05:24:47 UTC
Hi Giulio,

The logs mentioned in the Description is not accessible and I would like to know exactly what the issue is and how do we verify the fix ?

Thanks,
Hemanth

Comment 7 Giulio Fidente 2020-01-08 07:43:03 UTC
(In reply to Hemanth Kumar from comment #6)
> Hi Giulio,
> 
> The logs mentioned in the Description is not accessible and I would like to
> know exactly what the issue is and how do we verify the fix ?

logs might have expired, I will attach them to bug next time

the issue was only seen when mds and mon were colocated; I think that in such a scenario the container_exec_cmd fact, which is set per-node, was mistakenly updated to run within an mds container but later on the "get keys" task expected instead to run within a mon container

Comment 11 errata-xmlrpc 2020-01-31 12:47:33 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