devstack

Screen is causing non-deterministic behaviour

Bug #1183449 reported by Dean Troyer
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
devstack
Fix Released
High
Dean Troyer
grenade
Invalid
High
Dean Troyer

Bug Description

Screen does not reliably stop services in a small amount if time, similar to the issues that caused us to change DevStack to not use screen in the CI testing. The correct fix is to add a screen_stop() function that knows how to properly stop services when screen is in use and when it is not. Then we can switch Grenade to USE_SCREEN=False and eliminate screen from the indeterminate failure list.

Dean Troyer (dtroyer)
affects: grenade → devstack
Changed in devstack:
importance: Undecided → Medium
Changed in grenade:
importance: Undecided → High
Changed in devstack:
importance: Medium → High
assignee: nobody → Dean Troyer (dtroyer)
Changed in grenade:
assignee: nobody → Dean Troyer (dtroyer)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to devstack (master)

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

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

Reviewed: https://review.openstack.org/66080
Committed: https://git.openstack.org/cgit/openstack-dev/devstack/commit/?id=9fc8792b0ac7525b4c353b0a55b8b80eabf76e2a
Submitter: Jenkins
Branch: master

commit 9fc8792b0ac7525b4c353b0a55b8b80eabf76e2a
Author: Dean Troyer <email address hidden>
Date: Wed May 22 17:19:06 2013 -0500

    Robustify service shutdown

    * Save PID when using screen in screen_it()
    * Add screen_stop()
    * Call out service stop_*() in unstack.sh functions so screen_stop()
      can do its thing

    Closes-bug: 1183449
    Change-Id: Iac84231cfda960c4197de5b6e8ba6eb19225169a

Changed in devstack:
status: In Progress → Fix Released
Revision history for this message
Sean Dague (sdague) wrote :

This grenade bug was last updated over 180 days ago, as grenade
is a fast moving project and we'd like to get the tracker down to
currently actionable bugs, this is getting marked as Invalid. If the
issue still exists, please feel free to reopen it.

Changed in grenade:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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