non-existent block device should make deploy fail, not create directory whose name starts with /dev
Bug #1665697 reported by
John Fulton
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
puppet-ceph |
Fix Released
|
Medium
|
John Fulton |
Bug Description
- puppet-ceph can receive a list of block devices to set each up as an OSD.
- if a user passes a block device that doesn't actually exist (/dev/$foo), then the user made a mistake
- in that case the deploy should fail and point out this mistake to the user so they can check if they're hardware is broken and decide what to do
- instead it produces a working deployment but...
- the OSD that should be on a block device is on a directory named /dev/$foo
- this is bad because the user may think they have a real block device backing their OSD when they don't
Changed in puppet-ceph: | |
assignee: | nobody → John Fulton (jfulton-org) |
status: | New → Confirmed |
Changed in puppet-ceph: | |
importance: | Undecided → Medium |
To post a comment you must log in.
What you get in this scenario is a working directory-based OSD, not block-based directory as the user intended (and they did intend it if they passed /dev/foo along with a list of other block devices).
[root@osd ~]# ls -laF /dev/sdq
total 28
drwxr-xr-x. 3 ceph ceph 220 Feb 17 10:10 ./
drwxr-xr-x. 22 root root 3180 Feb 17 10:10 ../
-rw-r--r--. 1 root root 189 Feb 17 10:10 activate.monmap
-rw-r--r--. 1 ceph ceph 37 Feb 17 10:10 ceph_fsid
drwxr-xr-x. 3 ceph ceph 80 Feb 17 10:10 current/
-rw-r--r--. 1 ceph ceph 37 Feb 17 10:10 fsid
-rw-r--r--. 1 ceph ceph 0 Feb 17 10:10 journal
-rw-r--r--. 1 ceph ceph 21 Feb 17 10:10 magic
-rw-r--r--. 1 ceph ceph 4 Feb 17 10:10 store_version
-rw-r--r--. 1 ceph ceph 53 Feb 17 10:10 superblock
-rw-r--r--. 1 ceph ceph 2 Feb 17 10:10 whoami