Tests are leaving network resources behind

Bug #1274410 reported by Salvatore Orlando
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tempest
Fix Released
Undecided
Salvatore Orlando

Bug Description

After the changes for selectively creating resources were introduced, tempest is leaving network resources behind.
This also implies the possibility of having a consistent number of active dnsmasq and neutron-ns-metadata-proxy active processes, which could be a possibility of unexpected gate failures.

This is not a duplicate of bug 1157306

Revision history for this message
Salvatore Orlando (salvatore-orlando) wrote :

I don't know if this is related to the kernel crash, but at this stage I would try everything :)

Changed in tempest:
assignee: nobody → Salvatore Orlando (salvatore-orlando)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tempest (master)

Fix proposed to branch: master
Review: https://review.openstack.org/70169

Changed in tempest:
status: New → In Progress
Revision history for this message
Salvatore Orlando (salvatore-orlando) wrote :

The kernel bug manifests when mounting of nbd devices is combined with ip namespace operations.
Using openstack it can be reproduced only with the following configuration:
- compute service must run on the same node as the dhcp-agent and/or the l3-agent
- file injection should be turned on: libvirt.inject_partition != -2
- key injection should be enabled: libvirt.inject_key = True
- config drive should be disabled: force_config_drive = 'False' or empty string or None

If these conditions are met, nbd mount will be used to inject the key into the instance. This will trigger something in the kernel which subsequently will cause the crash in a process running in a network namespace. After this crash nbd mount won't work anymore.

Using openstack the crash can be reproduced within a few minutes with the scripts available here: https://gist.github.com/salv-orlando/8715991

- keep_booting_stuff.sh creates and destroys vms continuously, ensuring a key is always injected
- stress_me_to_death creates network namespaces, launches a process in them, kills the process and then the namespace

The two scripts require openstack and should be executed concurrently.
Crashdump data will posted as soon as possible.

It should not be too hard to provide a script that reproduces the issue and is indepedent from openstack.

Revision history for this message
Salvatore Orlando (salvatore-orlando) wrote :

sorry, wrong bug!

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tempest (master)

Reviewed: https://review.openstack.org/70169
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=cf996c653bef62f2ae71331cf45323e5f183b2be
Submitter: Jenkins
Branch: master

commit cf996c653bef62f2ae71331cf45323e5f183b2be
Author: Salvatore Orlando <email address hidden>
Date: Thu Jan 30 09:15:18 2014 -0800

    Remove network resources created in scenario tests

    Change-Id: I1bd53d99f2632441ebf648cb0c2929c9b55998b6
    Closes-Bug: #1274410

Changed in tempest:
status: In Progress → 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.