LVM getting stuck in containerized cinder-volume
Bug #1700982 reported by
Jiří Stránský
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Jiří Stránský |
Bug Description
When trying to use LVM with udev-related capabilities in a cinder-volume container, all LVM calls gets stuck. This was the root cause of the infamous bug 1698136 that even prevented log collection from happening.
Additional info:
https:/
Changed in tripleo: | |
assignee: | nobody → Jiří Stránský (jistr) |
status: | Triaged → In Progress |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/478164 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=e718f93872a 070969050f60ce5 3a15c234c717a5
Committed: https:/
Submitter: Jenkins
Branch: master
commit e718f93872a0709 69050f60ce53a15 c234c717a5
Author: Jiri Stransky <email address hidden>
Date: Tue Jun 27 15:48:40 2017 +0200
LVM in cinder-volume container without udev
Disabling udev usage from LVM seems to be the only observed working
way of running containerized cinder-volume with local LVM backend.
I didn't come across reports that not using udev would have negative
impact on the functionality.
Additional info at /groups. google. com/forum/ #!topic/ docker- user/n4Xtvsb4RA w
https:/
Change-Id: I491795deab0c37 d1bad3b50524481 e0b76529667 66fa6bf9b8bcc9f 3ac3d922a49
Depends-On: I1bf395a6228dba
Closes-Bug: #1700982