test_interrupt_avoids_respawn_storm fails when run under fakeroot

Bug #1061637 reported by Stuart McLaren
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Glance
Fix Released
Low
Stuart McLaren
Grizzly
Fix Released
Low
Stuart McLaren

Bug Description

If the functional tests are run using pbuilder then the 'test_interrupt_avoids_respawn_storm' test fails.

The following check doesn't work since the glance-api processes haven't been created with the
current setting of the "USER" environment variable.

        cmd = ("ps -fu $USER | grep glance-api | "
               "grep -v grep | awk '{print $2}' | sort -nr")

Changed in glance:
assignee: nobody → Stuart McLaren (stuart-mclaren)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to glance (master)

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

Changed in glance:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to glance (master)

Reviewed: https://review.openstack.org/14042
Committed: http://github.com/openstack/glance/commit/bcafbd2da2a9b8c361cd154925958f940e8cbce2
Submitter: Jenkins
Branch: master

commit bcafbd2da2a9b8c361cd154925958f940e8cbce2
Author: Stuart McLaren <email address hidden>
Date: Thu Oct 4 14:52:59 2012 +0000

    Multiprocess respawn functional test fix

    In 'test_interrupt_avoids_respawn_storm' the environment variable
    'USER' was being used to determine if the glance-api processes had been
    spawned correctly. This method doesn't work when running in a fakeroot
    environment. Switch to use the current UID instead which works in
    both cases.

    Fix for bug 1061637.

    Change-Id: I79e36ef02ed2adb1c951222d105d7302f4190f84

Changed in glance:
status: In Progress → Fix Committed
Brian Waldon (bcwaldon)
Changed in glance:
importance: Undecided → Low
Thierry Carrez (ttx)
Changed in glance:
milestone: none → grizzly-1
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.