Volume pushing using iofog2.0-rc1


(Jingyang Chen) #1

Hello,

All, I have successfully used the new feature - volume, of iofog2.0 couple weeks ago using the iofog beta - 4 version, the volume has been pushed to my agent and the microservice was running well.

I saw an update of iofog2.0, so I just updated to iofog2.0-rc1, I can successfully deploy microservice, but when I try to push the volume, I always get the error - “✘ dial tcp 123.127.237.44:22: connect: connection timed out” and I can see the volume show up when I use $iofogctl get all but I can not delete the volume either, will get the same error - “✘ dial tcp 123.127.237.44:22: connect: connection timed out”

Do you think this is some issue related to my network connection? Thank you for the help in advance!


(Serge Radinovich) #2

The commands failing with that error are failing to SSH into the corresponding Agent (123.127.237.44).

Can you verify that you can manually SSH to that Agent from the machine you are running iofogctl from please?


(Jingyang Chen) #3

Hi,

my virtual machine is actually behind a NAT, and it’s address is 192.168.12.150, before I could deploy the volume but after update the iofogctl, I could not, it should not be SSH to 123.127.237.44, instead it should be trying to SSH to 192.168.12.150. Do you know how can I resolve this issue?

Thanks,
Jingyang


(Serge Radinovich) #4

Could you please redeploy the Agent with the 192.168.12.150 address and let me know if the problem persists?


(Jingyang Chen) #5

I deployed the agent with the address 192.168.12.151(sorry, I had a typo, it is 151), here is my yaml file, but I can do it again and let you know.


apiVersion: iofog.org/v2
kind: Agent
metadata:
name: agent-151
namespace: default
spec:
host: 192.168.12.151
ssh:
user: ubuntu
keyFile: ~/.ssh/iofog_rsa
port: 22

but when I do,
ubuntu@iotagent-cephese-209:~/iofog-rc1$ sudo iofogctl get all
NAMESPACE
default

CONTROLLER STATUS AGE UPTIME ADDR PORT
vm-209 online - 1d1h 192.168.12.209 51121

AGENT STATUS AGE UPTIME ADDR VERSION
agent-151 RUNNING 10d1h 123.127.237.42 2.0.0-rc1

the address is 123.127.237.42, but not 151, because our virtual machine is behind the NAT.


(Serge Radinovich) #6

Sorry for the confusion - I have realized that iofogctl 2.0.0-rc2 does not have the fix for this issue.

We have not released a fix yet so the only solution for now is to build iofogctl from source on the develop branch.