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 1783412

Summary: ceph-volume - 3.x -zap - output says zapping successful for "None" when tried zapping using osd-fsid
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Vasishta <vashastr>
Component: Ceph-VolumeAssignee: Christina Meno <gmeno>
Status: CLOSED ERRATA QA Contact: Vasishta <vashastr>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.3CC: ceph-eng-bugs, ceph-qe-bugs, tchandra, tserlin
Target Milestone: z4   
Target Release: 3.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: ceph-12.2.12-91.el7cp Ubuntu: ceph_12.2.12-88redhat1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-06 08:27:06 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 2019-12-13 17:30:47 UTC 
Description of problem:
When an OSD is zapped using its fsid, though the OSD gets zapped, the output says that OSD'None' was zapped successfully.

Version-Release number of selected component (if applicable):
ceph version 12.2.12-84.el7cp 

How reproducible:
Always(2/2)

Steps to Reproduce:
1. Zap an OSD using its fsid

Actual results:
# ceph-volume lvm zap --destroy --osd-fsid a6050577-520c-4829-bbde-79aa67cfb03c
--> Zapping: /dev/data_vg/data_lv1
--> Unmounting /var/lib/ceph/osd/ceph-7
Running command: umount -v /var/lib/ceph/osd/ceph-7
 stderr: umount: /var/lib/ceph/osd/ceph-7 (/dev/mapper/data_vg-data_lv1) unmounted
Running command: dd if=/dev/zero of=/dev/data_vg/data_lv1 bs=1M count=10
 stderr: 10+0 records in
10+0 records out
10485760 bytes (10 MB) copied
 stderr: , 0.00518822 s, 2.0 GB/s
--> Only 1 LV left in VG, will proceed to destroy volume group data_vg
Running command: vgremove -v -f data_vg
 stderr: Removing data_vg-data_lv1 (253:0)
 stderr: Archiving volume group "data_vg" metadata (seqno 30).
 stderr: Releasing logical volume "data_lv1"
 stderr: Creating volume group backup "/etc/lvm/backup/data_vg" (seqno 31).
 stdout: Logical volume "data_lv1" successfully removed
 stderr: Removing physical volume "/dev/sdb" from volume group "data_vg"
 stderr: Removing physical volume "/dev/sdd" from volume group "data_vg"
 stdout: Volume group "data_vg" successfully removed
--> Zapping: /dev/sdc1
Running command: dd if=/dev/zero of=/dev/sdc1 bs=1M count=10
 stderr: 10+0 records in
10+0 records out
10485760 bytes (10 MB) copied
 stderr: , 0.049838 s, 210 MB/s
--> Destroying partition since --destroy was used: /dev/sdc1
Running command: parted /dev/sdc --script -- rm 1
--> Zapping successful for OSD: None


This BZ has been created to track the fix into 3.x 
This issue was originally filed as BZ 1738379
Comment 9 Vasishta 2020-03-17 11:27:08 UTC 
Working fine with 12.2.12-101
(tried on a bluestore OSD)
Comment 11 errata-xmlrpc 2020-04-06 08:27:06 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:1320