test_get_console_output_server_id_in_reboot_status has issues

Bug #1014683 reported by David Kranz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tempest
Fix Released
Medium
Ken'ichi Ohmichi

Bug Description

1. It is not correct to wait for REBOOT state because it is ephemeral.
2. What if we ask for the console output when the number of lines is less than 10?
3. I don't see the purpose of waiting for the server to be ACTIVE in the finally.

Tags: tempest
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/9503

Changed in tempest:
assignee: nobody → Jay Pipes (jaypipes)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tempest (master)

Reviewed: https://review.openstack.org/9503
Committed: http://github.com/openstack/tempest/commit/257d3f847b06bbc3bed0fddde549e2ab7da13a05
Submitter: Jenkins
Branch: master

commit 257d3f847b06bbc3bed0fddde549e2ab7da13a05
Author: Jay Pipes <email address hidden>
Date: Sun Jul 8 23:01:31 2012 -0400

    Adds a script for tracking bug skips in tempest

    New file tools/skip_tracker.py can be used to show the
    status and priority of bugs that are marking test methods
    for skipping, and instruct the caller to remove skips
    on bugs that have been fixed in upstream. Output looks like this:

    jpipes@uberbox:~/repos/tempest$ python tools/skip_tracker.py
    INFO: Total bug skips found: 52
    INFO: Total unique bugs causing skips: 30
    INFO: Bug # 940500 ( Medium - Fix Released)
    INFO: Bug # 963248 ( Undecided - Invalid)
    INFO: Bug # 966249 ( Undecided - Fix Released)
    INFO: Bug # 987121 ( Medium - Fix Released)
    INFO: Bug # 988920 ( Undecided - Opinion)
    INFO: Bug # 997725 ( Medium - Fix Released)
    INFO: Bug # 999084 ( Medium - Triaged)
    INFO: Bug # 999209 ( Low - Fix Released)
    INFO: Bug # 999219 ( High - Triaged)
    INFO: Bug # 999567 ( Medium - Fix Released)
    INFO: Bug # 999594 ( Medium - In Progress)
    INFO: Bug # 999608 ( Low - Fix Released)
    INFO: Bug #1002892 ( Undecided - Invalid)
    INFO: Bug #1002901 ( Undecided - Invalid)
    INFO: Bug #1002911 ( Undecided - Invalid)
    INFO: Bug #1002918 ( Undecided - Invalid)
    INFO: Bug #1002924 ( Undecided - Incomplete)
    INFO: Bug #1002926 ( Undecided - Invalid)
    INFO: Bug #1002935 ( Undecided - Invalid)
    INFO: Bug #1004007 ( Low - Confirmed)
    INFO: Bug #1004564 ( Low - Confirmed)
    INFO: Bug #1005397 ( Undecided - Invalid)
    INFO: Bug #1005423 ( Low - Triaged)
    INFO: Bug #1006033 ( Undecided - New)
    INFO: Bug #1006725 ( Low - Triaged)
    INFO: Bug #1006857 ( Low - Confirmed)
    INFO: Bug #1006875 ( Low - Confirmed)
    INFO: Bug #1014647 ( Medium - Confirmed)
    INFO: Bug #1014683 ( Undecided - New)
    INFO: Bug #1022411 ( Undecided - In Progress)
    The following bugs have been fixed and the corresponding skips
    should be removed from the test cases:

       940500
       966249
       987121
       997725
       999209
       999567
       999608

    Change-Id: Ic58fc8beb2f6134504d4eb2f6ebe40fa24fe06f6

Changed in tempest:
status: In Progress → Fix Committed
Changed in tempest:
status: Fix Committed → In Progress
tags: added: 1014683
tags: added: tempest
removed: 1014683
Revision history for this message
Attila Fazekas (afazekas) wrote :

IMHO We should tag the ephemeral test cases with 'ephemeral ', attribute, and we should not run them by default.
Or we should remove them.

Revision history for this message
Sean Dague (sdague) wrote :

Can you explain what you mean by ephemeral?

Revision history for this message
Attila Fazekas (afazekas) wrote :

Nothing grantees the system is slow enough to see these statuses with low sample rate (1-3 second) .

These statuses are transitional statuses. Not a stable statuses. Normally they will be leaved without any interaction. The time spend in these statuses are not deterministic.

If we keep these kind of test cases, making openstack faster will causes issues. Some of these test cases already can cause issues on ultrafast machines.

Changed in tempest:
importance: Undecided → Medium
status: In Progress → Confirmed
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/59116

Changed in tempest:
assignee: Jay Pipes (jaypipes) → Ken'ichi Ohmichi (oomichi)
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tempest (master)

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

commit 547a306af133f1ca9588bfba026081cca26f93b4
Author: Ken'ichi Ohmichi <email address hidden>
Date: Mon Dec 2 09:30:36 2013 +0900

    Change unstable test which gets console output

    We don't necessarily get "REBOOT" status of a server because the
    state is ephemeral. As the result, the test fails sometimes.
    This patch changes the server status from "REBOOT" to "SHUTOFF" for
    stable test condition.

    Closes-Bug: #1014683
    Change-Id: I4b06b148b5d9bceda0cef2d2bb5f3b72325928ac

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.