share_volume_fstype configuration option not used
Bug #1525933 reported by
Thomas Bechtold
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Won't Fix
|
Low
|
Unassigned |
Bug Description
When specifying "share_
tags: | added: liberty-backport-potential |
Changed in manila: | |
assignee: | nobody → NidhiMittalHada (nidhimittal19) |
Changed in manila: | |
assignee: | NidhiMittalHada (nidhimittal19) → nobody |
tags: |
added: driver generic removed: liberty-backport-potential |
To post a comment you must log in.
Hi Thomas
As discussed on IRC
The experiments i did to understand the bug .. says that
if i use share_volume_ fstype= ext3 in [DEFAULT] in /etc/manila/ manila. conf file
it remains ext4 as you mentioned.
but fstype= ext3 in [generic1] in the group as handles_ share_servers = True instance_ user = manila service- image .ssh/id_ rsa .ssh/id_ rsa.pub share.drivers. generic. GenericShareDri ver fstype= ext3
if we set share_volume_
[generic1]
driver_
service_
service_image_name = manila-
path_to_private_key = /home/stack/
path_to_public_key = /home/stack/
share_backend_name = GENERIC1
share_driver = manila.
share_volume_
i am not facing any bug
its coming correctly.
my doubt is ..
is it right to put it in generic section .. ??