REBOOTING_HARD not in expected_task_state

Bug #1379425 reported by Jesse J. Cook
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
High
Tracy Jones

Bug Description

On hard reboot, the task state is set to REBOOTING_HARD (https://github.com/openstack/nova/blob/master/nova/compute/api.py#L2213). This can be verified by rebooting twice in a row: {"conflictingRequest": {"message": "Cannot 'reboot' while instance is in task_state rebooting_hard", "code": 409}}. However, REBOOTING_HARD is not in expected_task_state (https://github.com/openstack/nova/blob/master/nova/compute/api.py#L2215). Shouldn't it be?

Revision history for this message
Jesse J. Cook (jesse-j-cook) wrote :
Changed in nova:
status: New → Confirmed
importance: Undecided → Medium
importance: Medium → High
Revision history for this message
Christopher Yeoh (cyeoh-0) wrote :

So we don't allow a hard reboot whilst hard rebooting, but there is a lot of cleanup that we could do here.

Changed in nova:
assignee: nobody → Christopher Yeoh (cyeoh-0)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

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

Changed in nova:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on nova (master)

Change abandoned by Sean Dague (<email address hidden>) on branch: master
Review: https://review.openstack.org/127427
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote :

Fix proposed again.

Revision history for this message
Park (jianlonghei) wrote :

https://bugs.launchpad.net/nova/+bug/1376384
does this bug fix the bug 1379425?

I noticed that 1376384 added REBOOTING_HARD and made some other things update.

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

This seems stalled, taking out of in progress

Changed in nova:
status: In Progress → Confirmed
assignee: Christopher Yeoh (cyeoh-0) → nobody
Changed in nova:
assignee: nobody → Tracy Jones (tjones-i)
status: Confirmed → In Progress
Revision history for this message
Diana Clarke (diana-clarke) wrote :

Indeed, I think this bug can be closed (see comment #6, thanks Park).

I could be wrong, but I think this unit test shows that this case has been fixed (doing a HARD_REBOOT when the current state is REBOOTING_HARD).

https://github.com/openstack/nova/blob/master/nova/tests/unit/api/openstack/compute/test_server_actions.py#L261

Can someone please confirm & close this bug? Thanks!

Changed in nova:
assignee: Tracy Jones (tjones-i) → nobody
status: In Progress → Incomplete
Ammar Raza (ammar-reza)
Changed in nova:
assignee: nobody → Ammar Raza (ammar-reza)
assignee: Ammar Raza (ammar-reza) → nobody
Changed in nova:
assignee: nobody → Tracy Jones (tjones-i)
status: Incomplete → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/127427
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d60497e9f9ce8a6fc54a457eaa2cdab2a817ac90
Submitter: Jenkins
Branch: master

commit d60497e9f9ce8a6fc54a457eaa2cdab2a817ac90
Author: Chris Yeoh <email address hidden>
Date: Fri Oct 10 16:44:52 2014 +1030

    Cleanup of compute api reboot method

    The interaction between the check_instance_state decorator for
    the compute api reboot method and the extra checking done within
    the method for task states was confusing and in some cases
    contradictory.

    Also several task states allowed by the decorator were implicitly
    rejected because they were not listed in the expected task_states for
    the instance save call. This too is fixed.

    Change-Id: Iba24f2ed9d2d3161318b4b1fc55c0e97d7aed1c6
    Closes-Bug: 1379425

Changed in nova:
status: In Progress → Fix Committed
Changed in nova:
status: Fix Committed → Fix Released
Revision history for this message
Thierry Carrez (ttx) wrote : Fix included in openstack/nova 13.0.0.0b2

This issue was fixed in the openstack/nova 13.0.0.0b2 development milestone.

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.