<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 1, 2015 at 11:32 AM, Krishnan Parthasarathi <span dir="ltr"><<a href="mailto:kparthas@redhat.com" target="_blank">kparthas@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
> Yeah this followed by glusterd restart should help<br>
><br>
> But frankly, i was hoping that 'rm' the file isn't a neat way to fix this<br>
> issue<br>
<br>
</span>Why is rm not a neat way? Is it because the container deployment tool needs to<br>
know about gluster internals? But isn't a Dockerfile dealing with details<br>
of the service(s) that is being deployment in a container.<br></blockquote><div><br></div><div>IIUC post 'rm' we need to restart glusterd, but touching a file as part of Dockerfile<br></div><div>would bringup glusterd with the new UUID. I haven't tried this tho'<br><br></div><div>I guess like Humble said, fixing this in glusterd seems ideal<br></div><div>The above discussion was _if_ glusterd continues the current behavior<br></div><div>then either 'rm' or 'touch' methods could be considered.<br><br></div><div>thanx,<br></div><div>deepak<br></div></div><br></div></div>