Description of problem: Clufter does not add "bind" to the "options" option of filesystem resource. Because of this the resource fails to start when config is deployed. Version-Release number of selected component (if applicable): next branch, commit f5fa0f8fccacb1bdc76ec792df34f9bf373f8229 How reproducible: always Steps to Reproduce: 1. working cluster.conf with bind-mount resource 2. convert with clufter 3. deploy to pacemaker cluster Actual results: $ pcs status ... RESOURCE-bind-mount-foo (ocf::heartbeat:Filesystem): Stopped ... RESOURCE-bind-mount-foo_start_0 on host-028.example.com 'unknown error' (1): call=44, status=complete, exit-reason='Couldn't mount filesystem /var on /mnt/foo', last-rc-change='Fri Mar 27 08:05:36 2015', queued=0ms, exec=109ms ... Expected results: bind mount converted to working bind mount Additional info: none
Created attachment 1009682 [details] cluster.conf with bind-mount resource
Fixed upstream as of: https://github.com/jnpkrn/clufter/commit/be5f2b1411d43270c35b4a9c8452c996064eaba9