yahoo-eng-team team mailing list archive

[sun <nnusun@xxxxxxxx>]

Public bug reported:

When I create two ipsec-site-connections as the following steps,
the first ipsec-site-connection's status is blocked on "DOWN"
the environment has only one network node.
step1: use tenantA create ipsec-site-connection-A
step2: use tenantB(not admin tenant)create  ipsec-site-connection-B

After  ipsec-site-connection-B is created,  ipsec-site-connection-B's 
status becomes "ACTIVE" while  ipsec-site-connection-A's status
is blocked on "DOWN"

This can happen on the following condition too.
environment A has only one network node.
step1: use tenantA create ipsec-site-connection-A on environment A
step2: use tenantB create ipsec-site-connection-B on environment B
step3: before the neutron-vpn-agent's loopcall is executed on environment A 
             use tenantC(not admin tenant) to create ipsec-site-connection-C
After ipsec-site-connection-C is created,  ipsec-site-connection-A's status
is blocked on "DOWN" and can not be changed by the neutron-vpn-agent's loopcall.

** Affects: neutron
     Importance: Undecided
     Assignee: sun (nnusun)
         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/1531743

Title:
  ipsec site connection status is blocked on "DOWN"

Status in neutron:
  New

Bug description:
  When I create two ipsec-site-connections as the following steps,
  the first ipsec-site-connection's status is blocked on "DOWN"
  the environment has only one network node.
  step1: use tenantA create ipsec-site-connection-A
  step2: use tenantB(not admin tenant)create  ipsec-site-connection-B

  After  ipsec-site-connection-B is created,  ipsec-site-connection-B's 
  status becomes "ACTIVE" while  ipsec-site-connection-A's status
  is blocked on "DOWN"

  This can happen on the following condition too.
  environment A has only one network node.
  step1: use tenantA create ipsec-site-connection-A on environment A
  step2: use tenantB create ipsec-site-connection-B on environment B
  step3: before the neutron-vpn-agent's loopcall is executed on environment A 
               use tenantC(not admin tenant) to create ipsec-site-connection-C
  After ipsec-site-connection-C is created,  ipsec-site-connection-A's status
  is blocked on "DOWN" and can not be changed by the neutron-vpn-agent's loopcall.

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