[STAC] - passwordless communication between pods

[mrsiano]

The issue is, we can't ssh from container to docker host.

when executing the stac networking test (https://github.com/openshift/svt/blob/master/networking/synthetic/run-stac-test.sh), it is always ask for ssh psswd.
since we have some sort of iterations it is not ideal for execution.
we need to include the ssh-key inside the container to avoid any ssh authentication dialog during the test execution.

I tried few different methods:

• edit the dockerfile and redeploy the application from scratch within the docker host '.ssh' folder - it works when I test it with some fedora container, but for our s2i it doesn't.
• I tired to copy keys online manually from the container - didn't work.

please advise
@sjug @vikaschoudhary16 @jeremyeder

[jeremyeder]

I understand what you're saying but I don't see any ssh commands in run-stac-test.sh.

Is this the part that's not happening?

svt/networking/synthetic/content/stac-deploymentconfig.yaml

Line 59 in 17123a3

- mountPath: "/root/.ssh/id_rsa"

[mrsiano]

hmmm, it's used by stac-build-n-deploy.sh
but yet, it is not working, we need to debug it.
also the run-stac-test.sh dose not execute ssh commands but calls other script inside the container such as runTest.sh, run_common.sh and others.

[vikaschoudhary16]

@mrsiano please enable passwordless ssh between the hosts by updating "/root/.ssh/authorized_keys". Once hosts are able to connect passwordless, containers will also be able to connect passwordless because all the ssh configuration is being mounted into stac containers in deploymentconfig as refered by Jeremy above.
Before running stack test, you can verify that passwordless ssh is happening between producer and consumer containers. If face any port related error, we might need configure ssh client and ssh server in the Docker file to use any other port than 22. May be i missed to commit the updated Dockerfile with these port related changes. But please verify it first.

And then run run-stact-test.sh.
After verification, you can automate steps for passwordless ssh b/w hosts at "host-prepare" stage.

[mrsiano]

Issue resolved by ssh-copy-id . from each other.

we should automate it, as part of the prepare nodes script.

[sjug]

@mrsiano The ssh keys are mounted into the pod, you don't need to ssh-copy-id as @vikaschoudhary16 has already explained...

[mrsiano]

@sjug @vikaschoudhary16 right, but it worked for me only when the entries of the hosts was placed there, we should consider to have an automation for that thing, may be in part of the prepare-nodes script.

cause authorized_keys file must include the relevant entries, in our case, 70.70.70.x and the actual host name.
and for now we add them manually.

it dose not work unless we copy the keys each other (bare-metal).
note: we should done it just once when establishing the env, or re-provision it.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.