Scenario "boot-runcommand-delete" doesn't properly clean resources after completion

Bug #1414597 reported by Evgeny Sboychakov
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Rally
Fix Released
High
Pavel Boldin

Bug Description

After successful launching and then stopping the Virtual Machine the "boot-runcommand-delete" scenario does not delete the network created.

The following error could be found in the log:

2015-01-26 12:03:12.201 29512 INFO rally.benchmark.context.network [-] Task d1b3152d-1dc5-4e1e-b209-aa7c8ac78dca | Starting: Exit context: `network`
2015-01-26 12:03:20.717 29512 ERROR rally.benchmark.context.network [-] Failed to delete network for tenant 8d89b6e00bbd4d089e503995decd3ff3
 reason: Unable to complete operation on subnet c5d4d8d6-c812-42fe-a8fa-d3f18831a180. One or more ports have an IP allocation from this subnet.

This network could be deleted manually via Horizon dashboard -> Networks tab. However to do that all ports associated wth the network should be deleted first.

Environment:
existing Fuel environment, Neutron GRE network

Rally scenario:
{
    "VMTasks.boot_runcommand_delete": [
        {
            "args": {
                "flavor": {
                    "name": "net.1-2Gb-32Gb"
                },
                "image": {
                    "name": "trusty-server-cloudimg-amd64-disk1"
                },
                "script": "instance_dd_test.sh",
                "interpreter": "/bin/sh",
                "username": "ubuntu"
            },
            "runner": {
                "type": "constant",
                "times": 1,
                "concurrency": 1
            },
            "context": {
                "users": {
                    "tenants": 1,
                    "users_per_tenant": 1
                },
                "network": {
                }
            }
        }
    ]

Changed in rally:
assignee: nobody → Alexander Maretskiy (maretskiy)
Changed in rally:
status: New → Triaged
importance: Undecided → High
milestone: none → 0.0.2
milestone: 0.0.2 → none
Revision history for this message
Pavel Boldin (pboldin) wrote :

The reason is that rally have no code to remove network's ports.

Revision history for this message
Pavel Boldin (pboldin) wrote :

Patch proposed: https://review.openstack.org/c/152226/

I've ensured that it fixes the problem indeed.

Changed in rally:
assignee: Alexander Maretskiy (maretskiy) → Pavel Boldin (pboldin)
status: Triaged → In Progress
Revision history for this message
Pavel Boldin (pboldin) wrote :
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to rally (master)

Reviewed: https://review.openstack.org/152226
Committed: https://git.openstack.org/cgit/stackforge/rally/commit/?id=fe7ce24b61689a8482ce31b9361a0767b171bf86
Submitter: Jenkins
Branch: master

commit fe7ce24b61689a8482ce31b9361a0767b171bf86
Author: Pavel Boldin <email address hidden>
Date: Mon Feb 2 17:31:48 2015 +0200

    Neutron: remove ports before removing network

    Fixes rally being unable to remove network because there are still
    ports allocated under it.

    Change-Id: I1628d08d76500ec2b0f46a7520b59d0a1b8a047f
    Closes-Bug: #1414597

Changed in rally:
status: In Progress → Fix Committed
Changed in rally:
milestone: none → 0.0.2
Changed in rally:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.