yahoo-eng-team team mailing list archive

["Maxim V. Yefimov" <mefimov@xxxxxxxxxxxx>]

Public bug reported:

SSH, HTTP and other services are not accessible from VM1 to VM2 if both
these VMs have floating IP assigned, spawned on the same host and on
same private network. From VM1, ping to VM2 floating IP is successful,
but looks like it isn't reaching VM2 and stops on qr interface.

Steps to reproduce:

VM1 and VM2 runs on the same host.

VM1 has fixed IP of 10.10.3.5, floating-ip=10.17.1.44
VM2 has fixed IP of 10.10.3.17 floating-ip=10.17.1.46

Logged into VM1

# curl 10.17.1.46
curl: (7) Failed to connect to 10.17.1.46 port 80: Connection refused
# ssh 10.17.1.46
connect to host 10.17.1.46 port 22: Connection refused

Same commands are successful from hypervisor console.
Same commands are successful from VM1 if we use private IP (10.10.3.17) for VM2.

Security group

ALLOW IPv4 80/tcp from 0.0.0.0/0
ALLOW IPv4 to 0.0.0.0/0
ALLOW IPv4 22/tcp from 0.0.0.0/0
ALLOW ICMP any from 0.0.0.0/0

Singular case:

VM with floating IP couldn't reach itself by SSH via its floating IP

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1640555

Title:
  In an environment with DVR, a VM with floating IP is not reachable
  (through its floating IP) by another VM with floating IP, while both
  are on the same private network and same hypervisor.

Status in neutron:
  New

Bug description:
  SSH, HTTP and other services are not accessible from VM1 to VM2 if
  both these VMs have floating IP assigned, spawned on the same host and
  on same private network. From VM1, ping to VM2 floating IP is
  successful, but looks like it isn't reaching VM2 and stops on qr
  interface.

  Steps to reproduce:

  VM1 and VM2 runs on the same host.

  VM1 has fixed IP of 10.10.3.5, floating-ip=10.17.1.44
  VM2 has fixed IP of 10.10.3.17 floating-ip=10.17.1.46

  Logged into VM1

  # curl 10.17.1.46
  curl: (7) Failed to connect to 10.17.1.46 port 80: Connection refused
  # ssh 10.17.1.46
  connect to host 10.17.1.46 port 22: Connection refused

  Same commands are successful from hypervisor console.
  Same commands are successful from VM1 if we use private IP (10.10.3.17) for VM2.

  Security group

  ALLOW IPv4 80/tcp from 0.0.0.0/0
  ALLOW IPv4 to 0.0.0.0/0
  ALLOW IPv4 22/tcp from 0.0.0.0/0
  ALLOW ICMP any from 0.0.0.0/0

  Singular case:

  VM with floating IP couldn't reach itself by SSH via its floating IP

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1640555/+subscriptions