Description of problem: Unable to open images from nautilus client for luminous cluster Version-Release number of selected component (if applicable): 14.2.0 How reproducible: Always Steps to Reproduce: 1. From nautilus client for luminous cluster, try to access an image Actual results: $ sudo rbd bench --io-type write --io-total 10M from_rhcs4_client/image_1 2019-03-29 06:22:04.050 7f99ce7fc700 -1 librbd::image::RefreshRequest: failed to retrieve group: (95) Operation not supported 2019-03-29 06:22:04.051 7f99cdffb700 -1 librbd::image::OpenRequest: failed to refresh image: (95) Operation not supported 2019-03-29 06:22:04.051 7f99cdffb700 -1 librbd::ImageState: 0x55e72c570570 failed to open image: (95) Operation not supported rbd: error opening image image_1: (95) Operation not supported Expected results: client should be able to open image
I'm having similar problems, but with Kubernetes PVCs after upgrading one of my Kubernetes nodes to Fedora 30.
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. Regards, Giri
Verified bug on 3.x with 4.0 client version and it's working as expected. [root@f23-h33-000-6018r ceph]# rbd bench --io-type write g_data/g_image --cluster site-a -n client.site-a bench type write io_size 4096 io_threads 16 bytes 1073741824 pattern sequential SEC OPS OPS/SEC BYTES/SEC 1 15104 15014.82 61500696.55 2 28080 14033.89 57482829.19 3 40368 13398.74 54881225.32 4 51680 12811.83 52477255.70 5 65168 12905.10 52859293.32 6 75312 12060.84 49401181.77 7 85744 11434.40 46835322.02 8 94784 10771.12 44118525.22 9 105584 10830.57 44361994.82 10 117088 10493.07 42979633.39 11 126320 9964.39 40814161.59 3.x cluster details: ceph version 12.2.12-83.el7cp (4b34b893d114fdf8fcbf17368a3702cbfcf668d6) luminous (stable) ceph-mon-12.2.12-83.el7cp.x86_64 ceph-ansible-3.2.36-1.el7cp.noarch 4.0 client details: ceph version 14.2.4-91.el8cp (23607558df3b077b6190cdf96cd8d9043aa2a1c5) nautilus (stable)
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:0312