So the situation is:
* VM1 has a floating IP and can be reached via floating IP
* VM1 can ping VM2
* VM2 can't ssh VM2
Useful additional information you may have gathered already:
* Does the ssh client issue any error message, and which?
* Is an sshd running on VM2?
* If yes, any err
On 04/06/2018 01:28 PM, s serge wrote:
Hello,
I'm evaluating an installation and everything from networking side was looking
good
until I tried to reach a VM host via private network from another VM via ssh.
In short:
1. Spawn a VM
2. Associate a floating IP
3. Logon to VM via ssh on public ne
I'm sorry, some corrections,
p.5 and p.6 should be:
5. From 1st VM try to reach the second VM(p.4) via ssh private network IP -
FAIL.
6. ICMP from 1st VM to second(p.4) IP via private network works well.
06.04.2018, 20:42, "s serge" :
> Hello,
>
> I'm evaluating an installation and everything
Hello,
I'm evaluating an installation and everything from networking side was looking
good
until I tried to reach a VM host via private network from another VM via ssh.
In short:
1. Spawn a VM
2. Associate a floating IP
3. Logon to VM via ssh on public network
4. Spawn another VM
5. Try to reac
OPNFV - Danube 3.0 Fuel install error.
I am getting this error during the openstack install process. I have
installed OS using fuel many times, and never ran into this.
It says pacemaker can't install without corosync, but it appears to be
installed. Would anyone know why I'm seeing this error?
