Bug 1939887

Summary: [ceph-ansible] : cephadm-adopt :conf file needs to be copied to alertmanager node inorder to adopt alertmanager
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: 5.0CC: aschoen, ceph-eng-bugs, gmeno, nthomas, vereddy, ykaul
Target Milestone: ---Keywords: UpgradeBlocker
Target Release: 5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-ansible-6.0.2-1.el8cp Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-08-30 08:29:07 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:

Description Vasishta 2021-03-17 09:36:08 UTC
Description of problem:
When cephadm-adopt playbook was tried on cluster with dedicated grafana node, plybook fails on grafana node while adopting alertmanager

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

How reproducible:
Tried once

Steps to Reproduce:
1. Configure 4.x cluster with dedicated grafana node
2. Upgrade to 5.x
3. Run cephadm-adopt.yml playbook

Actual results:
stderr: 'ERROR: could not detect legacy fsid; set fsid in ceph.conf'

Expected results:
Playbook should succeed 

Additional info:

Comment 6 Vasishta 2021-03-24 15:39:46 UTC
Working fine with ceph-ansible-6.0.2-1.el8cp
Moving to VERIFIED state.

Comment 8 errata-xmlrpc 2021-08-30 08:29:07 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 (Red Hat Ceph Storage 5.0 bug fix and enhancement), 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-2021:3294