GBP: PTG delete errors out

[puppet-py]

Created a PTG(implicit L2policy), created a PT and instantiated a VM
Delete workflow:
-------------------------
1. Deleted the VM
2. Deleted the PT
3. Delete the PTG <<<< here it fails. Please refer the log file and search for the string "PTG_DELETE_LOG"

Here is the log sequence of workflow:
===================================

test@localhost:~/devstack$ nova list
+--------------------------------------+-------------+--------+------------+-------------+--------------------- ----+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+-------------+--------+------------+-------------+--------------------- ----+
| 3728859f-7923-4040-a6f9-aa2c29e60812 | client-vm-1 | ACTIVE | - | Running | l2p_client-1=10.0.0. 66 |
| 711d02e8-684c-470a-a334-07185e9abc9b | client-vm-2 | ACTIVE | - | Running | l2p_client-2=10.0.0. 130 |
| 529fc932-d7d5-4feb-8339-ad8640618779 | web-vm-1 | ACTIVE | - | Running | l2p_web=10.0.0.2 |
+--------------------------------------+-------------+--------+------------+-------------+--------------------- ----+
test@localhost:~/devstack$
test@localhost:~/devstack$
test@localhost:~/devstack$ nova delete client-vm-1
Request to delete server client-vm-1 has been accepted.
test@localhost:~/devstack$
test@localhost:~/devstack$ nova delete client-vm-2
Request to delete server client-vm-2 has been accepted.
test@localhost:~/devstack$
test@localhost:~/devstack$ nova delete web-vm-1
Request to delete server web-vm-1 has been accepted.
test@localhost:~/devstack$
test@localhost:~/devstack$
test@localhost:~/devstack$
test@localhost:~/devstack$
test@localhost:~/devstack$ nova list
+----+------+--------+------------+-------------+----------+
| ID | Name | Status | Task State | Power State | Networks |
+----+------+--------+------------+-------------+----------+
+----+------+--------+------------+-------------+----------+
test@localhost:~/devstack$
test@localhost:~/devstack$ gbp policy-target-list
+--------------------------------------+-------------+-------------+--------------------------------------+
| id | name | description | policy_target_group_id |
+--------------------------------------+-------------+-------------+--------------------------------------+
| 66098ae4-9fca-411f-8be8-dabf59f9dc2f | web-pt-1 | | b5cb7cd1-a7fa-4a69-914e-25941aaa853b |
| 6f1c4d89-10fb-4c88-a33b-528a3fd6e9ea | client-pt-2 | | 3f6563c3-297f-4216-89e0-54db16fc04cd |
| acc533d3-269e-463f-a24c-3afd25023f90 | test-pt | | c2bdd707-48a6-4c17-bead-57b09fd5138f |
| fbb40cce-19ed-4acf-b917-63d69035d5df | client-pt-1 | | c3250194-14bf-4968-a4bc-4ef242748827 |
+--------------------------------------+-------------+-------------+--------------------------------------+
test@localhost:~/devstack$
test@localhost:~/devstack$ gbp policy-target-delete web-pt-1
Deleted policy_target: web-pt-1
test@localhost:~/devstack$ gbp policy-target-delete client-pt-1
Deleted policy_target: client-pt-1
test@localhost:~/devstack$ gbp policy-target-delete client-pt-2
Deleted policy_target: client-pt-2
test@localhost:~/devstack$
test@localhost:~/devstack$ gbp policy-target-delete test-pt
Deleted policy_target: test-pt
test@localhost:~/devstack$
test@localhost:~/devstack$ gbp policy-target-group-list
+--------------------------------------+---------+-------------+
| id | name | description |
+--------------------------------------+---------+-------------+
| 3f6563c3-297f-4216-89e0-54db16fc04cd | c2 | |
| 405253a4-5e81-4b01-a924-48d745784fde | J | |
| b5cb7cd1-a7fa-4a69-914e-25941aaa853b | web | |
| c2bdd707-48a6-4c17-bead-57b09fd5138f | testptg | |
| c3250194-14bf-4968-a4bc-4ef242748827 | c1 | |
+--------------------------------------+---------+-------------+
test@localhost:~/devstack$
test@localhost:~/devstack$ gbp policy-target-group-show web
+---------------------------+--------------------------------------+
| Field | Value |
+---------------------------+--------------------------------------+
| consumed_policy_rule_sets | |
| description | |
| id | b5cb7cd1-a7fa-4a69-914e-25941aaa853b |
| l2_policy_id | dda4e553-32a3-4aa2-a4d9-e4449dfd2430 |
| name | web |
| network_service_policy_id | |
| policy_targets | |
| provided_policy_rule_sets | ac9aec17-7ff5-4720-8696-81bba83495ec |
| | e0b2ffd7-94fa-4608-b180-d30bc9e1be65 |
| shared | False |
| subnets | 5060400a-ed05-4383-ac39-358b8931e0dc |
| tenant_id | b3094e3ded7e4d6ea7b91b3641214a7a |
+---------------------------+--------------------------------------+
test@localhost:~/devstack$
test@localhost:~/devstack$ gbp policy-target-group-delete J
Internal Server Error (HTTP 500) (Request-ID: req-d2e9ea93-1693-499e-b6df-767325592697)
test@localhost:~/devstack$

