Description of problem: Tendrl creates RBD which cannot be mapped. It is created with unsupported feature: $ rbd --cluster test_ceph map rbd2 rbd: sysfs write failed RBD image feature set mismatch. You can disable features unsupported by the kernel with "rbd feature disable". In some cases useful info is found in syslog - try "dmesg | tail" or so. rbd: map failed: (6) No such device or address $ dmesg | tail rbd: image rbd2: image uses unsupported features: 0x38 Version-Release number of selected component (if applicable): ceph-ansible-2.2.11-1.el7scon.noarch ceph-base-11.2.0-0.el7.x86_64 ceph-common-11.2.0-0.el7.x86_64 ceph-installer-1.3.0-1.el7scon.noarch ceph-mon-11.2.0-0.el7.x86_64 ceph-osd-11.2.0-0.el7.x86_64 ceph-selinux-11.2.0-0.el7.x86_64 etcd-3.1.7-1.el7.x86_64 libcephfs2-11.2.0-0.el7.x86_64 python-cephfs-11.2.0-0.el7.x86_64 python-etcd-0.4.5-1.noarch rubygem-etcd-0.3.0-1.el7.noarch tendrl-alerting-3.0-alpha.3.el7scon.noarch tendrl-api-3.0-alpha.4.el7scon.noarch tendrl-api-doc-3.0-alpha.4.el7scon.noarch tendrl-api-httpd-3.0-alpha.4.el7scon.noarch tendrl-ceph-integration-3.0-alpha.5.el7scon.noarch tendrl-commons-3.0-alpha.9.el7scon.noarch tendrl-dashboard-3.0-alpha.4.el7scon.noarch tendrl-node-agent-3.0-alpha.9.el7scon.noarch tendrl-node-monitoring-3.0-alpha.5.el7scon.noarch tendrl-performance-monitoring-3.0-alpha.7.el7scon.noarch How reproducible: 100% Steps to Reproduce: 1. create RBD by Tendrl 2. try to map it Actual results: image uses unsupported features: 0x38 Expected results: It is able to map rbd created by Tendrl.
Martin, I use below set of commands to map the RBD. By default rbd created from tendrl is not disabled any features as the command `rbd create {image-name} --size {megabytes} --pool {pool-name} --cluster {cluster-name}` is used in tendrl ===================== > rbd feature disable {rbd-name} fast-diff --cluster {cluster-name} > rbd feature disable {rbd-name} object-map --cluster {cluster-name} > rbd feature disable {rbd-name} deep-flatten --cluster {cluster-name} > rbd map {rbd-name} --cluster {cluster-name} /dev/rbd0 > mkfs -t xfs /dev/rbd0 > mkdir ~/rbd_mnt > mount /dev/rbd0 ~/rbd_mnt
I haven't done steps: > rbd feature disable {rbd-name} fast-diff --cluster {cluster-name} > rbd feature disable {rbd-name} object-map --cluster {cluster-name} > rbd feature disable {rbd-name} deep-flatten --cluster {cluster-name} because I think that RBD created by Tendrl should be prepared for mapping right after it is created without any special tuning. I tried it on top of RHEL 7.4 and ceph-base-11.2.0-0.el7.x86_64 ceph-common-11.2.0-0.el7.x86_64 ceph-mon-11.2.0-0.el7.x86_64 ceph-selinux-11.2.0-0.el7.x86_64 libcephfs2-11.2.0-0.el7.x86_64 python-cephfs-11.2.0-0.el7.x86_64
Is there a specific requirement talks about this? Even in RHSC2.0 there was discussion around this(cblum initiated) and finally we decided to go ahead with the standard option @JeffA can you comment here?
@kbader can you comment on this?
This product is EOL now