Install Multipathd with ceph have an ceph_osd error
Bug #1741489 reported by
mhhli
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla-ansible |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I also try to install Multipathd with the ceph as the storage back-end.
Then the bootstrap_osd container will be exit because "mkfs.xfs /dev/sdb1" will get error "mkfs cannot open <device>: Device or resource busy"
I don't know install each container by what order. I see the multipathd container is runing ,then the bootstrap_osd can not runing .
The follow link is I find about this error on the internet.
Changed in kolla-ansible: | |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in kolla-ansible: | |
assignee: | nobody → wangwei (wangwei-david) |
status: | Confirmed → In Progress |
To post a comment you must log in.
We are facing the same issue. OSD_BOOTSTRAP and KOLLA_CEPH_ OSD_CACHE_ BOOTSTRAP.
We have two nodes with multipath enabled with related labels KOLLA_CEPH_
From docker logs of the centos- binary- ceph-osd: 5.0.1 we get:
INFO:__ main__: Loading config file at /var/lib/ kolla/config_ files/config. json main__: Validating config file main__: Copying service configuration files main__: Copying /var/lib/ kolla/config_ files/ceph. conf to /etc/ceph/ceph.conf main__: Setting permission for /etc/ceph/ceph.conf main__: Copying /var/lib/ kolla/config_ files/ceph. client. admin.keyring to /etc/ceph/ ceph.client. admin.keyring main__: Setting permission for /etc/ceph/ ceph.client. admin.keyring main__: Writing out command to execute epoch": 4,"quorum" :[0,1], "quorum_ names": ["172.25. 41.248" ,"172.25. 41.249" ],"quorum_ leader_ name":" 172.25. 41.248" ,"monmap" :{"epoch" :1,"fsid" :"e2b1db1c- a0f9-41f0- b826-d5250a0c98 d5","modified" :"2018- 02-27 18:03:43. 946171" ,"created" :"2018- 02-27 18:03:43. 946171" ,"mons" :[{"rank" :0,"name" :"172.25. 41.248" ,"addr" :"172.25. 41.248: 6789\/0" },{"rank" :1,"name" :"172.25. 41.249" ,"addr" :"172.25. 41.249: 6789\/0" }]}} mpath-sperca (Device or resource busy). This means Linux won't know anything about the modifications you made. 36d09466006fbc5 002184ce7c1fb8d 583 failed: Device or resource busy mpath-spercc (Device or resource busy). This means Linux won't know anything about the modifications you made. 36d09466006fbc5 0021ef5dde1a13d 1f4 failed: Device or resource busy
INFO:__
INFO:__main__:Kolla config strategy set to: COPY_ALWAYS
INFO:__
INFO:__
INFO:__
INFO:__
INFO:__
INFO:__
{"election_
GPT data structures destroyed! You may now partition the disk using fdisk or
other utilities.
Creating new GPT entries.
The operation has completed successfully.
The operation has completed successfully.
device-mapper: remove ioctl on mpath-sperca1 failed: Device or resource busy
Warning: parted was unable to re-read the partition table on /dev/mapper/
device-mapper: create ioctl on mpath-sperca1 part1-mpath-
device-mapper: remove ioctl on mpath-sperca1 failed: Device or resource busy
device-mapper: remove ioctl on mpath-spercc1 failed: Device or resource busy
Warning: parted was unable to re-read the partition table on /dev/mapper/
device-mapper: create ioctl on mpath-spercc1 part1-mpath-
device-mapper: remove ioctl on mpath-spercc1 failed: Device or resource busy
mkfs.xfs: cannot open /dev/sdb1: Device or resource busy
Please take into account that CACHE is enabled that is the reason whit there are mpath-spercc and mpath-sperca.
Thanks.