Description of problem: " radosgw-admin orphans finish --job-id=" crashes. Related upstream bugs are http://tracker.ceph.com/issues/13824 and http://tracker.ceph.com/issues/13888 Version-Release number of selected component (if applicable): ceph version 0.94.5-3.el7cp How reproducible: Always Steps to Reproduce: 1.Configure radosgw and run orphans command tool. # radosgw-admin orphans finish --job-id=test 2> findfinish.txt Segmentation fault (core dumped) From the output of the comamnd: 2016-01-29 07:17:31.912779 7fa407013900 20 init_complete bucket index max shards: 0 *** Caught signal (Segmentation fault) ** in thread 7fa407013900 ceph version 0.94.5-3.el7cp (cd5b9adaf4725d17c27dc32258778be21520e1bb) 1: radosgw-admin() [0x6316c2] 2: (()+0xf100) [0x7fa4037b1100] 3: (RGWOrphanSearch::init(std::string const&, RGWOrphanSearchInfo*)+0x9e) [0x51b61e] 4: (main()+0xbe92) [0x5010b2] 5: (__libc_start_main()+0xf5) [0x7fa4027d4b15] 6: radosgw-admin() [0x5064d9] 2016-01-29 07:17:31.914752 7fa407013900 -1 *** Caught signal (Segmentation fault) ** in thread 7fa407013900 Bt on the coredump: [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `radosgw-admin orphans finish --job-id=something'. Program terminated with signal 11, Segmentation fault. #0 0x00007fdab4319fcb in raise (sig=11) at ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:37 37 return INLINE_SYSCALL (tgkill, 3, pid, THREAD_GETMEM (THREAD_SELF, tid), Missing separate debuginfos, use: debuginfo-install ceph-radosgw-0.94.5-3.el7cp.x86_64 (gdb) bt #0 0x00007fdab4319fcb in raise (sig=11) at ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:37 #1 0x000000000063178d in handle_fatal_signal(int) () #2 <signal handler called> #3 0x000000000051b61e in RGWOrphanSearch::init(std::string const&, RGWOrphanSearchInfo*) () #4 0x00000000005010b2 in main ()
We can cherry-pick https://github.com/ceph/ceph/pull/7186 to ceph-1.3-rhel-patches in Gerrit.
Tested on ceph-0.94.5-8.el7cp. Verified that the command works fine.
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-2016:0313