[Sumit Naiksatam (snaiksat)]

It seems that the PTG still had PTs in this case. Are you sure there were no other PTs apart from the one you mention here that was created for the VM?

[puppet-py (jbanerje)]

Yes Sumit .. if I remember there was no PT created for the PTG J.
Unfortunately I do not have the system in the same state to re-verify

I will surely try to see how I re-manifest the issue

Regards
jishnu

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Sumit Naiksatam
Sent: Monday, February 02, 2015 11:23 AM
To: Jishnu Banerjee (jbanerje)
Subject: [Bug 1416527] Re: GBP: PTG delete errors out

It seems that the PTG still had PTs in this case. Are you sure there were no other PTs apart from the one you mention here that was created for the VM?

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1416527

Title:
  GBP: PTG delete errors out

Status in Group Based Policy:
  New

Bug description:
  Created a PTG(implicit L2policy), created a PT and instantiated a VM
  Delete workflow:
  -------------------------
  1. Deleted the VM
  2. Deleted the PT
  3. Delete the PTG <<<< here it fails. Please refer the log file and search for the string "PTG_DELETE_LOG"

  Here is the log sequence of workflow:
  ===================================

  test@localhost:~/devstack$ nova list
  +--------------------------------------+-------------+--------+------------+-------------+--------------------- ----+
  | ID | Name | Status | Task State | Power State | Networks |
  +--------------------------------------+-------------+--------+------------+-------------+--------------------- ----+
  | 3728859f-7923-4040-a6f9-aa2c29e60812 | client-vm-1 | ACTIVE | - | Running | l2p_client-1=10.0.0. 66 |
  | 711d02e8-684c-470a-a334-07185e9abc9b | client-vm-2 | ACTIVE | - | Running | l2p_client-2=10.0.0. 130 |
  | 529fc932-d7d5-4feb-8339-ad8640618779 | web-vm-1 | ACTIVE | - | Running | l2p_web=10.0.0.2 |
  +--------------------------------------+-------------+--------+------------+-------------+--------------------- ----+
  test@localhost:~/devstack$
  test@localhost:~/devstack$
  test@localhost:~/devstack$ nova delete client-vm-1
  Request to delete server client-vm-1 has been accepted.
  test@localhost:~/devstack$
  test@localhost:~/devstack$ nova delete client-vm-2
  Request to delete server client-vm-2 has been accepted.
  test@localhost:~/devstack$
  test@localhost:~/devstack$ nova delete web-vm-1
  Request to delete server web-vm-1 has been accepted.
  test@localhost:~/devstack$
  test@localhost:~/devstack$
  test@localhost:~/devstack$
  test@localhost:~/devstack$
  test@localhost:~/devstack$ nova list
  +----+------+--------+------------+-------------+----------+
  | ID | Name | Status | Task State | Power State | Networks |
  +----+------+--------+------------+-------------+----------+
  +----+------+--------+------------+-------------+----------+
  test@localhost:~/devstack$
  test@localhost:~/devstack$ gbp policy-target-list
  +--------------------------------------+-------------+-------------+--------------------------------------+
  | id ...

[Robert Kukura (rkukura)]

From the log file, it seems the PTG delete was trying to delete an implicit L2P, which was trying to delete an implicit L3P, which was trying to delete a Router, which still had a port.

Can you verify that both the L2P and L3P were implicitly created, and that this PTG was the last reference to both of them?

Did any previous commands involving the same implicit L3P or any L2Ps, PTGs or PTs referencing it fail, possibly leaving things in a bad state?

If you can recreate this failure, can you use "neutron router-list" and other commands to try and track down what subnet still has a port on the PTG's L2P's L3P's Router?

[Chenghui Yu (chenghuiyu)]

From the bug file, there are two provided_policy_rule_sets related to the policy target group, before you delete the policy target group ,you should delete the provided_policy_rule_sets firstly.