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 1918424

Summary: [RFE] [ceph-ansible] cephadm-adopt - Playbook needs to be idempotent
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Vasishta <vashastr>
Component: Ceph-AnsibleAssignee: Dimitri Savineau <dsavinea>
Status: CLOSED ERRATA QA Contact: Vasishta <vashastr>
Severity: high Docs Contact: Ranjini M N <rmandyam>
Priority: unspecified    
Version: 5.0CC: asakthiv, aschoen, ceph-eng-bugs, dsavinea, gabrioux, gmeno, nthomas, rmandyam, tserlin, vereddy, ykaul
Target Milestone: ---Keywords: FutureFeature
Target Release: 5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-ansible-6.0.0-0.1.alpha7.el8cp Doc Type: Enhancement
Doc Text:
.The `cephadm-adopt.yml` playbook is idempotent With this release, the `cephadm-adopt.yml` playbook is idempotent, that is the playbook can be run multiple times. If the playbook fails for any reason in the first attempt, you can rerun the playbook and it works as expected. For more information, see the link:{install-guide}#upgrading-from-rhcs-4-to-rhcs-5-using-ceph-ansible_install[_Upgrading from {storage-product} 4 to {storage-product} 5 using `ceph-ansible`_] section in the _{storage-product} Installation Guide_.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2021-08-30 08:27:54 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: 1927685    
Bug Blocks: 1959686    

Description Vasishta 2021-01-20 17:03:29 UTC 
Description of problem:
cephadm-adopt had failed because of Bug 1917530
We tried again on the same cluster once we had the fix, to complete cephadm adoption
Playbook failed at task get current fsid saying that monitor container

It would be nice if we can fix this to support users for those who might have a unsuccessful initial run for any reason


Version-Release number of selected component (if applicable):
ceph-ansible-6.0.0-0.1.alpha6.el8cp.noarch

How reproducible:
Tried once

Steps to Reproduce:
1. Configure rhcs 4.x 
2. upgrade the cluster to 5.x and run cephadm-adopt playbook, induce playbook failure
3. Re-run cephadm-adopt playbook again

Actual results:
  stderr: 'Error: no container with name or ID ceph-mon-pluto002 found: no such container'


Expected results:
Playbook could be idempotent

Additional info:
Comment 6 Vasishta 2021-03-19 13:07:09 UTC 
Tried with 6.0.1-1.el8cp
Including task mentioned in description, all tasks did not fail when initiated second time after a failure almost end of the playbook.
Moving to Verified state.
Comment 10 errata-xmlrpc 2021-08-30 08:27:54 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