OpenStack Compute (nova)

MIGRATING status doesn't reset when an InvalidSharedStorage ERROR occurred.

Bug #1163252 reported by Hiroyuki Eguchi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Undecided
Unassigned

Bug Description

MIGRATING status doesn't reset when an InvalidSharedStorage ERROR occurred.

It seems that deserialize_remote_exception method(nova/openstack/common/rpc/common.py) create an InvalidSharedStorage_Remote ERROR dynamically from an InvalidSharedStorage ERROR,so nova-scheduler can not catch an InvalidSharedStorage ERROR.

nova-scheduler should catch an InvalidSharedStorage_Remote Error to reset MIGRATING status.

See original description
Hiroyuki Eguchi (h-eguchi)
description: updated
Revision history for this message
Vish Ishaya (vishvananda) wrote :

InvalidSharedStorage_Remote is a subclass of InvalidSharedStorage so the catch should owrk. There must be something else going on.

Changed in nova:
status: New → Incomplete
Revision history for this message
Andrew Laski (alaski) wrote :

What code version are you running? There's a fix that should address this in trunk and grizzly-rc1.

Revision history for this message
Michael Still (mikal) wrote :

Hi. Have you had a chance to test this with trunk?

Revision history for this message
Luis Russi (luisguilherme-cr) wrote :

Any news about how to fix it? Thank you.

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

2 year old bug, that was reported fixed in grizzly

Changed in nova:
status: Incomplete → 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.