Hide Forgot
Description of problem: By default host system sshd is running on 22 port. To access RHGS container using Heketi need to stop sshd service on host system and start on RHGS container. Using host Networking for RHGS containers. on RHGS conatiner: journalctl -u sshd Apr 20 05:24:35 hostname sshd[445]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. Apr 20 05:24:35 hostname sshd[445]: error: Bind to port 22 on :: failed: Address already in use. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1] Create two RHGS container 2] Try to load topology file using heketi-cli Actual results: Trying to access host system and failing with [sshexec] ERROR 2016/04/21 11:43:29 /builddir/build/BUILD/heketi-6563551111f7178b679866e85a0682325929d037/src/github.com/heketi/heketi/utils/ssh/ssh.go:155: Failed to run command [sudo gluster peer probe 10.70.34.60] on 10.70.34.54:22: Err[Process exited with: 1. Reason was: ()]: Stdout []: Stderr [sudo: gluster: command not found Expected results: Should load topology file Additional info:
Upstream: https://github.com/heketi/heketi/issues/289
This looks like incorrect configuration. Only one RHGS container is supported per node. Running two container will cause the port conflict which is shown above. I think this bug is invalid, right?
It has only one RHGS container running, its conflicting with the port used by Host system.
Updated RHGS 3 layered docker image based on RHGS 3.1.3 and RHEL 7.2.2 available (rhgs-server-docker-3.1.3-8). Brew build @ https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=496477 . This has '3.7.9-6.el7rhgs' gluster package and the fix for this issue.