yahoo-eng-team team mailing list archive

[Neeti Munshi <neeti.munshi@xxxxxxxxxxx>]

Public bug reported:

In the devstack setup with VPNaas enabled:

1. Establish a IPsec site connection between 2 devstack clouds.
2. Verify that the connection is active from both ends.
3. Now run "service ipsec status" on either of the cloud.

$ service ipsec status
IPsec running - pluto pid: 8489
pluto pid 8489
No tunnels up

4. ipsec status shows that there is no tunnel up, though there is a
active and working IPsec site connection established.

** 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/1440655

Title:
  VPNaas:service ipsec status gives incorrect status of the ipsec
  tunnel.

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  In the devstack setup with VPNaas enabled:

  1. Establish a IPsec site connection between 2 devstack clouds.
  2. Verify that the connection is active from both ends.
  3. Now run "service ipsec status" on either of the cloud.

  $ service ipsec status
  IPsec running - pluto pid: 8489
  pluto pid 8489
  No tunnels up

  4. ipsec status shows that there is no tunnel up, though there is a
  active and working IPsec site connection established.

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