Closed deanpemberton closed 8 years ago
Looking now.
I have tested this to not be the case on CentOS 7.1* at least with the following:
# cat /etc/redhat-release && uname -r && ceph --version
CentOS Linux release 7.1.1503 (Core)
3.10.0-229.11.1.el7.x86_64
ceph version 0.94.2 (5fb85614ca8f354284c713a2f9c610860720bbf3)
# rbd showmapped
# rbd map rbd/foo
/dev/rbd0
# rbd unmap /dev/rbd0
# rbd map --id admin --pool rbd foo
/dev/rbd0
Can you attach your version of ceph you are running and any pertinent system info?
jessie/sid 3.16.0-57-generic ceph version 0.80.10 (ea6c958c38df1216bf95c927f143d8b13c4a9e70)
Let me try with a later version of ceph. Thats the latest in the 14.04 repo, so I'll get something directly and retry.
ceph-common: Installed: 0.80.10-0ubuntu1.14.04.3 Candidate: 0.80.10-0ubuntu1.14.04.3 Version table: *\ 0.80.10-0ubuntu1.14.04.3 0 500 http://ftp.X/mirrors/linux/ubuntu/packages/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.79-0ubuntu1 0 500 http://ftp.X/mirrors/linux/ubuntu/packages/ trusty/main amd64 Packages
Maybe just change the PR to include logic to only call getRBDDeviceName if line 832 doesn't return the device? I will put comments on the commit.
That would work.
On Friday, 22 January 2016, Adam Avilla notifications@github.com wrote:
Maybe just change the PR to include logic to only call getRBDDeviceName if line 832 https://github.com/deanpemberton/rbd-docker-plugin/commit/10300b88fa02ad4419b4426e532847520cfa22d1#diff-749da71b40f8ff06fc9e78ce917b0cceR832 doesn't return the device?
— Reply to this email directly or view it on GitHub https://github.com/yp-engineering/rbd-docker-plugin/issues/19#issuecomment-173665986 .
Regards,
Dean
@deanpemberton how did it go? Did you end up just updating ceph and using this as is?
'rbd map' doesn't return the mapped device name.
This means that the name is never returned to the mapImage function and therefore unavailable to later functions.
Here is the output showing what happens when the device name isn't returned by mapImage
I've tested this on Debian Wheezy and Ubuntu 14.04.
I've got a fix which I'll make a pull request for in a second which seems to fix it. More than willing to admit it's not the most glamourous way to handle it though