| 2015-04-06 07:21:40 |
Neeti Munshi |
bug |
|
|
added bug |
| 2015-04-06 07:26:02 |
Neeti Munshi |
description |
In the devstack setup with VPNaas enabled:
1. Establish a IPsec 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. |
In the devstack setup with VPNaas enabled:
1. Establish a IPsec 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 -issue 1
5. If we kill Pluto process also, then the IPsec site connection goes down.
6. If before creating the IPsec site connection IPsec service was stopped, after that if we create IPsec site connection it doesnot become active even after starting the IPsec service.-issue 2 |
|
| 2015-04-06 07:27:09 |
Neeti Munshi |
description |
In the devstack setup with VPNaas enabled:
1. Establish a IPsec 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 -issue 1
5. If we kill Pluto process also, then the IPsec site connection goes down.
6. If before creating the IPsec site connection IPsec service was stopped, after that if we create IPsec site connection it doesnot become active even after starting the IPsec service.-issue 2 |
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 -issue 1
5. If we kill Pluto process also, then the IPsec site connection goes down.
6. If before creating the IPsec site connection IPsec service was stopped, after that if we create IPsec site connection it doesnot become active even after starting the IPsec service.-issue 2 |
|
| 2015-04-06 07:29:42 |
Neeti Munshi |
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 -issue 1
5. If we kill Pluto process also, then the IPsec site connection goes down.
6. If before creating the IPsec site connection IPsec service was stopped, after that if we create IPsec site connection it doesnot become active even after starting the IPsec service.-issue 2 |
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 stop" on either of the cloud.
4. Now check the status of IPsec site connection, it will still show active on both ends.
5. If we kill Pluto process also, then the IPsec site connection goes down.
6. If before creating the IPsec site connection IPsec service was stopped, after that if we create IPsec site connection it doesnot become active even after starting the IPsec service.-issue 2 |
|
| 2015-04-06 07:30:44 |
Neeti Munshi |
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 stop" on either of the cloud.
4. Now check the status of IPsec site connection, it will still show active on both ends.
5. If we kill Pluto process also, then the IPsec site connection goes down.
6. If before creating the IPsec site connection IPsec service was stopped, after that if we create IPsec site connection it doesnot become active even after starting the IPsec service.-issue 2 |
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 stop" on either of the cloud.
4. Now check the status of IPsec site connection, it will still show active on both ends, and the VMs launched on both clouds are still accessible using the private IP. -issue 1
5. If we kill Pluto process also, then the IPsec site connection goes down.
6. If before creating the IPsec site connection IPsec service was stopped, after that if we create IPsec site connection it doesnot become active even after starting the IPsec service.-issue 2 |
|
| 2015-04-17 20:34:50 |
Paul Michali |
neutron: status |
New |
Incomplete |
|
| 2015-04-30 10:36:29 |
Aniruddha Singh Gautam |
neutron: assignee |
|
Aniruddha Singh Gautam (aniruddha-gautam) |
|
| 2016-08-17 23:29:08 |
Armando Migliaccio |
neutron: assignee |
Aniruddha Singh Gautam (aniruddha-gautam) |
|
|
| 2016-10-17 04:21:54 |
Launchpad Janitor |
neutron: status |
Incomplete |
Expired |
|
