<div dir="ltr"><div>A quick thought:<br><br></div>Any luk if you supply "2222" instead of "22" via heketi.json ?<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 30, 2017 at 7:35 PM, Jose A. Rivera <span dir="ltr"><<a href="mailto:jarrpa@redhat.com" target="_blank">jarrpa@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Slightly different error. Yours is:<br>
<br>
/src/<a href="http://github.com/heketi/heketi/executors/sshexec/peer.go:76" rel="noreferrer" target="_blank">github.com/heketi/heketi/<wbr>executors/sshexec/peer.go:76</a>: dial tcp<br>
<a href="http://192.168.10.100:22" rel="noreferrer" target="_blank">192.168.10.100:22</a>: getsockopt: no route to host<br>
<br>
Mine is:<br>
<br>
/src/<a href="http://github.com/heketi/heketi/executors/sshexec/peer.go:76" rel="noreferrer" target="_blank">github.com/heketi/heketi/<wbr>executors/sshexec/peer.go:76</a>: dial tcp<br>
<a href="http://192.168.121.249:22" rel="noreferrer" target="_blank">192.168.121.249:22</a>: getsockopt: connection timed out<br>
<br>
What's your setup? I'm just using the gluster-kubernetes vagrant environment.<br>
<span class="HOEnZb"><font color="#888888"><br>
--Jose<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Wed, Aug 30, 2017 at 8:03 AM, Michael Adam <<a href="mailto:obnox@samba.org">obnox@samba.org</a>> wrote:<br>
> Seems like you're hitting the same thing that I asked about<br>
> two weeks ago:<br>
><br>
> <a href="http://lists.gluster.org/pipermail/heketi-devel/2017-August/000165.html" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>pipermail/heketi-devel/2017-<wbr>August/000165.html</a><br>
><br>
> (with unmodified code)<br>
><br>
> You seem to have a few more clues than I do.<br>
> I'll have to re-test again. Just linking the<br>
> two cases for now...<br>
><br>
> Cheers - Michael<br>
><br>
> On 2017-08-29 at 13:17 -0500, Jose A. Rivera wrote:<br>
>> Ping.<br>
>><br>
>> Also, I forgot to mention that I'm running glusterd natively on the<br>
>> same nodes running kubelet, so similar to our default test setup just<br>
>> non-containerized GlusterFS. I realized that the node that succeeds is<br>
>> the one that the heketi pod is running on. :)<br>
>><br>
>> On Sat, Aug 26, 2017 at 5:39 PM, Jose A. Rivera <<a href="mailto:jarrpa@redhat.com">jarrpa@redhat.com</a>> wrote:<br>
>> > Howdy, List!<br>
>> ><br>
>> > I'm having some trouble with (I think?) getting the heketi SSH<br>
>> > executor to work from a container in Kubernetes.<br>
>> ><br>
>> > For a reference of my environment, I'm running and testing gk-deploy from here:<br>
>> ><br>
>> > <a href="https://github.com/jarrpa/gluster-kubernetes/tree/jarrpa-dev" rel="noreferrer" target="_blank">https://github.com/jarrpa/<wbr>gluster-kubernetes/tree/<wbr>jarrpa-dev</a><br>
>> ><br>
>> > I'm using the provided vagrant environment (with some minor storage<br>
>> > modifications) and running the following test files:<br>
>> ><br>
>> > tests/complex/test-setup.sh <-- sets up the vagrant environment<br>
>> > tests/complex/test-gk-deploy-<wbr>ssh.sh <-- runs test-inside-gk-deploy with SSH exec<br>
>> > tests/complex/test-inside-gk-<wbr>deploy.sh <-- actually runs gk-deploy<br>
>> > with SSH params<br>
>> ><br>
>> > When I run gk-deploy, the script has checks to verify that glusterd is<br>
>> > running on the target nodes (check if "gluster volume info" succeeds)<br>
>> > and those succeed. The script then goes along as normal until it tries<br>
>> > to load the topology. At that point the two nodes of my three nodes<br>
>> > experience SSH timeouts but the third one succeeds. Naturally, the<br>
>> > script fails out after that. There seems to be no pattern on which<br>
>> > nodes fail or succeed between iterations of the vagrant environment,<br>
>> > but thus far it seems consistent that only one will succeed.<br>
>> ><br>
>> > I've attached the heketi log from the container trying to run the<br>
>> > topology load. I've turned on as much debugging as I could find, but<br>
>> > still didn't see any clues.<br>
>> ><br>
>> > Any ideas? :)<br>
>> ><br>
>> > Thanks,<br>
>> > --Jose<br>
>> ______________________________<wbr>_________________<br>
>> heketi-devel mailing list<br>
>> <a href="mailto:heketi-devel@gluster.org">heketi-devel@gluster.org</a><br>
>> <a href="http://lists.gluster.org/mailman/listinfo/heketi-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/heketi-devel</a><br>
______________________________<wbr>_________________<br>
heketi-devel mailing list<br>
<a href="mailto:heketi-devel@gluster.org">heketi-devel@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/heketi-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/heketi-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div>Cheers,<br>Humble<br><br></div>Red Hat Storage Engineering<br></div><div>Mastering KVM Virtualization: <span><a href="http://amzn.to/2vFTXaW" target="_blank">http://amzn.to/2vFTXaW</a></span></div>Website: <a href="http://humblec.com" target="_blank">http://humblec.com</a><br></div></div></div></div></div></div>
</div>