[heketi-devel] Trouble with SSH executor

[Jose A. Rivera]

Slightly different error. Yours is:

/src/github.com/heketi/heketi/executors/sshexec/peer.go:76: dial tcp
192.168.10.100:22: getsockopt: no route to host

Mine is:

/src/github.com/heketi/heketi/executors/sshexec/peer.go:76: dial tcp
192.168.121.249:22: getsockopt: connection timed out

What's your setup? I'm just using the gluster-kubernetes vagrant environment.

--Jose

On Wed, Aug 30, 2017 at 8:03 AM, Michael Adam <obnox at samba.org> wrote:
> Seems like you're hitting the same thing that I asked about
> two weeks ago:
>
> http://lists.gluster.org/pipermail/heketi-devel/2017-August/000165.html
>
> (with unmodified code)
>
> You seem to have a few more clues than I do.
> I'll have to re-test again. Just linking the
> two cases for now...
>
> Cheers - Michael
>
> On 2017-08-29 at 13:17 -0500, Jose A. Rivera wrote:
>> Ping.
>>
>> Also, I forgot to mention that I'm running glusterd natively on the
>> same nodes running kubelet, so similar to our default test setup just
>> non-containerized GlusterFS. I realized that the node that succeeds is
>> the one that the heketi pod is running on. :)
>>
>> On Sat, Aug 26, 2017 at 5:39 PM, Jose A. Rivera <jarrpa at redhat.com> wrote:
>> > Howdy, List!
>> >
>> > I'm having some trouble with (I think?) getting the heketi SSH
>> > executor to work from a container in Kubernetes.
>> >
>> > For a reference of my environment, I'm running and testing gk-deploy from here:
>> >
>> > https://github.com/jarrpa/gluster-kubernetes/tree/jarrpa-dev
>> >
>> > I'm using the provided vagrant environment (with some minor storage
>> > modifications) and running the following test files:
>> >
>> > tests/complex/test-setup.sh <-- sets up the vagrant environment
>> > tests/complex/test-gk-deploy-ssh.sh <-- runs test-inside-gk-deploy with SSH exec
>> > tests/complex/test-inside-gk-deploy.sh <-- actually runs gk-deploy
>> > with SSH params
>> >
>> > When I run gk-deploy, the script has checks to verify that glusterd is
>> > running on the target nodes (check if "gluster volume info" succeeds)
>> > and those succeed. The script then goes along as normal until it tries
>> > to load the topology. At that point the two nodes of my three nodes
>> > experience SSH timeouts but the third one succeeds. Naturally, the
>> > script fails out after that. There seems to be no pattern on which
>> > nodes fail or succeed between iterations of the vagrant environment,
>> > but thus far it seems consistent that only one will succeed.
>> >
>> > I've attached the heketi log from the container trying to run the
>> > topology load. I've turned on as much debugging as I could find, but
>> > still didn't see any clues.
>> >
>> > Any ideas? :)
>> >
>> > Thanks,
>> > --Jose
>> _______________________________________________
>> heketi-devel mailing list
>> heketi-devel at gluster.org
>> http://lists.gluster.org/mailman/listinfo/heketi-devel