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 1805041

Summary: [ceph-ansible] add-osd.yml fails if fetch directory has been removed
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: James Biao <jbiao>
Component: Ceph-AnsibleAssignee: Guillaume Abrioux <gabrioux>
Status: CLOSED DUPLICATE QA Contact: Vasishta <vashastr>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.3CC: aschoen, ceph-eng-bugs, gmeno, nthomas, ykaul
Target Milestone: z5   
Target Release: 3.3   
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: 2020-04-07 13:07:14 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 James Biao 2020-02-20 07:04:18 UTC
Description of problem:

When running add-osd.yml bootstrap keys are not fetched and placed back into fetch_directory if the fetch_directory no longer exists, is empty, or the key is otherwise not present on the Ansible node.

Eventually, add-osd.yml gets to a task in the ceph-osd role where it copies back keys to /var/lib/ceph/bootstrap-osd, but fails because the source key in fetch_directory does not exist.

A couple of possible resolutions could be to:

1) Ensure keys are always fetched if fetch_directory is empty, possibly baking this into one of the common roles

2) Provide an additional infrastructure playbook to perform the fetch and re-populate fetch_directory

Version-Release number of selected component (if applicable):
ceph-ansible 3.2.38-1

How reproducible:
Always

Steps to Reproduce:
1.Purging fetch_directory and running add-osd.yml, even without an OSD to replace, should generate the problem
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Guillaume Abrioux 2020-04-07 13:07:14 UTC

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